PQ76492: In PME 502 Work Area service the values for MaxSendSize and MaxReceiveSize got hard coded to their default values | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description In PME 502 Work Area service the values for MaxSendSize and MaxReceiveSize got hard coded to their default values rather than the values entered by the user under the Work Area Service in the Admin Console. In 502, the vaules set by a user are disregarded. This fix will also address another very minute issue. In 502, when a user calls one of the API methods on Work Area prior to doing a begin (a legal action) a NoActivityException is thrown. This doesn't adversly effect the user, they still get the correct results. Howerver, the NoActivityException is logged to the FFDC files which could lead to concerns or false blame by a user.Local fix Problem summary **************************************************************** * USERS AFFECTED: Applications that use the WorkArea service * * on WebSphere PME 5.0.2 are affected. * **************************************************************** * PROBLEM DESCRIPTION: Remote invocations associated with * * WorkArea context may unexpectedly fail * * with a com.ibm.ws.javax.activity. * * SystemException. or with an * * org.omg.CORBA.IMP_LIMIT. * * Remote invocations associated with * * a WorkArea context which is larger * * than the configured maximum send size * * or maximum receive size may * * unexpectedly succeed. * * A WebSphere server's FFDC logs may * * register com.ibm.ws.javax.activity * * .NoActivity exceptions although the * * application may have executed without * * error. * **************************************************************** * RECOMMENDATION: * **************************************************************** First, users may configure a maximum send and a maximum receive size using the WebSphere administration console. In 5.0.2, these configured limits are not processed by the WebSphere server runtime; instead, a default value of 32767 bytes are being used. Applications attempting to send a request with more than 32767 bytes contained in a WorkArea may fail with a com.ibm.ws.javax.activity.SystemException or an org.omg.CORBA.IMP_LIMIT. Applications that wish to deny requests with more than 32767 bytes in a WorkArea context are unable to do so. Second, applications calling read-only functions on the WorkArea service in the absence of an active work area will cause com.ibm.ws.javax.activity.NoActivity exceptions to be written to the WebSphere server's FFDC logs. These exceptions are internal only and do not indicate a real problem and should not be written to the logs.Problem conclusion With the fix to this apar, the WebSphere PME 5.0.2 runtime will correctly apply the configured maximum send and receive limits. Also, the com.ibm.ws.javax.activity.NoActivity exception will no longer be logged to the WebSphere server's FFDC logs.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > Enterprise Edition (EE)
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ76492
IBM Group: Software Group
Modified date: Sep 22, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.