RE: [jbosscache-dev] Developer release
by Brian Stansberry
Are the jars in repository.jboss.com? (I haven't looked.)
Ben Wang wrote:
> Brian,
>
> Thanks! I have subscribed to that Jira issue.
>
> -Ben
>
> -----Original Message-----
> From: Brian Stansberry
> Sent: Tuesday, September 26, 2006 2:52 AM
> To: Ben Wang; Manik Surtani; jbosscache-dev(a)lists.jboss.org
> Subject: RE: [jbosscache-dev] Developer release
>
> FYI, JIRA for integrating this in the AS and seeing what
> comes up is http://jira.jboss.com/jira/browse/JBAS-3695.
>
> jbosscache-dev-bounces(a)lists.jboss.org wrote:
>> OK, I have just tagged JBossCache head as "JBossCache_2_0_DR1". Since
>> this is only a DR release so it is not going thru QA and not put out
>> on sf.net. I will also announce it on the forum for those who are
>> interested in the api changes.
>>
>> And as Manik mentioned, couple tests are still failing (CC stands as
>> 98.3% today), docs and tutorial need to be updated, although I have
>> updated the examples directory for PojoCache.
>> Also good place to check is tests/functional/o/j/c/api and
>> tests-50/functional/o/j/c/pojo for the new api changes.
>>
>> Please also note that (they are all in the Jiras):
>>
>> 1. Packaging is different now as previously discussed:
>> jboss-cache-core, jboss-cache-pojo, and jboss-cache-all.
>> 2. There is a separate pojocache.jar in addition to the regular
>> jboss-cache.jar (now only has core Cache APIs).
>> 3. In PojoCache, previoulsy we have jboss-aop.xml. Now I have renamed
>> it as pojocache-aop.xml that contains the configuration for
>> PojoCache interceptors.
>>
>> -Ben
>>
>> -----Original Message-----
>> From: jbosscache-dev-bounces(a)lists.jboss.org
>> [mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of Manik
>> Surtani Sent: Thursday, September 21, 2006 6:41 PM
>> To: jbosscache-dev(a)lists.jboss.org
>> Subject: [jbosscache-dev] Developer release
>>
>> Guys,
>>
>> Ben and I are thinking of cutting a DR before the alpha.
>>
>> Known bugs include the one about marshalling large Strings (waiting
>> for jboss-serialization-1.0.3 to be released) and
>> StateTransferUnderLoad. Other issues include timing/concurrency
>> issues with BR which show up on the multi-cpu lab servers and
>> notifications around the move() API which I hope to sort out by the
>> weekend, and some of Ben's PojoCache tests.
>>
>> The rest of the functionality is all in place though and I'd like to
>> test this DR with AS HEAD and Hibernate (speaking with Steve E about
>> this).
>>
>> Ben's going to release the DR over the weekend (I'll be off to Berlin
>> on a clustering training) and hopefully we can look at an Alpha when
>> I get back.
>>
>> FYI, refer to unit tests in org.jboss.cache.api for examples of using
>> the new API and SPI. I'll update docs and tutorial with these
>> before cutting the alpha.
>>
>> Cheers,
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
Ph: 510-396-3864
skype: bstansberry
19 years
RE: [jbosscache-dev] Developer release
by Ben Wang
Brian,
Thanks! I have subscribed to that Jira issue.
-Ben
-----Original Message-----
From: Brian Stansberry
Sent: Tuesday, September 26, 2006 2:52 AM
To: Ben Wang; Manik Surtani; jbosscache-dev(a)lists.jboss.org
Subject: RE: [jbosscache-dev] Developer release
FYI, JIRA for integrating this in the AS and seeing what comes up is
http://jira.jboss.com/jira/browse/JBAS-3695.
jbosscache-dev-bounces(a)lists.jboss.org wrote:
> OK, I have just tagged JBossCache head as "JBossCache_2_0_DR1". Since
> this is only a DR release so it is not going thru QA and not put out
> on sf.net. I will also announce it on the forum for those who are
> interested in the api changes.
>
> And as Manik mentioned, couple tests are still failing (CC stands as
> 98.3% today), docs and tutorial need to be updated, although I have
> updated the examples directory for PojoCache.
> Also good place to check is tests/functional/o/j/c/api and
> tests-50/functional/o/j/c/pojo for the new api changes.
>
> Please also note that (they are all in the Jiras):
>
> 1. Packaging is different now as previously discussed:
> jboss-cache-core, jboss-cache-pojo, and jboss-cache-all.
> 2. There is a separate pojocache.jar in addition to the regular
> jboss-cache.jar (now only has core Cache APIs).
> 3. In PojoCache, previoulsy we have jboss-aop.xml. Now I have renamed
> it as pojocache-aop.xml that contains the configuration for PojoCache
> interceptors.
>
> -Ben
>
> -----Original Message-----
> From: jbosscache-dev-bounces(a)lists.jboss.org
> [mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of Manik
> Surtani Sent: Thursday, September 21, 2006 6:41 PM
> To: jbosscache-dev(a)lists.jboss.org
> Subject: [jbosscache-dev] Developer release
>
> Guys,
>
> Ben and I are thinking of cutting a DR before the alpha.
>
> Known bugs include the one about marshalling large Strings (waiting
> for jboss-serialization-1.0.3 to be released) and
> StateTransferUnderLoad. Other issues include timing/concurrency
> issues with BR which show up on the multi-cpu lab servers and
> notifications around the move() API which I hope to sort out by the
> weekend, and some of Ben's PojoCache tests.
>
> The rest of the functionality is all in place though and I'd like to
> test this DR with AS HEAD and Hibernate (speaking with Steve E about
> this).
>
> Ben's going to release the DR over the weekend (I'll be off to Berlin
> on a clustering training) and hopefully we can look at an Alpha when I
> get back.
>
> FYI, refer to unit tests in org.jboss.cache.api for examples of using
> the new API and SPI. I'll update docs and tutorial with these before
> cutting the alpha.
>
> Cheers,
19 years
RE: [jbosscache-dev] Developer release
by Brian Stansberry
FYI, JIRA for integrating this in the AS and seeing what comes up is
http://jira.jboss.com/jira/browse/JBAS-3695.
jbosscache-dev-bounces(a)lists.jboss.org wrote:
> OK, I have just tagged JBossCache head as
> "JBossCache_2_0_DR1". Since this is only a DR release so it
> is not going thru QA and not put out on sf.net. I will also
> announce it on the forum for those who are interested in the api
> changes.
>
> And as Manik mentioned, couple tests are still failing (CC
> stands as 98.3% today), docs and tutorial need to be updated,
> although I have updated the examples directory for PojoCache.
> Also good place to check is tests/functional/o/j/c/api and
> tests-50/functional/o/j/c/pojo for the new api changes.
>
> Please also note that (they are all in the Jiras):
>
> 1. Packaging is different now as previously discussed:
> jboss-cache-core, jboss-cache-pojo, and jboss-cache-all.
> 2. There is a separate pojocache.jar in addition to the
> regular jboss-cache.jar (now only has core Cache APIs).
> 3. In PojoCache, previoulsy we have jboss-aop.xml. Now I have
> renamed it as pojocache-aop.xml that contains the
> configuration for PojoCache interceptors.
>
> -Ben
>
> -----Original Message-----
> From: jbosscache-dev-bounces(a)lists.jboss.org
> [mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of Manik
> Surtani Sent: Thursday, September 21, 2006 6:41 PM
> To: jbosscache-dev(a)lists.jboss.org
> Subject: [jbosscache-dev] Developer release
>
> Guys,
>
> Ben and I are thinking of cutting a DR before the alpha.
>
> Known bugs include the one about marshalling large Strings
> (waiting for jboss-serialization-1.0.3 to be released) and
> StateTransferUnderLoad. Other issues include
> timing/concurrency issues with BR which show up on the
> multi-cpu lab servers and notifications around the move() API
> which I hope to sort out by the weekend, and some of Ben's PojoCache
> tests.
>
> The rest of the functionality is all in place though and I'd
> like to test this DR with AS HEAD and Hibernate (speaking with Steve
> E about this).
>
> Ben's going to release the DR over the weekend (I'll be off
> to Berlin on a clustering training) and hopefully we can look at an
> Alpha when I get back.
>
> FYI, refer to unit tests in org.jboss.cache.api for examples
> of using the new API and SPI. I'll update docs and tutorial
> with these before cutting the alpha.
>
> Cheers,
19 years
RE: [jbosscache-dev] Developer release
by Ben Wang
OK, I have just tagged JBossCache head as "JBossCache_2_0_DR1". Since this is only a DR release so it is not going thru QA and not put out on sf.net. I will also announce it on the forum for those who are interested in the api changes.
And as Manik mentioned, couple tests are still failing (CC stands as 98.3% today), docs and tutorial need to be updated, although I have updated the examples directory for PojoCache. Also good place to check is tests/functional/o/j/c/api and tests-50/functional/o/j/c/pojo for the new api changes.
Please also note that (they are all in the Jiras):
1. Packaging is different now as previously discussed: jboss-cache-core, jboss-cache-pojo, and jboss-cache-all.
2. There is a separate pojocache.jar in addition to the regular jboss-cache.jar (now only has core Cache APIs).
3. In PojoCache, previoulsy we have jboss-aop.xml. Now I have renamed it as pojocache-aop.xml that contains the configuration for PojoCache interceptors.
-Ben
-----Original Message-----
From: jbosscache-dev-bounces(a)lists.jboss.org [mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of Manik Surtani
Sent: Thursday, September 21, 2006 6:41 PM
To: jbosscache-dev(a)lists.jboss.org
Subject: [jbosscache-dev] Developer release
Guys,
Ben and I are thinking of cutting a DR before the alpha.
Known bugs include the one about marshalling large Strings (waiting for jboss-serialization-1.0.3 to be released) and StateTransferUnderLoad. Other issues include timing/concurrency issues with BR which show up on the multi-cpu lab servers and notifications around the move() API which I hope to sort out by the weekend, and some of Ben's PojoCache tests.
The rest of the functionality is all in place though and I'd like to test this DR with AS HEAD and Hibernate (speaking with Steve E about this).
Ben's going to release the DR over the weekend (I'll be off to Berlin on a clustering training) and hopefully we can look at an Alpha when I get back.
FYI, refer to unit tests in org.jboss.cache.api for examples of using the new API and SPI. I'll update docs and tutorial with these before cutting the alpha.
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
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev
19 years
RE: [jbosscache-dev] Re: CruiseControl
by Ryan Campbell
The last commits should be on top. The last time I looked into this,
there was not a way to control this behavior.
> -----Original Message-----
> From: Vladimir Blagojevic
> Sent: Friday, September 22, 2006 11:08 AM
> To: Ryan Campbell; Eric Brown; Manik Surtani; QA
> Cc: 'jbosscache-dev(a)lists.jboss.org'
> Subject: RE: [jbosscache-dev] Re: CruiseControl
>
> Ryan, you are right. I overlooked this fact when I analyzed remoting
> example. It is very hard for a project of jbc complexity to achieve
100%
> test passing with almost 2000 unit tests during dev stage. It would be
> great
> if this option could be changed from build to build during dev stage
> rather
> than between two successful builds.
>
>
>
> > -----Original Message-----
> > From: Ryan Campbell
> > Sent: Friday, September 22, 2006 11:54 AM
> > To: Vladimir Blagojevic; Eric Brown; Manik Surtani; QA
> > Cc: 'jbosscache-dev(a)lists.jboss.org'
> > Subject: RE: [jbosscache-dev] Re: CruiseControl
> >
> > The commits are reported until a successful build.
19 years
RE: [jbosscache-dev] Re: CruiseControl
by Vladimir Blagojevic
Ryan, you are right. I overlooked this fact when I analyzed remoting
example. It is very hard for a project of jbc complexity to achieve 100%
test passing with almost 2000 unit tests during dev stage. It would be
great
if this option could be changed from build to build during dev stage
rather
than between two successful builds.
> -----Original Message-----
> From: Ryan Campbell
> Sent: Friday, September 22, 2006 11:54 AM
> To: Vladimir Blagojevic; Eric Brown; Manik Surtani; QA
> Cc: 'jbosscache-dev(a)lists.jboss.org'
> Subject: RE: [jbosscache-dev] Re: CruiseControl
>
> The commits are reported until a successful build.
19 years
RE: [jbosscache-dev] Re: CruiseControl
by Ryan Campbell
The commits are reported until a successful build.
> -----Original Message-----
> From: Vladimir Blagojevic
> Sent: Friday, September 22, 2006 10:02 AM
> To: Eric Brown; Manik Surtani; QA
> Cc: jbosscache-dev(a)lists.jboss.org
> Subject: RE: [jbosscache-dev] Re: CruiseControl
>
> Eric,
>
> Did you notice that jboss cache cruise control modification list is
always
> listing the
> same modifications since the last build?
>
> Manik, wouldn't you agree that it would be more useful to have list of
> modifications
> between each build? I don't think this is impossible to setup. Jboss
> remoting [1], for
> example, has this setup.
>
>
> [1] http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-
> testsuite-1.4
>
>
> > -----Original Message-----
> > From: jbosscache-dev-bounces(a)lists.jboss.org
> > [mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of
> > Eric Brown
> > Sent: Thursday, September 14, 2006 1:38 PM
> > To: Manik Surtani; QA
> > Cc: jbosscache-dev(a)lists.jboss.org
> > Subject: [jbosscache-dev] Re: CruiseControl
> >
> > We had the CC builds servers down for scheduled maint. for
> > several hours.
> >
> >
> > > From: Manik Surtani <manik(a)jboss.org>
> > > Date: Thu, 14 Sep 2006 13:35:31 +0100
> > > To: QA <qa(a)jboss.org>
> > > Cc: <jbosscache-dev(a)lists.jboss.org>
> > > Subject: CruiseControl
> > >
> > > Hi, I noticed that CC did not run the JBC testsuite last night.
Any
> > > idea what's up?
> > >
> > > 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
> > >
> > >
> >
> > _______________________________________________
> > jbosscache-dev mailing list
> > jbosscache-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jbosscache-dev
> >
19 years
RE: [jbosscache-dev] Re: CruiseControl
by Vladimir Blagojevic
Eric,
Did you notice that jboss cache cruise control modification list is
always listing the
same modifications since the last build?
Manik, wouldn't you agree that it would be more useful to have list of
modifications
between each build? I don't think this is impossible to setup. Jboss
remoting [1], for
example, has this setup.
[1]
http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-
1.4
> -----Original Message-----
> From: jbosscache-dev-bounces(a)lists.jboss.org
> [mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of
> Eric Brown
> Sent: Thursday, September 14, 2006 1:38 PM
> To: Manik Surtani; QA
> Cc: jbosscache-dev(a)lists.jboss.org
> Subject: [jbosscache-dev] Re: CruiseControl
>
> We had the CC builds servers down for scheduled maint. for
> several hours.
>
>
> > From: Manik Surtani <manik(a)jboss.org>
> > Date: Thu, 14 Sep 2006 13:35:31 +0100
> > To: QA <qa(a)jboss.org>
> > Cc: <jbosscache-dev(a)lists.jboss.org>
> > Subject: CruiseControl
> >
> > Hi, I noticed that CC did not run the JBC testsuite last night. Any
> > idea what's up?
> >
> > 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
> >
> >
>
> _______________________________________________
> jbosscache-dev mailing list
> jbosscache-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
>
19 years
Developer release
by Manik Surtani
Guys,
Ben and I are thinking of cutting a DR before the alpha.
Known bugs include the one about marshalling large Strings (waiting
for jboss-serialization-1.0.3 to be released) and
StateTransferUnderLoad. Other issues include timing/concurrency
issues with BR which show up on the multi-cpu lab servers and
notifications around the move() API which I hope to sort out by the
weekend, and some of Ben's PojoCache tests.
The rest of the functionality is all in place though and I'd like to
test this DR with AS HEAD and Hibernate (speaking with Steve E about
this).
Ben's going to release the DR over the weekend (I'll be off to Berlin
on a clustering training) and hopefully we can look at an Alpha when
I get back.
FYI, refer to unit tests in org.jboss.cache.api for examples of using
the new API and SPI. I'll update docs and tutorial with these before
cutting the alpha.
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
Buddy replication tests
by Vladimir Blagojevic
It seems like buddy replication tests are failing due to a simple
oversight in BuddyReplicationContentTest and BuddyGroupAssignmentTest.
BuddyReplicationContentTest does not have tearDown method and thus cache
members accumulate over tests leading to test failures.
BuddyGroupAssignmentTest has tearDown method but instead of assigning
created caches to field of TreeCache[] each test method assigns created
caches to method local variable. Thus tearDown which cleans up private
field of TreeCache [] has no effect. The end result is the same - number
of caches in the cluster accumulate over the tests leading to test
failures.
19 years