August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10716) Readme files point to the wrong Guide but some of the information is included in Getting Started Guide

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10716?page=com.atlassian.jira.plugin... ] Sande Gilda commented on WFLY-10716: ------------------------------------ Content can be verified here: https://github.com/jboss-developer/jboss-developer-shared-resources/blob/... > Readme files point to the wrong Guide but some of the information is included in Getting Started Guide > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-10716 > URL: https://issues.jboss.org/browse/WFLY-10716 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sultan Zhantemirov > Assignee: Sande Gilda > Fix For: 14.0.0.CR1 > > > Section "Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse" has a link to [Use JBoss Developer Studio or Eclipse to Run the Quickstarts|https://github.com/jboss-developer/jboss-developer-shared-res...]. > But there is no information about importing a quickstart at content provided by this link. This information is available in other [document|https://doc-stage.usersys.redhat.com/documentation/en-us/jboss_e...] only. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-12) [Artemis upgrade] Output of CLI operations in messaging subsystem's server changed from 7.1

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFWIP-12?page=com.atlassian.jira.plugin.s... ] Jeff Mesnil commented on WFWIP-12: ---------------------------------- [~martyn-taylor] I have a commit in my branch (https://github.com/jmesnil/wildfly/commit/a964ae16dfe8f095df202908f403c8c...) with commented code that needs to be uncommented once there is a version of Artemis with the fix. I tested it locally with upstream snapshots and it is working fine. However we should keep this issue open as a reminder that the fix will not be complete until the subsystem code is also uncommented. > [Artemis upgrade] Output of CLI operations in messaging subsystem's server changed from 7.1 > ------------------------------------------------------------------------------------------- > > Key: WFWIP-12 > URL: https://issues.jboss.org/browse/WFWIP-12 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis, JMS > Reporter: Martin Styk > Assignee: Jeff Mesnil > Priority: Blocker > Labels: activemq, feature-branch-blocker > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Output of CLI operations in messaging subsystem's server element changed and it is is missing some attributes it used to display in EAP 7.1. > _Affected operations_ > *list-all-consumers-as-json* and *list-consumers-as-json* > Missing attributes > * destinationName > * destinationType > * durable > {noformat:title="7.1.0.GA"} > Result list-all-consumers-as-json{"outcome" => "success","result" => "[{\"consumerID\":0,\"connectionID\":\"-733935378\",\"sessionID\":\"fede1b60-04e9-11e8-9641-cc3d825a3be2\",\"queueName\":\"testSubscriberClientId-hornetqCliOperations.testSubscriber-hqServerCliOperations\",\"browseOnly\":false,\"creationTime\":1517226368495,\"destinationName\":\"testTopic\",\"destinationType\":\"topic\",\"durable\":true}]"} > {noformat} > {noformat:title="Wildfly latest with artemis 2.x"} > Result list-all-consumers-as-json{"outcome" => "success","result" => "[{\"consumerID\":0,\"connectionID\":\"784f1287\",\"sessionID\":\"f146b48e-04e3-11e8-bb50-cc3d825a3be2\",\"queueName\":\"jms.queue.testQueue\",\"browseOnly\":false,\"creationTime\":1517223768695,\"deliveringCount\":8}]"} > {noformat} > *list-connections-as-json* > Missing attributes > * clientID > {noformat:title="7.1.0.GA"} > "result" => "[{\"connectionID\":\"1343044951\",\"clientAddress\":\"/127.0.0.1:57038\",\"creationTime\":1517303830995,\"clientID\":\"testSubscriberClientId-hornetqCliOperations\"},{\"connectionID\":\"2052915500\",\"clientAddress\":\"/127.0.0.1:57040\",\"creationTime\":1517303831216},{\"connectionID\":\"668896556\",\"clientAddress\":\"/127.0.0.1:57042\",\"creationTime\":1517303831210},{\"connectionID\":\"2096792561\",\"clientAddress\":\"/127.0.0.1:57044\",\"creationTime\":1517303831223,\"clientID\":\"testPublisherClientId\"}]" > {noformat} > {noformat:title="Wildfly latest with artemis 2.x"} > "result" => "[{\"connectionID\":\"a8842f44\",\"clientAddress\":\"/127.0.0.1:55938\",\"creationTime\":1517298838294,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2},{\"connectionID\":\"c515bc06\",\"clientAddress\":\"/127.0.0.1:55936\",\"creationTime\":1517298837454,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":0},{\"connectionID\":\"b9a9153f-0592-11e8-80ff-54ee7547c83e\",\"clientAddress\":\"invm:0\",\"creationTime\":1517298837312,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":0},{\"connectionID\":\"fe42578a\",\"clientAddress\":\"/127.0.0.1:55944\",\"creationTime\":1517298838495,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2},{\"connectionID\":\"cde89186\",\"clientAddress\":\"/127.0.0.1:55940\",\"creationTime\":1517298838493,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2},{\"connectionID\":\"480099e7\",\"clientAddress\":\"/127.0.0.1:55942\",\"creationTime\":1517298838495,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2}]" > {noformat} > This is compatibility issue, as some scripts may depend on missing attributes. Customer's tooling which used to work with 7.1 may not work now. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-12) [Artemis upgrade] Output of CLI operations in messaging subsystem's server changed from 7.1

by Martyn Taylor (JIRA)

[ https://issues.jboss.org/browse/WFWIP-12?page=com.atlassian.jira.plugin.s... ] Martyn Taylor commented on WFWIP-12: ------------------------------------ [~jmesnil] We're using snapshot builds right now. What do you need to test this, FYI we are carrying a patch to build against 2.7.0-SNAPSHOT on your WF branch in order to do this. > [Artemis upgrade] Output of CLI operations in messaging subsystem's server changed from 7.1 > ------------------------------------------------------------------------------------------- > > Key: WFWIP-12 > URL: https://issues.jboss.org/browse/WFWIP-12 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis, JMS > Reporter: Martin Styk > Assignee: Jeff Mesnil > Priority: Blocker > Labels: activemq, feature-branch-blocker > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Output of CLI operations in messaging subsystem's server element changed and it is is missing some attributes it used to display in EAP 7.1. > _Affected operations_ > *list-all-consumers-as-json* and *list-consumers-as-json* > Missing attributes > * destinationName > * destinationType > * durable > {noformat:title="7.1.0.GA"} > Result list-all-consumers-as-json{"outcome" => "success","result" => "[{\"consumerID\":0,\"connectionID\":\"-733935378\",\"sessionID\":\"fede1b60-04e9-11e8-9641-cc3d825a3be2\",\"queueName\":\"testSubscriberClientId-hornetqCliOperations.testSubscriber-hqServerCliOperations\",\"browseOnly\":false,\"creationTime\":1517226368495,\"destinationName\":\"testTopic\",\"destinationType\":\"topic\",\"durable\":true}]"} > {noformat} > {noformat:title="Wildfly latest with artemis 2.x"} > Result list-all-consumers-as-json{"outcome" => "success","result" => "[{\"consumerID\":0,\"connectionID\":\"784f1287\",\"sessionID\":\"f146b48e-04e3-11e8-bb50-cc3d825a3be2\",\"queueName\":\"jms.queue.testQueue\",\"browseOnly\":false,\"creationTime\":1517223768695,\"deliveringCount\":8}]"} > {noformat} > *list-connections-as-json* > Missing attributes > * clientID > {noformat:title="7.1.0.GA"} > "result" => "[{\"connectionID\":\"1343044951\",\"clientAddress\":\"/127.0.0.1:57038\",\"creationTime\":1517303830995,\"clientID\":\"testSubscriberClientId-hornetqCliOperations\"},{\"connectionID\":\"2052915500\",\"clientAddress\":\"/127.0.0.1:57040\",\"creationTime\":1517303831216},{\"connectionID\":\"668896556\",\"clientAddress\":\"/127.0.0.1:57042\",\"creationTime\":1517303831210},{\"connectionID\":\"2096792561\",\"clientAddress\":\"/127.0.0.1:57044\",\"creationTime\":1517303831223,\"clientID\":\"testPublisherClientId\"}]" > {noformat} > {noformat:title="Wildfly latest with artemis 2.x"} > "result" => "[{\"connectionID\":\"a8842f44\",\"clientAddress\":\"/127.0.0.1:55938\",\"creationTime\":1517298838294,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2},{\"connectionID\":\"c515bc06\",\"clientAddress\":\"/127.0.0.1:55936\",\"creationTime\":1517298837454,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":0},{\"connectionID\":\"b9a9153f-0592-11e8-80ff-54ee7547c83e\",\"clientAddress\":\"invm:0\",\"creationTime\":1517298837312,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":0},{\"connectionID\":\"fe42578a\",\"clientAddress\":\"/127.0.0.1:55944\",\"creationTime\":1517298838495,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2},{\"connectionID\":\"cde89186\",\"clientAddress\":\"/127.0.0.1:55940\",\"creationTime\":1517298838493,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2},{\"connectionID\":\"480099e7\",\"clientAddress\":\"/127.0.0.1:55942\",\"creationTime\":1517298838495,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2}]" > {noformat} > This is compatibility issue, as some scripts may depend on missing attributes. Customer's tooling which used to work with 7.1 may not work now. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-87) [Artemis 2.x upgrade] Transaction remained in prepared state after failover of MDB

by Justin Bertram (JIRA)

[ https://issues.jboss.org/browse/WFWIP-87?page=com.atlassian.jira.plugin.s... ] Justin Bertram reassigned WFWIP-87: ----------------------------------- Assignee: Justin Bertram (was: Martyn Taylor) > [Artemis 2.x upgrade] Transaction remained in prepared state after failover of MDB > ---------------------------------------------------------------------------------- > > Key: WFWIP-87 > URL: https://issues.jboss.org/browse/WFWIP-87 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Justin Bertram > Priority: Blocker > > There is regression in test scenario where MDB failovers from live to backup. Live is cleanly shutdown. > Problem is that after MDB failovers to backup then there is still transaction in prepared state which survive periodic recovery cycles. > Link to build: > https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2880) Show all top level custom Data Types in the dialog, instead of only the selected one

by Guilherme Carreiro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2880?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-2880: --------------------------------------- Story Points: 2 (was: 3) > Show all top level custom Data Types in the dialog, instead of only the selected one > ------------------------------------------------------------------------------------ > > Key: DROOLS-2880 > URL: https://issues.jboss.org/browse/DROOLS-2880 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Labels: drools-tools > > Show all top level custom Data Types in the dialog, instead of only the selected one. Even when the user does not have any ItemDefinition, the dialog must lunch. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10716) Readme files point to the wrong Guide but some of the information is included in Getting Started Guide

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10716?page=com.atlassian.jira.plugin... ] Sande Gilda commented on WFLY-10716: ------------------------------------ [~emmartins]: I'll take this one. > Readme files point to the wrong Guide but some of the information is included in Getting Started Guide > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-10716 > URL: https://issues.jboss.org/browse/WFLY-10716 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sultan Zhantemirov > Assignee: Eduardo Martins > > Section "Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse" has a link to [Use JBoss Developer Studio or Eclipse to Run the Quickstarts|https://github.com/jboss-developer/jboss-developer-shared-res...]. > But there is no information about importing a quickstart at content provided by this link. This information is available in other [document|https://doc-stage.usersys.redhat.com/documentation/en-us/jboss_e...] only. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10716) Readme files point to the wrong Guide but some of the information is included in Getting Started Guide

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10716?page=com.atlassian.jira.plugin... ] Sande Gilda reassigned WFLY-10716: ---------------------------------- Assignee: Sande Gilda (was: Eduardo Martins) > Readme files point to the wrong Guide but some of the information is included in Getting Started Guide > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-10716 > URL: https://issues.jboss.org/browse/WFLY-10716 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sultan Zhantemirov > Assignee: Sande Gilda > > Section "Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse" has a link to [Use JBoss Developer Studio or Eclipse to Run the Quickstarts|https://github.com/jboss-developer/jboss-developer-shared-res...]. > But there is no information about importing a quickstart at content provided by this link. This information is available in other [document|https://doc-stage.usersys.redhat.com/documentation/en-us/jboss_e...] only. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-26) [Artemis 2.x Upgrade] MDB doesn't find its source queue when useJndi property is set to false

by Justin Bertram (JIRA)

[ https://issues.jboss.org/browse/WFWIP-26?page=com.atlassian.jira.plugin.s... ] Justin Bertram reassigned WFWIP-26: ----------------------------------- Assignee: Justin Bertram (was: Martyn Taylor) Resolution: Done > [Artemis 2.x Upgrade] MDB doesn't find its source queue when useJndi property is set to false > --------------------------------------------------------------------------------------------- > > Key: WFWIP-26 > URL: https://issues.jboss.org/browse/WFWIP-26 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis, JMS > Reporter: Martin Styk > Assignee: Justin Bertram > Priority: Blocker > Labels: activemq, feature-branch-blocker > > Having a MDB configured as follows: > {code} > @MessageDriven(name = "mdb", > activationConfig = { > @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), > @ActivationConfigProperty(propertyName = "destination", propertyValue ="InQueue"), > @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"), > }) > {code} > MDB is not able to receive messages from InQueue. > Server logs: > {noformat} > 09:53:29,128 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151004: Instantiating javax.jms.Queue "jms/queue/InQueue" directly since UseJNDI=false. > 09:53:29,188 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "Mdb.jar" (runtime-name : "Mdb.jar") > 09:53:29,306 INFO [org.wildfly.naming] (default task-1) WildFly Naming version 1.0.7.Final > 09:53:29,364 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151000: awaiting topic/queue creation jms/queue/InQueue > 09:53:31,366 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151001: Attempting to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter@2bd07716 destination=jms/queue/InQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15) > 09:53:31,368 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151004: Instantiating javax.jms.Queue "jms/queue/InQueue" directly since UseJNDI=false. > 09:53:33,480 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151004: Instantiating javax.jms.Queue "jms/queue/InQueue" directly since UseJNDI=false. > 09:53:35,092 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0236: Suspending server with no timeout. > {noformat} > In {{ActiveMQActivation.setup()}}, call to {{setupDestination()}} is made. Destiantion InQueue is instantiated there. However, during the {{ActiveMQMessageHandler.setup()}} call. consumer can not be created for this destination and exception {{AMQ119017: Queue InQueue does not exist}} is being thrown. > {code:title=ActiveMQActivation.setup()} > protected synchronized void setup() throws Exception { > logger.debug("Setting up " + spec); > setupCF(); > setupDestination(); > Exception firstException = null; > for (int i = 0; i < spec.getMaxSession(); i++) { > ClientSessionFactory cf = null; > ClientSession session = null; > try { > cf = factory.getServerLocator().createSessionFactory(); > session = setupSession(cf); > ActiveMQMessageHandler handler = new ActiveMQMessageHandler(factory, this, ra.getTM(), (ClientSessionInternal) session, cf, i); > handler.setup(); > handlers.add(handler); > } catch (Exception e) { > ... > } > } > ... > } > {code} > This is regression against Artemis 1.5. > Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a) > Artemis: upstream master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-26) [Artemis 2.x Upgrade] MDB doesn't find its source queue when useJndi property is set to false

by Justin Bertram (JIRA)

[ https://issues.jboss.org/browse/WFWIP-26?page=com.atlassian.jira.plugin.s... ] Justin Bertram commented on WFWIP-26: ------------------------------------- Fix: https://github.com/apache/activemq-artemis/pull/2233 > [Artemis 2.x Upgrade] MDB doesn't find its source queue when useJndi property is set to false > --------------------------------------------------------------------------------------------- > > Key: WFWIP-26 > URL: https://issues.jboss.org/browse/WFWIP-26 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis, JMS > Reporter: Martin Styk > Assignee: Martyn Taylor > Priority: Blocker > Labels: activemq, feature-branch-blocker > > Having a MDB configured as follows: > {code} > @MessageDriven(name = "mdb", > activationConfig = { > @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), > @ActivationConfigProperty(propertyName = "destination", propertyValue ="InQueue"), > @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"), > }) > {code} > MDB is not able to receive messages from InQueue. > Server logs: > {noformat} > 09:53:29,128 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151004: Instantiating javax.jms.Queue "jms/queue/InQueue" directly since UseJNDI=false. > 09:53:29,188 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "Mdb.jar" (runtime-name : "Mdb.jar") > 09:53:29,306 INFO [org.wildfly.naming] (default task-1) WildFly Naming version 1.0.7.Final > 09:53:29,364 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151000: awaiting topic/queue creation jms/queue/InQueue > 09:53:31,366 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151001: Attempting to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter@2bd07716 destination=jms/queue/InQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15) > 09:53:31,368 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151004: Instantiating javax.jms.Queue "jms/queue/InQueue" directly since UseJNDI=false. > 09:53:33,480 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151004: Instantiating javax.jms.Queue "jms/queue/InQueue" directly since UseJNDI=false. > 09:53:35,092 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0236: Suspending server with no timeout. > {noformat} > In {{ActiveMQActivation.setup()}}, call to {{setupDestination()}} is made. Destiantion InQueue is instantiated there. However, during the {{ActiveMQMessageHandler.setup()}} call. consumer can not be created for this destination and exception {{AMQ119017: Queue InQueue does not exist}} is being thrown. > {code:title=ActiveMQActivation.setup()} > protected synchronized void setup() throws Exception { > logger.debug("Setting up " + spec); > setupCF(); > setupDestination(); > Exception firstException = null; > for (int i = 0; i < spec.getMaxSession(); i++) { > ClientSessionFactory cf = null; > ClientSession session = null; > try { > cf = factory.getServerLocator().createSessionFactory(); > session = setupSession(cf); > ActiveMQMessageHandler handler = new ActiveMQMessageHandler(factory, this, ra.getTM(), (ClientSessionInternal) session, cf, i); > handler.setup(); > handlers.add(handler); > } catch (Exception e) { > ... > } > } > ... > } > {code} > This is regression against Artemis 1.5. > Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a) > Artemis: upstream master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10055) [Artemis 2.x Upgrade] Auto-create-queue creates runtime queue without jms.queue prefix

by Justin Bertram (JIRA)

[ https://issues.jboss.org/browse/WFLY-10055?page=com.atlassian.jira.plugin... ] Justin Bertram commented on WFLY-10055: --------------------------------------- Fix: https://github.com/apache/activemq-artemis/pull/2238 > [Artemis 2.x Upgrade] Auto-create-queue creates runtime queue without jms.queue prefix > --------------------------------------------------------------------------------------- > > Key: WFLY-10055 > URL: https://issues.jboss.org/browse/WFLY-10055 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Martin Styk > Assignee: Martyn Taylor > > {{Auto-create-jms-queue}} feature of EAP 7.1 creates runtime queues with name pattern {{"jms.queue.<QUEUE_NAME>"}}. > With Artemis 2.5, {{auto-create-queue}} is a successor of deprecated {{auto-create-jms-queue}} feature. {{Auto-create-queue}} creates queues with name pattern {{"<QUEUE_NAME>"}}. > {code} > session.createQueue("testQueue") > --> "jms.queue.testQueue" (EAP 7.1 + Artemis 1.5, auto-create-jms-queue=true) > --> "testQueue" (Artemis 2.5, auto-create-queue=true) > {code} > This feature is not supported. > Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018