A fix is available
APAR status
Closed as program error.
Error description
WebSphere Application Server controller regions issue message BBOO0325W when an IIOP request stays active for longer than the timeout value specified by protocol_iiop_local_timeout. For example: BBOO0325W An IIOP request for Class Name 'biz.aa.bbbbbbb.cccc.dddddHome' and Method Name '?ヤ ?￴ ', to 'hostname=h1111.h222.BIZ port=###', has timed out. SessionHandle=################, Request ID=########. The unprintable method names appear if the timed-out IIOP request is a LOCATE or a RE-LOCATE. For a LOCATE request, the Class name will be an EJB HOME interface name. For a RE-LOCATE, the class name could be anything. The garbled method name is the result of incorrect method name translation between ascii and ebcdic.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 * * * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS * * controller region version 6.1 issues * * BBOO0325W timeout message with * * garbled method name for an IIOP * * request. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** The code page of the operation name and the operation name are managed by 2 fields within the ORBR (bbooorbr). The code page of the operation name represents the code page of the current connection related to the ORBR request (ex. for a local communication connection the code page is EBCDIC). The garbled operation name appearing in the BBOO0325W message was caused by a mismatch between these 2 fields. example of garbled message. BBOO0325W An IIOP request for Class Name 'biz.aa.bbbbbbb.cccc.dddddHome' and Method Name '??', to 'hostname=h1111.h222.BIZ port=###', has timed out. SessionHandle=################, Request ID=########.
Problem conclusion
The management scheme of the operation name within the ORBR is now based on maintaining the operation name in the EBCDIC code page within the native at all times. To implement this new management scheme the following code changes have been made. The GIOP message build code (bbocgiop) was modified to convert the operation name to ASCII before writing the GIOP message based on the operation flag in the ORBR. Also bboojorb and bboofjni were modified to remove the conversion of operation name to ASCII so that operation name remains EBCDIC in ORBR. APAR PM10317 is currently targeted for inclusion in Service Level (Fix Pack) 7.0.0.13 of WebSphere Application Server V7.0. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM10317
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-03-18
Closed date
2010-10-05
Last modified date
2010-11-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
BBGUBINF BBOUBINF
Fix information
Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R700 PSY UK61114
UP10/10/21 P F010
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.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 February 2022