[jboss-jira] [JBoss JIRA] Assigned: (JBAS-7849) Determine long run strategy for shared access to JGroups channel by elements of the same service

Tue Apr 13 00:00:06 EDT 2010

     [ https://jira.jboss.org/jira/browse/JBAS-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry reassigned JBAS-7849:
--------------------------------------

    Assignee: Paul Ferraro  (was: Brian Stansberry)

Paul, assigning to you as you're working this in JGroups.

> Determine long run strategy for shared access to JGroups channel by elements of the same service
> ------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-7849
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7849
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>            Assignee: Paul Ferraro
>             Fix For: JBossAS-6.0.0.M4
>
>
> Example: JBAS-7844 requires group RPCs by session manager for session ownership; session manager also uses Infinispan for caching.
> Hibernate 2LC cache eviction also needs this for a proper solution to implement it's non-transaction evictAll() SPI method and any solution at all to evict(Object key).
> Temporarily this can be hacked by using Infinispan's RPCManager and using a custom CacheManager that places a custom InboundInvocationHandler in the globalComponentRegistry. But we need a long term solution that doesn't hack Infinispan and preferably is transparent to Infinispan.
> The ultimate solution could live in JGroups or in a JBCLUSTER project. Some project that's lightweight and consumable without extraneous dependencies by 1) AS 2) EJB3 standalone 3) Hibernate (2LC provider).
> The solution needs to account for the Hibernate use case; i.e. can't just be AS-specific.

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