[
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