Hi, I've just subscribed to this list and so apologize if this question has been answered already.
Last week I ported an application 'jaba server' from an earlier avalon implementation to avalon4.1.3/pheonix 4.0.1. These symptons did not occur with the earlier implementation. i recompiled the app using the new version's lib and jdk1.3 (I also tried with jdk 1.4 less the xerces stuff and experienced the same symptons). What happens is 1. a client makes a socket connection with the server (server socket manager is using the cornerstone lib) 2. the client sends an xml message to the server. 3. the server acts on the message and replies with an xml message 4. the client receives the first message and continues to read the stream for more xml 5. the server attempts to emit the subsequent xml messages but on the 2nd message attempt finds the socket closed 6. the avalon-default log shows --> DEBUG 2002-11-13 15:14:21.079 [thread-m] (): Retrieving a org.apache.avalon.excalibur.thread.impl.WorkerThread from the pool DEBUG 2002-11-13 15:14:21.210 [thread-m] (): Retrieving a org.apache.avalon.excalibur.thread.impl.WorkerThread from the pool DEBUG 2002-11-13 15:14:21.260 [jaba-lis] (): Will publish block: jaba-publisher DEBUG 2002-11-13 15:14:21.270 [thread-m] (): Retrieving a org.apache.avalon.excalibur.thread.impl.WorkerThread from the pool DEBUG 2002-11-13 15:14:21.300 [jaba-pub] (): Publishing object [as: jabaserver, impl: [EMAIL PROTECTED], interf: class org.novadeck.jabaserver.core.Server] DEBUG 2002-11-13 15:17:03.613 [thread-m] (): Retrieving a org.apache.avalon.excalibur.thread.impl.WorkerThread from the pool DEBUG 2002-11-13 15:17:03.623 [connecti] (): Starting connection on 192.168.0.2 DEBUG 2002-11-13 15:17:09.542 [connecti] (): Ending connection on 192.168.0.2 DEBUG 2002-11-13 15:17:09.552 [thread-m] (): Returning a org.apache.avalon.excalibur.thread.impl.WorkerThread to the pool DEBUG 2002-11-13 15:24:01.835 [thread-m] (): Retrieving a org.apache.avalon.excalibur.thread.impl.WorkerThread from the pool I cannot find any deliberate code in the client or server app that deliberately closes the socket and all ioexceptions are caught and logged as far as i can tell. Can someone tell me whether i am bumping up against a cornerstone bug or some configuration issure... Any help would be appreciated! Thanks! Ed
