JMS with WildFly 20.0.1.Final problem
2,102 views
Skip to first unread message
Jo Ann Griffin
Sep 15, 2020, 4:14:28 PM9/15/20
to WildFly
I've been using WildFly since 10.0 as a Server/Client successfully for a JMS application. Since this is distributed to end-users, the install involves minimal configuration. The user unpacks the tarfile, runs a script which defines an app user and a management user and defines the JMS queues, and runs the app. This has always worked flawlessly, up through 14.0.
Now I'm trying to upgrade to 20.0.1.Final using Java 11, and my client connects to WildFly just fine, but when I try to do the JNDI lookup on the queue (jms/queue/test1), I get a NamingException. The queue exists, and displays in the Management Console as well as with jboss-cli.
When WildFly comes up, the following shows up:
11:29:20,581 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 84) AMQ221003: Deploying ANYCAST queue jms.queue.test1 on address jms.queue.test1
11:29:20,649 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
11:29:20,649 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
11:29:20,649 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
11:29:20,649 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
11:29:20,813 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 84) AMQ221007: Server is now live
11:29:20,814 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 84) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.10.1 [default, nodeID=29195677-f5ea-11ea-85ee-d46d6dfd687b]
11:29:20,844 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 88) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
11:29:20,846 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 85) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
11:29:20,909 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA
11:29:20,972 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-4) AMQ151007: Resource adaptor started
11:29:20,649 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
11:29:20,649 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
11:29:20,649 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
11:29:20,813 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 84) AMQ221007: Server is now live
11:29:20,814 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 84) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.10.1 [default, nodeID=29195677-f5ea-11ea-85ee-d46d6dfd687b]
11:29:20,844 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 88) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
11:29:20,846 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 85) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
11:29:20,909 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA
11:29:20,972 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-4) AMQ151007: Resource adaptor started
No error shows up in the server log, although a message does show up when the lookup is attempted:
11:30:26,388 INFO [org.wildfly.naming] (default task-1) WildFly Naming version 1.0.13.Final
The version on the client side matches:
Sep 15, 2020 1:01:27 PM org.wildfly.naming.client.Version <clinit>
INFO: WildFly Naming version 1.0.13.Final
INFO: WildFly Naming version 1.0.13.Final
The jndi.properties file is:
java.naming.factory.initial=org.wildfly.naming.client.WildFlyInitialContextFactory
java.naming.provider.url=http-remoting://127.0.0.1:8080
java.naming.security.principal=userA
java.naming.security.credentials=********
java.naming.provider.url=http-remoting://127.0.0.1:8080
java.naming.security.principal=userA
java.naming.security.credentials=********
The lookup for the ConnectionFactory (jms/RemoteConnectionFactory) works fine:
dpsrJMSPLOGServer.cfact = (ConnectionFactory)
dpsrJMSPLOGServer.jndiContext.lookup
( dpsrJMSPLOGServer.szFactoryName );
dpsrJMSPLOGServer.jndiContext.lookup
( dpsrJMSPLOGServer.szFactoryName );
But the lookup for the queue fails:
this.conn = dpsrJMSPLOGServer
.cfact
.createConnection( this.szUserID,
this.szPassword );
.cfact
.createConnection( this.szUserID,
this.szPassword );
I've tried adding <TRACE> for org.wildfly.naming, but I get no output in server.log. Both the app client and WildFly are running on the same system, and should be connecting using localhost.
The client builds under Maven using the following dependencies from WildFly:
<dependency>
<groupId>org.wildfly.bom</groupId>
<artifactId>wildfly-client</artifactId>
<version>20.0.1.Final</version>
<type>pom</type>
</dependency>
<dependency>
<groupId>org.wildfly</groupId>
<artifactId>wildfly-jms-client-bom</artifactId>
<version>20.0.1.Final</version>
<type>pom</type>
</dependency>
<groupId>org.wildfly.bom</groupId>
<artifactId>wildfly-client</artifactId>
<version>20.0.1.Final</version>
<type>pom</type>
</dependency>
<dependency>
<groupId>org.wildfly</groupId>
<artifactId>wildfly-jms-client-bom</artifactId>
<version>20.0.1.Final</version>
<type>pom</type>
</dependency>
Can anyone suggest a diagnostic path to follow here ? Thanks for any input.
Jo Ann Griffin
Sep 15, 2020, 9:22:03 PM9/15/20
to WildFly
I ran a wireshark trace. The next to last packet contains the (correct) queue name being sent from the client to the server, and the last packet is a TCP RST from the server to the client shutting down the connection. This suggests that perhaps a lookup for a queue name is not welcome from 127.0.0.1, although a lookup on the ConnectionFactory name was. The server (from the above) obviously knows about the queue. Is it possible that the ConnectionFactory lookup is handled by WildFly but the queue name lookup is passed to Artemis/ActiveMQ which doesn't like the incoming interface ?
Emmanuel Hugonnet
Sep 16, 2020, 4:55:14 AM9/16/20
to wil...@googlegroups.com
Hello,
Could you please share your configuration on this ? Also did you upgrade your client libs ?
Apache Artemis has changed from 1.x to 2.x in WF14 so a lot of things are different now.
Cheers,
Emmanuel
> java.naming.provider.url=http-remoting://127.0.0.1:8080 <http://127.0.0.1:8080>
> --
> You received this message because you are subscribed to the Google Groups "WildFly" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> <mailto:wildfly+u...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/wildfly/cc8d85a0-a1ec-4b1f-9f6e-f5eaef46ad73n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/cc8d85a0-a1ec-4b1f-9f6e-f5eaef46ad73n%40googlegroups.com?utm_medium=email&utm_source=footer>.
Could you please share your configuration on this ? Also did you upgrade your client libs ?
Apache Artemis has changed from 1.x to 2.x in WF14 so a lot of things are different now.
Cheers,
Emmanuel
> You received this message because you are subscribed to the Google Groups "WildFly" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> <mailto:wildfly+u...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/wildfly/cc8d85a0-a1ec-4b1f-9f6e-f5eaef46ad73n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/cc8d85a0-a1ec-4b1f-9f6e-f5eaef46ad73n%40googlegroups.com?utm_medium=email&utm_source=footer>.
Emmanuel Hugonnet
Sep 16, 2020, 11:20:05 AM9/16/20
to wil...@googlegroups.com
Do you have some sample code which fails now ?
I'll try to run this. Please give me also the script or classpath you use to run your client.
Regards
Emmanuel
> > java.naming.provider.url=http-remoting://127.0.0.1:8080 <http://127.0.0.1:8080> <http://127.0.0.1:8080>
> https://groups.google.com/d/msgid/wildfly/0ec50bc6-bac9-423f-a56e-1936a388d4b4n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/0ec50bc6-bac9-423f-a56e-1936a388d4b4n%40googlegroups.com?utm_medium=email&utm_source=footer>.
I'll try to run this. Please give me also the script or classpath you use to run your client.
Regards
Emmanuel
> <https://groups.google.com/d/msgid/wildfly/0ec50bc6-bac9-423f-a56e-1936a388d4b4n%40googlegroups.com?utm_medium=email&utm_source=footer>.
Jo Ann Griffin
Sep 17, 2020, 9:25:50 AM9/17/20
to WildFly
I'm attaching a zip file that contains a NetBeans project giving a simple reproducible case. The project is packaged using Maven, so you can find the source in src/main/java/org/profsoftsvcs/dpsrtest/test.java. The project is built using Maven assembly, so there is a standalone JAR in target that contains all of the WildFly client classes as well as test.class.
src/main/resources contains a test.sh which can be run to cause the error. You will need to modify the directory names based on where you unzip it.
Here's the client stdout/stderr when I run it:
[ftg@ftglap resources]$ pwd
/home/ftg/data/dpsrTest/src/main/resources
[ftg@ftglap resources]$ sh ./test.sh
Sep 17, 2020 8:54:53 AM org.wildfly.naming.client.Version <clinit>
INFO: WildFly Naming version 1.0.13.Final
Sep 17, 2020 8:54:53 AM org.wildfly.security.Version <clinit>
INFO: ELY00001: WildFly Elytron version 1.12.1.Final
Sep 17, 2020 8:54:53 AM org.xnio.Xnio <clinit>
INFO: XNIO version 3.8.1.Final
Sep 17, 2020 8:54:53 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.8.1.Final
Sep 17, 2020 8:54:53 AM org.jboss.threads.Version <clinit>
INFO: JBoss Threads version 2.3.3.Final
Sep 17, 2020 8:54:53 AM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 5.0.18.Final
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.marshalling.reflect.JDKSpecific$SerMethods (file:/data/ftg/dpsrTest/target/dpsrTest-1.0-SNAPSHOT-jar-with-dependencies.jar) to constructor java.util.AbstractMap()
WARNING: Please consider reporting this to the maintainers of org.jboss.marshalling.reflect.JDKSpecific$SerMethods
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Exception in thread "main" javax.naming.NameNotFoundException: jms/queue -- service jboss.naming.context.java.jboss.exported.jms.queue
at org.jboss...@20.0.1.Final//org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
at org.wildfly....@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:203)
at org.wildfly....@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:123)
at org.jboss...@5.0.18.Final//org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
at org.jboss...@5.0.18.Final//org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
at org.jbos...@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jbos...@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jbos...@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jbos...@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:834)
[ftg@ftglap resources]$
The test code doesn't catch the NamingException, so it comes out with the original stacktrace, but the source of the error is clear: the application is doing a lookup on jms/queue/test1 but the argument displayed in the stacktrace is jms/queue with the "/test1" removed.
Thanks for looking into this.
Update: the ZIP is apparently too large for google groups. If the above stacktrace isn't enough, I'll split the ZIP and attach the fragments separately. I'll attach the source code for test.java, the pom.xml, and test.sh.
Emmanuel Hugonnet
Sep 21, 2020, 2:52:04 AM9/21/20
to wil...@googlegroups.com
Do you have a org.apache.activemq.artemis.api.jms.ActiveMQJMSClient.properties file in your aggregated jar:
dpsrTest-1.0-SNAPSHOT-jar-with-dependencies.jar ?
Emmanuel
> <https://groups.google.com/d/msgid/wildfly/33f8c57b-7ace-429c-8ded-7f7d009f1478n%40googlegroups.com?utm_medium=email&utm_source=footer>.
dpsrTest-1.0-SNAPSHOT-jar-with-dependencies.jar ?
Emmanuel
> --
> You received this message because you are subscribed to the Google Groups "WildFly" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> <mailto:wildfly+u...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/wildfly/33f8c57b-7ace-429c-8ded-7f7d009f1478n%40googlegroups.com
> You received this message because you are subscribed to the Google Groups "WildFly" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> <mailto:wildfly+u...@googlegroups.com>.
> To view this discussion on the web visit
> <https://groups.google.com/d/msgid/wildfly/33f8c57b-7ace-429c-8ded-7f7d009f1478n%40googlegroups.com?utm_medium=email&utm_source=footer>.
Jo Ann Griffin
Sep 21, 2020, 9:53:24 AM9/21/20
to WildFly
Yes, it contains:
# Copyright 2018 Red Hat, Inc.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
enable1xPrefixes=true
I didn't supply this, so I'm not sure where it came from.
Emmanuel Hugonnet
Sep 21, 2020, 12:41:41 PM9/21/20
to Jo Ann Griffin, WildFly
Hello,
I've updated your code a little and now everything passes:
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "http-remoting://127.0.0.1:8080");
InitialContext jndiContext = new InitialContext(env);
BUT since you are using security maybe something is wrongly configured there for you.
Try disabling the broker security to check that this is not it too.
Cheers,
Emmanuel
> https://groups.google.com/d/msgid/wildfly/1c6cc81d-c317-4a7e-a7ee-57a21aad0145n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/1c6cc81d-c317-4a7e-a7ee-57a21aad0145n%40googlegroups.com?utm_medium=email&utm_source=footer>.
I've updated your code a little and now everything passes:
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "http-remoting://127.0.0.1:8080");
InitialContext jndiContext = new InitialContext(env);
BUT since you are using security maybe something is wrongly configured there for you.
Try disabling the broker security to check that this is not it too.
Cheers,
Emmanuel
> <https://groups.google.com/d/msgid/wildfly/1c6cc81d-c317-4a7e-a7ee-57a21aad0145n%40googlegroups.com?utm_medium=email&utm_source=footer>.
Jo Ann Griffin
Sep 21, 2020, 12:51:41 PM9/21/20
to WildFly
Hi Emmanuel,
I don't understand. The WF docs say that org.jboss.naming.remote.client.InitialContextFactory is deprecated, and the WF InitialContextFactory should be used. But in any case, I tried it with both and got the same error. Note that the error does not occur creating the InitialContext, but when I try to look up a queue name.
The JBoss and WF docs since forever have said that to use JMS you have to have a user with the "guest" property. Is this no longer the case ?
Did your test not get the NamingException ? If it didn't, I'll try reverting the InitialContextFactory and removing the userid and password to see if it makes a difference.
Thanks !
Jo Ann Griffin
Sep 21, 2020, 3:04:49 PM9/21/20
to WildFly
OK, I tried replacing the InitialContextFactory and removed the userid and password from the createConnection call, and I get:
[ftg@ftglap classes]$ sh ./test.sh
Sep 21, 2020 2:57:50 PM org.jboss.naming.remote.client.InitialContextFactory <clinit>
INFO: WFNAM00025: org.jboss.naming.remote.client.InitialContextFactory is deprecated; new applications should use org.wildfly.naming.client.WildFlyInitialContextFactory instead
Sep 21, 2020 2:57:50 PM org.wildfly.naming.client.Version <clinit>
Sep 21, 2020 2:57:50 PM org.jboss.naming.remote.client.InitialContextFactory <clinit>
INFO: WFNAM00025: org.jboss.naming.remote.client.InitialContextFactory is deprecated; new applications should use org.wildfly.naming.client.WildFlyInitialContextFactory instead
Sep 21, 2020 2:57:50 PM org.wildfly.naming.client.Version <clinit>
INFO: WildFly Naming version 1.0.13.Final
Sep 21, 2020 2:57:50 PM org.wildfly.security.Version <clinit>
INFO: ELY00001: WildFly Elytron version 1.12.1.Final
Sep 21, 2020 2:57:50 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.8.1.Final
Sep 21, 2020 2:57:50 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO version 3.8.1.Final
Sep 21, 2020 2:57:50 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.8.1.Final
Sep 21, 2020 2:57:50 PM org.jboss.threads.Version <clinit>
INFO: JBoss Threads version 2.3.3.Final
Sep 21, 2020 2:57:50 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 5.0.18.Final
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Exception in thread "main" javax.jms.JMSSecurityException: AMQ229031: Unable to validate user from /127.0.0.1:42940. Username: null; SSL certificate subject DN: unavailable
at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:464)
at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:358)
at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:300)
at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:249)
at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionChannel(ClientSessionFactoryImpl.java:1348)
at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:673)
at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:298)
at org.apache.activemq.artemis.jms.client.ActiveMQConnection.authorize(ActiveMQConnection.java:684)
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:920)
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:299)
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:294)
at org.profsoftsvcs.dpsrtest.test.main(test.java:114)
Caused by: ActiveMQSecurityException[errorType=SECURITY_EXCEPTION message=AMQ229031: Unable to validate user from /127.0.0.1:42940. Username: null; SSL certificate subject DN: unavailable]
... 12 more
at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:464)
at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:358)
at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:300)
at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:249)
at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionChannel(ClientSessionFactoryImpl.java:1348)
at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:673)
at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:298)
at org.apache.activemq.artemis.jms.client.ActiveMQConnection.authorize(ActiveMQConnection.java:684)
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:920)
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:299)
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:294)
at org.profsoftsvcs.dpsrtest.test.main(test.java:114)
Caused by: ActiveMQSecurityException[errorType=SECURITY_EXCEPTION message=AMQ229031: Unable to validate user from /127.0.0.1:42940. Username: null; SSL certificate subject DN: unavailable]
... 12 more
Note that there is a warning about the old InitialContextFactory being deprecated, and the exception occurs because no userid was passed.
Emmanuel Hugonnet
Sep 21, 2020, 3:45:22 PM9/21/20
to Jo Ann Griffin, WildFly
You can disable security for testing purpose on the broker.
Emmanuel
> env.put(Context.PROVIDER_URL, "http-remoting://127.0.0.1:8080 <http://127.0.0.1:8080>");
> https://groups.google.com/d/msgid/wildfly/9f8cb8fe-d5ac-4c55-8047-ce4d5df6ad8bn%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/9f8cb8fe-d5ac-4c55-8047-ce4d5df6ad8bn%40googlegroups.com?utm_medium=email&utm_source=footer>.
Emmanuel
> <https://groups.google.com/d/msgid/wildfly/9f8cb8fe-d5ac-4c55-8047-ce4d5df6ad8bn%40googlegroups.com?utm_medium=email&utm_source=footer>.
Jo Ann Griffin
Sep 21, 2020, 3:47:27 PM9/21/20
to WildFly
>You can disable security for testing purpose on the broker.
Sorry, I don't know how to do that.
Jo Ann Griffin
Sep 23, 2020, 7:16:43 AM9/23/20
to WildFly
Hi Emmanuel,
Could you please post your version of test.java in toto so that I can build it into my JAR and try it ? Also, what is the "broker" and how do you disable security in it ?
Thanks
Jo Ann Griffin
Sep 23, 2020, 8:49:20 AM9/23/20
to WildFly
Hi Emmanuel,
In going through the Artemis documentation, I see what you mean by "broker', but it's configured by an /etc/broker.xml which is not used by WF.
Alban
Sep 23, 2020, 10:21:57 AM9/23/20
to WildFly
Hello,
I believe this is what Emmanuel meant - You can disable security in your standalone configuration file:
<subsystem xmlns="urn:jboss:domain:messaging-activemq:10.0">
<server name="default">
<statistics enabled="${wildfly.messaging-activemq.statistics-enabled:${wildfly.statistics-enabled:false}}"/>
<security enabled="false" />
<security-setting name="#">
<role name="guest" send="true" consume="true" create-non-durable-queue="true" delete-non-durable-queue="true" />
</security-setting>
Either change the file manually or through the jboss-cli: /subsystem=messaging-activemq/server=default/:write-attribute(name=security-enabled,value=false)
Jo Ann Griffin
Sep 23, 2020, 10:30:13 AM9/23/20
to WildFly
Ah, thank you Alban.
Emmanuel Hugonnet
Sep 24, 2020, 5:39:50 AM9/24/20
to Jo Ann Griffin, WildFly
Artemis is a message broker, by broker I meant Artemis server.
to disable security:
subsystem=messaging-activemq/server=default:write-attribute(name=security-enabled, value=false)
Emmanuel
> <http://127.0.0.1:42940>. Username: null; SSL
> https://groups.google.com/d/msgid/wildfly/73435c52-b209-4f35-b57f-e6694fb90f41n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/73435c52-b209-4f35-b57f-e6694fb90f41n%40googlegroups.com?utm_medium=email&utm_source=footer>.
to disable security:
subsystem=messaging-activemq/server=default:write-attribute(name=security-enabled, value=false)
Emmanuel
> > certificate subject DN: unavailable
> > at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:464)
> > at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:358)
> > at
> >
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:300)
> > at
> >
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:249)
> > at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionChannel(ClientSessionFactoryImpl.java:1348)
> > at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:673)
> > at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:298)
> > at org.apache.activemq.artemis.jms.client.ActiveMQConnection.authorize(ActiveMQConnection.java:684)
> > at
> org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:920)
> > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:299)
> > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:294)
> > at org.profsoftsvcs.dpsrtest.test.main(test.java:114)
> > Caused by: ActiveMQSecurityException[errorType=SECURITY_EXCEPTION message=AMQ229031: Unable to validate user from
> /127.0.0.1:42940 <http://127.0.0.1:42940>.
> > at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:464)
> > at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:358)
> > at
> >
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:300)
> > at
> >
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:249)
> > at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionChannel(ClientSessionFactoryImpl.java:1348)
> > at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:673)
> > at
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:298)
> > at org.apache.activemq.artemis.jms.client.ActiveMQConnection.authorize(ActiveMQConnection.java:684)
> > at
> org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:920)
> > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:299)
> > at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:294)
> > at org.profsoftsvcs.dpsrtest.test.main(test.java:114)
> > Caused by: ActiveMQSecurityException[errorType=SECURITY_EXCEPTION message=AMQ229031: Unable to validate user from
> > Username: null; SSL certificate subject DN: unavailable]
> > ... 12 more
> >
> > Note that there is a warning about the old InitialContextFactory being deprecated, and the exception occurs because no
> userid was passed.
> >
> > On Monday, September 21, 2020 at 12:51:41 PM UTC-4 Jo Ann Griffin wrote:
> >
> > Hi Emmanuel,
> >
> > I don't understand. The WF docs say that org.jboss.naming.remote.client.InitialContextFactory is deprecated, and the WF
> > InitialContextFactory should be used. But in any case, I tried it with both and got the same error. Note that the error
> does not
> > occur creating the InitialContext, but when I try to look up a queue name.
> >
> > The JBoss and WF docs since forever have said that to use JMS you have to have a user with the "guest" property. Is this no
> longer
> > the case ?
> >
> > Did your test not get the NamingException ? If it didn't, I'll try reverting the InitialContextFactory and removing the
> userid and
> > password to see if it makes a difference.
> >
> > Thanks !
> >
> > On Monday, September 21, 2020 at 12:41:41 PM UTC-4 ehug...@redhat.com wrote:
> >
> > Hello,
> > I've updated your code a little and now everything passes:
> > final Properties env = new Properties();
> > env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
> > env.put(Context.PROVIDER_URL, "http-remoting://127.0.0.1:8080 <http://127.0.0.1:8080> <http://127.0.0.1:8080>");
> > ... 12 more
> >
> > Note that there is a warning about the old InitialContextFactory being deprecated, and the exception occurs because no
> userid was passed.
> >
> > On Monday, September 21, 2020 at 12:51:41 PM UTC-4 Jo Ann Griffin wrote:
> >
> > Hi Emmanuel,
> >
> > I don't understand. The WF docs say that org.jboss.naming.remote.client.InitialContextFactory is deprecated, and the WF
> > InitialContextFactory should be used. But in any case, I tried it with both and got the same error. Note that the error
> does not
> > occur creating the InitialContext, but when I try to look up a queue name.
> >
> > The JBoss and WF docs since forever have said that to use JMS you have to have a user with the "guest" property. Is this no
> longer
> > the case ?
> >
> > Did your test not get the NamingException ? If it didn't, I'll try reverting the InitialContextFactory and removing the
> userid and
> > password to see if it makes a difference.
> >
> > Thanks !
> >
> > On Monday, September 21, 2020 at 12:41:41 PM UTC-4 ehug...@redhat.com wrote:
> >
> > Hello,
> > I've updated your code a little and now everything passes:
> > final Properties env = new Properties();
> > env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
> <https://groups.google.com/d/msgid/wildfly/73435c52-b209-4f35-b57f-e6694fb90f41n%40googlegroups.com?utm_medium=email&utm_source=footer>.
Jo Ann Griffin
Sep 24, 2020, 9:41:33 AM9/24/20
to WildFly
Hi All,
Still no joy after disabling security and using createConnection() instead of passing credentials:
Exception in thread "main" javax.naming.NameNotFoundException: jms/queue -- service jboss.naming.context.java.jboss.exported.jms.queue
Emmanuel, the only difference I can see between the code you say works and mine is that you're creating a Properties explicitly and I'm using the same values but letting the InitialContext pick them up from jndi.properties. Should this make a difference ?
Please attach your version of test.java so that I can test that against my server. It may be that our server configs differ.
Thanks.
Emmanuel Hugonnet
Sep 24, 2020, 10:35:21 AM9/24/20
to wil...@googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/9a436904-9b87-4ec8-858b-796e07d53f8en%40googlegroups.com?utm_medium=email&utm_source=footer>.
Jo Ann Griffin
Sep 24, 2020, 11:54:36 AM9/24/20
to WildFly
Still no joy. I get the same NameNotFound exception with your code:
Exception in thread "main" javax.naming.NameNotFoundException: jms/queue -- service jboss.naming.context.java.jboss.exported.jms.queue
at org.jboss...@20.0.1.Final//org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
at org.wildfly....@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:203)
at org.wildfly....@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:123)
at org.jboss...@5.0.18.Final//org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
at org.jboss...@5.0.18.Final//org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
at org.jbos...@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jbos...@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jbos...@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jbos...@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:834)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
at org.wildfly....@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:203)
at org.wildfly....@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:123)
at org.jboss...@5.0.18.Final//org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
at org.jboss...@5.0.18.Final//org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
at org.jbos...@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jbos...@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jbos...@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jbos...@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:834)
For reference, my queue definitions are:
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default:read-children-names(child-type="jms-queue")
{
"outcome" => "success",
"result" => [
"DLQ",
"ExpiryQueue",
"test1",
"test2",
"test3",
"test4",
"test5"
]
}
{
"outcome" => "success",
"result" => [
"DLQ",
"ExpiryQueue",
"test1",
"test2",
"test3",
"test4",
"test5"
]
}
and "jms/queue/test1" is the argument to the lookup().
What do you get running the above command in jboss-cli ?
Emmanuel Hugonnet
Sep 24, 2020, 12:17:08 PM9/24/20
to Jo Ann Griffin, WildFly
I setup my server like this:
/subsystem=messaging-activemq/server=default:write-attribute(name=security-enabled, value=false)
/subsystem=messaging-activemq/server=default/jms-queue=createdTestQueue:add(entries=["java:jboss/exported/jms/queue/createdTestQueue",
"jms/queue/createdTestQueue"])
then I ran my Java code.
Emmanuel
> > > /127.0.0.1:42940 <http://127.0.0.1:42940> <http://127.0.0.1:42940> <http://127.0.0.1:42940>.
> https://groups.google.com/d/msgid/wildfly/d4811dc2-8a11-4768-80a9-d427b76ffbccn%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/d4811dc2-8a11-4768-80a9-d427b76ffbccn%40googlegroups.com?utm_medium=email&utm_source=footer>.
/subsystem=messaging-activemq/server=default:write-attribute(name=security-enabled, value=false)
/subsystem=messaging-activemq/server=default/jms-queue=createdTestQueue:add(entries=["java:jboss/exported/jms/queue/createdTestQueue",
"jms/queue/createdTestQueue"])
then I ran my Java code.
Emmanuel
> <https://groups.google.com/d/msgid/wildfly/d4811dc2-8a11-4768-80a9-d427b76ffbccn%40googlegroups.com?utm_medium=email&utm_source=footer>.
Jo Ann Griffin
Sep 24, 2020, 12:22:22 PM9/24/20
to WildFly
Ah, that explains it. We're not using the same queue name. I'll retry, and also compare your "entries" data with my own.
Jo Ann Griffin
Sep 24, 2020, 1:15:41 PM9/24/20
to WildFly
I changed your queue name to test1 to match my definition, but I still get the Exception. My definition is:
/subsystem=messaging-activemq/server=default/jms-queue=test1/:add(entries=["java:/jboss/exported/jms/queue/test1"])
Two differences here: I have a slash before ":add" and you don't, and you've got a second "entries" value and I don't.
I'll work with that.
Jo Ann Griffin
Sep 24, 2020, 1:44:16 PM9/24/20
to WildFly
The syntax changes didn't seem to work.
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/jms-queue=test1:add(entries=["java:/jboss/exported/jms/queue/test1","jms/queue/test1"])
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/jms-queue=test2:add(entries=["java:/jboss/exported/jms/queue/test2","jms/queue/test2"])
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/jms-queue=test3:add(entries=["java:/jboss/exported/jms/queue/test3","jms/queue/test3"])
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/jms-queue=test4:add(entries=["java:/jboss/exported/jms/queue/test4","jms/queue/test4"])
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/jms-queue=test5:add(entries=["java:/jboss/exported/jms/queue/test5","jms/queue/test5"])
{"outcome" => "success"}
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/jms-queue=test2:add(entries=["java:/jboss/exported/jms/queue/test2","jms/queue/test2"])
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/jms-queue=test3:add(entries=["java:/jboss/exported/jms/queue/test3","jms/queue/test3"])
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/jms-queue=test4:add(entries=["java:/jboss/exported/jms/queue/test4","jms/queue/test4"])
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/jms-queue=test5:add(entries=["java:/jboss/exported/jms/queue/test5","jms/queue/test5"])
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default:read-children-names(child-type="jms-queue")
{
"outcome" => "success",
"result" => [
"DLQ",
"ExpiryQueue",
"test1",
"test2",
"test3",
"test4",
"test5"
]
}
which looks pretty much as it did before.
The exception is the same:
Exception in thread "main" javax.naming.NameNotFoundException: jms/queue -- service jboss.naming.context.java.jboss.exported.jms.queue
at org.jboss...@20.0.1.Final//org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
at org.wildfly....@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:203)
at org.wildfly....@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:123)
at org.jboss...@5.0.18.Final//org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
at org.jboss...@5.0.18.Final//org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
at org.jbos...@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jbos...@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jbos...@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jbos...@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:834)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
at org.jboss...@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
at org.wildfly....@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:203)
at org.wildfly....@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:123)
at org.jboss...@5.0.18.Final//org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
at org.jboss...@5.0.18.Final//org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
at org.jbos...@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jbos...@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jbos...@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jbos...@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:834)
Any suggestions on how to proceed ? Are there DEBUG settings for Artemis ?
Thanks.
Jo Ann Griffin
Sep 24, 2020, 4:48:30 PM9/24/20
to WildFly
Hi Emmanuel,
When you built your client, did you use Maven and the same pom.xml that I previously attached ? If so, the difference must be in our servers. I created mine by un-tar'ing the WildFly 20.0.1.Final tarball to a fresh directory, starting it, and then running the following script:
cd
cd w*l/bin
sh ./add-user.sh -a -u 'userA' -p 'Wiz314159!' -g 'guest'
sh ./add-user.sh -u 'userM' -p 'Wiz314159!' -g 'admin'
sh ./jboss-cli.sh -c <<EOF
/subsystem=messaging-activemq/server=default/address-setting=#:write-attribute(name=max-delivery-attempts,value=-1)
cd w*l/bin
sh ./add-user.sh -a -u 'userA' -p 'Wiz314159!' -g 'guest'
sh ./add-user.sh -u 'userM' -p 'Wiz314159!' -g 'admin'
sh ./jboss-cli.sh -c <<EOF
/subsystem=messaging-activemq/server=default/address-setting=#:write-attribute(name=max-delivery-attempts,value=-1)
/subsystem=messaging-activemq/server=default/jms-queue=test1:add(entries=["java:/jboss/exported/jms/queue/test1","jms/queue/test1"])
/subsystem=messaging-activemq/server=default/jms-queue=test2:add(entries=["java:/jboss/exported/jms/queue/test2","jms/queue/test2"])
/subsystem=messaging-activemq/server=default/jms-queue=test3:add(entries=["java:/jboss/exported/jms/queue/test3","jms/queue/test3"])
/subsystem=messaging-activemq/server=default/jms-queue=test4:add(entries=["java:/jboss/exported/jms/queue/test4","jms/queue/test4"])
/subsystem=messaging-activemq/server=default/jms-queue=test5:add(entries=["java:/jboss/exported/jms/queue/test5","jms/queue/test5"])
quit
EOF
EOF
Can you re-test with this bare-bones server ?
Thanks.
Emmanuel Hugonnet
Sep 25, 2020, 7:51:33 AM9/25/20
to Jo Ann Griffin, WildFly
Hello,
I didn't add the user
Used a fresh tar.gz install
Used your pom except that I used target and source to 1.8
I didn't change the address-settings
I just added the queue and disabled security with the commands I sent you.
Then I ran the Test code
Cheers,
Emmanuel
> > > > /127.0.0.1:42940 <http://127.0.0.1:42940> <http://127.0.0.1:42940> <http://127.0.0.1:42940> <http://127.0.0.1:42940>.
> https://groups.google.com/d/msgid/wildfly/4a376696-53d5-4aa6-9b25-345847ea4a0fn%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/4a376696-53d5-4aa6-9b25-345847ea4a0fn%40googlegroups.com?utm_medium=email&utm_source=footer>.
I didn't add the user
Used a fresh tar.gz install
Used your pom except that I used target and source to 1.8
I didn't change the address-settings
I just added the queue and disabled security with the commands I sent you.
Then I ran the Test code
Cheers,
Emmanuel
> <https://groups.google.com/d/msgid/wildfly/4a376696-53d5-4aa6-9b25-345847ea4a0fn%40googlegroups.com?utm_medium=email&utm_source=footer>.
Jo Ann Griffin
Oct 1, 2020, 12:35:18 PM10/1/20
to WildFly
Hi Emmanuel,
This has me tearing my hair out. Could you please post the stdout from your test run as well as your standalone-full.xml ?
Thanks.
Jo Ann Griffin
Oct 2, 2020, 11:47:01 AM10/2/20
to WildFly
Hi Emmanuel,
I tried an experiment. I created a wildfly Maven project under NetBeans, and then ran a utility of mine that rearranges the classes in wildfly-20.0.1.Final-src so that they appear in the correct package structure under src/main/java. Then I ran the test case using the debugger, with a breakpoint at the top line in the stacktrace (org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106). According to the source file, that is indeed a throw command for a NameNotFound Exception which displays "name.toString() + " -- " + lookupName", as displayed in the stacktrace. However, the breakpoint doesn't hit.
Another thing I noticed is that NetBeans shows compilation errors in many of the source files, all of which stem from org.jboss.as.naming or org.wildfly.naming classes not existing. For example, in org.jboss.as.naming.WritableServiceBasedNamingStoreTestCase.java the following imports fail because the classes don't exist:
import org.wildfly.naming.java.permission.JndiPermission;
import org.jboss.as.naming.deployment.ContextNames;
import org.jboss.as.naming.deployment.JndiNamingDependencyProcessor;
import org.jboss.as.naming.deployment.RuntimeBindReleaseService;
import org.jboss.as.naming.service.NamingStoreService;
import org.jboss.msc.service.LifecycleEvent;
import org.jboss.msc.service.LifecycleListener;
import org.jboss.msc.service.ServiceContainer;
import org.jboss.msc.service.ServiceController;
import org.jboss.msc.service.ServiceName;
import org.jboss.as.naming.deployment.ContextNames;
import org.jboss.as.naming.deployment.JndiNamingDependencyProcessor;
import org.jboss.as.naming.deployment.RuntimeBindReleaseService;
import org.jboss.as.naming.service.NamingStoreService;
import org.jboss.msc.service.LifecycleEvent;
import org.jboss.msc.service.LifecycleListener;
import org.jboss.msc.service.ServiceContainer;
import org.jboss.msc.service.ServiceController;
import org.jboss.msc.service.ServiceName;
and, indeed, in the src tarfile they do *not* exist.
So I'm thinking that either I'm getting bad org.wildfly.naming dependencies, or else there are other src tarfiles I need to unpack as well as wildfly-src.
Anyway, from the source I have for ServiceBasedNamingStore.java, the name for which lookup fails is indeed jms/queue -- service jboss.naming.context.java.jboss.exported.jms.queue, which indicates that it's indeed "jms/queue" that's having the problem, and not the actual test1 queue name.
Thanks.
Emmanuel Hugonnet
Oct 2, 2020, 12:04:34 PM10/2/20
to Jo Ann Griffin, WildFly
Hello,
I use Apache NetBeans too and with your configuraiotn I couldn't find the exported/jms/queue in the jndiView using jboss-cli.
I couldn't find your issue but it worked with my sample using a clean standalone-full.xml
Cheers,
EMmanuel
> https://groups.google.com/d/msgid/wildfly/615f0b1e-e9e1-49c2-8e8a-ece1d57bbdc9n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/615f0b1e-e9e1-49c2-8e8a-ece1d57bbdc9n%40googlegroups.com?utm_medium=email&utm_source=footer>.
I use Apache NetBeans too and with your configuraiotn I couldn't find the exported/jms/queue in the jndiView using jboss-cli.
I couldn't find your issue but it worked with my sample using a clean standalone-full.xml
Cheers,
EMmanuel
> <https://groups.google.com/d/msgid/wildfly/615f0b1e-e9e1-49c2-8e8a-ece1d57bbdc9n%40googlegroups.com?utm_medium=email&utm_source=footer>.
Jo Ann Griffin
Oct 2, 2020, 12:14:28 PM10/2/20
to WildFly
Update: the compilation errors (almost all of them, anyway) were my error, as a previous test had moved to Java 1.8 to match your scenario, and the current wildfly-src requires module support to build. However, the breakpoints still aren't hitting when the exception occurs.
Jo Ann Griffin
Oct 2, 2020, 12:18:12 PM10/2/20
to WildFly
Hi Emmanuel,
Can you post which configuration of mine you used, and your standalone-full.xml ? Also, the stdout from running your test case ?
Thanks.
Jo Ann Griffin
Oct 6, 2020, 11:30:26 AM10/6/20
to WildFly
Someone else has seen this: http://wildfly-development.1055759.n5.nabble.com/javax-naming-NameNotFoundException-jms-queue-service-jboss-naming-context-java-jboss-exported-jms-qu-td5719414.html
I'm becoming convinced that the problem is tied to jms/queue rather than the actual queue name, as I replaced jms/queue/test1 with jms/queue/DLQ (which is supplied by WildFly itself) and got the same error.
Jo Ann Griffin
Oct 6, 2020, 2:44:28 PM10/6/20
to WildFly
Hi Emmanuel,
I noticed one other difference, in your PROVIDER_URL. You have:
env.put(Context.PROVIDER_URL, "http-remoting://127.0.0.1:8080 <http://127.0.0.1:8080> <http://127.0.0.1:8080>
> <http://127.0.0.1:8080>");
When I put this in my jndi.properties:
java.naming.provider.url=http-remoting://127.0.0.1:8080 <http://127.0.0.1:8080> <http://127.0.0.1:8080>
> <http://127.0.0.1:8080>
> <http://127.0.0.1:8080>
I get:
Exception in thread "main" javax.naming.ConfigurationException: WFNAM00003: Invalid naming provider URI: http-remoting://127.0.0.1:8080 <http://127.0.0.1:8080> <http://127.0.0.1:8080> [Root exception is java.net.URISyntaxException: Illegal character in authority at index 16: http-remoting://127.0.0.1:8080 <http://127.0.0.1:8080> <http://127.0.0.1:8080>]
at org.wildfly.naming.client.ProviderEnvironment$Builder.populateProviderUris(ProviderEnvironment.java:540)
at org.wildfly.naming.client.ProviderEnvironment$Builder.populateFromEnvironment(ProviderEnvironment.java:292)
at org.wildfly.naming.client.WildFlyRootContext.<init>(WildFlyRootContext.java:114)
at org.wildfly.naming.client.WildFlyRootContext.<init>(WildFlyRootContext.java:89)
at org.wildfly.naming.client.WildFlyRootContext.<init>(WildFlyRootContext.java:79)
at org.wildfly.naming.client.WildFlyInitialContextFactory.getInitialContext(WildFlyInitialContextFactory.java:54)
at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:64)
at java.naming/javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:719)
at java.naming/javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:305)
at java.naming/javax.naming.InitialContext.init(InitialContext.java:236)
at java.naming/javax.naming.InitialContext.<init>(InitialContext.java:184)
at org.profsoftsvcs.dpsrtest.Test.main(Test.java:75)
Caused by: java.net.URISyntaxException: Illegal character in authority at index 16: http-remoting://127.0.0.1:8080 <http://127.0.0.1:8080> <http://127.0.0.1:8080>
at java.base/java.net.URI$Parser.fail(URI.java:2913)
at java.base/java.net.URI$Parser.parseAuthority(URI.java:3247)
at java.base/java.net.URI$Parser.parseHierarchical(URI.java:3158)
at java.base/java.net.URI$Parser.parse(URI.java:3114)
at java.base/java.net.URI.<init>(URI.java:600)
at org.wildfly.naming.client.ProviderEnvironment$Builder.populateProviderUris(ProviderEnvironment.java:538)
... 11 more
[
at org.wildfly.naming.client.ProviderEnvironment$Builder.populateProviderUris(ProviderEnvironment.java:540)
at org.wildfly.naming.client.ProviderEnvironment$Builder.populateFromEnvironment(ProviderEnvironment.java:292)
at org.wildfly.naming.client.WildFlyRootContext.<init>(WildFlyRootContext.java:114)
at org.wildfly.naming.client.WildFlyRootContext.<init>(WildFlyRootContext.java:89)
at org.wildfly.naming.client.WildFlyRootContext.<init>(WildFlyRootContext.java:79)
at org.wildfly.naming.client.WildFlyInitialContextFactory.getInitialContext(WildFlyInitialContextFactory.java:54)
at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:64)
at java.naming/javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:719)
at java.naming/javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:305)
at java.naming/javax.naming.InitialContext.init(InitialContext.java:236)
at java.naming/javax.naming.InitialContext.<init>(InitialContext.java:184)
at org.profsoftsvcs.dpsrtest.Test.main(Test.java:75)
Caused by: java.net.URISyntaxException: Illegal character in authority at index 16: http-remoting://127.0.0.1:8080 <http://127.0.0.1:8080> <http://127.0.0.1:8080>
at java.base/java.net.URI$Parser.fail(URI.java:2913)
at java.base/java.net.URI$Parser.parseAuthority(URI.java:3247)
at java.base/java.net.URI$Parser.parseHierarchical(URI.java:3158)
at java.base/java.net.URI$Parser.parse(URI.java:3114)
at java.base/java.net.URI.<init>(URI.java:600)
at org.wildfly.naming.client.ProviderEnvironment$Builder.populateProviderUris(ProviderEnvironment.java:538)
... 11 more
[
Emmanuel Hugonnet
Oct 14, 2020, 9:48:20 AM10/14/20
to Jo Ann Griffin, WildFly
The JNDI name is incorrect, removing the '/' between java and jboss fixed this.
Cheers,
Emmanuel
PS: I'll close your JIRA once you're ok with that.
> > > > > > > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder <http://www.slf4j.org/codes.html#StaticLoggerBinder> for
> > <http://127.0.0.1:42940 <http://127.0.0.1:42940>>.
> > > <http://127.0.0.1:8080 <http://127.0.0.1:8080>> <http://127.0.0.1:8080 <http://127.0.0.1:8080>>
> > > > > <http://127.0.0.1:8080 <http://127.0.0.1:8080>>");
> > > > > > > > > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder <http://www.slf4j.org/codes.html#StaticLoggerBinder>
> <https://groups.google.com/d/msgid/wildfly/33f8c57b-7ace-429c-8ded-7f7d009f1478n%40googlegroups.com?utm_medium=email&utm_source=footer
> <https://groups.google.com/d/msgid/wildfly/615f0b1e-e9e1-49c2-8e8a-ece1d57bbdc9n%40googlegroups.com?utm_medium=email&utm_source=footer>>.
> <https://groups.google.com/d/msgid/wildfly/717fc13d-9fde-4b46-b88d-d5e42fee9b1cn%40googlegroups.com?utm_medium=email&utm_source=footer>.
Cheers,
Emmanuel
PS: I'll close your JIRA once you're ok with that.
> further details.
> > > > > > > Exception in thread "main" javax.jms.JMSSecurityException: AMQ229031: Unable to validate user from
> > > /127.0.0.1:42940 <http://127.0.0.1:42940> <http://127.0.0.1:42940 <http://127.0.0.1:42940>> <http://127.0.0.1:42940
> <http://127.0.0.1:42940>>
> > > > <http://127.0.0.1:42940 <http://127.0.0.1:42940>>
> > > > > <http://127.0.0.1:42940 <http://127.0.0.1:42940>>
> > > > > > <http://127.0.0.1:42940 <http://127.0.0.1:42940>>. Username: null; SSL
> > > > > > > Exception in thread "main" javax.jms.JMSSecurityException: AMQ229031: Unable to validate user from
> > > /127.0.0.1:42940 <http://127.0.0.1:42940> <http://127.0.0.1:42940 <http://127.0.0.1:42940>> <http://127.0.0.1:42940
> <http://127.0.0.1:42940>>
> > > > <http://127.0.0.1:42940 <http://127.0.0.1:42940>>
> > > > > <http://127.0.0.1:42940 <http://127.0.0.1:42940>>
> > > > > > > certificate subject DN: unavailable
> > > > > > > at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:464)
> > > > > > > at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:358)
> > > > > > > at
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:300)
> > > > > > > at
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:249)
> > > > > > > at
> > > > > >
> > > org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionChannel(ClientSessionFactoryImpl.java:1348)
> > > > > > > at
> > > > > >
> > > org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:673)
> > > > > > > at
> > > > > > org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:298)
> > > > > > > at org.apache.activemq.artemis.jms.client.ActiveMQConnection.authorize(ActiveMQConnection.java:684)
> > > > > > > at
> > > > > >
> > > org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:920)
> > > > > > > at
> > > org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:299)
> > > > > > > at
> > > org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:294)
> > > > > > > at org.profsoftsvcs.dpsrtest.test.main(test.java:114)
> > > > > > > Caused by: ActiveMQSecurityException[errorType=SECURITY_EXCEPTION message=AMQ229031: Unable to validate user from
> > > > > > /127.0.0.1:42940 <http://127.0.0.1:42940> <http://127.0.0.1:42940 <http://127.0.0.1:42940>> <http://127.0.0.1:42940
> <http://127.0.0.1:42940>> <http://127.0.0.1:42940 <http://127.0.0.1:42940>> <http://127.0.0.1:42940 <http://127.0.0.1:42940>>
> > > > > > > at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:464)
> > > > > > > at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:358)
> > > > > > > at
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:300)
> > > > > > > at
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQClientProtocolManager.createSessionContext(ActiveMQClientProtocolManager.java:249)
> > > > > > > at
> > > > > >
> > > org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionChannel(ClientSessionFactoryImpl.java:1348)
> > > > > > > at
> > > > > >
> > > org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:673)
> > > > > > > at
> > > > > > org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:298)
> > > > > > > at org.apache.activemq.artemis.jms.client.ActiveMQConnection.authorize(ActiveMQConnection.java:684)
> > > > > > > at
> > > > > >
> > > org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:920)
> > > > > > > at
> > > org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:299)
> > > > > > > at
> > > org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:294)
> > > > > > > at org.profsoftsvcs.dpsrtest.test.main(test.java:114)
> > > > > > > Caused by: ActiveMQSecurityException[errorType=SECURITY_EXCEPTION message=AMQ229031: Unable to validate user from
> > > > > > /127.0.0.1:42940 <http://127.0.0.1:42940> <http://127.0.0.1:42940 <http://127.0.0.1:42940>> <http://127.0.0.1:42940
> > <http://127.0.0.1:42940 <http://127.0.0.1:42940>>.
> > > > > <http://127.0.0.1:8080 <http://127.0.0.1:8080>>");
> > > > > > > InitialContext jndiContext = new InitialContext(env);
> > > > > > >
> > > > > > > BUT since you are using security maybe something is wrongly configured there for you.
> > > > > > > Try disabling the broker security to check that this is not it too.
> > > > > > > Cheers,
> > > > > > > Emmanuel
> > > > > > >
> > > > > > > Le 21/09/2020 à 15:53, Jo Ann Griffin a écrit :
> > > > > > > > Yes, it contains:
> > > > > > > >
> > > > > > > > # Copyright 2018 Red Hat, Inc.
> > > > > > > > #
> > > > > > > > # Licensed under the Apache License, Version 2.0 (the "License");
> > > > > > > > # you may not use this file except in compliance with the License.
> > > > > > > > # You may obtain a copy of the License at
> > > > > > > > #
> > > > > > > > # http://www.apache.org/licenses/LICENSE-2.0 <http://www.apache.org/licenses/LICENSE-2.0>
> > > > > > >
> > > > > > > BUT since you are using security maybe something is wrongly configured there for you.
> > > > > > > Try disabling the broker security to check that this is not it too.
> > > > > > > Cheers,
> > > > > > > Emmanuel
> > > > > > >
> > > > > > > Le 21/09/2020 à 15:53, Jo Ann Griffin a écrit :
> > > > > > > > Yes, it contains:
> > > > > > > >
> > > > > > > > # Copyright 2018 Red Hat, Inc.
> > > > > > > > #
> > > > > > > > # Licensed under the Apache License, Version 2.0 (the "License");
> > > > > > > > # you may not use this file except in compliance with the License.
> > > > > > > > # You may obtain a copy of the License at
> > > > > > > > #
> <https://groups.google.com/d/msgid/wildfly/33f8c57b-7ace-429c-8ded-7f7d009f1478n%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
> >
> > >
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > You received this message because you are subscribed to the Google Groups "WildFly" group.
> > > > > > > > To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> > > > > > > > <mailto:wildfly+u...@googlegroups.com>.
> > > > > > > > To view this discussion on the web visit
> > > > > > > > https://groups.google.com/d/msgid/wildfly/1c6cc81d-c317-4a7e-a7ee-57a21aad0145n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/1c6cc81d-c317-4a7e-a7ee-57a21aad0145n%40googlegroups.com>
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> <https://groups.google.com/d/msgid/wildfly/1c6cc81d-c317-4a7e-a7ee-57a21aad0145n%40googlegroups.com?utm_medium=email&utm_source=footer
>
> >
> > >
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > You received this message because you are subscribed to the Google Groups "WildFly" group.
> > > > > > > > To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> > > > > > > > <mailto:wildfly+u...@googlegroups.com>.
> > > > > > > > To view this discussion on the web visit
> > > > > > > > https://groups.google.com/d/msgid/wildfly/1c6cc81d-c317-4a7e-a7ee-57a21aad0145n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/1c6cc81d-c317-4a7e-a7ee-57a21aad0145n%40googlegroups.com>
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> <https://groups.google.com/d/msgid/wildfly/1c6cc81d-c317-4a7e-a7ee-57a21aad0145n%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
> >
> > >
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > You received this message because you are subscribed to the Google Groups "WildFly" group.
> > > > > > > To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> > > > > > > <mailto:wildfly+u...@googlegroups.com>.
> > > > > > > To view this discussion on the web visit
> > > > > > > https://groups.google.com/d/msgid/wildfly/9f8cb8fe-d5ac-4c55-8047-ce4d5df6ad8bn%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/9f8cb8fe-d5ac-4c55-8047-ce4d5df6ad8bn%40googlegroups.com>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> <https://groups.google.com/d/msgid/wildfly/9f8cb8fe-d5ac-4c55-8047-ce4d5df6ad8bn%40googlegroups.com?utm_medium=email&utm_source=footer
>
> >
> > >
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > You received this message because you are subscribed to the Google Groups "WildFly" group.
> > > > > > > To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> > > > > > > <mailto:wildfly+u...@googlegroups.com>.
> > > > > > > To view this discussion on the web visit
> > > > > > > https://groups.google.com/d/msgid/wildfly/9f8cb8fe-d5ac-4c55-8047-ce4d5df6ad8bn%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/9f8cb8fe-d5ac-4c55-8047-ce4d5df6ad8bn%40googlegroups.com>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> <https://groups.google.com/d/msgid/wildfly/9f8cb8fe-d5ac-4c55-8047-ce4d5df6ad8bn%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
> >
> > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > You received this message because you are subscribed to the Google Groups "WildFly" group.
> > > > > > To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> > > > > > <mailto:wildfly+u...@googlegroups.com>.
> > > > > > To view this discussion on the web visit
> > > > > > https://groups.google.com/d/msgid/wildfly/73435c52-b209-4f35-b57f-e6694fb90f41n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/73435c52-b209-4f35-b57f-e6694fb90f41n%40googlegroups.com>
> > > > > >
> > > > >
> > > >
> > >
> >
> <https://groups.google.com/d/msgid/wildfly/73435c52-b209-4f35-b57f-e6694fb90f41n%40googlegroups.com?utm_medium=email&utm_source=footer
>
> >
> > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > You received this message because you are subscribed to the Google Groups "WildFly" group.
> > > > > > To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> > > > > > <mailto:wildfly+u...@googlegroups.com>.
> > > > > > To view this discussion on the web visit
> > > > > > https://groups.google.com/d/msgid/wildfly/73435c52-b209-4f35-b57f-e6694fb90f41n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/73435c52-b209-4f35-b57f-e6694fb90f41n%40googlegroups.com>
> > > > > >
> > > > >
> > > >
> > >
> >
> <https://groups.google.com/d/msgid/wildfly/73435c52-b209-4f35-b57f-e6694fb90f41n%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
> >
> > >
> > > > >
> > > > >
> > > > > --
> > > > > You received this message because you are subscribed to the Google Groups "WildFly" group.
> > > > > To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> > > > > <mailto:wildfly+u...@googlegroups.com>.
> > > > > To view this discussion on the web visit
> > > > > https://groups.google.com/d/msgid/wildfly/9a436904-9b87-4ec8-858b-796e07d53f8en%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/9a436904-9b87-4ec8-858b-796e07d53f8en%40googlegroups.com>
> > > > >
> > > >
> > >
> >
> <https://groups.google.com/d/msgid/wildfly/9a436904-9b87-4ec8-858b-796e07d53f8en%40googlegroups.com?utm_medium=email&utm_source=footer
>
> >
> > >
> > > > >
> > > > >
> > > > > --
> > > > > You received this message because you are subscribed to the Google Groups "WildFly" group.
> > > > > To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> > > > > <mailto:wildfly+u...@googlegroups.com>.
> > > > > To view this discussion on the web visit
> > > > > https://groups.google.com/d/msgid/wildfly/9a436904-9b87-4ec8-858b-796e07d53f8en%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/9a436904-9b87-4ec8-858b-796e07d53f8en%40googlegroups.com>
> > > > >
> > > >
> > >
> >
> <https://groups.google.com/d/msgid/wildfly/9a436904-9b87-4ec8-858b-796e07d53f8en%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
> >
> > >
> > > >
> > > > --
> > > > You received this message because you are subscribed to the Google Groups "WildFly" group.
> > > > To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> > > > <mailto:wildfly+u...@googlegroups.com>.
> > > > To view this discussion on the web visit
> > > > https://groups.google.com/d/msgid/wildfly/d4811dc2-8a11-4768-80a9-d427b76ffbccn%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/d4811dc2-8a11-4768-80a9-d427b76ffbccn%40googlegroups.com>
> > > >
> > >
> >
> <https://groups.google.com/d/msgid/wildfly/d4811dc2-8a11-4768-80a9-d427b76ffbccn%40googlegroups.com?utm_medium=email&utm_source=footer
>
> >
> > >
> > > >
> > > > --
> > > > You received this message because you are subscribed to the Google Groups "WildFly" group.
> > > > To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> > > > <mailto:wildfly+u...@googlegroups.com>.
> > > > To view this discussion on the web visit
> > > > https://groups.google.com/d/msgid/wildfly/d4811dc2-8a11-4768-80a9-d427b76ffbccn%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/d4811dc2-8a11-4768-80a9-d427b76ffbccn%40googlegroups.com>
> > > >
> > >
> >
> <https://groups.google.com/d/msgid/wildfly/d4811dc2-8a11-4768-80a9-d427b76ffbccn%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
> >
> > >
> > >
> > >
> > > --
> > > You received this message because you are subscribed to the Google Groups "WildFly" group.
> > > To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> > > <mailto:wildfly+u...@googlegroups.com>.
> > > To view this discussion on the web visit
> > > https://groups.google.com/d/msgid/wildfly/4a376696-53d5-4aa6-9b25-345847ea4a0fn%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/4a376696-53d5-4aa6-9b25-345847ea4a0fn%40googlegroups.com>
> > >
> >
> <https://groups.google.com/d/msgid/wildfly/4a376696-53d5-4aa6-9b25-345847ea4a0fn%40googlegroups.com?utm_medium=email&utm_source=footer
>
> >
> > >
> > >
> > >
> > > --
> > > You received this message because you are subscribed to the Google Groups "WildFly" group.
> > > To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> > > <mailto:wildfly+u...@googlegroups.com>.
> > > To view this discussion on the web visit
> > > https://groups.google.com/d/msgid/wildfly/4a376696-53d5-4aa6-9b25-345847ea4a0fn%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/4a376696-53d5-4aa6-9b25-345847ea4a0fn%40googlegroups.com>
> > >
> >
> <https://groups.google.com/d/msgid/wildfly/4a376696-53d5-4aa6-9b25-345847ea4a0fn%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
> >
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups "WildFly" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> > <mailto:wildfly+u...@googlegroups.com>.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/wildfly/615f0b1e-e9e1-49c2-8e8a-ece1d57bbdc9n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/615f0b1e-e9e1-49c2-8e8a-ece1d57bbdc9n%40googlegroups.com>
> >
> <https://groups.google.com/d/msgid/wildfly/615f0b1e-e9e1-49c2-8e8a-ece1d57bbdc9n%40googlegroups.com?utm_medium=email&utm_source=footer
>
> >
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups "WildFly" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> > <mailto:wildfly+u...@googlegroups.com>.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/wildfly/615f0b1e-e9e1-49c2-8e8a-ece1d57bbdc9n%40googlegroups.com
> <https://groups.google.com/d/msgid/wildfly/615f0b1e-e9e1-49c2-8e8a-ece1d57bbdc9n%40googlegroups.com>
> >
> <https://groups.google.com/d/msgid/wildfly/615f0b1e-e9e1-49c2-8e8a-ece1d57bbdc9n%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "WildFly" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> <mailto:wildfly+u...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/wildfly/717fc13d-9fde-4b46-b88d-d5e42fee9b1cn%40googlegroups.com
>
>
> --
> You received this message because you are subscribed to the Google Groups "WildFly" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> <mailto:wildfly+u...@googlegroups.com>.
> To view this discussion on the web visit
> <https://groups.google.com/d/msgid/wildfly/717fc13d-9fde-4b46-b88d-d5e42fee9b1cn%40googlegroups.com?utm_medium=email&utm_source=footer>.
Frank Griffin
Oct 14, 2020, 11:33:57 AM10/14/20
to WildFly
Hi Emmanuel,
I'd put this in the JIRA except JIRA is suddenly throwing exceptions in Firefox and won't let me comment there.
You're mixing use cases. The use case in the JIRA does not involve me creating a Queue called test1. It uses the predefined DLQ Queue that comes with the distribution. The only modification to the distro in the JIRA is to define a user with users.sh, and that's probably not necessary since the test case does not create a Connection which would require authentication. The point of this is that the JIRA case uses an unmodifed standalone-full.xml, as shipped (adding the user only affects the user files outside of standalone-full.xml).
Please reopen the JIRA (I would if I could) and try the use case as included there.
Thanks,
Frank
Emmanuel Hugonnet
Oct 14, 2020, 12:14:21 PM10/14/20
to Frank Griffin, WildFly
Then the Jira reproducer is wrong as it uses String szDestPrimary = "jms/queue/test1";
Cheers,
Emmanuel
Le 14/10/2020 à 17:33, Frank Griffin a écrit :
> Hi Emmanuel,
>
> > <http://127.0.0.1:42940 <http://127.0.0.1:42940>>> <http://127.0.0.1:42940 <http://127.0.0.1:42940> <http://127.0.0.1:42940
> > > > <http://127.0.0.1:8080 <http://127.0.0.1:8080> <http://127.0.0.1:8080 <http://127.0.0.1:8080>>> <http://127.0.0.1:8080
> <https://groups.google.com/d/msgid/wildfly/717fc13d-9fde-4b46-b88d-d5e42fee9b1cn%40googlegroups.com?utm_medium=email&utm_source=footer
> <https://groups.google.com/d/msgid/wildfly/717fc13d-9fde-4b46-b88d-d5e42fee9b1cn%40googlegroups.com?utm_medium=email&utm_source=footer>>.
> <https://groups.google.com/d/msgid/wildfly/1846b438-066e-4aac-91b2-0a2e482defb0n%40googlegroups.com?utm_medium=email&utm_source=footer>.
Cheers,
Emmanuel
Le 14/10/2020 à 17:33, Frank Griffin a écrit :
> Hi Emmanuel,
>
> <http://127.0.0.1:42940>>> <http://127.0.0.1:42940 <http://127.0.0.1:42940> <http://127.0.0.1:42940 <http://127.0.0.1:42940>>>
> <https://groups.google.com/d/msgid/wildfly/717fc13d-9fde-4b46-b88d-d5e42fee9b1cn%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
> --
> You received this message because you are subscribed to the Google Groups "WildFly" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> <mailto:wildfly+u...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/wildfly/1846b438-066e-4aac-91b2-0a2e482defb0n%40googlegroups.com
> --
> You received this message because you are subscribed to the Google Groups "WildFly" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com
> <mailto:wildfly+u...@googlegroups.com>.
> To view this discussion on the web visit
> <https://groups.google.com/d/msgid/wildfly/1846b438-066e-4aac-91b2-0a2e482defb0n%40googlegroups.com?utm_medium=email&utm_source=footer>.
Reply all
Reply to author
Forward
0 new messages