PQ71903: J2EE APPLICATION SERVER HANGS WHEN STOP ISSUED ON A SERVER WHERE AN APPLICATION THAT USES IMS JDBC CONNECTOR IS INSTALLED.

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
When the stop command is issued to a WebSphere J2EE application
server that contains an application which uses the IMS JDBC
Connector, the application server does not terminate and
must be cancelled.  The application server also will not respond
to being recycled from the SM EUI.
.
Message "BBON1017E Server instance <servinst1> on server
<servera> could not be stopped." may be observed in the J2EE
application server region job output.  The J2EE application
server region job output may show LE message CEE3250C along
with an SVC dump indicating USER COMPLETION CODE=4088 REASON
CODE=00000063.  In the SVC dump, there is a TCB containing
Abend S0052 with Reg15 containing a 08 for the reason code for
the abend052.  That TCB shows the following traceback stack:
sysThreadEnterBlockingSection
jni_GetPrimitiveArrayElements
DFSAERG0
Java_com_ibm_ims_base_JavaToDLI_JavTDLI1
com/ibm/ims/base/JavaToDLI.JavTDLI1(com/ibm/ims/base/AIB)
(com/ibm/ims/base/JavaToDLI.execute)
(com/ibm/ims/base/JavaToDLI.terminateODBA)
(com/ibm/connector2/ims/db/IMSJdbcCustomService.shutdown)
(com/ibm/ws390/rmi/corba/CustomServices.shutdownCustomServices)
(com/ibm/ws390/rmi/corba/ORBEJSBridge.pre_deregister_Term)
INVOKDMY
EXECJAVA
(com/ibm/ws390/rmi/corba/ORBEJSBridge.pre_deregister_Term)
xeRunJniMethod
jni_CallStaticVoidMethodA
ORBEJSBridge::pre_deregister_Term()
SMO_Impl::Stop()
SR_WorkThread::RemoveAndProcessWork(ThreadCleanUp*)
SR_WorkRoutine
.
The shutdownCustomServices is being called on a TCB other than
the thread installCustomService was called on as required by
the IMS JDBC driver.  This causes the J2EE application server
to hang after the stop command is issued and no work is left
running in the application server region.
Local fix
Manually cancel the J2EE application server that failed to
end when the stop command was issued.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: J2ee application server hangs when a    *
*                      STOP is issued on a server where an     *
*                      application that uses the IMS JDBC      *
*                      connector is installed.                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the stop command is issued to a WebSphere J2EE application
server that contains an application which uses the IMS JDBC
Connector, the application server does not terminate and
must be cancelled.  The application server also will not respond
to being recycled from the SM EUI.

A server region processing the STOP request took an
ABENDS052/ABEND052 RC=08 when driving shutdown() on the
CustomService related to the IMS JDBC Connector.  This abend
indicates that a detach was attempted from a task other than the
mother task. The CustomService was attempting to detach a task
that it attached during its "initialize(...)" invocation.  The
"initialize" was driven from the Server Region main thread
(a Job Step task). The STOP processing is driven from an ACRW
thread (a daughter task).

The ABENDS052 caused the Server Region to skip a notification
call to the Control Region (Stop Phase 1 complete notification).
The Control Region will not progress beyond the first phase
of STOP.
Problem conclusion
Code has been modified in the Server Region to drive the
CustomService.shutdown from the Server Region Main task (Job
Step task).  Also, the notification from the Server Region of
the completion of STOP phase 1 is not dependent on the
successful shutdown of CustomServices.

APAR PQ71903 is associated with SERVICE LEVEL W401503 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ71903
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-03-10
Closed date 2003-04-07
Last modified date 2003-05-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ75776    UP03/04/15 P F304

  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


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ71903
IBM Group: Software Group
Modified date: May 3, 2003