1 Reply Latest reply on Apr 6, 2018 1:25 AM by Prageetika Sharma

    JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

    jack_tauson_sr Newbie

      I am getting an error while starting JBoss AS 7.1.1 from Eclipse.

       

      Does this mean that I can ignore this error and do my work as I saw the message that the server was started?  I came across this thread but could not figure out from where to kill another process. I am on Windows 7. I  have WildFly installed and I don't see this error while starting it from eclipse. I installed WildFly first and then JBoss AS 7.1.1

       

      Here is the server log:

       

      11:43:44,175 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem

      11:43:44,310 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem

      11:43:44,320 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

      11:43:44,242 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem

      11:43:44,349 INFO  [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.7.Final

      11:43:44,240 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.

      11:43:44,395 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

      11:43:44,469 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

      11:43:44,780 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA

      11:43:44,827 INFO  [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

      11:43:44,840 INFO  [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service

      11:43:44,994 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]

      11:43:45,256 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080

      11:43:46,044 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory D:\Users\akhare\jboss-as-7.1.1.Final\standalone\deployments

      11:43:46,057 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on localhost/127.0.0.1:4447

      11:43:46,058 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on localhost/127.0.0.1:9999

      11:43:46,209 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:43:46,341 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

      11:43:46,472 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

      11:43:46,473 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 5008ms - Started 133 of 208 services (74 services are passive or on-demand)

      11:43:46,533 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:43:47,750 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:43:48,068 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:43:49,294 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:43:49,605 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:43:50,830 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:43:51,143 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:43:52,366 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:43:52,677 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:44:27,054 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:44:27,117 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:44:27,237 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:44:27,255 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:44:28,780 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:44:28,798 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:44:30,316 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:44:30,343 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:44:31,853 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:44:31,891 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:44:33,387 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:44:33,427 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:45:11,659 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:45:11,717 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:45:59,945 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

      11:45:59,949 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem

      11:45:59,959 INFO  [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.7.Final

      11:45:59,976 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

      11:45:59,992 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.

      11:46:00,227 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

      11:46:00,327 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem

      11:46:00,341 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem

      11:46:00,426 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-2) JBoss Web Services - Stack CXF Server 4.0.2.GA

      11:46:00,443 INFO  [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

      11:46:00,631 INFO  [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service

      11:46:00,777 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080

      11:46:00,879 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]

      11:46:01,459 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory D:\Users\akhare\jboss-as-7.1.1.Final\standalone\deployments

      11:46:01,464 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on localhost/127.0.0.1:4447

      11:46:01,471 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost/127.0.0.1:9999

      11:46:01,740 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:46:01,741 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

      11:46:01,846 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:46:01,873 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

      11:46:01,874 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 5490ms - Started 133 of 208 services (74 services are passive or on-demand)

      11:46:03,444 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:46:03,446 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:46:05,209 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:46:05,437 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:46:06,748 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:46:06,978 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:46:08,284 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      11:46:08,968 ERROR [org.jboss.remoting.remote.connection] (Remoting "vc5webgrpwi0010:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

       

      Here is the boot.log:

       

      11:45:56,950 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

      11:45:57,584 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

      11:45:57,700 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

      11:45:57,702 DEBUG [org.jboss.as.config] Configured system properties:

      awt.toolkit = sun.awt.windows.WToolkit

      file.encoding = Cp1252

      file.encoding.pkg = sun.io

      file.separator = \

      java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment

      java.awt.headless = true

      java.awt.printerjob = sun.awt.windows.WPrinterJob

      java.class.path = D:\Users\akhare\jboss-as-7.1.1.Final\jboss-modules.jar

      java.class.version = 51.0

      java.endorsed.dirs = C:\Program Files\Java\jdk1.7.0_80\jre\lib\endorsed

      java.ext.dirs = C:\Program Files\Java\jdk1.7.0_80\jre\lib\ext;C:\Windows\Sun\Java\lib\ext

      java.home = C:\Program Files\Java\jdk1.7.0_80\jre

      java.io.tmpdir = d:\Users\akhare\AppData\Local\Temp\

      java.library.path = C:\Program Files\Java\jdk1.7.0_80\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;native;d:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Git\cmd;C:\Program Files\TortoiseGit\bin;D:\Users\akhare\Downloads\apache-maven-3.5.0\bin;C:\Program Files\nodejs\;d:\Users\akhare\AppData\Local\atom\bin;d:\Users\akhare\AppData\Roaming\npm;C:\Program Files (x86)\SSH Communications Security\SSH Secure Shell;.

      java.net.preferIPv4Stack = true

      java.runtime.name = Java(TM) SE Runtime Environment

      java.runtime.version = 1.7.0_80-b15

      java.specification.name = Java Platform API Specification

      java.specification.vendor = Oracle Corporation

      java.specification.version = 1.7

      java.util.logging.manager = org.jboss.logmanager.LogManager

      java.vendor = Oracle Corporation

      java.vendor.url = http://java.oracle.com/

      java.vendor.url.bug = http://bugreport.sun.com/bugreport/

      java.version = 1.7.0_80

      java.vm.info = mixed mode

      java.vm.name = Java HotSpot(TM) 64-Bit Server VM

      java.vm.specification.name = Java Virtual Machine Specification

      java.vm.specification.vendor = Oracle Corporation

      java.vm.specification.version = 1.7

      java.vm.vendor = Oracle Corporation

      java.vm.version = 24.80-b11

      javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder

      javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory

      javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory

      javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory

      javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory

      javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory

      javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory

      javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory

      javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory

      javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory

      jboss.bind.address = localhost

      jboss.bind.address.management = localhost

      jboss.home.dir = D:\Users\akhare\jboss-as-7.1.1.Final

      jboss.host.name = vc5webgrpwi0010

      jboss.modules.dir = D:\Users\username\jboss-as-7.1.1.Final\modules

      jboss.modules.system.pkgs = org.jboss.byteman

      jboss.node.name = vc5webgrpwi0010

      jboss.qualified.host.name = vc5webgrpwi0010

      jboss.server.base.dir = D:\Users\username\jboss-as-7.1.1.Final\standalone

      jboss.server.config.dir = D:\Users\username\jboss-as-7.1.1.Final\standalone\configuration

      jboss.server.data.dir = D:\Users\username\jboss-as-7.1.1.Final\standalone\data

      jboss.server.deploy.dir = D:\Users\username\jboss-as-7.1.1.Final\standalone\data\content

      jboss.server.log.dir = D:\Users\username\jboss-as-7.1.1.Final\standalone\log

      jboss.server.name = vc5webgrpwi0010

      jboss.server.temp.dir = D:\Users\username\jboss-as-7.1.1.Final\standalone\tmp

      line.separator =

       

       

      logging.configuration = file:/D:/Users/username/jboss-as-7.1.1.Final/standalone/configuration/logging.properties

      module.path = D:/Users/username/jboss-as-7.1.1.Final/modules

      org.jboss.boot.log.file = D:/Users/username/jboss-as-7.1.1.Final/standalone/log/boot.log

      org.jboss.resolver.warning = true

      org.xml.sax.driver = __redirected.__XMLReaderFactory

      os.arch = amd64

      os.name = Windows 7

      os.version = 6.1

      path.separator = ;

      program.name = JBossTools: JBoss AS 7.1

      sun.arch.data.model = 64

      sun.boot.class.path = C:\Program Files\Java\jdk1.7.0_80\jre\lib\resources.jar;C:\Program Files\Java\jdk1.7.0_80\jre\lib\rt.jar;C:\Program Files\Java\jdk1.7.0_80\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.7.0_80\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.7.0_80\jre\lib\jce.jar;C:\Program Files\Java\jdk1.7.0_80\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.7.0_80\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.7.0_80\jre\classes

      sun.boot.library.path = C:\Program Files\Java\jdk1.7.0_80\jre\bin

      sun.cpu.endian = little

      sun.cpu.isalist = amd64

      sun.desktop = windows

      sun.io.unicode.encoding = UnicodeLittle

      sun.java.command = org.jboss.modules.Main -mp D:/Users/username/jboss-as-7.1.1.Final/modules -jaxpmodule javax.xml.jaxp-provider -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=D:\Users\username\jboss-as-7.1.1.Final\standalone

      sun.java.launcher = SUN_STANDARD

      sun.jnu.encoding = Cp1252

      sun.management.compiler = HotSpot 64-Bit Tiered Compilers

      sun.os.patch.level = Service Pack 1

      sun.rmi.dgc.client.gcInterval = 3600000

      sun.rmi.dgc.server.gcInterval = 3600000

      user.country = US

      user.dir = D:\Users\username\jboss-as-7.1.1.Final\bin

      user.home = \\hnas1-users\USERS\username

      user.language = en

      user.name = username

      user.script =

      user.timezone = America/Chicago

      user.variant =

      11:45:57,720 DEBUG [org.jboss.as.config] VM Arguments: -Dprogram.name=JBossTools: JBoss AS 7.1 -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=D:/Users/username/jboss-as-7.1.1.Final/standalone/log/boot.log -Dlogging.configuration=file:/D:/Users/username/jboss-as-7.1.1.Final/standalone/configuration/logging.properties -Djboss.home.dir=D:/Users/username/jboss-as-7.1.1.Final -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252

      11:45:59,803 INFO  [org.xnio] XNIO Version 3.0.3.GA

      11:45:59,804 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

      11:45:59,816 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

      11:45:59,827 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA

      11:45:59,928 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

        • 1. Re: JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856
          Prageetika Sharma Newbie

          This error is normal if someone tries to access port 9999 (Native Management Port) or 4447 (remoting port) from anything other than a JBoss Remoting 3 client.

           

          1) The simplest solution is to find out what hosts are sending non-remoting data to JBoss Remoting ports (9999 and 4447) and stop them from doing so.

           

          To find Process ID of process that uses a Port in Windows you can use netstat command as :

           

          ++++++++++

          netstat -ano | findstr 9999

          ++++++++++

           

          And once you have identified the process PID, you can kill the process with taskkill command as :

           

          ++++++++++

          taskkill /F /PID 12345

          ++++++++++

           

          2) This error message is common with users who try to connect to JBoss from JConsole using only the host and port e.g. hostname:9999. Instead, you need to utilize the JBoss JMX Remoting protocol as:

           

          ++++++++++

          service:jmx:remoting-jmx://hostname:9999

          ++++++++++

           

          3) Or as a workaround you can edit your configuration file to use different ports (management-http/management-https/management-native).