Kind of yes.   They are relatively harmless and as I've seen them, I've been 
trying to fix them.  It's basically due to there not being a "I'm done with 
this proxy" thing on the JAX-WS proxies.   If you call 
ClientProxy.getClient(proxy).close() on the client proxy, the problem should 
go away as the JMS listeners and such can be properly shutdown.

Dan



On Monday 27 September 2010 6:33:27 pm Benson Margulies wrote:
> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> Running org.apache.cxf.systest.factory_pattern.MultiplexClientServerTest
> [WARN,SingleConnectionFactory,ActiveMQ Connection Worker:
> tcp://localhost/127.0.0.1:55198] Encountered a JMSException -
> resetting the underlying JMS Connection
> javax.jms.JMSException: java.io.EOFException
>       at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.ja
> va:49) at
> org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection
> .java:1803) at
> org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java
> :1820) at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.
> java:99) at
> org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorre
> lator.java:126) at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.
> java:99) at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.
> java:99) at
> org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatN
> egotiator.java:160) at
> org.apache.activemq.transport.InactivityMonitor.onException(InactivityMoni
> tor.java:254) at
> org.apache.activemq.transport.TransportSupport.onException(TransportSuppor
> t.java:97) at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:190)
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.EOFException
>       at java.io.DataInputStream.readInt(DataInputStream.java:375)
>       at
> org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:
> 269) at
> org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.ja
> va:211) at
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:203
> ) at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:186)
> ... 1 more
> [WARN,SingleConnectionFactory,ActiveMQ Connection Worker:
> tcp://localhost/127.0.0.1:55198] Encountered a JMSException -
> resetting the underlying JMS Connection
> javax.jms.JMSException: java.io.EOFException
>       at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.ja
> va:49) at
> org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection
> .java:1803) at
> org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java
> :1820) at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.
> java:99) at
> org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorre
> lator.java:126) at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.
> java:99) at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.
> java:99) at
> org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatN
> egotiator.java:160) at
> org.apache.activemq.transport.InactivityMonitor.onException(InactivityMoni
> tor.java:254) at
> org.apache.activemq.transport.TransportSupport.onException(TransportSuppor
> t.java:97) at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:190)
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.EOFException
>       at java.io.DataInputStream.readInt(DataInputStream.java:375)
>       at
> org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:
> 269) at
> org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.ja
> va:211) at
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:203
> ) at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:186)
> ... 1 more
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.412 sec
> 
> Results :
> 
> Tests run: 22, Failures: 0, Errors: 0, Skipped: 1

-- 
Daniel Kulp
dk...@apache.org
http://dankulp.com/blog

Reply via email to