[jboss-user] [JBoss Messaging] - java.rmi.MarshalException: Failed to communicate. Problem d
anonymous wrote :
|
| Hi,
|
| We have deployed the JBoss 4.2.3 with JBoss-messaging-1.4 in production environment.
|
| And it is working fine but we can see some errors in JBoss console at some time. Those
exceptions are pasted below.
|
| Please any body have the idea to what is the impact of this exception and steps to
resolve this.
|
|
|
| 20:37:38,098 WARN [SimpleConnectionManager] A problem has been detected with the
connection to remote client a04c-61m6zr-fn37yfu2-1-fn39ixky-w,
jmsClientID=b-a5ky73nf-1-2ufy73nf-rz6m16-c40a. It is possible the client has exited
without closing its connection(s) or the network has failed. All connection resources
corresponding to that client process will now be removed.
| 20:37:38,168 ERROR [ExceptionUtil]
ConnectionEndpoint[f21-y81v83nf-1-e21b83nf-j857ym-56js4] close
[vv1-wilx83nf-1-e21b83nf-j857ym-56js4]
| java.lang.NullPointerException
| at
org.jboss.jms.server.endpoint.ServerSessionEndpoint.localClose(ServerSessionEndpoint.java:1192)
| at
org.jboss.jms.server.endpoint.ServerConnectionEndpoint.close(ServerConnectionEndpoint.java:385)
| at
org.jboss.jms.server.connectionmanager.SimpleConnectionManager.closeConsumersForClientVMID(SimpleConnectionManager.java:377)
| at
org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleClientFailure(SimpleConnectionManager.java:173)
| at
org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleConnectionException(SimpleConnectionManager.java:200)
| at
org.jboss.remoting.ConnectionNotifier.connectionLost(ConnectionNotifier.java:50)
| at org.jboss.remoting.Lease.notifyClientLost(Lease.java:211)
| at org.jboss.remoting.Lease.access$500(Lease.java:39)
| at org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:249)
| at java.util.TimerThread.mainLoop(Timer.java:512)
| at java.util.TimerThread.run(Timer.java:462)
|
|
|
|
|
| =================================================================
|
|
|
| 11:59:41,848 ERROR [ServerInvokerCallbackHandler] Error handling callback
| java.rmi.MarshalException: Failed to communicate. Problem during
marshalling/unmarshalling; nested exception is:
| java.io.IOException: Connection reset
| at
org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:122)
| at
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:669)
| at
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:418)
| at
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
| at org.jboss.remoting.Client.invoke(Client.java:1634)
| at org.jboss.remoting.Client.invoke(Client.java:548)
| at org.jboss.remoting.Client.invokeOneway(Client.java:598)
| at
org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:826)
| at
org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:697)
| at
org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1432)
| at
org.jboss.jms.server.endpoint.ServerSessionEndpoint.handleDelivery(ServerSessionEndpoint.java:1344)
| at
org.jboss.jms.server.endpoint.ServerConsumerEndpoint.handle(ServerConsumerEndpoint.java:322)
| at
org.jboss.messaging.core.impl.RoundRobinDistributor.handle(RoundRobinDistributor.java:119)
| at
org.jboss.messaging.core.impl.MessagingQueue$DistributorWrapper.handle(MessagingQueue.java:582)
| at
org.jboss.messaging.core.impl.ClusterRoundRobinDistributor.handle(ClusterRoundRobinDistributor.java:79)
| at
org.jboss.messaging.core.impl.ChannelSupport.deliverInternal(ChannelSupport.java:606)
| at
org.jboss.messaging.core.impl.MessagingQueue.deliverInternal(MessagingQueue.java:505)
| at
org.jboss.messaging.core.impl.ChannelSupport.deliver(ChannelSupport.java:356)
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187192#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...