Wildfly 10 remote connection issue
mykelbrooks May 31, 2016 11:50 PMI 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.