RE: [jbosscache-dev] Finalizing JBCACHE-840
by Vladimir Blagojevic
Nothing I can find. I did not get notificatin email. There is no trace
that the build ran at all...
> -----Original Message-----
> From: Manik Surtani [mailto:manik@jboss.org]
> Sent: Friday, January 12, 2007 9:49 AM
> To: Vladimir Blagojevic
> Cc: Brian Stansberry; jbosscache-dev(a)lists.jboss.org
> Subject: Re: [jbosscache-dev] Finalizing JBCACHE-840
>
> Nothing in the compile log?
> --
> 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 12 Jan 2007, at 14:41, Vladimir Blagojevic wrote:
>
> >
> > Hmm. Build report is missing! Locally it worked for me and
> the suite
> > ran for about 180 minutes. Report looked good, everything was fine.
> > Wonder why is it missing?
>
>
>
19 years, 1 month
RE: [jbosscache-dev] Finalizing JBCACHE-840
by Vladimir Blagojevic
Hmm. Build report is missing! Locally it worked for me and the suite ran
for about 180 minutes. Report looked good, everything was fine. Wonder
why is it missing?
19 years, 1 month
RE: [jbosscache-dev] JBCACHE-928 (lifecycle state)
by Brian Stansberry
Manik Surtani wrote:
> On 11 Jan 2007, at 15:33, Brian Stansberry wrote:
>
>> I should have discussed this before opening JIRA, since the use case
>> isn't clear, but...
>>
>> Exposure in JMX makes sense, since we expose the lifecycle
>> operations, i.e. you stop the cache and your colleague comes and
>> bugs you, it's nice to be able to see the state it's in when you get
>> back to work.
>>
>> I *believe* (pretty sure actually) in AS 5 the MC will uninstall a
>> bean if it fails in deployment, and this will include deregistering
>> from JMX. So, the AS 4.x use case of being able to see the status of
>> a failed deployment in the JMX console probably doesn't apply.
>>
>> Are there situations where the cache lifecycle can change internally?
>> For example, as a result of the channel being shunned and auto-
>> closing? Right now we don't handle that, but if we did, is it
>> possible it would trigger a lifecycle transition?
>
> True. At the moment though this is not the case. But since
> this is just an addition of an API, perhaps we add it later when we
> have the need?
>
+1. I reread the JIRA and it's to "consider" the issue. By Beta1, since
it impacts API. We've now considered it, so pushing it out to some
future point is fine by me. :-)
- Brian
19 years, 1 month
RE: [jbosscache-dev] Finalizing JBCACHE-840
by Vladimir Blagojevic
Ok. I am doing a testsuite run locally now. If all good, I'll commit
changes to build and we start with both udp and tcp test starting
tonight!
> -----Original Message-----
> From: Manik Surtani [mailto:manik@jboss.org]
> Sent: Thursday, January 11, 2007 12:56 PM
> To: Vladimir Blagojevic
> Cc: Brian Stansberry; jbosscache-dev(a)lists.jboss.org
> Subject: Re: [jbosscache-dev] Finalizing JBCACHE-840
>
> Yeah, fine by me ... I'd say if it is just a single formatter
> class lets copy it to our test src tree.
> --
> 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] Finalizing JBCACHE-840
by Vladimir Blagojevic
Hey,
Brian thanks for the pointer. This works! There is a small caveat. We
have to use a special formatter [1] in order to have a nice report that
indicates which stack was used in a specific test. Since this formatter
class resides in jboss test project and is not dependent to anything
else should we copy it to our source tree or use a jboss test project
jar?
So how will test report look like, you ask? Each test name will have
appended jgroups stack configuration used. Something like this report
[2] except it is not going to be reddish so much, same colours as
before.
What do you guys say?
[1]
http://fisheye.jboss.org/viewrep/JBoss/jbosstest/src/main/org/jboss/ant/
taskdefs/XMLJUnitMultipleResultFormatter.java?r=1.3.4.2
[2]
http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.2-testsuite-1.4/2006
1231190048/results/org/jboss/test/cluster/test/package-summary.html
> Have a look at tests-clustering-all-stacks in the AS
> testsuite build.xml. It basically re-runs all the tests with
> a different config, and info about the config is appended to
> the name of the test report so the 2nd run doesn't overwrite
> the 1st. I'm sure what you'd do would be different, but you
> can probably gets some ideas from there.
>
> - Brian
19 years, 1 month
RE: [jbosscache-dev] JBCACHE-928 (lifecycle state)
by Brian Stansberry
I should have discussed this before opening JIRA, since the use case
isn't clear, but...
Exposure in JMX makes sense, since we expose the lifecycle operations,
i.e. you stop the cache and your colleague comes and bugs you, it's nice
to be able to see the state it's in when you get back to work.
I *believe* (pretty sure actually) in AS 5 the MC will uninstall a bean
if it fails in deployment, and this will include deregistering from JMX.
So, the AS 4.x use case of being able to see the status of a failed
deployment in the JMX console probably doesn't apply.
Are there situations where the cache lifecycle can change internally?
For example, as a result of the channel being shunned and auto-closing?
Right now we don't handle that, but if we did, is it possible it would
trigger a lifecycle transition?
- Brian
jbosscache-dev-bounces(a)lists.jboss.org wrote:
> Brian,
>
> What would the use case of getState() be? Is this for use by
> the MC and other mechanisms to manage the cache via JMX?
>
> I guess what I'm asking is, where does this need to reside?
> In the Cache, CacheSPI or JMX interface? And also, what
> statii are we looking for? I have a simple boolean "started"
> at the moment, but this could change to an enum of {CREATED,
> STARTED, STOPPED, DESTROYED} ...
>
> Cheers,
19 years, 1 month
RE: [jbosscache-dev] Habanero BETAs
by Ben Wang
I have no problem to cut beta1 early. However, we need to leave sufficient time for beta2 (or CR, for that matter). Main reason being this is a major release. I think we need to do some benchmark to make sure the performance does not suffer too much, and perform necessary optimization. This will take some time, IMO.
-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, January 11, 2007 6:13 PM
To: jbosscache-dev(a)lists.jboss.org
Cc: QA
Subject: [jbosscache-dev] Habanero BETAs
Guys,
Now that Alpha2 has been released and is in the wild, can we focus on
BETA1 tasks and target to have these cleared by Monday the 22nd so QA has time to very thoroughly test and release by the 25th.
Please let me know your thoughts on this, or if you have any concerns about tasks that may not be complete by then. Pls refer to
http://jira.jboss.com/jira/browse/JBCACHE
for the tasks I have scheduled for BETA1. The goal is to be both feature complete and to freeze the API. Profiling, benching and refactoring for BETA2.
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
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev
19 years, 1 month
RE: [jbosscache-dev] Habanero BETAs
by Galder Zamarreno
Seeing this email, I was thinking that I could commit now the changes in JDBCCacheLoader (to use VAM instead of Standard Serialization which in terms of functionality, it's working) and the VAM performance unit test that I'm about to finish.
We could the focus on VAM regression and profiling for BETA2. We would have the unit test in place and we could start testing and extending it to cover other types of objects here.
This would also allow me to introduce c3p0 connection pooling for BETA1 on time.
Manik, what do you think? And the rest?
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
IT executives: Red Hat still #1 for value http://www.redhat.com/promo/vendor/
-----Original Message-----
From: jbosscache-dev-bounces(a)lists.jboss.org [mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of Manik Surtani
Sent: 11 January 2007 11:13
To: jbosscache-dev(a)lists.jboss.org
Cc: QA
Subject: [jbosscache-dev] Habanero BETAs
Guys,
Now that Alpha2 has been released and is in the wild, can we focus on
BETA1 tasks and target to have these cleared by Monday the 22nd so QA
has time to very thoroughly test and release by the 25th.
Please let me know your thoughts on this, or if you have any concerns
about tasks that may not be complete by then. Pls refer to
http://jira.jboss.com/jira/browse/JBCACHE
for the tasks I have scheduled for BETA1. The goal is to be both
feature complete and to freeze the API. Profiling, benching and
refactoring for BETA2.
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
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev
19 years, 1 month
RE: [jbosscache-dev] Habanero BETAs
by Brian Stansberry
I don't think I'm going to be able to do much JBC stuff before 1/22.
I've got to plow through a bunch of AS/EJB3 stuff and will teach
clustering next week.
jbosscache-dev-bounces(a)lists.jboss.org wrote:
> Guys,
>
> Now that Alpha2 has been released and is in the wild, can we focus on
> BETA1 tasks and target to have these cleared by Monday the
> 22nd so QA has time to very thoroughly test and release by the 25th.
>
> Please let me know your thoughts on this, or if you have any
> concerns about tasks that may not be complete by then. Pls refer to
>
> http://jira.jboss.com/jira/browse/JBCACHE
>
> for the tasks I have scheduled for BETA1. The goal is to be
> both feature complete and to freeze the API. Profiling,
> benching and refactoring for BETA2.
>
> Thanks,
19 years, 1 month
Habanero BETAs
by Manik Surtani
Guys,
Now that Alpha2 has been released and is in the wild, can we focus on
BETA1 tasks and target to have these cleared by Monday the 22nd so QA
has time to very thoroughly test and release by the 25th.
Please let me know your thoughts on this, or if you have any concerns
about tasks that may not be complete by then. Pls refer to
http://jira.jboss.com/jira/browse/JBCACHE
for the tasks I have scheduled for BETA1. The goal is to be both
feature complete and to freeze the API. Profiling, benching and
refactoring for BETA2.
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
19 years, 1 month
