4:50 p.m.
on Windows, org.jboss.test.naming.test.SimpleUnitTestCase fail
--------------------------------------------------------------
Key: JBAS-3722
URL: http://jira.jboss.com/jira/browse/JBAS-3722
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Naming
Affects Versions: JBossAS-4.0.5.GA
Environment: Windows 2003 - dev28 in qa lab, Sun jdk1.4.2
Reporter: Prabhat Jha
Assigned To: Scott M Stark
testHaParitionName and testDiscoveryPort of org.jboss.test.naming.test.SimpleUnitTestCase
fail with :
javax.naming.CommunicationException: Could not obtain connection to any of these urls:
10.16.56.139:65535 and discovery failed with error: javax.naming.CommunicationException:
Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
[Root exception is javax.naming.CommunicationException: Failed to connect to server
10.16.56.139:65535 [Root exception is javax.naming.ServiceUnavailableException: Failed to
connect to server 10.16.56.139:65535 [Root exception is java.net.ConnectException:
Connection refused: connect]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1414)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at
org.jboss.test.naming.test.SimpleUnitTestCase.testDiscoveryPort(SimpleUnitTestCase.java:284)
Caused by: javax.naming.CommunicationException: Failed to connect to server
10.16.56.139:65535 [Root exception is javax.naming.ServiceUnavailableException: Failed to
connect to server 10.16.56.139:65535 [Root exception is java.net.ConnectException:
Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1385)
... 19 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server
10.16.56.139:65535 [Root exception is java.net.ConnectException: Connection refused:
connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243)
... 20 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:461)
at java.net.Socket.connect(Socket.java:411)
at java.net.Socket.<init>(Socket.java:310)
at java.net.Socket.<init>(Socket.java:212)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:32 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-3722) on Windows, org.jboss.test.naming.test.SimpleUnitTestCase fail
[ http://jira.jboss.com/jira/browse/JBAS-3722?page=all ]
Ryan Campbell updated JBAS-3722:
--------------------------------
Fix Version/s: JBossAS-4.0.5.GA
on Windows, org.jboss.test.naming.test.SimpleUnitTestCase fail
--------------------------------------------------------------
Key: JBAS-3722
URL: http://jira.jboss.com/jira/browse/JBAS-3722
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Naming
Affects Versions: JBossAS-4.0.5.GA
Environment: Windows 2003 - dev28 in qa lab, Sun jdk1.4.2
Reporter: Prabhat Jha
Assigned To: Scott M Stark
Fix For: JBossAS-4.0.5.GA
testHaParitionName and testDiscoveryPort of org.jboss.test.naming.test.SimpleUnitTestCase
fail with :
javax.naming.CommunicationException: Could not obtain connection to any of these urls:
10.16.56.139:65535 and discovery failed with error: javax.naming.CommunicationException:
Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
[Root exception is javax.naming.CommunicationException: Failed to connect to server
10.16.56.139:65535 [Root exception is javax.naming.ServiceUnavailableException: Failed to
connect to server 10.16.56.139:65535 [Root exception is java.net.ConnectException:
Connection refused: connect]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1414)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at
org.jboss.test.naming.test.SimpleUnitTestCase.testDiscoveryPort(SimpleUnitTestCase.java:284)
Caused by: javax.naming.CommunicationException: Failed to connect to server
10.16.56.139:65535 [Root exception is javax.naming.ServiceUnavailableException: Failed to
connect to server 10.16.56.139:65535 [Root exception is java.net.ConnectException:
Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1385)
... 19 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server
10.16.56.139:65535 [Root exception is java.net.ConnectException: Connection refused:
connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243)
... 20 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:461)
at java.net.Socket.connect(Socket.java:411)
at java.net.Socket.<init>(Socket.java:310)
at java.net.Socket.<init>(Socket.java:212)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:53 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-3722) on Windows, org.jboss.test.naming.test.SimpleUnitTestCase fail
[ http://jira.jboss.com/jira/browse/JBAS-3722?page=comments#action_12344321 ]
Dimitris Andreadis commented on JBAS-3722:
------------------------------------------
It could be we are not running the tests properly. Are there any environment settings
needed like
MYTESTIP_1
MYTESTIP_2
?
on Windows, org.jboss.test.naming.test.SimpleUnitTestCase fail
--------------------------------------------------------------
Key: JBAS-3722
URL: http://jira.jboss.com/jira/browse/JBAS-3722
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Naming
Affects Versions: JBossAS-4.0.5.GA
Environment: Windows 2003 - dev28 in qa lab, Sun jdk1.4.2
Reporter: Prabhat Jha
Assigned To: Scott M Stark
Fix For: JBossAS-4.0.5.GA
testHaParitionName and testDiscoveryPort of org.jboss.test.naming.test.SimpleUnitTestCase
fail with :
javax.naming.CommunicationException: Could not obtain connection to any of these urls:
10.16.56.139:65535 and discovery failed with error: javax.naming.CommunicationException:
Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
[Root exception is javax.naming.CommunicationException: Failed to connect to server
10.16.56.139:65535 [Root exception is javax.naming.ServiceUnavailableException: Failed to
connect to server 10.16.56.139:65535 [Root exception is java.net.ConnectException:
Connection refused: connect]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1414)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at
org.jboss.test.naming.test.SimpleUnitTestCase.testDiscoveryPort(SimpleUnitTestCase.java:284)
Caused by: javax.naming.CommunicationException: Failed to connect to server
10.16.56.139:65535 [Root exception is javax.naming.ServiceUnavailableException: Failed to
connect to server 10.16.56.139:65535 [Root exception is java.net.ConnectException:
Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1385)
... 19 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server
10.16.56.139:65535 [Root exception is java.net.ConnectException: Connection refused:
connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243)
... 20 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:461)
at java.net.Socket.connect(Socket.java:411)
at java.net.Socket.<init>(Socket.java:310)
at java.net.Socket.<init>(Socket.java:212)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:44 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-3722) on Windows, org.jboss.test.naming.test.SimpleUnitTestCase fail
[ http://jira.jboss.com/jira/browse/JBAS-3722?page=comments#action_12344335 ]
Brian Stansberry commented on JBAS-3722:
----------------------------------------
What IP was the server bound to? Has to be 10.16.56.139. That comes from the
"node0=xxx" line in testsuite/local.properties. The 10.16.56.139 in the posted
stack trace comes from system property jbosstest.server.host, which by default also comes
from "node0=xxx" in local.properties. Only way I could see those being out of
sync is if jbosstest.server.host were being overridden in some way.
The stack trace above doesn't show much, as what's being reported is the expected
failure of connecting to the naming server via java.naming.provider.url. The real test
failure is why automatic discovery didn't find the server when the above exception was
caught. If you could attach the junit report for this test from testsuite/output/reports
that may provide more info.
on Windows, org.jboss.test.naming.test.SimpleUnitTestCase fail
--------------------------------------------------------------
Key: JBAS-3722
URL: http://jira.jboss.com/jira/browse/JBAS-3722
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Naming
Affects Versions: JBossAS-4.0.5.GA
Environment: Windows 2003 - dev28 in qa lab, Sun jdk1.4.2
Reporter: Prabhat Jha
Assigned To: Scott M Stark
Fix For: JBossAS-4.0.5.GA
testHaParitionName and testDiscoveryPort of org.jboss.test.naming.test.SimpleUnitTestCase
fail with :
javax.naming.CommunicationException: Could not obtain connection to any of these urls:
10.16.56.139:65535 and discovery failed with error: javax.naming.CommunicationException:
Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
[Root exception is javax.naming.CommunicationException: Failed to connect to server
10.16.56.139:65535 [Root exception is javax.naming.ServiceUnavailableException: Failed to
connect to server 10.16.56.139:65535 [Root exception is java.net.ConnectException:
Connection refused: connect]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1414)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at
org.jboss.test.naming.test.SimpleUnitTestCase.testDiscoveryPort(SimpleUnitTestCase.java:284)
Caused by: javax.naming.CommunicationException: Failed to connect to server
10.16.56.139:65535 [Root exception is javax.naming.ServiceUnavailableException: Failed to
connect to server 10.16.56.139:65535 [Root exception is java.net.ConnectException:
Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1385)
... 19 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server
10.16.56.139:65535 [Root exception is java.net.ConnectException: Connection refused:
connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243)
... 20 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:461)
at java.net.Socket.connect(Socket.java:411)
at java.net.Socket.<init>(Socket.java:310)
at java.net.Socket.<init>(Socket.java:212)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:35 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-3722) on Windows, org.jboss.test.naming.test.SimpleUnitTestCase fail
[ http://jira.jboss.com/jira/browse/JBAS-3722?page=comments#action_12344341 ]
Prabhat Jha commented on JBAS-3722:
-----------------------------------
I have just started a fresh test run on windows. I will attach the junit report once
it's done which will be after 4 hours.
on Windows, org.jboss.test.naming.test.SimpleUnitTestCase fail
--------------------------------------------------------------
Key: JBAS-3722
URL: http://jira.jboss.com/jira/browse/JBAS-3722
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Naming
Affects Versions: JBossAS-4.0.5.GA
Environment: Windows 2003 - dev28 in qa lab, Sun jdk1.4.2
Reporter: Prabhat Jha
Assigned To: Scott M Stark
Fix For: JBossAS-4.0.5.GA
testHaParitionName and testDiscoveryPort of org.jboss.test.naming.test.SimpleUnitTestCase
fail with :
javax.naming.CommunicationException: Could not obtain connection to any of these urls:
10.16.56.139:65535 and discovery failed with error: javax.naming.CommunicationException:
Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
[Root exception is javax.naming.CommunicationException: Failed to connect to server
10.16.56.139:65535 [Root exception is javax.naming.ServiceUnavailableException: Failed to
connect to server 10.16.56.139:65535 [Root exception is java.net.ConnectException:
Connection refused: connect]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1414)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at
org.jboss.test.naming.test.SimpleUnitTestCase.testDiscoveryPort(SimpleUnitTestCase.java:284)
Caused by: javax.naming.CommunicationException: Failed to connect to server
10.16.56.139:65535 [Root exception is javax.naming.ServiceUnavailableException: Failed to
connect to server 10.16.56.139:65535 [Root exception is java.net.ConnectException:
Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1385)
... 19 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server
10.16.56.139:65535 [Root exception is java.net.ConnectException: Connection refused:
connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243)
... 20 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:461)
at java.net.Socket.connect(Socket.java:411)
at java.net.Socket.<init>(Socket.java:310)
at java.net.Socket.<init>(Socket.java:212)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:02 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-3722) on Windows, org.jboss.test.naming.test.SimpleUnitTestCase fail
[ http://jira.jboss.com/jira/browse/JBAS-3722?page=comments#action_12344342 ]
Prabhat Jha commented on JBAS-3722:
-----------------------------------
This test passed when I ran with one-test. Either I messed up ip address or udpGroup while
running test yesterday or someting got fixed today. We will see if this happens again
during the entire test run in windows.
on Windows, org.jboss.test.naming.test.SimpleUnitTestCase fail
--------------------------------------------------------------
Key: JBAS-3722
URL: http://jira.jboss.com/jira/browse/JBAS-3722
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Naming
Affects Versions: JBossAS-4.0.5.GA
Environment: Windows 2003 - dev28 in qa lab, Sun jdk1.4.2
Reporter: Prabhat Jha
Assigned To: Scott M Stark
Fix For: JBossAS-4.0.5.GA
testHaParitionName and testDiscoveryPort of org.jboss.test.naming.test.SimpleUnitTestCase
fail with :
javax.naming.CommunicationException: Could not obtain connection to any of these urls:
10.16.56.139:65535 and discovery failed with error: javax.naming.CommunicationException:
Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
[Root exception is javax.naming.CommunicationException: Failed to connect to server
10.16.56.139:65535 [Root exception is javax.naming.ServiceUnavailableException: Failed to
connect to server 10.16.56.139:65535 [Root exception is java.net.ConnectException:
Connection refused: connect]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1414)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at
org.jboss.test.naming.test.SimpleUnitTestCase.testDiscoveryPort(SimpleUnitTestCase.java:284)
Caused by: javax.naming.CommunicationException: Failed to connect to server
10.16.56.139:65535 [Root exception is javax.naming.ServiceUnavailableException: Failed to
connect to server 10.16.56.139:65535 [Root exception is java.net.ConnectException:
Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1385)
... 19 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server
10.16.56.139:65535 [Root exception is java.net.ConnectException: Connection refused:
connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243)
... 20 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:461)
at java.net.Socket.connect(Socket.java:411)
at java.net.Socket.<init>(Socket.java:310)
at java.net.Socket.<init>(Socket.java:212)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:30 a.m.
New subject: [JBoss JIRA] Closed: (JBAS-3722) on Windows, org.jboss.test.naming.test.SimpleUnitTestCase fail
[ http://jira.jboss.com/jira/browse/JBAS-3722?page=all ]
Dimitris Andreadis closed JBAS-3722.
------------------------------------
Resolution: Done
Looks this has been resolved.
on Windows, org.jboss.test.naming.test.SimpleUnitTestCase fail
--------------------------------------------------------------
Key: JBAS-3722
URL: http://jira.jboss.com/jira/browse/JBAS-3722
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Naming
Affects Versions: JBossAS-4.0.5.GA
Environment: Windows 2003 - dev28 in qa lab, Sun jdk1.4.2
Reporter: Prabhat Jha
Assigned To: Scott M Stark
Fix For: JBossAS-4.0.5.GA
testHaParitionName and testDiscoveryPort of org.jboss.test.naming.test.SimpleUnitTestCase
fail with :
javax.naming.CommunicationException: Could not obtain connection to any of these urls:
10.16.56.139:65535 and discovery failed with error: javax.naming.CommunicationException:
Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
[Root exception is javax.naming.CommunicationException: Failed to connect to server
10.16.56.139:65535 [Root exception is javax.naming.ServiceUnavailableException: Failed to
connect to server 10.16.56.139:65535 [Root exception is java.net.ConnectException:
Connection refused: connect]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1414)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at
org.jboss.test.naming.test.SimpleUnitTestCase.testDiscoveryPort(SimpleUnitTestCase.java:284)
Caused by: javax.naming.CommunicationException: Failed to connect to server
10.16.56.139:65535 [Root exception is javax.naming.ServiceUnavailableException: Failed to
connect to server 10.16.56.139:65535 [Root exception is java.net.ConnectException:
Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1385)
... 19 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server
10.16.56.139:65535 [Root exception is java.net.ConnectException: Connection refused:
connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243)
... 20 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:461)
at java.net.Socket.connect(Socket.java:411)
at java.net.Socket.<init>(Socket.java:310)
at java.net.Socket.<init>(Socket.java:212)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6572
days inactive
6583
days old
6 comments
4 participants
participants (4)
-
Brian Stansberry (JIRA) -
Dimitris Andreadis (JIRA)
-
Prabhat Jha (JIRA)
-
Ryan Campbell (JIRA)