Exception not caught when a socketserver isn't running

["Schuweiler, Joel J." <Sc...@mayo.edu>]

 java.net.ConnectException: Connection refused: connect

Get's thrown if there is no socket server to connect to. This is with log4j version 1.2.11 I don't think I experienced said behavior with 1.2.9

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org

Re: Exception not caught when a socketserver isn't running

[Jacob Kjome <ho...@visi.com>]

At 03:28 PM 6/28/2005 -0500, you wrote:
 > java.net.ConnectException: Connection refused: connect
 >
 >Get's thrown if there is no socket server to connect to. This is with log4j
 >version 1.2.11 I don't think I experienced said behavior with 1.2.9
 >

I think you should retry with 1.2.9.  I'm using it and if there is no 
socket server to connect to, 1.2.9 will *definitely* throw an exception 
which you will see in the console.  Are you saying that it bombs out your 
app?  It shouldn't.  It's simply annoying.  In Log4j-1.3, this should be 
more of a warning, not a print of the stack trace which is a bit more 
alarming than it should be.


Jake 


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org