You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2011/08/21 17:48:27 UTC
[jira] [Resolved] (QPID-3307) ClassNotfound Exception when using
Qpid java client in Complex classloading Environments.
[ https://issues.apache.org/jira/browse/QPID-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPID-3307.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.13
> ClassNotfound Exception when using Qpid java client in Complex classloading Environments.
> -------------------------------------------------------------------------------------------
>
> Key: QPID-3307
> URL: https://issues.apache.org/jira/browse/QPID-3307
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Charith Dhanushka Wickramarachchi
> Assignee: Robbie Gemmell
> Priority: Critical
> Fix For: 0.13
>
> Attachments: QPID-3307_patch.txt, QPID-3307_patch.txt, QPID-3307_patch.txt, QPID-3307_patch_unit_test.txt
>
>
> Hi ,
> When we are using qpid client to receive JMSObject in complex class loading environments like web application containers/Osgi environments .There is a scenario where this issues comes.
> Scenario.
> In a web application container normally they use a class loader per web app. and if we have qpid client libs at the root classloader level this error can come. The reason for this is Serializable Object types that are used inside the web app are not visible to the class loader that loads the JMSObject message and unmarshall it.
> thanks,
> Charith
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org