Failed to connect to the controller

JBoss Issue Tracker | Wolf-Dieter Fink | 3 years ago
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    If a standalone server is started with a binding port-offset it is not possible to connect to the native management interface. To reproduce start a WildFly Beta server (Alpha3 has the same problem) bin/ -Djboss.socket.binding.port-offset=100 and a cli client: bin/ -c --controller=localhost:10099 It makes no difference whether the port is changed by port-offset or configuration. All other ports (i.e. 10090 8180) can be used correct for http-management or ejb invocation. The server log an ERROR message: ERROR [org.jboss.remoting.remote.connection] (Remoting "home:MANAGEMENT" I/O-1) JBREM000200: Remote connection failed: XNIO000804: Received an invalid message length of 1195725856 The client show: Failed to connect to the controller at at at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( at sun.reflect.DelegatingMethodAccessorImpl.invoke( at java.lang.reflect.Method.invoke( at at org.jboss.modules.Main.main( Caused by: The controller is not available at localhost:10099 at at at at ... 8 more Caused by: JBAS012174: Could not connect to http-remoting://localhost:10099. The connection failed at at at ... 11 more Caused by: JBAS012174: Could not connect to http-remoting://localhost:10099. The connection failed at at$EstablishingConnection.connect( at at$Establishing.getChannel( at at$2.getChannel( at at at at at ... 13 more Caused by: XNIO000812: Connection closed unexpectedly at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent( at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent( at org.xnio.ChannelListeners.invokeChannelListener( at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady( at org.xnio.nio.NioSocketConduit.handleReady( at at ...asynchronous invocation...(Unknown Source) at org.jboss.remoting3.EndpointImpl.doConnect( at org.jboss.remoting3.EndpointImpl.doConnect( at org.jboss.remoting3.EndpointImpl.connect( at org.jboss.remoting3.EndpointImpl.connect( at at ... 23 more

    JBoss Issue Tracker | 3 years ago | Wolf-Dieter Fink Failed to connect to the controller
  2. 0

    Gradle-Cargo-Plugin fails when deploying to remote wildfly using ssl

    Stack Overflow | 2 years ago XNIO000812: Connection closed unexpectedly

    Root Cause Analysis


      XNIO000812: Connection closed unexpectedly

      at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent()
    2. org.xnio.http
      1. org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(
      2. org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(
      2 frames
    3. XNIO API
      1. org.xnio.ChannelListeners.invokeChannelListener(
      1 frame
    4. org.xnio.conduits
      1. org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(
      1 frame
    5. XNIO NIO Implementation
      1. org.xnio.nio.NioSocketConduit.handleReady(
      2 frames