[JBoss JIRA] (DROOLS-1116) After adding new Rule by different drl filename getting error while calling fireRules
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1116?page=com.atlassian.jira.plugi... ]
Mario Fusco reassigned DROOLS-1116:
-----------------------------------
Assignee: Mario Fusco (was: Edson Tirelli)
> After adding new Rule by different drl filename getting error while calling fireRules
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-1116
> URL: https://issues.jboss.org/browse/DROOLS-1116
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.4.0.CR2
> Reporter: Vivek Singh
> Assignee: Mario Fusco
>
> Issue is similar to https://issues.jboss.org/browse/DROOLS-978
> But its showing its fixed in 6.4.0.Beta1 but i am still lfacing in 6.4.0.CR2
> While Adding the new or Updated Rules by createKieJar.
> Even renaming the Drool file.
> After that while calling the fireRules i am getting the below error:-
> Exception in thread "main" java.lang.NullPointerException
> at org.drools.core.reteoo.NodeTypeEnums.isBetaNode(NodeTypeEnums.java:88)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:254)
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:166)
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:123)
> at org.drools.core.phreak.RuleExecutor.evaluateNetwork(RuleExecutor.java:65)
> at org.drools.core.common.DefaultAgenda.evaluateEagerList(DefaultAgenda.java:1004)
> at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:961)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1292)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1294)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1281)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1260
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6013) Admin Console: cannot update min and max pool sizes for XA data source
by Chen Maoqian (JIRA)
[ https://issues.jboss.org/browse/WFLY-6013?page=com.atlassian.jira.plugin.... ]
Chen Maoqian edited comment on WFLY-6013 at 4/8/16 3:38 AM:
------------------------------------------------------------
Hello,i just want to reproduce the error from what your description,but it can not be reproduced in Wildfly 9.0.2.Final and Wildfly 10.0.0.so i suggest you can try it with wildfly 10,and if you can also meet this error,you can tell us !Thanks.
was (Author: bayern39):
Hello,i just want to reproduce the erro from what your description,but it can not be reproduced in Wildfly 9.0.2.Final and Wildfly 10.0.0.so i suggest you can try it with wildfly 10,and if you can also meet this error,you can tell us !Thanks.
> Admin Console: cannot update min and max pool sizes for XA data source
> ----------------------------------------------------------------------
>
> Key: WFLY-6013
> URL: https://issues.jboss.org/browse/WFLY-6013
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 9.0.2.Final
> Reporter: The Alchemist
> Assignee: Chen Maoqian
> Priority: Minor
>
> h2. How to Reproduce
> # Start Wildfly
> # Create a XA data source and set min pool size to 1, max pool size to 5
> # Refresh your web browser
> # Go to the data source you created, and update the min to 10, and max to 50. You'll get this error:
> {code}
> Unexpected HTTP response: 500
> Request
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "java:jboss/datasources/myAuth")
> ],
> "operation" => "write-attribute",
> "name" => "min-pool-size",
> "value" => 10
> },
> {
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "java:jboss/datasources/myAuth")
> ],
> "operation" => "write-attribute",
> "name" => "initial-pool-size",
> "value" => undefined
> },
> {
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "java:jboss/datasources/myAuth")
> ],
> "operation" => "write-attribute",
> "name" => "max-pool-size",
> "value" => 50
> }
> ]
> }
> Response
> Internal Server Error
> {
> "outcome" => "failed",
> "result" => {
> "step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> },
> "step-2" => {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0045: failed to set attribute: null",
> "rolled-back" => true
> },
> "step-3" => {
> "outcome" => "failed",
> "rolled-back" => true
> }
> },
> "failure-description" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "WFLYJCA0045: failed to set attribute: null"}},
> "rolled-back" => true
> }
> {code}
> Looks like the web console is trying to write the {{initialPoolSize}} attribute too, even though I haven't touched it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6013) Admin Console: cannot update min and max pool sizes for XA data source
by Chen Maoqian (JIRA)
[ https://issues.jboss.org/browse/WFLY-6013?page=com.atlassian.jira.plugin.... ]
Chen Maoqian edited comment on WFLY-6013 at 4/8/16 3:38 AM:
------------------------------------------------------------
Hello,i just want to reproduce the error from your description,but it can not be reproduced in Wildfly 9.0.2.Final and Wildfly 10.0.0.so i suggest you can try it with wildfly 10,and if you can also meet this error,you can tell us !Thanks.
was (Author: bayern39):
Hello,i just want to reproduce the error from what your description,but it can not be reproduced in Wildfly 9.0.2.Final and Wildfly 10.0.0.so i suggest you can try it with wildfly 10,and if you can also meet this error,you can tell us !Thanks.
> Admin Console: cannot update min and max pool sizes for XA data source
> ----------------------------------------------------------------------
>
> Key: WFLY-6013
> URL: https://issues.jboss.org/browse/WFLY-6013
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 9.0.2.Final
> Reporter: The Alchemist
> Assignee: Chen Maoqian
> Priority: Minor
>
> h2. How to Reproduce
> # Start Wildfly
> # Create a XA data source and set min pool size to 1, max pool size to 5
> # Refresh your web browser
> # Go to the data source you created, and update the min to 10, and max to 50. You'll get this error:
> {code}
> Unexpected HTTP response: 500
> Request
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "java:jboss/datasources/myAuth")
> ],
> "operation" => "write-attribute",
> "name" => "min-pool-size",
> "value" => 10
> },
> {
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "java:jboss/datasources/myAuth")
> ],
> "operation" => "write-attribute",
> "name" => "initial-pool-size",
> "value" => undefined
> },
> {
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "java:jboss/datasources/myAuth")
> ],
> "operation" => "write-attribute",
> "name" => "max-pool-size",
> "value" => 50
> }
> ]
> }
> Response
> Internal Server Error
> {
> "outcome" => "failed",
> "result" => {
> "step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> },
> "step-2" => {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0045: failed to set attribute: null",
> "rolled-back" => true
> },
> "step-3" => {
> "outcome" => "failed",
> "rolled-back" => true
> }
> },
> "failure-description" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "WFLYJCA0045: failed to set attribute: null"}},
> "rolled-back" => true
> }
> {code}
> Looks like the web console is trying to write the {{initialPoolSize}} attribute too, even though I haven't touched it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6013) Admin Console: cannot update min and max pool sizes for XA data source
by Chen Maoqian (JIRA)
[ https://issues.jboss.org/browse/WFLY-6013?page=com.atlassian.jira.plugin.... ]
Chen Maoqian resolved WFLY-6013.
--------------------------------
Resolution: Cannot Reproduce
Hello,i just want to reproduce the erro from what your description,but it can not be reproduced in Wildfly 9.0.2.Final and Wildfly 10.0.0.so i suggest you can try it with wildfly 10,and if you can also meet this error,you can tell us !Thanks.
> Admin Console: cannot update min and max pool sizes for XA data source
> ----------------------------------------------------------------------
>
> Key: WFLY-6013
> URL: https://issues.jboss.org/browse/WFLY-6013
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 9.0.2.Final
> Reporter: The Alchemist
> Assignee: Chen Maoqian
> Priority: Minor
>
> h2. How to Reproduce
> # Start Wildfly
> # Create a XA data source and set min pool size to 1, max pool size to 5
> # Refresh your web browser
> # Go to the data source you created, and update the min to 10, and max to 50. You'll get this error:
> {code}
> Unexpected HTTP response: 500
> Request
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "java:jboss/datasources/myAuth")
> ],
> "operation" => "write-attribute",
> "name" => "min-pool-size",
> "value" => 10
> },
> {
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "java:jboss/datasources/myAuth")
> ],
> "operation" => "write-attribute",
> "name" => "initial-pool-size",
> "value" => undefined
> },
> {
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "java:jboss/datasources/myAuth")
> ],
> "operation" => "write-attribute",
> "name" => "max-pool-size",
> "value" => 50
> }
> ]
> }
> Response
> Internal Server Error
> {
> "outcome" => "failed",
> "result" => {
> "step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> },
> "step-2" => {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0045: failed to set attribute: null",
> "rolled-back" => true
> },
> "step-3" => {
> "outcome" => "failed",
> "rolled-back" => true
> }
> },
> "failure-description" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "WFLYJCA0045: failed to set attribute: null"}},
> "rolled-back" => true
> }
> {code}
> Looks like the web console is trying to write the {{initialPoolSize}} attribute too, even though I haven't touched it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6013) Admin Console: cannot update min and max pool sizes for XA data source
by Chen Maoqian (JIRA)
[ https://issues.jboss.org/browse/WFLY-6013?page=com.atlassian.jira.plugin.... ]
Chen Maoqian reassigned WFLY-6013:
----------------------------------
Assignee: Chen Maoqian (was: Heiko Braun)
> Admin Console: cannot update min and max pool sizes for XA data source
> ----------------------------------------------------------------------
>
> Key: WFLY-6013
> URL: https://issues.jboss.org/browse/WFLY-6013
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 9.0.2.Final
> Reporter: The Alchemist
> Assignee: Chen Maoqian
> Priority: Minor
>
> h2. How to Reproduce
> # Start Wildfly
> # Create a XA data source and set min pool size to 1, max pool size to 5
> # Refresh your web browser
> # Go to the data source you created, and update the min to 10, and max to 50. You'll get this error:
> {code}
> Unexpected HTTP response: 500
> Request
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "java:jboss/datasources/myAuth")
> ],
> "operation" => "write-attribute",
> "name" => "min-pool-size",
> "value" => 10
> },
> {
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "java:jboss/datasources/myAuth")
> ],
> "operation" => "write-attribute",
> "name" => "initial-pool-size",
> "value" => undefined
> },
> {
> "address" => [
> ("subsystem" => "datasources"),
> ("xa-data-source" => "java:jboss/datasources/myAuth")
> ],
> "operation" => "write-attribute",
> "name" => "max-pool-size",
> "value" => 50
> }
> ]
> }
> Response
> Internal Server Error
> {
> "outcome" => "failed",
> "result" => {
> "step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> },
> "step-2" => {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0045: failed to set attribute: null",
> "rolled-back" => true
> },
> "step-3" => {
> "outcome" => "failed",
> "rolled-back" => true
> }
> },
> "failure-description" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "WFLYJCA0045: failed to set attribute: null"}},
> "rolled-back" => true
> }
> {code}
> Looks like the web console is trying to write the {{initialPoolSize}} attribute too, even though I haven't touched it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6294) Session draining always takes maximum configured timeout
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-6294?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-6294:
-----------------------------------------------
baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1314792|https://bugzilla.redhat.com/show_bug.cgi?id=1314792] from NEW to MODIFIED
> Session draining always takes maximum configured timeout
> --------------------------------------------------------
>
> Key: WFLY-6294
> URL: https://issues.jboss.org/browse/WFLY-6294
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.Final
> Reporter: Aaron Ogburn
> Assignee: Radoslav Husar
> Priority: Minor
>
> The mod_cluster session drain wait is not ending as expected. mod_cluster adds a session listener to be notified of session destruction. That is fired appropriately, but when the listener is invoked, the infinispan session manager still reports the session as active. Thus, this drain loop doesn't end after the notify because it still sees the active session:
> {code}
> while ((remainingSessions > 0) && (noTimeout || (timeout > 0))) {
> ModClusterLogger.LOGGER.drainSessions(remainingSessions, context.getHost(), context);
> listener.wait(noTimeout ? 0 : timeout);
> current = System.currentTimeMillis();
> timeout = end - current;
> remainingSessions = context.getActiveSessionCount();
> }
> {code}
> Can the listeners be invoked when the session is fully removed and no longer considered active?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6294) Session draining always takes maximum configured timeout
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-6294?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-6294:
-----------------------------------------------
baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1314792|https://bugzilla.redhat.com/show_bug.cgi?id=1314792] from POST to NEW
> Session draining always takes maximum configured timeout
> --------------------------------------------------------
>
> Key: WFLY-6294
> URL: https://issues.jboss.org/browse/WFLY-6294
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.Final
> Reporter: Aaron Ogburn
> Assignee: Radoslav Husar
> Priority: Minor
>
> The mod_cluster session drain wait is not ending as expected. mod_cluster adds a session listener to be notified of session destruction. That is fired appropriately, but when the listener is invoked, the infinispan session manager still reports the session as active. Thus, this drain loop doesn't end after the notify because it still sees the active session:
> {code}
> while ((remainingSessions > 0) && (noTimeout || (timeout > 0))) {
> ModClusterLogger.LOGGER.drainSessions(remainingSessions, context.getHost(), context);
> listener.wait(noTimeout ? 0 : timeout);
> current = System.currentTimeMillis();
> timeout = end - current;
> remainingSessions = context.getActiveSessionCount();
> }
> {code}
> Can the listeners be invoked when the session is fully removed and no longer considered active?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (DROOLS-1117) After 2 times loading the same Rule 3rd time its not loading, Even No error occured
by Vivek Singh (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1117?page=com.atlassian.jira.plugi... ]
Vivek Singh updated DROOLS-1117:
--------------------------------
Summary: After 2 times loading the same Rule 3rd time its not loading, Even No error occured (was: After 2 times loading the same Rule 3rd time its loading, Even No error occured)
> After 2 times loading the same Rule 3rd time its not loading, Even No error occured
> -----------------------------------------------------------------------------------
>
> Key: DROOLS-1117
> URL: https://issues.jboss.org/browse/DROOLS-1117
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.4.0.CR2
> Reporter: Vivek Singh
> Assignee: Edson Tirelli
>
> While Loading the Rules in Server, After that i removed the Rule from KieBase then again
> added the Rule By creating the newJar with different ReleaseId but same Drl filename.
> Then i again removed the rule from KieBase using same command
> kieBase.removeRule(kiePackage.getName(), ruleName);
> But after that when i again added the same Rule it will not adding into the KieBase Knowledge packages. Even i am not getting any error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (DROOLS-1117) After 2 times loading the same Rule 3rd time its loading, Even No error occured
by Vivek Singh (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1117?page=com.atlassian.jira.plugi... ]
Vivek Singh updated DROOLS-1117:
--------------------------------
Component/s: core engine
(was: kie server)
> After 2 times loading the same Rule 3rd time its loading, Even No error occured
> -------------------------------------------------------------------------------
>
> Key: DROOLS-1117
> URL: https://issues.jboss.org/browse/DROOLS-1117
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.4.0.CR2
> Reporter: Vivek Singh
> Assignee: Edson Tirelli
>
> While Loading the Rules in Server, After that i removed the Rule from KieBase then again
> added the Rule By creating the newJar with different ReleaseId but same Drl filename.
> Then i again removed the rule from KieBase using same command
> kieBase.removeRule(kiePackage.getName(), ruleName);
> But after that when i again added the same Rule it will not adding into the KieBase Knowledge packages. Even i am not getting any error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (DROOLS-1116) After adding new Rule by different drl filename getting error while calling fireRules
by Vivek Singh (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1116?page=com.atlassian.jira.plugi... ]
Vivek Singh updated DROOLS-1116:
--------------------------------
Component/s: core engine
(was: kie server)
> After adding new Rule by different drl filename getting error while calling fireRules
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-1116
> URL: https://issues.jboss.org/browse/DROOLS-1116
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.4.0.CR2
> Reporter: Vivek Singh
> Assignee: Edson Tirelli
>
> Issue is similar to https://issues.jboss.org/browse/DROOLS-978
> But its showing its fixed in 6.4.0.Beta1 but i am still lfacing in 6.4.0.CR2
> While Adding the new or Updated Rules by createKieJar.
> Even renaming the Drool file.
> After that while calling the fireRules i am getting the below error:-
> Exception in thread "main" java.lang.NullPointerException
> at org.drools.core.reteoo.NodeTypeEnums.isBetaNode(NodeTypeEnums.java:88)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:254)
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:166)
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:123)
> at org.drools.core.phreak.RuleExecutor.evaluateNetwork(RuleExecutor.java:65)
> at org.drools.core.common.DefaultAgenda.evaluateEagerList(DefaultAgenda.java:1004)
> at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:961)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1292)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1294)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1281)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1260
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month