SOA server not starting: Due to change of hostname of SOA suite 11g

Question

Hi friends,
My machine has been recently moved to a new location and hostname (ip address remains same) has changed. Hence, the soa server (admin server still running) on my machine is not starting up.
Some details are:
a.) Earlier hostname: CALTP8BB13
b.) New hostname: CALTP8BB16
From the soa server log files the details are as follows:
####<Jul 13, 2010 6:31:52 PM IST> <Info> <messaging.interception> <CALTP8BB16> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1279026112029> <BEA-400000> <Initializing message interception service>
####<Jul 13, 2010 6:31:54 PM IST> <Error> <Configuration Management> <CALTP8BB16> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1279026114342> <BEA-150000> <An error occurred while establishing a connection back to the adminstration server t3://CALTP8BB13:7001 during startup. Since bootstrap succeeded check that t3://CALTP8BB13:7001 uniquely identifies the administration server.
javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: CALTP8BB13]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:34)
     at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:411)
     at weblogic.jndi.Environment.getInitialReference(Environment.java:245)
     at weblogic.server.channels.RemoteChannelServiceImpl.registerInternal(RemoteChannelServiceImpl.java:173)
     at weblogic.server.channels.RemoteChannelServiceImpl.registerForever(RemoteChannelServiceImpl.java:146)
     at weblogic.protocol.ConnectMonitorFactory.registerForever(ConnectMonitorFactory.java:88)
     at weblogic.management.provider.MSIService.registerForReconnectToAdminServer(MSIService.java:173)
     at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService.start(CompatibilityMBeanServerService.java:154)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Any pointers regarding the same will be helpful.
Regards,
Shomit

Answer 1

Hi Shomit
As far as I know, the Domains Hostname is stored only in config.xml file. So IP Address is same just Host name is changed CALTP8BB13 to CALTP8BB16. Check for some basic things.
1. If on Windows OS, try adding this new Hostname and its IP address in hosts file located at C:\WINDOWS\system32\drivers\etc. If on Unix Env, I guess there should be a similar file to set the hostnames mapped with IP addresses.
2. Since the machine is moved to a brand new location and incase kind of different network, check the firewall settings to see if firewall is blocking this new hostname.
3. To make sure the domain is still good, I guess you already tested with old hostname after moving to new building. Try testing by giving the direct IP address also. This is just confirmation test to make sure domain is not messed up. If both of these works, it simply means issue is with Hostname and IP not getting mapped or new hostname getting blocked over the network. May be network folks can pitch in.
Hostname or IP addresses should not be in any startup or env scripts. Domainname, servername will be definetly there in lot of files but not the hostname or ip address as far as I know.
Thanks
Ravi Jegga