That stack is printed by either server or client side when the opposite side dies.
It is printed all the time (even with no debug) and the user can not catch it.
If it participates of the standard connector behavior, it should be completely masked to the end user.
It there is matter of printing a regular WARNING level message, it should be a fully informative message without the stack.
Note the 'GenericConenctor' typo.

Dec 23, 2003 10:50:45 AM GenericConenctor RequestHandler-connectionException
WARNING: java.io.EOFException
java.io.EOFException
        at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2438)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1245)
        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
        at com.sun.jmx.remote.socket.SocketConnection.readMessage(SocketConnection.java:211)
        at com.sun.jmx.remote.generic.SynchroMessageConnectionImpl$MessageReader.run(SynchroMessageConnectionImpl.java:409)
        at com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:208)
        at com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:59)