lenchan
Sep 12th, 2004, 11:05 AM
Anyone using the above combination?
1. Really interested to know how you are dealing with JNDI setup in WebLogic. MQ normally uses filesystem as the JNDI provider. So, do you guys just use that, or you use a WebLogic startup class (example provided by WebLogic) to load configuration into WebLogic's JNDI tree?
2. With WebSphere MQ 5.3, are you using JMS 1.0.2 or 1.1? Just curious to know.
3. Our MQ environment is not very stable at the moment (i.e. queue managers or network can go down intermittently), so I'm trying to find ways to deal with that. If the queue manager is down (and then restarted), what is the best way to recreate Connection/Session objects specified in the applicationContext.xml?
4. JMSException will only be thrown if a send or sync receive is attempted when the connection has problems. For async receive (using MessageListener), it has no idea that the connection is gone and still sits there waiting (even after the queue manager is up and running again). I understand that ExceptionListener is designed to be used especially in the case of async receive, but I am unclear under what situation will the ExceptionListener be invoked by MQ 5.3? I am prototyping with ActiveMQ 1.0, but I cannot see ExceptionListener getting invoked at all :-(
5. I suppose I can also have a scheduled task (using Quartz or otherwise) that runs periodically to check the connection(s).
1. Really interested to know how you are dealing with JNDI setup in WebLogic. MQ normally uses filesystem as the JNDI provider. So, do you guys just use that, or you use a WebLogic startup class (example provided by WebLogic) to load configuration into WebLogic's JNDI tree?
2. With WebSphere MQ 5.3, are you using JMS 1.0.2 or 1.1? Just curious to know.
3. Our MQ environment is not very stable at the moment (i.e. queue managers or network can go down intermittently), so I'm trying to find ways to deal with that. If the queue manager is down (and then restarted), what is the best way to recreate Connection/Session objects specified in the applicationContext.xml?
4. JMSException will only be thrown if a send or sync receive is attempted when the connection has problems. For async receive (using MessageListener), it has no idea that the connection is gone and still sits there waiting (even after the queue manager is up and running again). I understand that ExceptionListener is designed to be used especially in the case of async receive, but I am unclear under what situation will the ExceptionListener be invoked by MQ 5.3? I am prototyping with ActiveMQ 1.0, but I cannot see ExceptionListener getting invoked at all :-(
5. I suppose I can also have a scheduled task (using Quartz or otherwise) that runs periodically to check the connection(s).