[jbosscache-issues] [JBoss JIRA] Updated: (JBCACHE-1579) NPE on some operations after calling removeNode on an unexistent FQN
Galder Zamarreno (JIRA)
jira-events at lists.jboss.org
Thu Apr 22 10:55:10 EDT 2010
[ https://jira.jboss.org/jira/browse/JBCACHE-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Galder Zamarreno updated JBCACHE-1579:
--------------------------------------
Fix Version/s: 3.2.4.GA
Affects Version/s: 3.2.3.GA
> NPE on some operations after calling removeNode on an unexistent FQN
> --------------------------------------------------------------------
>
> Key: JBCACHE-1579
> URL: https://jira.jboss.org/jira/browse/JBCACHE-1579
> Project: JBoss Cache
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Locking
> Affects Versions: 3.1.0.GA, 3.2.0.GA, 3.2.1.GA, 3.2.2.GA, 3.2.3.GA
> Reporter: Galder Zamarreno
> Assignee: Galder Zamarreno
> Fix For: 3.2.4.GA
>
>
> NullPointerException can be thrown when you call removeNode on a non-existing FQN and then call clearData on that FQN, clearData throws an NPE, i.e.
> java.lang.NullPointerException
> at org.jboss.cache.invocation.NodeInvocationDelegate.clearDataDirect(NodeInvocationDelegate.java:243)
> at org.jboss.cache.commands.write.ClearDataCommand.perform(ClearDataCommand.java:79)
> at org.jboss.cache.interceptors.CallInterceptor.invokeCommand(CallInterceptor.java:108)
> at org.jboss.cache.interceptors.CallInterceptor.handleAlterCacheMethod(CallInterceptor.java:173)
> at org.jboss.cache.interceptors.CallInterceptor.visitClearDataCommand(CallInterceptor.java:149)
> at org.jboss.cache.commands.write.ClearDataCommand.acceptVisitor(ClearDataCommand.java:86)
> at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
> at org.jboss.cache.interceptors.EvictionInterceptor.visitClearDataCommand(EvictionInterceptor.java:235)
> at org.jboss.cache.commands.write.ClearDataCommand.acceptVisitor(ClearDataCommand.java:86)
> at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116)
> at org.jboss.cache.interceptors.MVCCLockingInterceptor.handleClearDataCommand(MVCCLockingInterceptor.java:124)
> at org.jboss.cache.interceptors.base.PrePostProcessingCommandInterceptor.visitClearDataCommand(PrePostProcessingCommandInterceptor.java:167)
> at org.jboss.cache.commands.write.ClearDataCommand.acceptVisitor(ClearDataCommand.java:86)
> The same thing would occur if you called remove(fqn, key) after calling removeNode(fqn) on an unexistent FQN.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosscache-issues
mailing list