Fixes are available
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
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.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
An '$AdminApp edit' command that worked in v7.0 no longer works in v8.5.5. The following command results in a java.util.regex.PatternSyntaxException: $AdminApp edit AppName {-WebServicesClientBindPortInfo {{AppName.jar .* service/utilitycomponent/PrintManager {{ http://hostname.com/AppName/utility/service/printmanager/intf/1} PrintManager} {} {} {} {} http://hostname2.com/AppNameutilitycomponent/PrintManagerV3/Prin tManager.svc {}}}} The error is: java.util.regex.PatternSyntaxException: java.util.regex.PatternSyntaxException: Illegal repetition near index 87 This error is seen in the SystemOut.log file and in the wsadmin.traceout file.
Local fix
There seems to be a problem with how we process the wildcard (".*") in the command. If the client replaces the wildcard with the specific bean they want to use, then the command has no problem running in my test environment. If they edit their script and change lines 282 and 283 to something like this: set webservicesclientbindingportinfo1 [list "EpsilonCommunicationManagementComponentEJB.jar" PlanCommunicationManagementBean $websr1 $port1 "" "" "" "" $http1 ""] replacing ".*" with "PlanCommuncationManagementBean" their script should not have any errors.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: Problem with regular expression in * * application installation code * **************************************************************** * RECOMMENDATION: * **************************************************************** Certain characters were not accounted for in regular expressions on application installation and edit.
Problem conclusion
The code is updated so the problem no longer occurs. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.11 and 8.5.5.5. 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
PI25880
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-09-17
Closed date
2015-01-19
Last modified date
2015-01-19
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
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022