PQ82937: MDB CLASSIFICATION TROUBLE | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description After classify any MDB workload the application CR abends with signal=SIGSEGV sicode=SEGV_PROTECT ABEND IN *PATHNAM/unicode2UTF After this, the CR will not restart. Upon restart of the server, initialization never completed. It ABENDs with signal=SIGSEGV sicode=SEGV_PROTECT and *PATHNAM/unicode2UTF. To confirm you are experiencing a problem in the MDB classification logic, enable RAS tracing with this: MDB=all=enabled And then look for resulting trace entries similar to: Trace: 2003/12/03 19:13:49.706 01 t=8D2CF0 c=UNK key=S2 (13007002) FunctionName: com.ibm.ejs.jms.listener.WS390EndPointClassificationParser SourceId: com.ibm.ejs.jms.listener.WS390EndPointClassificationParser Category: ENTRY ExtendedMessage: getClassificationString; SimpleMDBListenerPort, <null> Trace: 2003/12/03 19:13:49.706 01 t=8D2CF0 c=UNK key=S2 (13007002) FunctionName: com.ibm.ejs.jms.listener.WS390EndPointClassificationParser SourceId: com.ibm.ejs.jms.listener.WS390EndPointClassificationParser Category: EXIT ExtendedMessage: getClassificationString; <null> . Its the null ClassificationString that is the problem indicator.Local fix There are two possible work-arounds available to choose in this situation. CHOICE A: The easier approach is to just disable classification. To do this follow these steps: 1- In the administrative console page, click Environment>Manage WebSphere Variables and remove the variable endpoint_config_file from the entries. 2- Restart the server to 'pick-up' the change. . CHOICE B: If you want/need to run with classification then you will need to follow these steps: . 1) Determine which listener port has a <null> classification string. Do this by enabling MDB tracing: MDB=all=enabled 2) Run your problem scenario again. Then review the trace data, looking for a line similar to this: ExtendedMessage: getClassificationString; SimpleMDBListenerPort, <null> 3) You will then need to add an empty endpoint entry, that has "MDB" defined as the default classification, to the endpoint configuration file. Using the example above the empty endpoint would be added for SimpleMDBListenerPort. 4) Finally restart the server to pick up the change 5) If you have more than one 'unclassified' endpoint then you will need to add multiple empty endpoint entries to the endpoint configuration file.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: MDB endpoint classification support * * assigns null classification string for * * endpoints not included in the endpoint * * classification file. The default "MDB" * * classification string should be used * * instead. * **************************************************************** * RECOMMENDATION: * **************************************************************** Null classification string is used for endpoints not included in the endpoint classification file. The Controller Region abends with signal=SIGSEGV sicode=SEGV_PROTECT ABEND IN *PATHNAM/unicode2UTF.Problem conclusion Assign default "MDB" classification string when the endpoint is not in the classification file. APAR PQ82937 is associated with SERVICE LEVEL W502002 of WebSphere Application Server V5.0 for z/OS.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
|
Document Information |
Current web document: swg1PQ82937.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 #: PQ82937
IBM Group: Software Group
Modified date: Mar 3, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.