-
1. Re: Reconnect to remote JMS / TopicConnection after reoboot As7
jbertram May 12, 2012 12:07 AM (in response to suikast42)It looks to me like you're using a stale InitialContext. In other words, you create the InitialContext and use it for a lookup, but once the server is restarted the InitialContext becomes stale and you need to create a new one. When you receive an exception on javax.naming.InitialContext.lookup() try invoking restart() and attempting the lookup again. I believe this is related to this feature request: AS7-4508.
-
2. Re: Reconnect to remote JMS / TopicConnection after reoboot As7
suikast42 May 12, 2012 6:46 AM (in response to jbertram)Hi Justin,
Thanks for reply. If you execute the attached example app you will see that the ejb lookup survives the reboot but the jms lookup doesn't. It seems so that this feature only implmented for ejb lookups at the moment.
-
3. Re: Reconnect to remote JMS / TopicConnection after reoboot As7
suikast42 May 16, 2012 6:20 AM (in response to suikast42)So the reconnection works now. See https://issues.jboss.org/browse/AS7-4508?focusedCommentId=12693189#comment-12693189
-
4. Re: Reconnect to remote JMS / TopicConnection after reoboot As7
thinksteep Oct 3, 2012 12:28 PM (in response to jbertram)Hi Justin, I am having similar issue and even when I try to create new InitialContext and do a lookup, it is failing. What might be going wrong? Any input would be appreciated. As well as, is there any way we can use remote-naming-1.4 jar in JBoss 7.1.1.Final? Thanks for your time and help.
-
5. Re: Reconnect to remote JMS / TopicConnection after reoboot As7
jbertram Oct 3, 2012 12:40 PM (in response to thinksteep)While your issue may be similar, if it is different at all (which it appears to be) you should open a new thread instead of hi-jacking an existing one.