Fixes are available
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
APAR status
Closed as program error.
Error description
java.io.IOException: Server returned HTTP response code: 500 occurs when the xJCL for a parallel job contains special characters in the job name.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.5 * **************************************************************** * PROBLEM DESCRIPTION: Parallel Job Manager jobs having * * special characters in the job name * * have issues retrieving sub-job logs as * * shown below: * * System.out: [06/27/13 11:28:35:075 * * EDT] ********** Begin * * XDCGIVT!_#PAR#:64994:64995 log * * ********** * * System.out: [06/27/13 11:28:35:075 * * EDT] Unable to retrieve sub job * * [XDCGIVT!_#PAR#:64994:64995] logs due * * to the following exception: * * java.io.IOException: Server returned * * HTTP response code: 500 for * * URL: * **************************************************************** * RECOMMENDATION: * **************************************************************** When a WebSphere batch parallel job containing one or more special characters in the job name, is submitted, a failure will occur during the underlying HTTP communication that takes place. The string containing the character is not encoded, causing the failure.
Problem conclusion
The code which handles this parameter has been updated to encode the string prior to making the HTTP call. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.1. 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
PM93373
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-07-18
Closed date
2013-10-22
Last modified date
2014-01-08
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
11 January 2022