7:07 p.m.
NPE during state transfer after restarting cache
------------------------------------------------
Key: ISPN-696
URL: https://jira.jboss.org/browse/ISPN-696
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 4.2.0.ALPHA2
Reporter: Paul Ferraro
Assignee: Manik Surtani
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry during in the constructor and unregistered on stop(). Because of
this unbalanced registration, when the stopped component registry is restarted, it never
get re-registered with the GlobalComponentRegistry, hence the NPE during state transfer
the second time around.
--
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
7:11 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-696) NPE during state transfer after restarting cache
[
https://jira.jboss.org/browse/ISPN-696?page=com.atlassian.jira.plugin.sys...
]
Paul Ferraro updated ISPN-696:
------------------------------
Workaround Description: Regression was introduced in revision 2384. Workaround
involves rolling back ComponentRegistry.java to revision 2273.
Workaround: [Workaround Exists]
NPE during state transfer after restarting cache
------------------------------------------------
Key: ISPN-696
URL: https://jira.jboss.org/browse/ISPN-696
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 4.2.0.ALPHA2
Reporter: Paul Ferraro
Assignee: Manik Surtani
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry during in the constructor and unregistered on stop(). Because of
this unbalanced registration, when the stopped component registry is restarted, it never
get re-registered with the GlobalComponentRegistry, hence the NPE during state transfer
the second time around.
--
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
7:11 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-696) NPE during state transfer after restarting cache
[
https://jira.jboss.org/browse/ISPN-696?page=com.atlassian.jira.plugin.sys...
]
Paul Ferraro updated ISPN-696:
------------------------------
Workaround Description: (was: Regression was introduced in revision 2384.
Workaround involves rolling back ComponentRegistry.java to revision 2273.)
Workaround: (was: [Workaround Exists])
Description:
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry during in the constructor and unregistered on stop(). Because of
this unbalanced registration, when the stopped component registry is restarted, it never
get re-registered with the GlobalComponentRegistry, hence the NPE during state transfer
the second time around.
This specific regression was introduced in revision 2384. Rolling back
ComponentRegistry.java to revision 2273 resolves the issue.
was:
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry during in the constructor and unregistered on stop(). Because of
this unbalanced registration, when the stopped component registry is restarted, it never
get re-registered with the GlobalComponentRegistry, hence the NPE during state transfer
the second time around.
NPE during state transfer after restarting cache
------------------------------------------------
Key: ISPN-696
URL: https://jira.jboss.org/browse/ISPN-696
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 4.2.0.ALPHA2
Reporter: Paul Ferraro
Assignee: Manik Surtani
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry during in the constructor and unregistered on stop(). Because of
this unbalanced registration, when the stopped component registry is restarted, it never
get re-registered with the GlobalComponentRegistry, hence the NPE during state transfer
the second time around.
This specific regression was introduced in revision 2384. Rolling back
ComponentRegistry.java to revision 2273 resolves the issue.
--
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
7:13 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-696) NPE during state transfer after restarting cache
[
https://jira.jboss.org/browse/ISPN-696?page=com.atlassian.jira.plugin.sys...
]
Paul Ferraro updated ISPN-696:
------------------------------
Description:
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry in the constructor and unregistered in stop(). Because of the
unbalanced logic, when the stopped component registry is restarted, it never gets
re-registered with the GlobalComponentRegistry, hence the NPE during state transfer the
second time around.
This specific regression was introduced in revision 2384. Rolling back
ComponentRegistry.java to revision 2273 resolves the issue.
was:
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry during in the constructor and unregistered on stop(). Because of
this unbalanced registration, when the stopped component registry is restarted, it never
get re-registered with the GlobalComponentRegistry, hence the NPE during state transfer
the second time around.
This specific regression was introduced in revision 2384. Rolling back
ComponentRegistry.java to revision 2273 resolves the issue.
NPE during state transfer after restarting cache
------------------------------------------------
Key: ISPN-696
URL: https://jira.jboss.org/browse/ISPN-696
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 4.2.0.ALPHA2
Reporter: Paul Ferraro
Assignee: Manik Surtani
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry in the constructor and unregistered in stop(). Because of the
unbalanced logic, when the stopped component registry is restarted, it never gets
re-registered with the GlobalComponentRegistry, hence the NPE during state transfer the
second time around.
This specific regression was introduced in revision 2384. Rolling back
ComponentRegistry.java to revision 2273 resolves the issue.
--
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
9:39 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-696) NPE during state transfer after restarting cache
[
https://jira.jboss.org/browse/ISPN-696?page=com.atlassian.jira.plugin.sys...
]
Galder Zamarreño commented on ISPN-696:
---------------------------------------
http://fisheye.jboss.org/changelog/Infinispan/?cs=2384
NPE during state transfer after restarting cache
------------------------------------------------
Key: ISPN-696
URL: https://jira.jboss.org/browse/ISPN-696
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 4.2.0.ALPHA2
Reporter: Paul Ferraro
Assignee: Manik Surtani
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry in the constructor and unregistered in stop(). Because of the
unbalanced logic, when the stopped component registry is restarted, it never gets
re-registered with the GlobalComponentRegistry, hence the NPE during state transfer the
second time around.
This specific regression was introduced in revision 2384. Rolling back
ComponentRegistry.java to revision 2273 resolves the issue.
--
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
9:39 a.m.
New subject: [JBoss JIRA] Assigned: (ISPN-696) NPE during state transfer after restarting cache
[
https://jira.jboss.org/browse/ISPN-696?page=com.atlassian.jira.plugin.sys...
]
Galder Zamarreño reassigned ISPN-696:
-------------------------------------
Assignee: Galder Zamarreño (was: Manik Surtani)
NPE during state transfer after restarting cache
------------------------------------------------
Key: ISPN-696
URL: https://jira.jboss.org/browse/ISPN-696
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 4.2.0.ALPHA2
Reporter: Paul Ferraro
Assignee: Galder Zamarreño
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry in the constructor and unregistered in stop(). Because of the
unbalanced logic, when the stopped component registry is restarted, it never gets
re-registered with the GlobalComponentRegistry, hence the NPE during state transfer the
second time around.
This specific regression was introduced in revision 2384. Rolling back
ComponentRegistry.java to revision 2273 resolves the issue.
--
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
10:05 a.m.
New subject: [JBoss JIRA] Work started: (ISPN-696) NPE during state transfer after restarting cache
[
https://jira.jboss.org/browse/ISPN-696?page=com.atlassian.jira.plugin.sys...
]
Work on ISPN-696 started by Galder Zamarreño.
NPE during state transfer after restarting cache
------------------------------------------------
Key: ISPN-696
URL: https://jira.jboss.org/browse/ISPN-696
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 4.2.0.ALPHA2
Reporter: Paul Ferraro
Assignee: Galder Zamarreño
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry in the constructor and unregistered in stop(). Because of the
unbalanced logic, when the stopped component registry is restarted, it never gets
re-registered with the GlobalComponentRegistry, hence the NPE during state transfer the
second time around.
This specific regression was introduced in revision 2384. Rolling back
ComponentRegistry.java to revision 2273 resolves the issue.
--
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
10:05 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-696) NPE during state transfer after restarting cache
[
https://jira.jboss.org/browse/ISPN-696?page=com.atlassian.jira.plugin.sys...
]
Galder Zamarreño commented on ISPN-696:
---------------------------------------
For reference:
2010-10-11 17:02:47,236 ERROR [JGroupsTransport]
(Incoming-2,Infinispan-Cluster,NodeB-26331) Caught while requesting or applying state
java.lang.NullPointerException
at
org.infinispan.remoting.InboundInvocationHandlerImpl.applyState(InboundInvocationHandlerImpl.java:102)
at
org.infinispan.remoting.transport.jgroups.JGroupsTransport.setState(JGroupsTransport.java:592)
at
org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUpEvent(MessageDispatcher.java:712)
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:772)
at org.jgroups.JChannel.up(JChannel.java:1410)
at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:887)
at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:483)
at
org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.connectToStateProvider(STREAMING_STATE_TRANSFER.java:525)
at
org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.handleStateRsp(STREAMING_STATE_TRANSFER.java:464)
at
org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.up(STREAMING_STATE_TRANSFER.java:225)
at org.jgroups.protocols.FRAG2.up(FRAG2.java:188)
at org.jgroups.protocols.FC.up(FC.java:474)
at org.jgroups.protocols.pbcast.GMS.up(GMS.java:888)
at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234)
at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:614)
at org.jgroups.protocols.UNICAST.up(UNICAST.java:294)
at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:707)
at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:132)
at org.jgroups.protocols.FD.up(FD.java:266)
at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:270)
at org.jgroups.protocols.MERGE2.up(MERGE2.java:210)
at org.jgroups.protocols.Discovery.up(Discovery.java:281)
at org.jgroups.protocols.TP.passMessageUp(TP.java:1009)
at org.jgroups.protocols.TP.access$100(TP.java:56)
at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1549)
at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1531)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:637)
NPE during state transfer after restarting cache
------------------------------------------------
Key: ISPN-696
URL: https://jira.jboss.org/browse/ISPN-696
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 4.2.0.ALPHA2
Reporter: Paul Ferraro
Assignee: Galder Zamarreño
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry in the constructor and unregistered in stop(). Because of the
unbalanced logic, when the stopped component registry is restarted, it never gets
re-registered with the GlobalComponentRegistry, hence the NPE during state transfer the
second time around.
This specific regression was introduced in revision 2384. Rolling back
ComponentRegistry.java to revision 2273 resolves the issue.
--
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
11:07 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-696) NPE during state transfer after restarting cache
[
https://jira.jboss.org/browse/ISPN-696?page=com.atlassian.jira.plugin.sys...
]
Galder Zamarreño commented on ISPN-696:
---------------------------------------
I've gone and look at the commits and hudson.
The change came in at:
http://hudson.infinispan.org/hudson/job/Infinispan-4.2.x-JDK6-tcp/32/#sho...
That change seems to have fixed three tests from previous run:
http://hudson.infinispan.org/hudson/job/Infinispan-4.2.x-JDK6-tcp/org.inf...
as opposed to
http://hudson.infinispan.org/hudson/job/Infinispan-4.2.x-JDK6-tcp/org.inf...
Funnily enough, I've run these state transfer tests after moving register code to
start() and it looks fine.
I'm gonna run the whole testsuite again locally and see what it comes back with. If it
looks good, I'll put it back and Manik can double check it when he gets back.
NPE during state transfer after restarting cache
------------------------------------------------
Key: ISPN-696
URL: https://jira.jboss.org/browse/ISPN-696
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 4.2.0.ALPHA2
Reporter: Paul Ferraro
Assignee: Galder Zamarreño
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry in the constructor and unregistered in stop(). Because of the
unbalanced logic, when the stopped component registry is restarted, it never gets
re-registered with the GlobalComponentRegistry, hence the NPE during state transfer the
second time around.
This specific regression was introduced in revision 2384. Rolling back
ComponentRegistry.java to revision 2273 resolves the issue.
--
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
12:57 p.m.
New subject: [JBoss JIRA] Resolved: (ISPN-696) NPE during state transfer after restarting cache
[
https://jira.jboss.org/browse/ISPN-696?page=com.atlassian.jira.plugin.sys...
]
Galder Zamarreño resolved ISPN-696.
-----------------------------------
Fix Version/s: 4.2.0.BETA1
Resolution: Done
NPE during state transfer after restarting cache
------------------------------------------------
Key: ISPN-696
URL: https://jira.jboss.org/browse/ISPN-696
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 4.2.0.ALPHA2
Reporter: Paul Ferraro
Assignee: Galder Zamarreño
Fix For: 4.2.0.BETA1
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry in the constructor and unregistered in stop(). Because of the
unbalanced logic, when the stopped component registry is restarted, it never gets
re-registered with the GlobalComponentRegistry, hence the NPE during state transfer the
second time around.
This specific regression was introduced in revision 2384. Rolling back
ComponentRegistry.java to revision 2273 resolves the issue.
--
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
12:59 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-696) NPE during state transfer after restarting cache
[
https://jira.jboss.org/browse/ISPN-696?page=com.atlassian.jira.plugin.sys...
]
Galder Zamarreño commented on ISPN-696:
---------------------------------------
I've reverted register component registry call to start(). Testsuite looks fine but
I'll keep an eye just in case.
NPE during state transfer after restarting cache
------------------------------------------------
Key: ISPN-696
URL: https://jira.jboss.org/browse/ISPN-696
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 4.2.0.ALPHA2
Reporter: Paul Ferraro
Assignee: Galder Zamarreño
Fix For: 4.2.0.BETA1
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry in the constructor and unregistered in stop(). Because of the
unbalanced logic, when the stopped component registry is restarted, it never gets
re-registered with the GlobalComponentRegistry, hence the NPE during state transfer the
second time around.
This specific regression was introduced in revision 2384. Rolling back
ComponentRegistry.java to revision 2273 resolves the issue.
--
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
7:07 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-696) NPE during state transfer after restarting cache
[
https://jira.jboss.org/browse/ISPN-696?page=com.atlassian.jira.plugin.sys...
]
Mircea Markus updated ISPN-696:
-------------------------------
Fix Version/s: 4.2.0.ALPHA3
(was: 4.2.0.BETA1)
NPE during state transfer after restarting cache
------------------------------------------------
Key: ISPN-696
URL: https://jira.jboss.org/browse/ISPN-696
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 4.2.0.ALPHA2
Reporter: Paul Ferraro
Assignee: Galder Zamarreño
Fix For: 4.2.0.ALPHA3
When a named cache is restarted, and fetchInMemoryState = true, the state transfer
initiated in StateTransferManager.start() causes a NPE, because the cache's
ComponentRegistry does not get reregistered with the GlobalComponentRegistry.
The NPE comes from InboundInvocationHandlerImpl:
public void applyState(String cacheName, InputStream i) throws StateTransferException
{
getStateTransferManager(cacheName).applyState(i);
}
private StateTransferManager getStateTransferManager(String cacheName) throws
StateTransferException {
ComponentRegistry cr = gcr.getNamedComponentRegistry(cacheName);
if (cr == null) {
return null;
}
return cr.getComponent(StateTransferManager.class);
}
A quick glance at ComponentRegistry indicates that the registry is registered with the
GlobalComponentRegistry in the constructor and unregistered in stop(). Because of the
unbalanced logic, when the stopped component registry is restarted, it never gets
re-registered with the GlobalComponentRegistry, hence the NPE during state transfer the
second time around.
This specific regression was introduced in revision 2384. Rolling back
ComponentRegistry.java to revision 2273 resolves the issue.
--
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
5469
days inactive
5475
days old
infinispan-issues@lists.jboss.org
11 comments
3 participants
participants (3)
-
Galder Zamarreño (JIRA) -
Mircea Markus (JIRA)
-
Paul Ferraro (JIRA)