-
1. Re: Exiting on IOE java.net.SocketException: socket closed
genman Jul 12, 2005 9:19 PM (in response to geniusfox)
It's DEBUG my friend, if it were an error you'd see ERROR in the logs. -
2. Re: Exiting on IOE java.net.SocketException: socket closed
geniusfox Jul 12, 2005 10:04 PM (in response to geniusfox)But, When i catch too many "close exception",then Jboss would send a "Sockte:Open too many files" and stop work.
How can i fill it. -
3. Re: Exiting on IOE java.net.SocketException: socket closed
viky4u Nov 9, 2005 11:31 PM (in response to geniusfox)Well the same is happening to me !
Did u find a work around for this ?
I get this when iam browsing the queue.
Thanks
Vigneesh -
4. Re: Exiting on IOE java.net.SocketException: socket closed
viky4u Nov 10, 2005 12:28 AM (in response to geniusfox)You might want to watch this topic
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3906491#3906491
Thanks
Vignesh -
5. Re: Exiting on IOE java.net.SocketException: socket closed
fsanti Mar 19, 2007 8:59 AM (in response to geniusfox)This is an old topic, but since there is not much information about this issue, it could be useful ...
I had the same problem when I tried to get the connection factory from JNDI "/ConnectionFactory". The code works fine, messages can be sent and received sucessfully, but generating a lot of server.log entries...
I did the same thing sucessfully when I changed the connection factory to "/QueueConnectionFactory".
ConnectionFactory = (ConnectionFactory)ic.lookup("/QueueConnectionFactory");