Log Entries Fluctuate on Different JMS Messages Between IP And Hostname

(Doc ID 2315146.1)

Last updated on OCTOBER 08, 2017

Applies to:

Oracle WebLogic Server - Version 12.2.1.2.0 and later
Information in this document applies to any platform.

Goal

Is the fluctuation of references to IP Address and Hostname as noticed from different JMS log-entries meaning that IP Address are used sometimes and other times is the hostname used?

see for example:

####<Sep 26, 2017 2:04:23 PM BST> <Debug> <JTANaming>  <[ACTIVE] ExecuteThread: '80' for queue: 'weblogic.kernel.Default (self-tuning)'>   <BEA-000000> <SubCoordinatorImpl.getSubCoordinatorInfo(managed1_XXXX02+10.999.999.999:61001+XXX02+t3+)>
----> Ip used
####<Sep 26, 2017 2:04:23 PM BST> <Debug> <JTANaming>  <[ACTIVE] ExecuteThread: '80' for queue: 'weblogic.kernel.Default (self-tuning)'>    <BEA-000000> <ServerCoordinatorDescriptor.scheduleRefresh(managed1_XXXX02+hostname:61001+XXX02+t3+)>
----> Host used
####<Sep 26, 2017 2:04:23 PM BST> <Debug> <JTANaming>  <[ACTIVE] ExecuteThread: '84' for queue: 'weblogic.kernel.Default (self-tuning)'>   <BEA-000000> <SecureAction.runAction Use  Subject= <WLS Kernel>for action:refreshServer to t3://hostname:61001>
----> Host used


Concerned about this is because may be for some network configuration issue the hostname may not resolve and cause error.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms