May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10392) Regression in Remote JCA scenario with JDBC store after Artemis upgrade

by Francesco Nigro (JIRA)

[ https://issues.jboss.org/browse/WFLY-10392?page=com.atlassian.jira.plugin... ] Francesco Nigro edited comment on WFLY-10392 at 5/17/18 11:23 AM: ------------------------------------------------------------------ [~eduda] I will take a look to the logs too! Yes already done (now): you can use the same branch I've posted above (y) Please could you share here the commit of the version that is working (without the JDBC HA porting)? Looking at the logs I have spotted other 2 commits: # a change done on [ARTEMIS-1757 Improve DB2 compatibility|https://github.com/franz1981/activemq-artemis/commit/17502f...] # a [change|https://github.com/franz1981/activemq-artemis/commit/3ee566c07a532...] on ActiveMQScheduledComponent::initialDelay The first seems to appear while stopping the SQL driver while the second one could affect the JDBCJournal periodic sync process that would start before having the tables created. was (Author: fnigro): [~eduda] I will take a look to the logs too! Yes already done (now): you can use the same branch I've posted above (y) Please could you share here the commit of the version that is working (without the JDBC HA porting)? Looking at the logs I have spotted other 2 commits: # a change done on [ARTEMIS-1757 Improve DB2 compatibility|https://github.com/franz1981/activemq-artemis/commit/17502f...] # a [change|https://github.com/franz1981/activemq-artemis/commit/3ee566c07a532...] on ActiveMQScheduledComponent::initialDelay The first seems to compare while stopping the SQL driver while the second one could affect the JDBCJournal periodic sync process that would start before having the tables created. > Regression in Remote JCA scenario with JDBC store after Artemis upgrade > ----------------------------------------------------------------------- > > Key: WFLY-10392 > URL: https://issues.jboss.org/browse/WFLY-10392 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Critical > > After Artemis upgrade to 1.5.5.jbossorg-011 (WFLY-10139) I can see a regression in Remote JCA test case when JDBC persistent store is used. This issue is not present if Artemis file based journal is used. > When I removed commits related to JDBC HA from Artemis upgrade, the test passed with both JDBC and file based store. > *Remote JCA scenario:* > * There are 4 Wildfly servers > * Servers 1 and 3 are used as messaging brokers - they are called JMS servers > * Servers 2 and 4 have MDBs and RA configured to connect to JMS servers. These servers are called MDB servers. > * External standalone producer sends messages to server 1 to InQueue > * MDBs on MBD severs receive messages from InQueue and send them to OutQueue > * External standalone receiver receives messages from server 3 from OutQueue > * During this scenario server 1 is several times killed and restarted. > *Expectation:* All messages sent by the standalone producer are received by the standalone receiver. There are no lost or duplicated messages. > *Reality:* After some kills of server 1, message flow coming from the standalone producer is broken and the receiver does not receive any messages in specified timeout. > *Critical* priority was chosen because the regression has been detected only in this particular test case so far. We ran only nightly testing scope. After that we run full testing, we will know more about impact of this issue. > *Technical details:* > At some point following log messages start to occur in the test log. It seems that they are related to malfunction of communication among Artemis brokers what causes that message flow is broken. > {code} > 21:55:51,724 WARN [org.apache.activemq.artemis.core.server] (Thread-1 (ActiveMQ-client-global-threads)) AMQ222139: MessageFlowRecordImpl [nodeID=e53da514-5953-11e8-910a-fa163e48a89a, connector=TransportConfigur > ation(name=connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=10080&host=rhel7-la > rge-58597, queueName=sf.my-cluster.e53da514-5953-11e8-910a-fa163e48a89a, queue=QueueImpl[name=sf.my-cluster.e53da514-5953-11e8-910a-fa163e48a89a, postOffice=PostOfficeImpl [server=ActiveMQServerImpl::serverUUID= > d80bf5bd-5953-11e8-ac10-fa163e48a89a]]@756a727a, isClosed=false, reset=true]::Remote queue binding jms.queue.DLQe53da514-5953-11e8-910a-fa163e48a89a has already been bound in the post office. Most likely cause f > or this is you have a loop in your cluster due to cluster max-hops being too large or you have multiple cluster connections to the same nodes using overlapping addresses > {code} > {code} > 21:55:53,078 ERROR [org.apache.activemq.artemis.core.server] (Thread-6 (ActiveMQ-client-global-threads)) AMQ224037: cluster connection Failed to handle message: java.lang.IllegalStateException: Cannot find binding for jms.queue.InQueuee53da514-5953-11e8-910a-fa163e48a89a on ClusterConnectionImpl@14989488[nodeUUID=d80bf5bd-5953-11e8-ac10-fa163e48a89a, connector=TransportConfiguration(name=connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=8080&host=rhel7-large-58597, address=jms, server=ActiveMQServerImpl::serverUUID=d80bf5bd-5953-11e8-ac10-fa163e48a89a] > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.doConsumerCreated(ClusterConnectionImpl.java:1294) [artemis-server-1.5.5.jbossorg-011.jar:1.5.5.jbossorg-011] > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.handleNotificationMessage(ClusterConnectionImpl.java:1029) [artemis-server-1.5.5.jbossorg-011.jar:1.5.5.jbossorg-011] > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.onMessage(ClusterConnectionImpl.java:1004) [artemis-server-1.5.5.jbossorg-011.jar:1.5.5.jbossorg-011] > at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1001) [artemis-core-client-1.5.5.jbossorg-011.jar:1.5.5.jbossorg-011] > at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:49) [artemis-core-client-1.5.5.jbossorg-011.jar:1.5.5.jbossorg-011] > at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1124) [artemis-core-client-1.5.5.jbossorg-011.jar:1.5.5.jbossorg-011] > at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122) [artemis-commons-1.5.5.jbossorg-011.jar:1.5.5.jbossorg-011] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_171] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_171] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171] > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2536) Executable model - incremental compilation tests fail with the model

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2536?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2536: ------------------------------------- Fix for from on global https://github.com/kiegroup/drools/commit/dd51c2511faa99f32241acf7ccaa998... > Executable model - incremental compilation tests fail with the model > -------------------------------------------------------------------- > > Key: DROOLS-2536 > URL: https://issues.jboss.org/browse/DROOLS-2536 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > > When running incremental compilation tests [1] with the executable model, there are various failures. To run the tests, uncomment the model runs [2][3][4][5][6]. > [1] https://github.com/kiegroup/drools/tree/master/drools-test-coverage/test-... > [2] https://github.com/kiegroup/drools/blob/master/drools-test-coverage/test-... > [3] https://github.com/kiegroup/drools/blob/master/drools-test-coverage/test-... > [4] https://github.com/kiegroup/drools/blob/master/drools-test-coverage/test-... > [5] https://github.com/kiegroup/drools/blob/master/drools-test-coverage/test-... > [6] https://github.com/kiegroup/drools/blob/master/drools-test-coverage/test-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3861) Fix POM name of wildfly-core-testsuite-embedded

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3861?page=com.atlassian.jira.plugi... ] David Lloyd moved ELY-1585 to WFCORE-3861: ------------------------------------------ Project: WildFly Core (was: WildFly Elytron) Key: WFCORE-3861 (was: ELY-1585) Component/s: Test Suite (was: Testsuite) > Fix POM name of wildfly-core-testsuite-embedded > ----------------------------------------------- > > Key: WFCORE-3861 > URL: https://issues.jboss.org/browse/WFCORE-3861 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Trivial > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1585) Fix POM name of wildfly-core-testsuite-embedded

by David Lloyd (JIRA)

David Lloyd created ELY-1585: -------------------------------- Summary: Fix POM name of wildfly-core-testsuite-embedded Key: ELY-1585 URL: https://issues.jboss.org/browse/ELY-1585 Project: WildFly Elytron Issue Type: Task Components: Testsuite Reporter: David Lloyd Assignee: David Lloyd Priority: Trivial -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2558) Improve error message for Msg.EXPRESSION_IS_RANGE_BUT_VALUE_IS_NOT_COMPARABLE

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-2558: -------------------------------------- Summary: Improve error message for Msg.EXPRESSION_IS_RANGE_BUT_VALUE_IS_NOT_COMPARABLE Key: DROOLS-2558 URL: https://issues.jboss.org/browse/DROOLS-2558 Project: Drools Issue Type: Enhancement Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari When the following expression is evaluated: {code:java} duration(\"PT24H\") in[ duration(\"P1Y2M\") .. duration(\"P1Y3M\")] {code} it is generating: {code:java} Value 'PT24H' is not comparable with range '[ org.kie.dmn.feel.lang.ast.RangeNode$ComparablePeriod@e .. org.kie.dmn.feel.lang.ast.RangeNode$ComparablePeriod@f ]' {code} while it is desired: {code:java} Value 'PT24H' is not comparable with range '[ duration( "P1Y2M" ) .. duration( "P1Y3M" ) ]' {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-229) Make Jenkins Job Parameters consistent

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-229: ---------------------------------- Summary: Make Jenkins Job Parameters consistent Key: SWSQE-229 URL: https://issues.jboss.org/browse/SWSQE-229 Project: Kiali QE Issue Type: Task Reporter: Matt Mahoney Assignee: Michael Foley Priority: Minor Currently the Job parameters are inconsistent from one job to another, thus make consistent across all jobs. Ex: Some jobs use Kiali Hostname while others use Kiali URL Some jobs use OS Hostname while others use OS URL etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1584) Add ability to log security manager violates to out-of-band log file

by David Lloyd (JIRA)

David Lloyd created ELY-1584: -------------------------------- Summary: Add ability to log security manager violates to out-of-band log file Key: ELY-1584 URL: https://issues.jboss.org/browse/ELY-1584 Project: WildFly Elytron Issue Type: Enhancement Components: Security Manager Reporter: David Lloyd It would be useful for CI if we could set a system property which would log security manager permission check violations (and the details thereof) to a log file, outside of the standard log infrastructure. This would potentially allow us to fail CI when unexpected "hidden" permission violations occur by way of a post-build script analyzes the log output. This might also be useful for troubleshooting more obscure security manager related problems. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1584) Add ability to log security manager violations to out-of-band log file

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1584?page=com.atlassian.jira.plugin.s... ] David Lloyd updated ELY-1584: ----------------------------- Summary: Add ability to log security manager violations to out-of-band log file (was: Add ability to log security manager violates to out-of-band log file) > Add ability to log security manager violations to out-of-band log file > ---------------------------------------------------------------------- > > Key: ELY-1584 > URL: https://issues.jboss.org/browse/ELY-1584 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Security Manager > Reporter: David Lloyd > > It would be useful for CI if we could set a system property which would log security manager permission check violations (and the details thereof) to a log file, outside of the standard log infrastructure. This would potentially allow us to fail CI when unexpected "hidden" permission violations occur by way of a post-build script analyzes the log output. > This might also be useful for troubleshooting more obscure security manager related problems. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10380) ThreadPoolExecutor leak under SM due to lack of privileged block

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10380?page=com.atlassian.jira.plugin... ] Jeff Mesnil commented on WFLY-10380: ------------------------------------ [~clebertsuconic] fiy, there might be a need to ensure that *all* ThreadPoolExecutor instantiated by Artemis are done in a priviledged block. Do you want me to create an ARTEMIS issue for it? > ThreadPoolExecutor leak under SM due to lack of privileged block > ---------------------------------------------------------------- > > Key: WFLY-10380 > URL: https://issues.jboss.org/browse/WFLY-10380 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: David Lloyd > Priority: Critical > > Still researching the source of these leaks. > The way the leak happens is, a {{java.util.concurrent.ThreadPoolExecutor}} is constructed from an unprivileged context. The pool starts up and threads are created without a problem, however, the thread pool is never shut down. The finalizer runs but since it tries to shut down the pool with an access control context that was captured during construction, it fails because the context did not have the {{modifyThread}} {{RuntimePermission}}, and the thread pool never shuts down. > We need to identify the points where TPEs are being constructed without controlled privileges. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2556) Not possible to deploy kjar with rule including timer

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2556?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-2556: ------------------------------------- Assignee: Mario Fusco (was: Edson Tirelli) > Not possible to deploy kjar with rule including timer > ----------------------------------------------------- > > Key: DROOLS-2556 > URL: https://issues.jboss.org/browse/DROOLS-2556 > Project: Drools > Issue Type: Bug > Affects Versions: 7.7.0.Final > Reporter: Anton Giertli > Assignee: Mario Fusco > Attachments: kjar.zip, reproducer.zip > > > When KJAR contains a rule with timer: > {code:java} > package com.sample; > > rule "Timer to stop long running rules" > timer (int: 150s) > ruleflow-group "whatever" > salience 99 > when > then > System.err.println("**** Exit rule engine ****"); > drools.halt(); > end > {code} > It's not possible to deploy it with KIE Services API > it fails with this error: > https://gist.github.com/agiertli/12fb71e3103dbf493308dc263fdc4607 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2018