[JBoss JIRA] (ISPN-2739) Incorrect help for "encoding" command
by Martin Gencur (JIRA)
Martin Gencur created ISPN-2739:
-----------------------------------
Summary: Incorrect help for "encoding" command
Key: ISPN-2739
URL: https://issues.jboss.org/browse/ISPN-2739
Project: Infinispan
Issue Type: Feature Request
Components: CLI
Affects Versions: 5.2.0.CR2
Reporter: Martin Gencur
Assignee: Tristan Tarrant
Priority: Minor
Fix For: 5.2.0.Final
The help for "encoding" command shows the following:
SYNOPSIS
encoding [cachename]
DESCRIPTION
Shows the currently selected cache or selects a cache to be used as default for CLI operations
ARGUMENTS
cachename
(optional) the name of the cache to set as default for the following operations
--
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
11 years, 11 months
[JBoss JIRA] (ISPN-2739) Incorrect help for "encoding" command
by Martin Gencur (JIRA)
[ https://issues.jboss.org/browse/ISPN-2739?page=com.atlassian.jira.plugin.... ]
Martin Gencur updated ISPN-2739:
--------------------------------
Issue Type: Bug (was: Feature Request)
> Incorrect help for "encoding" command
> --------------------------------------
>
> Key: ISPN-2739
> URL: https://issues.jboss.org/browse/ISPN-2739
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Affects Versions: 5.2.0.CR2
> Reporter: Martin Gencur
> Assignee: Tristan Tarrant
> Priority: Minor
> Fix For: 5.2.0.Final
>
>
> The help for "encoding" command shows the following:
> SYNOPSIS
> encoding [cachename]
> DESCRIPTION
> Shows the currently selected cache or selects a cache to be used as default for CLI operations
> ARGUMENTS
> cachename
> (optional) the name of the cache to set as default for the following operations
--
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
11 years, 11 months
[JBoss JIRA] (ISPN-2714) org.infinispan.distexec.mapreduce.TopologyAwareTwoNodesMapReduceTest.testInvokeMapperCancellation test fails randomly
by Anna Manukyan (JIRA)
[ https://issues.jboss.org/browse/ISPN-2714?page=com.atlassian.jira.plugin.... ]
Anna Manukyan updated ISPN-2714:
--------------------------------
Assignee: Anna Manukyan (was: Vladimir Blagojevic)
> org.infinispan.distexec.mapreduce.TopologyAwareTwoNodesMapReduceTest.testInvokeMapperCancellation test fails randomly
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-2714
> URL: https://issues.jboss.org/browse/ISPN-2714
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Execution and Map/Reduce
> Affects Versions: 5.2.0.CR1
> Reporter: Anna Manukyan
> Assignee: Anna Manukyan
> Labels: testsuite_stability
>
> The test org.infinispan.distexec.mapreduce.TopologyAwareTwoNodesMapReduceTest.testInvokeMapperCancellation fails randomly on all environments.
> The error log is:
> {code}
> Error Message
> Expected exception java.util.concurrent.CancellationException but got java.lang.AssertionError: Mapper not cancelled, root cause org.jgroups.TimeoutException: timeout sending message to TopologyAwareTwoNodesMapReduceTest-NodeB-22523(test2)
> Stacktrace
> org.testng.TestException:
> Expected exception java.util.concurrent.CancellationException but got java.lang.AssertionError: Mapper not cancelled, root cause org.jgroups.TimeoutException: timeout sending message to TopologyAwareTwoNodesMapReduceTest-NodeB-22523(test2)
> at org.testng.internal.Invoker.handleInvocationResults(Invoker.java:1503)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:764)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
> at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
> at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> 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.AssertionError: Mapper not cancelled, root cause org.jgroups.TimeoutException: timeout sending message to TopologyAwareTwoNodesMapReduceTest-NodeB-22523(test2)
> at org.infinispan.distexec.mapreduce.SimpleTwoNodesMapReduceTest.testInvokeMapperCancellation(SimpleTwoNodesMapReduceTest.java:106)
> 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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:715)
> ... 15 more
> {code}
--
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
11 years, 11 months
[JBoss JIRA] (ISPN-2705) site command does not work correctly
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-2705?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-2705:
-----------------------------------------------
Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 894321|https://bugzilla.redhat.com/show_bug.cgi?id=894321] from ON_QA to VERIFIED
> site command does not work correctly
> ------------------------------------
>
> Key: ISPN-2705
> URL: https://issues.jboss.org/browse/ISPN-2705
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Affects Versions: 5.2.0.CR1
> Reporter: Martin Gencur
> Assignee: Tristan Tarrant
> Fix For: 5.2.0.CR2
>
>
> * Issuing "site --status" command results in NPE:
> {code}
> 13:11:10,278 ERROR [org.infinispan.cli.interpreter.Interpreter] (pool-1-thread-1) ISPN019003: Interpreter error: java.lang.NullPointerException
> at org.infinispan.cli.interpreter.statement.SiteStatement.execute(SiteStatement.java:56) [infinispan-cli-server-5.2.0.CR1-redhat-1.jar:5.2.0.CR1-redhat-1]
> at org.infinispan.cli.interpreter.Interpreter.execute(Interpreter.java:161) [infinispan-cli-server-5.2.0.CR1-redhat-1.jar:5.2.0.CR1-redhat-1]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_09]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_09]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_09]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_09]
> at org.infinispan.jmx.ResourceDMBean.invoke(ResourceDMBean.java:270) [infinispan-core-5.2.0.CR1-redhat-1.jar:5.2.0.CR1-redhat-1]
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) [rt.jar:1.7.0_09]
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:791) [rt.jar:1.7.0_09]
> at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:498) [jboss-as-jmx-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:246) [jboss-as-jmx-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at org.jboss.remotingjmx.protocol.v1.ServerProxy$InvokeHandler.handle(ServerProxy.java:1034)
> at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:215)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
> {code}
> * "site --offline" has the same results
> * "site --status default.LON" results in "Incorrect site name: null"
> I'm pretty sure the active site is named LON as I was using an example configuration file shipped with JDG: standalone-xsite.xml. Also, the log shows Received new cluster view: [mgencur/LON|0] [mgencur/LON]
--
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
11 years, 11 months
[JBoss JIRA] (ISPN-2705) site command does not work correctly
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-2705?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-2705:
-----------------------------------------------
Martin Gencur <mgencur(a)redhat.com> made a comment on [bug 894321|https://bugzilla.redhat.com/show_bug.cgi?id=894321]
This command is now working correctly. Marking as verified.
> site command does not work correctly
> ------------------------------------
>
> Key: ISPN-2705
> URL: https://issues.jboss.org/browse/ISPN-2705
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Affects Versions: 5.2.0.CR1
> Reporter: Martin Gencur
> Assignee: Tristan Tarrant
> Fix For: 5.2.0.CR2
>
>
> * Issuing "site --status" command results in NPE:
> {code}
> 13:11:10,278 ERROR [org.infinispan.cli.interpreter.Interpreter] (pool-1-thread-1) ISPN019003: Interpreter error: java.lang.NullPointerException
> at org.infinispan.cli.interpreter.statement.SiteStatement.execute(SiteStatement.java:56) [infinispan-cli-server-5.2.0.CR1-redhat-1.jar:5.2.0.CR1-redhat-1]
> at org.infinispan.cli.interpreter.Interpreter.execute(Interpreter.java:161) [infinispan-cli-server-5.2.0.CR1-redhat-1.jar:5.2.0.CR1-redhat-1]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_09]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_09]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_09]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_09]
> at org.infinispan.jmx.ResourceDMBean.invoke(ResourceDMBean.java:270) [infinispan-core-5.2.0.CR1-redhat-1.jar:5.2.0.CR1-redhat-1]
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) [rt.jar:1.7.0_09]
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:791) [rt.jar:1.7.0_09]
> at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:498) [jboss-as-jmx-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:246) [jboss-as-jmx-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at org.jboss.remotingjmx.protocol.v1.ServerProxy$InvokeHandler.handle(ServerProxy.java:1034)
> at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:215)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
> {code}
> * "site --offline" has the same results
> * "site --status default.LON" results in "Incorrect site name: null"
> I'm pretty sure the active site is named LON as I was using an example configuration file shipped with JDG: standalone-xsite.xml. Also, the log shows Received new cluster view: [mgencur/LON|0] [mgencur/LON]
--
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
11 years, 11 months