APAR status
Closed as program error.
Error description
The specifics on the test and failure scenario is as follows
After creating two server clusters, and configuring one for
applications
which used a replication domain that the other server
cluster served as the replication servers for.
I then walked through two test cases
1) I failed one of the application servers, failover worked
correctly
as well as recovery upon restart of the server,
2) I failed the "primary" replicator server , the one defined
as the
replicator to both app servers, the session manager did not
switch
to the other backup replicator server in the repication sever
cluster
(for the domain), which is the expected behavior.
started both clusters and invoked application
Server Name = drsappserver2
Count: 1 (from new session)
Session ID = NK3eonZVZst8x2t-WQC0QW7
Session ID from getHeader JSESSIONID=0001ZF4B4FT5
4iIiplnYqngY-fU:vau911ie
stopped drsappserver2 (failover occurs correctly)
Server Name = drsappserver1
Count: 2 (from existing session)
Session ID = NK3eonZVZst8x2t-WQC0QW7
Session ID from getHeader JSESSIONID=0001NK3eonZVZst8x2t-
WQC0QW7:vau911ie
stopped drsrepserver1 (the primary replicator), started
drsappserver2, stopped drsappserver1
failover does not occur, new session object is created. Attached
are the logs from both clusters (names should be self
explantory) with the trace spec " com.ibm.ws.drs.*=all=enabled:
com.ibm.ws.webcontainer.httpsession.*=all=enabled" set.
Local fix
no work around
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server *
* using HTTP Session memory-to-memory *
* replication or Dynamic Cache, with a *
* replicator configured on a different machine *
****************************************************************
* PROBLEM DESCRIPTION: Http Session Memory-to-memory or *
* Dynamic Cache do not connect to *
* replicator at server-start time. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Http Session Memory-to-memory or Dynamic Cache do not connect
to replicator at server-start time.
Problem conclusion
Code has been changed so that http Session Memory-to-memory or
Dynamic Cache connect to replicator at server-start time.
The fix for this problem is expected to be made available for
the 5.0.2 release in 'WebSphere Application Server 5.0.2
Cumulative Fix 5'. It is expected to be made available for the
5.1.0 release in 'WebSphere Application Server 5.1.0
Cumulative Fix 2'.
Temporary fix Comments
APAR information |
APAR number |
PQ85234 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-02-26 |
Closed date |
2004-03-02 |
Last modified date |
2004-03-02 |
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 |
R00A PSY |
UP |
R00W PSY |
UP |
|