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

[Jason T. Greene (JIRA)]

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

Jason T. Greene updated JBAS-7849:
----------------------------------

    Fix Version/s: TBD-6.x
                       (was: 6.0.0.M4)


All uncompleted issues are now moved to the new "To be determined for future 6.x releases" category. Feel free to reassign this to a specific release, but only if you have the time to do it

> Determine long run strategy for shared access to JGroups channel by elements of the same service
> ------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-7849
>                 URL: https://jira.jboss.org/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: TBD-6.x
>
>
> 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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira