April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5225) Constraint grouping fails with executable model

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5225?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-5225. --------------------------------- Resolution: Won't Fix As clarified in the former comment removing the unnecessary parenthesis fixes the problem. Making it work also with those additional parenthesis will unnecessary complicate (and slow down) the parser, so we agreed to avoid this. > Constraint grouping fails with executable model > ----------------------------------------------- > > Key: DROOLS-5225 > URL: https://issues.redhat.com/browse/DROOLS-5225 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.35.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: constraints-grouping.zip > > > Executable model rule compilation fails when trying to build a pattern using constraint grouping. > Example of DRL that fails to compile: > {noformat} > rule "TestBusiness" > when $p : Pojo(departuretimedayofweek (== 1 || == 2 || == 7) ) > then > end > {noformat} > Error: > {noformat} > java.lang.StackOverflowError > at java.base/java.util.LinkedList.unlink(LinkedList.java:215) > at java.base/java.util.LinkedList.remove(LinkedList.java:530) > at com.github.javaparser.ast.Node.setParentNode(Node.java:389) > 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:347) > at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:194) > at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:185) > at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:195) > at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:185) > ... > {noformat} > The example works fine when compiling without executable model. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4748) Expose the ability to add jboss-modules specific arguments

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-4748?page=com.atlassian.jira.plug... ] James Perkins reopened WFCORE-4748: ----------------------------------- > Expose the ability to add jboss-modules specific arguments > ---------------------------------------------------------- > > Key: WFCORE-4748 > URL: https://issues.redhat.com/browse/WFCORE-4748 > Project: WildFly Core > Issue Type: Feature Request > Components: Launcher, Scripts > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Currently the scripts have an environment variable {{MODULE_OPTS}} which is used to enable the security manager for JBoss Modules. This variable is not currently allowed to be set yet in the {{*.conf}} files however we could expose it. The need for this comes from WFCORE-4674 where the fix will be to add JBoss Modules as an agent, then add {{-javaagent:some-agent.jar}} to the arguments for JBoss Modules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4908) The write-attribute operation does not work on a hosts JVM resource

by James Perkins (Jira)

James Perkins created WFCORE-4908: ------------------------------------- Summary: The write-attribute operation does not work on a hosts JVM resource Key: WFCORE-4908 URL: https://issues.redhat.com/browse/WFCORE-4908 Project: WildFly Core Issue Type: Bug Components: Server Reporter: James Perkins Assignee: Jeff Mesnil Under a hosts server config, {{/host=master/server-config=server-one/}}, there is a {{jvm}} resource. On this resource the {{write-attribute}} operation does not work expected. {code} [domain@embedded /] /host=master/server-config=server-one/jvm=default:add { "outcome" => "success", "result" => undefined, "server-groups" => undefined } [domain@embedded /] /host=master/server-config=server-one/jvm=default:write-attribute(name=jvm-options["-Xlog:gc*:file=${jboss.domain.servers.dir}/server-two/log/gc.log"]) { "outcome" => "success", "result" => undefined, "server-groups" => undefined } [domain@embedded /] /host=master/server-config=server-one/jvm=default:read-resource { "outcome" => "success", "result" => { "agent-lib" => undefined, "agent-path" => undefined, "debug-enabled" => undefined, "debug-options" => undefined, "env-classpath-ignored" => undefined, "environment-variables" => undefined, "heap-size" => undefined, "java-agent" => undefined, "java-home" => undefined, "jvm-options" => undefined, "launch-command" => undefined, "max-heap-size" => undefined, "max-permgen-size" => undefined, "permgen-size" => undefined, "stack-size" => undefined, "type" => undefined } } {code} As you can see from the above command does not update the {{jvm-options}}. However if you use the {{add-jvm-option}} operation that does work. It seems the {{write-attribute}} operation should also work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1407) Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/JBJCA-1407?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on JBJCA-1407: ----------------------------------------- https://github.com/ironjacamar/ironjacamar/pull/703 is a likely fix > Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown > --------------------------------------------------------------------------------------------------- > > Key: JBJCA-1407 > URL: https://issues.redhat.com/browse/JBJCA-1407 > Project: IronJacamar > Issue Type: Bug > Reporter: Chao Wang > Assignee: Flavia Rainone > Priority: Critical > > By upgrading IJ to 1.4.21. Final https://issues.redhat.com/browse/WFLY-1324 > There is a constant error in server shutdown > {code:xml} > 12:12:44,713 ERROR [stderr] (ConnectionValidator) Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException > 12:12:44,714 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:151) > 12:12:44,714 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1261) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:457) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at org.jboss.jca.core.connectionmanager.pool.validator.ConnectionValidator$ConnectionValidatorRunner.run(ConnectionValidator.java:317) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1407) Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/JBJCA-1407?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-13344 to JBJCA-1407: ------------------------------------------------ Project: IronJacamar (was: WildFly) Key: JBJCA-1407 (was: WFLY-13344) Workflow: classic default workflow (was: GIT Pull Request workflow ) Component/s: (was: JCA) Fix Version/s: (was: 20.0.0.Beta1) > Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown > --------------------------------------------------------------------------------------------------- > > Key: JBJCA-1407 > URL: https://issues.redhat.com/browse/JBJCA-1407 > Project: IronJacamar > Issue Type: Bug > Reporter: Chao Wang > Assignee: Flavia Rainone > Priority: Critical > > By upgrading IJ to 1.4.21. Final https://issues.redhat.com/browse/WFLY-1324 > There is a constant error in server shutdown > {code:xml} > 12:12:44,713 ERROR [stderr] (ConnectionValidator) Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException > 12:12:44,714 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:151) > 12:12:44,714 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1261) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:457) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at org.jboss.jca.core.connectionmanager.pool.validator.ConnectionValidator$ConnectionValidatorRunner.run(ConnectionValidator.java:317) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13344) Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13344: --------------------------------------- Summary: Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown Key: WFLY-13344 URL: https://issues.redhat.com/browse/WFLY-13344 Project: WildFly Issue Type: Bug Components: JCA Reporter: Chao Wang Assignee: Flavia Rainone Fix For: 20.0.0.Beta1 By upgrading IJ to 1.4.21. Final https://issues.redhat.com/browse/WFLY-1324 There is a constant error in server shutdown {code:xml} 12:12:44,713 ERROR [stderr] (ConnectionValidator) Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException 12:12:44,714 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:151) 12:12:44,714 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1261) 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:457) 12:12:44,715 ERROR [stderr] (ConnectionValidator) at org.jboss.jca.core.connectionmanager.pool.validator.ConnectionValidator$ConnectionValidatorRunner.run(ConnectionValidator.java:317) 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.lang.Thread.run(Thread.java:748) {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13340) Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13340?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13340: ------------------------------------ Fix Version/s: 20.0.0.Beta1 > Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown > --------------------------------------------------------------------------------------------------- > > Key: WFLY-13340 > URL: https://issues.redhat.com/browse/WFLY-13340 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Chao Wang > Assignee: Flavia Rainone > Priority: Critical > Fix For: 20.0.0.Beta1 > > > By upgrading IJ to 1.4.21. Final https://issues.redhat.com/browse/WFLY-1324 > There is a constant error in server shutdown > {code:xml} > 12:12:44,713 ERROR [stderr] (ConnectionValidator) Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException > 12:12:44,714 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:151) > 12:12:44,714 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1261) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:457) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at org.jboss.jca.core.connectionmanager.pool.validator.ConnectionValidator$ConnectionValidatorRunner.run(ConnectionValidator.java:317) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4907) Expose the ability to add jboss-modules specific arguments

by James Perkins (Jira)

James Perkins created WFCORE-4907: ------------------------------------- Summary: Expose the ability to add jboss-modules specific arguments Key: WFCORE-4907 URL: https://issues.redhat.com/browse/WFCORE-4907 Project: WildFly Core Issue Type: Enhancement Components: Launcher, Scripts Reporter: James Perkins Assignee: James Perkins Currently the scripts have an environment variable {{MODULE_OPTS}} which is used to enable the security manager for JBoss Modules. This variable is not currently allowed to be set yet in the {{*.conf}} files however we could expose it. The need for this comes from WFCORE-4674 where the fix will be to add JBoss Modules as an agent, then add {{-javaagent:some-agent.jar}} to the arguments for JBoss Modules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4748) Expose the ability to add jboss-modules specific arguments

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-4748?page=com.atlassian.jira.plug... ] James Perkins updated WFCORE-4748: ---------------------------------- Issue Type: Feature Request (was: Enhancement) > Expose the ability to add jboss-modules specific arguments > ---------------------------------------------------------- > > Key: WFCORE-4748 > URL: https://issues.redhat.com/browse/WFCORE-4748 > Project: WildFly Core > Issue Type: Feature Request > Components: Launcher, Scripts > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Currently the scripts have an environment variable {{MODULE_OPTS}} which is used to enable the security manager for JBoss Modules. This variable is not currently allowed to be set yet in the {{*.conf}} files however we could expose it. The need for this comes from WFCORE-4674 where the fix will be to add JBoss Modules as an agent, then add {{-javaagent:some-agent.jar}} to the arguments for JBoss Modules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13343) Guard against lookup of local user transaction using EJBClient

by Stephen Fikes (Jira)

Stephen Fikes created WFLY-13343: ------------------------------------ Summary: Guard against lookup of local user transaction using EJBClient Key: WFLY-13343 URL: https://issues.redhat.com/browse/WFLY-13343 Project: WildFly Issue Type: Feature Request Components: EJB, Transactions Affects Versions: 19.0.0.Final, 18.0.1.Final Reporter: Stephen Fikes Assignee: Cheng Fang A local UserTransaction instance obtained via EJBClient (which is meant solely for remote access) is non-functional and any use of it will fail subsequently. The lookup attempt should fail immediately with an unambiguous exception to make it clear this is a usage error as the subsequent behavior may be much more difficult to diagnose. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2020