javax.naming.ServiceUnavailableException

Failed to query JNDI: Failed to connect to the server at tcp://lu201a001v.au.oceania.intranet:4222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://lu201a001v.au.oceania.intranet:4222]

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web3

  • Stack trace

    • javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://lu201a001v.au.oceania.intranet:4222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://lu201a001v.au.oceania.intranet:4222] at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669) at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489) at javax.naming.InitialContext.lookup(InitialContext.java:351) at com.mercury.ws.jms.ConnectionManagerImpl.initialize(ConnectionManagerImpl.java:99) at com.mercury.ws.jms.JMSSupportImpl.initialize(JMSSupportImpl.java:28) at com.mercury.ws.jms.JMSBridge.init_jms(JMSBridge.java:154) Caused by: javax.jms.JMSException: Failed to connect to the server at tcp://lu201a001v.au.oceania.intranet:4222 at com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:817) at com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:913) at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:1002) at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:2707) at com.tibco.tibjms.TibjmsQueueConnection.<init>(TibjmsQueueConnection.java:36) at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:186) at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:239) at com.tibco.tibjms.TibjmsQueueConnectionFactory.createQueueConnection(TibjmsQueueConnectionFactory.java:87) at com.tibco.tibjms.naming.TibjmsContext$Messenger.request(TibjmsContext.java:325) at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:655) ... 5 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.