[JBoss-dev] jboss-remoting-testsuite-1.4 Build Timed Out

2006-02-25 Thread qa 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060225015715
BUILD TIMED OUTAnt Error Message: build timeoutDate of build: 02/25/2006 01:57:15Time to build: 




    Unit Tests: (0)    Total Errors and Failures: (0) 
 Modifications since last build: (first 50 of 0)

[JBoss-dev] jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors

2006-02-25 Thread qa 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060225035730
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 02/25/2006 03:57:30Time to build: 75 minutes 3 secondsLast changed: 12/31/2005 20:37:24Last log entry: JBREM-272:Added tests for (clientPool != null) and (threadPool != null) in cleanup.




    Unit Tests: (285)    Total Errors and Failures: (4)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(java_serialization)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(jboss_serialization)testStartorg.jboss.test.remoting.callback.pull.memory.nullstore.NullStoreCallbackTestCase(java_serialization)testStartorg.jboss.test.remoting.transport.multiplex.MultipleMultiplexTestCase(jboss_serialization) 
 Modifications since last build: (first 50 of 2053)1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutClientTest.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutServerTest.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/TimeoutTestCase.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/ComplexObject.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvocationHandler.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvokerTestClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestClient.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestServer.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestServerImpl.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TransporterTestCase.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/SSLInvokerConstants.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerClientTest.javaJBREM-235 - added new lgpl headers.1.8modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerTestCase.javaJBREM-235 - added new lgpl headers.1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerClientTest.javaJBREM-235 - added new lgpl headers.1.7modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-235 - added new lgpl headers.1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerTestCase.javaJBREM-235 - added new lgpl headers.1.2modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/test/SSLSimpleClient.javaJBREM-235 - added new lgpl headers.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/test/SSLSimpleServer.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/keepalive/TimeoutClientTest.javaJBREM-235 - added new lgpl headers.1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/timeout/keepalive/TimeoutServerTest.javaJBREM-235 - added new lgpl headers.1.7modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-270:Replaced "," with "&"1.6modifiedrsigalsrc/tests/org/jboss/test/remoting/transport/socket/ssl/custom/InvokerServerTest.javaJBREM-270:Replaced "," with "&"1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/web/WebInvokerTestClient.javaJBREM-253 - changed to use coyote connector by default instead of http server invoker.  Also adding many fixes so now only ssl related http tests are failing within the tests suite.1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/.truststoreJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years).1.6modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/socket/ssl/basic/InvokerServerTest.javaJBREM-214 - fixes for test failures (includes replacing keystore for ssl tests with one that will not expire for many years).1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/tr

[JBoss-dev] Re: Finalizing the Release of JBAS 3.2.8.SP1 & 4.0.4.GA - YourHelp is Needed

2006-02-25 Thread Mark Little 

Yes, we're still on target for a 4.0.4 plug-in for end of March.

Mark.


Scott M Stark wrote:

The new jta code is not fully cleaned and in a public repository. Need
to check with Mark/Kevin to see if this is still on target for a 4.0.4
release next month. 

  

-Original Message-
From: Adrian Brock 
Sent: Friday, February 24, 2006 8:48 AM

To: Dimitris Andreadis
Cc: jboss-development@lists.sourceforge.net; Architect 
Council; QA; Scott M Stark; Ivelin Ivanov
Subject: Re: Finalizing the Release of JBAS 3.2.8.SP1 & 
4.0.4.GA - YourHelp is Needed


The JCA, JTA and JMS work is pretty much done.

The outstanding stuff is all testing, some just to prove 
there is still no problem on bugs already fixed.


But this also includes the big one,
i.e. testing JMS inflow.

Incidently, I thought there would be some tasks raised for 
JBoss Transactions before the 4.0.4 release was finalized?


On Fri, 2006-02-17 at 12:31, Dimitris Andreadis wrote:


Hello everybody,

We have scheduled 2 releases of JBoss AS:

v3.2.8.SP1 for 03/Mar/06 (i.e. in 2 weeks time) v4.0.4.GA  for 
17/Mar/06 (i.e. in 4 weeks time)


3.2.8SP1 is needed to address a couple of issues with 3.2.8 
  
(JBossMQ 

-already fixed- and some extra interop scenarios with 4.0.2 
  
versions, 

plus whatever appears within the next 2 weeks), so it's 
  

under control.

However, getting 4.0.4.GA out the door is a big challenge 
  
as we have 

about 290 issues open! This list needs to be reduced to a 
  
manageable 


size of 90 or less issues to be solved until the release date.

We need EVERYONE to have a close look at the JBAS JIRA 
  
tasks related 


to his area of interest in order to:

1) Decide what features/bug/task are really important to go 
  
out with 


4.0.4.

Remember, 4.0.4RC1 is already out so new features shouldn't 
  
really be 

included between RC1 and GA, unless absolutely necessary, so we are 
talking about bug fixing mostly.


Please make use of the task Priorities to increase to 
  
"Critical" the 

priority of the tasks you want to get done for 4.0.4, and 
  
decrease to 


"Minor" those you don't.

2) Assign the issues to yourself or a member of your team; allocate 
time to work and close those critical issues within the 
  
next 3 WEEKS 


(to leave some time for testing).

If you don't have time to work on those tasks, keep them unassigned 
and either postpone those for 4.0.5.CR1, or if something is never 
going to get fixed just close it as such with an explanation.


If it still something important that you don't have time to work on 
and we must look at, RAISE the issue in the DEV list so we find 
someone to work on it.


Again, please raise any issues, especially integration ones 
  
EARLY in 


the DEV and QA lists.

Thanks for all your help in advance.

/Dimitris
  

--

Adrian Brock
Chief Scientist
JBoss Inc.
 







---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] Re: Finalizing the Release of JBAS 3.2.8.SP1 & 4.0.4.GA - YourHelpis Needed

2006-02-25 Thread Mark Little 
Yes. The intention is for 2 plugins for 4.0.4: one to cover the purely 
local JTA implementation (which becomes the default in 5.0) and one to 
cover JTS/WS-T (which will remain as a separate plugin in 5.0).


Mark.


Andy Miller wrote:
JBoss Transactions should stay an optional plug-in for the 4.0.x 
series.  It should only be integrated into JBoss AS 5.0.x.


Andy

On Fri, 2006-02-24 at 14:39 -0600, Dimitris Andreadis wrote:

Isn't the new Transaction Manager supposed to be an optional plug-in
offered seperately, at this stage?

This is what I gathered from the integration plan:

http://jira.jboss.com/jira/browse/JBTM-13

I can't find any integration tasks in JIRA.

> -Original Message-
> From: Scott M Stark 
> Sent: 24 February, 2006 21:43

> To: Adrian Brock; Dimitris Andreadis
> Cc: jboss-development@lists.sourceforge.net ; Architect 
> Council; QA; Ivelin Ivanov
> Subject: RE: Finalizing the Release of JBAS 3.2.8.SP1 & 
> 4.0.4.GA - YourHelp is Needed
> 
> The new jta code is not fully cleaned and in a public 
> repository. Need to check with Mark/Kevin to see if this is 
> still on target for a 4.0.4 release next month. 
> 
> > -Original Message-

> > From: Adrian Brock
> > Sent: Friday, February 24, 2006 8:48 AM
> > To: Dimitris Andreadis
> > Cc: jboss-development@lists.sourceforge.net ; Architect Council; QA; 
> > Scott M Stark; Ivelin Ivanov
> > Subject: Re: Finalizing the Release of JBAS 3.2.8.SP1 & 4.0.4.GA - 
> > YourHelp is Needed
> > 
> > The JCA, JTA and JMS work is pretty much done.
> > 
> > The outstanding stuff is all testing, some just to prove there is 
> > still no problem on bugs already fixed.
> > 
> > But this also includes the big one,

> > i.e. testing JMS inflow.
> > 
> > Incidently, I thought there would be some tasks raised for JBoss 
> > Transactions before the 4.0.4 release was finalized?
> > 
> > On Fri, 2006-02-17 at 12:31, Dimitris Andreadis wrote:

> > > Hello everybody,
> > > 
> > > We have scheduled 2 releases of JBoss AS:
> > > 
> > > v3.2.8.SP1 for 03/Mar/06 (i.e. in 2 weeks time) v4.0.4.GA  for

> > > 17/Mar/06 (i.e. in 4 weeks time)
> > > 
> > > 3.2.8SP1 is needed to address a couple of issues with 3.2.8

> > (JBossMQ
> > > -already fixed- and some extra interop scenarios with 4.0.2
> > versions,
> > > plus whatever appears within the next 2 weeks), so it's
> > under control.
> > > 
> > > However, getting 4.0.4.GA out the door is a big challenge

> > as we have
> > > about 290 issues open! This list needs to be reduced to a
> > manageable
> > > size of 90 or less issues to be solved until the release date.
> > > 
> > > We need EVERYONE to have a close look at the JBAS JIRA

> > tasks related
> > > to his area of interest in order to:
> > > 
> > > 1) Decide what features/bug/task are really important to go

> > out with
> > > 4.0.4.
> > > 
> > > Remember, 4.0.4RC1 is already out so new features shouldn't

> > really be
> > > included between RC1 and GA, unless absolutely necessary, 
> so we are 
> > > talking about bug fixing mostly.
> > > 
> > > Please make use of the task Priorities to increase to

> > "Critical" the
> > > priority of the tasks you want to get done for 4.0.4, and
> > decrease to
> > > "Minor" those you don't.
> > > 
> > > 2) Assign the issues to yourself or a member of your 
> team; allocate 
> > > time to work and close those critical issues within the

> > next 3 WEEKS
> > > (to leave some time for testing).
> > > 
> > > If you don't have time to work on those tasks, keep them 
> unassigned 
> > > and either postpone those for 4.0.5.CR1, or if something is never 
> > > going to get fixed just close it as such with an explanation.
> > > 
> > > If it still something important that you don't have time 
> to work on 
> > > and we must look at, RAISE the issue in the DEV list so we find 
> > > someone to work on it.
> > > 
> > > Again, please raise any issues, especially integration ones

> > EARLY in
> > > the DEV and QA lists.
> > > 
> > > Thanks for all your help in advance.
> > > 
> > > /Dimitris

> > --
> > 
> > Adrian Brock
> > Chief Scientist
> > JBoss Inc.
> > 
> > 
> > 




---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] Re: Finalizing the Release of JBAS 3.2.8.SP1 & 4.0.4.GA - YourHelp is Needed

2006-02-25 Thread Mark Little 
So it depends what you expect to see. 
http://jira.jboss.com/jira/browse/JBTM-2 is one example of the tasks 
left. You need to remember that the main integration effort was done 
months ago in Arjuna, who've been selling the integrated components for 
a few years. What we're doing here is a rebadge to JBoss Transactions 
and 4.0.4. Unless there are major differences between 4.0.2 and 4.0.4 
that directly affect TS then these tasks should be sufficient to cover 
the integration effort.


Mark.


Dimitris Andreadis wrote:

Isn't the new Transaction Manager supposed to be an optional plug-in
offered seperately, at this stage?

This is what I gathered from the integration plan:

http://jira.jboss.com/jira/browse/JBTM-13

I can't find any integration tasks in JIRA.

  

-Original Message-
From: Scott M Stark 
Sent: 24 February, 2006 21:43

To: Adrian Brock; Dimitris Andreadis
Cc: jboss-development@lists.sourceforge.net; Architect 
Council; QA; Ivelin Ivanov
Subject: RE: Finalizing the Release of JBAS 3.2.8.SP1 & 
4.0.4.GA - YourHelp is Needed


The new jta code is not fully cleaned and in a public 
repository. Need to check with Mark/Kevin to see if this is 
still on target for a 4.0.4 release next month. 



-Original Message-
From: Adrian Brock
Sent: Friday, February 24, 2006 8:48 AM
To: Dimitris Andreadis
Cc: jboss-development@lists.sourceforge.net; Architect Council; QA; 
Scott M Stark; Ivelin Ivanov
Subject: Re: Finalizing the Release of JBAS 3.2.8.SP1 & 4.0.4.GA - 
YourHelp is Needed


The JCA, JTA and JMS work is pretty much done.

The outstanding stuff is all testing, some just to prove there is 
still no problem on bugs already fixed.


But this also includes the big one,
i.e. testing JMS inflow.

Incidently, I thought there would be some tasks raised for JBoss 
Transactions before the 4.0.4 release was finalized?


On Fri, 2006-02-17 at 12:31, Dimitris Andreadis wrote:
  

Hello everybody,

We have scheduled 2 releases of JBoss AS:

v3.2.8.SP1 for 03/Mar/06 (i.e. in 2 weeks time) v4.0.4.GA  for
17/Mar/06 (i.e. in 4 weeks time)

3.2.8SP1 is needed to address a couple of issues with 3.2.8


(JBossMQ
  

-already fixed- and some extra interop scenarios with 4.0.2


versions,
  

plus whatever appears within the next 2 weeks), so it's


under control.
  

However, getting 4.0.4.GA out the door is a big challenge


as we have
  

about 290 issues open! This list needs to be reduced to a


manageable
  

size of 90 or less issues to be solved until the release date.

We need EVERYONE to have a close look at the JBAS JIRA


tasks related
  

to his area of interest in order to:

1) Decide what features/bug/task are really important to go


out with
  

4.0.4.

Remember, 4.0.4RC1 is already out so new features shouldn't


really be
  
included between RC1 and GA, unless absolutely necessary, 

so we are 


talking about bug fixing mostly.

Please make use of the task Priorities to increase to


"Critical" the
  

priority of the tasks you want to get done for 4.0.4, and


decrease to
  

"Minor" those you don't.

2) Assign the issues to yourself or a member of your 

team; allocate 


time to work and close those critical issues within the


next 3 WEEKS
  

(to leave some time for testing).

If you don't have time to work on those tasks, keep them 

unassigned 

and either postpone those for 4.0.5.CR1, or if something is never 
going to get fixed just close it as such with an explanation.


If it still something important that you don't have time 

to work on 

and we must look at, RAISE the issue in the DEV list so we find 
someone to work on it.


Again, please raise any issues, especially integration ones


EARLY in
  

the DEV and QA lists.

Thanks for all your help in advance.

/Dimitris


--

Adrian Brock
Chief Scientist
JBoss Inc.



  



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: Finalizing the Release of JBAS 3.2.8.SP1 & 4.0.4.GA - YourHelp is Needed

2006-02-25 Thread Scott M Stark 
At a minimum there needs to be a placeholder issue in the 
http://jira.jboss.com/jira/browse/JBAS project that links to the JBTM
issues that need to be completed. Otherwise 4.0.4.GA can go out without
anyone actually testing the integration. 

Beyond that, is this going to be integrated into the installer? If it
is, then we also need an integration test in the jbossas testsuite.

> -Original Message-
> From: Mark Little [mailto:[EMAIL PROTECTED] 
> Sent: Saturday, February 25, 2006 5:19 AM
> To: Dimitris Andreadis
> Cc: Scott M Stark; Adrian Brock; 
> jboss-development@lists.sourceforge.net; Architect Council; 
> QA; Ivelin Ivanov
> Subject: Re: Finalizing the Release of JBAS 3.2.8.SP1 & 
> 4.0.4.GA - YourHelp is Needed
> 
> So it depends what you expect to see. 
> http://jira.jboss.com/jira/browse/JBTM-2 is one example of 
> the tasks left. You need to remember that the main 
> integration effort was done months ago in Arjuna, who've been 
> selling the integrated components for a few years. What we're 
> doing here is a rebadge to JBoss Transactions and 4.0.4. 
> Unless there are major differences between 4.0.2 and 4.0.4 
> that directly affect TS then these tasks should be sufficient 
> to cover the integration effort.
> 
> Mark.
> 
> 
> Dimitris Andreadis wrote:
> > Isn't the new Transaction Manager supposed to be an optional plug-in
> > offered seperately, at this stage?
> >
> > This is what I gathered from the integration plan:
> >
> > http://jira.jboss.com/jira/browse/JBTM-13
> >
> > I can't find any integration tasks in JIRA.
> >
> >   
> >> -Original Message-
> >> From: Scott M Stark 
> >> Sent: 24 February, 2006 21:43
> >> To: Adrian Brock; Dimitris Andreadis
> >> Cc: jboss-development@lists.sourceforge.net; Architect 
> >> Council; QA; Ivelin Ivanov
> >> Subject: RE: Finalizing the Release of JBAS 3.2.8.SP1 & 
> >> 4.0.4.GA - YourHelp is Needed
> >>
> >> The new jta code is not fully cleaned and in a public 
> >> repository. Need to check with Mark/Kevin to see if this is 
> >> still on target for a 4.0.4 release next month. 
> >>
> >> 
> >>> -Original Message-
> >>> From: Adrian Brock
> >>> Sent: Friday, February 24, 2006 8:48 AM
> >>> To: Dimitris Andreadis
> >>> Cc: jboss-development@lists.sourceforge.net; Architect 
> Council; QA; 
> >>> Scott M Stark; Ivelin Ivanov
> >>> Subject: Re: Finalizing the Release of JBAS 3.2.8.SP1 & 
> 4.0.4.GA - 
> >>> YourHelp is Needed
> >>>
> >>> The JCA, JTA and JMS work is pretty much done.
> >>>
> >>> The outstanding stuff is all testing, some just to prove there is 
> >>> still no problem on bugs already fixed.
> >>>
> >>> But this also includes the big one,
> >>> i.e. testing JMS inflow.
> >>>
> >>> Incidently, I thought there would be some tasks raised for JBoss 
> >>> Transactions before the 4.0.4 release was finalized?
> >>>
> >>> On Fri, 2006-02-17 at 12:31, Dimitris Andreadis wrote:
> >>>   
>  Hello everybody,
> 
>  We have scheduled 2 releases of JBoss AS:
> 
>  v3.2.8.SP1 for 03/Mar/06 (i.e. in 2 weeks time) v4.0.4.GA  for
>  17/Mar/06 (i.e. in 4 weeks time)
> 
>  3.2.8SP1 is needed to address a couple of issues with 3.2.8
>  
> >>> (JBossMQ
> >>>   
>  -already fixed- and some extra interop scenarios with 4.0.2
>  
> >>> versions,
> >>>   
>  plus whatever appears within the next 2 weeks), so it's
>  
> >>> under control.
> >>>   
>  However, getting 4.0.4.GA out the door is a big challenge
>  
> >>> as we have
> >>>   
>  about 290 issues open! This list needs to be reduced to a
>  
> >>> manageable
> >>>   
>  size of 90 or less issues to be solved until the release date.
> 
>  We need EVERYONE to have a close look at the JBAS JIRA
>  
> >>> tasks related
> >>>   
>  to his area of interest in order to:
> 
>  1) Decide what features/bug/task are really important to go
>  
> >>> out with
> >>>   
>  4.0.4.
> 
>  Remember, 4.0.4RC1 is already out so new features shouldn't
>  
> >>> really be
> >>>   
>  included between RC1 and GA, unless absolutely necessary, 
>  
> >> so we are 
> >> 
>  talking about bug fixing mostly.
> 
>  Please make use of the task Priorities to increase to
>  
> >>> "Critical" the
> >>>   
>  priority of the tasks you want to get done for 4.0.4, and
>  
> >>> decrease to
> >>>   
>  "Minor" those you don't.
> 
>  2) Assign the issues to yourself or a member of your 
>  
> >> team; allocate 
> >> 
>  time to work and close those critical issues within the
>  
> >>> next 3 WEEKS
> >>>   
>  (to leave some time for testing).
> 
>  If you don't have time to work on those tasks, keep them 
>  
> >> unassigned 
> >> 
>  and either postpone tho

[JBoss-dev] jbossretro-testsuite Build Completed With Testsuite Errors

2006-02-25 Thread qa 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jbossretro-testsuite?log=log20060225123519
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jbossretro-testsuite.xml:75: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 02/25/2006 12:35:19Time to build: 7 minutes 9 secondsLast changed: 02/22/2006 11:11:01Last log entry: Provide more information than "UnexpectedException"




    Unit Tests: (1351)    Total Errors and Failures: (119)testIsHeldExclusivelyorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAcquireorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestTryAcquireorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttesthasQueuedThreadsorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestIsQueuedNPEorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestIsQueuedorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestGetFirstQueuedThreadorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestHasContendedorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestGetQueuedThreadsorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestGetExclusiveQueuedThreadsorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestGetSharedQueuedThreadsorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestInterruptedException2org.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestTryAcquireWhenSyncedorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAcquireNanos_Timeoutorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestGetStateorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAcquireInterruptibly1org.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAcquireInterruptibly2org.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestOwnsorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAwait_IllegalMonitororg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestSignal_IllegalMonitororg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAwaitNanos_Timeoutorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAwait_Timeoutorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAwaitUntil_Timeoutorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAwaitorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestHasWaitersNPEorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestGetWaitQueueLengthNPEorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestGetWaitingThreadsNPEorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestHasWaitersIAEorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestHasWaitersIMSEorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestGetWaitQueueLengthIAEorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestGetWaitQueueLengthIMSEorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestGetWaitingThreadsIAEorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestGetWaitingThreadsIMSEorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestHasWaitersorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestGetWaitQueueLengthorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestGetWaitingThreadsorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAwaitUninterruptiblyorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAwait_Interruptorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAwaitNanos_Interruptorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAwaitUntil_Interruptorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestSignalAllorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestToStringorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestSerializationorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestGetStateWithReleaseSharedorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestReleaseSharedorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAcquireSharedInterruptiblyorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAsquireSharedTimedorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAcquireSharedInterruptibly_InterruptedExceptionorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAcquireSharedNanos_InterruptedExceptionorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestAcquireSharedNanos_Timeoutorg.jboss.test.concurrent.AbstractQueuedSynchronizerTesttestParkorg.jboss.test.concurrent.LockSupportTesttestPark2org.jboss.test.concurrent.LockSupportTestunknownorg.jboss.test.concurrent.ReentrantLockTesttestConstructororg.jboss.test.concurrent.ReentrantReadWriteLockTesttestLockorg.jboss.test.concurrent.ReentrantReadWriteLockTesttestFairLockorg.jboss.test.concurrent.ReentrantReadWriteLockTesttestGetWriteHoldCountorg.jboss.test.concurrent.ReentrantReadWriteLockTesttestUnlock_IllegalMonitorSta

[JBoss-dev] concurrent-testsuite Build Completed With Testsuite Errors

2006-02-25 Thread qa 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/concurrent-testsuite?log=log20060225124236
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-concurrent-testsuite.xml:73: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 02/25/2006 12:42:36Time to build: 7 minutes 21 secondsLast changed: 02/21/2006 05:34:26Last log entry: Build concurrent with JDK1.4




    Unit Tests: (1707)    Total Errors and Failures: (1)testPrivilegedThreadFactory.ExecutorsTest 
 Modifications since last build: (first 50 of 1)1.3modifiedadrian/.classpathBuild concurrent with JDK1.4

[JBoss-dev] jboss-portal-2.4-testsuite Build Completed With Testsuite Errors

2006-02-25 Thread qa 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.4-testsuite?log=log20060225112357
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:67: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:93: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:204: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 02/25/2006 11:23:57Time to build: 2 minutes 29 secondsLast changed: 02/24/2006 19:50:54Last log entry: added LayoutMetaData




    Unit Tests: (84)    Total Errors and Failures: (0)All Tests Passed 
 Modifications since last build: (first 50 of 576)1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/MarkupType.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/MissingParametersFault.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/ModelDescription.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/ModelTypes.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/ModifyRegistration.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/NamedString.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/Online.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/OperationFailedFault.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/PerformBlockingInteraction.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/PersonName.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/PortletContext.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core classes from WSDL with run-wscompile.sh.- Adapted build.xml to run tests (still needs work).- Adapted classes to new core classes.- Removed unused wsrpcore compiled classes.1.2deletedclaprunwsrp/src/resources/wsrpcore/classes/org/jboss/portal/wsrp/core/PortletDescription.class- Adapted run-wscompile.sh according to JBWS-717.- Re-generated core

[JBoss-dev] jboss-3.2-testsuite Build Completed With Testsuite Errors

2006-02-25 Thread qa 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060225190735
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:26: Build Successful - Tests completed with errors or failures.Date of build: 02/25/2006 19:07:35Time to build: 49 minutes 22 secondsLast changed: 02/24/2006 17:52:42Last log entry: fix the testsuite build - use the new version naming conventions




    Unit Tests: (1848)    Total Errors and Failures: (5)testNotificationWithBadListenerorg.jboss.test.jmx.test.JMXInvokerUnitTestCasetestClientLoginorg.jboss.test.security.test.LoginModulesUnitTestCasetestJCACallerIdentityorg.jboss.test.security.test.LoginModulesUnitTestCasetestClientLoginorg.jboss.test.security.test.XMLLoginModulesUnitTestCasetestJCACallerIdentityorg.jboss.test.security.test.XMLLoginModulesUnitTestCase 
 Modifications since last build: (first 50 of 35)1.1.2.17modifieddimitristestsuite/imports/server-config.xmlfix the testsuite build - use the new version naming conventions1.32.2.10modifieddimitrisserver/src/main/org/jboss/ejb/plugins/SecurityInterceptor.javaJBAS-2857, avoid NPE when calling org.jboss.ejb.Container.getMethodPermission with a null Method1.8.2.5modifiedadrianmessaging/src/main/org/jboss/mq/SpyBytesMessage.javaPort JBAS-2641 from jboss41.1.4.7modifiedadriantestsuite/src/main/org/jboss/test/jbossmq/test/LargeMessageUnitTestCase.javaPort JBAS-2641 from jboss41.1.2.17modifieddimitristools/etc/buildmagic/version-info.xmlJBAS-2843, Update to use the new release convention names1.1.2.42modifieddimitristools/etc/buildmagic/buildmagic.entJBAS-2843, Update to use the new release convention names1.1.4.4modifiedadrianconnector/src/main/org/jboss/resource/connectionmanager/JBossLocalXAException.java[JBAS-2807] - Add the XAException error code to the JBossLocalXAExceptions thrown by the local resource wrapper.1.2.2.31modifiedadrianconnector/src/main/org/jboss/resource/connectionmanager/TxConnectionManager.java[JBAS-2807] - Add the XAException error code to the JBossLocalXAExceptions thrown by the local resource wrapper.1.3.2.5modifieddimitrisbuild/build-release.xmlfix the module name1.3.2.4modifieddimitrisbuild/build-release.xmlJBAS-2843, Update to use the new release convention names1.160.2.190modifieddimitrisbuild/build.xmlJBAS-2843, Update to use the new release convention names1.1.2.41modifieddimitristools/etc/buildmagic/buildmagic.entJBAS-2843, Update to use the new release convention names1.1.2.16modifieddimitristools/etc/buildmagic/version-info.xmlJBAS-2843, Update to use the new release convention names1.1.2.8modifiedadrianmessaging/src/main/org/jboss/mq/server/BasicQueueParameters.java[JBAS-2838] - Set the day count to zero by default1.2.8.4modifiedadrianmessaging/src/main/org/jboss/mq/TransactionRequest.javaBackport JBAS-2822 from head.1.39.2.58modifieddimitrisserver/src/etc/conf/default/standardjbosscmp-jdbc.xmlJBAS-1671, alias-max-length DB2 typemapping from 32 to 181.5.2.17modifieddimitrisvaria/src/resources/services/binding/sample-bindings.xmltidy up the header1.165.2.202modifiedcsuconictestsuite/build.xmlAdding 3.2.8 on the matrix testsuite list1.8.2.9modifieddimitrismanagement/src/main/org/jboss/management/j2ee/MBean.javaJBAS-2082, avoid creating a dynamic proxy for a single attribute read, reduce the trace verboseness of the caught exception when cannot find an MBean's "State" attribute1.12.2.14modifieddimitrisnaming/src/main/org/jnp/server/Main.javaJBAS-1806, call custom RMIClientSocketFactory.setBindAddress() if method is provided (+ tidy up the MBean interface, and synch across branches)1.6.2.4modifieddimitrisnaming/src/main/org/jnp/server/MainMBean.javaJBAS-1806, call custom RMIClientSocketFactory.setBindAddress() if method is provided (+ tidy up the MBean interface, and synch across branches)1.2.2.7modifieddimitrisvaria/src/main/org/jboss/varia/scheduler/ScheduleManager.javaJBAS-2797, fix wrong way for retrieving Hashtable mSchedules values1.1.2.19modifiedbstansberrytomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.java[JBAS-2792] Avoid NPE; don't assign the result of loadSession to local variable1.2.2.6modifieddimitrisvaria/src/main/org/jboss/varia/scheduler/ScheduleManager.javatidy up the ScheduleManager, synch across branches1.2.4.3modifieddimitrisvaria/src/main/org/jboss/varia/scheduler/ScheduleManagerMBean.javatidy up the ScheduleManager, synch across branches1.2.2.4modifiedcsuconicserver/src/main/org/jboss/jmx/adaptor/rmi/RMIAdaptor.javaJBAS-2803 - Proposed fix1.3.2.6modifiedcsuconicserver/src/main/org/jboss/jmx/adaptor/rmi/RMIAdaptorImpl.javaJBAS-2803 - Proposed fix1.9.2.3modifiedcsuconicserver/src/main/org/jboss/jmx/connector/rmi/RMIConnectorImpl.javaJBAS-2803 - Proposed fix1

[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors

2006-02-25 Thread qa 

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060225215817
TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 02/25/2006 21:58:17Time to build: 34 minutes 49 secondsLast changed: 12/28/2005 10:48:11Last log entry: Add the 1.2.4SP1 changelog notes.




    Unit Tests: (1377)    Total Errors and Failures: (8)testSimplifiedorg.jboss.cache.aop.integrated.PropagationManagerlAopTesttestPropagationorg.jboss.cache.aop.integrated.PropagationManagerlAopTesttestSimplifiedorg.jboss.cache.aop.integrated.ReplicatedPropagationManagerlAopTesttestPropagationorg.jboss.cache.aop.integrated.ReplicatedPropagationManagerlAopTesttestInvalidationMgmtorg.jboss.cache.mgmt.InvalidationTesttestSharedCacheLoadingWithReplicationorg.jboss.cache.optimistic.OptimisticWithCacheLoaderTesttestCheckReplInstanceorg.jboss.cache.aop.ReplicatedObjectGraphAopTesttestCollectionWithCacheLoaderorg.jboss.cache.aop.loader.FileCacheLoaderAopTest 
 Modifications since last build: (first 50 of 1825)1.3modifiedmsurtanitests/perf/org/jboss/cache/loader/CacheLoaderPerfTest.javaFixes rating to JBCACHE-118 - optimising cache loader functionality.1.2modifiedmsurtanitests/perf/org/jboss/cache/loader/CacheLoaderPerfTest.javaAdded a perf test to measure performance on basic operations with a cache loader1.1addedmsurtanitests/perf/org/jboss/cache/loader/CacheLoaderPerfTest.javaAdded a perf test to measure performance on basic operations with a cache loader1.2modifieddhuangtests/stress/org/jboss/cache/EvictionLocalStressTest.javaEviction policy refactoring to support 1 Policy per Region.Refactoring of Eviction Policies to allow for easier user extension.Introduce EvictionQueue and EvictionConfiguration interfaces.New Eviction Policies for MRU and LFU.Allow configuration of EvictionPolicies at runtime.References JIRA tasks:JBCACHE-314JBCACHE-313JBCACHE-312JBCACHE-286JBCACHE-225JBCACHE-2131.2modifieddhuangtests/stress/org/jboss/cache/LocalStressTest.javaEviction policy refactoring to support 1 Policy per Region.Refactoring of Eviction Policies to allow for easier user extension.Introduce EvictionQueue and EvictionConfiguration interfaces.New Eviction Policies for MRU and LFU.Allow configuration of EvictionPolicies at runtime.References JIRA tasks:JBCACHE-314JBCACHE-313JBCACHE-312JBCACHE-286JBCACHE-225JBCACHE-2131.1addedmsurtanitests/perf/org/jboss/cache/benchmark/tests/ReplAsyncPessRead50JRunitTest.javaAdded replicated tests1.1addedmsurtanitests/perf/org/jboss/cache/benchmark/tests/ReplAsyncPessRead75JRunitTest.javaAdded replicated tests1.1addedmsurtanitests/perf/org/jboss/cache/benchmark/tests/ReplAsyncPessRead90JRunitTest.javaAdded replicated tests1.1addedmsurtanitests/perf/org/jboss/cache/benchmark/tests/ReplSyncPessRead50JRunitTest.javaAdded replicated tests1.1addedmsurtanitests/perf/org/jboss/cache/benchmark/tests/ReplSyncPessRead75JRunitTest.javaAdded replicated tests1.1addedmsurtanitests/perf/org/jboss/cache/benchmark/tests/ReplSyncPessRead90JRunitTest.javaAdded replicated tests1.1addedmsurtanitests/perf/org/jboss/cache/benchmark/tests/LocalPessIsoRRRead90JRunitTest.javaAdded more tests1.1addedbwangtests/scripts/profile.shnew1.1addedhmeshatests/perf/org/jboss/cache/loader/JDBCCacheLoaderPerfTest.javaJBCACHE-330 first draft JDBCCacheLoader performance test case1.2modifiedbwangtests-50/functional/org/jboss/cache/aop/test/TestNode.javaMissed the annotation.1.1addedbwangtests-50/functional/org/jboss/cache/aop/test/Address.javaJBCACHE-175 JDK50 annotation support1.1addedbwangtests-50/functional/org/jboss/cache/aop/test/CacheObject.javaJBCACHE-175 JDK50 annotation support1.1addedbwangtests-50/functional/org/jboss/cache/aop/test/IdObject.javaJBCACHE-175 JDK50 annotation support1.1addedbwangtests-50/functional/org/jboss/cache/aop/test/Link.javaJBCACHE-175 JDK50 annotation support1.1addedbwangtests-50/functional/org/jboss/cache/aop/test/NetworkAdmin.javaJBCACHE-175 JDK50 annotation support1.1addedbwangtests-50/functional/org/jboss/cache/aop/test/NetworkDomain.javaJBCACHE-175 JDK50 annotation support1.1addedbwangtests-50/functional/org/jboss/cache/aop/test/NetworkElement.javaJBCACHE-175 JDK50 annotation support1.1addedbwangtests-50/functional/org/jboss/cache/aop/test/NetworkNode.javaJBCACHE-175 JDK50 annotation support1.1addedbwangtests-50/functional/org/jboss/cache/aop/test/NodeManager.javaJBCACHE-175 JDK50 annotation support1.1addedbwangtests-50/functional/org/jboss/cache/aop/test/Person.javaJBCACHE-175 JDK50 annotation support1.1addedbwangtests-50/functional/org/jboss/cache/aop/test/SerializedAddress.javaJBCACHE-175 JDK50 annotation support1.1addedbwangtests-50/functional/org/jbo