geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevan Miller <kevan.mil...@gmail.com>
Subject Re: tomcat6 and wadi-clustering configuration classloader clashes
Date Thu, 03 Jul 2008 14:19:33 GMT

On Jul 3, 2008, at 5:10 AM, Gianny Damour wrote:

> Hello,
>
> I am back from holiday; A quick scan of the mailing lists tells me  
> that the upgrade to WADI 2.0 is causing classloader clashes.
>
> As identified by Jason W. and Kevan, a Tribes class is loaded by two  
> distinct classloaders (tomcat6 and wadi-clustering configuration  
> classloaders), which causes CCE upon message delivery. After having  
> investigated this problem, it seems to me that the best way to fix  
> it is to split the tomcat6 dependencies into two configurations:  
> tomcat6 and tomcat6-tribes. tomcat6-tribes imports the tomcat6  
> configuration and the tribes dependency. The new tomcat6  
> configuration is the current tomcat6 configuration minus the tribes  
> dependency. Such a change will break all the configurations defining  
> Tribes clustering GBeans. Users having such configurations will have  
> to redeploy them after having added the tromcat6-tribes configuration.
>
> I tried a backward compatible approach where the tribes dependency  
> was pushed up to a parent configuration. Unfortunately, this change  
> can only work if WADI dependencies are also imported by this new  
> configuration, which is a less ideal approach than the above one.

Can you explain this? Not sure I understand why that's the case.  
Creating a new configuration seems to be the more correct solution.  
So, not sure that it really matters...

> If no one objects, I intend to check-in this change over the week-end.

No objections from me.

--kevan

Mime
View raw message