[JBoss JIRA] (AS7-5967) RemoteNamingTestCase intermittently fails on IBM JDK due to org.jboss.remoting3.NotOpenException: Endpoint is not open
2:11 p.m.
Ivo Studensky created AS7-5967:
----------------------------------
Summary: 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: Test Suite
Affects Versions: 7.1.3.Final (EAP)
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
9:42 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
IBM JDK seems to be too fast. The culprit of this issue is that IBM JDK sometimes
finalizes the InitialContext created by getRemoteContext() method before the lookup()
method finishes. See the following log snippet. The RemoteContext is finalized by
J9VMInternals.runFinalize and then lookup() method fails.
{noformat}
16:21:13,521 TRACE [org.jboss.remoting.resource] (Finalizer thread) my own stack trace
from AbstractHandleableCloseable#closeAsync at ENTRY:
16:21:13,524 TRACE [org.jboss.remoting.resource] (Finalizer thread)
org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:350)
16:21:13,529 TRACE [org.jboss.remoting.resource] (Finalizer thread)
org.jboss.remoting3.EndpointImpl.closeAction(EndpointImpl.java:208)
16:21:13,535 TRACE [org.jboss.remoting.resource] (Finalizer thread)
org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:369)
16:21:13,539 TRACE [org.jboss.remoting.resource] (Finalizer thread)
org.jboss.naming.remote.client.EndpointCache.release(EndpointCache.java:58)
16:21:13,543 TRACE [org.jboss.remoting.resource] (Finalizer thread)
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.closeAsync(EndpointCache.java:189)
16:21:13,545 TRACE [org.jboss.remoting.resource] (Finalizer thread)
org.jboss.naming.remote.client.InitialContextFactory$1.close(InitialContextFactory.java:228)
16:21:13,555 TRACE [org.jboss.remoting.resource] (Finalizer thread)
org.jboss.naming.remote.client.RemoteContext.finalize(RemoteContext.java:199)
16:21:13,558 TRACE [org.jboss.remoting.resource] (Finalizer thread)
java.lang.J9VMInternals.runFinalize(J9VMInternals.java:455)
16:21:13,562 TRACE [org.jboss.remoting.resource] (Finalizer thread) Closing Remoting
remote connection provider 50f78597 for endpoint
"config-based-naming-client-endpoint" <e6872e7> asynchronously
16:21:13,570 TRACE [org.jboss.remoting.endpoint] (Finalizer thread) Phase 1 shutdown count
00000001 of endpoint "config-based-naming-client-endpoint" <e6872e7>
(closed a cancelled connection)
16:21:13,571 TRACE [org.xnio.nio.selector] (Remoting
"config-based-naming-client-endpoint" read-1) Beginning select on
sun.nio.ch.EPollSelectorImpl@3e388ef1
16:21:13,574 TRACE [org.xnio.nio.selector] (Remoting
"config-based-naming-client-endpoint" read-1) Selected on
sun.nio.ch.EPollSelectorImpl@3e388ef1
16:21:13,576 TRACE [org.xnio.nio.selector] (Remoting
"config-based-naming-client-endpoint" read-1) Beginning select on
sun.nio.ch.EPollSelectorImpl@3e388ef1
16:21:13,575 DEBUG [org.jboss.naming.remote.client.HaRemoteNamingStore] (main) Failed to
connect to server remote://127.0.0.1:4447: java.lang.RuntimeException: Operation failed
with status CANCELLED
at org.jboss.naming.remote.protocol.IoFutureHelper.get(IoFutureHelper.java:89)
at
org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:180)
at
org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:131)
at
org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:112)
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:77)
{noformat}
The current test method which does not work on IBM JDK is as follows:
{code}
@Test public void testRemoteLookup() throws Exception {
assertEquals("TestValue", getRemoteContext().lookup("test"));
}
{code}
And this is a slightly modified test method which works on IBM JDK nicely (it holds an
explicit reference to the InitialContext):
{code}
@Test public void testRemoteLookup() throws Exception {
Context context = null;
try {
context = getRemoteContext();
assertEquals("TestValue", context.lookup("test"));
} finally {
if (context != null)
context.close();
}
}
{code}
Note that the issue disappears when running with any Byteman's script, i.e. it is not
possible to debug it with Byteman. That's the reason why I had to modify the remoting
sources to print out a stack trace on closeAsync method entry.
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: Test Suite
Affects Versions: 7.1.3.Final (EAP)
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
10:35 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky updated AS7-5967:
-------------------------------
Affects Version/s: 7.2.0.Alpha1
Component/s: Naming
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
10:37 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky updated AS7-5967:
-------------------------------
Git Pull Request: https://github.com/jbossas/jboss-as/pull/3481,
https://github.com/jbossas/jboss-as/pull/3482
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
12:25 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-5967:
---------------------------------------
When this fails, is it ever the first test executed that fails, or is it always the 2nd or
third?
I'm concerned this patch is covering over a race condition.
If you look at your trace logging, you can see that the DEBUG stack trace shows the
javax.naming.InitialContext has a ref to the RemoteContext. The test execution stack will
also have a reference, even without your patch. Either one of these references is
sufficient to keep the RemoteContext from being gc'd, unless the JVM is fundamentally
broken (unlikely in the extreme.)
The patch creating a local variable reference to the RemoteContext is just another form of
reference on the stack and shouldn't be preventing the RemoteContext being gc'd,
since it shouldn't be gc'd anyway.
I suspect what the patch is really doing that solves the intermittent failure is calling
context.close(). That means each test method is cleaning up the context. I'm concerned
what was happening before is a race condition. Test method #1 uses a RemoteContext, and
then it gets closed by the gc. There's a race with the next test method #2 creating a
new RemoteContext using the same underlying endpoint (which is cached and would be reused
by the 2nd test if the 1st hasn't cleaned up yet.) Looking at the code in
RemoteContext EndpointCache I don't see how this could happen though.
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
3:52 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry edited comment on AS7-5967 at 11/21/12 9:51 PM:
-----------------------------------------------------------------
When this fails, is it ever the first test executed that fails, or is it always the 2nd or
third?
I'm concerned this patch is covering over a race condition.
If you look at your trace logging, you can see that the DEBUG stack trace shows the
javax.naming.InitialContext has a ref to the RemoteContext. The test execution stack has a
reference to the InitialContext, even without your patch. This is sufficient to keep the
RemoteContext from being gc'd, unless the JVM is fundamentally broken (unlikely in the
extreme.)
The patch creating a local variable reference to the RemoteContext is just another form of
reference on the stack and shouldn't be preventing the RemoteContext being gc'd,
since it shouldn't be gc'd anyway.
I suspect what the patch is really doing that solves the intermittent failure is calling
context.close(). That means each test method is cleaning up the context. I'm concerned
what was happening before is a race condition. Test method #1 uses a RemoteContext, and
then it gets closed by the gc. There's a race with the next test method #2 creating a
new RemoteContext using the same underlying endpoint (which is cached and would be reused
by the 2nd test if the 1st hasn't cleaned up yet.) Looking at the code in
RemoteContext EndpointCache I don't see how this could happen though.
was (Author: brian.stansberry):
When this fails, is it ever the first test executed that fails, or is it always the
2nd or third?
I'm concerned this patch is covering over a race condition.
If you look at your trace logging, you can see that the DEBUG stack trace shows the
javax.naming.InitialContext has a ref to the RemoteContext. The test execution stack will
also have a reference, even without your patch. Either one of these references is
sufficient to keep the RemoteContext from being gc'd, unless the JVM is fundamentally
broken (unlikely in the extreme.)
The patch creating a local variable reference to the RemoteContext is just another form of
reference on the stack and shouldn't be preventing the RemoteContext being gc'd,
since it shouldn't be gc'd anyway.
I suspect what the patch is really doing that solves the intermittent failure is calling
context.close(). That means each test method is cleaning up the context. I'm concerned
what was happening before is a race condition. Test method #1 uses a RemoteContext, and
then it gets closed by the gc. There's a race with the next test method #2 creating a
new RemoteContext using the same underlying endpoint (which is cached and would be reused
by the 2nd test if the 1st hasn't cleaned up yet.) Looking at the code in
RemoteContext EndpointCache I don't see how this could happen though.
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
9:51 a.m.
[
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
9:53 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky updated AS7-5967:
-------------------------------
Environment:
IBM JDK 6 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
was:
IBM JDK 6
IBM JDK 7
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
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
11 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
It is even more weird. A passes, but B fails, see below.
{code:title=A}
public void testRemoteLookup() throws Exception {
Context context = getRemoteContext();
assertEquals("TestValue", context.lookup("test"));
context.toString();
}
{code}
{code:title=B}
public void testRemoteLookup() throws Exception {
Context context = getRemoteContext();
assertEquals("TestValue", context.lookup("test"));
}
{code}
I am now trying to compare byte code of those two generated by IBM JDK7 as Carlo
suggested.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
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
12:01 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
Nothing interesting in byte code between A and B, see the bold part below. And byte code
generated by Oracle JDK is the same as byte code generated by IBM JDK, there is no
difference. Also disabling JIT did not help.
{panel}
public void testRemoteLookup() throws java.lang.Exception;
Code:
0: aload_0
1: invokevirtual #29 // Method
getRemoteContext:()Ljavax/naming/Context;
4: astore_1
5: ldc #30 // String TestValue
7: aload_1
8: ldc #31 // String test
10: invokeinterface #32, 2 // InterfaceMethod
javax/naming/Context.lookup:(Ljava/lang/String;)Ljava/lang/Object;
15: invokestatic #33 // Method
org/junit/Assert.assertEquals:(Ljava/lang/Object;Ljava/lang/Object;)V
*18: aload_1*
*19: invokevirtual #34* // Method
java/lang/Object.toString:()Ljava/lang/String;
*22: pop*
23: return
{panel}
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
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
1:59 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
With '-verbose:gc' the issue disappears too.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
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
2:01 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky edited comment on AS7-5967 at 11/22/12 8:00 AM:
--------------------------------------------------------------
With '-verbose:gc' the issue disappears as well.
was (Author: istudens):
With '-verbose:gc' the issue disappears too.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
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
3:17 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-5967:
---------------------------------------
Very weird indeed!
Since the problem is fixed without having to call context.close(), then I'm not
concerned about our code, particularly since the problem occurs when only 1 test method is
executed. Last night I looked very carefully at our
InitialContextFactory/RemoteContext/NamingStoreCache/EndpointCache/HaRemoteNamingStore to
look for a race conditions or a way the Endpoint could leak out and get closed
inappropriately and I found nothing.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
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
12:59 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-5967:
-------------------------------------
I just can't see what could cause this. The cache access is all synchronized, it
should not be possible for the finalizer to close an active endpoint, as the reference
count should have been increased by this point.
Can you add some trace logging to EndpointCache and have a look at what is going on? In
particular at every call to get and release it would be good to see the endpoint object,
the reference count, and the stack trace?
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
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
9:44 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
Stuart, I will try that. The finalize method, however, is called on RemoteContext, so it
should be the RemoteContext which has lost references... I don't understand what
happens there.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
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
9:48 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-5967:
-------------------------------------
The endpoint is shared between multiple remote contexts. If all remote contexts are
finalised then the Endpoint will be closed and a new one created on the next connection.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
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
10:01 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
Another note which might not be related to this issue: I've noticed the javadoc of
InitialContextFactory#getInitialContext(Hashtable<?,?> environment) says:
{quote}
The environment parameter is owned by the caller.
The implementation will not modify the object or keep a reference
to it, although it may keep a reference to a clone or copy.
{quote}
The implementation of RemoteContext, however, keeps a reference to the environment
parameter without copying/cloning it (line 71). Is it correct?
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
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
10:49 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
The environment parameter is cloned in the constructor of InitialContext actually, so it
seems to be alright.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
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
12:35 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
I've added more trace logging to the EndpointCache as follows:
{code}
diff --git a/src/main/java/org/jboss/naming/remote/client/EndpointCache.java
b/src/main/java/org/jboss/naming/remote/client/EndpointCache.java
index be369b7..ee3ce13 100644
--- a/src/main/java/org/jboss/naming/remote/client/EndpointCache.java
+++ b/src/main/java/org/jboss/naming/remote/client/EndpointCache.java
@@ -47,11 +47,33 @@ public class EndpointCache {
cache.putIfAbsent(endpointHash, cacheEntry);
}
cacheEntry.referenceCount.incrementAndGet();
+
+ logger.info("==============================");
+ logger.info("EndpointCache.get()");
+ logger.infof("cacheEntry.endpoint = %s", cacheEntry.endpoint);
+ logger.infof("cacheEntry.referenceCount = %s",
cacheEntry.referenceCount.get());
+ logger.info("stack trace:");
+ for (StackTraceElement ste : new Throwable().getStackTrace()) {
+ logger.infof("===== \t %s", ste);
+ }
+ logger.info("==============================");
+
return cacheEntry.endpointWrapper;
}
public synchronized void release(final CacheKey endpointHash, final boolean async) {
final CacheEntry cacheEntry = cache.get(endpointHash);
+
+ logger.info("------------------------------");
+ logger.info("EndpointCache.release()");
+ logger.infof("cacheEntry.endpoint = %s", cacheEntry.endpoint);
+ logger.infof("cacheEntry.referenceCount = %s",
cacheEntry.referenceCount.get());
+ logger.info("stack trace:");
+ for (StackTraceElement ste : new Throwable().getStackTrace()) {
+ logger.infof("===== \t %s", ste);
+ }
+ logger.info("------------------------------");
+
if (cacheEntry.referenceCount.decrementAndGet() == 0) {
try {
if (async) {
{code}
Here is the snippet from test log output:
{noformat}
12:22:35,244 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread)
------------------------------
12:22:35,246 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread)
EndpointCache.release()
12:22:35,248 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread)
cacheEntry.endpoint = endpoint "config-based-naming-client-endpoint"
<c825c546>
12:22:35,251 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread)
cacheEntry.referenceCount = 1
12:22:35,254 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) stack
trace:
12:22:35,257 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) =====
org.jboss.naming.remote.client.EndpointCache.release(EndpointCache.java:72)
12:22:35,262 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) =====
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.closeAsync(EndpointCache.java:211)
12:22:35,265 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) =====
org.jboss.naming.remote.client.InitialContextFactory$1.close(InitialContextFactory.java:228)
12:22:35,268 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) =====
org.jboss.naming.remote.client.RemoteContext.finalize(RemoteContext.java:199)
12:22:35,271 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) =====
java.lang.J9VMInternals.runFinalize(J9VMInternals.java:455)
12:22:35,273 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread)
------------------------------
{noformat}
See the attached full test log.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: test_output_with_trace_logging_in_EndpointCache.xml
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
12:35 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky updated AS7-5967:
-------------------------------
Attachment: test_output_with_trace_logging_in_EndpointCache.xml
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: test_output_with_trace_logging_in_EndpointCache.xml
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
12:39 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky edited comment on AS7-5967 at 11/23/12 6:37 AM:
--------------------------------------------------------------
I've added more trace logging to the EndpointCache as follows:
{code}
diff --git a/src/main/java/org/jboss/naming/remote/client/EndpointCache.java
b/src/main/java/org/jboss/naming/remote/client/EndpointCache.java
index be369b7..ee3ce13 100644
--- a/src/main/java/org/jboss/naming/remote/client/EndpointCache.java
+++ b/src/main/java/org/jboss/naming/remote/client/EndpointCache.java
@@ -47,11 +47,33 @@ public class EndpointCache {
cache.putIfAbsent(endpointHash, cacheEntry);
}
cacheEntry.referenceCount.incrementAndGet();
+
+ logger.info("==============================");
+ logger.info("EndpointCache.get()");
+ logger.infof("cacheEntry.endpoint = %s", cacheEntry.endpoint);
+ logger.infof("cacheEntry.referenceCount = %s",
cacheEntry.referenceCount.get());
+ logger.info("stack trace:");
+ for (StackTraceElement ste : new Throwable().getStackTrace()) {
+ logger.infof("===== \t %s", ste);
+ }
+ logger.info("==============================");
+
return cacheEntry.endpointWrapper;
}
public synchronized void release(final CacheKey endpointHash, final boolean async) {
final CacheEntry cacheEntry = cache.get(endpointHash);
+
+ logger.info("------------------------------");
+ logger.info("EndpointCache.release()");
+ logger.infof("cacheEntry.endpoint = %s", cacheEntry.endpoint);
+ logger.infof("cacheEntry.referenceCount = %s",
cacheEntry.referenceCount.get());
+ logger.info("stack trace:");
+ for (StackTraceElement ste : new Throwable().getStackTrace()) {
+ logger.infof("===== \t %s", ste);
+ }
+ logger.info("------------------------------");
+
if (cacheEntry.referenceCount.decrementAndGet() == 0) {
try {
if (async) {
{code}
Here is the snippet from test log output:
{noformat}
12:22:35,244 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread)
------------------------------
12:22:35,246 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread)
EndpointCache.release()
12:22:35,248 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread)
cacheEntry.endpoint = endpoint "config-based-naming-client-endpoint"
<c825c546>
12:22:35,251 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread)
cacheEntry.referenceCount = 1
12:22:35,254 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) stack
trace:
12:22:35,257 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) =====
org.jboss.naming.remote.client.EndpointCache.release(EndpointCache.java:72)
12:22:35,262 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) =====
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.closeAsync(EndpointCache.java:211)
12:22:35,265 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) =====
org.jboss.naming.remote.client.InitialContextFactory$1.close(InitialContextFactory.java:228)
12:22:35,268 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) =====
org.jboss.naming.remote.client.RemoteContext.finalize(RemoteContext.java:199)
12:22:35,271 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) =====
java.lang.J9VMInternals.runFinalize(J9VMInternals.java:455)
12:22:35,273 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread)
------------------------------
{noformat}
See the attached full test log - test_output_with_trace_logging_in_EndpointCache.xml.
was (Author: istudens):
I've added more trace logging to the EndpointCache as follows:
{code}
diff --git a/src/main/java/org/jboss/naming/remote/client/EndpointCache.java
b/src/main/java/org/jboss/naming/remote/client/EndpointCache.java
index be369b7..ee3ce13 100644
--- a/src/main/java/org/jboss/naming/remote/client/EndpointCache.java
+++ b/src/main/java/org/jboss/naming/remote/client/EndpointCache.java
@@ -47,11 +47,33 @@ public class EndpointCache {
cache.putIfAbsent(endpointHash, cacheEntry);
}
cacheEntry.referenceCount.incrementAndGet();
+
+ logger.info("==============================");
+ logger.info("EndpointCache.get()");
+ logger.infof("cacheEntry.endpoint = %s", cacheEntry.endpoint);
+ logger.infof("cacheEntry.referenceCount = %s",
cacheEntry.referenceCount.get());
+ logger.info("stack trace:");
+ for (StackTraceElement ste : new Throwable().getStackTrace()) {
+ logger.infof("===== \t %s", ste);
+ }
+ logger.info("==============================");
+
return cacheEntry.endpointWrapper;
}
public synchronized void release(final CacheKey endpointHash, final boolean async) {
final CacheEntry cacheEntry = cache.get(endpointHash);
+
+ logger.info("------------------------------");
+ logger.info("EndpointCache.release()");
+ logger.infof("cacheEntry.endpoint = %s", cacheEntry.endpoint);
+ logger.infof("cacheEntry.referenceCount = %s",
cacheEntry.referenceCount.get());
+ logger.info("stack trace:");
+ for (StackTraceElement ste : new Throwable().getStackTrace()) {
+ logger.infof("===== \t %s", ste);
+ }
+ logger.info("------------------------------");
+
if (cacheEntry.referenceCount.decrementAndGet() == 0) {
try {
if (async) {
{code}
Here is the snippet from test log output:
{noformat}
12:22:35,244 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread)
------------------------------
12:22:35,246 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread)
EndpointCache.release()
12:22:35,248 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread)
cacheEntry.endpoint = endpoint "config-based-naming-client-endpoint"
<c825c546>
12:22:35,251 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread)
cacheEntry.referenceCount = 1
12:22:35,254 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) stack
trace:
12:22:35,257 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) =====
org.jboss.naming.remote.client.EndpointCache.release(EndpointCache.java:72)
12:22:35,262 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) =====
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.closeAsync(EndpointCache.java:211)
12:22:35,265 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) =====
org.jboss.naming.remote.client.InitialContextFactory$1.close(InitialContextFactory.java:228)
12:22:35,268 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) =====
org.jboss.naming.remote.client.RemoteContext.finalize(RemoteContext.java:199)
12:22:35,271 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread) =====
java.lang.J9VMInternals.runFinalize(J9VMInternals.java:455)
12:22:35,273 INFO [org.jboss.naming.remote.client.EndpointCache] (Finalizer thread)
------------------------------
{noformat}
See the attached full test log.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: test_output_with_trace_logging_in_EndpointCache.xml
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
3:10 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-5967:
-------------------------------------
This is really weird, it really does look like an active object is being finalized.
Can you add some logging in lookup, the constructor, and finalise() of RemoteNamingStore?
And add a finalised flag, and log a message if lookup is called after the object is
finalized?
This really seems unlikely to me, as I would expect pretty much everything to be broken,
but I really can't see anything else that could be happening.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: test_output_with_trace_logging_in_EndpointCache.xml
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
8:57 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-5967:
---------------------------------------
Stuart, I think you were looking for logging from RemoteContext, not RemoteNamingStore.
In any logging added to RemoteContext, please include the toString() output of the
RemoteContext so we see its identity hashcode and can track the instance.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: test_output_with_trace_logging_in_EndpointCache.xml
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
10:39 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
I will add more logging into it. The finalization often happens during the execution of
HaRemoteNamingStore.java:180 which is:
{code}
connection = IoFutureHelper.get(futureConnection, connectionInfo.getConnectionTimeout(),
TimeUnit.MILLISECONDS);
{code}
In that case it ends with 'Operation failed with status CANCELLED' as shown in
previous logs above.
Sometimes the finalization also hits HaRemoteNamingStore.java:179 and then it ends up with
'org.jboss.remoting3.NotOpenException: Endpoint is not open' as shown in the first
logs of this jira.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: test_output_with_trace_logging_in_EndpointCache.xml
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
11:39 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky updated AS7-5967:
-------------------------------
Attachment: endpoint_is_not_open_2012-11-26.xml
failed_with_status_cancelled_2012-11-26.xml
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
11:41 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
Here are new logs, see endpoint_is_not_open_2012-11-26.xml and
failed_with_status_cancelled_2012-11-26.xml attached to this jira.
The relevant patch of jboss-remote-naming can be seen at
http://pastebin.test.redhat.com/117046
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
12:56 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
When trying a patch like the following one (see finally clause there) the issue again
disappears.
{code}
@@ -73,10 +80,17 @@ public class RemoteContext implements Context, NameParser {
}
public Object lookup(final Name name) throws NamingException {
+ log.info("entering RemoteContext#lookup(), instance " + this);
+ log.info(this + "#finalized = " + finalized);
if (isEmpty(name)) {
return new RemoteContext(prefix, namingStore, environment);
}
- return namingStore.lookup(getAbsoluteName(name));
+ try {
+ return namingStore.lookup(getAbsoluteName(name));
+ } finally {
+ log.info("RemoteContext#lookup finally clause, instance " + this);
+ log.info(this + "#finalized = " + finalized);
+ }
}
public Object lookup(final String name) throws NamingException {
{code}
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
11:41 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-5967:
-------------------------------------
Wow, according to those logs the RemoteContext is finalized while there is a reference to
it on the stack.
Only 1 instance is ever created (which we can say for sure as there is logging in the
constructor), it is finalized, then several hundred ms later the stack trace shows that
the instance is still on the stack.
We probably need to take this up with IBM.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
11:43 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-5967:
-------------------------------------
Of course it is possible I am reading this wrong, but it looks pretty conclusive to me,
and is backed up by the circumstantial evidence. If anyone else wants to provide a second
opinion that would be appreciated.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
12:20 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-5967:
---------------------------------------
Both of those logs show the RemoteContext that is used for the lookup() call also being
finalized. I think IBM has a bug.
You've now made 2 changes to code that result in a local variable ref to an object
being needed for use on the operand stack a bit longer, and both result in the object no
longer being garbage collected. Your patch to the test case does that by requiring use of
local variable 1 in
18: aload_1
19: invokevirtual #34 // Method java/lang/Object.toString)Ljava/lang/String;
and your finally block in RemoteContext.lookup() will have a similar effect with local
variable 0 (this). Even more amazing, the two changes affect refs to different objects
(InitialContext vs RemoteContext).
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
10:42 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse commented on AS7-5967:
---------------------------------------
If looking at a timing issue and the logs do not look as you would expect I would double
check we are not using asynchronous logging - from my previous role I remember Galder
having some problems debugging clustering issues where the ordering and timing of log
messages was not as expected.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
1:38 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-5967:
---------------------------------------
Luckily in this case the timing issues are quite clear. There are 3 basic events --
construct, lookup, finalize -- with the first two done on one thread and the 3rd on
another. Logically, the 3rd has to follow the 1st, and does in the logs. The logs show the
3rd happening in the middle of execution of the 2nd. We know that reported timing is
essentially accurate, because the 3rd is producing side effects (closing the endpoint)
that result in failure of the 2nd.
Once the constructor executes there is a reference chain leading back to a variable on the
stack that should be sufficient to keep the RemoteContext from being gc'd.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
1:44 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
I will try to isolate it into a simple test case which then can be used for filing a bug
against IBM 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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
3:04 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-5967:
-----------------------------------
Just stating the obvious here, which may or may not change the results. The logs shows
that you are using:
{code}
<property value="pxa6470sr2-20120901_01 (SR2)"
name="java.runtime.version"/>
{code}
There's a SR3 JDK update available
http://www.ibm.com/developerworks/java/jdk/aix/j764/Java7_64.fixinfo.html which you might
want to try reproducing against, before reporting it to IBM, if it's reproducible in
that version.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
3:38 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
Thanks, Jaikiran, I will try that.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
4:45 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
The issue also affects IBM JDK7 SR3.
And as mentioned in the Environment field, IBM JDK6 is affected too.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
4:39 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
I tried to use -Xtgc: and -Xtrace: settings of IBM JDK, but with no luck. I have not
reached to any clue why the finalize method is triggered on the RemoteContext.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
4:43 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
However, it is possible to invoke this issue with jboss-remote-naming unit tests as well.
See FinalizerTest at
https://github.com/istudens/jboss-remote-naming/compare/AS7-5967
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
1:26 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
I've posted it to IBM forum:
https://www.ibm.com/developerworks/forums/thread.jspa?threadID=463851
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
6:13 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
It seems it is not considered being a bug, see
https://www.ibm.com/developerworks/forums/thread.jspa?messageID=14914414&...
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
6:25 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-5967:
---------------------------------------
I vote that when jboss-remote-naming requires JDK 7 we get rid of the finalize()
implementation with the expectation that users will use try-with-resource. Until then,
this is a known issue and users are advised to close their InitialContext in a finally
block the way you did in your testsuite patch. That's the right thing to do anyway.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
6:27 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-5967:
---------------------------------------
BTW, if you all agree with my suggestion, we should probably leave this JIRA open. Just
fix the test so it's reliable and reword the JIRA title a bit to something like
"Naming lookup intermittently fails on IBM JDK due to
org.jboss.remoting3.NotOpenException: Endpoint is not open."
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
6:39 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
I agree with Brian.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
4:19 p.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
A link that appeared on the ibm forum:
https://www.securecoding.cert.org/confluence/display/java/MET12-J.+Do+not...
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
9:57 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
I cannot re-open the pull requests. Shall I create them again?
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
10:03 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-5967:
-----------------------------------
{quote}
I cannot re-open the pull requests. Shall I create them again?
{quote}
I've re-opened them. You can update them appropriately.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
10:26 a.m.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky commented on AS7-5967:
------------------------------------
Done. I've just rebased them.
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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
10:05 a.m.
New subject: [JBoss JIRA] (AS7-5967) Naming lookup intermittently fails on IBM JDK due to org.jboss.remoting3.NotOpenException: Endpoint is not open.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Ivo Studensky updated AS7-5967:
-------------------------------
Summary: Naming lookup intermittently fails on IBM JDK due to
org.jboss.remoting3.NotOpenException: Endpoint is not open. (was: RemoteNamingTestCase
intermittently fails on IBM JDK due to org.jboss.remoting3.NotOpenException: Endpoint is
not open)
Assignee: (was: Ivo Studensky)
Leaving this jira unassigned and open.
Naming lookup 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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
9:26 a.m.
New subject: [JBoss JIRA] (AS7-5967) Naming lookup intermittently fails on IBM JDK due to org.jboss.remoting3.NotOpenException: Endpoint is not open.
[
https://issues.jboss.org/browse/AS7-5967?page=com.atlassian.jira.plugin.s...
]
Carlo de Wolf commented on AS7-5967:
------------------------------------
I think that the actual finalize method is on the wrong object. (Or the close tasks tied
to the wrong object).
The RemoteContext goes out of use early in the game, while other objects are still in use.
So essentially each object should govern its own lifecycle properly and not let it be
governed by an aggregate.
Naming lookup 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 (build 20110203_074623)
IBM JDK 7 (build 20120809_118929)
Reporter: Ivo Studensky
Attachments: endpoint_is_not_open_2012-11-26.xml,
failed_with_status_cancelled_2012-11-26.xml,
test_output_with_trace_logging_in_EndpointCache.xml
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
4152
days inactive
4172
days old
48 comments
6 participants
participants (6)
-
Brian Stansberry (JIRA) -
Carlo de Wolf (JIRA)
-
Darran Lofthouse (JIRA)
-
Ivo Studensky (JIRA)
-
jaikiran pai (JIRA)
-
Stuart Douglas (JIRA)