I have a simple stateless session bean and a simple client that connects to it through jndi. If the ejb object the client holds goes stale(the server goes down), I want to catch the exception, retrieve a new object and process the clients request. When I do the new lookup though, the client trys to use its existing tcp connection to jndi and gets a connection refused to host exception. If I retry the lookup it now works and my client never knows the object went stale.
My question is: Is retrying the lookup a couple of times safe solution or is this some fluke of a development environment that won't work the same way in production?
Thanks for any input.
You don't say which version you are using,
but it is probably related to this bug?
http://sourceforge.net/tracker/index.php?func=detail&aid=637730&group_id=22866&atid=376685
Regards,
Adrian