Affects: Release Notes project_key: JBPAPP6 Reopened AS7-3180 Technical details tracked here https://issues.jboss.org/browse/AS7-3180 Excerpt from current logging https://issues.jboss.org/browse/AS7-3180?focusedCommentId=12676146&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12676146
Link: Added: This issue is related to JBPAPP-7577
Link: Added: This issue Cloned from AS7-3180
If anyone looms in here: The logging has now changed after adding the ExternalizerTable into: {noformat} [JBossINF] 10:53:32,192 WARN [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] Problems unmarshalling remote command from byte buffer: java.lang.NullPointerException [JBossINF] at org.infinispan.marshall.jboss.ExternalizerTable.readObject(ExternalizerTable.java:222) [JBossINF] at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:351) [JBossINF] at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209) [JBossINF] at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:37) [jboss-marshalling-1.3.14.GA.jar:1.3.14.GA] [JBossINF] at org.infinispan.marshall.jboss.AbstractJBossMarshaller.objectFromObjectStream(AbstractJBossMarshaller.java:154) [JBossINF] at org.infinispan.marshall.VersionAwareMarshaller.objectFromByteBuffer(VersionAwareMarshaller.java:114) [JBossINF] at org.infinispan.marshall.AbstractDelegatingMarshaller.objectFromByteBuffer(AbstractDelegatingMarshaller.java:85) [JBossINF] at org.infinispan.remoting.transport.jgroups.MarshallerAdapter.objectFromBuffer(MarshallerAdapter.java:50) [JBossINF] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.handle(CommandAwareRpcDispatcher.java:200) [JBossINF] at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:456) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:363) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:238) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:543) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.blocks.mux.MuxUpHandler.up(MuxUpHandler.java:130) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.JChannel.up(JChannel.java:716) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1026) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.RSVP.up(RSVP.java:192) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.FRAG2.up(FRAG2.java:181) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.FlowControl.up(FlowControl.java:400) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.FlowControl.up(FlowControl.java:418) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.pbcast.GMS.up(GMS.java:889) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:244) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:383) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:706) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:566) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.BARRIER.up(BARRIER.java:126) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:143) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.FD.up(FD.java:273) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:288) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.MERGE2.up(MERGE2.java:205) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.Discovery.up(Discovery.java:359) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.stack.Protocol.up(Protocol.java:363) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.TP.passMessageUp(TP.java:1180) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1728) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1710) [jgroups-3.0.9.Final.jar:3.0.9.Final] [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] [JBossINF] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] {noformat}
Release Notes Docs Status: Added: Documented as Known Issue Release Notes Text: Added: If you shut down your cluster cleanly, you may still receive error messages such as <code>Problems unmarshalling remote command from byte buffer</code>. This will be fixed with an update to the Infinispan component. Affects: Added: Release Notes
Link: Added: This issue is a dependency of JBPAPP-9290
Link: Removed: This issue is related to JBPAPP-7577
This was resolved in upstream master and 7.1 quite a while ago.
Writer: Added: mistysj
reopening to update release notes (these are still documented as known issues from the previous release)
Writer: Removed: mistysj Added: Darrin
Setting these to "Not Yet Documented" since they required updating from known to resolved issues.
Release Notes Docs Status: Removed: Documented as Known Issue Added: Not Yet Documented
Hi Paul, I hunting for some additional information so I can document this as a resolved issue for EAP6.0.1. Can you provide any additional information about what caused this problem and how it was fixed? Thanks.
Release Notes Docs Status: Removed: Not Yet Documented Added: Needs More Info
Release Notes Text: Removed: If you shut down your cluster cleanly, you may still receive error messages such as <code>Problems unmarshalling remote command from byte buffer</code>. This will be fixed with an update to the Infinispan component. Added: If you shut down your cluster cleanly, you may still receive error messages such as "Problems unmarshalling remote command from byte buffer". This will be fixed with an update to the Infinispan component.
Release Notes Text: Removed: If you shut down your cluster cleanly, you may still receive error messages such as "Problems unmarshalling remote command from byte buffer". This will be fixed with an update to the Infinispan component. Added: If you shut down a cluster node cleanly, you may have received error messages such as "Problems unmarshalling remote command from byte buffer".
Release Notes Text: Removed: If you shut down a cluster node cleanly, you may have received error messages such as "Problems unmarshalling remote command from byte buffer". Added: A clean shutdown of JBoss Enterprise Application Platform 6 cluster node would result in several warning messages being logged. The log messages warned of: "Problems unmarshalling remote command from byte buffer: java.lang.NullPointerException" but there was no other effect apart from the log messages. This was due to the some of the components being shutdown in the wrong order. The clustering components have been updated to correct this. A clean shutdown of a JBoss Enterprise Application Platform 6 cluster node no longer causes these warnings to be issued.
Radoslav, Thanks for the info. Release Notes updated.
Release Notes Docs Status: Removed: Needs More Info Added: Documented as Resolved Issue
I just saw it again in our 6.0.1.ER3 runs, please have a look at the logs here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Failover/job/eap-6x-failover-ejb-ejbservlet-shutdown-repl-async/26/console-perf18/ Reopening.
Release Notes Docs Status: Removed: Documented as Resolved Issue Writer: Removed: Darrin Release Notes Text: Removed: A clean shutdown of JBoss Enterprise Application Platform 6 cluster node would result in several warning messages being logged. The log messages warned of: "Problems unmarshalling remote command from byte buffer: java.lang.NullPointerException" but there was no other effect apart from the log messages. This was due to the some of the components being shutdown in the wrong order. The clustering components have been updated to correct this. A clean shutdown of a JBoss Enterprise Application Platform 6 cluster node no longer causes these warnings to be issued. Docs QE Status: Removed: NEW
Also affects 6.1.0.DR3.
Also affects 6.1.0.ER1. Seen in https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Clustering/view/EAP6-Failover/job/eap-6x-failover-ejb-ejbservlet-undeploy-repl-async/25/console-perf21/
Closing as per last comment. Thanks.