]
Mark De Leon updated ISPN-3536:
-------------------------------
Attachment: pearson-clustered-xsite-bos.xml
Exception when handling command SingleRpcCommand
------------------------------------------------
Key: ISPN-3536
URL:
https://issues.jboss.org/browse/ISPN-3536
Project: Infinispan
Issue Type: Bug
Components: Cross-Site Replication
Affects Versions: 5.3.0.Final, 6.0.0.Alpha4
Environment: Linux ip-10-252-170-214 3.4.43-43.43.amzn1.x86_64 #1 SMP Mon May 6
18:04:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.11.90) (amazon-62.1.11.11.90.55.amzn1-x86_64)
OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
Reporter: Mark De Leon
Assignee: Mircea Markus
Attachments: pearson-clustered-xsite-bos.xml, pearson-clustered-xsite-va.xml
The following can be referenced from forum post by Chris Riley ISPN000071
Trying to perform an insert of a cache value into a distributed cache that is replicated
via Cross Site Replication in JBoss 6.0.0.Alpha4. The cross site replication has two nodes
in the global cluster.
When a value is put on the local site we get the following error on the remote site. We
just upgraded to 6.0.0.Alpha4 because of JIRA ISSUE ISPN-3346, which we reproduced in
5.3.0.Final. I have attached our jboss configuration file for review.
17:22:41,798 WARN [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher]
(Incoming-2,shared=tcp) ISPN000071: Caught exception when handling command
SingleRpcCommand{cacheName='importantCache', command=PutKeyValueCommand{key=1,
value=[B@363f983f, flags=null, putIfAbsent=false,
metadata=MimeMetadata(contentType=text/plain), successful=true,
ignorePreviousValue=false}}: java.lang.NullPointerException
at
org.infinispan.xsite.BackupReceiverRepositoryImpl.isBackupForRemoteCache(BackupReceiverRepositoryImpl.java:112)
[infinispan-core-6.0.0.Alpha4.jar:6.0.0.Alpha4]
at
org.infinispan.xsite.BackupReceiverRepositoryImpl.getBackupCacheManager(BackupReceiverRepositoryImpl.java:95)
[infinispan-core-6.0.0.Alpha4.jar:6.0.0.Alpha4]
at
org.infinispan.xsite.BackupReceiverRepositoryImpl.handleRemoteCommand(BackupReceiverRepositoryImpl.java:67)
[infinispan-core-6.0.0.Alpha4.jar:6.0.0.Alpha4]
at
org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.executeCommandFromRemoteSite(CommandAwareRpcDispatcher.java:234)
[infinispan-core-6.0.0.Alpha4.jar:6.0.0.Alpha4]
at
org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.handle(CommandAwareRpcDispatcher.java:209)
[infinispan-core-6.0.0.Alpha4.jar:6.0.0.Alpha4]
at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:460)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at
org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:377)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:247)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at
org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:665)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.blocks.mux.MuxUpHandler.up(MuxUpHandler.java:130)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.JChannel.up(JChannel.java:719)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1002)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.relay.RELAY2.deliver(RELAY2.java:612)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.relay.RELAY2.route(RELAY2.java:508)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.relay.RELAY2.handleMessage(RELAY2.java:483)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.relay.RELAY2.handleRelayMessage(RELAY2.java:461)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.relay.Relayer$Bridge.receive(Relayer.java:263)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.JChannel.up(JChannel.java:749)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1006)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.stack.Protocol.up(Protocol.java:406)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.FRAG2.up(FRAG2.java:195)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.FlowControl.up(FlowControl.java:439)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.FlowControl.up(FlowControl.java:439)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.stack.Protocol.up(Protocol.java:406)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:304)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.UNICAST.removeAndDeliver(UNICAST.java:748)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.UNICAST.handleBatchReceived(UNICAST.java:704)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.UNICAST.up(UNICAST.java:454)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.stack.Protocol.up(Protocol.java:406)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.stack.Protocol.up(Protocol.java:406)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.FD.up(FD.java:274)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.stack.Protocol.up(Protocol.java:406)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.MERGE2.up(MERGE2.java:223)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.stack.Protocol.up(Protocol.java:406)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.stack.Protocol.up(Protocol.java:406)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.TP.passBatchUp(TP.java:1409)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at org.jgroups.protocols.TP$BatchHandler.run(TP.java:1564)
[jgroups-3.4.0.Alpha1.jar:3.4.0.Alpha1]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[rt.jar:1.6.0_24]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: