Bug 262740 - Need to add Cache Coordination tests using JMS and RMI for WebLogic
Summary: Need to add Cache Coordination tests using JMS and RMI for WebLogic
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: All Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords: test
Depends on:
Blocks:
 
Reported: 2009-01-28 07:46 EST by Praba Vijayaratnam CLA
Modified: 2022-06-09 10:26 EDT (History)
6 users (show)

See Also:


Attachments
JPA Cachecoordination tests for WebLogic (57.25 KB, patch)
2009-01-29 06:11 EST, Praba Vijayaratnam CLA
no flags Details | Diff
updated patch for cachecoordination test implementation (53.43 KB, patch)
2009-02-04 09:46 EST, Praba Vijayaratnam CLA
no flags Details | Diff
attachment patch created off the 'trunk' directory (54.24 KB, patch)
2009-02-05 06:05 EST, Praba Vijayaratnam CLA
no flags Details | Diff
combined rmi and jms configuration in single customizer class (51.94 KB, patch)
2009-02-09 09:22 EST, Praba Vijayaratnam CLA
peter.krogh: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Praba Vijayaratnam CLA 2009-01-28 07:46:42 EST
We need to have JPA cache coordination tests utilizing protocols such as JMS and RMI on clustered WebLogic server environment.
Comment 1 Praba Vijayaratnam CLA 2009-01-29 06:11:03 EST
Created attachment 124136 [details]
JPA Cachecoordination tests for WebLogic

Following two targets added to eclipselink.jpa.test/build.xml:
    <target name="server-start-cachecoordination"/>
    <target name="server-run-test-cachecoordination"/>

JPA Sessionbean test model is used to test cachecoordination (using JMS or RMI) on preconfigured WebLogic (10.3) clustered environment. For JMS protocol, a JMS server configuration also required on WebLogic.
Tests involve CRUD operations, and changes to entities are verified from the cache update notification.
Comment 2 Praba Vijayaratnam CLA 2009-02-04 09:46:23 EST
Created attachment 124679 [details]
updated patch for cachecoordination test implementation

Reduced number of java files, removed hard-coded properties in java/xml files.
Also, made easier to switch between JMS and RMI configuration for testing.
Comment 3 Sebastien Tardif CLA 2009-02-04 11:38:01 EST
We know by experience that cache invalidation (to not confuse with propagation) was not tested in base TopLink 10.x. 

The kind of tests to have are:
- check that it's only invalidated, not refresh
- check that via UOW if children was invalidated but not the parent, when query via parent, the children will be refresh
- JMS implementation cannot span thread, it's not EJB compliant
Comment 4 Praba Vijayaratnam CLA 2009-02-05 06:05:36 EST
Created attachment 124791 [details]
attachment patch created off the 'trunk' directory
Comment 5 Praba Vijayaratnam CLA 2009-02-09 09:22:24 EST
Created attachment 125134 [details]
combined rmi and jms configuration in single customizer class

1) more properties moved to persistence_cachecoordination.xml
2) usage of single session customizer class implemented for both JMS and RMI
3) removed temporary java files that employed in previous patch
Comment 6 Yiping Zhao CLA 2009-02-20 14:09:13 EST
checked in Praba's pacth for this bug on Feb 9, 2009.
Comment 7 Peter Krogh CLA 2009-08-26 09:46:26 EDT
Mass update to change fixed in target.
Comment 8 Peter Krogh CLA 2009-08-26 09:48:47 EDT
Mass update to change fixed in target.
Comment 9 Peter Krogh CLA 2009-08-26 09:53:45 EDT
Mass update to change fixed in target.
Comment 10 Peter Krogh CLA 2009-08-26 09:56:07 EDT
Mass update to change fixed in target.
Comment 11 Eclipse Webmaster CLA 2022-06-09 10:26:36 EDT
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink