On Thu, 2003-09-18 at 09:53, Daniel Krieg wrote: > I am righting an application that uses PhoenixJMS as a block with > another block acting as a client -- through standard JMS API. There was > a problem with the current Block implement that I pulled from CVS. The > EmbeddedJmsServer is executed in a separate Thread during Block > initialization. Unfortunately, the JMS server does not complete its > startup sequence before the client block requests a ConnectionFactory. > Furthermore, the Block does not cleanup on shutdown. I have created a > separate Block implementation (specific to Phoenix) that resolves these > issues and thought I would share it with the community...do with it as > you will. :) I thought that I would also mention that in order for Phoenix to shutdown correctly, the client block must declare a dependency on the JMSServer otherwise the shutdown sequence will not force the JMS client block to shutdown before the JMSServer, thus causing the JMSServer to throw an exception on shutdown.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
