1 2 Previous Next 16 Replies Latest reply on Jun 4, 2016 6:47 AM by Wolfgang Mayer

    Wildfly 10 remote connection issue

    Mike Brooks Newbie

      I am using Wildfly-10.0.0.Final.

       

      I think I am trying to use a RMI connection to Wildfly running as a localhost.  (relative newbie following tutorial)

       

      When I started Wildfly, I got the following:

      ....

      2016-05-31 21:26:31,819 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'EmployeeManagementImplementation' in deployment unit 'deployment "EmployeeManagementServerApplication.jar"' are as follows:

       

          java:global/EmployeeManagementServerApplication/EmployeeManagementImplementation!com.vpp_wildfly.employeemanagement.EmployeeManagementService

          java:app/EmployeeManagementServerApplication/EmployeeManagementImplementation!com.vpp_wildfly.employeemanagement.EmployeeManagementService

          java:module/EmployeeManagementImplementation!com.vpp_wildfly.employeemanagement.EmployeeManagementService

         java:jboss/exported/EmployeeManagementServerApplication/EmployeeManagementImplementation!com.vpp_wildfly.employeemanagement.EmployeeManagementService

          java:global/EmployeeManagementServerApplication/EmployeeManagementImplementation

          java:app/EmployeeManagementServerApplication/EmployeeManagementImplementation

          java:module/EmployeeManagementImplementation

       

      2016-05-31 21:26:31,986 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0006: Starting Services for CDI deployment: EmployeeManagementServerApplication.jar

      2016-05-31 21:26:31,986 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.

      2016-05-31 21:26:31,986 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.

      2016-05-31 21:26:32,002 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.

      2016-05-31 21:26:32,002 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.

      2016-05-31 21:26:32,119 INFO  [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 2.3.2 (Final)

      2016-05-31 21:26:32,140 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment EmployeeManagementServerApplication.jar

      2016-05-31 21:26:32,425 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 58) WFLYCLINF0002: Started client-mappings cache from ejb container

      2016-05-31 21:26:32,988 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "EmployeeManagementServerApplication.jar" (runtime-name : "EmployeeManagementServerApplication.jar")

      2016-05-31 21:26:33,158 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management

      2016-05-31 21:26:33,158 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

      2016-05-31 21:26:33,158 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 13334ms - Started 366 of 635 services (379 services are lazy, passive or on-demand)

       

      I then went into eclipse and did a "run as" Java application of my test client to access the above EJB.  I used the highlighted/italicized jndi name (without "java:jboss/exported/") to gain access to my EJB.

       

      Although nothing was added to my server log, I got the following in my eclipse console:

      21:37:06.696 [main] DEBUG org.jboss.logging - Logging Provider: org.jboss.logging.Slf4jLoggerProvider

      21:37:06.726 [main] DEBUG o.j.e.c.EJBClientPropertiesLoader - Looking for jboss-ejb-client.properties using classloader sun.misc.Launcher$AppClassLoader@73d16e93

      21:37:06.744 [main] DEBUG o.j.n.r.client.InitialContextFactory - Looking for jboss-naming-client.properties using classloader sun.misc.Launcher$AppClassLoader@73d16e93

      21:37:06.745 [main] DEBUG o.j.n.r.client.InitialContextFactory - jboss.naming.client.endpoint.create.options. has the following options {}

      21:37:06.746 [main] DEBUG o.j.n.r.client.InitialContextFactory - jboss.naming.client.remote.connectionprovider.create.options. has the following options {}

      21:37:06.763 [main] INFO  org.xnio - XNIO version 3.3.4.Final

      21:37:06.842 [main] INFO  org.xnio.nio - XNIO NIO Implementation Version 3.3.4.Final

      21:37:06.936 [Remoting "config-based-naming-client-endpoint" I/O-1] DEBUG org.xnio.nio - Started channel thread 'Remoting "config-based-naming-client-endpoint" I/O-1', selector sun.nio.ch.WindowsSelectorImpl@413235c8

      21:37:06.936 [Remoting "config-based-naming-client-endpoint" Accept] DEBUG org.xnio.nio - Started channel thread 'Remoting "config-based-naming-client-endpoint" Accept', selector sun.nio.ch.WindowsSelectorImpl@128d5ff6

      21:37:06.950 [main] INFO  org.jboss.remoting - JBoss Remoting version 4.0.18.Final

      21:37:06.968 [main] DEBUG o.j.n.r.client.InitialContextFactory - jboss.naming.client.connect.options. has the following options {}

      EmployeeManagementServerApplication/EmployeeManagementImplementation!com.vpp_wildfly.employeemanagement.EmployeeManagementService

      21:37:12.079 [main] DEBUG o.j.n.r.client.HaRemoteNamingStore - Failed to connect to server http-remoting://localhost:8080

      java.net.ConnectException: Operation failed with status WAITING after 5000 MILLISECONDS

          at org.jboss.naming.remote.protocol.IoFutureHelper.get(IoFutureHelper.java:97) ~[jboss-client.jar:10.0.0.Final]

          at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:198) ~[jboss-client.jar:10.0.0.Final]

          at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149) ~[jboss-client.jar:10.0.0.Final]

          at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130) ~[jboss-client.jar:10.0.0.Final]

          at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272) ~[jboss-client.jar:10.0.0.Final]

          at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104) [jboss-client.jar:10.0.0.Final]

          at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93) [jboss-client.jar:10.0.0.Final]

          at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146) [jboss-client.jar:10.0.0.Final]

          at javax.naming.InitialContext.lookup(InitialContext.java:417) [na:1.8.0_92]

          at com.vpp_wildfly.employeemanagement.Main.main(Main.java:38) [bin/:na]

      Exception in thread "main" javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [http-remoting://localhost:8080 (Operation failed with status WAITING after 5000 MILLISECONDS)] [Root exception is java.net.ConnectException: Operation failed with status WAITING after 5000 MILLISECONDS]

          at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:240)

          at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149)

          at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130)

          at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)

          at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104)

       

      I tried  "netstat -aon"

       

      Which gave me:  port 8080 with pid 10416 listening

         pid 10416 was also listening to port 9990 (so I assumed it was Wildfly)

       

      When I  did  a task manager, it said pid 10416 was java.exe.

       

      I have tried up ing the timeout parameter to 40 secs, but it just took me longer to get the  same error message.

       

      I have been knocking my head against the wall for some time, so any thoughts would be appreciated.

        • 1. Re: Wildfly 10 remote connection issue
          Wolfgang Mayer Master

          It looks like Wildfly is not listening on port 8080 for http.

          You could check this via jboss-cli

          /socket-binding-group=standard-sockets/socket-binding=http:read-attribute(name=port)

           

          in your log you should also find an entry like:

          WFLYUT0006: Undertow HTTP listener default listening on <IP-address>:8080

          • 2. Re: Wildfly 10 remote connection issue
            Mike Brooks Newbie

            2016-05-31 21:26:29,707 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080

            • 3. Re: Wildfly 10 remote connection issue
              Mike Brooks Newbie

              For completeness sake, I have added my server.log file:

               

              2016-05-31 21:26:21,241 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
              2016-05-31 21:26:22,643 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
              2016-05-31 21:26:22,759 INFO  [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting
              2016-05-31 21:26:22,775 DEBUG [org.jboss.as.config] (MSC service thread 1-6) 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.printerjob = sun.awt.windows.WPrinterJob
              java.class.path = C:\Wildfly\wildfly-10.0.0.Final\jboss-modules.jar
              java.class.version = 52.0
              java.endorsed.dirs = C:\Java\jdk1.8.0_92\jre\lib\endorsed
              java.ext.dirs = C:\Java\jdk1.8.0_92\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
              java.home = C:\Java\jdk1.8.0_92\jre
              java.io.tmpdir = C:\Users\Mike\AppData\Local\Temp\
              java.library.path = C:\Java\jdk1.8.0_92\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\Java\jdk1.8.0_77\bin;C:\WINDOWS\system32;C:\WINDOWS\system32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Maven\apache-maven-3.3.3\bin\;C:\Program Files (x86)\Groovy\groovy-2.4.1\bin;C:\Gradle\gradle-2.13\bin;C:\Nexus\nexus-2.11.4-01\bin;C:\Wildfly\Wildfly-10.0.0.Final\bin;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Microsoft JDBC Driver 4.0 for SQL Server\sqljdbc_4.1\enu;C:\Program Files (x86)\Microsoft JDBC Driver 4.0 for SQL Server\sqljdbc_4.1\enu\auth\x64\;C:\Program Files (x86)\Git\cmd;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft SQL Server\120\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\Ant\apache-ant-1.9.6\bin;C:\Program Files\IDM Computer Solutions\UltraEdit;C:\Program Files (x86)\Brackets\command;.
              java.net.preferIPv4Stack = true
              java.runtime.name = Java(TM) SE Runtime Environment
              java.runtime.version = 1.8.0_92-b14
              java.specification.name = Java Platform API Specification
              java.specification.vendor = Oracle Corporation
              java.specification.version = 1.8
              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.8.0_92
              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.8
              java.vm.vendor = Oracle Corporation
              java.vm.version = 25.92-b14
              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.home.dir = C:\Wildfly\wildfly-10.0.0.Final
              jboss.host.name = mydesktop
              jboss.modules.dir = C:\Wildfly\wildfly-10.0.0.Final\modules
              jboss.modules.system.pkgs = org.jboss.byteman
              jboss.node.name = mydesktop
              jboss.qualified.host.name = mydesktop
              jboss.server.base.dir = C:\Wildfly\wildfly-10.0.0.Final\standalone
              jboss.server.config.dir = C:\Wildfly\wildfly-10.0.0.Final\standalone\configuration
              jboss.server.data.dir = C:\Wildfly\wildfly-10.0.0.Final\standalone\data
              jboss.server.deploy.dir = C:\Wildfly\wildfly-10.0.0.Final\standalone\data\content
              jboss.server.log.dir = C:\Wildfly\wildfly-10.0.0.Final\standalone\log
              jboss.server.name = mydesktop
              jboss.server.persist.config = true
              jboss.server.temp.dir = C:\Wildfly\wildfly-10.0.0.Final\standalone\tmp
              line.separator =

              logging.configuration = file:C:\Wildfly\wildfly-10.0.0.Final\standalone\configuration/logging.properties
              module.path = C:\Wildfly\wildfly-10.0.0.Final\modules
              org.jboss.boot.log.file = C:\Wildfly\wildfly-10.0.0.Final\standalone\log\server.log
              org.jboss.resolver.warning = true
              org.xml.sax.driver = __redirected.__XMLReaderFactory
              os.arch = amd64
              os.name = Windows 10
              os.version = 10.0
              path.separator = ;
              program.name = standalone.bat
              sun.arch.data.model = 64
              sun.boot.class.path = C:\Java\jdk1.8.0_92\jre\lib\resources.jar;C:\Java\jdk1.8.0_92\jre\lib\rt.jar;C:\Java\jdk1.8.0_92\jre\lib\sunrsasign.jar;C:\Java\jdk1.8.0_92\jre\lib\jsse.jar;C:\Java\jdk1.8.0_92\jre\lib\jce.jar;C:\Java\jdk1.8.0_92\jre\lib\charsets.jar;C:\Java\jdk1.8.0_92\jre\lib\jfr.jar;C:\Java\jdk1.8.0_92\jre\classes
              sun.boot.library.path = C:\Java\jdk1.8.0_92\jre\bin
              sun.cpu.endian = little
              sun.cpu.isalist = amd64
              sun.desktop = windows
              sun.io.unicode.encoding = UnicodeLittle
              sun.java.command = C:\Wildfly\wildfly-10.0.0.Final\jboss-modules.jar -mp C:\Wildfly\wildfly-10.0.0.Final\modules org.jboss.as.standalone -Djboss.home.dir=C:\Wildfly\wildfly-10.0.0.Final
              sun.java.launcher = SUN_STANDARD
              sun.jnu.encoding = Cp1252
              sun.management.compiler = HotSpot 64-Bit Tiered Compilers
              sun.os.patch.level =
              sun.stderr.encoding = cp437
              sun.stdout.encoding = cp437
              user.country = US
              user.dir = C:\Wildfly\wildfly-10.0.0.Final\bin
              user.home = C:\Users\Mike
              user.language = en
              user.name = Mike
              user.script =
              user.timezone = America/Chicago
              user.variant =
              2016-05-31 21:26:22,775 DEBUG [org.jboss.as.config] (MSC service thread 1-6) VM Arguments: -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Dorg.jboss.boot.log.file=C:\Wildfly\wildfly-10.0.0.Final\standalone\log\server.log -Dlogging.configuration=file:C:\Wildfly\wildfly-10.0.0.Final\standalone\configuration/logging.properties -Xmx512M
              2016-05-31 21:26:28,585 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
              2016-05-31 21:26:28,638 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.3.4.Final
              2016-05-31 21:26:28,654 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.4.Final
              2016-05-31 21:26:28,716 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
              2016-05-31 21:26:28,716 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
              2016-05-31 21:26:28,716 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
              2016-05-31 21:26:28,738 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
              2016-05-31 21:26:28,738 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
              2016-05-31 21:26:28,738 INFO  [org.jboss.as.security] (MSC service thread 1-6) WFLYSEC0001: Current PicketBox version=4.9.4.Final
              2016-05-31 21:26:28,754 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
              2016-05-31 21:26:28,754 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
              2016-05-31 21:26:28,886 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0003: Undertow 1.3.15.Final starting
              2016-05-31 21:26:28,886 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.3.15.Final starting
              2016-05-31 21:26:28,917 INFO  [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final)
              2016-05-31 21:26:29,147 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
              2016-05-31 21:26:29,157 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = h2
              2016-05-31 21:26:29,359 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path 'C:\Wildfly\wildfly-10.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
              2016-05-31 21:26:29,437 INFO  [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
              2016-05-31 21:26:29,437 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-8) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
              2016-05-31 21:26:29,559 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.
              2016-05-31 21:26:29,560 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.18.Final
              2016-05-31 21:26:29,575 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0018: Host default-host starting
              2016-05-31 21:26:29,707 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
              2016-05-31 21:26:29,738 INFO  [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
              2016-05-31 21:26:29,755 INFO  [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
              2016-05-31 21:26:29,957 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
              2016-05-31 21:26:30,145 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Wildfly\wildfly-10.0.0.Final\standalone\deployments
              2016-05-31 21:26:30,170 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "EmployeeManagementServerApplication.jar" (runtime-name: "EmployeeManagementServerApplication.jar")
              2016-05-31 21:26:30,421 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry activation-1.1.1.jar,cdi-api-1.2.jar,javax.inject-1.jar,jsr181-api-1.0-MR1.jar,javax.mail-1.5.3.jar,validation-api-1.1.0.Final.jar,hibernate-jpa-2.1-api-1.0.0.Final.jar,jboss-annotations-api_1.2_spec-1.0.0.Final.jar,jboss-batch-api_1.0_spec-1.0.0.Final.jar,jboss-ejb-api_3.2_spec-1.0.0.Final.jar,jboss-el-api_3.0_spec-1.0.4.Final.jar,jboss-concurrency-api_1.0_spec-1.0.0.Final.jar,jboss-jsf-api_2.2_spec-2.2.11.jar,jboss-interceptors-api_1.2_spec-1.0.0.Final.jar,jboss-json-api_1.0_spec-1.0.0.Final.jar,jboss-j2eemgmt-api_1.1_spec-1.0.1.Final.jar,jboss-connector-api_1.7_spec-1.0.0.Final.jar,jboss-rmi-api_1.0_spec-1.0.4.Final.jar,jboss-jacc-api_1.5_spec-1.0.0.Final.jar,jboss-jaspi-api_1.1_spec-1.0.0.Final.jar,jboss-jms-api_2.0_spec-1.0.0.Final.jar,jboss-servlet-api_3.1_spec-1.0.0.Final.jar,jboss-jsp-api_2.3_spec-1.0.1.Final.jar,jboss-jstl-api_1.2_spec-1.1.2.Final.jar,jboss-transaction-api_1.2_spec-1.0.0.Final.jar,jboss-jaxrs-api_2.0_spec-1.0.0.Final.jar,jboss-websocket-api_1.1_spec-1.1.0.Final.jar,jboss-jaxb-api_2.2_spec-1.0.4.Final.jar,jboss-saaj-api_1.3_spec-1.0.3.Final.jar,jboss-jaxws-api_2.2_spec-2.0.2.Final.jar,javax.el-api-3.0.0.jar,javax.interceptor-api-1.2.jar in /C:/Wildfly/wildfly-10.0.0.Final/bin/content/EmployeeManagementServerApplication.jar  does not point to a valid jar for a Class-Path reference.
              2016-05-31 21:26:30,527 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-7) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
              2016-05-31 21:26:30,527 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
              2016-05-31 21:26:31,159 INFO  [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
              2016-05-31 21:26:31,485 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment EmployeeManagementServerApplication.jar
              2016-05-31 21:26:31,739 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-4) HV000001: Hibernate Validator 5.2.3.Final
              2016-05-31 21:26:31,819 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'EmployeeManagementImplementation' in deployment unit 'deployment "EmployeeManagementServerApplication.jar"' are as follows:

              java:global/EmployeeManagementServerApplication/EmployeeManagementImplementation!com.vpp_wildfly.employeemanagement.EmployeeManagementService
              java:app/EmployeeManagementServerApplication/EmployeeManagementImplementation!com.vpp_wildfly.employeemanagement.EmployeeManagementService
              java:module/EmployeeManagementImplementation!com.vpp_wildfly.employeemanagement.EmployeeManagementService
              java:jboss/exported/EmployeeManagementServerApplication/EmployeeManagementImplementation!com.vpp_wildfly.employeemanagement.EmployeeManagementService
              java:global/EmployeeManagementServerApplication/EmployeeManagementImplementation
              java:app/EmployeeManagementServerApplication/EmployeeManagementImplementation
              java:module/EmployeeManagementImplementation

              2016-05-31 21:26:31,986 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0006: Starting Services for CDI deployment: EmployeeManagementServerApplication.jar
              2016-05-31 21:26:31,986 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
              2016-05-31 21:26:31,986 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
              2016-05-31 21:26:32,002 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
              2016-05-31 21:26:32,002 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
              2016-05-31 21:26:32,119 INFO  [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 2.3.2 (Final)
              2016-05-31 21:26:32,140 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment EmployeeManagementServerApplication.jar
              2016-05-31 21:26:32,425 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 58) WFLYCLINF0002: Started client-mappings cache from ejb container
              2016-05-31 21:26:32,988 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "EmployeeManagementServerApplication.jar" (runtime-name : "EmployeeManagementServerApplication.jar")
              2016-05-31 21:26:33,158 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
              2016-05-31 21:26:33,158 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
              2016-05-31 21:26:33,158 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 13334ms - Started 366 of 635 services (379 services are lazy, passive or on-demand)

              • 4. Re: Wildfly 10 remote connection issue
                Wolfgang Mayer Master

                This could be an issue with MS/Windows

                Does the problem persist if you use the IP address instaed of the hostname?

                You should also verify that your hosts file contains these entries:

                 

                127.0.0.1  localhost

                ::1  localhost

                • 5. Re: Wildfly 10 remote connection issue
                  Wolf-Dieter Fink Master

                  Maybe a Windows issue with port 8080?

                  You might change the port to something else within the standalone.xml

                  • 6. Re: Wildfly 10 remote connection issue
                    Nicklas Karlsson Master

                    What happens when you point a browser at http://localhost:8080 or http://127.0.0.1:8080 ?

                    • 7. Re: Wildfly 10 remote connection issue
                      Mike Brooks Newbie

                      Nicklas: Welcome to Wildfly 10 screen in both cases.

                      • 8. Re: Wildfly 10 remote connection issue
                        Mike Brooks Newbie

                        @Wolf-Dieter Fink:  I changed standalone.xml to 12904.

                        at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93) [jboss-client.jar:10.0.0.Final]

                            at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146) [jboss-client.jar:10.0.0.Final]

                            at javax.naming.InitialContext.lookup(InitialContext.java:417) [na:1.8.0_92]

                            at com.vpp_wildfly.employeemanagement.Main.main(Main.java:38) [bin/:na]

                        Exception in thread "main" javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [http-remoting://localhost:12904 (Operation failed with status WAITING after 40000 MILLISECONDS)] [Root exception is java.net.ConnectException: Operation failed with status WAITING after 40000 MILLISECONDS]

                            at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:240)

                            at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149)

                            at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130)

                            at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)

                            at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104)

                            at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93)

                            at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146)

                            at javax.naming.InitialContext.lookup(InitialContext.java:417)

                            at com.vpp_wildfly.employeemanagement.Main.main(Main.java:38)

                        Caused by: java.net.ConnectException: Operation failed with status WAITING after 40000 MILLISECONDS

                            at org.jboss.naming.remote.protocol.IoFutureHelper.get(IoFutureHelper.java:97)

                            at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:198)

                            ... 8 more

                        Picked up _JAVA_OPTIONS: -Xmx512M

                        • 9. Re: Wildfly 10 remote connection issue
                          Mike Brooks Newbie

                          @Wolf-Dieter Fink  In addition:

                          2016-06-03 03:16:45,984 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:12904


                          Also tried 127.0.0.1:12904 (instead of localhost) in test client:

                           

                          03:29:13.934 [main] DEBUG o.j.n.r.client.HaRemoteNamingStore - Failed to connect to server http-remoting://127.0.0.1:12904

                          • 10. Re: Wildfly 10 remote connection issue
                            Nicklas Karlsson Master

                            Can you telnet to the port it says it's listening on? I know, a long shot since the front page came up with a normal browser...

                            • 11. Re: Wildfly 10 remote connection issue
                              Wolfgang Mayer Master

                              Can you post the source code of your client?

                              • 12. Re: Wildfly 10 remote connection issue
                                Mike Brooks Newbie

                                Nicklas, I think you have hit on something.  First of all my machine did not recognize telnet as a command.  So I had to go to Windows 10 control panel, programs and features, turn on or off windows features and then scroll down to Telnet Client and turn it on.  Then it  recognized the telnet command.  That is the  good news, the bad news for  me is  that when I did 

                                telnet localhost 8080

                                Connecting To localhost...Could not open connection to the host, on port 8080: Connect failed.

                                 

                                I am new to telnet and am afraid I do not  know where to go from here.  Any advice.

                                • 13. Re: Wildfly 10 remote connection issue
                                  Nicklas Karlsson Master

                                  And you changed the listener back to 8080?

                                  • 14. Re: Wildfly 10 remote connection issue
                                    Wolfgang Mayer Master

                                    Does the telnet command work for port 23?

                                    The above message usually simply means that your Telnet service is not started.

                                    To run telnet you should activate this feature and start the service.

                                    You should also make sure that the user is authorized to use the telnet command. For this you should open a command prompt as administrator and enter a command like this:

                                    net localgroup TelnetClients <username> /ADD

                                    1 2 Previous Next