Yes, it should.  It does this by doing a JNDI lookup of the bean invoker stub.  
If it's failing to reconnect, I suspect the problem is the JNDI lookup is 
failing.

What are your jndi.properties? And is auto-discovery turned on in the HA-JNDI 
service on the server side? (It is by default; you'd have to explicitly turn it 
off.)

The RetryInterceptor will just use a default InitialContext() unless you pass a 
set of JNDI properties to the static RetryInterceptor.setRetryEnv() method. 
Often people don't do that (it requires a call to JBoss-specific code).  But, 
even if you don't do it, the default InitialContext() should eventually fall 
back to auto-discovery of HA-JNDI and find the cluster that way.

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921268#3921268

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921268


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to