[infinispan-issues] [JBoss JIRA] (ISPN-4445) RHQ or CLI server -- cli.interpreter.ParseException in newly started cache for getting stats
William Burns (JIRA)
issues at jboss.org
Fri Dec 12 11:29:29 EST 2014
[ https://issues.jboss.org/browse/ISPN-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027419#comment-13027419 ]
William Burns commented on ISPN-4445:
-------------------------------------
So I am not quite sure what this issue is getting at. Is it the fact that you can't view information on the cache when it is not running? Or is there something else? I also can't even start the cache if it is marked as LAZY from RHQ as well. It seems we should handle these runtime attributes a bit better.
This following blurb is also on the CacheMetricsHandler#executeRuntimeStep method, but it still seems to negatively impact things.
{code}
/*
* Two constraints need to be dealt with here:
* 1. There may be no started cache instance available to interrogate. Because of lazy deployment,
* a cache instance is only started upon deployment of an application which uses that cache instance.
* 2. The attribute name passed in may not correspond to a defined metric
*
* Read-only attributes have no easy way to throw an exception without negatively impacting other parts
* of the system. Therefore in such cases, as message will be logged and a ModelNode of undefined will be returned.
*/
{code}
> RHQ or CLI server -- cli.interpreter.ParseException in newly started cache for getting stats
> --------------------------------------------------------------------------------------------
>
> Key: ISPN-4445
> URL: https://issues.jboss.org/browse/ISPN-4445
> Project: Infinispan
> Issue Type: Bug
> Components: CLI, JMX, reporting and management
> Affects Versions: 7.0.0.Alpha4
> Reporter: Tomas Sykora
> Assignee: William Burns
>
> We found this issue during RHQ testing.
> When we create a new Cache child resource under cache-manager, it should create a cache, change server configuration file and (after server restart) monitor a new cache without problem.
> However, we spotted and issue in CLI. Even a connecting through jboss-cli.sh is showing the same problem with parsing.
> Relevant server console output:
> 07:44:28,195 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-1) JBAS010281: Started new-local-cache-9990 cache from local container
> 07:44:28,369 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 0.0.0.0:9999
> 07:44:28,371 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 0.0.0.0:4447
> 07:44:28,550 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://0.0.0.0:9990/management
> 07:44:28,551 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
> 07:44:28,551 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss Data Grid 6.3.0 (AS 7.3.3.Final-redhat-3) started in 8928ms - Started 96 of 137 services (41 services are passive or on-demand)
> 07:46:16,328 INFO [org.jboss.as.clustering.infinispan] (management-handler-thread - 3) JBAS010281: Started ___defaultcache cache from local container
> 07:46:26,593 ERROR [stderr] (management-handler-thread - 2) line 1:10 mismatched character 'l' expecting '-'
> 07:46:26,607 ERROR [stderr] (management-handler-thread - 2) line 1:16 mismatched character 'c' expecting '-'
> 07:46:26,608 ERROR [stderr] (management-handler-thread - 2) line 1:22 mismatched character '9' expecting '-'
> 07:46:26,609 ERROR [org.infinispan.cli.interpreter.Interpreter] (management-handler-thread - 2) ISPN019003: Interpreter error: org.infinispan.cli.interpreter.ParseException: line 1:11 mismatched input 'ocal' expecting set null
> at org.infinispan.cli.interpreter.Interpreter.execute(Interpreter.java:144) [infinispan-cli-server-6.1.0.Final-redhat-1.jar:6.1.0.Final-redhat-1]
> at org.infinispan.server.infinispan.SecurityActions$6.run(SecurityActions.java:237) [infinispan-server-infinispan-6.1.0.Final-redhat-1.jar:6.1.0.Final-redhat-1]
> at org.infinispan.server.infinispan.SecurityActions$6.run(SecurityActions.java:234) [infinispan-server-infinispan-6.1.0.Final-redhat-1.jar:6.1.0.Final-redhat-1]
> at org.infinispan.security.Security.doPrivileged(Security.java:89) [infinispan-core-6.1.0.Final-redhat-1.jar:6.1.0.Final-redhat-1]
> at org.infinispan.server.infinispan.SecurityActions.doPrivileged(SecurityActions.java:55) [infinispan-server-infinispan-6.1.0.Final-redhat-1.jar:6.1.0.Final-redhat-1]
> at org.infinispan.server.infinispan.SecurityActions.executeInterpreter(SecurityActions.java:240) [infinispan-server-infinispan-6.1.0.Final-redhat-1.jar:6.1.0.Final-redhat-1]
> at org.jboss.as.clustering.infinispan.subsystem.CliInterpreterHandler.execute(CliInterpreterHandler.java:49) [infinispan-server-infinispan-6.1.0.Final-redhat-1.jar:6.1.0.Final-redhat-1]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:601) [jboss-as-controller-7.3.3.Final-redhat-3.jar:7.3.3.Final-redhat-3]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:479) [jboss-as-controller-7.3.3.Final-redhat-3.jar:7.3.3.Final-redhat-3]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:283) [jboss-as-controller-7.3.3.Final-redhat-3.jar:7.3.3.Final-redhat-3]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:278) [jboss-as-controller-7.3.3.Final-redhat-3.jar:7.3.3.Final-redhat-3]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:231) [jboss-as-controller-7.3.3.Final-redhat-3.jar:7.3.3.Final-redhat-3]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:137) [jboss-as-controller-7.3.3.Final-redhat-3.jar:7.3.3.Final-redhat-3]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:173) [jboss-as-controller-7.3.3.Final-redhat-3.jar:7.3.3.Final-redhat-3]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:105) [jboss-as-controller-7.3.3.Final-redhat-3.jar:7.3.3.Final-redhat-3]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:125) [jboss-as-controller-7.3.3.Final-redhat-3.jar:7.3.3.Final-redhat-3]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:121) [jboss-as-controller-7.3.3.Final-redhat-3.jar:7.3.3.Final-redhat-3]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_09-icedtea]
> at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_09-icedtea]
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [jboss-as-controller-7.3.3.Final-redhat-3.jar:7.3.3.Final-redhat-3]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:121) [jboss-as-controller-7.3.3.Final-redhat-3.jar:7.3.3.Final-redhat-3]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09-icedtea]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09-icedtea]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Final-redhat-1]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the infinispan-issues
mailing list