-
Bug
-
Resolution: Won't Do
-
Major
-
7.0.8.GA
-
None
-
-
-
-
-
-
+
-
- install IBM JDK 1.8
- copy host.xml, server.keystore, server.truststore to domain/configuration
- start JBoss in domain mode (./bin/domain.sh)
When using EAP 7.0.8 in domain mode and using SSL with mutual auth, the server instances cannot connect to the host controller.
The server instances will timeout and log the following error:
2017-11-17 09:09:42,439 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool – 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service.StartException in service jboss.server-boot-operations: java.net.ConnectException: WFLYPRT0023: Could not connect to https-remoting://127.0.0.1:9990. The connection timed out
at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.lang.Thread.run(Thread.java:795)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.net.ConnectException: WFLYPRT0023: Could not connect to https-remoting://127.0.0.1:9990. The connection timed out
at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:124)
at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:257)
at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:71)
at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128)
at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:104)
at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68)
... 4 more
2017-11-17 09:09:42,440 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: java.util.concurrent.ExecutionException: Operation failed
at org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:185)
at org.jboss.as.server.ServerService.boot(ServerService.java:362)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:301)
at java.lang.Thread.run(Thread.java:795)
Caused by: java.util.concurrent.ExecutionException: Operation failed
at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268)
at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:113)
at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:95)
at org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:182)
... 3 more
Caused by: java.net.ConnectException: WFLYPRT0023: Could not connect to https-remoting://127.0.0.1:9990. The connection timed out
at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:124)
at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:257)
at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:71)
at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128)
at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:104)
at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.lang.Thread.run(Thread.java:795)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
This does not happen on 7.0.8 with the Oracle 1.8 JDK. This does not happen on 7.0.7 with the IBM 1.8 JDK.
Copying jboss-remoting-4.0.23.Final-redhat-1.jar from 7.0.7 to 7.0.8 resolves the issue.
- is caused by
-
JBEAP-10156 [GSS](7.0.z) Authentication via remoting fail for larger requests i.e. long password
- Closed
- relates to
-
REM3-318 RemotingMessageChannel, invalid return value when reading length
- Resolved