Details
-
Bug
-
Resolution: Done
-
Blocker
-
None
Description
This is regression against EAP 7.0 . Customers relying on this feature won't be able to migrate to EAP 7.1.
Working configuration of TLS between domain and host controller from EAP 7.0 (legacy) does not work on EAP 7.1 anymore.
In server log there is this error:
server.log
[Host Controller] Caused by: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL [Host Controller] at org.jboss.remoting3.remote.ClientConnectionOpenListener$StartTls.handleEvent(ClientConnectionOpenListener.java:527) [Host Controller] at org.jboss.remoting3.remote.ClientConnectionOpenListener$StartTls.handleEvent(ClientConnectionOpenListener.java:477) [Host Controller] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [Host Controller] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [Host Controller] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) [Host Controller] at org.xnio.nio.WorkerThread.run(WorkerThread.java:567) [Host Controller] at ...asynchronous invocation...(Unknown Source) [Host Controller] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:466) [Host Controller] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:437) [Host Controller] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:430) [Host Controller] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:163) [Host Controller] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:119) [Host Controller] ... 9 more
See attached server.log for context log.
Tests in wildfly-core covering this scenario are currently ignored:
- SSLMasterSlaveOneWayTestCase is ignored by
WFCORE-1978 - SSLMasterSlaveTwoWayTestCase is ignored by
WFCORE-2068
Attachments
Issue Links
- clones
-
-
- Verified
-
