APAR status
Closed as program error.
Error description
Created cluster with appsvr1 and appsvr2 on machine1 and
machine2
Problem Description:
Created cluster with appsvr1 and appsvr2 on machine1 and
machine2
Enabled Dynamic Cache Service on application server appsvr1 and
appsvr2
Enabled servlet caching on appsvr1 and appsvr2
Created replication domain with 2 replicators
Configured replicators into cache replication one on each
machine
Deployed struts application to cluster
Configured cachespec.xml in application WEB-INF directory on
both
machine1 and machine2
Had cache monitor on both
Called application using host:port/application on one machine
Viewed contents of cache on machine1/appsvr1 using cache monitor
(see
cache1.jpg)
Contents cached according to cachespec.xml
- /blank.do
- /filter/open.do
- note template only described for /blank.do
Viewed contents of cache on machine2/appsvr2 using cache monitor
(see
cache2.jpg)
- only those items with templates replicated ie /blank.do
Other points
Replication timing set at 5 seconds
The application has two action inside one another, only the
inner seems
to have a template and be replicated. See:
/wiw.do as the first action - not required to be cached
/filter/open.do as the second action - required to be cached
/blank.do as the third action, starts and finished within second
action
(/filter/open.do) - required to be cached
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Dynamic cache users on WebSphere *
* Application Server 5.0.2.6 *
****************************************************************
* PROBLEM DESCRIPTION: Struts Application does not replicate *
* dynamic cache content *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Problem is due to the struts application setting
non-serialzable request attributes on an entry
marked "shared-push".
Problem conclusion
The fix for this problem is to log a message and store the
content in local cache. There is no way to
replicate entries containing non-serializable
attributes. The user should mark the entry as not-shared
in this case. Another option is to leave the entry
shared-push and mark the entry with
<property name="save-attributes ">false</property>.
This will allow the entry to be pushed to the remote
machine but, depending on the application, this may or
may not work because attributes will not be saved with
the cached entry.
Temporary fix Comments
APAR information |
APAR number |
PQ91455 |
Reported component name |
WAS ENTERPRISE |
Reported component ID |
5630A3700 |
Reported release |
00S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-07-15 |
Closed date |
2004-10-12 |
Last modified date |
2004-11-03 |
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 |
R00S PSY |
UP |
R00W PSY |
UP |
|