[JBoss JIRA] (ISPN-6071) NullPointerException when executing RemoveExpiredCommand
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-6071?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-6071:
--------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/4160
> NullPointerException when executing RemoveExpiredCommand
> --------------------------------------------------------
>
> Key: ISPN-6071
> URL: https://issues.…
[View More]jboss.org/browse/ISPN-6071
> Project: Infinispan
> Issue Type: Bug
> Components: Expiration
> Affects Versions: 8.0.2.Final
> Reporter: Jason Hoetger
> Assignee: William Burns
> Fix For: 9.0.0.Alpha1, 8.1.4.Final, 8.2.2.Final
>
>
> I'm running Infinispan 8.0.2 in a clustered environment with a replicated cache with a single file cache store. I'm seeing some NullPointerExceptions when Infinispan executes the RemoveExpiredCommand. Here's a snippet from the stack trace:
> {noformat}
> ISPN000136: Error executing command RemoveExpiredCommand, writing keys [...large key here...]
> ...
> Caused by: java.lang.NullPointerException: null
> at org.infinispan.commands.write.RemoveExpiredCommand.setParameters(RemoveExpiredCommand.java:142)
> {noformat}
> Here's RemoveExpiredCommand#setParameters(...):
> {code} @Override
> public void setParameters(int commandId, Object[] args) {
> if (commandId != COMMAND_ID) throw new IllegalStateException("Invalid method id");
> int i = 0;
> commandInvocationId = (CommandInvocationId) args[i++];
> key = args[i++];
> value = args[i++];
> lifespan = (long) args[i++];
> }{code}
> Line 142 is the cast of assignment of {{args\[3\]}} to primitive type long, which is causing the NPE. lifespan is actually a Long, not a long, and the {{perform()}} method seems to anticipate null lifespans at line 72:
> {code} // If the provided lifespan is null, that means it is a store removal command, so we can't compare lifespan
> if (lifespan == null) {}{code}
> Could this be fixed by simply changing the cast at line 142 from (long) to (Long)?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 9 months
[JBoss JIRA] (ISPN-6465) Managent console - launching task with no parameters creates one empty parameter
by Jiří Holuša (JIRA)
Jiří Holuša created ISPN-6465:
---------------------------------
Summary: Managent console - launching task with no parameters creates one empty parameter
Key: ISPN-6465
URL: https://issues.jboss.org/browse/ISPN-6465
Project: Infinispan
Issue Type: Bug
Components: Console
Reporter: Jiří Holuša
Assignee: Vladimir Blagojevic
Page: Caches -> select cache container -> select Tasks …
[View More]execution tab
When launching new task, you can specify parameters, which works correctly, if you do. However, if you specify no parameters, you would then expect in your task when calling TaskContext.getParameters() to be null (or at least empty). Currently when you specify no parameters, the getParameters() returns Map with one entry, both empty key and value.
This issue was not present in previous releases, when if no parameter specified, the getParameters returned null. I went through the history and tracked down the commit which causes it:
{code}
commit 6a4d156a9678bcde18d8365ee75fbcea31373949
Author: vblagoje <vblagoje(a)redhat.com>
Date: Wed Mar 16 14:57:02 2016 -0400
Simplify task handling
{code}
However, finding the actual cause is below my AngularJS knowledge.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 9 months
[JBoss JIRA] (ISPN-6071) NullPointerException when executing RemoveExpiredCommand
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-6071?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-6071:
-------------------------------
Description:
I'm running Infinispan 8.0.2 in a clustered environment with a replicated cache with a single file cache store. I'm seeing some NullPointerExceptions when Infinispan executes the RemoveExpiredCommand. Here's a snippet from the stack trace:
{noformat}
ISPN000136: Error executing command RemoveExpiredCommand, writing keys [...large …
[View More]key here...]
...
Caused by: java.lang.NullPointerException: null
at org.infinispan.commands.write.RemoveExpiredCommand.setParameters(RemoveExpiredCommand.java:142)
{noformat}
Here's RemoveExpiredCommand#setParameters(...):
{code} @Override
public void setParameters(int commandId, Object[] args) {
if (commandId != COMMAND_ID) throw new IllegalStateException("Invalid method id");
int i = 0;
commandInvocationId = (CommandInvocationId) args[i++];
key = args[i++];
value = args[i++];
lifespan = (long) args[i++];
}{code}
Line 142 is the cast of assignment of {{args\[3\]}} to primitive type long, which is causing the NPE. lifespan is actually a Long, not a long, and the {{perform()}} method seems to anticipate null lifespans at line 72:
{code} // If the provided lifespan is null, that means it is a store removal command, so we can't compare lifespan
if (lifespan == null) {}{code}
Could this be fixed by simply changing the cast at line 142 from (long) to (Long)?
was:
I'm running Infinispan 8.0.2 in a clustered environment with a replicated cache with a single file cache store. I'm seeing some NullPointerExceptions when Infinispan executes the RemoveExpiredCommand. Here's a snippet from the stack trace:
{{ISPN000136: Error executing command RemoveExpiredCommand, writing keys [...large key here...]
...
Caused by: java.lang.NullPointerException: null
at org.infinispan.commands.write.RemoveExpiredCommand.setParameters(RemoveExpiredCommand.java:142)}}
Here's RemoveExpiredCommand#setParameters(...):
{{ @Override
public void setParameters(int commandId, Object[] args) {
if (commandId != COMMAND_ID) throw new IllegalStateException("Invalid method id");
int i = 0;
commandInvocationId = (CommandInvocationId) args[i++];
key = args[i++];
value = args[i++];
lifespan = (long) args[i++];
}}}
Line 142 is the cast of assignment of args[3] to primitive type long, which is causing the NPE. lifespan is actually a Long, not a long, and the #perform() method seems to anticipate null lifespans at line 72:
{{ // If the provided lifespan is null, that means it is a store removal command, so we can't compare lifespan
if (lifespan == null) {}}
Could this be fixed by simply changing the cast at line 142 from (long) to (Long)?
> NullPointerException when executing RemoveExpiredCommand
> --------------------------------------------------------
>
> Key: ISPN-6071
> URL: https://issues.jboss.org/browse/ISPN-6071
> Project: Infinispan
> Issue Type: Bug
> Components: Expiration
> Affects Versions: 8.0.2.Final
> Reporter: Jason Hoetger
> Assignee: William Burns
> Fix For: 9.0.0.Alpha1, 8.1.4.Final, 8.2.2.Final
>
>
> I'm running Infinispan 8.0.2 in a clustered environment with a replicated cache with a single file cache store. I'm seeing some NullPointerExceptions when Infinispan executes the RemoveExpiredCommand. Here's a snippet from the stack trace:
> {noformat}
> ISPN000136: Error executing command RemoveExpiredCommand, writing keys [...large key here...]
> ...
> Caused by: java.lang.NullPointerException: null
> at org.infinispan.commands.write.RemoveExpiredCommand.setParameters(RemoveExpiredCommand.java:142)
> {noformat}
> Here's RemoveExpiredCommand#setParameters(...):
> {code} @Override
> public void setParameters(int commandId, Object[] args) {
> if (commandId != COMMAND_ID) throw new IllegalStateException("Invalid method id");
> int i = 0;
> commandInvocationId = (CommandInvocationId) args[i++];
> key = args[i++];
> value = args[i++];
> lifespan = (long) args[i++];
> }{code}
> Line 142 is the cast of assignment of {{args\[3\]}} to primitive type long, which is causing the NPE. lifespan is actually a Long, not a long, and the {{perform()}} method seems to anticipate null lifespans at line 72:
> {code} // If the provided lifespan is null, that means it is a store removal command, so we can't compare lifespan
> if (lifespan == null) {}{code}
> Could this be fixed by simply changing the cast at line 142 from (long) to (Long)?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 9 months
[JBoss JIRA] (ISPN-6404) Add missing schemas into docs/schemas for ISPN
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6404?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6404:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.0.0.Alpha1
8.2.2.Final
9.0.0.Final
Resolution: Done
> Add missing schemas into docs/schemas for ISPN
> ----------------------------------------------
>
> Key: ISPN-6404
> URL: …
[View More]https://issues.jboss.org/browse/ISPN-6404
> Project: Infinispan
> Issue Type: Enhancement
> Components: Build process, Server
> Reporter: Sebastian Łaskawiec
> Assignee: Sebastian Łaskawiec
> Fix For: 9.0.0.Alpha1, 8.2.2.Final, 9.0.0.Final
>
>
> ISPN server is missing some important schemas. We need to add them since they are mentioned in the configuration.
> We need the following:
> jboss-as-jgroups_1_0.xsd
> jboss-as-jgroups_1_1.xsd
> jboss-as-jgroups_1_2.xsd
> jboss-as-jgroups_2_0.xsd
> jboss-as-jgroups_3_0.xsd
> jboss-infinispan-endpoint_5_2.xsd
> jboss-infinispan-endpoint_6_0.xsd
> jboss-infinispan-endpoint_7_0.xsd
> jboss-infinispan-endpoint_7_2.xsd
> jboss-infinispan-endpoint_8_0.xsd
> jboss-infinispan-jgroups_7_0.xsd
> jboss-infinispan-jgroups_8_0.xsd
> jboss-infinispan-core_6_0.xsd
> jboss-infinispan-core_7_1.xsd
> jboss-infinispan-core_8_0.xsd
> jboss-infinispan-core_8_2.xsd
> jboss-infinispan-core_7_0.xsd
> jboss-infinispan-core_7_2.xsd
> jboss-infinispan-core_8_1.xsd
> jboss-infinispan-core_9_0.xsd
> jboss-as-cli_1_0.xsd
> jboss-as-cli_1_1.xsd
> jboss-as-cli_1_2.xsd
> jboss-as-cli_2_0.xsd
> jboss-as-config_1_0.xsd
> jboss-as-config_1_1.xsd
> jboss-as-config_1_2.xsd
> jboss-as-config_1_3.xsd
> jboss-as-config_1_4.xsd
> jboss-as-config_1_5.xsd
> jboss-as-config_2_0.xsd
> jboss-as-config_2_1.xsd
> jboss-as-datasources_1_0.xsd
> jboss-as-datasources_1_1.xsd
> jboss-as-datasources_1_2.xsd
> jboss-as-jmx_1_0.xsd
> jboss-as-jmx_1_1.xsd
> jboss-as-jmx_1_2.xsd
> jboss-as-jmx_1_3.xsd
> jboss-as-logging_1_0.xsd
> jboss-as-logging_1_1.xsd
> jboss-as-logging_1_2.xsd
> jboss-as-logging_1_3.xsd
> jboss-as-logging_2_0.xsd
> jboss-as-txn_1_0.xsd
> jboss-as-txn_1_1.xsd
> jboss-as-txn_1_2.xsd
> jboss-as-txn_1_3.xsd
> jboss-as-txn_1_4.xsd
> jboss-as-txn_1_5.xsd
> jboss-as-txn_2_0.xsd
> jboss-as-xts_1_0.xsd
> jboss-as-xts_2_0.xsd
> wildfly-cli_3_0.xsd
> wildfly-config_3_0.xsd
> wildfly-config_4_0.xsd
> module-1_0.xsd
> module-1_1.xsd
> module-1_2.xsd
> module-1_3.xsd
> module-1_5.xsd
> jboss-as-deployment-scanner_1_0.xsd
> jboss-as-deployment-scanner_1_1.xsd
> jboss-as-deployment-scanner_2_0.xsd
> wildfly-txn_3_0.xsd
> wildfly-datasources_2_0.xsd
> wildfly-datasources_3_0.xsd
> wildfly-datasources_4_0.xsd
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 9 months
[JBoss JIRA] (ISPN-6404) Add missing schemas into docs/schemas for ISPN
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6404?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6404:
----------------------------------
Status: Open (was: New)
> Add missing schemas into docs/schemas for ISPN
> ----------------------------------------------
>
> Key: ISPN-6404
> URL: https://issues.jboss.org/browse/ISPN-6404
> Project: Infinispan
> Issue Type: Enhancement
> Components: …
[View More]Build process, Server
> Reporter: Sebastian Łaskawiec
> Assignee: Sebastian Łaskawiec
>
> ISPN server is missing some important schemas. We need to add them since they are mentioned in the configuration.
> We need the following:
> jboss-as-jgroups_1_0.xsd
> jboss-as-jgroups_1_1.xsd
> jboss-as-jgroups_1_2.xsd
> jboss-as-jgroups_2_0.xsd
> jboss-as-jgroups_3_0.xsd
> jboss-infinispan-endpoint_5_2.xsd
> jboss-infinispan-endpoint_6_0.xsd
> jboss-infinispan-endpoint_7_0.xsd
> jboss-infinispan-endpoint_7_2.xsd
> jboss-infinispan-endpoint_8_0.xsd
> jboss-infinispan-jgroups_7_0.xsd
> jboss-infinispan-jgroups_8_0.xsd
> jboss-infinispan-core_6_0.xsd
> jboss-infinispan-core_7_1.xsd
> jboss-infinispan-core_8_0.xsd
> jboss-infinispan-core_8_2.xsd
> jboss-infinispan-core_7_0.xsd
> jboss-infinispan-core_7_2.xsd
> jboss-infinispan-core_8_1.xsd
> jboss-infinispan-core_9_0.xsd
> jboss-as-cli_1_0.xsd
> jboss-as-cli_1_1.xsd
> jboss-as-cli_1_2.xsd
> jboss-as-cli_2_0.xsd
> jboss-as-config_1_0.xsd
> jboss-as-config_1_1.xsd
> jboss-as-config_1_2.xsd
> jboss-as-config_1_3.xsd
> jboss-as-config_1_4.xsd
> jboss-as-config_1_5.xsd
> jboss-as-config_2_0.xsd
> jboss-as-config_2_1.xsd
> jboss-as-datasources_1_0.xsd
> jboss-as-datasources_1_1.xsd
> jboss-as-datasources_1_2.xsd
> jboss-as-jmx_1_0.xsd
> jboss-as-jmx_1_1.xsd
> jboss-as-jmx_1_2.xsd
> jboss-as-jmx_1_3.xsd
> jboss-as-logging_1_0.xsd
> jboss-as-logging_1_1.xsd
> jboss-as-logging_1_2.xsd
> jboss-as-logging_1_3.xsd
> jboss-as-logging_2_0.xsd
> jboss-as-txn_1_0.xsd
> jboss-as-txn_1_1.xsd
> jboss-as-txn_1_2.xsd
> jboss-as-txn_1_3.xsd
> jboss-as-txn_1_4.xsd
> jboss-as-txn_1_5.xsd
> jboss-as-txn_2_0.xsd
> jboss-as-xts_1_0.xsd
> jboss-as-xts_2_0.xsd
> wildfly-cli_3_0.xsd
> wildfly-config_3_0.xsd
> wildfly-config_4_0.xsd
> module-1_0.xsd
> module-1_1.xsd
> module-1_2.xsd
> module-1_3.xsd
> module-1_5.xsd
> jboss-as-deployment-scanner_1_0.xsd
> jboss-as-deployment-scanner_1_1.xsd
> jboss-as-deployment-scanner_2_0.xsd
> wildfly-txn_3_0.xsd
> wildfly-datasources_2_0.xsd
> wildfly-datasources_3_0.xsd
> wildfly-datasources_4_0.xsd
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 9 months
[JBoss JIRA] (ISPN-6404) Add missing schemas into docs/schemas for ISPN
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6404?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6404:
----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/4189
> Add missing schemas into docs/schemas for ISPN
> ----------------------------------------------
>
> Key: ISPN-6404
> URL: https://issues.jboss.org/browse/ISPN-6404
> …
[View More] Project: Infinispan
> Issue Type: Enhancement
> Components: Build process, Server
> Reporter: Sebastian Łaskawiec
> Assignee: Sebastian Łaskawiec
>
> ISPN server is missing some important schemas. We need to add them since they are mentioned in the configuration.
> We need the following:
> jboss-as-jgroups_1_0.xsd
> jboss-as-jgroups_1_1.xsd
> jboss-as-jgroups_1_2.xsd
> jboss-as-jgroups_2_0.xsd
> jboss-as-jgroups_3_0.xsd
> jboss-infinispan-endpoint_5_2.xsd
> jboss-infinispan-endpoint_6_0.xsd
> jboss-infinispan-endpoint_7_0.xsd
> jboss-infinispan-endpoint_7_2.xsd
> jboss-infinispan-endpoint_8_0.xsd
> jboss-infinispan-jgroups_7_0.xsd
> jboss-infinispan-jgroups_8_0.xsd
> jboss-infinispan-core_6_0.xsd
> jboss-infinispan-core_7_1.xsd
> jboss-infinispan-core_8_0.xsd
> jboss-infinispan-core_8_2.xsd
> jboss-infinispan-core_7_0.xsd
> jboss-infinispan-core_7_2.xsd
> jboss-infinispan-core_8_1.xsd
> jboss-infinispan-core_9_0.xsd
> jboss-as-cli_1_0.xsd
> jboss-as-cli_1_1.xsd
> jboss-as-cli_1_2.xsd
> jboss-as-cli_2_0.xsd
> jboss-as-config_1_0.xsd
> jboss-as-config_1_1.xsd
> jboss-as-config_1_2.xsd
> jboss-as-config_1_3.xsd
> jboss-as-config_1_4.xsd
> jboss-as-config_1_5.xsd
> jboss-as-config_2_0.xsd
> jboss-as-config_2_1.xsd
> jboss-as-datasources_1_0.xsd
> jboss-as-datasources_1_1.xsd
> jboss-as-datasources_1_2.xsd
> jboss-as-jmx_1_0.xsd
> jboss-as-jmx_1_1.xsd
> jboss-as-jmx_1_2.xsd
> jboss-as-jmx_1_3.xsd
> jboss-as-logging_1_0.xsd
> jboss-as-logging_1_1.xsd
> jboss-as-logging_1_2.xsd
> jboss-as-logging_1_3.xsd
> jboss-as-logging_2_0.xsd
> jboss-as-txn_1_0.xsd
> jboss-as-txn_1_1.xsd
> jboss-as-txn_1_2.xsd
> jboss-as-txn_1_3.xsd
> jboss-as-txn_1_4.xsd
> jboss-as-txn_1_5.xsd
> jboss-as-txn_2_0.xsd
> jboss-as-xts_1_0.xsd
> jboss-as-xts_2_0.xsd
> wildfly-cli_3_0.xsd
> wildfly-config_3_0.xsd
> wildfly-config_4_0.xsd
> module-1_0.xsd
> module-1_1.xsd
> module-1_2.xsd
> module-1_3.xsd
> module-1_5.xsd
> jboss-as-deployment-scanner_1_0.xsd
> jboss-as-deployment-scanner_1_1.xsd
> jboss-as-deployment-scanner_2_0.xsd
> wildfly-txn_3_0.xsd
> wildfly-datasources_2_0.xsd
> wildfly-datasources_3_0.xsd
> wildfly-datasources_4_0.xsd
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 9 months
[JBoss JIRA] (ISPN-6071) NullPointerException when executing RemoveExpiredCommand
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-6071?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-6071:
--------------------------------
Fix Version/s: 9.0.0.Alpha1
8.1.4.Final
8.2.2.Final
> NullPointerException when executing RemoveExpiredCommand
> --------------------------------------------------------
>
> Key: ISPN-6071
> URL: https://issues.jboss.org/browse/ISPN-6071
> …
[View More]Project: Infinispan
> Issue Type: Bug
> Components: Expiration
> Affects Versions: 8.0.2.Final
> Reporter: Jason Hoetger
> Assignee: William Burns
> Fix For: 9.0.0.Alpha1, 8.1.4.Final, 8.2.2.Final
>
>
> I'm running Infinispan 8.0.2 in a clustered environment with a replicated cache with a single file cache store. I'm seeing some NullPointerExceptions when Infinispan executes the RemoveExpiredCommand. Here's a snippet from the stack trace:
> {{ISPN000136: Error executing command RemoveExpiredCommand, writing keys [...large key here...]
> ...
> Caused by: java.lang.NullPointerException: null
> at org.infinispan.commands.write.RemoveExpiredCommand.setParameters(RemoveExpiredCommand.java:142)}}
> Here's RemoveExpiredCommand#setParameters(...):
> {{ @Override
> public void setParameters(int commandId, Object[] args) {
> if (commandId != COMMAND_ID) throw new IllegalStateException("Invalid method id");
> int i = 0;
> commandInvocationId = (CommandInvocationId) args[i++];
> key = args[i++];
> value = args[i++];
> lifespan = (long) args[i++];
> }}}
> Line 142 is the cast of assignment of args[3] to primitive type long, which is causing the NPE. lifespan is actually a Long, not a long, and the #perform() method seems to anticipate null lifespans at line 72:
> {{ // If the provided lifespan is null, that means it is a store removal command, so we can't compare lifespan
> if (lifespan == null) {}}
> Could this be fixed by simply changing the cast at line 142 from (long) to (Long)?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 9 months