RE: [jbosscache-dev] Re: Jboss Cache CC
by Vladimir Blagojevic
Yeah I agree with this option as well.
> -----Original Message-----
> From: jbosscache-dev-bounces(a)lists.jboss.org
> [mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of
> Galder Zamarreno
> Sent: Monday, January 15, 2007 7:36 AM
> To: Manik Surtani; Ryan Campbell
> Cc: jbosscache-dev(a)lists.jboss.org; QA
> Subject: RE: [jbosscache-dev] Re: Jboss Cache CC
>
> This one:
>
> "The other alternative is to include a separate log4j.cc.xml
> in CVS and point the ant task to use this configuration (via
> the - Dlog4j.configuration property) for CC runs."
>
> 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/
18 years, 7 months
JBCACHE-752 - marshalling response values to methodcalls
by Manik Surtani
I have a prelim fix for JBCACHE-752 in HEAD. I know it's a little
hacky, but couldn't come up with a better solution without
significantly reengineering a lot of stuff. Here's where the problem
lies. Note that this only pertains to when region-based marshalling
is used.
1) When marshalling method calls, we run through a switch statement
on method id to determine which parameter contains the Fqn in
question, and we use the Fqn to determine the cache region and use
the appropriate context class loader. A bit hacky in the way the
region is identified, but works well.
2) Now for return values, there is no way to determine the region
with which to attach the response value to, without changing the
interface of the marshaller (which implements a JGroups interface) so
the Region or Fqn or maybe even a ClassLoader is somehow passed in.
What I've done is that I've assumed that when objectFromByteBuffer()
is called, you could safely assume that if the object that you
recreate is NOT a MethodCall, then it is a return value. If it is a
MethodCall, we get a hold of the Fqn (see (1)) and put it in a
ThreadLocal container. This way, when the same thread calls
objectToByteBuffer() to marshall a return value, it will have a
handle on the Fqn and hence the class loader.
Like I said, this is a bit hacky and only really works for RPC based
use of the marshaller to deal with return values of method calls.
I don't think this is a problem for other uses of the marshaller like
State Transfer and cache loaders since it is not used in an RPC
context, but I just thought I'd post this here in case someone feels
like proving me wrong. :-)
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
18 years, 7 months
RE: Jboss Cache CC
by Vladimir Blagojevic
Yeah I agree with Ryan. Lets just log to our project relative output
directory.
This is a simple change in our current etc/log4j.xml
> -----Original Message-----
> From: Ryan Campbell
> Sent: Monday, January 15, 2007 11:05 AM
> To: Manik Surtani
> Cc: Vladimir Blagojevic; jbosscache-dev(a)lists.jboss.org; QA
> Subject: RE: Jboss Cache CC
>
> We don't care if you log verbosely. Just that you don't put
> it in /tmp. ;-)
18 years, 7 months
RE: Jboss Cache CC
by Ryan Campbell
We don't care if you log verbosely. Just that you don't put it in /tmp.
;-)
> -----Original Message-----
> From: Manik Surtani [mailto:manik@jboss.org]
> Sent: Monday, January 15, 2007 4:34 AM
> To: Ryan Campbell
> Cc: Vladimir Blagojevic; jbosscache-dev(a)lists.jboss.org; QA
> Subject: Re: Jboss Cache CC
>
> Man - this is crap that there is so much logging going on. By
> default we ship with log4j.xml configured to log at INFO level, and
> this is what is in CVS.
>
> Does anyone have any objections to my setting it to ERROR before
> checking it into CVS, so CC runs perform tests with ERROR level
> logging? In addition to taking up less disk space it would also mean
> much quicker runs.
>
> It would mean an additional release task of setting this to INFO
> before releasing though, but I think this is reasonable.
>
> The other alternative is to include a separate log4j.cc.xml in CVS
> and point the ant task to use this configuration (via the -
> Dlog4j.configuration property) for CC runs.
>
> Which do people prefer?
> --
> 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 Jan 2007, at 03:37, Ryan Campbell wrote:
>
> > This is the problem:
> >
> > -rw-rw-r-- 1 cruisecontrol cruisecontrol 134848512 Jan 14 03:24
> > jbosscache.log
> > -rw-rw-r-- 1 cruisecontrol cruisecontrol 193673415 Jan 5 04:06
> > jbosscache.log.2007-01-05
> > -rw-rw-r-- 1 cruisecontrol cruisecontrol 114693620 Jan 6 02:48
> > jbosscache.log.2007-01-06
> > -rw-rw-r-- 1 cruisecontrol cruisecontrol 124116582 Jan 7 03:00
> > jbosscache.log.2007-01-07
> > -rw-rw-r-- 1 cruisecontrol cruisecontrol 222840969 Jan 8 07:24
> > jbosscache.log.2007-01-08
> > -rw-rw-r-- 1 cruisecontrol cruisecontrol 211811326 Jan 9 06:58
> > jbosscache.log.2007-01-09
> > -rw-rw-r-- 1 cruisecontrol cruisecontrol 186563185 Jan 10 05:51
> > jbosscache.log.2007-01-10
> > -rw-rw-r-- 1 cruisecontrol cruisecontrol 166926968 Jan 11 04:12
> > jbosscache.log.2007-01-11
> > -rw-rw-r-- 1 cruisecontrol cruisecontrol 465786953 Jan 13 12:02
> > jbosscache.log.2007-01-13
> >
> > This is being written to /tmp which is being filled up. It needs
> > to be
> > written to output/logs instead. Can you guys fix this?
> >
> > I've deleted the existing logs.
> >
> >> -----Original Message-----
> >> From: Vladimir Blagojevic
> >> Sent: Sunday, January 14, 2007 8:38 PM
> >> To: Ryan Campbell
> >> Cc: 'Manik Surtani'
> >> Subject: RE: Jboss Cache CC
> >>
> >> Ryan,
> >>
> >> Thanks. It worked for a day but looking at the latest logs it seems
> > like
> >> CC machine does not have disk space anymore.
> >>
> >> http://cruisecontrol.jboss.com/cc/artifacts/jboss-cache-
> >> testsuite/20070114011906/tests.log
> >>
> >>
> >> Cheers,
> >> Vladimir
> >>
> >>> -----Original Message-----
> >>> From: Ryan Campbell
> >>> Sent: Sunday, January 14, 2007 9:29 PM
> >>> To: Vladimir Blagojevic; QA
> >>> Cc: 'Manik Surtani'
> >>> Subject: RE: Jboss Cache CC
> >>>
> >>> Sorry for the delay, I believe this was due to a restart of
> >>> cruisecontrol.
> >>>
> >>>> -----Original Message-----
> >>>> From: Vladimir Blagojevic
> >>>> Sent: Friday, January 12, 2007 10:04 AM
> >>>> To: QA
> >>>> Cc: Manik Surtani
> >>>> Subject: Jboss Cache CC
> >>>>
> >>>> Hey guys,
> >>>>
> >>>> Would you please look at the reason why Jboss Cache
> >>> testsuite did not
> >>>> run on CC last night. Last time it ran was a day ago [1].
> >>> Since then
> >>>> we made some changes to a build process where a testsuite
> >>> now should
> >>>> run twice as long as usual - for about 180 minutes. It ran
> >>> ok locally on my machine.
> >>>>
> >>>> Much appreciated,
> >>>> Vladimir
> >>>>
> >>>>
> >>>>
> >>>> [1] http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-
> >>>> testsuite?log=log20070111023624
> >>>>
> >>>> -----Original Message-----
> >>>> From: Manik Surtani [mailto:manik@jboss.org]
> >>>> Sent: Friday, January 12, 2007 10:58 AM
> >>>> To: Vladimir Blagojevic
> >>>> Subject: Re: [jbosscache-dev] Finalizing JBCACHE-840
> >>>>
> >>>> Ping QA. They may have server issues
> >>>>
> >>>> --
> >>>> 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 15:20, Vladimir Blagojevic wrote:
> >>>>
> >>>>> 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?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>>
> >>>
18 years, 7 months
RE: [jbosscache-dev] Re: Jboss Cache CC
by Brian Stansberry
+1
jbosscache-dev-bounces(a)lists.jboss.org wrote:
> This one:
>
> "The other alternative is to include a separate log4j.cc.xml
> in CVS and point the ant task to use this configuration (via
> the - Dlog4j.configuration property) for CC runs."
>
> 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: 15 January 2007 11:34
> To: Ryan Campbell
> Cc: QA; jbosscache-dev(a)lists.jboss.org
> Subject: [jbosscache-dev] Re: Jboss Cache CC
>
> Man - this is crap that there is so much logging going on.
> By default we ship with log4j.xml configured to log at INFO
> level, and this is what is in CVS.
>
> Does anyone have any objections to my setting it to ERROR
> before checking it into CVS, so CC runs perform tests with
> ERROR level logging? In addition to taking up less disk
> space it would also mean much quicker runs.
>
> It would mean an additional release task of setting this to
> INFO before releasing though, but I think this is reasonable.
>
> The other alternative is to include a separate log4j.cc.xml
> in CVS and point the ant task to use this configuration (via
> the - Dlog4j.configuration property) for CC runs.
>
> Which do people prefer?
>
>> This is the problem:
>>
>> -rw-rw-r-- 1 cruisecontrol cruisecontrol 134848512 Jan 14 03:24
>> jbosscache.log
>> -rw-rw-r-- 1 cruisecontrol cruisecontrol 193673415 Jan 5 04:06
>> jbosscache.log.2007-01-05
>> -rw-rw-r-- 1 cruisecontrol cruisecontrol 114693620 Jan 6 02:48
>> jbosscache.log.2007-01-06
>> -rw-rw-r-- 1 cruisecontrol cruisecontrol 124116582 Jan 7 03:00
>> jbosscache.log.2007-01-07
>> -rw-rw-r-- 1 cruisecontrol cruisecontrol 222840969 Jan 8 07:24
>> jbosscache.log.2007-01-08
>> -rw-rw-r-- 1 cruisecontrol cruisecontrol 211811326 Jan 9 06:58
>> jbosscache.log.2007-01-09
>> -rw-rw-r-- 1 cruisecontrol cruisecontrol 186563185 Jan 10 05:51
>> jbosscache.log.2007-01-10
>> -rw-rw-r-- 1 cruisecontrol cruisecontrol 166926968 Jan 11 04:12
>> jbosscache.log.2007-01-11
>> -rw-rw-r-- 1 cruisecontrol cruisecontrol 465786953 Jan 13 12:02
>> jbosscache.log.2007-01-13
>>
>> This is being written to /tmp which is being filled up. It needs to
>> be written to output/logs instead. Can you guys fix this?
>>
>> I've deleted the existing logs.
>>
>>> -----Original Message-----
>>> From: Vladimir Blagojevic
>>> Sent: Sunday, January 14, 2007 8:38 PM
>>> To: Ryan Campbell
>>> Cc: 'Manik Surtani'
>>> Subject: RE: Jboss Cache CC
>>>
>>> Ryan,
>>>
>>> Thanks. It worked for a day but looking at the latest logs it seems
>>> like CC machine does not have disk space anymore.
>>>
>>> http://cruisecontrol.jboss.com/cc/artifacts/jboss-cache-
>>> testsuite/20070114011906/tests.log
>>>
>>>
>>> Cheers,
>>> Vladimir
>>>
>>>> -----Original Message-----
>>>> From: Ryan Campbell
>>>> Sent: Sunday, January 14, 2007 9:29 PM
>>>> To: Vladimir Blagojevic; QA
>>>> Cc: 'Manik Surtani'
>>>> Subject: RE: Jboss Cache CC
>>>>
>>>> Sorry for the delay, I believe this was due to a restart of
>>>> cruisecontrol.
>>>>
>>>>> -----Original Message-----
>>>>> From: Vladimir Blagojevic
>>>>> Sent: Friday, January 12, 2007 10:04 AM
>>>>> To: QA
>>>>> Cc: Manik Surtani
>>>>> Subject: Jboss Cache CC
>>>>>
>>>>> Hey guys,
>>>>>
>>>>> Would you please look at the reason why Jboss Cache testsuite did
>>>>> not run on CC last night. Last time it ran was a day ago [1].
>>>>> Since then we made some changes to a build process where a
>>>>> testsuite now should run twice as long as usual - for about 180
>>>>> minutes. It ran ok locally on my machine.
>>>>>
>>>>> Much appreciated,
>>>>> Vladimir
>>>>>
>>>>>
>>>>>
>>>>> [1] http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-
>>>>> testsuite?log=log20070111023624
>>>>>
>>>>> -----Original Message-----
>>>>> From: Manik Surtani [mailto:manik@jboss.org]
>>>>> Sent: Friday, January 12, 2007 10:58 AM
>>>>> To: Vladimir Blagojevic
>>>>> Subject: Re: [jbosscache-dev] Finalizing JBCACHE-840
>>>>>
>>>>> Ping QA. They may have server issues
>>>>>
>>>>> --
>>>>> 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 15:20, Vladimir Blagojevic wrote:
>>>>>
>>>>>> 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?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>>
>
> _______________________________________________
> jbosscache-dev mailing list
> jbosscache-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
>
> _______________________________________________
> 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
18 years, 7 months
RE: [jbosscache-dev] Re: Jboss Cache CC
by Galder Zamarreno
This one:
"The other alternative is to include a separate log4j.cc.xml in CVS and point the ant task to use this configuration (via the - Dlog4j.configuration property) for CC runs."
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: 15 January 2007 11:34
To: Ryan Campbell
Cc: QA; jbosscache-dev(a)lists.jboss.org
Subject: [jbosscache-dev] Re: Jboss Cache CC
Man - this is crap that there is so much logging going on. By
default we ship with log4j.xml configured to log at INFO level, and
this is what is in CVS.
Does anyone have any objections to my setting it to ERROR before
checking it into CVS, so CC runs perform tests with ERROR level
logging? In addition to taking up less disk space it would also mean
much quicker runs.
It would mean an additional release task of setting this to INFO
before releasing though, but I think this is reasonable.
The other alternative is to include a separate log4j.cc.xml in CVS
and point the ant task to use this configuration (via the -
Dlog4j.configuration property) for CC runs.
Which do people prefer?
--
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 Jan 2007, at 03:37, Ryan Campbell wrote:
> This is the problem:
>
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 134848512 Jan 14 03:24
> jbosscache.log
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 193673415 Jan 5 04:06
> jbosscache.log.2007-01-05
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 114693620 Jan 6 02:48
> jbosscache.log.2007-01-06
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 124116582 Jan 7 03:00
> jbosscache.log.2007-01-07
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 222840969 Jan 8 07:24
> jbosscache.log.2007-01-08
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 211811326 Jan 9 06:58
> jbosscache.log.2007-01-09
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 186563185 Jan 10 05:51
> jbosscache.log.2007-01-10
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 166926968 Jan 11 04:12
> jbosscache.log.2007-01-11
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 465786953 Jan 13 12:02
> jbosscache.log.2007-01-13
>
> This is being written to /tmp which is being filled up. It needs
> to be
> written to output/logs instead. Can you guys fix this?
>
> I've deleted the existing logs.
>
>> -----Original Message-----
>> From: Vladimir Blagojevic
>> Sent: Sunday, January 14, 2007 8:38 PM
>> To: Ryan Campbell
>> Cc: 'Manik Surtani'
>> Subject: RE: Jboss Cache CC
>>
>> Ryan,
>>
>> Thanks. It worked for a day but looking at the latest logs it seems
> like
>> CC machine does not have disk space anymore.
>>
>> http://cruisecontrol.jboss.com/cc/artifacts/jboss-cache-
>> testsuite/20070114011906/tests.log
>>
>>
>> Cheers,
>> Vladimir
>>
>>> -----Original Message-----
>>> From: Ryan Campbell
>>> Sent: Sunday, January 14, 2007 9:29 PM
>>> To: Vladimir Blagojevic; QA
>>> Cc: 'Manik Surtani'
>>> Subject: RE: Jboss Cache CC
>>>
>>> Sorry for the delay, I believe this was due to a restart of
>>> cruisecontrol.
>>>
>>>> -----Original Message-----
>>>> From: Vladimir Blagojevic
>>>> Sent: Friday, January 12, 2007 10:04 AM
>>>> To: QA
>>>> Cc: Manik Surtani
>>>> Subject: Jboss Cache CC
>>>>
>>>> Hey guys,
>>>>
>>>> Would you please look at the reason why Jboss Cache
>>> testsuite did not
>>>> run on CC last night. Last time it ran was a day ago [1].
>>> Since then
>>>> we made some changes to a build process where a testsuite
>>> now should
>>>> run twice as long as usual - for about 180 minutes. It ran
>>> ok locally on my machine.
>>>>
>>>> Much appreciated,
>>>> Vladimir
>>>>
>>>>
>>>>
>>>> [1] http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-
>>>> testsuite?log=log20070111023624
>>>>
>>>> -----Original Message-----
>>>> From: Manik Surtani [mailto:manik@jboss.org]
>>>> Sent: Friday, January 12, 2007 10:58 AM
>>>> To: Vladimir Blagojevic
>>>> Subject: Re: [jbosscache-dev] Finalizing JBCACHE-840
>>>>
>>>> Ping QA. They may have server issues
>>>>
>>>> --
>>>> 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 15:20, Vladimir Blagojevic wrote:
>>>>
>>>>> 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?
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>
>>>
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev
18 years, 7 months
Re: Jboss Cache CC
by Manik Surtani
Man - this is crap that there is so much logging going on. By
default we ship with log4j.xml configured to log at INFO level, and
this is what is in CVS.
Does anyone have any objections to my setting it to ERROR before
checking it into CVS, so CC runs perform tests with ERROR level
logging? In addition to taking up less disk space it would also mean
much quicker runs.
It would mean an additional release task of setting this to INFO
before releasing though, but I think this is reasonable.
The other alternative is to include a separate log4j.cc.xml in CVS
and point the ant task to use this configuration (via the -
Dlog4j.configuration property) for CC runs.
Which do people prefer?
--
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 Jan 2007, at 03:37, Ryan Campbell wrote:
> This is the problem:
>
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 134848512 Jan 14 03:24
> jbosscache.log
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 193673415 Jan 5 04:06
> jbosscache.log.2007-01-05
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 114693620 Jan 6 02:48
> jbosscache.log.2007-01-06
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 124116582 Jan 7 03:00
> jbosscache.log.2007-01-07
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 222840969 Jan 8 07:24
> jbosscache.log.2007-01-08
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 211811326 Jan 9 06:58
> jbosscache.log.2007-01-09
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 186563185 Jan 10 05:51
> jbosscache.log.2007-01-10
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 166926968 Jan 11 04:12
> jbosscache.log.2007-01-11
> -rw-rw-r-- 1 cruisecontrol cruisecontrol 465786953 Jan 13 12:02
> jbosscache.log.2007-01-13
>
> This is being written to /tmp which is being filled up. It needs
> to be
> written to output/logs instead. Can you guys fix this?
>
> I've deleted the existing logs.
>
>> -----Original Message-----
>> From: Vladimir Blagojevic
>> Sent: Sunday, January 14, 2007 8:38 PM
>> To: Ryan Campbell
>> Cc: 'Manik Surtani'
>> Subject: RE: Jboss Cache CC
>>
>> Ryan,
>>
>> Thanks. It worked for a day but looking at the latest logs it seems
> like
>> CC machine does not have disk space anymore.
>>
>> http://cruisecontrol.jboss.com/cc/artifacts/jboss-cache-
>> testsuite/20070114011906/tests.log
>>
>>
>> Cheers,
>> Vladimir
>>
>>> -----Original Message-----
>>> From: Ryan Campbell
>>> Sent: Sunday, January 14, 2007 9:29 PM
>>> To: Vladimir Blagojevic; QA
>>> Cc: 'Manik Surtani'
>>> Subject: RE: Jboss Cache CC
>>>
>>> Sorry for the delay, I believe this was due to a restart of
>>> cruisecontrol.
>>>
>>>> -----Original Message-----
>>>> From: Vladimir Blagojevic
>>>> Sent: Friday, January 12, 2007 10:04 AM
>>>> To: QA
>>>> Cc: Manik Surtani
>>>> Subject: Jboss Cache CC
>>>>
>>>> Hey guys,
>>>>
>>>> Would you please look at the reason why Jboss Cache
>>> testsuite did not
>>>> run on CC last night. Last time it ran was a day ago [1].
>>> Since then
>>>> we made some changes to a build process where a testsuite
>>> now should
>>>> run twice as long as usual - for about 180 minutes. It ran
>>> ok locally on my machine.
>>>>
>>>> Much appreciated,
>>>> Vladimir
>>>>
>>>>
>>>>
>>>> [1] http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-
>>>> testsuite?log=log20070111023624
>>>>
>>>> -----Original Message-----
>>>> From: Manik Surtani [mailto:manik@jboss.org]
>>>> Sent: Friday, January 12, 2007 10:58 AM
>>>> To: Vladimir Blagojevic
>>>> Subject: Re: [jbosscache-dev] Finalizing JBCACHE-840
>>>>
>>>> Ping QA. They may have server issues
>>>>
>>>> --
>>>> 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 15:20, Vladimir Blagojevic wrote:
>>>>
>>>>> 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?
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>
>>>
18 years, 7 months
JBC testsuite failed - no disk space?
by Vladimir Blagojevic
all-perftests:
stresstests:
[echo] Running stress tests using udp jgroups stack
[junit] Running org.jboss.cache.EvictionLocalStressTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 39.794
sec
[junit] Running org.jboss.cache.LocalStressTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 19.767
sec
[junit] Running org.jboss.cache.ReadWriteLockWithUpgradeStressTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 94.552
sec
[junit] Running org.jboss.cache.optimistic.OptimisticDeadlockTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3.506
sec
all-unittests:
Overriding previous definition of reference to junit.excludes
compile-cache:
[copy] Copying 43 files to
/services/cruisecontrol/work/checkout/jboss-cache-testsuite/output/etc
[copy] Copying 1 file to
/services/cruisecontrol/work/checkout/jboss-cache-testsuite/output/resou
rces
compile-pojocache-1:
aopc-pojocache:
BUILD FAILED
/services/cruisecontrol/work/checkout/jboss-cache-testsuite/build.xml:10
12: The following error occurred while executing this line:
/services/cruisecontrol/work/checkout/jboss-cache-testsuite/build.xml:24
1: java.lang.RuntimeException: java.io.IOException: No space left on
device
Total time: 123 minutes 16 seconds
18 years, 7 months
RE: [jbosscache-dev] Habanero BETAs
by Galder Zamarreno
Re: http://jira.jboss.com/jira/browse/JBCACHE-879, check last comment and commits with this JIRA issue.
Ok, I have committed the changes so that JDBCacheLoader uses VAM. I have commented previous serialization in case we need to rollback at some point.
I have added VersionAwareMarshallerPerfTest that replicates the issues I found profiling. Just try setting NUM_TIMES_PER_THREAD to 1000 and you'll see the difference.
We'll look at VAM and its impact in the performance tests once BETA1 is out.
I'll now concentrate in getting standalone JDBC connection pooling in for BETA1.
Have a nice weekend! I'm off to try out Nintendo's WII :D
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: Manik Surtani [mailto:manik@jboss.org]
Sent: 11 January 2007 18:52
To: Galder Zamarreno
Cc: jbosscache-dev(a)lists.jboss.org
Subject: Re: [jbosscache-dev] Habanero BETAs
On 11 Jan 2007, at 16:14, Galder Zamarreno wrote:
> 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?
If you reckon you have the time, then great.
>
> 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(a)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
18 years, 7 months