[JBoss JIRA] (WFLY-12140) Set bridgeName while creating JMSBridge on server
by Shailendra Singh (Jira)
[ https://issues.jboss.org/browse/WFLY-12140?page=com.atlassian.jira.plugin... ]
Shailendra Singh commented on WFLY-12140:
-----------------------------------------
Possible fix :- https://github.com/wildfly/wildfly/pull/12329
> Set bridgeName while creating JMSBridge on server
> -------------------------------------------------
>
> Key: WFLY-12140
> URL: https://issues.jboss.org/browse/WFLY-12140
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 17.0.0.Beta1
> Reporter: Shailendra Singh
> Assignee: Emmanuel Hugonnet
> Priority: Minor
>
> Set bridgeName while creating JMSBridge on server
> When JMS bridge get reconnected after network issue the logs contains the default bridgeName i.e "N/A"
> {code:java}
> 14:07:56,933 WARN [org.apache.activemq.artemis.jms.bridge] (Thread-109) AMQ342010: Failed to connect JMS Bridge N/A: javax.jms.JMSException: Failed to create session factory
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:846)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:282)
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.createConnection(JMSBridgeImpl.java:1120)
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1286)
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.setupJMSObjectsWithRetry(JMSBridgeImpl.java:1392)
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.access$2800(JMSBridgeImpl.java:77)
> at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl$FailureHandler.run(JMSBridgeImpl.java:1902)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007: Cannot connect to server(s). Tried with all available servers.]
> at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:795)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:844)
> ... 9 more
> {code}
> And reconenct message.
> {code:java}
> 14:07:57,834 INFO [org.apache.activemq.artemis.jms.bridge] (Thread-109) AMQ341001: JMS Bridge N/A succeeded in reconnecting to servers
> {code}
> bridgeName will be helpful to find the bridge having the issue in multi JMS Bridge scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4089) EvaluatedExpression not well resolved with JIT during race
by vincent palau (Jira)
[ https://issues.jboss.org/browse/DROOLS-4089?page=com.atlassian.jira.plugi... ]
vincent palau updated DROOLS-4089:
----------------------------------
Description:
We recently moved from Drools 7.9.0 to 7.20.
Some errors started appearing in ours tests when calling static methods in LHS drools.
This started happening when all tests were run simultaneously.
It seems the mvel JIT compiler kicks in and it incorrectly evaluates the property name:
A simple call to {noformat}ValidationUtils.isNullOrEmpty(interestedPartyNumber){noformat} ends up with this kind of error:
{noformat}
"java.lang.RuntimeException: Unknown property 'nullOrEmpty' on class tech.stage.utils.cwr.model.PublisherRecord"
{noformat}
Debugging info:
Related source-code: https://github.com/kiegroup/drools/blob/7.20.0.Final/drools-core/src/main...
!debugging-1.png|full!
1) is the current evaluated property
2) Should be the right property of WriterRecord
3) Perhaps the expression which should be executed instead of invocations.get(0)
We fixed that somehow disabling JIT with {noformat}ConstraintJittingThresholdOption{noformat}
Is there any chance to this bug fixed?
Do you need more info?
Thanks in advance for your support.
{panel:title=Reproducer}
https://github.com/vp-stage/evaluatedexpressionandjit
{panel}
was:
We recently moved from Drools 7.9.0 to 7.20.
Some errors started appearing in ours tests when calling static methods in LHS drools.
This started happening when all tests were run simultaneously.
It seems the mvel JIT compiler kicks in and it incorrectly evaluates the property name:
A simple call to {noformat}ValidationUtils.isNullOrEmpty(interestedPartyNumber){noformat} ends up with this kind of error:
{noformat}
"java.lang.RuntimeException: Unknown property 'nullOrEmpty' on class tech.stage.utils.cwr.model.PublisherRecord"
{noformat}
Debugging info:
Related source-code: https://github.com/kiegroup/drools/blob/7.20.0.Final/drools-core/src/main...
!debugging-1.png|full!
1) is the current evaluated property
2) Should be the right property of WriterRecord
3) Perhaps the expression which should be executed instead of invocations.get(0)
We fixed that somehow disabling JIT with {noformat}ConstraintJittingThresholdOption{noformat}
Is there any chance to this bug fixed?
Do you need more info?
Thanks in advance for your support.
> EvaluatedExpression not well resolved with JIT during race
> ------------------------------------------------------------
>
> Key: DROOLS-4089
> URL: https://issues.jboss.org/browse/DROOLS-4089
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.20.0.Final
> Reporter: vincent palau
> Assignee: Mario Fusco
> Priority: Major
> Attachments: debugging-1.png
>
>
> We recently moved from Drools 7.9.0 to 7.20.
> Some errors started appearing in ours tests when calling static methods in LHS drools.
> This started happening when all tests were run simultaneously.
> It seems the mvel JIT compiler kicks in and it incorrectly evaluates the property name:
> A simple call to {noformat}ValidationUtils.isNullOrEmpty(interestedPartyNumber){noformat} ends up with this kind of error:
> {noformat}
> "java.lang.RuntimeException: Unknown property 'nullOrEmpty' on class tech.stage.utils.cwr.model.PublisherRecord"
> {noformat}
> Debugging info:
> Related source-code: https://github.com/kiegroup/drools/blob/7.20.0.Final/drools-core/src/main...
> !debugging-1.png|full!
> 1) is the current evaluated property
> 2) Should be the right property of WriterRecord
> 3) Perhaps the expression which should be executed instead of invocations.get(0)
> We fixed that somehow disabling JIT with {noformat}ConstraintJittingThresholdOption{noformat}
> Is there any chance to this bug fixed?
> Do you need more info?
> Thanks in advance for your support.
> {panel:title=Reproducer}
> https://github.com/vp-stage/evaluatedexpressionandjit
> {panel}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-12140) Set bridgeName while creating JMSBridge on server
by Shailendra Singh (Jira)
Shailendra Singh created WFLY-12140:
---------------------------------------
Summary: Set bridgeName while creating JMSBridge on server
Key: WFLY-12140
URL: https://issues.jboss.org/browse/WFLY-12140
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 17.0.0.Beta1
Reporter: Shailendra Singh
Assignee: Emmanuel Hugonnet
Set bridgeName while creating JMSBridge on server
When JMS bridge get reconnected after network issue the logs contains the default bridgeName i.e "N/A"
{code:java}
14:07:56,933 WARN [org.apache.activemq.artemis.jms.bridge] (Thread-109) AMQ342010: Failed to connect JMS Bridge N/A: javax.jms.JMSException: Failed to create session factory
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:846)
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:282)
at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.createConnection(JMSBridgeImpl.java:1120)
at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1286)
at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.setupJMSObjectsWithRetry(JMSBridgeImpl.java:1392)
at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl.access$2800(JMSBridgeImpl.java:77)
at org.apache.activemq.artemis.jms.bridge.impl.JMSBridgeImpl$FailureHandler.run(JMSBridgeImpl.java:1902)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007: Cannot connect to server(s). Tried with all available servers.]
at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:795)
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:844)
... 9 more
{code}
And reconenct message.
{code:java}
14:07:57,834 INFO [org.apache.activemq.artemis.jms.bridge] (Thread-109) AMQ341001: JMS Bridge N/A succeeded in reconnecting to servers
{code}
bridgeName will be helpful to find the bridge having the issue in multi JMS Bridge scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4046) Scenario Is Executed even if non existing RuleFlowGroup is set
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4046?page=com.atlassian.jira.plugi... ]
Jozef Marko reopened DROOLS-4046:
---------------------------------
> Scenario Is Executed even if non existing RuleFlowGroup is set
> --------------------------------------------------------------
>
> Key: DROOLS-4046
> URL: https://issues.jboss.org/browse/DROOLS-4046
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.22.0.Final
> Reporter: Jozef Marko
> Assignee: Daniele Zonca
> Priority: Major
> Labels: ScenarioSimulation
> Attachments: Screenshot from 2019-05-17 14-46-11.png, rules.zip
>
>
> The test scenario run pass, even if non existing RuleFlowGroup is set. In the attached project there is single rule and scenario. the has not the RuleFlowGroup set, while scenario has - a non existing one. If you run the scenario, it will pass regardless of the RuleFlowGroup set inside.
> Expected: Scenario run fail if non-existing RuleFlowGroup is set in the attached project/scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4046) Scenario Is Executed even if non existing RuleFlowGroup is set
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4046?page=com.atlassian.jira.plugi... ]
Jozef Marko closed DROOLS-4046.
-------------------------------
Resolution: Explained
> Scenario Is Executed even if non existing RuleFlowGroup is set
> --------------------------------------------------------------
>
> Key: DROOLS-4046
> URL: https://issues.jboss.org/browse/DROOLS-4046
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.22.0.Final
> Reporter: Jozef Marko
> Assignee: Daniele Zonca
> Priority: Major
> Labels: ScenarioSimulation
> Attachments: Screenshot from 2019-05-17 14-46-11.png, rules.zip
>
>
> The test scenario run pass, even if non existing RuleFlowGroup is set. In the attached project there is single rule and scenario. the has not the RuleFlowGroup set, while scenario has - a non existing one. If you run the scenario, it will pass regardless of the RuleFlowGroup set inside.
> Expected: Scenario run fail if non-existing RuleFlowGroup is set in the attached project/scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4046) Scenario Is Executed even if non existing RuleFlowGroup is set
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-4046?page=com.atlassian.jira.plugi... ]
Daniele Zonca closed DROOLS-4046.
---------------------------------
Resolution: Done
> Scenario Is Executed even if non existing RuleFlowGroup is set
> --------------------------------------------------------------
>
> Key: DROOLS-4046
> URL: https://issues.jboss.org/browse/DROOLS-4046
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.22.0.Final
> Reporter: Jozef Marko
> Assignee: Daniele Zonca
> Priority: Major
> Labels: ScenarioSimulation
> Attachments: Screenshot from 2019-05-17 14-46-11.png, rules.zip
>
>
> The test scenario run pass, even if non existing RuleFlowGroup is set. In the attached project there is single rule and scenario. the has not the RuleFlowGroup set, while scenario has - a non existing one. If you run the scenario, it will pass regardless of the RuleFlowGroup set inside.
> Expected: Scenario run fail if non-existing RuleFlowGroup is set in the attached project/scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4046) Scenario Is Executed even if non existing RuleFlowGroup is set
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-4046?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-4046:
-------------------------------------
I confirm that if you select a not existing agenda-group it is simply ignored. Thinking twice I'm not sure this is the right behavior and I agree that it could be misleading. I'm open to discuss and eventually change this, but this is how it works now (and always worked).
> Scenario Is Executed even if non existing RuleFlowGroup is set
> --------------------------------------------------------------
>
> Key: DROOLS-4046
> URL: https://issues.jboss.org/browse/DROOLS-4046
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.22.0.Final
> Reporter: Jozef Marko
> Assignee: Daniele Zonca
> Priority: Major
> Labels: ScenarioSimulation
> Attachments: Screenshot from 2019-05-17 14-46-11.png, rules.zip
>
>
> The test scenario run pass, even if non existing RuleFlowGroup is set. In the attached project there is single rule and scenario. the has not the RuleFlowGroup set, while scenario has - a non existing one. If you run the scenario, it will pass regardless of the RuleFlowGroup set inside.
> Expected: Scenario run fail if non-existing RuleFlowGroup is set in the attached project/scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFCORE-4440) Changes made via CLI in static-discovery are not reflected in host.xml
by Teresa Miyar Gil (Jira)
[ https://issues.jboss.org/browse/WFCORE-4440?page=com.atlassian.jira.plugi... ]
Teresa Miyar Gil reassigned WFCORE-4440:
----------------------------------------
Assignee: Teresa Miyar Gil (was: Jeff Mesnil)
> Changes made via CLI in static-discovery are not reflected in host.xml
> ----------------------------------------------------------------------
>
> Key: WFCORE-4440
> URL: https://issues.jboss.org/browse/WFCORE-4440
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 8.0.0.Final, 9.0.0.Beta3
> Reporter: Brian Stansberry
> Assignee: Teresa Miyar Gil
> Priority: Major
>
> The value from this operation is not persisted in the host xml file, nor is it reflected in a read-resource response:
> /host=slave/core-service=discovery-options/static-discovery=primary:write-attribute(name=port,value=9999)
> It also doesn't put the HC in reload-required state.
> This works:
> /host=slave/core-service=discovery-options:write-attribute(name=options,value=[{static-discovery={name=primary,protocol="${jboss.domain.master.protocol:remote+http}",host="${jboss.domain.master.address}",port=9999}}]
> The /host=slave/core-service=discovery-options/static-discovery=* resources are meant to be a kind of alias for elements in that 'options' list to make it easier to manipulate the details. But that linkage has a bug. (Probably several.)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4091) Validate all XSD only locally
by Marek Novotny (Jira)
Marek Novotny created DROOLS-4091:
-------------------------------------
Summary: Validate all XSD only locally
Key: DROOLS-4091
URL: https://issues.jboss.org/browse/DROOLS-4091
Project: Drools
Issue Type: Bug
Reporter: Marek Novotny
Assignee: Luca Molteni
There is still online validation of XSD. With later switching from http to https some of services referenced in code this showed up as a real problem.
We should bundle all schemas in drools jars and validate them only from that location.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month