History | Log In     View a printable version of the current page. Get help!  
   HOME       BROWSE PROJECT       FIND ISSUES   
    QUICK SEARCH:  
Issue Details (XML | Word)

Key: HJMS-196
Type: Bug Bug
Status: Closed Closed
Resolution: Cannot Reproduce
Priority: Critical Critical
Assignee: Colin Crist
Reporter: Varun Jindal
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
HermesJMS

Hermes JMS not able to connect to JBoss(JMS) Queues (JBoss being installed on UNIX environment).

Created: 26/Jun/12 02:30 AM   Updated: 30/Jul/12 04:36 AM
Component/s: None
Affects Version/s: 1.13
Fix Version/s: 1.15

File Attachments: 1. File Screen_Shot.docx (139 kb)
Environment: Unix OS


 Description  « Hide
I have created a JNDI initial context to connect to JBOSS queues(JBOSS installed on UNIX Box). But i am not able to connect to those queues though the JBoss is up and running on UNIX box. The following exception is received.

javax.naming.CommunicationException: Could not obtain connection to any of these urls: ssapp0445v03.in.telstra.com.au:1099 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 ssapp0445v03.in.telstra.com.au/192.74.206.173:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server ssapp0445v03.in.telstra.com.au/192.74.206.173:1099 [Root exception is java.net.ConnectException: Connection timed out: connect]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)
at org.jnp.interfaces.NamingContext.list(NamingContext.java:927)
at org.jnp.interfaces.NamingContext.list(NamingContext.java:920)
at javax.naming.InitialContext.list(InitialContext.java:395)
at hermes.browser.model.tree.ContextTreeNode.setContext(ContextTreeNode.java:101)
at hermes.browser.model.tree.ContextTreeNode.<init>(ContextTreeNode.java:65)
at hermes.browser.model.tree.ContextTreeNode.<init>(ContextTreeNode.java:70)
at hermes.browser.components.ContextTreeModelFactory.create(ContextTreeModelFactory.java:60)
at hermes.browser.tasks.JNDIBrowseTask.invoke(JNDIBrowseTask.java:59)
at hermes.browser.tasks.TaskSupport.run(TaskSupport.java:175)
at hermes.browser.tasks.ThreadPool.run(ThreadPool.java:170)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.naming.CommunicationException: Failed to connect to server ssapp0445v03.in.telstra.com.au/192.74.206.173:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server ssapp0445v03.in.telstra.com.au/192.74.206.173:1099 [Root exception is java.net.ConnectException: Connection timed out: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1734)
... 11 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server ssapp0445v03.in.telstra.com.au/192.74.206.173:1099 [Root exception is java.net.ConnectException: Connection timed out: connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)
... 12 more
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:507)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301)
... 12 more



Following are the properties set:-

loader - jboss-5.1.0.GA
provider URL - ssapp0445v03.in.telstra.com.au:1099
initialContextFactory - org.jnp.interfaces.NamingContextFactory
urlPkgPrefixes - org.jboss.naming

I haven't set any rest of the properties


 All   Comments   Change History      Sort Order:
[ Permlink | « Hide ]
Colin Crist [26/Jun/12 05:15 AM]
What happens when you "telnet ssapp0445v03.in.telstra.com.au 1099" ?

If the JNDI server port is accessible to you should see:

Trying X.Y.Z...
Connected to xxxxx.
Escape character is '^]'.
��srjava.rmi.MarshalledObject|���c�>IhashlocBytest[BobjBytesq~xp �q~ur[B���T�xp+��thttp://xxxxx:8083/q~q~uq~?�sr org.jnp.server.NamingServer_Stubxrjava.rmi.server.RemoteStub���?�exrjava.rmi.server.RemoteObject�a��
                                                                                                                                                                                                                                               a3xpw8
ldndmsdevapp1J��{��"��Td8a�xConnection closed by foreign host.

If you get connection timed out then you have a problem in your network connectivity to port 1099 on that host (firewall?) or JNDI is not exposed to the network (only on loopback for example and not all interfaces, i.e. 0.0.0.0 )?



[ Permlink | « Hide ]
Colin Crist [30/Jul/12 04:36 AM]
Issue looks more like network connectivity than anything to do with Hermes.


This site is running on Atlassian JIRA, the Professional Issue Tracker with a free Open Source Project / Non-profit License.
Download and evaluate JIRA for your organisation.
Try Atlassian JIRA™ software for bug tracking and task tracking.
Powered by Atlassian JIRA™ the Professional Issue Tracker. (Enterprise Edition, Version: 3.6.5-#161) - Bug/feature request - Contact Administrators