That is a windows tcp error:
WSAENOBUFS(10055):
An operation on a socket could not be performed because the system lacked sufficient
buffer space or because a queue was full.
Your creating too many connections for your OS. Try keeping one InitialContext
around instead of creating every time or look into tweaking the OS tcp
parameters.
----- Original Message -----
From: "Greg Merrill" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 15, 2001 12:19 PM
Subject: [JBoss-user] inconsistent (but frequent) InitialContext.lookup() problems
> I have recently begun having serious problems
> retrieving beans from JNDI. For some reason,
> InitialContext.lookup() keeps throwing a
> CommunicationException. However, it doesn't always
> happen! (Although after it happens once, it happens
> fairly consistently until a re-deploy or restart
> JBoss, at which times it will *sometimes* recover.)
> Has anyone seen this (or anything like this) before?
> I'm stumped.
>
> My context properties are:
> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
> java.naming.provider.url=localhost:1099
> java.naming.factory.url.pkgs=org.jboss.naming
>
> Here is the stack trace:
> javax.naming.CommunicationException. Root exception
> is java.rmi.ConnectIOException: Exception creating
> connection to: 24.250.12.187; nested exception is:
> java.net.SocketException: no further information
> (code=10055)
> java.net.SocketException: no further information
> (code=10055)
> at java.net.PlainSocketImpl.socketConnect(Native
> Method)
> at
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
