-
Bug
-
Resolution: Done
-
Critical
-
11.0.0.Alpha1
If server is configured to authenticate JMS client with SSL configured using Elytron SSLContext then if client is using IBM JDK 8, authentication fails with:
ERROR: AMQ214016: Failed to create netty connection java.nio.channels.ClosedChannelException at io.netty.handler.ssl.SslHandler.channelInactive(...)(Unknown Source) Producer got exception and ended:javax.jms.JMSException: Failed to create session factory javax.jms.JMSException: Failed to create session factory at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:757) at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:265) at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:260) at ProducerTransSession.run(ProducerTransSession.java:75) Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:787) at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:755) ... 3 more
If client uses Oracle JDK 8 or SSL authentication is configured on http listener using PicketBox then client connects successfully.
Issue is under investigation.
- causes
-
WFLY-11200 Messaging-activemq integration code alters the JMS client's enabled protocols via TransportConfiguration
- Closed
- clones
-
JBEAP-11765 JMS client fails to connect with SSL on IBM JDK 8
- Closed
- is blocked by
-
WFLY-9407 Upgrade Artemis 2.6.3.jbossorg-001
- Closed
-
ARTEMIS-1299 Loading...