[JNDI and Naming] - javax naming serviceunavailableexception failed to connect to server localhost 1099
3:54 a.m.
dattathreya bonakurthi [https://community.jboss.org/people/dattathreya] created the
discussion
"javax naming serviceunavailableexception failed to connect to server localhost
1099"
To view the discussion, visit: https://community.jboss.org/message/833021#833021
--------------------------------------------------------------
Hi team,
I m getting below error
javax naming serviceunavailableexception failed to connect to server <old_hostname>
1099
At present in my system, the jboss is clonned from the another system and make up.
It is running well but whenever if there are requests coming to it they taking more time
compared to earlier one.
From the serverlog file I can see it is trying to point to the old
hostname...
At the time of clonning I had made required changes and updated all the HOST & IP
entries.
Can anyone suggest me how I can make my system not to point to old host name ..
javax.naming.CommunicationException: Failed to connect to server TVCLTAPSE01:1099 [Root
exception is javax.naming.ServiceUnavailableException: Failed to connect to server
TVCLTAPSE01:1099 [Root exception is java.net.UnknownHostException: TVCLTAPSE01]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:274)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1533)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:634)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at
org.jboss.soa.esb.helpers.NamingContextPool.createContext(NamingContextPool.java:350)
at
org.jboss.soa.esb.helpers.NamingContextPool.getContext(NamingContextPool.java:304)
at
org.jboss.soa.esb.helpers.NamingContextPool.getContext(NamingContextPool.java:159)
at
org.jboss.soa.esb.helpers.NamingContextPool.getNamingContext(NamingContextPool.java:410)
at
org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getFactoryConnection(JmsConnectionPool.java:310)
at
org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.internalGetSession(JmsConnectionPool.java:222)
at
org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:194)
at
org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:159)
at
org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageProducer(JmsCourier.java:385)
at
org.jboss.internal.soa.esb.couriers.JmsCourier.internalDeliver(JmsCourier.java:209)
at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:181)
at
org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:189)
at
org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDelivery(ServiceInvoker.java:667)
at
org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.access$200(ServiceInvoker.java:569)
at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:359)
at org.jboss.soa.esb.client.ServiceInvoker.deliverSync(ServiceInvoker.java:219)
at
org.jboss.soa.esb.listeners.message.UncomposedMessageDeliveryAdapter.deliverSyncWithoutDecomposing(UncomposedMessageDeliveryAdapter.java:107)
at
org.jboss.soa.esb.listeners.message.UncomposedMessageDeliveryAdapter.deliverSync(UncomposedMessageDeliveryAdapter.java:86)
at
org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener.invoke(JBossRemotingGatewayListener.java:371)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
at
org.jboss.remoting.transport.coyote.CoyoteInvoker.service(CoyoteInvoker.java:310)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server
TVCLTAPSE01:1099 [Root exception is java.net.UnknownHostException: TVCLTAPSE01]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:248)
... 29 more
Caused by: java.net.UnknownHostException: TVCLTAPSE01
at java.net.InetAddress.getAllByName0(InetAddress.java:1150)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/833021#833021]
Start a new discussion in JNDI and Naming at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
10:12 a.m.
New subject: [JNDI and Naming] - Re: javax naming serviceunavailableexception failed to connect to server localhost 1099
Wolf-Dieter Fink [https://community.jboss.org/people/wdfink] created the discussion
"Re: javax naming serviceunavailableexception failed to connect to server localhost
1099"
To view the discussion, visit: https://community.jboss.org/message/833095#833095
--------------------------------------------------------------
I'm not sure what the problem could be.
Maybe you have a problem with the network that the hostname is used from your network
configuration.
Another possibility is that you have it hardcoded in the applicaiton or use a datastore
which contains that outdated information.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/833095#833095]
Start a new discussion in JNDI and Naming at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
10:32 a.m.
New subject: [JNDI and Naming] - Re: javax naming serviceunavailableexception failed to connect to server localhost 1099
dattathreya bonakurthi [https://community.jboss.org/people/dattathreya] created the
discussion
"Re: javax naming serviceunavailableexception failed to connect to server localhost
1099"
To view the discussion, visit: https://community.jboss.org/message/833103#833103
--------------------------------------------------------------
Hi,
There is no problem from network side .
I just want to know if I do an cloning of an jbosss from one server to another will there
any issues.
As I did the clonning for whole application under which we use jboss 4.2.2 version.
*Issue* : When ever someone is trying to call an webservice on jboss the response is very
low.
In the previous environments , the response was in seconds.
As I stated earlier, it is showing the hostname of previous server.
I want to know if it stores the hostnames in any files internally, so that I can change
and my requests can be processes in short time.
Thanks.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/833103#833103]
Start a new discussion in JNDI and Naming at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5:10 a.m.
New subject: [JNDI and Naming] - Re: javax naming serviceunavailableexception failed to connect to server localhost 1099
Wolf-Dieter Fink [https://community.jboss.org/people/wdfink] created the discussion
"Re: javax naming serviceunavailableexception failed to connect to server localhost
1099"
To view the discussion, visit: https://community.jboss.org/message/833353#833353
--------------------------------------------------------------
If you don't change the configuration you can set the bind-address with the start
command by using '+-b IP+' or even hostname.
Internaly there is no name stored, you can clone the directory to a different system, I
would remove *tmp* and *work* and maybe *data* directories.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/833353#833353]
Start a new discussion in JNDI and Naming at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
3:55 a.m.
New subject: [JNDI and Naming] - Re: javax naming serviceunavailableexception failed to connect to server localhost 1099
dattathreya bonakurthi [https://community.jboss.org/people/dattathreya] created the
discussion
"Re: javax naming serviceunavailableexception failed to connect to server localhost
1099"
To view the discussion, visit: https://community.jboss.org/message/833498#833498
--------------------------------------------------------------
Hi ,
I had tried as per ur directions but still there is no performance or result I could see.
Please help if I have missed out something which need to be updated while cloning jboss.
Thanks
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/833498#833498]
Start a new discussion in JNDI and Naming at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4094
days inactive
4097
days old
4 comments
2 participants
participants (2)
-
dattathreya bonakurthi -
Wolf-Dieter Fink