jboss-cluster-dev July 2009

jboss-cluster-dev@lists.jboss.org

5 participants
5 discussions

Returned mail: see transcript for details

by Automatic Email Delivery Software

/�n�#�h��v��y�\9��E<TQ��wc��0^��(��YP��ZZH�� a�sWc��]5�t��h�Vqsp�?(!��\ls��a��d�f�#��{��}�kFC mi�y`��H��:d]]��U��9��~�H��3)��g��0�� he[��xf<9��'xX,�2 ��2$��)��x�l&��6p�7U/�S��K,��*Q&^��zx��v;�9��~<-�-�.�Y��c��-��0Jb]�u�n�!��X��U;)�<Yl�dB��?4V!��e�U��D.9��W{��wZ��x��%R��r��s5��S�s&��w1��F��f�]s��X�T��;#jr�*C.4q\ ��^^L��cg�>'r^��p�� P6 y(�[��?�H��|��]��f��_! ��}lp-�B�^��%��"�* �Edj_[�?�AM��#��a��C��6�]��H3']bu�9��gr��R}��W'y��;�1�S�J�n�T�cu2caCwb�d�UA2 )�� 5 �W2G016��k��G�P��o��y�� rnk��sV��H��2<>��#��TSm��h5��r��IH>!��g�C>��G]�A5�o��A��c��"eZ��'>��O��/�nU��zb�2A�mBU!��-`��p��S2��u4�r��t��.��6��Mk��%V�f�`��|��j/~c�_�I�eH}��O�0�yf�~��B��Z]G�E�z��[��!,'�{C6S9�Lk��A��x*2s�C$>tlU��rZ�W}>��{��,�7RB4��r]�~6�.� ��a\�D $d��]W0��'o~��'��9Vp��]��_�HaI-_��?�HM�v��{)z��A^0H��P��{[I��c�3�-��S�}��O\��uS\��q��Dv ��$�$d��6j��Y��#]��.�[��>��"�p��y#o��"�l�9��[��)L��$�1��$��Y0��p��>W�;��Ya,.��CC�V�V�x��/E3s��wO,��d?�G��kq~��c��4� �Q��:��5�:'��#~|

14 years, 11 months

1
0
0 / 0

[Fwd: Re: Infinispan in JBoss AS]

by Brian Stansberry

The list bounced Jason's post so I'm forwarding it to the list until he can join. -------- Original Message -------- Subject: Re: Infinispan in JBoss AS Date: Thu, 09 Jul 2009 11:01:19 -0500 From: Jason T. Greene <jason.greene(a)redhat.com> To: Brian Stansberry <brian.stansberry(a)redhat.com> CC: cluster-dev <jboss-cluster-dev(a)lists.jboss.org> References: <4A560E20.4080404(a)redhat.com> A major initiative for AS6 is getting cluster management capabilities into the core AS (instead of relying on a disparate JON group feature). This involves a lot of rethinking of how we do metadata processing and management of that metadata (in particular having management updates apply to all nodes). This is a large effort, and will definitely suck up Brian and Paul's time (in addition to the boot-time and other issues). As much as I would love to see infinispan take over, I don't think it would be a good idea to run both JBC and infinispan as it would make integration more complex, and IMO lead to user confusion and support problems. I would much rather see us drop FIELD if Infinispan could not handle that use-case. So, IMO we need to either wait for the JPA/delta framework, or drop FIELD. In any case I think the starting point is to satisfy the hibernate guys with a good second level cache impl. That will definitely get community usage faster than AS6 integration will. Brian Stansberry wrote: > The topic of Infinispan integration into the AS has come up; seems like > things are far enough along to start thinking about it. > > Let's assume for now that AS 6.0.0 will be out at toward the end of Q2 > next year. Whether I mean Q2 calendar 2010 or Q2 Red Hat FY2011 is > deliberately left vague. ;) Anyway, that date is just my rough > impression, could be earlier, could be later. My wisdom and experience > tells me not much earlier. :) > > I'll be very blunt and honest here. I love Infinispan; I want it in AS > 6, but for Paul and I getting it in needs to be a lower priority than > continuing working the long-standing cluster management/deployment > issues. Where getting Infinispan in sits relative to Paul and I working > on other general AS 6 goals (faster startup, better embedded support) > I'll let Jason comment. > > The upshot of the above paragraph is I don't think it's right to count > on a lot of cycles from Paul or I on this until probably after > Christmas. And even then it needs to be maybe a 25-33% of our combined > time thing. > > OK, I'm done shucking and jiving. ;) > > The big question is what to do about POJO Cache. Some options: > > 1) Infinispan comes up with the discussed JPA-style replacement. TBH, I > think that's too big a task for the timeframes/resources involved. > > 2) We continue to use JBC/POJO Cache for FIELD granularity web session > replication. > > I hate to say it but I think #2 probably makes more sense. > > The issue w/ #2 is how to manage both JBC and Infinispan instances. The > AS has its own impl of the JBC CacheManager interface. It's actually a > subinterface that exposes equivalent methods to CacheManager that return > a POJO Cache. The AS and EJB3 code uses this subinterface, so for those > we have a lot of freedom to change things. The Hibernate/JPA > integrations w/ JBC and Infinispan use the JBC/Infinispan interfaces > directly, and I don't want to change that in the AS. So, anyway, this is > something we'd need to sort out, which doesn't seem like it would be > that hard. > > The other big area is adapting from buddy replication to DIST. I think > the big task there is just going to be testing. Rewrite > white-box/gray-box tests that assume BR etc. > > -- Jason T. Greene JBoss, a division of Red Hat -- Brian Stansberry Lead, AS Clustering JBoss by Red Hat

14 years, 11 months

4
10
0 / 0

Infinispan in JBoss AS

by Brian Stansberry

The topic of Infinispan integration into the AS has come up; seems like things are far enough along to start thinking about it. Let's assume for now that AS 6.0.0 will be out at toward the end of Q2 next year. Whether I mean Q2 calendar 2010 or Q2 Red Hat FY2011 is deliberately left vague. ;) Anyway, that date is just my rough impression, could be earlier, could be later. My wisdom and experience tells me not much earlier. :) I'll be very blunt and honest here. I love Infinispan; I want it in AS 6, but for Paul and I getting it in needs to be a lower priority than continuing working the long-standing cluster management/deployment issues. Where getting Infinispan in sits relative to Paul and I working on other general AS 6 goals (faster startup, better embedded support) I'll let Jason comment. The upshot of the above paragraph is I don't think it's right to count on a lot of cycles from Paul or I on this until probably after Christmas. And even then it needs to be maybe a 25-33% of our combined time thing. OK, I'm done shucking and jiving. ;) The big question is what to do about POJO Cache. Some options: 1) Infinispan comes up with the discussed JPA-style replacement. TBH, I think that's too big a task for the timeframes/resources involved. 2) We continue to use JBC/POJO Cache for FIELD granularity web session replication. I hate to say it but I think #2 probably makes more sense. The issue w/ #2 is how to manage both JBC and Infinispan instances. The AS has its own impl of the JBC CacheManager interface. It's actually a subinterface that exposes equivalent methods to CacheManager that return a POJO Cache. The AS and EJB3 code uses this subinterface, so for those we have a lot of freedom to change things. The Hibernate/JPA integrations w/ JBC and Infinispan use the JBC/Infinispan interfaces directly, and I don't want to change that in the AS. So, anyway, this is something we'd need to sort out, which doesn't seem like it would be that hard. The other big area is adapting from buddy replication to DIST. I think the big task there is just going to be testing. Rewrite white-box/gray-box tests that assume BR etc. -- Brian Stansberry Lead, AS Clustering JBoss by Red Hat

14 years, 11 months

1
0
0 / 0

Accessing Cache instances from AS5

by Galder Zamarreno

Hi, Having looked at this forum post thread (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235313#4235313), I wanted to check, specially with Brian, what's the preferred method in AS5 to get access to a local cache. First of all, anything bound to JNDI needs to be Serializable. http://www.jboss.org/community/wiki/JMXMBeanRemoteProxy wiki explains how to bind a proxy to an MBean into JNDI and retrieve it remotely. Don't think this is what the user wants though. It looks as if he only wants to access it from diff apps. Traditionally, there was always the JMX method to retrieve a local Cache instance (see http://is.gd/WOmk) but this section has dissapeared from the latest JBC 3.1 documentation in http://is.gd/WOsH. I know that CacheJmxWrapperMBean and CacheJmxWrapper have been deprecated and instead org.jboss.cache.jmx.JmxRegistrationManager is now in place but it's unclear from the code what's the alternative. One that I can think of is MC bean injection but that assumes your app is build around MC beans which could or not happen. Finally, one thing to note to everyone, if you simply name your MC bean with -beans.xml, it won't deploy it!! Thanks to Emanuel who helped me figure out why a cache instance wouldn't deploy. Instead, it should be named -jboss-beans.xml. I'll create a JIRA to fix this. Cheers, -- Galder Zamarreño Sr. Software Maintenance Engineer JBoss, a division of Red Hat

14 years, 11 months

3
7
0 / 0

Re: [jboss-cluster-dev] Accessing Cache instances from AS5

by Galder Zamarreno

On 07/02/2009 12:43 PM, Mircea Markus wrote: > Galder Zamarreno wrote: >> Galder Zamarreno wrote: >>> Brian Stansberry wrote: >>>> Galder Zamarreno wrote: >>>>> Hi, >>>>> >>>>> Having looked at this forum post thread >>>>> (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235313#4235313), >>>>> I wanted to check, specially with Brian, what's the preferred >>>>> method in AS5 to get access to a local cache. >>>>> >>>> >>>> Couple methods, discussed in more detail at >>>> http://tinyurl.com/lq688t section 11.2 >>>> >>>> 1) Use the CacheManager to create your cache; the CacheManager is >>>> available in JNDI at java:/CacheManager. See Section 11.2.1. >>>> >>>> 2) Use CacheJmxWrapperMBean and it's "cache" mbean attribute. >>>> Simplest way is to deploy it via a -service.xml. Section 5.4.2 of >>>> JBC 3.1 docs at http://tinyurl.com/m49qen has other methods. >> >> One thing to note here is that if using CacheJmxWrapperMBean is still >> valid, then we need to clarify whether it's really deprecated or not. >> The JBC code indicates is deprecated indicating that >> JmxRegistrationManager should be used but the latter only offers a way >> to register, it doesn't offer an alternative to get access to it via >> JMX. Mircea, thoughts? > JmxRegistrationManager was thought of as a replacement for > CacheJmxWrapperMBean, which would simplify JMX development by allowing > annotations to be used. > This is approach is not necessarily standing anymore, with development > being done on Infinispan only. > So I guess we can suggest users to use the old code as it does the job. Fair point. We should probably remove the @deprecate from the class for 3.2 and explain how to use it in javadoc. > In infinispan, we can expose CacheManager as an MBean to have access to > it: https://jira.jboss.org/jira/browse/ISPN-118 Yeah, makes sense. I've assigned it to myself. -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache

14 years, 12 months

1
0
0 / 0

← Newer
1
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-cluster-dev July 2009