[ 
https://issues.apache.org/jira/browse/ARTEMIS-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198323#comment-17198323
 ] 

Justin Bertram edited comment on ARTEMIS-2905 at 9/18/20, 1:27 PM:
-------------------------------------------------------------------

Apache Camel team says below.

bq. It smells like an Artemis security issue where you cant establish a 
connection. It reports null in username, and certificate DN unavaialbe. I 
suggest to talk to ActiveMQ Artemis team about running Artemis in Docker


was (Author: ramarajan):
Apache Camel team says below.

It smells like an Artemis security issue where you cant establish a connection. 
It reports null in username, and certificate DN unavaialbe. I suggest to talk 
to ActiveMQ Artemis team about running Artemis in Docker

> Multiple jms component Consumers is throwing  Connection error when 
> connecting to Artemis broker inside docker container
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-2905
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2905
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: OpenWire
>    Affects Versions: 2.13.0
>            Reporter: Ramarajan R
>            Priority: Minor
>         Attachments: Camel+Artemis with 1 consumer, Camel+Artemis with 2 
> consumer, artemis-core-consumer.zip, camel-artemis.zip
>
>
> We are connecting to Artemis broker (2.13.0) deployed in Docker Container 
> using Camel JMS Component (Version 2.25.1).
> When we have multiple consumer routes we are facing below exception:
> {noformat}
> ActiveMQSecurityException[errorType=SECURITY_EXCEPTION message=AMQ229031: 
> Unable to validate user from /host:52202. Username: null; SSL certificate 
> subject DN: unavailable
> {noformat}
> {noformat}
> DEBUG org.apache.camel.component.jms.DefaultJmsMessageListenerContainer  - 
> Could not establish shared JMS Connection - leaving it up to asynchronous 
> invokers to establish a Connection as soon as possible
> javax.jms.JMSSecurityException: AMQ229031: Unable to validate user from 
> /localhost:52486. Username: null; SSL certificate subject DN: unavailable
>         at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:467)
>         at 
> org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:361)
>         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:1366)
>         at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:691)
>         at 
> org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:316)
>         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)
> {noformat}
> The same works when we have single consumer routes. When we connect to a 
> standalone broker both single and multiple consumer route works
> When I use Artemis core library with plain Java classes without Camel JMS 
> component then we are able to make connection for more than 1 consumer.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to