Monday, 17 February 2014

Problems with IBM HTTP Server, WebSphere Plugin, WebSphere Application Server and Virtual Hosts

I was trying to resolve an issue whereby requests for Business Space ( part of IBM Business Monitor ) weren't being routed from IBM HTTP Server via the WebSphere Plugin to WebSphere Application Server

To find out what was going, I changed the error level in the Plugin configuration file: -

/opt/IBM/WebSphere/Plugins/config/webserver/config/webserver/plugin-cfg.xml

from: -

   <Log LogLevel="Error" Name="/opt/IBM/WebSphere/Plugins/logs/webserver/http_plugin.log"/>

to: -

   <Log LogLevel="Debug" Name="/opt/IBM/WebSphere/Plugins/logs/webserver/http_plugin.log"/>

and, having restarted IHS, I saw: -

...
[17/Feb/2014:16:45:00.08133] 00000899 cabcc700 - DEBUG: mod_was_ap22_http: as_child_init pid= 00000899
[17/Feb/2014:16:45:06.13870] 00000899 c4b2f700 - DEBUG: lib_util: parseHostHeader: Host: 'rhel6.uk.ibm.com', port 8443
[17/Feb/2014:16:45:06.13878] 00000899 c4b2f700 - DEBUG: ws_common: websphereCheckConfig: Current time is 1392655506, next stat time is 1392655560
[17/Feb/2014:16:45:06.13880] 00000899 c4b2f700 - DETAIL: ws_common: websphereShouldHandleRequest: trying to match a route for: vhost='rhel6.uk.ibm.com'; uri='/BusinessSpace'
[17/Feb/2014:16:45:06.13883] 00000899 c4b2f700 - DETAIL: ws_common: websphereShouldHandleRequest: No route found
[17/Feb/2014:16:45:06.13894] 00000899 c4b2f700 - DEBUG: mod_was_ap22_http: as_handler: In the app server handler
[17/Feb/2014:16:45:06.13929] 00000899 c4b2f700 - DEBUG: mod_was_ap22_http: in as_logger
[17/Feb/2014:16:45:07.09305] 000008bf cabcc700 - DEBUG: mod_was_ap22_http: as_child_init pid= 000008BF


in: -

/opt/IBM/WebSphere/Plugins/logs/webserver/http_plugin.log

Guess what the problem is ?

Yep, you've guessed it - I'd forgotten to add a Virtual Host entry for WAS for the required port - 8443.

I made, and saved, the change, synchronised the WAS nodes, restarted the appropriate JVM ( the WebApp cluster ), and voila, Business Space can now be accessed via IHS/Plugin: -



No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...