-
1. Re: Wildfly on Redhat 7.4
jaikiran Feb 14, 2018 10:26 PM (in response to vabara)Can you please paste the complete exception stacktrace? What vendor and version of JDK/JRE do you use on the client (and server) of this AIX system? Post the output of:
java -version
-
2. Re: Wildfly on Redhat 7.4
vabara Feb 14, 2018 11:29 PM (in response to jaikiran)The Redhat 7.4 server running Wildfly, is using jdk 1.8. (I am starting wildfly with -b, and there are no firewalls)
java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 1.8.0_161-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)
The AIX client spec:
oslevel -s
7100-05-01-1731
java -version
java version "1.8.0"
Java(TM) SE Runtime Environment (build pap6480sr4fp10-20170727_01(SR4 FP10))
IBM J9 VM (build 2.8, JRE 1.8.0 AIX ppc64-64 Compressed References 20170722_357405 (JIT enabled, AOT enabled)
J9VM - R28_20170722_0201_B357405
JIT - tr.r14.java_20170722_357405
GC - R28_20170722_0201_B357405_CMPRSS
J9CL - 20170722_357405)
JCL - 20170726_01 based on Oracle jdk8u144-b01
Here is the stacktrace:
Feb 14, 2018 8:31:55 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.3.0.Final
Feb 14, 2018 8:31:55 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.3.0.Final
Feb 14, 2018 8:31:55 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 4.0.7.Final
connected
javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [http-remoting://scalinux2: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.lookup(RemoteContext.java:87)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:129)
at javax.naming.InitialContext.lookup(InitialContext.java:428)
at ContextHelper.getQueueConnectionFactory(ContextHelper.java:52)
at ContextHelper.main(ContextHelper.java:63)
Caused by: java.net.ConnectException: Operation failed with status WAITING after 5000 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
Exception in thread "Remoting "config-based-naming-client-endpoint" I/O-1" java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
at org.xnio.nio.WorkerThread.execute(WorkerThread.java:568)
at org.xnio.AbstractIoFuture.runNotifier(AbstractIoFuture.java:354)
at org.xnio.AbstractIoFuture.runAllNotifiers(AbstractIoFuture.java:233)
at org.xnio.AbstractIoFuture.setCancelled(AbstractIoFuture.java:291)
at org.xnio.FutureResult.setCancelled(FutureResult.java:98)
at org.xnio.nio.WorkerThread$ConnectHandle.forceTermination(WorkerThread.java:339)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:490)
Thank you.
-
3. Re: Wildfly on Redhat 7.4
ctomc Feb 15, 2018 11:33 AM (in response to vabara)aix is in general quite particular platform.
can you try upgrading the JDK to latest to see if it helps.
usually they do fix lots of NIO related issues with each update.
-
4. Re: Wildfly on Redhat 7.4
vabara Feb 15, 2018 4:09 PM (in response to ctomc)Tomaz,
I upgraded the jdk on AIX machine to what i believe is the latest 1.8.
java version "1.8.0_151"
Java(TM) SE Runtime Environment (build 8.0.5.7 - pap6480sr5fp7-20171216_01(SR5 FP7))
IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64 Compressed References 20171215_373586 (JIT enabled, AOT enabled)
OpenJ9 - 5aa401f
OMR - 101e793
IBM - b4a79bf)
JCL - 20171214_01 based on Oracle jdk8u151-b12
Still the same issue.
-
5. Re: Wildfly on Redhat 7.4
andey Feb 17, 2018 12:38 AM (in response to vabara)If the host or port details are incorrect, the following +CommunicationException+ will be thrown, indicating the connection timed-out.
javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [http-remoting://scalinux2:8080 (Operation failed with status WAITING after 5000 MILLISECONDS)] [Root exception is java.net.ConnectException: Operation failed with status WAITING after 5000 MILLISECONDS]
Could you check it if it is correct?
Have you confirmed that you have basic connectivity from your jboss server to scalinux2 on port 8080 (e.g. via telnet)? Is there perhaps a firewall that is blocking that connection? Also check if connection manager is available or not.
-
6. Re: Wildfly on Redhat 7.4
jaikiran Feb 27, 2018 4:10 AM (in response to vabara)See my reply in the other similar thread here Re: Wildfly on RedHat 7.4 JMS Client on AIX 7.1Cannot Connect