Problem: many clients to try lookup a session bean concurrently. If the client count
reaches a certain number, the lookup fails with:
[java] javax.naming.CommunicationException: Receive timed out [Root exception is
java.net.SocketTimeoutException: Receive timed out]
[java] at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1119)
[java] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1196)
[java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:516)
[java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:509)
[java] at javax.naming.InitialContext.lookup(InitialContext.java:347)
Setting the "backlog" param of the naming service to a higher value does not have any
effect.
Is there any workaround to avoid this? Otherwise it is not possible to access EJBs
from many clients.
Thanks,
marek
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3843064#3843064
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3843064
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
