This issue is resolved.
I gave entry of the ip and server name of the hostname in the /etc/hosts
file
Regards,
Deepu Janardhananachary
From: Evans, Martin [mailto:martin.evans_at_credit-suisse.com]
Sent: Wednesday, December 30, 2009 7:55 PM
To: users_at_genericjmsra.dev.java.net
Cc: Ramesh.Parthasarathy_at_Sun.COM
Subject: RE: RE: Caused by: javax.naming.ServiceUnavailableException:
Failed to query JNDI
Are you using the same physical server?
The first exception shows "tcp://ldtibadm" as the JNDI server, the
second has "tcp://hostName" ?
If you changed to a new physical server, I would check you can lookup
the JNDI server ok from the new host.
Martin
________________________________
From: Deepu Syamaladevi Janardhananachary
[mailto:Deepu.Janardhananachary_at_ust-global.com]
Sent: 30 December 2009 04:44
To: users_at_genericjmsra.dev.java.net
Cc: Ramesh.Parthasarathy_at_Sun.COM
Subject: RE: Caused by: javax.naming.ServiceUnavailableException: Failed
to query JNDI
On restarting the server, I got the exception like this
Since it was working in other server of the same version, can it be due
to any network issue or server specific problem?
[#|2009-12-30T02:46:23.994-0600|WARNING|sun-appserver9.1|javax.enterpris
e.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=e7120fe0-b0
fa-4d1f-a689-2feedf9d8a4e;|javax.resource.ResourceException: Failed to
connect to the server at tcp://hostName:7222
at
com.sun.genericra.util.ExceptionUtils.newResourceException(ExceptionUtil
s.java:73)
at
com.sun.genericra.inbound.InboundJmsResourcePool.initialize(InboundJmsRe
sourcePool.java:149)
at
com.sun.genericra.inbound.EndpointConsumer.initialize(EndpointConsumer.j
ava:133)
at
com.sun.genericra.inbound.EndpointConsumer.start(EndpointConsumer.java:1
26)
at
com.sun.genericra.GenericJMSRA.endpointActivation(GenericJMSRA.java:215)
at
com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(Co
nnectorMessageBeanClient.java:252)
at
com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.
java:209)
at
com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFac
toryImpl.java:280)
at
com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:53
6)
at
com.sun.enterprise.server.ApplicationLoader.doLoad(ApplicationLoader.jav
a:188)
at
com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicati
onLoader.java:126)
at
com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:244)
at
com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:225)
at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLife
cycle.java:217)
at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.
java:442)
at
com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServ
er.java:120)
at com.sun.enterprise.server.PEMain.run(PEMain.java:411)
at com.sun.enterprise.server.PEMain.main(PEMain.java:338)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.server.PELaunch.main(PELaunch.java:412)
Caused by: javax.jms.JMSException: Failed to connect to the server at
tcp://hostName:7222
at
com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:821)
at
com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:915)
at
com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:1274)
Regards,
Deepu Janardhananachary
From: Deepu Syamaladevi Janardhananachary
[mailto:Deepu.Janardhananachary_at_ust-global.com]
Sent: Wednesday, December 30, 2009 12:39 PM
To: users_at_genericjmsra.dev.java.net
Subject: Caused by: javax.naming.ServiceUnavailableException: Failed to
query JNDI
Hi,
I am using Sun Java System Application Server 9.1_02 (build b04-fcs) and
resourceadapter-version 1.7 for MDB to listen to tibco queue.
It was working fine in my previous server of the same version without
any problem. But in the newly given glassfishserver, it is showing error
while deploying itself.
Caused by: javax.naming.ServiceUnavailableException: Failed to query
JNDI: Failed to connect to the server at tcp://ldtibadm:7222 [Root
exception is javax.jms.JMSException: Failed to connect to the server at
tcp://ldtibadm:7222]
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:392)
at
com.sun.genericra.util.ObjectBuilderFactory$JndiObjectBuilder.createObje
ct(ObjectBuilderFactory.java:98)
... 46 more
Caused by: javax.jms.JMSException: Failed to connect to the server at
tcp://ldtibadm:7222
at
com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:821)
at
com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:915)
at
com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:1274)
Did anyone faced similar issue? Please help
Regards,
Deepu Janardhananachary
========================================================================
======
Please access the attached hyperlink for an important electronic
communications disclaimer:
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
========================================================================
======