[JBoss JIRA] (ISPN-10129) CLI NullPointerException after running CLI "create" command
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10129?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10129:
-----------------------------------
Security: (was: Red Hat Internal)
> CLI NullPointerException after running CLI "create" command
> -----------------------------------------------------------
>
> Key: ISPN-10129
> URL: https://issues.jboss.org/browse/ISPN-10129
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Affects Versions: 9.4.12.Final, 10.0.0.Beta3
> Environment: JDG-7.3
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Beta4, 9.4.13.Final
>
>
> Getting Null Pointer Exception after running "create" command from CLI :
> Below is the exception snippet :
> ~~~
> 16:59:43,111 ERROR [org.infinispan.cli.interpreter.Interpreter] (management-handler-thread - 1) ISPN019003: Interpreter error: java.lang.NullPointerException
> at org.infinispan.cli.interpreter.session.SessionImpl.createCache(SessionImpl.java:109)
> at org.infinispan.cli.interpreter.statement.CreateStatement.execute(CreateStatement.java:25)
> at org.infinispan.cli.interpreter.Interpreter.execute(Interpreter.java:140)
> at org.infinispan.server.infinispan.SecurityActions.lambda$executeInterpreter$7(SecurityActions.java:268)
> at org.infinispan.security.Security.doPrivileged(Security.java:57)
> at org.infinispan.server.infinispan.SecurityActions.doPrivileged(SecurityActions.java:77)
> at org.infinispan.server.infinispan.SecurityActions.executeInterpreter(SecurityActions.java:269)
> at org.jboss.as.clustering.infinispan.subsystem.CliInterpreterHandler.execute(CliInterpreterHandler.java:71)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1411)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423)
> at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:265)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:231)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:246)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> ~~~
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[JBoss JIRA] (ISPN-10129) CLI NullPointerException after running CLI "create" command
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10129?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10129:
-----------------------------------
Status: Open (was: New)
> CLI NullPointerException after running CLI "create" command
> -----------------------------------------------------------
>
> Key: ISPN-10129
> URL: https://issues.jboss.org/browse/ISPN-10129
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Affects Versions: 9.4.12.Final, 10.0.0.Beta3
> Environment: JDG-7.3
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Beta4, 9.4.13.Final
>
>
> Getting Null Pointer Exception after running "create" command from CLI :
> Below is the exception snippet :
> ~~~
> 16:59:43,111 ERROR [org.infinispan.cli.interpreter.Interpreter] (management-handler-thread - 1) ISPN019003: Interpreter error: java.lang.NullPointerException
> at org.infinispan.cli.interpreter.session.SessionImpl.createCache(SessionImpl.java:109)
> at org.infinispan.cli.interpreter.statement.CreateStatement.execute(CreateStatement.java:25)
> at org.infinispan.cli.interpreter.Interpreter.execute(Interpreter.java:140)
> at org.infinispan.server.infinispan.SecurityActions.lambda$executeInterpreter$7(SecurityActions.java:268)
> at org.infinispan.security.Security.doPrivileged(Security.java:57)
> at org.infinispan.server.infinispan.SecurityActions.doPrivileged(SecurityActions.java:77)
> at org.infinispan.server.infinispan.SecurityActions.executeInterpreter(SecurityActions.java:269)
> at org.jboss.as.clustering.infinispan.subsystem.CliInterpreterHandler.execute(CliInterpreterHandler.java:71)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1411)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423)
> at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:265)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:231)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:246)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> ~~~
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[JBoss JIRA] (ISPN-10127) Error "mismatched input" in JDG CLI when trying to run site command with a hyphen in site's name
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10127?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10127:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/6843, https://github.com/infinispan/infinispan/pull/6844
> Error "mismatched input" in JDG CLI when trying to run site command with a hyphen in site's name
> ------------------------------------------------------------------------------------------------
>
> Key: ISPN-10127
> URL: https://issues.jboss.org/browse/ISPN-10127
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Affects Versions: 9.4.12.Final, 10.0.0.Beta3
> Environment: JDG 7.1.2 GA
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
>
> An error message is returned when trying to get status of a site in JDG CLI, possibly because the site name has a hyphen character on it.
> The following example of the site command being executed in CLI shows the response I've got, trying to execute in different ways:
> {code:borderStyle=solid}
> [standalone@localhost:9990 distributed-cache=default] site --status site-01
> line 1:14 mismatched input 'site' expecting set null
> line 1:20 mismatched input '1' expecting set null
> [standalone@localhost:9990 distributed-cache=default] site --status 'site-01'
> Incorrect site name: 'site-01'
> [standalone@localhost:9990 distributed-cache=default] site --status "site-01"
> Incorrect site name: "site-01"
> [standalone@localhost:9990 distributed-cache=default] site --status {site-01}
> line 1:14 mismatched input '{' expecting set null
> line 1:21 mismatched input '1' expecting set null
> [standalone@localhost:9990 distributed-cache=default] site --status "{site-01}"
> Incorrect site name: "{site-01}"
> {code}
> However, if I try to execute the following command with a site name without the hyphen character in it's value, everything works as expected:
> {code:borderStyle=solid}
> [standalone@localhost:9990 distributed-cache=default] site --status SFO
> online
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[JBoss JIRA] (ISPN-10127) Error "mismatched input" in JDG CLI when trying to run site command with a hyphen in site's name
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10127?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10127:
-----------------------------------
Status: Open (was: New)
> Error "mismatched input" in JDG CLI when trying to run site command with a hyphen in site's name
> ------------------------------------------------------------------------------------------------
>
> Key: ISPN-10127
> URL: https://issues.jboss.org/browse/ISPN-10127
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Affects Versions: 9.4.12.Final, 10.0.0.Beta3
> Environment: JDG 7.1.2 GA
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
>
> An error message is returned when trying to get status of a site in JDG CLI, possibly because the site name has a hyphen character on it.
> The following example of the site command being executed in CLI shows the response I've got, trying to execute in different ways:
> {code:borderStyle=solid}
> [standalone@localhost:9990 distributed-cache=default] site --status site-01
> line 1:14 mismatched input 'site' expecting set null
> line 1:20 mismatched input '1' expecting set null
> [standalone@localhost:9990 distributed-cache=default] site --status 'site-01'
> Incorrect site name: 'site-01'
> [standalone@localhost:9990 distributed-cache=default] site --status "site-01"
> Incorrect site name: "site-01"
> [standalone@localhost:9990 distributed-cache=default] site --status {site-01}
> line 1:14 mismatched input '{' expecting set null
> line 1:21 mismatched input '1' expecting set null
> [standalone@localhost:9990 distributed-cache=default] site --status "{site-01}"
> Incorrect site name: "{site-01}"
> {code}
> However, if I try to execute the following command with a site name without the hyphen character in it's value, everything works as expected:
> {code:borderStyle=solid}
> [standalone@localhost:9990 distributed-cache=default] site --status SFO
> online
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month
[JBoss JIRA] (ISPN-10127) Error "mismatched input" in JDG CLI when trying to run site command with a hyphen in site's name
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10127?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10127:
-----------------------------------
Security: (was: Red Hat Internal)
> Error "mismatched input" in JDG CLI when trying to run site command with a hyphen in site's name
> ------------------------------------------------------------------------------------------------
>
> Key: ISPN-10127
> URL: https://issues.jboss.org/browse/ISPN-10127
> Project: Infinispan
> Issue Type: Bug
> Components: CLI
> Affects Versions: 9.4.12.Final, 10.0.0.Beta3
> Environment: JDG 7.1.2 GA
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
>
> An error message is returned when trying to get status of a site in JDG CLI, possibly because the site name has a hyphen character on it.
> The following example of the site command being executed in CLI shows the response I've got, trying to execute in different ways:
> {code:borderStyle=solid}
> [standalone@localhost:9990 distributed-cache=default] site --status site-01
> line 1:14 mismatched input 'site' expecting set null
> line 1:20 mismatched input '1' expecting set null
> [standalone@localhost:9990 distributed-cache=default] site --status 'site-01'
> Incorrect site name: 'site-01'
> [standalone@localhost:9990 distributed-cache=default] site --status "site-01"
> Incorrect site name: "site-01"
> [standalone@localhost:9990 distributed-cache=default] site --status {site-01}
> line 1:14 mismatched input '{' expecting set null
> line 1:21 mismatched input '1' expecting set null
> [standalone@localhost:9990 distributed-cache=default] site --status "{site-01}"
> Incorrect site name: "{site-01}"
> {code}
> However, if I try to execute the following command with a site name without the hyphen character in it's value, everything works as expected:
> {code:borderStyle=solid}
> [standalone@localhost:9990 distributed-cache=default] site --status SFO
> online
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 1 month