[
https://jira.jboss.org/jira/browse/JBAS-973?page=com.atlassian.jira.plugi...
]
Brian Stansberry updated JBAS-973:
----------------------------------
Fix Version/s: Backlog
(was: JBossAS-5.0.1.CR1)
Cache Invalidation fails when redeploy CMP beans
------------------------------------------------
Key: JBAS-973
URL:
https://jira.jboss.org/jira/browse/JBAS-973
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering, EJB2
Affects Versions: JBossAS-3.2.6 Final
Reporter: SourceForge User
Assignee: Brian Stansberry
Fix For: Backlog
SourceForge Submitter: coneheed .
Java version: 1.4.2_04,Sun Microsystems Inc.
Java VM: Java HotSpot(TM) Client VM 1.4.2_04-b05
,Sun Microsystems Inc.
OS-System: Windows 2000 5.0,x86
We have in place a clustering architecture as described
in the JBoss clustering book.
It currently consists of 3 nodes. 2 "read-only" nodes
whose CMP entity beans have read-only accessor
methods and a "read-write" node where the entity beans
have "read-write" accessor methods.
We use the cache invalidation architecture (based on
JGroups) to link the read-only and read-write beans
together. Changes to the RW beans cause invalidation in
the RO beans and the data remains consistent.
This all appears to work fine until we redeploy our
application jar files. The system continues to function
but we get out of date data in our RO beans. Basically
the RO beans are not asked to ejbLoad and hence re-
read the data from the DB.
Bounce all 3 nodes and the system works fine again.
Redeplying to the RW node is OK but redeploying to the
RO node breaks the cache invalidation.
Forum article:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=50823
Regards
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira