Fixes are available
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
FFDC for a org.apache.http.conn.HttpHostConnectException exception is created when a WebSphere application server has the usage metering feature enabled, but the IBM Cloud Private metering service is unavailable to receive registration and metrics. The FFDC log file will be as follows: Exception = org.apache.http.conn.HttpHostConnectException Source = com.ibm.ws.usage.metering.common.RegisterTask.run probeid = 111 Stack Dump = org.apache.http.conn.HttpHostConnectException: Connect to localhost:8040 [localhost/127.0.0.1] failed: Connection refused at org.apache.http.impl.conn.DefaultHttpClientConnectionOperato r.connect(DefaultHttpClientConnectionOperator.java:159) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager .connect(PoolingHttpClientConnectionManager.java:373) at org.apache.http.impl.execchain.MainClientExec.establishRoute (MainClientExec.java:381) at org.apache.http.impl.execchain.MainClientExec.execute(MainCl ientExec.java:237) at org.apache.http.impl.execchain.ProtocolExec.execute(Protocol Exec.java:185) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.j ava:89) at org.apache.http.impl.execchain.RedirectExec.execute(Redirect Exec.java:111) at org.apache.http.impl.client.InternalHttpClient.doExecute(Int ernalHttpClient.java:185) at org.apache.http.impl.client.CloseableHttpClient.execute(Clos eableHttpClient.java:83) at org.apache.http.impl.client.CloseableHttpClient.execute(Clos eableHttpClient.java:108) at com.ibm.ws.usage.metering.common.MeteringMetadata.executeReq uest(MeteringMetadata.java:166) at com.ibm.ws.usage.metering.common.RegisterTask.register(Regis terTask.java:211) at com.ibm.ws.usage.metering.common.RegisterTask.run(RegisterTa sk.java:99)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty - Usage Metering * **************************************************************** * PROBLEM DESCRIPTION: Unnecessary HttpHostConnectException * * FFDC logged for usage metering * **************************************************************** * RECOMMENDATION: * **************************************************************** FFDC for a org.apache.http.conn.HttpHostConnectException exception is created when a WebSphere application server has the usage metering feature enabled, but the IBM Cloud Private metering service is unavailable to receive registration and metrics. The FFDC log file will be as follows: Exception = org.apache.http.conn.HttpHostConnectException Source = com.ibm.ws.usage.metering.common.RegisterTask.run probeid = 111 Stack Dump = org.apache.http.conn.HttpHostConnectException: Connect to localhost:8040 [localhost/127.0.0.1] failed: Connection refused at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.co nnect(DefaultHttpClientConnectionOperator.java:159) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.con nect(PoolingHttpClientConnectionManager.java:373) at org.apache.http.impl.execchain.MainClientExec.establishRoute(Mai nClientExec.java:381) at org.apache.http.impl.execchain.MainClientExec.execute(MainClient Exec.java:237) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec .java:185) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java: 89) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec .java:111) at org.apache.http.impl.client.InternalHttpClient.doExecute(Interna lHttpClient.java:185) at org.apache.http.impl.client.CloseableHttpClient.execute(Closeabl eHttpClient.java:83) at org.apache.http.impl.client.CloseableHttpClient.execute(Closeabl eHttpClient.java:108) at com.ibm.ws.usage.metering.common.MeteringMetadata.executeRequest (MeteringMetadata.java:166) at com.ibm.ws.usage.metering.common.RegisterTask.register(RegisterT ask.java:211) at com.ibm.ws.usage.metering.common.RegisterTask.run(RegisterTask.j ava:99)
Problem conclusion
The usage metering feature in WebSphere application server does not expect the IBM Cloud Private metering service to be available at all times, and will properly handle the HttpHostConnectException exception and send registration and metrics at a later time when the metering service becomes available. The exception is not unexpected and should not result in an FFDC log file. The usage metering feature has been updated to not create an FFDC file for the HttpHostConnectException exception. The fix for this APAR is currently targeted for inclusion in fix packs 9.0.0.11 and 8.5.5.16 for WebSphere Application Server and 19.0.0.1 for WebSphere Application Server Liberty. 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
PH07247
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-01-14
Closed date
2019-01-24
Last modified date
2019-01-24
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
RCD0 PSY
UP
Document Information
Modified date:
28 April 2022