[
https://issues.apache.org/jira/browse/OPENJPA-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-520:
------------------------------------
Summary: JMSRemoteCommitProvider throws ClassNotFoundExceptions on update
in some configurations (was: JMSRemoteCommitProvider not working for data
cache update)
> 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
> Attachments: MyEarTest.ear, ReproduceReadme.txt
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
