I don't see why this problem in the client would cause log4j to stop working. On the server side, the only thing that might happen when the client crashes is a connection warning. This warning is printed with the communicator logger which by default prints to stderr. This warning only shows up if you have Ice.Warn.Connections set to 1. If that's the case you could try disabling it to see if it makes a difference.
Cheers,
Benoit.

Reply With Quote