Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 325363 - jms cache coordination config broken
Summary: jms cache coordination config broken
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: James Sutherland CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-15 11:09 EDT by James Sutherland CLA
Modified: 2022-06-09 10:03 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James Sutherland CLA 2010-09-15 11:09:23 EDT 
In the 2.1 release a bug was added in processing the JMS cache coordination persistence.xml properties that will cause a null-pointer exception.

A workaround is to use a SessionCustomizer or set,
"eclipselink.cache.coordination.jms.reuse-topic-publisher"="false"

I will fix in trunk, but should probably be back ported.

Also our tests do not hit this error because they are using a customizer instead of using the normal JPA config.  They should be using the persistence.xml to configure it.

Also noticed we have no testing for the new publisher JMS option.  There should be.
Comment 1 Tom Ware CLA 2010-09-22 16:04:42 EDT 
targetting for 2.1.2 as suggested below
Comment 2 James Sutherland CLA 2010-09-27 15:33:20 EDT 
Fixed in trunk
Comment 3 James Sutherland CLA 2010-09-28 11:35:11 EDT 
Fixed in trunk(2.2) and 2.1
Comment 4 Eclipse Webmaster CLA 2022-06-09 10:03:32 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink