May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10424) Upgrade ActiveMQ Artemis to 1.5.5.jbossorg-012

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10424?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-10424: ------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/11233) > Upgrade ActiveMQ Artemis to 1.5.5.jbossorg-012 > ---------------------------------------------- > > Key: WFLY-10424 > URL: https://issues.jboss.org/browse/WFLY-10424 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Lin Gao > Assignee: Jeff Mesnil > Labels: downstream_dependency > > https://github.com/rh-messaging/jboss-activemq-artemis/compare/1.5.5.jbos... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10424) Upgrade ActiveMQ Artemis to 1.5.5.jbossorg-012

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10424?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-10424: ------------------------------- Description: https://github.com/rh-messaging/jboss-activemq-artemis/compare/1.5.5.jbos... (was: https://github.com/rh-messaging/jboss-activemq-artemis/compare/1.5.5.jbos...) > Upgrade ActiveMQ Artemis to 1.5.5.jbossorg-012 > ---------------------------------------------- > > Key: WFLY-10424 > URL: https://issues.jboss.org/browse/WFLY-10424 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Lin Gao > Assignee: Jeff Mesnil > Labels: downstream_dependency > > https://github.com/rh-messaging/jboss-activemq-artemis/compare/1.5.5.jbos... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10424) Upgrade ActiveMQ Artemis to 1.5.5.jbossorg-012

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-10424: ---------------------------------- Summary: Upgrade ActiveMQ Artemis to 1.5.5.jbossorg-012 Key: WFLY-10424 URL: https://issues.jboss.org/browse/WFLY-10424 Project: WildFly Issue Type: Component Upgrade Components: JMS Reporter: Lin Gao Assignee: Jeff Mesnil Fix For: 13.0.0.Beta1 https://github.com/rh-messaging/jboss-activemq-artemis/compare/1.5.5.jbos... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10424) Upgrade ActiveMQ Artemis to 1.5.5.jbossorg-012

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10424?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-10424: ------------------------------- Fix Version/s: (was: 13.0.0.Beta1) > Upgrade ActiveMQ Artemis to 1.5.5.jbossorg-012 > ---------------------------------------------- > > Key: WFLY-10424 > URL: https://issues.jboss.org/browse/WFLY-10424 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Lin Gao > Assignee: Jeff Mesnil > Labels: downstream_dependency > > https://github.com/rh-messaging/jboss-activemq-artemis/compare/1.5.5.jbos... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2570) DRL function import doesn't work using static inner class

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2570?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2570. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/76b2ecba97c8d35a44417b188e0bc9b... > DRL function import doesn't work using static inner class > --------------------------------------------------------- > > Key: DROOLS-2570 > URL: https://issues.jboss.org/browse/DROOLS-2570 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > Priority: Minor > > When having a test case like this [1], the build ends with errors. See the build output here [2]. To reproduce the issue, just paste the test to ImportsTest test class. > [1] https://gist.github.com/baldimir/6d27b37d157abd87b846e0947b1011cb > [2] https://gist.github.com/baldimir/71809d454cce4e26ad7080b1fa5655a8 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3865) .ps1 scripts Java system vars need to be quoted

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3865?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3865: ------------------------------------------ FWIW, little or none of our CI testing is using our scripts (Windows or otherwise) to launch the java processes. > .ps1 scripts Java system vars need to be quoted > ----------------------------------------------- > > Key: WFCORE-3865 > URL: https://issues.jboss.org/browse/WFCORE-3865 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 5.0.0.Beta4 > Reporter: R Searls > Assignee: R Searls > Priority: Minor > > .ps1 scripts appclient, wsconsume, wsprovide, need java system variables > (e.g., -Djave.home=blabla) to be quoted. Add a new function to common.ps1. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10423) (7.1.z) Regression in Remote JCA scenario with JDBC store after Artemis upgrade

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-10423?page=com.atlassian.jira.plugin... ] Lin Gao reassigned WFLY-10423: ------------------------------ Assignee: Lin Gao (was: Jeff Mesnil) > (7.1.z) Regression in Remote JCA scenario with JDBC store after Artemis upgrade > ------------------------------------------------------------------------------- > > Key: WFLY-10423 > URL: https://issues.jboss.org/browse/WFLY-10423 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Critical > Fix For: 7.1.3.GA > > > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10423) (7.1.z) Regression in Remote JCA scenario with JDBC store after Artemis upgrade

by Lin Gao (JIRA)

Lin Gao created WFLY-10423: ------------------------------ Summary: (7.1.z) Regression in Remote JCA scenario with JDBC store after Artemis upgrade Key: WFLY-10423 URL: https://issues.jboss.org/browse/WFLY-10423 Project: WildFly Issue Type: Bug Components: JMS Reporter: Lin Gao 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3870) Management Port sharing port 8080

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3870?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved WFLY-1099 to WFCORE-3870: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-3870 (was: WFLY-1099) Component/s: Management (was: Management) > Management Port sharing port 8080 > --------------------------------- > > Key: WFCORE-3870 > URL: https://issues.jboss.org/browse/WFCORE-3870 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Jim Tyrrell > Assignee: Darran Lofthouse > Labels: eap6-ux > > While it is great and there are many good reason to have a management console on a different port then the standard 8080 web ports, it should be possible to use port 8080 or equivalent for a management console and another port needing to be open should not be required, but can be a selectable feature. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3870) Management Port sharing port 8080

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3870?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-3870: ---------------------------------------- Assignee: (was: Darran Lofthouse) > Management Port sharing port 8080 > --------------------------------- > > Key: WFCORE-3870 > URL: https://issues.jboss.org/browse/WFCORE-3870 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Jim Tyrrell > Labels: eap6-ux > > While it is great and there are many good reason to have a management console on a different port then the standard 8080 web ports, it should be possible to use port 8080 or equivalent for a management console and another port needing to be open should not be required, but can be a selectable feature. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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