Cannot delete administered object (version number propery
I have two administered objects that can't be deleted, and I have no clue where reference to them are kept:
Here is an excerpt of my admin'ed objects listing:
(...)
Listing all administered objects in the object store specified by:
java.naming.factory.initialcom.sun.jndi.fscontext.RefFSContextFactory
java.naming.provider.urlfile:///global/bmq/nfs/shared/managed-objects-fs
Lookup Name Object Class Name
BankQueueConnectionFactory com.sun.messaging.QueueConnectionFactory
BankSecureQueueConnectionFactorycom.sun.messaging.QueueConnectionFactory
cn=BankQueueConnectionFactorycom.sun.messaging.QueueConnectionFactory
cn=QueueConnectionFactorycom.sun.messaging.QueueConnectionFactory
(...)
The objects I'd like to delete are the ones starting with "cn=".
Running the following command:
[b]
# imqobjmgr \
-j java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory \
-j java.naming.provider.url=file:///global/bmq/nfs/shared/managed-objects-fs \
delete -l cn=BankQueueConnectionFactory
[/b]
Results in the following output (and my admin'ed object is still around!):
Deleting the administered object with the following lookup name:
cn=BankQueueConnectionFactory
In the object store specified by:
java.naming.factory.initialcom.sun.jndi.fscontext.RefFSContextFactory
java.naming.provider.urlfile:///global/bmq/nfs/shared/managed-objects-fs
Error [A3060]: The object cn=BankQueueConnectionFactory is missing the version number property.
Object deletion failed.
What is the "version number property" ?
Also, each time I start the Admin Console (or refresh the objectstore), it complains about those object not being found. Using the imqobjmgr command, I can see them.
Thanks for your much appreciated help.
[1997 byte] By [
TiT] at [2007-12-5]

The JNDI bindings file that contains the objects should be located at
file:///global/bmq/nfs/shared/managed-objects-fs/.bindings
It looks like the version number is missing for those objects.
You can manually delete all references in the .bindings file
for those objects or we can take a look at your .bindings file. If you prefer to
not post it to this Forum, you can send the file to mq-feedback@sun.com
in which case it will go directory to the MQ team. Thanks.
I've deleted the entries from the ".bindings" file, and the GUI stops complaining. OK. Thank you for providing that workaround.
But, still, I'm wondering how I could create these objects using either the GUI or the command line (imqobjmgr), and not delete them afterwards using these very same tools.
What is a "version number property" ? How could I spot it on other objects in the ".bindings" files ? Is there any documentation about that (no result on docs.sun.com) ?
Little offside note: before posting my earlier "syslog" problem on this forum, which btw ended up being an undiscovered bug, I've tried the "mq-feedback@sun.com" mailing list, but did not get any reply at all.
If you would like to investigate further, I've kept a copy of the old ".bindings" file that I could send to "mq-feedback@sun.com", if it really is still active.
Thanks.
TiT at 2007-7-7 >

There is a version property string stored with each
administered object. That version is used to
determine how to handle the object so there is some
code that checks the version of the object as soon
as it is referenced.
To determine why your .bindings file doesn't have
that property, we need to look at it.
Please try sending your .bindings file to mq-feedback@sun.com again.
After you send it, you should get an automated email that says you
need to reply to the message in order for it to get past the spam
filters. If you did reply to that mail last time, then it could be a
problem with the filters on our side. Let us know after you send it
this time and we'll keep an eye for it over here in the mail logs.
Please send us the MQ version you used to add the admin. object,
the MQ version you used to delete the admin. object, and the
platform you are running on. Also, send us the imqobjmgr .properties
file (or list of attributes) you used when adding the admin. object
so that we can try and reproduce. Thanks.