PQ86088: STOP SERVER FAILS WITH JAVAX.JMS.ILLEGALSTATEEXCEPTION

APAR status
Closed as program error.

Error description
Stopping an Application Server hangs. The following errors are
seen in the systemout.log
 -
DRSW0002W: Connection to current host:port WebSphere internal
replication connect point lost.  The internal replication
service will attempt to connect to other host:port combinations
specified in the configuration
 -
DRSW0008E: Exception is: javax.jms.IllegalStateException:
  {-1924738140|}
at com.ibm.disthub.impl.jms.TopicPublisherImpl.publish
                    (TopicPublisherImpl.java:366)
at com.ibm.ws.drs.DRSJMS.jmsAckGet(DRSJMS.java:794)
at com.ibm.ws.drs.DRSCacheApp.jmsAckGet(DRSCacheApp.java:2757)
at com.ibm.ws.webcontainer.httpsession.DRSHttpSessCache.getEntry
         (DRSHttpSessCache.java:560)
at com.ibm.ws.drs.DRSJMS.onMessage(DRSJMS.java:966)
at com.ibm.ws.drs.DRSCacheApp.onMessage(DRSCacheApp.java:2143)
at com.ibm.disthub.impl.jms.MessageConsumerImpl.dispatch
    (MessageConsumerImpl.java:643)
at com.ibm.disthub.impl.jms.MessageImpl.dispatch
     (MessageImpl.java:306)
at com.ibm.disthub.impl.jms.SessionDispatcher.run
             (SessionDispatcher.java:166)
at java.lang.Thread.run(Thread.java:479)
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of the Websphere Application       *
*                 Server using HTTPSession Memory to memory    *
*                 replication and the Dynamic Cache.           *
****************************************************************
* PROBLEM DESCRIPTION: Application Server stop hangs with      *
*                      IllegalStateExceptions in the logs.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
While attempting to stop the Application server, it is observed
that the stop task does not return. The stop process is seen
to hang around without ever completing. Analysis of the traces
or logs at this point will show IllegalStateExceptions in the
Data Replication component.
Problem conclusion
The exceptions seen in the logs are caused by timing conditions
that occur due to incorrect order in which resources are shut
down. The fix for this problem has been included in a
cumulative fix that has been released for the Data Replication
component for 5.0.1 (WAS_DRS_03-16-2004_5.0.1_cumulative_Fix).
Temporary fix Comments
APAR information
APAR number PQ86088
Reported component name WAS NETWRK DEPL
Reported component ID 5630A3601
Reported release 00S
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-03-15
Closed date 2004-04-22
Last modified date 2004-04-22

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
drs          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00S
Software edition:
Reference #: PQ86088
IBM Group: Software Group
Modified date: Apr 22, 2004