[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
Thanks for the comment, Brian. I did my patch on closeAsync method just to see who/what is
closing the remoting connection on the client side, i.e. to be able to see it is JVM
finalizer. Trace logs only shows that a closing request was sent from client.
I am not sure if it really is a race condition between two test methods as it is failing
even when only one test method is executed (-Dtest=RemoteNamingTestCase#testRemoteLookup).
Furthermore, it is the first test method which fails when all test methods are executed.
Sometimes also the second method fails, but the third method usually passes, at least on
IBM JDK6. On IBM JDK7 all of them regularly fail.
I retested it again several times without 'context.close()' and it worked nicely
on my laptop, so it looks like the local variable reference fixing this. It is weird, I
know. Also note that this issue affects IBM JDKs only. I have not seen it on Oracle/Open
JDK.
RemoteNamingTestCase intermittently fails on IBM JDK due to
org.jboss.remoting3.NotOpenException: Endpoint is not open
----------------------------------------------------------------------------------------------------------------------
Key: AS7-5967
URL:
https://issues.jboss.org/browse/AS7-5967
Project: Application Server 7
Issue Type: Feature Request
Components: Naming, Test Suite
Affects Versions: 7.1.3.Final (EAP), 7.2.0.Alpha1
Environment: IBM JDK 6
IBM JDK 7
Reporter: Ivo Studensky
Assignee: Ivo Studensky
RemoteNamingTestCase intermittently fails when running on IBM JDK. According to logs the
remoting channel had been closed before the endpoint tried to connect to it.
Unfortunately, when I was trying to debug this issue the tests always nicely passed.
test.log snippet:
{noformat}
13:16:31,115 DEBUG [org.xnio.nio] (Remoting
"config-based-naming-client-endpoint" read-1) Started channel thread
'Remoting "config-based-naming-client-endpoint" read-1', selector
sun.nio.ch.EPollSelectorImpl@345642e1
13:16:31,115 DEBUG [org.xnio.nio] (Remoting
"config-based-naming-client-endpoint" write-1) Started channel thread
'Remoting "config-based-naming-client-endpoint" write-1', selector
sun.nio.ch.EPollSelectorImpl@1dc68cf2
13:16:31,121 DEBUG [org.jboss.naming.remote.client.InitialContextFactory] (main)
jboss.naming.client.connect.options. has the following options
{org.xnio.Options.SASL_POLICY_NOPLAINTEXT=>false}
13:16:31,191 ERROR [org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1] (Remoting
"config-based-naming-client-endpoint" task-1) Channel end notification received,
closing channel Channel ID d1f17196 (outbound) of Remoting connection fd3dcedc to
/127.0.0.1:4447
13:16:31,204 DEBUG [org.jboss.naming.remote.client.HaRemoteNamingStore] (main) Failed to
connect to server remote://127.0.0.1:4447: org.jboss.remoting3.NotOpenException: Endpoint
is not open
at org.jboss.remoting3.EndpointImpl.resourceUntick(EndpointImpl.java:182)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:261)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
at
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
at
org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:179)
at
org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:117)
at
org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:223)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:79)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:83)
at javax.naming.InitialContext.lookup(InitialContext.java:422)
at
org.jboss.as.test.integration.naming.remote.simple.RemoteNamingTestCase.testRemoteLookup(RemoteNamingTestCase.java:74)
{noformat}
server.log snippet:
{noformat}
13:16:31,025 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018559:
Deployed "test.jar"
13:16:31,163 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] (Remoting
"thinkpax" task-3) Channel Opened - Channel ID 51f17196 (inbound) of Remoting
connection b9da2788 to /127.0.0.1:46866
13:16:31,176 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] (Remoting
"thinkpax" task-4) Chosen version 0x01
13:16:31,189 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] (Remoting
"thinkpax" read-1) Channel Channel ID 51f17196 (inbound) of Remoting connection
b9da2788 to /127.0.0.1:46866 closed.
13:16:31,193 INFO [org.jboss.as.naming] (Remoting "thinkpax" task-1)
JBAS011806: Channel end notification received, closing channel Channel ID 51f17196
(inbound) of Remoting connection b9da2788 to null
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira