[Red Hat JIRA] (WFLY-14408) CLI journal-import command fails if in-vm connector has a server-id other than "0"
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-14408?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet updated WFLY-14408:
-------------------------------------
Steps to Reproduce:
Configure a WildFly instance with an in-vm connector and acceptor with a server-id other than "0".
Export messages from the same or other JBoss instance in admin mode.
Attempt to re-import messages into the current instance runing in normal mode via the cli method.
Operation fails as described above.
was:
Configure a JBoss EAP 7 instance with an in-vm connector and acceptor with a server-id other than "0".
Export messages from the same or other JBoss instance in admin mode.
Attempt to re-import messages into the current instance runing in normal mode via the cli method.
Operation fails as described above.
> CLI journal-import command fails if in-vm connector has a server-id other than "0"
> ----------------------------------------------------------------------------------
>
> Key: WFLY-14408
> URL: https://issues.redhat.com/browse/WFLY-14408
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 22.0.0.Final
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Labels: artemis, messaging
>
> If the in-vm-connector / in-vm-acceptor for the default / live messaging-activemq server is configured with a server-id higher than "0":
> {code}
> <in-vm-connector name="in-vm-connector1" server-id="1"/>
> {code}
> then performing an import-journal operation from the cli fails with a rather unhelpful "Cannot connect to server(s)" message:
> {code}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=ServerLive:import-journal(file=/home/jboss/messages.xml) { "outcome" => "failed", "failure-description" => "AMQ219007: Cannot connect to server(s). Tried with all available servers.", "rolled-back" => true }
> {code}
> After much debugging, resetting the server-id to "0" on the live server in-vm acceptor and connector and from "2" to "1" on the backup resolved the issue and the import succeeded.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14408) CLI journal-import command fails if in-vm connector has a server-id other than "0"
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-14408?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet moved JBEAP-20979 to WFLY-14408:
--------------------------------------------------
Component/s: JMS
(was: A-MQ7)
(was: CLI)
Key: WFLY-14408 (was: JBEAP-20979)
Affects Version/s: 22.0.0.Final
(was: 7.3.x)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Project: WildFly (was: JBoss Enterprise Application Platform)
> CLI journal-import command fails if in-vm connector has a server-id other than "0"
> ----------------------------------------------------------------------------------
>
> Key: WFLY-14408
> URL: https://issues.redhat.com/browse/WFLY-14408
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 22.0.0.Final
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Labels: artemis, cli, messaging
>
> If the in-vm-connector / in-vm-acceptor for the default / live messaging-activemq server is configured with a server-id higher than "0":
> {code}
> <in-vm-connector name="in-vm-connector1" server-id="1"/>
> {code}
> then performing an import-journal operation from the cli fails with a rather unhelpful "Cannot connect to server(s)" message:
> {code}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=ServerLive:import-journal(file=/home/jboss/messages.xml) { "outcome" => "failed", "failure-description" => "AMQ219007: Cannot connect to server(s). Tried with all available servers.", "rolled-back" => true }
> {code}
> After much debugging, resetting the server-id to "0" on the live server in-vm acceptor and connector and from "2" to "1" on the backup resolved the issue and the import succeeded.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14407) Upgrade to EE 9 Hibernate Validator 7.0.1.Final
by Scott Marlow (Jira)
Scott Marlow created WFLY-14407:
-----------------------------------
Summary: Upgrade to EE 9 Hibernate Validator 7.0.1.Final
Key: WFLY-14407
URL: https://issues.redhat.com/browse/WFLY-14407
Project: WildFly
Issue Type: Task
Components: Bean Validation
Reporter: Scott Marlow
Assignee: Brian Stansberry
The TCK runner in 7.0.1.Final was updated to work with the WildFly EE 9 build. This jira helps us to automatically use the Hibernate Validator 7.0.1.Final tagged branch in our TCK running job, for running the Bean Validator TCK.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-6006) Constraints with Complex Abbreviated Combined Relations Fail to Compile with Executable Model
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-6006?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-6006:
--------------------------------
Sprint: 2021 Week 04-06 (from Jan 25)
> Constraints with Complex Abbreviated Combined Relations Fail to Compile with Executable Model
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-6006
> URL: https://issues.redhat.com/browse/DROOLS-6006
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.49.0.Final
> Reporter: Matteo Casalino
> Assignee: Mario Fusco
> Priority: Major
> Attachments: complex-abbreviated-combined-relation-with-exec-model.zip
>
>
> Constraints with complex abbreviated combined relations such as:
> {noformat}
> Fact1(x ((>= "340000" && <= "340000")||(>= "370000" && <= "370000")))
> {noformat}
> fail to compile with executable model due to the following {{StackOverflowError}}:
> {noformat}
> java.lang.StackOverflowError
> at java.base/java.util.LinkedList.get(LinkedList.java:481)
> at com.github.javaparser.ast.Node.setParentNode(Node.java:388)
> at com.github.javaparser.ast.Node.setAsParentNodeOf(Node.java:403)
> at com.github.javaparser.ast.expr.BinaryExpr.setLeft(BinaryExpr.java:174)
> at com.github.javaparser.ast.expr.BinaryExpr.<init>(BinaryExpr.java:131)
> at com.github.javaparser.ast.expr.BinaryExpr.<init>(BinaryExpr.java:122)
> at org.drools.modelcompiler.builder.generator.DrlxParseUtil.trasformHalfBinaryToBinary(DrlxParseUtil.java:360)
> at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:208)
> at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:199)
> at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:209)
> at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:199)
> at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:209)
> at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:199)
> at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:209)
> at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:199)
> ...
> {noformat}
> The compilation works fine without executable model.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-6006) Constraints with Complex Abbreviated Combined Relations Fail to Compile with Executable Model
by Matteo Casalino (Jira)
Matteo Casalino created DROOLS-6006:
---------------------------------------
Summary: Constraints with Complex Abbreviated Combined Relations Fail to Compile with Executable Model
Key: DROOLS-6006
URL: https://issues.redhat.com/browse/DROOLS-6006
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.49.0.Final
Reporter: Matteo Casalino
Assignee: Mario Fusco
Attachments: complex-abbreviated-combined-relation-with-exec-model.zip
Constraints with complex abbreviated combined relations such as:
{noformat}
Fact1(x ((>= "340000" && <= "340000")||(>= "370000" && <= "370000")))
{noformat}
fail to compile with executable model due to the following {{StackOverflowError}}:
{noformat}
java.lang.StackOverflowError
at java.base/java.util.LinkedList.get(LinkedList.java:481)
at com.github.javaparser.ast.Node.setParentNode(Node.java:388)
at com.github.javaparser.ast.Node.setAsParentNodeOf(Node.java:403)
at com.github.javaparser.ast.expr.BinaryExpr.setLeft(BinaryExpr.java:174)
at com.github.javaparser.ast.expr.BinaryExpr.<init>(BinaryExpr.java:131)
at com.github.javaparser.ast.expr.BinaryExpr.<init>(BinaryExpr.java:122)
at org.drools.modelcompiler.builder.generator.DrlxParseUtil.trasformHalfBinaryToBinary(DrlxParseUtil.java:360)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:208)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:199)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:209)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:199)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:209)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:199)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:209)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:199)
...
{noformat}
The compilation works fine without executable model.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months