Simon Haslam's Oracle Fusion Middleware blog

Environment Variable Tip when using OHS 12.1.2

Here's a silly little issue I hit this afternoon - mostly a case of "administrator error" but a time waster nevertheless.

To recap, there was a big change to Web Tier administration in 12.1.2 in that OHS is controlled with what's now called the "WebLogic Management Framework" - in short this means OHS instance configuration is handled via WLST and lifecycle (start/stop etc) by Node Manager (i.e. OPMN has gone). You have a choice of either co-locating OHS in your existing WebLogic domain (diagrams from the Oracle Documentation):

OHS in co-located WebLogic configuration

Otherwise you can have OHS on its own:

OHS in standalone configuration

I have a customer shortly going live with Oracle HTTP Server / WebLogic Server 12.1.2. In this case OHS is in the DMZ and we have it in a standalone domain, with the main WebLogic domain/cluster in another zone.

Anyway, I was looking into a different issue and happened to have both WLS and OHS installed in one of my test VMs. After starting the standalone NodeManager, I was having trouble starting OHS and getting this error:

INFO: Running /oracle/middleware/ohs1212/ohs/bin/ httpd.worker -k start -f /oracle/admin/domains/test_ohs/config/fmwconfig/components/OHS/instances/ohs1/httpd.conf
Jun 10, 2014 4:26:34 PM oracle.ohs.plugin.nodemanager.OhsRunCommand runGeneric
INFO: /oracle/middleware/ohs1212/ohs/bin/httpd.worker: error while loading shared libraries: cannot open shared object file: No such file or directory
Jun 10, 2014 4:26:34 PM oracle.ohs.plugin.nodemanager.OhsRunCommand execute
INFO: /oracle/middleware/ohs1212/ohs/bin/ httpd.worker -k start -f /oracle/admin/domains/test_ohs/config/fmwconfig/components/OHS/instances/ohs1/httpd.conf: exit status = 127

The important message is shown in red. When I looked at lastinvocation.log in the OHS domain/server/ohs1/logs directory I found:


This is where it was going wrong - does exist in ohs1212/lib but it turned out my profile had MW_HOME set to /oracle/middleware/wls1212 and Node Manager was picking that up. I simply unset MW_HOME and restarted Node Manager - the LD_LIBRARY_PATH was set as Oracle intended and OHS started fine.

Interestingly from 12.1.2 Oracle is encouraging us use the term "Oracle Home" instead of "Middleware Home" so it's slightly odd that Node Manager even recognises MW_HOME...


Post a Comment:
Comments are closed for this entry.

Search this blog

About me
Oracle ACE Director (Middleware and SOA)
Presentation downloads

I'm speaking at Oracle OpenWorld

UKOUG Ambassador Partner
Oracle WebLogic Server 12c Certified Specialist
Oracle WebLogic Server 12c Certified Specialist