> I had the same problem until I discovered the following. If you look
> at the
> sample JMS programs that came with SwiftMQ, you will see they all call
> SampleUtilities.exit(exitResult). Looking at the code for that exit()
> method, you find the following. Note the comment.
>
> /**
> * The exit method is needed because of an RMI/IIOP bug that
> causes
> JMS
> * programs to exit only with an explicit call to
> System.exit().
> *
> * @param result The exit result; 0 indicates no errors
> */
> public static void exit(int result) {
>
> System.exit(result);
> }
That is a comment for the JMS RI from Sun (the examples are from Sun;
SwiftMQ doesn't use RMI/IIOP).
If the client doesn't terminate then the InitialContext is probably not
closed properly (it holds an active JMS connection). A 'ctx.close()'
should help.
--
Andreas Mueller, 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/
