This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I would like to know if JMS Topic destinations would still be able to Publish and Subscribe the messages if the weblogic server goes down and is restarted. Well, I know that it wont as the JMS will still be working on with the old instance of the weblogic server. I think one way to avoid this to cluster but is that the only solution. Without clustering can't we some how let the JMS server know about the new instance of the WebLogic (after resart), so that we can still have the application publishing and subcribing the messages. Because, I have a JMS application which has to be restarted every time WebLogic goes down and want to make this automated such that the application will configure the new instance of weblogic and will continue the messaging. Any help and knowledge sharing in this matter would be greatly appreciated. Thanks. Venkat
Venkat, in one of the projects we had used IBM MQSeries JMS server along with Weblogic. The MDB deployed on weblogic server will listen to messages posted to queues on MQSeries server. In this case even when the weblogic goes down the messages can be posted to MQ Queues and once the WLS server comes up it will obtain the reference to MQ Queues and start consuming messages lying in the queues.