Re: [jbosscache-dev] Re: Integrating steaming transfer in JBC
by Manik Surtani
Well then this is the ideal time to do it, while the interfaces are
still malleable.
I suspect the quick and dirty impl for most cache loader impls will
be to wait till the stream closes to capture the byte[] and process
this rather than a more efficient on-the-fly approach.
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
On 15 Aug 2006, at 17:16, Brian Stansberry wrote:
> Yep. The thread kind of morphed into a design discussion :)
>
> jbosscache-dev-bounces(a)lists.jboss.org wrote:
>> (This should be on the jbc dev mail list, btw - or on the
>> design forum if it warrants it)
>>
>> Vladimir/Brian:
>>
>> Does this relate to the need for something like:
>>
>> void storeEntireState(OutputStream s);
>> InputStream loadEntireState();
>> void storeState(OutputStream s, Fqn subtree); InputStream
>> loadState(Fqn subtree);
>>
>> In the CacheLoader interface?
>>
>> Firstly, is this feasible when it comes to cache loaders -
>> e.g., a JDBC cache loader - what sort of stream markers will
>> we have to let the cache loader know when it can start
>> chunking up data from the stream, parsing it and pushing this
>> state down to storage? Or will it just be an API-level
>> kludge where the CL impl attempts to keep reading from the
>> stream until the stream closes, yanks out a byte[] and passes
>> that into storeEntireState(byte[] b)? (May be the case for
>> an initial impl, just so we have the interface methods in place for
>> 2.0.0)
>>
>> Cheers,
>>
>>> I should have sent a copy to Manik and Bela as well. See below.
>>>
>>> Main point is: we need additional methods in CacheLoader to
>>> accommodate streaming state transfer.
>>> How should we proceed?
>>>
>>> Vladimir
>>>
>>> -----Original Message-----
>>> From: Vladimir Blagojevic
>>> Sent: Tuesday, August 15, 2006 11:41 AM
>>> To: Brian Stansberry
>>> Subject: RE: Integrating steaming transfer in JBC
>>>
>>> Oyyyy. Not only that but it also affects CacheLoader API:
>>>
>>> byte[] loadEntireState() throws Exception; void
>>> storeEntireState(byte[] state) throws Exception; byte[] loadState
>>> (Fqn
>>> subtree) throws Exception; void storeState(byte[] state, Fqn
>>> subtree) throws Exception;
>>>
>>> These should have streaming counterparts if we really want large
>>> state OOME to go away....
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Brian Stansberry
>>> Sent: Tuesday, August 15, 2006 11:27 AM
>>> To: Vladimir Blagojevic
>>> Subject: RE: Integrating steaming transfer in JBC
>>>
>>> Yep, plus there are different types of state that will be handled by
>>> different subsystems; that will be interesting for streaming state
>>> transfer.
>>>
>>> Also, for buddy replication, the state transfer is a push rather
>>> than
>>> a pull. Not sure what to do about that :(
>>>
>>> Vladimir Blagojevic wrote:
>>>> Ok I see. So it is not only integration of state transfer but
>>>> removing
>>>
>>>> rpc mechanism for partial state integration. I am looking at the
>>>> code and learning how is this done. Then I'll ping you tomorrow/
>>>> Thursday to
>>>
>>>> have a discussion with you.
>>>>
>>>> -----Original Message-----
>>>> From: Brian Stansberry
>>>> Sent: Monday, August 14, 2006 3:02 PM
>>>> To: Vladimir Blagojevic
>>>> Subject: RE: Integrating steaming transfer in JBC
>>>>
>>>> Just look at the JBCACHE issues and filter for the ones assigned to
>>>> you :)
>>>>
>>>> Vladimir Blagojevic wrote:
>>>>> Hey,
>>>>>
>>>>> What do you mean by looking at the non streaming state transfer
>>>>> tasks? Which ones are those?
>>>>>
>>>>> Vladimir
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: "Brian Stansberry" <brian.stansberry(a)jboss.com>
>>>>> Date: Mon, 14 Aug 2006 12:24:35
>>>>> To:<vladimirb(a)rogers.blackberry.net>
>>>>> Subject: RE: Integrating steaming transfer in JBC
>>>>>
>>>>> Sure, just let me know. But, I'd start with looking at the
>>>>> non-streaming state transfer tasks. That will get you familiar
>>>>> with the use cases and existing code.
>>>>>
>>
>> _______________________________________________
>> jbosscache-dev mailing list
>> jbosscache-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
>
>
>
> Brian Stansberry
> Lead, AS Clustering
> JBoss, a division of Red Hat
> Ph: 510-396-3864
> skype: bstansberry
19 years, 1 month
Re: Integrating steaming transfer in JBC
by Manik Surtani
(This should be on the jbc dev mail list, btw - or on the design
forum if it warrants it)
Vladimir/Brian:
Does this relate to the need for something like:
void storeEntireState(OutputStream s);
InputStream loadEntireState();
void storeState(OutputStream s, Fqn subtree);
InputStream loadState(Fqn subtree);
In the CacheLoader interface?
Firstly, is this feasible when it comes to cache loaders - e.g., a
JDBC cache loader - what sort of stream markers will we have to let
the cache loader know when it can start chunking up data from the
stream, parsing it and pushing this state down to storage? Or will
it just be an API-level kludge where the CL impl attempts to keep
reading from the stream until the stream closes, yanks out a byte[]
and passes that into storeEntireState(byte[] b)? (May be the case
for an initial impl, just so we have the interface methods in place
for 2.0.0)
Cheers,
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
On 15 Aug 2006, at 16:57, Vladimir Blagojevic wrote:
> I should have sent a copy to Manik and Bela as well. See below.
>
> Main point is: we need additional methods in CacheLoader to
> accommodate
> streaming state transfer.
> How should we proceed?
>
> Vladimir
>
> -----Original Message-----
> From: Vladimir Blagojevic
> Sent: Tuesday, August 15, 2006 11:41 AM
> To: Brian Stansberry
> Subject: RE: Integrating steaming transfer in JBC
>
> Oyyyy. Not only that but it also affects CacheLoader API:
>
> byte[] loadEntireState() throws Exception;
> void storeEntireState(byte[] state) throws Exception;
> byte[] loadState(Fqn subtree) throws Exception;
> void storeState(byte[] state, Fqn subtree) throws Exception;
>
> These should have streaming counterparts if we really want large state
> OOME to go away....
>
>
>
> -----Original Message-----
> From: Brian Stansberry
> Sent: Tuesday, August 15, 2006 11:27 AM
> To: Vladimir Blagojevic
> Subject: RE: Integrating steaming transfer in JBC
>
> Yep, plus there are different types of state that will be handled by
> different subsystems; that will be interesting for streaming state
> transfer.
>
> Also, for buddy replication, the state transfer is a push rather
> than a
> pull. Not sure what to do about that :(
>
> Vladimir Blagojevic wrote:
>> Ok I see. So it is not only integration of state transfer but
>> removing
>
>> rpc mechanism for partial state integration. I am looking at the code
>> and learning how is this done. Then I'll ping you tomorrow/
>> Thursday to
>
>> have a discussion with you.
>>
>> -----Original Message-----
>> From: Brian Stansberry
>> Sent: Monday, August 14, 2006 3:02 PM
>> To: Vladimir Blagojevic
>> Subject: RE: Integrating steaming transfer in JBC
>>
>> Just look at the JBCACHE issues and filter for the ones assigned to
>> you :)
>>
>> Vladimir Blagojevic wrote:
>>> Hey,
>>>
>>> What do you mean by looking at the non streaming state transfer
>>> tasks? Which ones are those?
>>>
>>> Vladimir
>>>
>>>
>>> -----Original Message-----
>>> From: "Brian Stansberry" <brian.stansberry(a)jboss.com>
>>> Date: Mon, 14 Aug 2006 12:24:35
>>> To:<vladimirb(a)rogers.blackberry.net>
>>> Subject: RE: Integrating steaming transfer in JBC
>>>
>>> Sure, just let me know. But, I'd start with looking at the
>>> non-streaming state transfer tasks. That will get you familiar with
>>> the use cases and existing code.
>>>
19 years, 1 month
RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
by Rajesh Rajasekaran
I guess the hostnames have been moved from dev02.pub.qa.atl.jboss.com to
dev02.qa.atl.jboss.com
dev02.qa.atl.jboss.com worked for me.
I m not sure where the clustering config picks up the hostname from. But
it picks up dev02.pub.qa.atl.jboss.com
I noticed the same when using VNC this morning. It was assigned the
title dev02.pub.qa.atl.jboss.com
-----Original Message-----
From: Ruel Loehr
Sent: Monday, August 14, 2006 1:13 PM
To: Ryan Campbell; Rajesh Rajasekaran; Brian Stansberry; 'Manik Surtani'
Cc: 'jbosscache-dev(a)lists.jboss.org'; QA; IT Ops Team
Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
I had that problem this morning. The hostnames no longer work for me.
We need to specify the IP address. See the etc/hosts/ file IT sent this
morning.
Ruel Loehr
JBoss QA
-----------------------------
512-342-7840 ext 2011
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel
-----Original Message-----
From: Ryan Campbell
Sent: Monday, August 14, 2006 1:04 PM
To: Rajesh Rajasekaran; Brian Stansberry; 'Manik Surtani'
Cc: 'jbosscache-dev(a)lists.jboss.org'; QA; IT Ops Team
Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
Rajesh,
Please make sure you can ping dev02.pub.qa.atl.jboss.com.
The hostname entry for this box may be invalid due to the VPN
transition.
-----Original Message-----
From: Rajesh Rajasekaran
Sent: Monday, August 14, 2006 11:02 AM
To: Brian Stansberry; 'Manik Surtani'
Cc: 'jbosscache-dev(a)lists.jboss.org'; QA
Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
Brian
I m unable to startup the servers for the clustering tests in Branch_4_0
irrespective of the version of JBossCache.
I get the following error on the server.
2006-08-14 13:55:39,904 WARN [org.jgroups.protocols.AUTOCONF] failed
creating DatagramSocket: java.net.UnknownHostException:
dev02.pub.qa.atl.jboss.com: dev02.pub.qa.atl.jboss.com
2006-08-14 13:55:39,906 ERROR [org.jgroups.protocols.UDP]
max_bundle_size (64000) is greater than largest UDP fragmentation size
(0)
2006-08-14 13:55:39,909 DEBUG [org.jboss.cache.aop.TreeCacheAop]
Initialization failed jboss.cache:service=TomcatClusteringCache
ChannelException: unable to setup the protocol stack
at org.jgroups.JChannel.<init>(JChannel.java:217)
at org.jgroups.JChannel.<init>(JChannel.java:189)
at org.jboss.cache.TreeCache._createService(TreeCache.java:1373)
at org.jboss.cache.TreeCache.createService(TreeCache.java:1300)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSup
port.java:260)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBean
Support.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2006-08-14 13:55:39,916 WARN [org.jboss.system.ServiceController]
Problem creating service jboss.cache:service=TomcatClusteringCache
ChannelException: unable to setup the protocol stack
at org.jgroups.JChannel.<init>(JChannel.java:217)
at org.jgroups.JChannel.<init>(JChannel.java:189)
at org.jboss.cache.TreeCache._createService(TreeCache.java:1373)
at org.jboss.cache.TreeCache.createService(TreeCache.java:1300)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSup
port.java:260)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBean
Support.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
-----Original Message-----
From: Brian Stansberry
Sent: Monday, August 14, 2006 11:55 AM
To: Manik Surtani; Rajesh Rajasekaran
Cc: jbosscache-dev(a)lists.jboss.org; QA
Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
Just Branch_4_0 is fine with me.
jbosscache-dev-bounces(a)lists.jboss.org wrote:
> If Brian's happy with just Branch_4_0 then I'm ok with it.
>
> We can regress with 4.0.4 and 4.0.3.Sp1 after release, for the compat
> matrix.
>
> Cheers,
>
>> Have verified the testsuite on jdk 1.5, 1.4 and on the packaged
>> binary. Tutorials and examples have also been verified.
>>
>> Have to check for any regression with Branch_4_0 (4.0.5.CR1)
>> 4.0.4.GA also required?
>>
>> -----Original Message-----
>> From: Manik Surtani [mailto:manik@jboss.org]
>> Sent: Monday, August 14, 2006 7:03 AM
>> To: QA; jbosscache-dev(a)lists.jboss.org
>> Subject: Re: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>
>> Sorry, meant to CC the mail list on this too.
>> --
>> Manik Surtani
>>
>> Lead, JBoss Cache
>> JBoss, a division of Red Hat
>>
>> Email: manik(a)jboss.org
>> Telephone: +44 7786 702 706
>> MSN: manik(a)surtani.org
>> Yahoo/AIM/Skype: maniksurtani
>>
>>
>> On 14 Aug 2006, at 13:02, Manik Surtani wrote:
>>
>>> How's this release looking now?
>>> --
>>> Manik Surtani
>>>
>>> Lead, JBoss Cache
>>> JBoss, a division of Red Hat
>>>
>>> Email: manik(a)jboss.org
>>> Telephone: +44 7786 702 706
>>> MSN: manik(a)surtani.org
>>> Yahoo/AIM/Skype: maniksurtani
>>>
>>>
>>> On 11 Aug 2006, at 21:07, Brian Stansberry wrote:
>>>
>>>> It was a trivial problem with a nested if (log.isDebugEnabled())
>>>> statement. I reran most of the failed tests (but just a
>>>> representative sample of the ones ino.j.c.aop.statetransfer and
>>>> o.j.c.statetransfer -- they duplicate the same thing, and the
>>>> failure mode was the same in all cases). All looks well.
>>>>
>>>> JBossCache_1_4_0_SP1 tag has been moved.
>>>>
>>>> Brian Stansberry
>>>> Lead, AS Clustering
>>>> JBoss, a division of Red Hat
>>>> Ph: 510-396-3864
>>>> skype: bstansberry
>>>>
>>>>> -----Original Message-----
>>>>> From: Rajesh Rajasekaran
>>>>> Sent: Friday, August 11, 2006 1:59 PM
>>>>> To: Manik Surtani; Brian Stansberry; Ben Wang
>>>>> Cc: QA
>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>
>>>>> I had all the statetransfer and interop tests failing.
>>>>> I ve attached the test results.
>>>>>
>>>>>
>>>>> Thanks
>>>>> Rajesh
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Rajesh Rajasekaran
>>>>>> Sent: Friday, August 11, 2006 12:03 PM
>>>>>> To: Brian Stansberry
>>>>>> Cc: Manik Surtani; Ryan Campbell
>>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>>
>>>>>> Yes. I have the testsuite results and I notice a few failures.
>>>>>> I ll verify the failures again and send out the list (after
>>>>>> lunch). Maybe you can move the tag once if any fixes are made
>>>>>> for those tests.
>>>>>>
>>>>>> Here's the jira to track the release.
>>>>>> http://jira.jboss.com/jira/browse/JBQA-432
>>>>>>
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Brian Stansberry
>>>>>> Sent: Friday, August 11, 2006 11:54 AM
>>>>>> To: Rajesh Rajasekaran
>>>>>> Cc: Manik Surtani
>>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>>
>>>>>> Hi Rajesh,
>>>>>>
>>>>>> Have you guys started on this? We had a conversation about
>>>>>> changing the logging level of 2 log statements, and I'd like to
>>>>>> move the tag for that.
>>>>>>
>>>>>> Brian Stansberry
>>>>>> Lead, AS Clustering
>>>>>> JBoss, a division of Red Hat
>>>>>> Ph: 510-396-3864
>>>>>> skype: bstansberry
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Rajesh Rajasekaran
>>>>>>> Sent: Thursday, August 10, 2006 11:11 AM
>>>>>>> To: Brian Stansberry; QA
>>>>>>> Cc: 'jbosscache-dev(a)lists.jboss.org'
>>>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>>>
>>>>>>> Yes. We could have this release out by tomorrow.
>>>>>>> Should the release be done with Sun jdk 1.5 or jrockit 1.5?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Brian Stansberry
>>>>>>> Sent: Thursday, August 10, 2006 11:08 AM
>>>>>>> To: QA
>>>>>>> Cc: jbosscache-dev(a)lists.jboss.org
>>>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>>>
>>>>>>> If possible, I'd like to have 1.4.0.SP1 ship with AS
>>>>>>> 4.0.5.CR1 (it's currently at 1.4.0.GA). It looks like there is
>>>>>>> still quite a bit to do on 4.0.5.CR1, so if this could be QA'd
>>>>>>> before
>>>>>>> 4.0.5.CR1 is ready that would be great.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Brian Stansberry
>>>>>>> Lead, AS Clustering
>>>>>>> JBoss, a division of Red Hat
>>>>>>> Ph: 510-396-3864
>>>>>>> skype: bstansberry
>>>>>>>
>>>>>>> jbosscache-dev-bounces(a)lists.jboss.org wrote:
>>>>>>>> Hi guys,
>>>>>>>>
>>>>>>>> I've tagged JBossCache_1_4_0_SP1 and this is ready for release.
>>>>>>>>
>>>>>>>> Could you please go ahead and complete this. Please note the
>>>>>>>> new steps on
>>>>>>> http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheQA which
>>>>>>>> will involve checking the release against JBoss AS. For this,
>>>>>>>> you'd need to check it against 4.0.5.CR1.
>>>>>>>>
>>>>>>>> I'll raise a separate task in JIRA for regression testing the
>>>>>>>> release with 4.0.3.SP1 and 4.0.4.GA after the release.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>
>>
>
> _______________________________________________
> jbosscache-dev mailing list
> jbosscache-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
Ph: 510-396-3864
skype: bstansberry
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.10.10/418 - Release Date:
8/14/2006
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.10.10/418 - Release Date:
8/14/2006
19 years, 1 month
RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
by Rajesh Rajasekaran
Brian
I m unable to startup the servers for the clustering tests in Branch_4_0
irrespective of the version of JBossCache.
I get the following error on the server.
2006-08-14 13:55:39,904 WARN [org.jgroups.protocols.AUTOCONF] failed
creating DatagramSocket: java.net.UnknownHostException:
dev02.pub.qa.atl.jboss.com: dev02.pub.qa.atl.jboss.com
2006-08-14 13:55:39,906 ERROR [org.jgroups.protocols.UDP]
max_bundle_size (64000) is greater than largest UDP fragmentation size
(0)
2006-08-14 13:55:39,909 DEBUG [org.jboss.cache.aop.TreeCacheAop]
Initialization failed jboss.cache:service=TomcatClusteringCache
ChannelException: unable to setup the protocol stack
at org.jgroups.JChannel.<init>(JChannel.java:217)
at org.jgroups.JChannel.<init>(JChannel.java:189)
at org.jboss.cache.TreeCache._createService(TreeCache.java:1373)
at org.jboss.cache.TreeCache.createService(TreeCache.java:1300)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSup
port.java:260)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBean
Support.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2006-08-14 13:55:39,916 WARN [org.jboss.system.ServiceController]
Problem creating service jboss.cache:service=TomcatClusteringCache
ChannelException: unable to setup the protocol stack
at org.jgroups.JChannel.<init>(JChannel.java:217)
at org.jgroups.JChannel.<init>(JChannel.java:189)
at org.jboss.cache.TreeCache._createService(TreeCache.java:1373)
at org.jboss.cache.TreeCache.createService(TreeCache.java:1300)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSup
port.java:260)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBean
Support.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
-----Original Message-----
From: Brian Stansberry
Sent: Monday, August 14, 2006 11:55 AM
To: Manik Surtani; Rajesh Rajasekaran
Cc: jbosscache-dev(a)lists.jboss.org; QA
Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
Just Branch_4_0 is fine with me.
jbosscache-dev-bounces(a)lists.jboss.org wrote:
> If Brian's happy with just Branch_4_0 then I'm ok with it.
>
> We can regress with 4.0.4 and 4.0.3.Sp1 after release, for the compat
> matrix.
>
> Cheers,
>
>> Have verified the testsuite on jdk 1.5, 1.4 and on the packaged
>> binary. Tutorials and examples have also been verified.
>>
>> Have to check for any regression with Branch_4_0 (4.0.5.CR1)
>> 4.0.4.GA also required?
>>
>> -----Original Message-----
>> From: Manik Surtani [mailto:manik@jboss.org]
>> Sent: Monday, August 14, 2006 7:03 AM
>> To: QA; jbosscache-dev(a)lists.jboss.org
>> Subject: Re: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>
>> Sorry, meant to CC the mail list on this too.
>> --
>> Manik Surtani
>>
>> Lead, JBoss Cache
>> JBoss, a division of Red Hat
>>
>> Email: manik(a)jboss.org
>> Telephone: +44 7786 702 706
>> MSN: manik(a)surtani.org
>> Yahoo/AIM/Skype: maniksurtani
>>
>>
>> On 14 Aug 2006, at 13:02, Manik Surtani wrote:
>>
>>> How's this release looking now?
>>> --
>>> Manik Surtani
>>>
>>> Lead, JBoss Cache
>>> JBoss, a division of Red Hat
>>>
>>> Email: manik(a)jboss.org
>>> Telephone: +44 7786 702 706
>>> MSN: manik(a)surtani.org
>>> Yahoo/AIM/Skype: maniksurtani
>>>
>>>
>>> On 11 Aug 2006, at 21:07, Brian Stansberry wrote:
>>>
>>>> It was a trivial problem with a nested if (log.isDebugEnabled())
>>>> statement. I reran most of the failed tests (but just a
>>>> representative sample of the ones ino.j.c.aop.statetransfer and
>>>> o.j.c.statetransfer -- they duplicate the same thing, and the
>>>> failure mode was the same in all cases). All looks well.
>>>>
>>>> JBossCache_1_4_0_SP1 tag has been moved.
>>>>
>>>> Brian Stansberry
>>>> Lead, AS Clustering
>>>> JBoss, a division of Red Hat
>>>> Ph: 510-396-3864
>>>> skype: bstansberry
>>>>
>>>>> -----Original Message-----
>>>>> From: Rajesh Rajasekaran
>>>>> Sent: Friday, August 11, 2006 1:59 PM
>>>>> To: Manik Surtani; Brian Stansberry; Ben Wang
>>>>> Cc: QA
>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>
>>>>> I had all the statetransfer and interop tests failing.
>>>>> I ve attached the test results.
>>>>>
>>>>>
>>>>> Thanks
>>>>> Rajesh
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Rajesh Rajasekaran
>>>>>> Sent: Friday, August 11, 2006 12:03 PM
>>>>>> To: Brian Stansberry
>>>>>> Cc: Manik Surtani; Ryan Campbell
>>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>>
>>>>>> Yes. I have the testsuite results and I notice a few failures.
>>>>>> I ll verify the failures again and send out the list (after
>>>>>> lunch). Maybe you can move the tag once if any fixes are made
>>>>>> for those tests.
>>>>>>
>>>>>> Here's the jira to track the release.
>>>>>> http://jira.jboss.com/jira/browse/JBQA-432
>>>>>>
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Brian Stansberry
>>>>>> Sent: Friday, August 11, 2006 11:54 AM
>>>>>> To: Rajesh Rajasekaran
>>>>>> Cc: Manik Surtani
>>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>>
>>>>>> Hi Rajesh,
>>>>>>
>>>>>> Have you guys started on this? We had a conversation about
>>>>>> changing the logging level of 2 log statements, and I'd like to
>>>>>> move the tag for that.
>>>>>>
>>>>>> Brian Stansberry
>>>>>> Lead, AS Clustering
>>>>>> JBoss, a division of Red Hat
>>>>>> Ph: 510-396-3864
>>>>>> skype: bstansberry
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Rajesh Rajasekaran
>>>>>>> Sent: Thursday, August 10, 2006 11:11 AM
>>>>>>> To: Brian Stansberry; QA
>>>>>>> Cc: 'jbosscache-dev(a)lists.jboss.org'
>>>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>>>
>>>>>>> Yes. We could have this release out by tomorrow.
>>>>>>> Should the release be done with Sun jdk 1.5 or jrockit 1.5?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Brian Stansberry
>>>>>>> Sent: Thursday, August 10, 2006 11:08 AM
>>>>>>> To: QA
>>>>>>> Cc: jbosscache-dev(a)lists.jboss.org
>>>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>>>
>>>>>>> If possible, I'd like to have 1.4.0.SP1 ship with AS
>>>>>>> 4.0.5.CR1 (it's currently at 1.4.0.GA). It looks like there is
>>>>>>> still quite a bit to do on 4.0.5.CR1, so if this could be QA'd
>>>>>>> before
>>>>>>> 4.0.5.CR1 is ready that would be great.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Brian Stansberry
>>>>>>> Lead, AS Clustering
>>>>>>> JBoss, a division of Red Hat
>>>>>>> Ph: 510-396-3864
>>>>>>> skype: bstansberry
>>>>>>>
>>>>>>> jbosscache-dev-bounces(a)lists.jboss.org wrote:
>>>>>>>> Hi guys,
>>>>>>>>
>>>>>>>> I've tagged JBossCache_1_4_0_SP1 and this is ready for release.
>>>>>>>>
>>>>>>>> Could you please go ahead and complete this. Please note the
>>>>>>>> new steps on
>>>>>>> http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheQA which
>>>>>>>> will involve checking the release against JBoss AS. For this,
>>>>>>>> you'd need to check it against 4.0.5.CR1.
>>>>>>>>
>>>>>>>> I'll raise a separate task in JIRA for regression testing the
>>>>>>>> release with 4.0.3.SP1 and 4.0.4.GA after the release.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>
>>
>
> _______________________________________________
> jbosscache-dev mailing list
> jbosscache-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
Ph: 510-396-3864
skype: bstansberry
19 years, 1 month
RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
by Brian Stansberry
Just Branch_4_0 is fine with me.
jbosscache-dev-bounces(a)lists.jboss.org wrote:
> If Brian's happy with just Branch_4_0 then I'm ok with it.
>
> We can regress with 4.0.4 and 4.0.3.Sp1 after release, for the compat
> matrix.
>
> Cheers,
>
>> Have verified the testsuite on jdk 1.5, 1.4 and on the packaged
>> binary. Tutorials and examples have also been verified.
>>
>> Have to check for any regression with Branch_4_0 (4.0.5.CR1)
>> 4.0.4.GA also required?
>>
>> -----Original Message-----
>> From: Manik Surtani [mailto:manik@jboss.org]
>> Sent: Monday, August 14, 2006 7:03 AM
>> To: QA; jbosscache-dev(a)lists.jboss.org
>> Subject: Re: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>
>> Sorry, meant to CC the mail list on this too.
>> --
>> Manik Surtani
>>
>> Lead, JBoss Cache
>> JBoss, a division of Red Hat
>>
>> Email: manik(a)jboss.org
>> Telephone: +44 7786 702 706
>> MSN: manik(a)surtani.org
>> Yahoo/AIM/Skype: maniksurtani
>>
>>
>> On 14 Aug 2006, at 13:02, Manik Surtani wrote:
>>
>>> How's this release looking now?
>>> --
>>> Manik Surtani
>>>
>>> Lead, JBoss Cache
>>> JBoss, a division of Red Hat
>>>
>>> Email: manik(a)jboss.org
>>> Telephone: +44 7786 702 706
>>> MSN: manik(a)surtani.org
>>> Yahoo/AIM/Skype: maniksurtani
>>>
>>>
>>> On 11 Aug 2006, at 21:07, Brian Stansberry wrote:
>>>
>>>> It was a trivial problem with a nested if (log.isDebugEnabled())
>>>> statement. I reran most of the failed tests (but just a
>>>> representative sample of the ones ino.j.c.aop.statetransfer and
>>>> o.j.c.statetransfer -- they duplicate the same thing, and the
>>>> failure mode was the same in all cases). All looks well.
>>>>
>>>> JBossCache_1_4_0_SP1 tag has been moved.
>>>>
>>>> Brian Stansberry
>>>> Lead, AS Clustering
>>>> JBoss, a division of Red Hat
>>>> Ph: 510-396-3864
>>>> skype: bstansberry
>>>>
>>>>> -----Original Message-----
>>>>> From: Rajesh Rajasekaran
>>>>> Sent: Friday, August 11, 2006 1:59 PM
>>>>> To: Manik Surtani; Brian Stansberry; Ben Wang
>>>>> Cc: QA
>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>
>>>>> I had all the statetransfer and interop tests failing.
>>>>> I ve attached the test results.
>>>>>
>>>>>
>>>>> Thanks
>>>>> Rajesh
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Rajesh Rajasekaran
>>>>>> Sent: Friday, August 11, 2006 12:03 PM
>>>>>> To: Brian Stansberry
>>>>>> Cc: Manik Surtani; Ryan Campbell
>>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>>
>>>>>> Yes. I have the testsuite results and I notice a few failures.
>>>>>> I ll verify the failures again and send out the list (after
>>>>>> lunch). Maybe you can move the tag once if any fixes are made
>>>>>> for those tests.
>>>>>>
>>>>>> Here's the jira to track the release.
>>>>>> http://jira.jboss.com/jira/browse/JBQA-432
>>>>>>
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Brian Stansberry
>>>>>> Sent: Friday, August 11, 2006 11:54 AM
>>>>>> To: Rajesh Rajasekaran
>>>>>> Cc: Manik Surtani
>>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>>
>>>>>> Hi Rajesh,
>>>>>>
>>>>>> Have you guys started on this? We had a conversation about
>>>>>> changing the logging level of 2 log statements, and I'd like to
>>>>>> move the tag for that.
>>>>>>
>>>>>> Brian Stansberry
>>>>>> Lead, AS Clustering
>>>>>> JBoss, a division of Red Hat
>>>>>> Ph: 510-396-3864
>>>>>> skype: bstansberry
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Rajesh Rajasekaran
>>>>>>> Sent: Thursday, August 10, 2006 11:11 AM
>>>>>>> To: Brian Stansberry; QA
>>>>>>> Cc: 'jbosscache-dev(a)lists.jboss.org'
>>>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>>>
>>>>>>> Yes. We could have this release out by tomorrow.
>>>>>>> Should the release be done with Sun jdk 1.5 or jrockit 1.5?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Brian Stansberry
>>>>>>> Sent: Thursday, August 10, 2006 11:08 AM
>>>>>>> To: QA
>>>>>>> Cc: jbosscache-dev(a)lists.jboss.org
>>>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>>>
>>>>>>> If possible, I'd like to have 1.4.0.SP1 ship with AS
>>>>>>> 4.0.5.CR1 (it's currently at 1.4.0.GA). It looks like there is
>>>>>>> still quite a bit to do on 4.0.5.CR1, so if this could be QA'd
>>>>>>> before
>>>>>>> 4.0.5.CR1 is ready that would be great.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Brian Stansberry
>>>>>>> Lead, AS Clustering
>>>>>>> JBoss, a division of Red Hat
>>>>>>> Ph: 510-396-3864
>>>>>>> skype: bstansberry
>>>>>>>
>>>>>>> jbosscache-dev-bounces(a)lists.jboss.org wrote:
>>>>>>>> Hi guys,
>>>>>>>>
>>>>>>>> I've tagged JBossCache_1_4_0_SP1 and this is ready for release.
>>>>>>>>
>>>>>>>> Could you please go ahead and complete this. Please note the
>>>>>>>> new steps on
>>>>>>> http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheQA which
>>>>>>>> will involve checking the release against JBoss AS. For this,
>>>>>>>> you'd need to check it against 4.0.5.CR1.
>>>>>>>>
>>>>>>>> I'll raise a separate task in JIRA for regression testing the
>>>>>>>> release with 4.0.3.SP1 and 4.0.4.GA after the release.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>
>>
>
> _______________________________________________
> jbosscache-dev mailing list
> jbosscache-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
Ph: 510-396-3864
skype: bstansberry
19 years, 1 month
Re: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
by Manik Surtani
If Brian's happy with just Branch_4_0 then I'm ok with it.
We can regress with 4.0.4 and 4.0.3.Sp1 after release, for the compat
matrix.
Cheers,
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
On 14 Aug 2006, at 17:18, Rajesh Rajasekaran wrote:
> Have verified the testsuite on jdk 1.5, 1.4 and on the packaged
> binary.
> Tutorials and examples have also been verified.
>
> Have to check for any regression with Branch_4_0 (4.0.5.CR1)
> 4.0.4.GA also required?
>
> -----Original Message-----
> From: Manik Surtani [mailto:manik@jboss.org]
> Sent: Monday, August 14, 2006 7:03 AM
> To: QA; jbosscache-dev(a)lists.jboss.org
> Subject: Re: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>
> Sorry, meant to CC the mail list on this too.
> --
> Manik Surtani
>
> Lead, JBoss Cache
> JBoss, a division of Red Hat
>
> Email: manik(a)jboss.org
> Telephone: +44 7786 702 706
> MSN: manik(a)surtani.org
> Yahoo/AIM/Skype: maniksurtani
>
>
> On 14 Aug 2006, at 13:02, Manik Surtani wrote:
>
>> How's this release looking now?
>> --
>> Manik Surtani
>>
>> Lead, JBoss Cache
>> JBoss, a division of Red Hat
>>
>> Email: manik(a)jboss.org
>> Telephone: +44 7786 702 706
>> MSN: manik(a)surtani.org
>> Yahoo/AIM/Skype: maniksurtani
>>
>>
>> On 11 Aug 2006, at 21:07, Brian Stansberry wrote:
>>
>>> It was a trivial problem with a nested if (log.isDebugEnabled())
>>> statement. I reran most of the failed tests (but just a
>>> representative
>>> sample of the ones ino.j.c.aop.statetransfer and
>>> o.j.c.statetransfer --
>>> they duplicate the same thing, and the failure mode was the same
>>> in all
>>> cases). All looks well.
>>>
>>> JBossCache_1_4_0_SP1 tag has been moved.
>>>
>>> Brian Stansberry
>>> Lead, AS Clustering
>>> JBoss, a division of Red Hat
>>> Ph: 510-396-3864
>>> skype: bstansberry
>>>
>>>> -----Original Message-----
>>>> From: Rajesh Rajasekaran
>>>> Sent: Friday, August 11, 2006 1:59 PM
>>>> To: Manik Surtani; Brian Stansberry; Ben Wang
>>>> Cc: QA
>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>
>>>> I had all the statetransfer and interop tests failing.
>>>> I ve attached the test results.
>>>>
>>>>
>>>> Thanks
>>>> Rajesh
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Rajesh Rajasekaran
>>>>> Sent: Friday, August 11, 2006 12:03 PM
>>>>> To: Brian Stansberry
>>>>> Cc: Manik Surtani; Ryan Campbell
>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>
>>>>> Yes. I have the testsuite results and I notice a few failures.
>>>>> I ll verify the failures again and send out the list (after
>>>>> lunch).
>>>>> Maybe you can move the tag once if any fixes are made for
>>>> those tests.
>>>>>
>>>>> Here's the jira to track the release.
>>>>> http://jira.jboss.com/jira/browse/JBQA-432
>>>>>
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: Brian Stansberry
>>>>> Sent: Friday, August 11, 2006 11:54 AM
>>>>> To: Rajesh Rajasekaran
>>>>> Cc: Manik Surtani
>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>
>>>>> Hi Rajesh,
>>>>>
>>>>> Have you guys started on this? We had a conversation about
>>>> changing
>>>>> the logging level of 2 log statements, and I'd like to move the
>>>>> tag
>>>>> for that.
>>>>>
>>>>> Brian Stansberry
>>>>> Lead, AS Clustering
>>>>> JBoss, a division of Red Hat
>>>>> Ph: 510-396-3864
>>>>> skype: bstansberry
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Rajesh Rajasekaran
>>>>>> Sent: Thursday, August 10, 2006 11:11 AM
>>>>>> To: Brian Stansberry; QA
>>>>>> Cc: 'jbosscache-dev(a)lists.jboss.org'
>>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>>
>>>>>> Yes. We could have this release out by tomorrow.
>>>>>> Should the release be done with Sun jdk 1.5 or jrockit 1.5?
>>>>>>
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Brian Stansberry
>>>>>> Sent: Thursday, August 10, 2006 11:08 AM
>>>>>> To: QA
>>>>>> Cc: jbosscache-dev(a)lists.jboss.org
>>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>>
>>>>>> If possible, I'd like to have 1.4.0.SP1 ship with AS
>>>>>> 4.0.5.CR1 (it's currently at 1.4.0.GA). It looks like
>>>>> there is still
>>>>>> quite a bit to do on 4.0.5.CR1, so if this could be QA'd before
>>>>>> 4.0.5.CR1 is ready that would be great.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Brian Stansberry
>>>>>> Lead, AS Clustering
>>>>>> JBoss, a division of Red Hat
>>>>>> Ph: 510-396-3864
>>>>>> skype: bstansberry
>>>>>>
>>>>>> jbosscache-dev-bounces(a)lists.jboss.org wrote:
>>>>>>> Hi guys,
>>>>>>>
>>>>>>> I've tagged JBossCache_1_4_0_SP1 and this is ready for release.
>>>>>>>
>>>>>>> Could you please go ahead and complete this. Please
>>>> note the new
>>>>>>> steps on
>>>>>> http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheQA which
>>>>>>> will involve checking the release against JBoss AS. For
>>>>>> this, you'd
>>>>>>> need to check it against 4.0.5.CR1.
>>>>>>>
>>>>>>> I'll raise a separate task in JIRA for regression testing
>>>>>> the release
>>>>>>> with 4.0.3.SP1 and 4.0.4.GA after the release.
>>>>>>>
>>>>>>> Thanks,
>>>>>>
>>>>>>
>>>>>
>>>>
>>
>
19 years, 1 month
Re: Mail lists
by Manik Surtani
I must say I'm not too keen on switching to SVN just yet - too much
on my plate at the moment. How does the end of Oct sound, once I've
released JBC 2.0.0?
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
On 14 Aug 2006, at 14:28, Ruel Loehr wrote:
> Converting the jboss-cache cvs proj over to svn would in my opinion
> be pretty trivial. It's one single module, no mutation craziness
> would be needed, just a straight cvs2svn conversion. I'm
> thinking it would take a couple of days at most, 1 day to setup and
> test, 1 day to do a production conversion.
>
> Ruel Loehr
> JBoss QA
>
> -----------------------------
> 512-342-7840 ext 2011
> Yahoo: ruelloehr
> Skype: ruelloehr
> AOL: dokoruel
>
> -----Original Message-----
> From: Eric Brown
> Sent: Sunday, August 13, 2006 8:44 PM
> To: Manik Surtani; Ruel Loehr; Ryan Campbell
> Cc: IT Ops Team
> Subject: Re: Mail lists
>
> Since your repo is still within the old JBoss cvs repo, we don't
> have much option here w/out making mods to the existing scripts.
>
> TomBen - Can our existing script do this easily?
>
> I'd rather just get you guys on the schedule to move out of the
> old CVS to your own svn repo. I'm including Ryan and Ruel to
> comment on cvs2svn conversion.
>
>
>> From: Manik Surtani <manik(a)jboss.org>
>> Date: Fri, 11 Aug 2006 10:21:47 -0500
>> To: Eric Brown <eric.brown(a)jboss.com>
>> Conversation: Mail lists
>> Subject: Mail lists
>>
>> Hi Eric
>>
>> Could we pls make sure CVS commits on JBoss Cache are now mailed to
>> jbosscache-commits and JIRA notifications to jbosscache-issues, pls.
>> I suspect they're currently going to either the jboss-* lists or the
>> old SF ones.
>>
>> Thanks!
>> --
>> Manik Surtani
>>
>> Lead, JBoss Cache
>> JBoss, a division of Red Hat
>>
>> Email: manik(a)jboss.org
>> Telephone: +44 7786 702 706
>> MSN: manik(a)surtani.org
>> Yahoo/AIM/Skype: maniksurtani
>>
>>
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.405 / Virus Database: 268.10.10/418 - Release Date:
> 8/14/2006
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.405 / Virus Database: 268.10.10/418 - Release Date:
> 8/14/2006
>
19 years, 1 month
Habanero: implementing peek() and _*() methods
by Manik Surtani
In 2.0.0, all interceptors have a reference to a CacheSPI only.
This causes a problem in some interceptors (cache loader, lock
interceptors, etc) which currently make a few direct calls to _get(),
_put(), etc. to perform operations on the cache while bypassing the
interceptor stack entirely.
What do people think the best way would be do provide this access for
very specialised cases, but not exposing such calls in the CacheSPI
interface for generic Interceptors people may implement?
I'm currently doing this by creating a 'bypassInterceptorChain'
option and then calling a standard put() or get(), but this is at
best a hack, plus it exposes the 'bypassInterceptorChain' option in a
public API for users to (ab)use. Any better ideas?
Cheers,
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
19 years, 1 month
Re: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
by Manik Surtani
Sorry, meant to CC the mail list on this too.
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
On 14 Aug 2006, at 13:02, Manik Surtani wrote:
> How's this release looking now?
> --
> Manik Surtani
>
> Lead, JBoss Cache
> JBoss, a division of Red Hat
>
> Email: manik(a)jboss.org
> Telephone: +44 7786 702 706
> MSN: manik(a)surtani.org
> Yahoo/AIM/Skype: maniksurtani
>
>
> On 11 Aug 2006, at 21:07, Brian Stansberry wrote:
>
>> It was a trivial problem with a nested if (log.isDebugEnabled())
>> statement. I reran most of the failed tests (but just a
>> representative
>> sample of the ones ino.j.c.aop.statetransfer and
>> o.j.c.statetransfer --
>> they duplicate the same thing, and the failure mode was the same
>> in all
>> cases). All looks well.
>>
>> JBossCache_1_4_0_SP1 tag has been moved.
>>
>> Brian Stansberry
>> Lead, AS Clustering
>> JBoss, a division of Red Hat
>> Ph: 510-396-3864
>> skype: bstansberry
>>
>>> -----Original Message-----
>>> From: Rajesh Rajasekaran
>>> Sent: Friday, August 11, 2006 1:59 PM
>>> To: Manik Surtani; Brian Stansberry; Ben Wang
>>> Cc: QA
>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>
>>> I had all the statetransfer and interop tests failing.
>>> I ve attached the test results.
>>>
>>>
>>> Thanks
>>> Rajesh
>>>
>>>
>>>> -----Original Message-----
>>>> From: Rajesh Rajasekaran
>>>> Sent: Friday, August 11, 2006 12:03 PM
>>>> To: Brian Stansberry
>>>> Cc: Manik Surtani; Ryan Campbell
>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>
>>>> Yes. I have the testsuite results and I notice a few failures.
>>>> I ll verify the failures again and send out the list (after lunch).
>>>> Maybe you can move the tag once if any fixes are made for
>>> those tests.
>>>>
>>>> Here's the jira to track the release.
>>>> http://jira.jboss.com/jira/browse/JBQA-432
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Brian Stansberry
>>>> Sent: Friday, August 11, 2006 11:54 AM
>>>> To: Rajesh Rajasekaran
>>>> Cc: Manik Surtani
>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>
>>>> Hi Rajesh,
>>>>
>>>> Have you guys started on this? We had a conversation about
>>> changing
>>>> the logging level of 2 log statements, and I'd like to move the tag
>>>> for that.
>>>>
>>>> Brian Stansberry
>>>> Lead, AS Clustering
>>>> JBoss, a division of Red Hat
>>>> Ph: 510-396-3864
>>>> skype: bstansberry
>>>>
>>>>> -----Original Message-----
>>>>> From: Rajesh Rajasekaran
>>>>> Sent: Thursday, August 10, 2006 11:11 AM
>>>>> To: Brian Stansberry; QA
>>>>> Cc: 'jbosscache-dev(a)lists.jboss.org'
>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>
>>>>> Yes. We could have this release out by tomorrow.
>>>>> Should the release be done with Sun jdk 1.5 or jrockit 1.5?
>>>>>
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: Brian Stansberry
>>>>> Sent: Thursday, August 10, 2006 11:08 AM
>>>>> To: QA
>>>>> Cc: jbosscache-dev(a)lists.jboss.org
>>>>> Subject: RE: [jbosscache-dev] Releasing JBoss Cache 1.4.0.SP1
>>>>>
>>>>> If possible, I'd like to have 1.4.0.SP1 ship with AS
>>>>> 4.0.5.CR1 (it's currently at 1.4.0.GA). It looks like
>>>> there is still
>>>>> quite a bit to do on 4.0.5.CR1, so if this could be QA'd before
>>>>> 4.0.5.CR1 is ready that would be great.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Brian Stansberry
>>>>> Lead, AS Clustering
>>>>> JBoss, a division of Red Hat
>>>>> Ph: 510-396-3864
>>>>> skype: bstansberry
>>>>>
>>>>> jbosscache-dev-bounces(a)lists.jboss.org wrote:
>>>>>> Hi guys,
>>>>>>
>>>>>> I've tagged JBossCache_1_4_0_SP1 and this is ready for release.
>>>>>>
>>>>>> Could you please go ahead and complete this. Please
>>> note the new
>>>>>> steps on
>>>>> http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheQA which
>>>>>> will involve checking the release against JBoss AS. For
>>>>> this, you'd
>>>>>> need to check it against 4.0.5.CR1.
>>>>>>
>>>>>> I'll raise a separate task in JIRA for regression testing
>>>>> the release
>>>>>> with 4.0.3.SP1 and 4.0.4.GA after the release.
>>>>>>
>>>>>> Thanks,
>>>>>
>>>>>
>>>>
>>>
>
19 years, 1 month
RE: [jbosscache-dev] Naming discussion
by Ben Wang
Manik,
I am not sure what is "more correct" though? To me, I can see right away that PojoCache is a feature, but have a hard time to tell the difference between it and Cache without explaining it in details. I don't know what others think but it doesn't convey the right functionality that is a HasMap-like "reference" cache.
Of course, detailed explanation will work but key is to first time user, will this create confusion or not?
-Ben
-----Original Message-----
From: Manik Surtani [mailto:manik@jboss.org]
Sent: Friday, August 11, 2006 9:00 PM
To: Ben Wang
Cc: jbosscache-dev(a)lists.jboss.org
Subject: Re: [jbosscache-dev] Naming discussion
On 11 Aug 2006, at 12:17, Ben Wang wrote:
> Guys (and Manik, secifically),
>
> I have been in the process of updating the PojoCache documentation for
> 2.0 release. One thing that came up that I'd like to solicit some
> inputs. As we all agreed that PojoCache will still be housed under
> JBoss Cache (alhtough may have two separate distributions).
> That is, JBoss Cache will have two cache libararies per se. Now we
> know one component is PojoCache. How do we call the other component
> (with Cache implementation)? We used to call it TreeCache that is more
> distinguished than simply Cache, IMO.
I agree that Cache vs. PojoCache is less distinct than TreeCache vs.
PojoCache, but at the end of the day we're trying to define a product that does a single task of caching data. As you said, PojoCache builds on top of this to add Pojo/AOP based features, so one may argue that Cache vs. PojoCache, while being less distinct, is in fact more correct.
>
> FYI, in 2.0, PojoCache will use a delegate to the Cache
> implementation. Actually, there will be two seprate configuration xml
> files. One is for the Cache and the other for PojoCache. So we can say
> PojoCache is a layer on top but not a sub-class anymore.
>
> Thanks,
>
> -Ben
>
> _______________________________________________
> jbosscache-dev mailing list
> jbosscache-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
19 years, 1 month