Brian,
are you using the same SwiftMQ versions for each the router and the
client? This might be a reason for hanging.
Is there something in the error.log?
To get deeper into the SwiftMQ internals, you must enable tracing. In the
property file is a section for the "sys$trace" Swiftlet. There are several
trace spaces defined. All of them have an entry "...enabled=false". Set
all those entries to true, run the stuff again (try to connect via CLI)
and kill the router. Then go to the respective trace directory and check
the protocol.trace (contains the SMQP interactions) and the jms.trace
(contains the JMS interactions). Maybe you find the problem. If not, send
both files to me (not to the list, please: [EMAIL PROTECTED]).
If all that stuff doesn't work, you can also use the Invokation API to
spawn a separate JVM for SwiftMQ (instead of calling the router's main
method) from within a C/C++ program. That should work in any case.
HTH!
--
Andreas Mueller, [EMAIL PROTECTED], IIT GmbH, Bremen/Germany, http://www.iit.de
SwiftMQ, JMS Enterprise Messaging System, http://www.swiftmq.com
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
