[JBoss JIRA] (ISPN-7726) Task execution failure does not display the cause of failure
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7726?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-7726:
--------------------------------------
Attachment: Screen Shot 2017-04-17 at 9.16.31 AM.png
> Task execution failure does not display the cause of failure
> ------------------------------------------------------------
>
> Key: ISPN-7726
> URL: https://issues.jboss.org/browse/ISPN-7726
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.0.0.Final
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.1.Final
>
> Attachments: Screen Shot 2017-04-17 at 9.15.20 AM.png, Screen Shot 2017-04-17 at 9.16.31 AM.png
>
>
> We do not capture the cause of script/task failure thus preventing the user from taking a proper corrective action. See attachments for details
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7726) Administration console - task execution failure does not display the cause of failure
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7726?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-7726:
--------------------------------------
Summary: Administration console - task execution failure does not display the cause of failure (was: Task execution failure does not display the cause of failure)
> Administration console - task execution failure does not display the cause of failure
> -------------------------------------------------------------------------------------
>
> Key: ISPN-7726
> URL: https://issues.jboss.org/browse/ISPN-7726
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.0.0.Final
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.1.Final
>
> Attachments: Screen Shot 2017-04-17 at 9.15.20 AM.png, Screen Shot 2017-04-17 at 9.16.31 AM.png
>
>
> We do not capture the cause of script/task failure thus preventing the user from taking a proper corrective action. See attachments for details
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7726) Task execution failure does not display the cause of failure
by Vladimir Blagojevic (JIRA)
Vladimir Blagojevic created ISPN-7726:
-----------------------------------------
Summary: Task execution failure does not display the cause of failure
Key: ISPN-7726
URL: https://issues.jboss.org/browse/ISPN-7726
Project: Infinispan
Issue Type: Bug
Components: Console
Affects Versions: 9.0.0.Final
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
Fix For: 9.0.1.Final
We do not capture the cause of script/task failure thus preventing the user from taking a proper corrective action. See attachments for details
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-6766) hot rod client: RemoteCache.removeClient method does not remove the listener from the list after server restart
by Katia Aresti (JIRA)
[ https://issues.jboss.org/browse/ISPN-6766?page=com.atlassian.jira.plugin.... ]
Work on ISPN-6766 started by Katia Aresti.
------------------------------------------
> hot rod client: RemoteCache.removeClient method does not remove the listener from the list after server restart
> ---------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6766
> URL: https://issues.jboss.org/browse/ISPN-6766
> Project: Infinispan
> Issue Type: Bug
> Components: Listeners, Remote Protocols
> Affects Versions: 8.2.1.Final
> Reporter: Eli Z
> Assignee: Katia Aresti
> Priority: Minor
> Fix For: 9.1.0.Final
>
>
> After registering a client listener in the client and then restarting the infinispan server --> The original listener object can not be removed from the client listener list by using the method RemoteCache.removeClient(Object listener) --> after calling this method and then get all listeners, i still see the old listener in the list.
> By doing a little debug, it seems that in class RemoveClientListenerOperation.execute when trying to remove from the server and a failure status is returned (probably due to the fact the the server after the restart does not know this listener id) the listener is not removed from the list eventually. the line this.listenerNotifier.removeClientListener(listenerId); is not executed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7725) NPE at org.infinispan.topology.ClusterTopologyManagerImpl.isRebalancingEnabled
by Roman Karpenko (JIRA)
Roman Karpenko created ISPN-7725:
------------------------------------
Summary: NPE at org.infinispan.topology.ClusterTopologyManagerImpl.isRebalancingEnabled
Key: ISPN-7725
URL: https://issues.jboss.org/browse/ISPN-7725
Project: Infinispan
Issue Type: Bug
Affects Versions: 8.1.7.Final
Reporter: Roman Karpenko
Priority: Critical
11:20:02.943 [cloud:background-1-30] WARN o.i.t.CacheTopologyControlCommand - ISPN000071: Caught exception when handling command CacheTopologyControlCommand{cache=users, type=POLICY_GET_STATUS,0, rebalanceId=0, currentCH=null, pendingCH=null, availabilityMode=null, actualMembers=null, throwable=null, viewId=2}
java.lang.NullPointerException: null
at org.infinispan.topology.ClusterTopologyManagerImpl.isRebalancingEnabled(ClusterTopologyManagerImpl.java:600)
at org.infinispan.topology.CacheTopologyControlCommand.doPerform(CacheTopologyControlCommand.java:190)
at org.infinispan.topology.CacheTopologyControlCommand.perform(CacheTopologyControlCommand.java:146)
at org.infinispan.topology.LocalTopologyManagerImpl.executeOnCoordinator(LocalTopologyManagerImpl.java:602)
at org.infinispan.topology.LocalTopologyManagerImpl.isCacheRebalancingEnabled(LocalTopologyManagerImpl.java:536)
at org.infinispan.cache.impl.CacheImpl.isRebalancingEnabled(CacheImpl.java:985)
at sun.reflect.GeneratedMethodAccessor539.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.infinispan.jmx.ResourceDMBean$InvokableSetterBasedMBeanAttributeInfo.invoke(ResourceDMBean.java:394)
at org.infinispan.jmx.ResourceDMBean.getNamedAttribute(ResourceDMBean.java:298)
at org.infinispan.jmx.ResourceDMBean.getAttributes(ResourceDMBean.java:197)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:709)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:705)
at com.netflix.servo.publish.JmxMetricPoller.batchLoadAttributes(JmxMetricPoller.java:325)
at com.netflix.servo.publish.JmxMetricPoller.safelyLoadAttributes(JmxMetricPoller.java:310)
at com.netflix.servo.publish.JmxMetricPoller.getMetrics(JmxMetricPoller.java:205)
at com.netflix.servo.publish.JmxMetricPoller.poll(JmxMetricPoller.java:288)
at com.netflix.servo.publish.PollRunnable.run(PollRunnable.java:82)
at com.playtech.crossteam.boot.JMXMonitoringHandler.lambda$setupGraphite$5(JMXMonitoringHandler.java:80)
at com.playtech.crossteam.support.RxPlatform.lambda$null$4(RxPlatform.java:119)
at com.playtech.crossteam.support.RxPlatform.lambda$work$2(RxPlatform.java:96)
at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:55)
ExecutorScheduler.java:107)dulers.ExecutorScheduler$ExecutorSchedulerWorker.run(--More--
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7705) Administration console - greyed out cluster action can still be selected
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7705?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-7705.
--------------------------------
Fix Version/s: 9.1.0.Final
9.0.1.Final
Resolution: Done
> Administration console - greyed out cluster action can still be selected
> ------------------------------------------------------------------------
>
> Key: ISPN-7705
> URL: https://issues.jboss.org/browse/ISPN-7705
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Final
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Priority: Minor
> Fix For: 9.1.0.Final, 9.0.1.Final
>
>
> When the cluster is in the running state, start, reload and restart actions are greyed out, but they can still be clicked and the selected action is performed.
> This is not the case for the node operations.
> Also, shouldn't restart action be available when server/node are in running state?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (ISPN-7724) getAllCacheEntries with byte[] throws ClassCastException
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-7724?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-7724:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.1.0.Final
9.0.1.Final
Resolution: Done
> getAllCacheEntries with byte[] throws ClassCastException
> --------------------------------------------------------
>
> Key: ISPN-7724
> URL: https://issues.jboss.org/browse/ISPN-7724
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.0.0.Final
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Fix For: 9.1.0.Final, 9.0.1.Final
>
>
> Testcase:
> {code}
> public void testGetAllCacheEntriesWithBytes() {
> Set<String> keys = new HashSet<>();
> for (int i = 0; i < numEntries; ++i) {
> String key = "key" + i;
> advancedCache(i % numNodes).put(key, new byte[]{(byte) i});
> keys.add(key);
> }
> List<Cache<String, byte[]>> caches = caches();
> for (Cache<String, byte[]> cache : caches) {
> Map<String, CacheEntry<String, byte[]>> map = cache.getAdvancedCache().getAllCacheEntries(keys);
> assertEquals(map.size(), keys.size());
> for (int i = 0; i < numEntries; ++i) {
> CacheEntry<String, byte[]> entry = map.get("key" + i);
> assertEquals(entry.getValue().length, 1);
> assertEquals(entry.getValue()[0], i);
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months