[JBoss JIRA] (DROOLS-1223) java.lang.NullPointerException druing Condition Evaluation
by Rodrigo Doria Medina (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1223?page=com.atlassian.jira.plugi... ]
Rodrigo Doria Medina updated DROOLS-1223:
-----------------------------------------
Description:
# Caused by: java.lang.NullPointerException
# at ConditionEvaluator2afa7f52e3ae42c98bf357b4d12bd2f2.evaluate(Unknown Source)
# at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:258)
# at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:214)
# at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:146)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
# at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
# at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
# at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
# at org.drools.core.reteoo.ObjectTypeNode.modifyObject(ObjectTypeNode.java:359)
# at org.drools.core.reteoo.EntryPointNode.propagateModify(EntryPointNode.java:249)
# at org.drools.core.phreak.PropagationEntry$Update.execute(PropagationEntry.java:150)
# at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:78)
# at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:68)
# at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:2011)
# at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:128)
# at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74)
# at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1007)
# at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1350)
# at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1288)
# at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1306)
# at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1297)
# at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1278)
This happens when running more than once the same piece of data. (It happens from the second time).
I have no clue what could that be. When running the first time everything computes as expected.
Thanks!
was:
All,
I have this issue,
#
# Caused by: java.lang.NullPointerException
# at ConditionEvaluator2afa7f52e3ae42c98bf357b4d12bd2f2.evaluate(Unknown Source)
# at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:258)
# at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:214)
# at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:146)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
# at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
# at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
# at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
# at org.drools.core.reteoo.ObjectTypeNode.modifyObject(ObjectTypeNode.java:359)
# at org.drools.core.reteoo.EntryPointNode.propagateModify(EntryPointNode.java:249)
# at org.drools.core.phreak.PropagationEntry$Update.execute(PropagationEntry.java:150)
# at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:78)
# at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:68)
# at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:2011)
# at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:128)
# at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74)
# at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1007)
# at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1350)
# at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1288)
# at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1306)
# at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1297)
# at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1278)
When running more than once the same piece of data. (It happens from the second time).
I have no clue what could that be. When running the first time everything computes as expected.
Thanks!
> java.lang.NullPointerException druing Condition Evaluation
> ----------------------------------------------------------
>
> Key: DROOLS-1223
> URL: https://issues.jboss.org/browse/DROOLS-1223
> Project: Drools
> Issue Type: Bug
> Reporter: Rodrigo Doria Medina
> Assignee: Mark Proctor
>
> # Caused by: java.lang.NullPointerException
> # at ConditionEvaluator2afa7f52e3ae42c98bf357b4d12bd2f2.evaluate(Unknown Source)
> # at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:258)
> # at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:214)
> # at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:146)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
> # at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
> # at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
> # at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
> # at org.drools.core.reteoo.ObjectTypeNode.modifyObject(ObjectTypeNode.java:359)
> # at org.drools.core.reteoo.EntryPointNode.propagateModify(EntryPointNode.java:249)
> # at org.drools.core.phreak.PropagationEntry$Update.execute(PropagationEntry.java:150)
> # at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:78)
> # at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:68)
> # at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:2011)
> # at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:128)
> # at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74)
> # at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1007)
> # at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1350)
> # at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1288)
> # at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1306)
> # at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1297)
> # at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1278)
> This happens when running more than once the same piece of data. (It happens from the second time).
> I have no clue what could that be. When running the first time everything computes as expected.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (DROOLS-1223) java.lang.NullPointerException druing Condition Evaluation
by Rodrigo Doria Medina (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1223?page=com.atlassian.jira.plugi... ]
Rodrigo Doria Medina updated DROOLS-1223:
-----------------------------------------
Description:
All,
I have this issue,
#
# Caused by: java.lang.NullPointerException
# at ConditionEvaluator2afa7f52e3ae42c98bf357b4d12bd2f2.evaluate(Unknown Source)
# at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:258)
# at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:214)
# at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:146)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
# at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
# at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
# at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
# at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
# at org.drools.core.reteoo.ObjectTypeNode.modifyObject(ObjectTypeNode.java:359)
# at org.drools.core.reteoo.EntryPointNode.propagateModify(EntryPointNode.java:249)
# at org.drools.core.phreak.PropagationEntry$Update.execute(PropagationEntry.java:150)
# at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:78)
# at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:68)
# at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:2011)
# at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:128)
# at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74)
# at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1007)
# at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1350)
# at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1288)
# at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1306)
# at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1297)
# at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1278)
When running more than once the same piece of data. (It happens from the second time).
I have no clue what could that be. When running the first time everything computes as expected.
Thanks!
was:
All,
I have this issue,
Caused by: java.lang.NullPointerException
at ConditionEvaluator2afa7f52e3ae42c98bf357b4d12bd2f2.evaluate(Unknown Source)
at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:258)
at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:214)
at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:146)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
at org.drools.core.reteoo.ObjectTypeNode.modifyObject(ObjectTypeNode.java:359)
at org.drools.core.reteoo.EntryPointNode.propagateModify(EntryPointNode.java:249)
at org.drools.core.phreak.PropagationEntry$Update.execute(PropagationEntry.java:150)
at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:78)
at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:68)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:2011)
at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:128)
at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74)
at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1007)
at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1350)
at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1288)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1306)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1297)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1278)
When running more than once the same piece of data. (It happens from the second time).
I have no clue what could that be. When running the first time everything computes as expected.
Thanks!
> java.lang.NullPointerException druing Condition Evaluation
> ----------------------------------------------------------
>
> Key: DROOLS-1223
> URL: https://issues.jboss.org/browse/DROOLS-1223
> Project: Drools
> Issue Type: Bug
> Reporter: Rodrigo Doria Medina
> Assignee: Mark Proctor
>
> All,
> I have this issue,
> #
> # Caused by: java.lang.NullPointerException
> # at ConditionEvaluator2afa7f52e3ae42c98bf357b4d12bd2f2.evaluate(Unknown Source)
> # at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:258)
> # at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:214)
> # at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:146)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
> # at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
> # at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
> # at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
> # at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
> # at org.drools.core.reteoo.ObjectTypeNode.modifyObject(ObjectTypeNode.java:359)
> # at org.drools.core.reteoo.EntryPointNode.propagateModify(EntryPointNode.java:249)
> # at org.drools.core.phreak.PropagationEntry$Update.execute(PropagationEntry.java:150)
> # at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:78)
> # at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:68)
> # at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:2011)
> # at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:128)
> # at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74)
> # at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1007)
> # at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1350)
> # at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1288)
> # at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1306)
> # at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1297)
> # at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1278)
> When running more than once the same piece of data. (It happens from the second time).
> I have no clue what could that be. When running the first time everything computes as expected.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (DROOLS-1223) java.lang.NullPointerException druing Condition Evaluation
by Rodrigo Doria Medina (JIRA)
Rodrigo Doria Medina created DROOLS-1223:
--------------------------------------------
Summary: java.lang.NullPointerException druing Condition Evaluation
Key: DROOLS-1223
URL: https://issues.jboss.org/browse/DROOLS-1223
Project: Drools
Issue Type: Bug
Reporter: Rodrigo Doria Medina
Assignee: Mark Proctor
All,
I have this issue,
Caused by: java.lang.NullPointerException
at ConditionEvaluator2afa7f52e3ae42c98bf357b4d12bd2f2.evaluate(Unknown Source)
at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:258)
at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:214)
at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:146)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
at org.drools.core.reteoo.AlphaNode.modifyObject(AlphaNode.java:147)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:504)
at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:434)
at org.drools.core.reteoo.ObjectTypeNode.modifyObject(ObjectTypeNode.java:359)
at org.drools.core.reteoo.EntryPointNode.propagateModify(EntryPointNode.java:249)
at org.drools.core.phreak.PropagationEntry$Update.execute(PropagationEntry.java:150)
at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:78)
at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:68)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:2011)
at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:128)
at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74)
at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1007)
at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1350)
at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1288)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1306)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1297)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1278)
When running more than once the same piece of data. (It happens from the second time).
I have no clue what could that be. When running the first time everything computes as expected.
Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (WFLY-6781) Wildfly cluster's failover functionality doesn't work as expected
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla edited comment on WFLY-6781 at 7/4/16 2:14 PM:
----------------------------------------------------------------
As per your suggestion,
I have tried setting <connection-ttl>60000</connection-ttl> in configuration of RemoteConnectionFactory.
When I do this, even without doing any failover testing , the SL(JMS) is not able to process any request. The status of these request is "processing" for ever.
It might mean that connection has timed out before processing with this setting. Also would like to remind you that the failover by power off method works properly on Linux. Only its got issues (probably JMS related) on Windows OS.
Thanks,
Preeta
was (Author: kpreeta12):
As per your suggestion,
I have tried setting <connection-ttl>60000</connection-ttl> in configuration of RemoteConnectionFactory.
When I do this, even without doing any failover testing , the SL(JMS) is not able to process any request. The status of these request is "processing" for ever.
It might mean that connection has timed out before processing with this setting.
Thanks,
Preeta
> Wildfly cluster's failover functionality doesn't work as expected
> -----------------------------------------------------------------
>
> Key: WFLY-6781
> URL: https://issues.jboss.org/browse/WFLY-6781
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 8.2.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: domain.Node1.xml, host.Node1.xml, host.Node2.xml, server.RC.Node1.AfterFailover.log, server.RC.Node1.BeforeFailover.log, server.RC.Node2.AfterFailover.log, server.RC.Node2.BeforeFailover.log, server.SL.Node1.AfterFailover.log, server.SL.Node1.BeforeFailover.log
>
>
> Following are the testing scenarios we did and the outcome:-
> 1. Network disabling on a VM for testing failover – Not working for both Linux and Windows environment.
> 2. Power off of a VM using VMware client for testing failover – Is working on Linux environment but not working on windows environment.
> 3. Ctrl + C method to stop services on a node for testing failover – works on both linux and windows environment
> 4. Stopping server running on Node /VM using Admin Console for testing failover - works on both linux and windows environment.
> Jgroups subsystem configuration in domain.xml we have is below:-
> <subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="udp">
> <stack name="udp">
> <transport type="UDP" socket-binding="jgroups-udp"/>
> <protocol type="PING"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <protocol type="MPING" socket-binding="jgroups-mping"/>
> <protocol type="MERGE2"/>
> <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
> <protocol type="FD"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (WFLY-6781) Wildfly cluster's failover functionality doesn't work as expected
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla commented on WFLY-6781:
----------------------------------------
As per your suggestion,
I have tried setting <connection-ttl>60000</connection-ttl> in configuration of RemoteConnectionFactory.
When I do this, even without doing any failover testing , the SL(JMS) is not able to process any request. The status of these request is "processing" for ever.
It might mean that connection has timed out before processing with this setting.
Thanks,
Preeta
> Wildfly cluster's failover functionality doesn't work as expected
> -----------------------------------------------------------------
>
> Key: WFLY-6781
> URL: https://issues.jboss.org/browse/WFLY-6781
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 8.2.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: domain.Node1.xml, host.Node1.xml, host.Node2.xml, server.RC.Node1.AfterFailover.log, server.RC.Node1.BeforeFailover.log, server.RC.Node2.AfterFailover.log, server.RC.Node2.BeforeFailover.log, server.SL.Node1.AfterFailover.log, server.SL.Node1.BeforeFailover.log
>
>
> Following are the testing scenarios we did and the outcome:-
> 1. Network disabling on a VM for testing failover – Not working for both Linux and Windows environment.
> 2. Power off of a VM using VMware client for testing failover – Is working on Linux environment but not working on windows environment.
> 3. Ctrl + C method to stop services on a node for testing failover – works on both linux and windows environment
> 4. Stopping server running on Node /VM using Admin Console for testing failover - works on both linux and windows environment.
> Jgroups subsystem configuration in domain.xml we have is below:-
> <subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="udp">
> <stack name="udp">
> <transport type="UDP" socket-binding="jgroups-udp"/>
> <protocol type="PING"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <protocol type="MPING" socket-binding="jgroups-mping"/>
> <protocol type="MERGE2"/>
> <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
> <protocol type="FD"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="RSVP"/>
> </stack>
> </subsystem>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (WFLY-6797) Is there a way to have more than one logging subystem belonging to one profile
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-6797?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla closed WFLY-6797.
----------------------------------
Resolution: Won't Fix
> Is there a way to have more than one logging subystem belonging to one profile
> ------------------------------------------------------------------------------
>
> Key: WFLY-6797
> URL: https://issues.jboss.org/browse/WFLY-6797
> Project: WildFly
> Issue Type: Task
> Components: Domain Management
> Affects Versions: 8.2.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Brian Stansberry
>
> I have "ha" profile in my domain.xml which has many subsystems.
> Below is the structure I have:-
> {color:#205081}<server-groups>
> <server-group name="main-server-group" profile="ha">
> <socket-binding-group ref="ha-sockets"/>
> <deployments>
> <deployment name="RC.war" runtime-name="RC.war"/>
> </deployments>
> </server-group>
> <server-group name="other-server-group" profile="ha">
> <socket-binding-group ref="standard-sockets"/>
> <deployments>
> <deployment name="SL.war" runtime-name="SL.war"/>
> </deployments>
> </server-group>
> </server-groups>{color}
> There is a logging subsystem which needs to be different for RC.war and SL.war. Both RC.war and SL.war belong to same profile.
>
> Is there a way to have 2 logging related subsystems defined in "ha" profile, such that RC can point to one and SL to the other although they belong to same profile?
> Example:-
> RC.war needs to use the below:-
> {color:#205081}<subsystem xmlns="urn:jboss:domain:logging:2.0">
> <console-handler name="CONSOLE">
> <level name="INFO"/>
> <formatter>
> <named-formatter name="COLOR-PATTERN"/>
> </formatter>
> </console-handler>
> <logger category="com.arjuna">
> <level name="WARN"/>
> </logger>
> <logger category="org.apache.tomcat.util.modeler">
> <level name="WARN"/>
> </logger>
> <logger category="org.jboss.as.config">
> <level name="DEBUG"/>
> </logger>
> <logger category="sun.rmi">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb.config">
> <level name="ERROR"/>
> </logger>
> <root-logger>
> <level name="INFO"/>
> <handlers>
> <handler name="CONSOLE"/>
> <handler name="FILE"/>
> </handlers>
> </root-logger>
> <formatter name="PATTERN">
> <pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <formatter name="COLOR-PATTERN">
> <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> </subsystem>
> {color}
> while SL.war needs to use the below:-
> {color:#205081}<subsystem xmlns="urn:jboss:domain:logging:2.0">
> <console-handler name="CONSOLE">
> <level name="INFO"/>
> <formatter>
> <named-formatter name="COLOR-PATTERN"/>
> </formatter>
> </console-handler>
> <periodic-rotating-file-handler name="ISEE">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="isee.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="FILE_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="fileadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="DB_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="dbadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="MQ_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="mqadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="JMS_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="jmsadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="HTTP_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="httpadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="VMWARE_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="vmwareadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="WSLISTENER_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="wslisteneradapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="SERVICEITEMLISTENER_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="serviceitemlisteneradapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="VSOC_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="vsocadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="CLOUD_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="cloudadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <logger category="com.arjuna">
> <level name="WARN"/>
> </logger>
> <logger category="org.apache.tomcat.util.modeler">
> <level name="WARN"/>
> </logger>
> <logger category="org.jboss.as.config">
> <level name="DEBUG"/>
> </logger>
> <logger category="sun.rmi">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb.config">
> <level name="ERROR"/>
> </logger>
> <root-logger>
> <level name="INFO"/>
> <handlers>
> <handler name="CONSOLE"/>
> <handler name="FILE"/>
> </handlers>
> </root-logger>
> <formatter name="PATTERN">
> <pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <formatter name="COLOR-PATTERN">
> <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> </subsystem>{color}
> Thanks,
> Preeta
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (WFLY-6797) Is there a way to have more than one logging subystem belonging to one profile
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-6797?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla commented on WFLY-6797:
----------------------------------------
I have fixed the issue by creating 2 different profiles.
I read about logging-profiles and per-deployment logging. However these didn't work for me. Hence created 2 different profiles. Each profile had many similar subsystems.
> Is there a way to have more than one logging subystem belonging to one profile
> ------------------------------------------------------------------------------
>
> Key: WFLY-6797
> URL: https://issues.jboss.org/browse/WFLY-6797
> Project: WildFly
> Issue Type: Task
> Components: Domain Management
> Affects Versions: 8.2.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Brian Stansberry
>
> I have "ha" profile in my domain.xml which has many subsystems.
> Below is the structure I have:-
> {color:#205081}<server-groups>
> <server-group name="main-server-group" profile="ha">
> <socket-binding-group ref="ha-sockets"/>
> <deployments>
> <deployment name="RC.war" runtime-name="RC.war"/>
> </deployments>
> </server-group>
> <server-group name="other-server-group" profile="ha">
> <socket-binding-group ref="standard-sockets"/>
> <deployments>
> <deployment name="SL.war" runtime-name="SL.war"/>
> </deployments>
> </server-group>
> </server-groups>{color}
> There is a logging subsystem which needs to be different for RC.war and SL.war. Both RC.war and SL.war belong to same profile.
>
> Is there a way to have 2 logging related subsystems defined in "ha" profile, such that RC can point to one and SL to the other although they belong to same profile?
> Example:-
> RC.war needs to use the below:-
> {color:#205081}<subsystem xmlns="urn:jboss:domain:logging:2.0">
> <console-handler name="CONSOLE">
> <level name="INFO"/>
> <formatter>
> <named-formatter name="COLOR-PATTERN"/>
> </formatter>
> </console-handler>
> <logger category="com.arjuna">
> <level name="WARN"/>
> </logger>
> <logger category="org.apache.tomcat.util.modeler">
> <level name="WARN"/>
> </logger>
> <logger category="org.jboss.as.config">
> <level name="DEBUG"/>
> </logger>
> <logger category="sun.rmi">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb.config">
> <level name="ERROR"/>
> </logger>
> <root-logger>
> <level name="INFO"/>
> <handlers>
> <handler name="CONSOLE"/>
> <handler name="FILE"/>
> </handlers>
> </root-logger>
> <formatter name="PATTERN">
> <pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <formatter name="COLOR-PATTERN">
> <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> </subsystem>
> {color}
> while SL.war needs to use the below:-
> {color:#205081}<subsystem xmlns="urn:jboss:domain:logging:2.0">
> <console-handler name="CONSOLE">
> <level name="INFO"/>
> <formatter>
> <named-formatter name="COLOR-PATTERN"/>
> </formatter>
> </console-handler>
> <periodic-rotating-file-handler name="ISEE">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="isee.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="FILE_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="fileadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="DB_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="dbadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="MQ_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="mqadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="JMS_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="jmsadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="HTTP_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="httpadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="VMWARE_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="vmwareadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="WSLISTENER_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="wslisteneradapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="SERVICEITEMLISTENER_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="serviceitemlisteneradapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="VSOC_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="vsocadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="CLOUD_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="cloudadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <logger category="com.arjuna">
> <level name="WARN"/>
> </logger>
> <logger category="org.apache.tomcat.util.modeler">
> <level name="WARN"/>
> </logger>
> <logger category="org.jboss.as.config">
> <level name="DEBUG"/>
> </logger>
> <logger category="sun.rmi">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb.config">
> <level name="ERROR"/>
> </logger>
> <root-logger>
> <level name="INFO"/>
> <handlers>
> <handler name="CONSOLE"/>
> <handler name="FILE"/>
> </handlers>
> </root-logger>
> <formatter name="PATTERN">
> <pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <formatter name="COLOR-PATTERN">
> <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> </subsystem>{color}
> Thanks,
> Preeta
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JGRP-2070) Add flag back to disable individual thread pools
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2070?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-2070.
----------------------------
Resolution: Done
> Add flag back to disable individual thread pools
> ------------------------------------------------
>
> Key: JGRP-2070
> URL: https://issues.jboss.org/browse/JGRP-2070
> Project: JGroups
> Issue Type: Task
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.0
>
>
> In 4.0, {{xxx_thread_pool.enbled}} was removed. The idea was that this could be done programmatically by using {{TP.setOOBThreadPool()}} using a {{DirectExecutor}}.
> However, sometimes it is convenient to do this declaratively, in the XML config file, e.g. if the code cannot be changed or the channel cannot be retrieved.
> Therefore add the attribute(s) to disable/enable thread pools back.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (WFCORE-1634) Wrong cursor position after deleting all characters in second line
by Tomas Hofman (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1634?page=com.atlassian.jira.plugi... ]
Tomas Hofman updated WFCORE-1634:
---------------------------------
Description:
In CLI, when typing expression that stretches more then one line, and then deleting all characters in the last line (using backspace), cursor appears on wrong position on the previous line (should be on last column, but is on column before the last).
Further editing messes up the displayed expression, which doesn't reflect the real content of the buffer.
Example:
* Terminal width is 80 characters.
* [] marks a cursor position.
Step 1. - I have expression spreading over two lines like this:
{code}
[standalone@embedded /] /subsystem=datasources/data-source=ExampleDS/connection-
factory[]
{code}
Step 2. - Delete "factory" word using backspace:
{code}
[standalone@embedded /] /subsystem=datasources/data-source=ExampleDS/connection-
[]
{code}
Step 3. - Another backspace:
{code}
[standalone@embedded /] /subsystem=datasources/data-source=ExampleDS/connectio[n]
{code}
while expected is:
{code}
[standalone@embedded /] /subsystem=datasources/data-source=ExampleDS/connection[]
{code}
was:
In CLI, when typing expression that stretches more then one line, and then deleting all characters in the last line (using backspace), cursor appears on wrong position on the previous line (should be on last row, but is on row before the last).
Further editing messes up the displayed expression, which doesn't reflect the real content of the buffer.
Example:
* Terminal width is 80 characters.
* [] marks a cursor position.
Step 1. - I have expression spreading over two lines like this:
{code}
[standalone@embedded /] /subsystem=datasources/data-source=ExampleDS/connection-
factory[]
{code}
Step 2. - Delete "factory" word using backspace:
{code}
[standalone@embedded /] /subsystem=datasources/data-source=ExampleDS/connection-
[]
{code}
Step 3. - Another backspace:
{code}
[standalone@embedded /] /subsystem=datasources/data-source=ExampleDS/connectio[n]
{code}
while expected is:
{code}
[standalone@embedded /] /subsystem=datasources/data-source=ExampleDS/connection[]
{code}
> Wrong cursor position after deleting all characters in second line
> ------------------------------------------------------------------
>
> Key: WFCORE-1634
> URL: https://issues.jboss.org/browse/WFCORE-1634
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0.Alpha3
> Environment: Fedora 24
> Gnome Terminal 3.20
> Bash 4.3.42
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
>
> In CLI, when typing expression that stretches more then one line, and then deleting all characters in the last line (using backspace), cursor appears on wrong position on the previous line (should be on last column, but is on column before the last).
> Further editing messes up the displayed expression, which doesn't reflect the real content of the buffer.
> Example:
> * Terminal width is 80 characters.
> * [] marks a cursor position.
> Step 1. - I have expression spreading over two lines like this:
> {code}
> [standalone@embedded /] /subsystem=datasources/data-source=ExampleDS/connection-
> factory[]
> {code}
> Step 2. - Delete "factory" word using backspace:
> {code}
> [standalone@embedded /] /subsystem=datasources/data-source=ExampleDS/connection-
> []
> {code}
> Step 3. - Another backspace:
> {code}
> [standalone@embedded /] /subsystem=datasources/data-source=ExampleDS/connectio[n]
> {code}
> while expected is:
> {code}
> [standalone@embedded /] /subsystem=datasources/data-source=ExampleDS/connection[]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months