APAR status
Closed as program error.
Error description
[6/25/04 11:32:57:888 EDT] 3d2b3 DRSResetJMS A DRSW0005I:
WebSphere internal replication has recovered from a previous
connection
failure.
[6/25/04 11:32:58:038 EDT] 3d2b3 DRSCacheApp E DRSW0001E: A
error
occured communicating over WebSphere internal replication. The
exception is: com.ibm.disthub.impl.jms.JMSWrappedException:
{800870265|java.io.IOException: Broken pipe|}
at
com.ibm.disthub.impl.jms.TopicPublisherImpl.publishInternal
(TopicPublisherImpl.java:511)
at com.ibm.disthub.impl.jms.TopicPublisherImpl.publish
(TopicPublisherImpl.java:450)
at com.ibm.disthub.impl.jms.TopicPublisherImpl.publish
(TopicPublisherImpl.java:375)
at com.ibm.ws.drs.DRSJMS.jmsPubUpd(DRSJMS.java:200)
at
com.ibm.ws.drs.DRSCacheApp.jmsPubUpd(DRSCacheApp.java:3290)
at com.ibm.ws.drs.DRSJMS.jmsPubUpd(DRSJMS.java:272)
at
com.ibm.ws.drs.DRSCacheApp.jmsPubUpd(DRSCacheApp.java:3290)
at
com.ibm.ws.drs.DRSAPI.updateEntryProp(DRSAPI.java:803)
at
com.ibm.ws.drs.DRSCacheApp.updateEntryProp(DRSCacheApp.java:
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of Websphere Application server *
* using HTTP session memory-to-memory *
* replication and Dynamic cache replication. *
****************************************************************
* PROBLEM DESCRIPTION: Users of the replication service who *
* attempt to replicate objects larger *
* than 2MB in size see broken pipe *
* exceptions and frequent resets. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The replication service has a default value of 2MB for its
maximum message size that it can transmit over the wire. If
the consumer service ( Http session memory to memory
replication or Websphere Dynamic cache service) attempt to
send messages that are larger in size than this value, the
replicator that is instructed to send this message disconnects
the client connection to the replication service on this
server thereby causing broken pipe exceptions. These
exceptions either happen immediately or on subsequent message
sends. These exceptions then cause a reset to happen wherein
the replication service instance resets its connectivity to
the current replicator and attempts to connect to an
alternate replicator in the domain. Thus, this problem
may also manifest itself in the form of frequent reset
attempts in the logs.
Problem conclusion
This fix increases the default maximum message size of 5MB.
This should alleviate the problem somewhat. Websphere best
practices do not recommend storing more than 3 to 4 MB of data
in a session. This fix is targeted for inclusion in 5.0.2.7 and
5.1.0.6.
Temporary fix Comments
APAR information |
APAR number |
PQ91090 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-07-07 |
Closed date |
2004-07-19 |
Last modified date |
2004-07-19 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
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 |
|