[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-877) TreeCache usage should not depend on trove.jar

[obalbous (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBCACHE-877?page=comments#action_12353351 ] 
            
obalbous commented on JBCACHE-877:
----------------------------------

FYI we just have this issue using JBC 1.4.1 GA on JBoss 3.2.6 using TreeCache with mode INVALIDATION_ASYNC.
The only appears when 2 Servers are up : the object put in the cache does contain a reference to a List - this is probably the cause of the problem 
(Marshalling requiring the trove.jar)

By the way, I'm surprised this happens, because the invalidation mode we're using should not require the whole object to be broadcasted but only an invalidation message.

> TreeCache usage should not depend on trove.jar
> ----------------------------------------------
>
>                 Key: JBCACHE-877
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-877
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0.SP1
>            Reporter: Galder Zamarreno
>         Assigned To: Ben Wang
>            Priority: Minor
>
> A customer is upgrading from JBC 1.1 to 1.4.0.SP1 and 
> even though it only uses plain TreeCache, it gets a 
> NoClassDefFoundError for trove classes.
> 2006-11-23 13:19:03,781  ERROR RpcDispatcher exception=java.lang.NoClassDefFoundError: gnu/trove/TObjectHashingStrategy
> This is a TreeCacheAop/PojoCache dependency and therefore,
> should be isolated and attempted to be loaded only when 
> PojoCache used.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira