Got Marshalling Exception when JMSWire Format writes object to Socket
---------------------------------------------------------------------
Key: JBMESSAGING-1869
URL:
https://issues.jboss.org/browse/JBMESSAGING-1869
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager, JMS Remoting
Affects Versions: 1.4.0.SP3.CP10
Environment: Windows, JBoss EAP 4.3.0.CP08
Reporter: Nordine B
We are using Spring's Message Driven Pojo to consume messages.
At startup when the MDP is lauched, we have the following exception:
12:09:43,656 INFO [STDOUT] 12:09:43.656 [MOMWorkManagerThreadPool(3)-8]]
INFO fr.msa.agora.socle.g2.mom.internal.MDPContainerListenerImpl - Successfully
refreshed JMS Connection
12:09:43,687 ERROR [SocketClientInvoker] Got marshalling exception, exiting
java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:375)
at org.jboss.jms.wireformat.JMSWireFormat.read(JMSWireFormat.java:288)
at
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedRead(MicroSocketClientInvoker.java:1036)
at
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:694)
at
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:458)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:141)
at org.jboss.remoting.Client.invoke(Client.java:1935)
at org.jboss.remoting.Client.invoke(Client.java:788)
at org.jboss.remoting.Client.invoke(Client.java:776)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
at
org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$closing$aop(ClientConsumerDelegate.java:129)
at
org.jboss.jms.client.delegate.ClientConsumerDelegate$closing_2473194355759371067.invokeNext(ClientConsumerDelegate$closing_2473194355759371067.java)
at org.jboss.jms.client.container.ConsumerAspect.handleClosing(ConsumerAspect.java:144)
at
org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect36.invoke(ConsumerAspect36.java)
at
org.jboss.jms.client.delegate.ClientConsumerDelegate$closing_2473194355759371067.invokeNext(ClientConsumerDelegate$closing_2473194355759371067.java)
at
org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at
org.jboss.jms.client.delegate.ClientConsumerDelegate$closing_2473194355759371067.invokeNext(ClientConsumerDelegate$closing_2473194355759371067.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:172)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at
org.jboss.jms.client.delegate.ClientConsumerDelegate$closing_2473194355759371067.invokeNext(ClientConsumerDelegate$closing_2473194355759371067.java)
at
org.jboss.jms.client.delegate.ClientConsumerDelegate.closing(ClientConsumerDelegate.java)
at org.jboss.jms.client.JBossMessageConsumer.close(JBossMessageConsumer.java:96)
at
org.springframework.jms.connection.CachingConnectionFactory$CachedSessionInvocationHandler.physicalClose(CachingConnectionFactory.java:418)
at
org.springframework.jms.connection.CachingConnectionFactory$CachedSessionInvocationHandler.invoke(CachingConnectionFactory.java:305)
at $Proxy133.close(Unknown Source)
at
org.springframework.jms.connection.JmsResourceHolder.closeAll(JmsResourceHolder.java:195)
at
org.springframework.jms.connection.JmsTransactionManager.doCleanupAfterCompletion(JmsTransactionManager.java:264)
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.cleanupAfterCompletion(AbstractPlatformTransactionManager.java:1011)
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:804)
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723)
at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:255)
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1056)
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:952)
at org.springframework.jca.work.DelegatingWork.run(DelegatingWork.java:57)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:213)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
at java.lang.Thread.run(Thread.java:662)
The exception repeats while MDP try to refresh the connection.
0
The strange thing is that if we replace jboss-messaging-client.jar 1.4.0.SP10 by the
1.4.0.SP08 version, everything works perfectly.
You may know that we have applied Slimming on our JBoss EAP 4.3CP08
(
http://community.jboss.org/wiki/JBoss4xSlimming)
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira