PM97514: UNABLE TO ASSOCIATE DIFFERENT APPLICATIONS TO DIFFERING HTTPENDPOINTS

Fixes are available

APAR status

Closed as program error.

Error description

Unable to configure Liberty profile server.xml such that two
applications are running against differing endpoints.

It appears that virtual hosting is not fully configurable and
applications only start on a single endpoint.

Local fix

```
no
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty Core wanting to use virtual  *
*                  hosting.                                    *
****************************************************************
* PROBLEM DESCRIPTION: Virtual hosting does not function on    *
*                      the Liberty profile.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
You are unable to configure applications to run on different
ports - there are no runtime errors or warnings.

Problem conclusion

The configuration code and the underlying implementation have
been altered such that a user can configure virtual hosting,
this has involved sizeable modifications to the transport
component within the Liberty profile, as well as modifications
in the web container.

The key configuration elements when configuring virtual
hosting after applying the fix pack containing this code are:

1.  The host attribute value(s) of the httpEndpoint(s)
2.  The id attribute value(s) of the httpEndpoint(s)
3.  The virtualHost configuration element(s) id value
4.  The hostAlias sub-element configuration
5.  The allowFromEndpoint sub-element configuration if used
6.  The virtual host configuration in the ibm-web-bnd.xml /
ibm-web-bnd.xmi file of the WAR

The example below shows one of the more common usages of
virtual hosting to give an understanding of some of the
configuration required.  This example shows how to configure
two applications running on differing ports, further in this
example one application is only available on the localhost
interface.

Additions to the server.xml :

<httpEndpoint id="defaultHttpEndpoint" host="*"
httpPort="9080" />
<httpEndpoint id="localHostOnly" host="localhost"
httpPort="9081" />

<virtualHost id="alice">
     <hostAlias>your_host_name:9080</hostAlias>
</virtualHost>

<virtualHost id="bob">
     <hostAlias>localhost:9081</hostAlias>
</virtualHost>

<application id="App1" location="myApp.ear" name="App1"
type="ear"/>
<application id="App2" location="myApp2.war" name="App2"
type="war"/>

The defaultHttpEndpoint exposes all interfaces on port 9080,
the http endpoint with id="localHostOnly" specifies
host="localhost", meaning that port 9081 is only exposed on
the localhost interface.

If App1 has a WAR file with an ibm-web.bnd.xml file specifying
<virtual-host name="alice"/> then  this application can only
be accessed at your_host_name:9080/app1_context_root.

If App2 (which is a WAR) has an ibm-web-bnd.xml file
specifying <virtual-host name="bob"/> then this application
can only be accessed at localhost:9081/app2_context_root.

If a third application were deployed which specified no
specific virtual host, that application in this configuration
would be available on all interfaces of the
defaultHttpEndpoint on port 9080, excluding
your_host_name:9080 - for example it could be accessed on
localhost:9080/app3_context_root.



The fix for this APAR is currently targeted for inclusion in
fix pack 8.5.5.2. Please refer to the Recommended Updates page
for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM97514
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-09-20
Closed date
2014-01-23
Last modified date
2014-01-23

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WAS LIBERTY COR
Fixed component ID
5725L2900

Applicable component levels

R855 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PM97514: UNABLE TO ASSOCIATE DIFFERENT APPLICATIONS TO DIFFERING HTTPENDPOINTS

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R855 PSY

Document Information

Share your feedback

Need support?