[infinispan-issues] [JBoss JIRA] (ISPN-3552) HotRod Rolling Upgrades NPE when disabling cache store on target node

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850953#comment-12850953 ] 

RH Bugzilla Integration commented on ISPN-3552:
-----------------------------------------------

Tomas Sykora <tsykora at redhat.com> made a comment on [bug 1011499|https://bugzilla.redhat.com/show_bug.cgi?id=1011499]

This issue depends on: https://bugzilla.redhat.com/show_bug.cgi?id=1026862

Formerly, I thought 1026862 exception is related to disabling remote cache store. This is not true and this issue blocks even the first of rolling upgrades operations -- recordKnownGlobalKeyset.

Once https://bugzilla.redhat.com/show_bug.cgi?id=1026862 is fixed and verified, this issue can be consequently verified as well.

We should remove this (1011499) bugzilla from beta release notes as it is superseded by 1026862 for now.
                
> HotRod Rolling Upgrades NPE when disabling cache store on target node
> ---------------------------------------------------------------------
>
>                 Key: ISPN-3552
>                 URL: https://issues.jboss.org/browse/ISPN-3552
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 6.0.0.Beta1
>            Reporter: Tomas Sykora
>            Assignee: Pedro Ruivo
>            Priority: Critical
>              Labels: 620
>             Fix For: 6.0.0.CR2
>
>         Attachments: standalone-source-node-rollups52-dist.xml, standalone-target-node-rollups-dist.xml
>
>
> After Tristan's fix for https://issues.jboss.org/browse/ISPN-3183 we can move successfully through recordKnownGlobalKeyset and synchronizeData operations.
> However, when we want to issue disconnectSource operation on target node, it is failing with given error:
> javax.management.MBeanException
>         at org.infinispan.jmx.ResourceDMBean.invoke(ResourceDMBean.java:273)
>         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
>         at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:791)
>         at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:527)
>         at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:263)
>         at org.jboss.remotingjmx.protocol.v1.ServerProxy$InvokeHandler.handle(ServerProxy.java:1058)
>         at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:225)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:722)
> Caused by: java.lang.reflect.InvocationTargetException
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:601)
>         at org.infinispan.jmx.ResourceDMBean.invoke(ResourceDMBean.java:271)
>         ... 9 more
> Caused by: java.lang.NullPointerException
>         at org.infinispan.persistence.manager.PersistenceManagerImpl.disableStore(PersistenceManagerImpl.java:253)
>         at org.infinispan.persistence.remote.upgrade.HotRodTargetMigrator.disconnectSource(HotRodTargetMigrator.java:101)
>         at org.infinispan.upgrade.RollingUpgradeManager.disconnectSource(RollingUpgradeManager.java:71)
>         ... 14 more
> Short input from Tristan: "problem is that after removing the store, it determines there are no more stores left so it tries to remove the loader/writer interceptors which for some reason are missing"
>  

--
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: http://www.atlassian.com/software/jira