PQ89244: WLM MAP FILE CAUSES AN INFINITE LOOP

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Setting the WLM transaction class mapping file via wsadmin.sh
caused to an infinite loop. The loop was also experienced when
the command was issued via the batch program.
For example:
 $AdminConfig modify was.transactionClassMappingFile
 (cells/w8cell/nodes/w8nodej/servers/w8sw81J:server.xml#Propert
 y_17)
 {value
 /USRS/was/runtime/wlm/w8-transclass.txt}
.
Customer is also seeing loop condition when performing
additional admin functions. For example:
the code issues this command:
$AdminConfig create HTTPTransport
cells/w8cell/nodes/w8nodej/servers/w8sw81J:server.xml#WebContain
er_1)
 {sslEnabled true} {sslConfig w8dm/W8KEYRINGWBC} {address {{host
*}
 {port 9480}}}
wsadmin trace shows:
 &#65517;5/1/04 13:35:51:280 EEST&#65529; 30708a6d SOAPConnector <
 invokeTemplate - failed invoke &#65517;SOAPException:
 faultCode=SOAP-ENV:Client; msg=EDC5120I Interrupted function
 call.; targetException=java.net.SocketException: EDC5120I
 Interrupted function call.&#65529;
 at
 org.apache.soap.transport.http.SOAPHTTPConnection.send(Unknown
 Source)
 at org.apache.soap.rpc.Call.invoke(Unknown Source)
 at
 com.ibm.ws.management.connector.soap.SOAPConnectorClient$4.run(
 SOAPConnectorClient.java:578)
 at java.security.AccessController.doPrivileged(Native Method)
 at
 com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke
 Template(SOAPConnectorClient.java:575)
 at
 com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke
 (SOAPConnectorClient.java:511)
 at
 com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke
 (SOAPConnectorClient.java:336)
 at $Proxy0.invoke(Unknown Source)
 at
 com.ibm.ws.management.AdminClientImpl.invoke(AdminClientImpl.ja
 va:162)
 at
 com.ibm.websphere.management.configservice.ConfigServiceProxy.g
 etAttributes(ConfigServiceProxy.java:657)
 at
 com.ibm.ws.scripting.types.FIPSTSHelper.getAttributeListFromON(
 FIPSTSHelper.java:88)
 at
 com.ibm.ws.scripting.types.PropertyTSHelper.getNameValuePropert
 yValues(PropertyTSHelper.java:280)
 at
 com.ibm.ws.scripting.types.PropertyTSHelper.getNameValuePropert
 yValues(PropertyTSHelper.java:282)
 at
 com.ibm.ws.scripting.types.PropertyTSHelper.getNameValuePropert
 yValues(PropertyTSHelper.java:282)
 at
 com.ibm.ws.scripting.types.PropertyTSHelper.getNameValuePropert
 yValues(PropertyTSHelper.java:282)
 at
 com.ibm.ws.scripting.types.PropertyTSHelper.getNameValuePropert
 yValues(PropertyTSHelper.java:282)
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: Setting the WLM transaction class       *
*                      mapping file via the wsadmin.sh modify  *
*                      command may cause an infinite loop.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Setting the WLM transaction class mapping file via the wsadmin
modify command may cause an infinite loop.  The wsadmin command,
if allowed to run long enough, will terminate with an exception
similar to the one below.  Prior to termination, CPU utilization
will spike and stay there.

This problem will occur only if the transaction class mapping
file property of the WebContainer has no value before the modify
command is issued.

Example of failing command:
   $AdminConfig modify was.transactionClassMappingFile
      (cells/w8cell/nodes/w8nodej/servers/w8sw81J:server.xml
         #Property_17) {{value /runtime/wlm/w8-transclass.txt}}

The wsadmin exception trace may look something like the
following:
5/1/04 13:35:51:280 EEST  30708a6d SOAPConnector <
  invokeTemplate - failed invoke  SOAPException:
  faultCode=SOAP-ENV:Client; msg=EDC5120I Interrupted function
  call.; targetException=java.net.SocketException: EDC5120I
  Interrupted function call.
at org.apache.soap.transport.http.SOAPHTTPConnection.
  send(UnknownSource)
at org.apache.soap.rpc.Call.invoke(Unknown Source)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient$4.
  run(SOAPConnectorClient.java:578)
. . .  (some entries deleted)
at com.ibm.ws.scripting.types.PropertyTSHelper.
  getNameValuePropertyValues(PropertyTSHelper.java:282)
at com.ibm.ws.scripting.types.PropertyTSHelper.
  getNameValuePropertyValues(PropertyTSHelper.java:282)
at com.ibm.ws.scripting.types.PropertyTSHelper.
  getNameValuePropertyValues(PropertyTSHelper.java:282)
at com.ibm.ws.scripting.types.PropertyTSHelper.
  getNameValuePropertyValues(PropertyTSHelper.java:282)
Problem conclusion
Corrections were made to a recursive method invocation.

APAR PQ89244 is associated with SERVICE LEVEL W502012 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ89244
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-05-23
Closed date 2004-06-30
Last modified date 2004-08-04

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ90251    UP04/07/09 P F407

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ89244.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ89244
IBM Group: Software Group
Modified date: Aug 4, 2004