Friday 1 May 2015

SOA Returning the wrong value for LOCAL_CLIENTLOCAL Constant

While building a Oracle Fusion Middleware stack on a single RedHat 6 VM an entry was added to the /etc/hosts file to spoof another URL bound to the SOA’s local listen address.

The (sanitzed) entry was:
128.128.128.128 old-env.example.com

Further along in the setup of this environment the hosts entry was removed. However, issues occurred in SOA/BPM whengetFactory().getBPMServiceClient() was called to set the LOCAL_CLIENTLOCAL Constant. It was returning old-env.example.com which was no longer a valid URL.

After hunting through MBean Directory, Config Plans and MDS Schema we fortunately we recalled that this value had been set in /etc/hosts. Performing a restart of the whole domain (Admin Server, SOA, OSB, NodeManager) did not help.

Clearly some caching of the invalid hostname was being done, most likely at an OS level due to the JVM restarts achieving nothing.

As this was a development environment the VM could be easily rebooted, and this resolved the cached Domain Name.

No comments:

Post a Comment