| Author |
Message
|
| scero |
 Posted: Tue May 29, 2007 2:41 am Post subject: JMSAdmin does not return to command line |
 |
|
Newbie
Joined: 29 May 2007
Posts: 3
|
I am using JMSAdmin to bind objects (connection factories and queues) to a contact admin registry (version 4.3.4) using a cmi initial context factory:
INITIAL_CONTEXT_FACTORY=org.objectweb.carol.cmi.jndi.CmiInitialContextFactory
The objects are correctly bound to the registry and can be retrieved as long as I leave JMSAdmin open. The JMSAdmin tool however cannot be terminated. Entering the END command will print a message saying that it will stop, however it never returns to the command line. If I quit via CTRL+C, I cannot access the JMS objects anymore (althought they still seem to be bound to the registry).
I cannot use this solution if it means that the JMSAdmin session has to remain open all the time.
Any ideas?
Btw: I get a similar problem when using jeremie instead of cmi. |
|
| Back to top |
|
 |
| rparti |
| Posted: Fri Jun 01, 2007 11:48 am Post subject: |
|
|
Voyager
Joined: 05 Oct 2005
Posts: 86
Location: U.S.A.
|
You might have to run JMS Admin in the background.
I think it has to be running to receive your initial context |
|
| Back to top |
|
|
| scero |
| Posted: Fri Jun 08, 2007 8:18 am Post subject: |
|
|
Newbie
Joined: 29 May 2007
Posts: 3
|
| OK, suppose you do that - then how do you end JMSAdmin correctly (which means without just killing the process)...? |
|
| Back to top |
|
|
| rparti |
| Posted: Fri Jun 08, 2007 8:23 am Post subject: |
|
|
Voyager
Joined: 05 Oct 2005
Posts: 86
Location: U.S.A.
|
If you just use kill it ends the process gracefully like a shutdown
If you use kill -9 it does a force shotdown which is bad |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jun 08, 2007 9:19 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I think you're both confused about the contact admin registry and how it's supposed to work, and the role of JMSAdmin.
But I don't know anything about how the contact admin registry is supposed to work, so I can't say for sure what's going wrong.
Regardless, JMSAdmin is not supposed to be a JNDI server of any kind. It's merely supposed to update an existing JNDI registry with new or changed information.
From the information scero has provided, I'm guessing that the thing that is supposed to be the JNDI server for contact admin is not being started correctly, and JMSAdmin's attemtps to access the context are causing things to try to treat it as a JNDI server.
But that's an extremely wide guess, based on almost no meaningful information at all.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| scero |
| Posted: Fri Jun 22, 2007 6:22 am Post subject: |
|
|
Newbie
Joined: 29 May 2007
Posts: 3
|
Yes, JMSAdmin is just a tool to bind objects to a registry - and not a server at all.
The problem I have is: I start a WMQ, I start a contact admin registry (actually, it is really just the registry service that is started) that acts as a JNDI server, and I then want to bind the objects to the registry, with the configuration I described in the first post. But the JMSAdmin tool does not quit correctly.
Bottom line: you may be right that the JNDI server is not started/configured correctly in order to work with the JMSAdmin utility. That would be a valid explanation. So if anybody has ever had a similar problem... |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jun 22, 2007 12:32 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Do you have
END
as the last line in your JMSAdmin script?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
