[
https://issues.apache.org/jira/browse/OPENJPA-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-520.
-------------------------------------
Resolution: Fixed
Already fixed in an earlier release: JMSRemoteCommitProvider uses the
application class loader saved at configuration time when it reads events
(777818d28). Closing.
> JMSRemoteCommitProvider throws ClassNotFoundExceptions on update in some
> configurations
> ---------------------------------------------------------------------------------------
>
> Key: OPENJPA-520
> URL: https://issues.apache.org/jira/browse/OPENJPA-520
> Project: OpenJPA
> Issue Type: Bug
> Components: datacache
> Affects Versions: 0.9.7, 1.0.0, 1.0.1, 1.0.2
> Environment: Weblogic Server 10.0 cluster
> JPA using Kodo cache enabled and JMS RemoteCommitProvider
> Reporter: Xiaoqin Feng
> Priority: Major
> Attachments: MyEarTest.ear, ReproduceReadme.txt,
> openjpa-520-v2.patch, openjpa-520.patch
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Customer is using WLS10.0/JPA cluster with 2 nodes. Customer has Kodo data
> cache enabled and set up JMS remote commitment. Customer is encountering
> ClassNotFound Exceptions when objects are trying to be deserialized from the
> JMS topic. Object notifications are correctly sent to the JMS topic but the
> application throws an exception when trying to retrieve the notifications
> from the JMS topic.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
