[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-04-05 Thread Rajesh Rajasekaran 
The minimal server log shows a time gap of 60 sec before starting the
shutdown, and the all config starts before this is complete.

http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite/20060405
072327/build/output/jboss-4.0.4.GA/server/minimal/log/server.log



2006-04-05 07:44:00,223 DEBUG [org.jboss.system.ServiceController]
stopping service: jboss.deployment:flavor=URL,type=DeploymentScanner
2006-04-05 07:44:00,223 DEBUG [org.jboss.system.ServiceController]
stopping dependent services for:
jboss.deployment:flavor=URL,type=DeploymentScanner dependent services
are: []
2006-04-05 07:44:00,223 DEBUG
[org.jboss.deployment.scanner.URLDeploymentScanner] Stopping
jboss.deployment:flavor=URL,type=DeploymentScanner
2006-04-05 07:44:00,223 DEBUG
[org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread]
Notified that enabled: false
2006-04-05 07:45:00,234 DEBUG
[org.jboss.deployment.scanner.URLDeploymentScanner] Stopped
jboss.deployment:flavor=URL,type=DeploymentScanner
2006-04-05 07:45:00,234 DEBUG [org.jboss.deployment.SARDeployer]
stopping mbean jboss:service=Naming
2006-04-05 07:45:00,235 DEBUG [org.jboss.system.ServiceController]
stopping service: jboss:service=Naming
2006-04-05 07:45:00,235 DEBUG [org.jboss.system.ServiceController]
stopping dependent services for: jboss:service=Naming dependent services
are: []
2006-04-05 07:45:00,235 DEBUG [org.jboss.naming.NamingService] Stopping
jboss:service=Naming
2006-04-05 07:45:00,236 DEBUG [org.jboss.naming.NamingService] JNP
server stopped



-Original Message-
From: Adrian Brock 
Sent: Wednesday, April 05, 2006 11:25 AM
To: Rajesh Rajasekaran
Cc: QA; Alexey Loubyansky; Amit Bhayani; Anil Saldhana; Bela Ban; Bill
Burke; Brian Stansberry; Clebert Suconic; Dimitris Andreadis; Emmanuel
Bernard; [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net;
[EMAIL PROTECTED]; Kabir Khan; Ryan Campbell; Ruel Loehr; Scott M
Stark; Thomas Diesler; Tom Elrod
Subject: RE: jboss-4.0-testsuite Build Failed

JBAS-3050 only waits if the deployment scanner's thread is busy
deploying stuff. Something that clearly isn't the case here.

At most it is going to wait 5 seconds if you are unlucky and
the background thread just went to sleep.

I don't see any problem shutting down minimal when done
manually.

17:20:52,846 INFO  [Server] JBoss (MX MicroKernel) [4.0.4.GA (build:
CVSTag=JBoss_4_0_4_GA date=200604051409)] Started in 5s:879ms
17:20:54,768 INFO  [Server] Runtime shutdown hook called, forceHalt:
true
17:20:54,769 INFO  [Server] JBoss SHUTDOWN: Undeploying all packages
17:20:57,878 INFO  [Server] Shutdown complete


On Wed, 2006-04-05 at 10:58 -0500, Rajesh Rajasekaran wrote:
 The all config fails to start because port 1098 is still in use by
the
 minimal configuration which started up earlier. 
 The minimal waits for 60 secs to completely shut down before which the
 all config starts. I guess this change is related to the following
 issue.
 http://jira.jboss.com/jira/browse/JBAS-3050
 
 This can be verfied by running the testsuite manually. ant tests
from
 the testsuite folder.
 This can be avoided by allowing the testsuite to wait for 60 secs or
 more before different configurations start up.
 
 Thanks
 Rajesh
 
 -Original Message-
 From: Adrian Brock 
 Sent: Wednesday, April 05, 2006 6:51 AM
 To: QA
 Cc: Alexey Loubyansky; Amit Bhayani; Anil Saldhana; Bela Ban; Bill
 Burke; Brian Stansberry; Clebert Suconic; Dimitris Andreadis; Emmanuel
 Bernard; [EMAIL PROTECTED];
jboss-development@lists.sourceforge.net;
 [EMAIL PROTECTED]; Kabir Khan; Rajesh Rajasekaran; Ryan Campbell;
 Ruel Loehr; Scott M Stark; Thomas Diesler; Tom Elrod
 Subject: Re: jboss-4.0-testsuite Build Failed
 
 Can somebody kill whatever is bound to port 1098 on this machine
please.
 
 On Wed, 2006-04-05 at 07:46 -0400, [EMAIL PROTECTED] wrote:
  View results here -
 

http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=l
 og20060405072327
  
   BUILD FAILED
Ant Error
  Message:
 /services/cruisecontrol/work/scripts/build-jboss-common.xml:224: The
 following error occurred while executing this line:
 /services/cruisecontrol/work/scripts/build-jboss-common.xml:148: Exit
 code: 1 See tests.log in Build Artifacts for details.
 
Date of build: 04/05/2006 07:23:27
   Time to build: 21 minutes 29 seconds
Last changed: 04/04/2006 17:29:53
 
-- 

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=lnkkid0944bid$1720dat1642

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-04-05 Thread Scott M Stark 
An undeployed class loader should probably still delegate to its parent
if it does not have a repository? 

 -Original Message-
 From: Adrian Brock 
 Sent: Wednesday, April 05, 2006 9:42 AM
 To: Scott M Stark
 Cc: Rajesh Rajasekaran; QA; jboss-development@lists.sourceforge.net
 Subject: RE: jboss-4.0-testsuite Build Failed
 
 Very interesting Mr Bond...
 
   new Thread(new Runnable()
   {
  public void run()
  {
 System.exit(0);
  }
   }, ExitOnShutdown).start();
 
 Can't do that either, because this cannot load a class from 
 the undeployed classloader. :-)
 


---
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=lnkkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-04-05 Thread Scott M Stark 
The minimal shutdown is very sensative to the implementation details of
the server because there is no jmx invoker in this config. The shutdown
relies on the behavior of a service undeployment calling System.exit so
JBAS-3050 has likely changed how this behaves. I don't remember why this
service could not use a jmx message instead.

 -Original Message-
 From: Rajesh Rajasekaran 
 Sent: Wednesday, April 05, 2006 8:59 AM
 To: Adrian Brock; QA
 Cc: Alexey Loubyansky; Amit Bhayani; Anil Saldhana; Bela Ban; 
 Bill Burke; Brian Stansberry; Clebert Suconic; Dimitris 
 Andreadis; Emmanuel Bernard; [EMAIL PROTECTED]; 
 jboss-development@lists.sourceforge.net; 
 [EMAIL PROTECTED]; Kabir Khan; Ryan Campbell; Ruel Loehr; 
 Scott M Stark; Thomas Diesler; Tom Elrod
 Subject: RE: jboss-4.0-testsuite Build Failed
 
 The all config fails to start because port 1098 is still in 
 use by the minimal configuration which started up earlier. 
 The minimal waits for 60 secs to completely shut down before 
 which the all config starts. I guess this change is related 
 to the following issue.
 http://jira.jboss.com/jira/browse/JBAS-3050
 
 This can be verfied by running the testsuite manually. ant 
 tests from the testsuite folder.
 This can be avoided by allowing the testsuite to wait for 60 
 secs or more before different configurations start up.
 
 Thanks
 Rajesh


---
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=lnkkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-04-05 Thread Adrian Brock 
The problem is that ExitOnShutDown.java
invokes exit() from stopService()
this means the new code thinks the deployment thread is busy,
because exit() never returns.

I'll make stopService() fork a thread.

On Wed, 2006-04-05 at 11:21 -0500, Scott M Stark wrote:
 The minimal shutdown is very sensative to the implementation details of
 the server because there is no jmx invoker in this config. The shutdown
 relies on the behavior of a service undeployment calling System.exit so
 JBAS-3050 has likely changed how this behaves. I don't remember why this
 service could not use a jmx message instead.
 
  -Original Message-
  From: Rajesh Rajasekaran 
  Sent: Wednesday, April 05, 2006 8:59 AM
  To: Adrian Brock; QA
  Cc: Alexey Loubyansky; Amit Bhayani; Anil Saldhana; Bela Ban; 
  Bill Burke; Brian Stansberry; Clebert Suconic; Dimitris 
  Andreadis; Emmanuel Bernard; [EMAIL PROTECTED]; 
  jboss-development@lists.sourceforge.net; 
  [EMAIL PROTECTED]; Kabir Khan; Ryan Campbell; Ruel Loehr; 
  Scott M Stark; Thomas Diesler; Tom Elrod
  Subject: RE: jboss-4.0-testsuite Build Failed
  
  The all config fails to start because port 1098 is still in 
  use by the minimal configuration which started up earlier. 
  The minimal waits for 60 secs to completely shut down before 
  which the all config starts. I guess this change is related 
  to the following issue.
  http://jira.jboss.com/jira/browse/JBAS-3050
  
  This can be verfied by running the testsuite manually. ant 
  tests from the testsuite folder.
  This can be avoided by allowing the testsuite to wait for 60 
  secs or more before different configurations start up.
  
  Thanks
  Rajesh
-- 

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=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-04-05 Thread Adrian Brock 
Very interesting Mr Bond...

  new Thread(new Runnable()
  {
 public void run()
 {
System.exit(0);
 }
  }, ExitOnShutdown).start();

Can't do that either, because this cannot load a class from the
undeployed classloader. :-)

2006-04-05 17:36:57,751 DEBUG [org.jboss.deployment.MainDeployer]
Undeployed
file:/home/ejort/jboss-4.0/build/output/jboss-4.0.4.GA/server/minimal/deploy/shutdown.sar
2006-04-05 17:36:57,753 ERROR [STDERR] java.lang.NoClassDefFoundError:
java/lang/System
2006-04-05 17:36:57,753 ERROR [STDERR]  at
org.jboss.test.jmx.shutdown.ExitOnShutdown$1.run(ExitOnShutdown.java:52)
2006-04-05 17:36:57,754 ERROR [STDERR]  at
java.lang.Thread.run(Thread.java:534)


On Wed, 2006-04-05 at 17:33 +0100, Adrian Brock wrote:
 The problem is that ExitOnShutDown.java
 invokes exit() from stopService()
 this means the new code thinks the deployment thread is busy,
 because exit() never returns.
 
 I'll make stopService() fork a thread.
 
 On Wed, 2006-04-05 at 11:21 -0500, Scott M Stark wrote:
  The minimal shutdown is very sensative to the implementation details of
  the server because there is no jmx invoker in this config. The shutdown
  relies on the behavior of a service undeployment calling System.exit so
  JBAS-3050 has likely changed how this behaves. I don't remember why this
  service could not use a jmx message instead.
  
   -Original Message-
   From: Rajesh Rajasekaran 
   Sent: Wednesday, April 05, 2006 8:59 AM
   To: Adrian Brock; QA
   Cc: Alexey Loubyansky; Amit Bhayani; Anil Saldhana; Bela Ban; 
   Bill Burke; Brian Stansberry; Clebert Suconic; Dimitris 
   Andreadis; Emmanuel Bernard; [EMAIL PROTECTED]; 
   jboss-development@lists.sourceforge.net; 
   [EMAIL PROTECTED]; Kabir Khan; Ryan Campbell; Ruel Loehr; 
   Scott M Stark; Thomas Diesler; Tom Elrod
   Subject: RE: jboss-4.0-testsuite Build Failed
   
   The all config fails to start because port 1098 is still in 
   use by the minimal configuration which started up earlier. 
   The minimal waits for 60 secs to completely shut down before 
   which the all config starts. I guess this change is related 
   to the following issue.
   http://jira.jboss.com/jira/browse/JBAS-3050
   
   This can be verfied by running the testsuite manually. ant 
   tests from the testsuite folder.
   This can be avoided by allowing the testsuite to wait for 60 
   secs or more before different configurations start up.
   
   Thanks
   Rajesh
-- 

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=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-04-05 Thread Adrian Brock 
On Wed, 2006-04-05 at 11:44 -0500, Scott M Stark wrote:
 An undeployed class loader should probably still delegate to its parent
 if it does not have a repository? 

Agreed. Reflection didn't work either.

I've changed the minimal config to have
attribute name=StopTimeOut0/attribute
to temporarily workaround the issue.

 
  -Original Message-
  From: Adrian Brock 
  Sent: Wednesday, April 05, 2006 9:42 AM
  To: Scott M Stark
  Cc: Rajesh Rajasekaran; QA; jboss-development@lists.sourceforge.net
  Subject: RE: jboss-4.0-testsuite Build Failed
  
  Very interesting Mr Bond...
  
new Thread(new Runnable()
{
   public void run()
   {
  System.exit(0);
   }
}, ExitOnShutdown).start();
  
  Can't do that either, because this cannot load a class from 
  the undeployed classloader. :-)
  
-- 

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=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-04-05 Thread Scott M Stark 
I'll create a jira issue for the class loader behavior. 

 -Original Message-
 From: Adrian Brock 
 Sent: Wednesday, April 05, 2006 10:16 AM
 To: Scott M Stark
 Cc: Rajesh Rajasekaran; QA; jboss-development@lists.sourceforge.net
 Subject: RE: jboss-4.0-testsuite Build Failed
 
 On Wed, 2006-04-05 at 11:44 -0500, Scott M Stark wrote:
  An undeployed class loader should probably still delegate to its 
  parent if it does not have a repository?
 
 Agreed. Reflection didn't work either.
 
 I've changed the minimal config to have
 attribute name=StopTimeOut0/attribute to temporarily 
 workaround the issue.


---
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=lnkkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-04-05 Thread Adrian Brock 
The deployment is destroyed before the classloader.
It is just that it left a thread lying around referencing the
classloader.

On Wed, 2006-04-05 at 12:33 -0500, Scott M Stark wrote:
 I do have to question why the class loader is destroyed before all
 deployments are though. I'll look into that as part of the JBAS-3063
 issue.
 
  -Original Message-
  From: Scott M Stark 
  Sent: Wednesday, April 05, 2006 10:24 AM
  To: Adrian Brock
  Cc: Rajesh Rajasekaran; QA; jboss-development@lists.sourceforge.net
  Subject: RE: jboss-4.0-testsuite Build Failed
  
  I'll create a jira issue for the class loader behavior. 
  
   -Original Message-
   From: Adrian Brock
   Sent: Wednesday, April 05, 2006 10:16 AM
   To: Scott M Stark
   Cc: Rajesh Rajasekaran; QA; jboss-development@lists.sourceforge.net
   Subject: RE: jboss-4.0-testsuite Build Failed
   
   On Wed, 2006-04-05 at 11:44 -0500, Scott M Stark wrote:
An undeployed class loader should probably still delegate to its 
parent if it does not have a repository?
   
   Agreed. Reflection didn't work either.
   
   I've changed the minimal config to have attribute 
   name=StopTimeOut0/attribute to temporarily workaround 
  the issue.
  
-- 

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=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-04-05 Thread Scott M Stark 
I do have to question why the class loader is destroyed before all
deployments are though. I'll look into that as part of the JBAS-3063
issue.

 -Original Message-
 From: Scott M Stark 
 Sent: Wednesday, April 05, 2006 10:24 AM
 To: Adrian Brock
 Cc: Rajesh Rajasekaran; QA; jboss-development@lists.sourceforge.net
 Subject: RE: jboss-4.0-testsuite Build Failed
 
 I'll create a jira issue for the class loader behavior. 
 
  -Original Message-
  From: Adrian Brock
  Sent: Wednesday, April 05, 2006 10:16 AM
  To: Scott M Stark
  Cc: Rajesh Rajasekaran; QA; jboss-development@lists.sourceforge.net
  Subject: RE: jboss-4.0-testsuite Build Failed
  
  On Wed, 2006-04-05 at 11:44 -0500, Scott M Stark wrote:
   An undeployed class loader should probably still delegate to its 
   parent if it does not have a repository?
  
  Agreed. Reflection didn't work either.
  
  I've changed the minimal config to have attribute 
  name=StopTimeOut0/attribute to temporarily workaround 
 the issue.
 


---
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=lnkkid0944bid$1720dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-03-28 Thread Kabir Khan 



Ah yes, I tested with a version compiled against the new 
javassist. I will release again

  
  
  From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  Scott M StarkSent: 28 March 2006 03:02To: Ryan 
  Campbell; jboss-developmentCc: QASubject: [JBoss-dev] 
  RE: jboss-4.0-testsuite Build Failed
  
  There have been 10 revisions to the jboss-head version of 
  FieldAccessTransformer since the JBoss_AOP_1_3_5 tagged version. The 
  stopPrunning(boolean) method return type has changed from void to boolean, 
  andthis is also a problem in the 1.3.5 release of aop. We probably need 
  a 1.4.0 release of aop that is just aop compiled against the new 
  javassist.
  
  
  
  
  From: Ryan Campbell 
  Sent: Monday, March 27, 2006 3:50 PMTo: 
  'jboss-development'Cc: QASubject: RE: 
  jboss-4.0-testsuite Build Failed
  

It looks like aop 1.3.4 is not compatible with javassist 3.2.0.CR1, but this is how I interpreted Kabirs assent to the upgrade on Friday._jars-cache: [mkdir] Created dir: /services/cruisecontrol/checkout/jboss-4.0-testsuite/testsuite/output/resources/META-INF [copy] Copying 9 files to /services/cruisecontrol/checkout/jboss-4.0-testsuite/testsuite/output/resources/META-INFOverriding previous definition of reference to aop.task.classpath [aopc] java.lang.NoSuchMethodError: javassist.CtClass.stopPruning(Z)V [aopc]  at org.jboss.aop.instrument.FieldAccessTransformer$OptimizedTransformer.createOptimizedInvocationClass(FieldAccessTransformer.java:857) [aopc]  at org.jboss.aop.instrument.FieldAccessTransformer$OptimizedTransformer.buildFieldWrappers(FieldAccessTransformer.java:533) [aopc]  at org.jboss.aop.instrument.FieldAccessTransformer.buildFieldWrappers(FieldAccessTransformer.java:73) [aopc]  at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:657) [aopc]  at org.jboss.aop.AspectManager.translate(AspectManager.java:792) [aopc]  at org.jboss.aop.AspectManager.transform(AspectManager.java:704) [aopc]  at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:325) [aopc]  at org.jboss.aop.standalone.Compiler.compile(Compiler.java:217) [aopc]  at org.jboss.aop.standalone.Compiler.main(Compiler.java:73)






From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, March 27, 2006 5:43 
PMTo: Adrian Brock; Alexey 
Loubyansky; Anil Saldhana; Bill 
Burke; Brian Stansberry; Emmanuel Bernard; 
jboss-development@lists.sourceforge.net; [EMAIL PROTECTED]; Kabir Khan; 
QA; Ryan Campbell; Ruel Loehr; 
Scott M Stark; Thomas DieslerSubject: jboss-4.0-testsuite Build 
FailedImportance: 
High

View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060327182315


  
  

  BUILD 
  FAILED
  

  Ant Error 
  Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:224: 
  The following error occurred while executing this line: 
  /services/cruisecontrol/work/scripts/build-jboss-common.xml:148: Exit 
  code: 1 See tests.log in Build Artifacts for 
  details.
  

  Date of 
  build:03/27/2006 
  18:23:15
  

  Time to 
  build:17 minutes 
  43 seconds
  

  Last 
  changed:03/27/2006 
  18:15:55
  

  Last log 
  entry:JBAS-3014 
  upgrade javassist to 
  3.2.0.CR1

RE: [JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-03-28 Thread Kabir Khan 



I've made a new release and added it to the repository. 
The testsuite builds fine now, and the aop tests pass. The build no longer adds 
deploy/jboss-aop.deployer/javassist.jar since this is now in 
lib. 

http://jira.jboss.com/jira/browse/JBAS-3017

  
  
  From: Kabir Khan [mailto:[EMAIL PROTECTED] 
  Sent: 28 March 2006 11:03To: 
  'jboss-development@lists.sourceforge.net'; 'Ryan Campbell'Cc: 
  'QA'Subject: RE: [JBoss-dev] RE: jboss-4.0-testsuite Build 
  Failed
  
  Ah yes, I tested with a version compiled against the new 
  javassist. I will release again
  


From: 
[EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of 
Scott M StarkSent: 28 March 2006 03:02To: Ryan 
Campbell; jboss-developmentCc: QASubject: [JBoss-dev] 
RE: jboss-4.0-testsuite Build Failed

There have been 10 revisions to the jboss-head version 
of FieldAccessTransformer since the JBoss_AOP_1_3_5 tagged version. The 
stopPrunning(boolean) method return type has changed from void to boolean, 
andthis is also a problem in the 1.3.5 release of aop. We probably 
need a 1.4.0 release of aop that is just aop compiled against the new 
javassist.




From: Ryan Campbell 
Sent: Monday, March 27, 2006 3:50 PMTo: 
'jboss-development'Cc: QASubject: RE: 
jboss-4.0-testsuite Build Failed

  
  It looks like aop 1.3.4 is not compatible with javassist 3.2.0.CR1, but this is how I interpreted Kabirs assent to the upgrade on Friday._jars-cache: [mkdir] Created dir: /services/cruisecontrol/checkout/jboss-4.0-testsuite/testsuite/output/resources/META-INF [copy] Copying 9 files to /services/cruisecontrol/checkout/jboss-4.0-testsuite/testsuite/output/resources/META-INFOverriding previous definition of reference to aop.task.classpath [aopc] java.lang.NoSuchMethodError: javassist.CtClass.stopPruning(Z)V [aopc]  at org.jboss.aop.instrument.FieldAccessTransformer$OptimizedTransformer.createOptimizedInvocationClass(FieldAccessTransformer.java:857) [aopc]  at org.jboss.aop.instrument.FieldAccessTransformer$OptimizedTransformer.buildFieldWrappers(FieldAccessTransformer.java:533) [aopc]  at org.jboss.aop.instrument.FieldAccessTransformer.buildFieldWrappers(FieldAccessTransformer.java:73) [aopc]  at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:657) [aopc]  at org.jboss.aop.AspectManager.translate(AspectManager.java:792) [aopc]  at org.jboss.aop.AspectManager.transform(AspectManager.java:704) [aopc]  at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:325) [aopc]  at org.jboss.aop.standalone.Compiler.compile(Compiler.java:217) [aopc]  at org.jboss.aop.standalone.Compiler.main(Compiler.java:73)
  
  
  
  
  
  
  From: 
  [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, March 27, 2006 5:43 
  PMTo: Adrian Brock; 
  Alexey Loubyansky; Anil 
  Saldhana; Bill Burke; Brian Stansberry; Emmanuel Bernard; 
  jboss-development@lists.sourceforge.net; [EMAIL PROTECTED]; Kabir Khan; 
  QA; Ryan Campbell; Ruel Loehr; 
  Scott M Stark; Thomas DieslerSubject: jboss-4.0-testsuite Build 
  FailedImportance: 
  High
  
  View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060327182315
  
  


  
BUILD 
FAILED

  
Ant Error 
Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:224: 
The following error occurred while executing this line: 
/services/cruisecontrol/work/scripts/build-jboss-common.xml:148: 
Exit code: 1 See tests.log in Build Artifacts for 
details.

  
Date of 
build:03/27/2006 
18:23:15

  
Time to 
build:17 minutes 
43 seconds

  
Last 
changed:03/27/2006 
18:15:55

  
Last log 
entry:JBAS-3014 
upgrade javassist to 
3.2.0.CR1

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-03-27 Thread Ryan Campbell 






It looks like aop 1.3.4 is not compatible with javassist 3.2.0.CR1, but this is how I interpreted Kabirs assent to the upgrade on Friday._jars-cache: [mkdir] Created dir: /services/cruisecontrol/checkout/jboss-4.0-testsuite/testsuite/output/resources/META-INF [copy] Copying 9 files to /services/cruisecontrol/checkout/jboss-4.0-testsuite/testsuite/output/resources/META-INFOverriding previous definition of reference to aop.task.classpath [aopc] java.lang.NoSuchMethodError: javassist.CtClass.stopPruning(Z)V [aopc]  at org.jboss.aop.instrument.FieldAccessTransformer$OptimizedTransformer.createOptimizedInvocationClass(FieldAccessTransformer.java:857) [aopc]  at org.jboss.aop.instrument.FieldAccessTransformer$OptimizedTransformer.buildFieldWrappers(FieldAccessTransformer.java:533) [aopc]  at org.jboss.aop.instrument.FieldAccessTransformer.buildFieldWrappers(FieldAccessTransformer.java:73) [aopc]  at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:657) [aopc]  at org.jboss.aop.AspectManager.translate(AspectManager.java:792) [aopc]  at org.jboss.aop.AspectManager.transform(AspectManager.java:704) [aopc]  at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:325) [aopc]  at org.jboss.aop.standalone.Compiler.compile(Compiler.java:217) [aopc]  at org.jboss.aop.standalone.Compiler.main(Compiler.java:73)













From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Monday, March 27, 2006 5:43
PM
To: Adrian Brock; Alexey
Loubyansky; Anil Saldhana; Bill
Burke; Brian Stansberry; Emmanuel Bernard;
jboss-development@lists.sourceforge.net; [EMAIL PROTECTED]; Kabir Khan; QA;
Ryan Campbell; Ruel Loehr; Scott M Stark; Thomas
 Diesler
Subject: jboss-4.0-testsuite Build
Failed
Importance: High





View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060327182315




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:224:
  The following error occurred while executing this line:
  /services/cruisecontrol/work/scripts/build-jboss-common.xml:148: Exit code: 1
  See tests.log in Build Artifacts for details.
  
 
 
  
  Date
  of build:03/27/2006 18:23:15
  
 
 
  
  Time
  to build:17 minutes 43 seconds
  
 
 
  
  Last
  changed:03/27/2006 18:15:55
  
 
 
  
  Last
  log entry:JBAS-3014 upgrade
  javassist to 3.2.0.CR1

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-03-27 Thread Scott M Stark 



There have been 10 revisions to the jboss-head version of 
FieldAccessTransformer since the JBoss_AOP_1_3_5 tagged version. The 
stopPrunning(boolean) method return type has changed from void to boolean, 
andthis is also a problem in the 1.3.5 release of aop. We probably need a 
1.4.0 release of aop that is just aop compiled against the new 
javassist.




From: Ryan Campbell 
Sent: Monday, March 27, 2006 3:50 PMTo: 
'jboss-development'Cc: QASubject: RE: jboss-4.0-testsuite 
Build Failed

  
  It looks like aop 1.3.4 is not compatible with javassist 3.2.0.CR1, but this is how I interpreted Kabirs assent to the upgrade on Friday._jars-cache: [mkdir] Created dir: /services/cruisecontrol/checkout/jboss-4.0-testsuite/testsuite/output/resources/META-INF [copy] Copying 9 files to /services/cruisecontrol/checkout/jboss-4.0-testsuite/testsuite/output/resources/META-INFOverriding previous definition of reference to aop.task.classpath [aopc] java.lang.NoSuchMethodError: javassist.CtClass.stopPruning(Z)V [aopc]  at org.jboss.aop.instrument.FieldAccessTransformer$OptimizedTransformer.createOptimizedInvocationClass(FieldAccessTransformer.java:857) [aopc]  at org.jboss.aop.instrument.FieldAccessTransformer$OptimizedTransformer.buildFieldWrappers(FieldAccessTransformer.java:533) [aopc]  at org.jboss.aop.instrument.FieldAccessTransformer.buildFieldWrappers(FieldAccessTransformer.java:73) [aopc]  at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:657) [aopc]  at org.jboss.aop.AspectManager.translate(AspectManager.java:792) [aopc]  at org.jboss.aop.AspectManager.transform(AspectManager.java:704) [aopc]  at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:325) [aopc]  at org.jboss.aop.standalone.Compiler.compile(Compiler.java:217) [aopc]  at org.jboss.aop.standalone.Compiler.main(Compiler.java:73)
  
  
  
  
  
  
  From: 
  [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, March 27, 2006 5:43 
  PMTo: Adrian Brock; Alexey 
  Loubyansky; Anil Saldhana; Bill 
  Burke; Brian Stansberry; Emmanuel Bernard; 
  jboss-development@lists.sourceforge.net; [EMAIL PROTECTED]; Kabir Khan; QA; 
  Ryan Campbell; Ruel Loehr; 
  Scott M Stark; Thomas DieslerSubject: jboss-4.0-testsuite Build 
  FailedImportance: 
  High
  
  View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060327182315
  
  


  
BUILD 
FAILED

  
Ant Error 
Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:224: 
The following error occurred while executing this line: 
/services/cruisecontrol/work/scripts/build-jboss-common.xml:148: Exit 
code: 1 See tests.log in Build Artifacts for 
details.

  
Date of 
build:03/27/2006 
18:23:15

  
Time to 
build:17 minutes 43 
seconds

  
Last 
changed:03/27/2006 
18:15:55

  
Last log 
entry:JBAS-3014 
upgrade javassist to 
  3.2.0.CR1

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-03-24 Thread Ryan Campbell 








It looks like javax.jws.WebService is
missing from jbossws14.jar. This was working yesterday, so I think this update
to the repository didnt include it for some reason?



http://fisheye.jboss.com/changelog/JBoss/repository.jboss.com?cs=MAIN:tdiesler:20060324094641




stack trace:



15:16:54,946 ERROR [MainDeployer] Could
not create deployment:
file:/home/rcampbell/work/jboss-4.0/build/output/jboss-4.0.4.CR2/server/all/deploy/httpha-invoker.sar/invoker.war/

org.jboss.ws.WSException:
java.lang.ClassNotFoundException: No ClassLoaders found for:
javax.jws.WebService


at
org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment(WebServiceDeployerJSE.java:159)


at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:101)


at org.jboss.ws.server.WebServiceDeployerJSE.create(WebServiceDeployerJSE.java:65)


at
org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)


at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)













From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Friday, March 24, 2006 1:38
PM
To: Adrian Brock; Anil Saldhana; Bill Burke; Brian Stansberry;
jboss-development@lists.sourceforge.net; [EMAIL PROTECTED]; QA; Ryan
Campbell; Ruel Loehr; Scott M Stark; Thomas Diesler
Subject: jboss-4.0-testsuite Build
Failed
Importance: High





View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060324140634




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:224:
  The following error occurred while executing this line:
  /services/cruisecontrol/work/scripts/build-jboss-common.xml:148: Exit code: 1
  See tests.log in Build Artifacts for details.
  
 
 
  
  Date
  of build:03/24/2006 14:06:34
  
 
 
  
  Time
  to build:29 minutes 7 seconds
  
 
 
  
  Last
  changed:03/24/2006 13:34:24
  
 
 
  
  Last
  log entry:Add wsdl4j.jar,
  xmlsec.jar to jbossall-client.jar

RE: [JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-03-24 Thread Jason T. Greene 








The annotation stuff is purposefully excluded
from jdk 1.4 builds. WebServiceDeployJSE should be commented out in the 1.4
version.



-Jason













From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ryan Campbell
Sent: Friday, March 24, 2006 3:33
PM
To: Thomas Diesler
Cc: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] RE:
jboss-4.0-testsuite Build Failed





It looks like javax.jws.WebService is
missing from jbossws14.jar. This was working yesterday, so I think this
update to the repository didnt include it for some reason?



http://fisheye.jboss.com/changelog/JBoss/repository.jboss.com?cs=MAIN:tdiesler:20060324094641




stack trace:



15:16:54,946 ERROR [MainDeployer] Could
not create deployment:
file:/home/rcampbell/work/jboss-4.0/build/output/jboss-4.0.4.CR2/server/all/deploy/httpha-invoker.sar/invoker.war/

org.jboss.ws.WSException:
java.lang.ClassNotFoundException: No ClassLoaders found for:
javax.jws.WebService


at
org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment(WebServiceDeployerJSE.java:159)


at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:101)


at org.jboss.ws.server.WebServiceDeployerJSE.create(WebServiceDeployerJSE.java:65)


at
org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)


at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)













From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Friday, March 24, 2006 1:38
PM
To: Adrian
 Brock; Anil Saldhana;
Bill Burke; Brian Stansberry; jboss-development@lists.sourceforge.net;
[EMAIL PROTECTED]; QA; Ryan Campbell; Ruel Loehr;
Scott M Stark; Thomas Diesler
Subject: jboss-4.0-testsuite Build
Failed
Importance: High





View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060324140634




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:224:
  The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-common.xml:148:
  Exit code: 1 See tests.log in Build Artifacts for details.
  
 
 
  
  Date
  of build:03/24/2006 14:06:34
  
 
 
  
  Time
  to build:29 minutes 7 seconds
  
 
 
  
  Last
  changed:03/24/2006 13:34:24
  
 
 
  
  Last
  log entry:Add wsdl4j.jar,
  xmlsec.jar to jbossall-client.jar

RE: [JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-03-24 Thread Jason T. Greene 








Nevermind, I was thinking of the EJB3
deployer. JSE of course should be enabled.













From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jason T. Greene
Sent: Friday, March 24, 2006 4:37
PM
To: jboss-development@lists.sourceforge.net;
Ryan Campbell
Cc: Thomas Diesler
Subject: RE: [JBoss-dev] RE:
jboss-4.0-testsuite Build Failed





The annotation stuff is purposefully
excluded from jdk 1.4 builds. WebServiceDeployJSE should be commented out
in the 1.4 version.



-Jason













From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ryan Campbell
Sent: Friday, March 24, 2006 3:33
PM
To: Thomas Diesler
Cc: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] RE:
jboss-4.0-testsuite Build Failed





It looks like javax.jws.WebService is
missing from jbossws14.jar. This was working yesterday, so I think this
update to the repository didnt include it for some reason?



http://fisheye.jboss.com/changelog/JBoss/repository.jboss.com?cs=MAIN:tdiesler:20060324094641




stack trace:



15:16:54,946 ERROR [MainDeployer] Could
not create deployment:
file:/home/rcampbell/work/jboss-4.0/build/output/jboss-4.0.4.CR2/server/all/deploy/httpha-invoker.sar/invoker.war/

org.jboss.ws.WSException:
java.lang.ClassNotFoundException: No ClassLoaders found for:
javax.jws.WebService


at
org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment(WebServiceDeployerJSE.java:159)


at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:101)


at
org.jboss.ws.server.WebServiceDeployerJSE.create(WebServiceDeployerJSE.java:65)


at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)


at
org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)













From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Friday, March 24, 2006 1:38
PM
To: Adrian
 Brock; Anil Saldhana;
Bill Burke; Brian Stansberry; jboss-development@lists.sourceforge.net;
[EMAIL PROTECTED]; QA; Ryan Campbell; Ruel Loehr;
Scott M Stark; Thomas Diesler
Subject: jboss-4.0-testsuite Build
Failed
Importance: High





View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060324140634




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:224:
  The following error occurred while executing this line:
  /services/cruisecontrol/work/scripts/build-jboss-common.xml:148: Exit code: 1
  See tests.log in Build Artifacts for details.
  
 
 
  
  Date
  of build:03/24/2006 14:06:34
  
 
 
  
  Time
  to build:29 minutes 7 seconds
  
 
 
  
  Last
  changed:03/24/2006 13:34:24
  
 
 
  
  Last
  log entry:Add wsdl4j.jar,
  xmlsec.jar to jbossall-client.jar

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2006-03-24 Thread Ryan Campbell 








This was fixed by the upgrade to
1.0.0.CR5. Triggering test run.











From: Ryan Campbell 
Sent: Friday, March 24, 2006 3:33
PM
To: 'Thomas
 Diesler'
Cc: 'jboss-development@lists.sourceforge.net'
Subject: RE: jboss-4.0-testsuite
Build Failed





It looks like javax.jws.WebService is
missing from jbossws14.jar. This was working yesterday, so I think this
update to the repository didnt include it for some reason?



http://fisheye.jboss.com/changelog/JBoss/repository.jboss.com?cs=MAIN:tdiesler:20060324094641




stack trace:



15:16:54,946 ERROR [MainDeployer] Could
not create deployment:
file:/home/rcampbell/work/jboss-4.0/build/output/jboss-4.0.4.CR2/server/all/deploy/httpha-invoker.sar/invoker.war/

org.jboss.ws.WSException:
java.lang.ClassNotFoundException: No ClassLoaders found for:
javax.jws.WebService


at
org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment(WebServiceDeployerJSE.java:159)


at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:101)


at org.jboss.ws.server.WebServiceDeployerJSE.create(WebServiceDeployerJSE.java:65)


at
org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)


at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)













From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Friday, March 24, 2006 1:38
PM
To: Adrian Brock; Anil Saldhana; Bill Burke; Brian Stansberry;
jboss-development@lists.sourceforge.net; [EMAIL PROTECTED]; QA; Ryan
Campbell; Ruel Loehr; Scott M Stark; Thomas
 Diesler
Subject: jboss-4.0-testsuite Build
Failed
Importance: High





View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060324140634




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:224:
  The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-common.xml:148:
  Exit code: 1 See tests.log in Build Artifacts for details.
  
 
 
  
  Date
  of build:03/24/2006 14:06:34
  
 
 
  
  Time
  to build:29 minutes 7 seconds
  
 
 
  
  Last
  changed:03/24/2006 13:34:24
  
 
 
  
  Last
  log entry:Add wsdl4j.jar,
  xmlsec.jar to jbossall-client.jar

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2005-09-09 Thread Ryan Campbell 








The testsuite build timed out (went longer
than 2 hours). The following tests timed out as well:



 [junit] Test
org.jboss.test.deadlock.test.BeanStressTestCase FAILED (timeout)

 [junit] Test
org.jboss.test.hello.test.HelloClusteredHttpStressTestCase FAILED (timeout)

 [junit] Test
org.jboss.test.hello.test.HelloHttpStressTestCase FAILED (timeout)

 [junit] Test
org.jboss.test.hello.test.HelloTimingStressTestCase FAILED (timeout)

 [junit] Test
org.jboss.test.jbossmq.perf.OILInvocationLayerStressTestCase FAILED (timeout)

 [junit] Test
org.jboss.test.jca.test.CachedConnectionBankStressTestCase FAILED (timeout)

 [junit] Test
org.jboss.test.jca.test.HAConnectionFactoryUnitTestCase FAILED (timeout)

 [junit] Test
org.jboss.test.jca.test.JDBCStatementTestsConnectionUnitTestCase FAILED
(timeout)

 [junit] Test
org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase FAILED (timeout)

 [junit] Test
org.jboss.test.jca.test.PSCacheUnitTestCase FAILED (timeout)

 [junit] Test
org.jboss.test.jca.test.RemoteDSUnitTestCase FAILED (timeout)

 [junit] Test
org.jboss.test.jca.test.SecurityContextUnitTestCase FAILED (timeout)

 [junit] Test
org.jboss.test.jmx.test.MBeanDependsOnConnectionManagerUnitTestCase FAILED
(timeout)

 [junit] Test
org.jboss.test.jmx.test.RedeployStressTestCase FAILED (timeout)

 [junit] Test
org.jboss.test.tm.test.TxTimeoutUnitTestCase FAILED



Not sure what to make of this, am forcing
the build again.













From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Friday, September 09, 2005
5:35 PM
To:
jboss-development@lists.sourceforge.net; QA
Subject: jboss-4.0-testsuite Build
Failed
Importance: High





View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050909163227




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message:build
  timeout
  
 
 
  
  Date
  of build:09/09/2005 16:32:27
  
 
 
  
  Time
  to build:
  
 
 
  
  Last
  changed:09/09/2005 15:19:15

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2005-09-09 Thread Scott M Stark 



The connectivity to the server is broken as these are 
trivial tests that take little time, for example:

testsuite errors="0" failures="0" 
name="org.jboss.test.jca.test.JDBCStatementTestsConnectionUnitTestCase" 
tests="5" time="1.547"

  
  
  From: Ryan Campbell Sent: Friday, 
  September 09, 2005 4:45 PMTo: 
  jboss-development@lists.sourceforge.net; QASubject: RE: 
  jboss-4.0-testsuite Build Failed
  
  
  The testsuite build 
  timed out (went longer than 2 hours). The following tests timed out as 
  well:
  
   
  [junit] Test org.jboss.test.deadlock.test.BeanStressTestCase FAILED 
  (timeout)
   
  [junit] Test org.jboss.test.hello.test.HelloClusteredHttpStressTestCase FAILED 
  (timeout)
   
  [junit] Test org.jboss.test.hello.test.HelloHttpStressTestCase FAILED 
  (timeout)
   
  [junit] Test org.jboss.test.hello.test.HelloTimingStressTestCase FAILED 
  (timeout)
   
  [junit] Test org.jboss.test.jbossmq.perf.OILInvocationLayerStressTestCase 
  FAILED (timeout)
   
  [junit] Test org.jboss.test.jca.test.CachedConnectionBankStressTestCase FAILED 
  (timeout)
   
  [junit] Test org.jboss.test.jca.test.HAConnectionFactoryUnitTestCase FAILED 
  (timeout)
   
  [junit] Test org.jboss.test.jca.test.JDBCStatementTestsConnectionUnitTestCase 
  FAILED (timeout)
   
  [junit] Test org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase FAILED 
  (timeout)
   
  [junit] Test org.jboss.test.jca.test.PSCacheUnitTestCase FAILED 
  (timeout)
   
  [junit] Test org.jboss.test.jca.test.RemoteDSUnitTestCase FAILED 
  (timeout)
   
  [junit] Test org.jboss.test.jca.test.SecurityContextUnitTestCase FAILED 
  (timeout)
   
  [junit] Test 
  org.jboss.test.jmx.test.MBeanDependsOnConnectionManagerUnitTestCase FAILED 
  (timeout)
   
  [junit] Test org.jboss.test.jmx.test.RedeployStressTestCase FAILED 
  (timeout)
   
  [junit] Test org.jboss.test.tm.test.TxTimeoutUnitTestCase 
  FAILED
  
  Not sure what to make 
  of this, am forcing the build again.
  
  
  
  
  
  
  From: 
  [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, September 09, 2005 5:35 
  PMTo: 
  jboss-development@lists.sourceforge.net; QASubject: jboss-4.0-testsuite Build 
  FailedImportance: 
  High
  
  View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050909163227
  
  


  
BUILD 
FAILED

  
Ant Error 
Message:build 
timeout

  
Date of 
build:09/09/2005 
16:32:27

  
Time to 
build:

  
Last 
changed:09/09/2005 
15:19:15

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2005-04-06 Thread Scott M Stark 



I 
don't understand the error relative to the subject. This says its a 4.0 branch 
testsuite build, but clearly this is a build of the jboss-head module. The 
errors are in the build of the hibernate deployer module:

/scratch/cruisecontrol/checkout/jboss-head/hibernate/src/main/org/jboss/hibernate/cache/DeployedTreeCacheProvider.java:59: cannot resolve symbol
symbol  : class CacheException 
location: class org.jboss.hibernate.cache.DeployedTreeCacheProvider
 throw new CacheException( "Unable to locate TreeCache MBean under object name [" + configObjectName + "]" );
   ^
/scratch/cruisecontrol/checkout/jboss-head/hibernate/src/main/org/jboss/hibernate/cache/DeployedTreeCacheProvider.java:85: package org.hibernate.cache does not exist
  return new org.hibernate.cache.TreeCache( deployedTreeCache, name );
^
/scratch/cruisecontrol/checkout/jboss-head/hibernate/src/main/org/jboss/hibernate/jmx/Hibernate.java:632: cannot resolve symbol
symbol  : variable NAMESPACE_PROP_NAME 
location: class org.jboss.hibernate.cache.DeployedTreeCacheProvider
  setUnlessNull(props, DeployedTreeCacheProvider.NAMESPACE_PROP_NAME, deployedTreeCacheJndiName);


  
  
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
  Sent: Wednesday, April 06, 2005 12:43 AMTo: 
  jboss-development@lists.sourceforge.net; QASubject: 
  jboss-4.0-testsuite Build FailedImportance: 
  High
  View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050406015757
  
  


  BUILD FAILED

  Ant Error 
Message:/home/cruisecontrol/work/scripts/build-jboss-head.xml:66: 
The following error occurred while executing this line: 
/home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 
See tests.log in Build Artifacts for details. 
JAVA_HOME=/opt/j2sdk1.4.2_05/

  Date of 
build:04/06/2005 01:57:57

  Time to 
build:91 minutes 15 seconds

  Last 
changed:04/05/2005 23:07:59

  Last log 
entry:Preserve the wsdl specified soap:address if it is a 
valid URLAdd AlwaysModifySOAPAddress option to the AxisService MBean 
which can be usedto switch to the previous behavior of always 
rewritingFix several tests that had invalid urlsAdd a addressrewrite 
test to verify new behaviorFix JBWS-157
  
  





  


  Unit Tests: (0) 
Total Errors and Failures: (0)

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2004-11-02 Thread Scott M Stark 



Shutdown should not be taking over a minute. The log 
shows 40 seconds to close the hypersonic database:

2004-11-02 07:04:19,241 DEBUG 
[org.jboss.resource.connectionmanager.RARDeployment] Stopped 
jboss.jca:name=DefaultDS,service=ManagedConnectionFactory2004-11-02 
07:04:19,241 DEBUG [org.jboss.jdbc.HypersonicDatabase] Stopping 
jboss:database=localDB,service=Hypersonic2004-11-02 07:04:59,771 INFO 
[org.jboss.jdbc.HypersonicDatabase] Database standalone closed 
clean

and another delay 
removing the tmp/deploy directory:
2004-11-02 07:05:07,456 DEBUG [org.jboss.system.ServiceController] Stopped 354 services
2004-11-02 07:05:07,537 DEBUG [org.jboss.system.server.Server] Deleting server tmp/deploy directory
2004-11-02 07:05:16,354 INFO  [org.jboss.system.server.Server] Shutdown complete

  
  
  From: Ryan Campbell Sent: Tuesday, 
  November 02, 2004 8:31 AMTo: [EMAIL PROTECTED]; 
  [EMAIL PROTECTED]; QASubject: RE: 
  jboss-4.0-testsuite Build Failed
  
  
  Shutdown is taking 67 
  seconds for the all configuration:
  
  2004-11-02 
  07:04:09,900 DEBUG [org.jboss.system.server.Server] Shutting 
  down
  
  2004-11-02 
  07:05:16,354 INFO [org.jboss.system.server.Server] Shutdown 
  complete
  
  So, shutdown took 7 
  seconds longer than the timeout of 60 seconds. Does this indicate a 
  problem? I have added the all-server.log to the build 
  artifacts.

RE: [JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2004-11-01 Thread Scott M Stark 



I have compiled both the codebase and testsuite under 
java5 so as of today I know its working.
The previous fix was probably not for the 
testuite.



  
  
  From: Ryan Campbell Sent: Monday, 
  November 01, 2004 12:53 PMTo: 
  [EMAIL PROTECTED]; QASubject: RE: [JBoss-dev] 
  RE: jboss-4.0-testsuite Build Failed
  
  
  This is an old failure 
  that had showed up as fixed Friday:
  
  I do not think that 
  this failure was necessarily fixed on Friday, unless you tested it outside of 
  the continuous build. I saw the build marked as fixed after your 
  commit. However, no tests were scheduled to run for that build. 
  Cruisecontrol was only reporting that it did not detect any failures for the 
  compile. 
  
  Now that we have 
  jboss-4.0-testsuite separate from jboss-4.0, this confusion should be 
  eliminated.
  
   It looks like an old 
  ant16x-build.xml was moved into build.xml
  
  Im fairly certain 
  this is not the case. I performed several updates before the move to catch 
  this possibility. Furthermore, I just now performed a diff of the last 
  version of ant16x-build.xml and the version of build.xml that I committed 
  after the move:
  
  $ cvs co -d 
  pre-move -r 1.9.2.8 jbosstest/ant16x-build.xml
  U 
  pre-move/ant16x-build.xml
  $ cvs co -d 
  post-move -r 1.406.2.10 jbosstest/build.xml
  U 
  post-move/build.xml
  $ diff 
  pre-move/ant16x-build.xml post-move/build.xml
  9c9
   !-- 
  $Id: ant16x-build.xml,v 1.9.2.8 2004/10/29 16:46:38 starksm Exp $ 
  --
  ---
   !-- 
  $Id: build.xml,v 1.406.2.10 2004/10/30 02:55:42 recampbell Exp $ 
  --
  $

[JBoss-dev] RE: jboss-4.0-testsuite Build Failed

2004-10-31 Thread Scott M Stark 



This is 
an old failure that had showed up as fixed Friday:
/scratch/cruisecontrol/checkout/jboss-4.0/testsuite/build.xml:1732: Reference ${jaxr.includes.refid} not found.
It 
looks like an old ant16x-build.xml was moved into 
build.xml

  
  
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
  Sent: Sunday, October 31, 2004 4:24 AMTo: 
  [EMAIL PROTECTED]; QASubject: 
  jboss-4.0-testsuite Build FailedImportance: 
  High
  View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20041031023640
  
  


  BUILD FAILED

  Ant Error 
Message:/home/cruisecontrol/work/scripts/build-jboss-head.xml:62: 
The following error occurred while executing this line: 
/home/cruisecontrol/work/scripts/build-jboss-head.xml:34: Exit code: 1 
See tests.log in Build Artifacts for details. 
JAVA_HOME=/opt/j2sdk1.4.2_05/

  Date of 
build:10/31/2004 02:36:40

  Time to 
build:104 minutes 27 seconds

  Last 
changed:10/31/2004 01:51:11

  Last log 
entry:Changed to trace log level
  
  





  


  Unit Tests: (0) 
Total Errors and Failures: (0) 

  

  


  
  
  


  Modifications 
since last build: (7) 

  1.18
  modified
  bwang00
  cache/src/main/org/jboss/cache/lock/IdentityLock.java
  Changed to trace log level

  1.51
  modified
  bwang00
  cache/src/main/org/jboss/cache/Node.java
  Changed to trace log level

  1.421
  modified
  loubyansky
  testsuite/build.xml
  moved jaxme and wutka's parsers to 
library.classpath from tests.classpath

  1.420
  modified
  loubyansky
  testsuite/build.xml
  added jaxme and wutka's parser to the 
tests.classpath

  1.2
  modified
  loubyansky
  testsuite/src/main/org/jboss/test/xml/XMLNameToJavaIdentifierUnitTestCase.java
  XML names to various Java indentifiers 
conversion tests

  1.2
  modified
  loubyansky
  common/src/main/org/jboss/xml/binding/Util.java
  various XML binding utilities

  1.5
  modified
  loubyansky
  server/src/main/org/jboss/ejb/plugins/cmp/jdbc2/QueryFactory.java
  fixed [ 1056837 ] NullPointerException in 
QueryFinder