[JBoss JIRA] (DROOLS-707) NullPointer when changing order of the rules
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-707?page=com.atlassian.jira.plugin... ]
Mario Fusco updated DROOLS-707:
-------------------------------
Fix Version/s: 6.2.0.Final
> NullPointer when changing order of the rules
> --------------------------------------------
>
> Key: DROOLS-707
> URL: https://issues.jboss.org/browse/DROOLS-707
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.0.Final, 6.0.1.Final, 6.1.0.Final, 6.2.0.CR4
> Reporter: Francesco Peloi
> Assignee: Mario Fusco
> Fix For: 6.2.0.Final
>
>
> Hi there,
> we are having some serious issues with some rules, they are throwing a NullPointerException and we don't understand why. I have tried to narrow down the problem to the smallest rule possible, now this rule doesn't really make much sense put like this but the real rule is more complex with more constraints. At the end the result is the same: a NPE.
> I have tried it with many Drools versions from 5.x to latest 6.3.0-SNAPSHOT.
> I tested this in isolation with the minimum amount of code possible, and attached it as well if someone wants to try it quickly.
> Note that if line 2 of the when:
> $a : Integer()
> is moved as first line, the rule runs ok.
> Please find the reproducer here: https://groups.google.com/forum/#!topic/drools-usage/-oNqu3l4cqE
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (DROOLS-707) NullPointer when changing order of the rules
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-707?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-707:
------------------------------------------------
Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1192054|https://bugzilla.redhat.com/show_bug.cgi?id=1192054] from ASSIGNED to MODIFIED
> NullPointer when changing order of the rules
> --------------------------------------------
>
> Key: DROOLS-707
> URL: https://issues.jboss.org/browse/DROOLS-707
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.0.Final, 6.0.1.Final, 6.1.0.Final, 6.2.0.CR4
> Reporter: Francesco Peloi
> Assignee: Mario Fusco
>
> Hi there,
> we are having some serious issues with some rules, they are throwing a NullPointerException and we don't understand why. I have tried to narrow down the problem to the smallest rule possible, now this rule doesn't really make much sense put like this but the real rule is more complex with more constraints. At the end the result is the same: a NPE.
> I have tried it with many Drools versions from 5.x to latest 6.3.0-SNAPSHOT.
> I tested this in isolation with the minimum amount of code possible, and attached it as well if someone wants to try it quickly.
> Note that if line 2 of the when:
> $a : Integer()
> is moved as first line, the rule runs ok.
> Please find the reproducer here: https://groups.google.com/forum/#!topic/drools-usage/-oNqu3l4cqE
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (DROOLS-707) NullPointer when changing order of the rules
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-707?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated DROOLS-707:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1192054
> NullPointer when changing order of the rules
> --------------------------------------------
>
> Key: DROOLS-707
> URL: https://issues.jboss.org/browse/DROOLS-707
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.0.Final, 6.0.1.Final, 6.1.0.Final, 6.2.0.CR4
> Reporter: Francesco Peloi
> Assignee: Mario Fusco
>
> Hi there,
> we are having some serious issues with some rules, they are throwing a NullPointerException and we don't understand why. I have tried to narrow down the problem to the smallest rule possible, now this rule doesn't really make much sense put like this but the real rule is more complex with more constraints. At the end the result is the same: a NPE.
> I have tried it with many Drools versions from 5.x to latest 6.3.0-SNAPSHOT.
> I tested this in isolation with the minimum amount of code possible, and attached it as well if someone wants to try it quickly.
> Note that if line 2 of the when:
> $a : Integer()
> is moved as first line, the rule runs ok.
> Please find the reproducer here: https://groups.google.com/forum/#!topic/drools-usage/-oNqu3l4cqE
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (DROOLS-707) NullPointer when changing order of the rules
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-707?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-707:
------------------------------------------------
Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1192054|https://bugzilla.redhat.com/show_bug.cgi?id=1192054] from NEW to ASSIGNED
> NullPointer when changing order of the rules
> --------------------------------------------
>
> Key: DROOLS-707
> URL: https://issues.jboss.org/browse/DROOLS-707
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.0.Final, 6.0.1.Final, 6.1.0.Final, 6.2.0.CR4
> Reporter: Francesco Peloi
> Assignee: Mario Fusco
>
> Hi there,
> we are having some serious issues with some rules, they are throwing a NullPointerException and we don't understand why. I have tried to narrow down the problem to the smallest rule possible, now this rule doesn't really make much sense put like this but the real rule is more complex with more constraints. At the end the result is the same: a NPE.
> I have tried it with many Drools versions from 5.x to latest 6.3.0-SNAPSHOT.
> I tested this in isolation with the minimum amount of code possible, and attached it as well if someone wants to try it quickly.
> Note that if line 2 of the when:
> $a : Integer()
> is moved as first line, the rule runs ok.
> Please find the reproducer here: https://groups.google.com/forum/#!topic/drools-usage/-oNqu3l4cqE
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (DROOLS-707) NullPointer when changing order of the rules
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-707?page=com.atlassian.jira.plugin... ]
Mario Fusco resolved DROOLS-707.
--------------------------------
Resolution: Done
Fixed by https://github.com/droolsjbpm/drools/commit/ef552a6f1
> NullPointer when changing order of the rules
> --------------------------------------------
>
> Key: DROOLS-707
> URL: https://issues.jboss.org/browse/DROOLS-707
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.0.Final, 6.0.1.Final, 6.1.0.Final, 6.2.0.CR4
> Reporter: Francesco Peloi
> Assignee: Mario Fusco
>
> Hi there,
> we are having some serious issues with some rules, they are throwing a NullPointerException and we don't understand why. I have tried to narrow down the problem to the smallest rule possible, now this rule doesn't really make much sense put like this but the real rule is more complex with more constraints. At the end the result is the same: a NPE.
> I have tried it with many Drools versions from 5.x to latest 6.3.0-SNAPSHOT.
> I tested this in isolation with the minimum amount of code possible, and attached it as well if someone wants to try it quickly.
> Note that if line 2 of the when:
> $a : Integer()
> is moved as first line, the rule runs ok.
> Please find the reproducer here: https://groups.google.com/forum/#!topic/drools-usage/-oNqu3l4cqE
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (REMJMX-84) Jboss JMX: Operation failed with status WAITING
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/REMJMX-84?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on REMJMX-84:
----------------------------------------
If you are a supported customer of EAP please raise a support case through the customer portal to discuss the supported options for obtaining these changes.
> Jboss JMX: Operation failed with status WAITING
> ------------------------------------------------
>
> Key: REMJMX-84
> URL: https://issues.jboss.org/browse/REMJMX-84
> Project: Remoting JMX
> Issue Type: Bug
> Environment: jboss-as-7.1.1.Final on windows server
> Reporter: Abhishek Apoorva
> Assignee: Darran Lofthouse
> Fix For: 2.0.1.CR1
>
>
> Version : jboss-as-7.1.1.Final on windows server
> I am getting below mentioned strange issue intermittently while fetching
> Jboss JMX Mbean.
> Can anyone help me to find the real cause of the issue? Secong thing is why it is coming intermittently either it should come always or it should not come at all.
> JMXConnectorFactory.connect(serviceURL, environment);
> While executing above mentioned line system is throwing below mentioned exception.
> {noformat}
> May 08 02:30:53:375 [DC#0, jboss] java.lang.RuntimeException: Operation failed with status WAITING
> at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:216)
> at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:143)
> at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94)
> at javax.management.remote.JMXConnectorFactory.connect(Unknown Source)
> at com.nimsoft.nimbus.probe.application.jboss.JmxConnection.createConnection(JmxConnection.java:68)
> at com.nimsoft.nimbus.probe.application.jsr160.Entity.createConnection(Entity.java:1772)
> at com.nimsoft.nimbus.probe.application.jsr160.Entity.getValue(Entity.java:1567)
> at com.nimsoft.nimbus.probe.application.extractbase.Extract.processMonitor(Extract.java:1324)
> at com.nimsoft.nimbus.probe.application.extractbase.Extract.processResource(Extract.java:1908)
> at com.nimsoft.nimbus.probe.application.extractbase.Extract$DataCollector.run(Extract.java:1158)
> at java.lang.Thread.run(Unknown Source)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (REMJMX-84) Jboss JMX: Operation failed with status WAITING
by Piotr Findeisen (JIRA)
[ https://issues.jboss.org/browse/REMJMX-84?page=com.atlassian.jira.plugin.... ]
Piotr Findeisen edited comment on REMJMX-84 at 2/12/15 8:28 AM:
----------------------------------------------------------------
Thanks!
i see this is REMJMX-86, delivered in 1.1.3.Final.
Can I use 1.1.3.Final with JBoss 7 and EAP 6.2?
was (Author: findepi):
Thanks!
>From blame i see this is REMJMX-86, delivered in 1.1.3.Final.
Can I use 1.1.3.Final with JBoss 7 and EAP 6.2?
> Jboss JMX: Operation failed with status WAITING
> ------------------------------------------------
>
> Key: REMJMX-84
> URL: https://issues.jboss.org/browse/REMJMX-84
> Project: Remoting JMX
> Issue Type: Bug
> Environment: jboss-as-7.1.1.Final on windows server
> Reporter: Abhishek Apoorva
> Assignee: Darran Lofthouse
> Fix For: 2.0.1.CR1
>
>
> Version : jboss-as-7.1.1.Final on windows server
> I am getting below mentioned strange issue intermittently while fetching
> Jboss JMX Mbean.
> Can anyone help me to find the real cause of the issue? Secong thing is why it is coming intermittently either it should come always or it should not come at all.
> JMXConnectorFactory.connect(serviceURL, environment);
> While executing above mentioned line system is throwing below mentioned exception.
> {noformat}
> May 08 02:30:53:375 [DC#0, jboss] java.lang.RuntimeException: Operation failed with status WAITING
> at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:216)
> at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:143)
> at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94)
> at javax.management.remote.JMXConnectorFactory.connect(Unknown Source)
> at com.nimsoft.nimbus.probe.application.jboss.JmxConnection.createConnection(JmxConnection.java:68)
> at com.nimsoft.nimbus.probe.application.jsr160.Entity.createConnection(Entity.java:1772)
> at com.nimsoft.nimbus.probe.application.jsr160.Entity.getValue(Entity.java:1567)
> at com.nimsoft.nimbus.probe.application.extractbase.Extract.processMonitor(Extract.java:1324)
> at com.nimsoft.nimbus.probe.application.extractbase.Extract.processResource(Extract.java:1908)
> at com.nimsoft.nimbus.probe.application.extractbase.Extract$DataCollector.run(Extract.java:1158)
> at java.lang.Thread.run(Unknown Source)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (REMJMX-84) Jboss JMX: Operation failed with status WAITING
by Piotr Findeisen (JIRA)
[ https://issues.jboss.org/browse/REMJMX-84?page=com.atlassian.jira.plugin.... ]
Piotr Findeisen commented on REMJMX-84:
---------------------------------------
Thanks!
>From blame i see this is REMJMX-86, delivered in 1.1.3.Final.
Can I use 1.1.3.Final with JBoss 7 and EAP 6.2?
> Jboss JMX: Operation failed with status WAITING
> ------------------------------------------------
>
> Key: REMJMX-84
> URL: https://issues.jboss.org/browse/REMJMX-84
> Project: Remoting JMX
> Issue Type: Bug
> Environment: jboss-as-7.1.1.Final on windows server
> Reporter: Abhishek Apoorva
> Assignee: Darran Lofthouse
> Fix For: 2.0.1.CR1
>
>
> Version : jboss-as-7.1.1.Final on windows server
> I am getting below mentioned strange issue intermittently while fetching
> Jboss JMX Mbean.
> Can anyone help me to find the real cause of the issue? Secong thing is why it is coming intermittently either it should come always or it should not come at all.
> JMXConnectorFactory.connect(serviceURL, environment);
> While executing above mentioned line system is throwing below mentioned exception.
> {noformat}
> May 08 02:30:53:375 [DC#0, jboss] java.lang.RuntimeException: Operation failed with status WAITING
> at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:216)
> at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:143)
> at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94)
> at javax.management.remote.JMXConnectorFactory.connect(Unknown Source)
> at com.nimsoft.nimbus.probe.application.jboss.JmxConnection.createConnection(JmxConnection.java:68)
> at com.nimsoft.nimbus.probe.application.jsr160.Entity.createConnection(Entity.java:1772)
> at com.nimsoft.nimbus.probe.application.jsr160.Entity.getValue(Entity.java:1567)
> at com.nimsoft.nimbus.probe.application.extractbase.Extract.processMonitor(Extract.java:1324)
> at com.nimsoft.nimbus.probe.application.extractbase.Extract.processResource(Extract.java:1908)
> at com.nimsoft.nimbus.probe.application.extractbase.Extract$DataCollector.run(Extract.java:1158)
> at java.lang.Thread.run(Unknown Source)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (REMJMX-84) Jboss JMX: Operation failed with status WAITING
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/REMJMX-84?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse resolved REMJMX-84.
------------------------------------
Assignee: Darran Lofthouse (was: David Lloyd)
Fix Version/s: 2.0.1.CR1
Resolution: Out of Date
Remoting JMX has already been updated to support configurable timeouts: -
https://github.com/jbossas/remoting-jmx/blob/master/src/main/java/org/jbo...
> Jboss JMX: Operation failed with status WAITING
> ------------------------------------------------
>
> Key: REMJMX-84
> URL: https://issues.jboss.org/browse/REMJMX-84
> Project: Remoting JMX
> Issue Type: Bug
> Environment: jboss-as-7.1.1.Final on windows server
> Reporter: Abhishek Apoorva
> Assignee: Darran Lofthouse
> Fix For: 2.0.1.CR1
>
>
> Version : jboss-as-7.1.1.Final on windows server
> I am getting below mentioned strange issue intermittently while fetching
> Jboss JMX Mbean.
> Can anyone help me to find the real cause of the issue? Secong thing is why it is coming intermittently either it should come always or it should not come at all.
> JMXConnectorFactory.connect(serviceURL, environment);
> While executing above mentioned line system is throwing below mentioned exception.
> {noformat}
> May 08 02:30:53:375 [DC#0, jboss] java.lang.RuntimeException: Operation failed with status WAITING
> at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:216)
> at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:143)
> at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94)
> at javax.management.remote.JMXConnectorFactory.connect(Unknown Source)
> at com.nimsoft.nimbus.probe.application.jboss.JmxConnection.createConnection(JmxConnection.java:68)
> at com.nimsoft.nimbus.probe.application.jsr160.Entity.createConnection(Entity.java:1772)
> at com.nimsoft.nimbus.probe.application.jsr160.Entity.getValue(Entity.java:1567)
> at com.nimsoft.nimbus.probe.application.extractbase.Extract.processMonitor(Extract.java:1324)
> at com.nimsoft.nimbus.probe.application.extractbase.Extract.processResource(Extract.java:1908)
> at com.nimsoft.nimbus.probe.application.extractbase.Extract$DataCollector.run(Extract.java:1158)
> at java.lang.Thread.run(Unknown Source)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (REMJMX-84) Jboss JMX: Operation failed with status WAITING
by Piotr Findeisen (JIRA)
[ https://issues.jboss.org/browse/REMJMX-84?page=com.atlassian.jira.plugin.... ]
Piotr Findeisen commented on REMJMX-84:
---------------------------------------
The reason seems simple:
{code:java|title=org.jboss.remotingjmx.RemotingConnector.internalConnect}
// Now open the channel
final IoFuture<Channel> futureChannel = connection.openChannel(serviceName, OptionMap.EMPTY);
IoFuture.Status result = futureChannel.await(5, TimeUnit.SECONDS); // <-- 5 seconds
if (result == IoFuture.Status.DONE) {
channel = futureChannel.get();
} else if (result == IoFuture.Status.FAILED) {
throw new IOException(futureChannel.getException());
} else {
throw new RuntimeException("Operation failed with status " + result);
}
{code}
As you see there is a hard-coded timeout of 5 seconds. I changed the timeout and now I'm able to connect. Apparently in some cases the connection takes up to 10 seconds! This is so even though the TCP-level connect takes 0.2s -- the 5 s timeout seems to cover _much_ more than just TCP connect.
(You can see my exact changes @ https://github.com/syncron/remoting-jmx/commit/32b35058230402b7b6a03ef1e3...)
> Jboss JMX: Operation failed with status WAITING
> ------------------------------------------------
>
> Key: REMJMX-84
> URL: https://issues.jboss.org/browse/REMJMX-84
> Project: Remoting JMX
> Issue Type: Bug
> Environment: jboss-as-7.1.1.Final on windows server
> Reporter: Abhishek Apoorva
> Assignee: David Lloyd
>
> Version : jboss-as-7.1.1.Final on windows server
> I am getting below mentioned strange issue intermittently while fetching
> Jboss JMX Mbean.
> Can anyone help me to find the real cause of the issue? Secong thing is why it is coming intermittently either it should come always or it should not come at all.
> JMXConnectorFactory.connect(serviceURL, environment);
> While executing above mentioned line system is throwing below mentioned exception.
> {noformat}
> May 08 02:30:53:375 [DC#0, jboss] java.lang.RuntimeException: Operation failed with status WAITING
> at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:216)
> at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:143)
> at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94)
> at javax.management.remote.JMXConnectorFactory.connect(Unknown Source)
> at com.nimsoft.nimbus.probe.application.jboss.JmxConnection.createConnection(JmxConnection.java:68)
> at com.nimsoft.nimbus.probe.application.jsr160.Entity.createConnection(Entity.java:1772)
> at com.nimsoft.nimbus.probe.application.jsr160.Entity.getValue(Entity.java:1567)
> at com.nimsoft.nimbus.probe.application.extractbase.Extract.processMonitor(Extract.java:1324)
> at com.nimsoft.nimbus.probe.application.extractbase.Extract.processResource(Extract.java:1908)
> at com.nimsoft.nimbus.probe.application.extractbase.Extract$DataCollector.run(Extract.java:1158)
> at java.lang.Thread.run(Unknown Source)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months