[infinispan-issues] [JBoss JIRA] Updated: (ISPN-673) Stopped cache still causing RPC timeouts on caller.
[
https://jira.jboss.org/browse/ISPN-673?page=com.atlassian.jira.plugin.sys...
]
Paul Ferraro updated ISPN-673:
------------------------------
Attachment: patch.txt
Patch to bypass wait logic if we're not using strict peer to peer.
Stopped cache still causing RPC timeouts on caller.
---------------------------------------------------
Key: ISPN-673
URL: https://jira.jboss.org/browse/ISPN-673
Project: Infinispan
Issue Type: Bug
Components: RPC
Affects Versions: 4.2.0.ALPHA2
Reporter: Paul Ferraro
Assignee: Manik Surtani
Attachments: patch.txt
Revision 2384 of org.infinispan.remoting.InboundInvocationHandlerImpl adds an 30 second
wait loop for stopped caches, causing RPCs to timeout. For a stopped cache,
GlobalComponentRegistry.getNamedComponentRegistry(...) returns null, since its global
component registry entry is removed during ComponentRegistry.stop(), yet isDefined(...)
will still return true. When not using strict peer to peer, this delay is inappropriate
and causes the RPC to timeout.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira