[JBoss-dev] JBossCache 1.4.0.CR2 released

2006-07-05 Thread Rajesh Rajasekaran








JBossCache 1.4.0.CR2 has been released and is available for
download on SourceForge at



http://sourceforge.net/project/showfiles.php?group_id=22866package_id=102339release_id=428151



JBossCache 1.4.0.CR2 jars are also updated in the
repository.





Thanks

Rajesh






Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] JBossIDE 2.0.0.Alpha released

2006-07-05 Thread Rajesh Rajasekaran








JBossIDE 2.0.0.Alpha has been released and is available for
download on SourceForge at



http://sourceforge.net/project/showfiles.php?group_id=22866package_id=72248release_id=429207





Thanks

Rajesh






Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


Re: [JBoss-dev] jboss-4.0-jdk-matrix Build Failed

2006-06-21 Thread Rajesh Rajasekaran








I ve cleaned this. The next build should
work.











From: Scott M Stark 
Sent: Wednesday, June 21, 2006
11:51 AM
To: [EMAIL PROTECTED]; Alexey Loubyansky;
jboss-development@lists.sourceforge.net; QA
Subject: RE: jboss-4.0-jdk-matrix
Build Failed





Looks like nfs is stuck.











From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 21, 2006
9:22 AM
To: Alexey
 Loubyansky; jboss-development@lists.sourceforge.net; QA
Subject: jboss-4.0-jdk-matrix
Build Failed
Importance: High

View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20060621121701





 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:201:
  The following error occurred while executing this line:
  /services/cruisecontrol/work/scripts/build-common-targets.xml:70: Unable to
  delete file /services/cruisecontrol/work/checkout/jboss-4.0.x/build/output/jboss-4.0.5.CR1/server/default/tmp/deploy/.nfs0102414b2618
  
 
 
  
  Date
  of build:06/21/2006 12:17:01
  
 
 
  
  Time
  to build:1 minute 54 seconds
  
 
 
  
  Last
  changed:06/21/2006 12:10:01
  
 
 
  
  Last
  log entry:JBAS-3328
  
 









 
  
  
  
 









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



   
  
  
  
  
  
  
  
  
  
  
  
  
  
 
 
  
  
  
  
  
  
  
  
  
  
  
  
 
 
  
  
  
  
  
  
  
  
  
 









 
  
  Modifications
  since last build: (first 50 of 1) 
  
 
 
  
  1.3.6.3
  
  
  modified
  
  
  aloubyansky
  
  
  server/src/main/org/jboss/ejb/plugins/keygenerator/hilo/HiLoKeyGenerator.java
  
  
  JBAS-3328
  
 
 
  
  
  
  
  
 









 
  
  
  
 













All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnkkid=107521bid=248729dat=121642___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


Re: [JBoss-dev] jbossweb-windows Build Failed

2006-06-19 Thread Rajesh Rajasekaran
The windows ia64 box (dev19) was down and I have already opened a ticket
with IT helpdesk and they are working on it. 
Once it's up I will force a build for jbossweb-windows.

Thanks
Rajesh

-Original Message-
From: Mladen Turk 
Sent: Monday, June 19, 2006 12:39 PM
To: QA
Cc: jboss-development@lists.sourceforge.net; Rajesh Rajasekaran; Eric
Brown; Ivelin Ivanov; Sacha Labourey
Subject: Re: jbossweb-windows Build Failed

[EMAIL PROTECTED] wrote:
 View results here - 

http://cruisecontrol.jboss.com/cc/buildresults/jbossweb-windows?log=log2
0060619003833
 
 BUILD FAILED

Hi guys,

It looks that the remote ant listener is down for
two days now!
Now, something like that simply sucks!

Can we do something to make sure the build
process is independent of the random closing of
the 'unknown' people that finds amusing to kill
the ant listener?

I'm sorry, but the frequency that breaks the
jbossweb build is simply unacceptable, and in
all the cases it's because someone kills the remote
ant process. Now, my question is: Who is that guy :)

Regards,
Mladen.



___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] JBossCache 1.4.0.CR1 released

2006-06-15 Thread Rajesh Rajasekaran








JBossCache 1.4.0.CR1 has been released and is available for
download on sourceforge at

http://sourceforge.net/project/showfiles.php?group_id=22866package_id=102339release_id=424990



JBossCache 1.4.0.CR1 has also been updated in the
repository.





Thanks

Rajesh






___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


Re: [JBoss-dev] jbossws-testsuite Build Failed

2006-06-09 Thread Rajesh Rajasekaran








The compile for jboss webservices looks broken.

Here s the log for the list of errors.

http://cruisecontrol.jboss.com/cc/artifacts/jbossws-testsuite/20060608204554/compilejbossws.log





Thanks

Rajesh











From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 08, 2006 7:49
PM
To: jboss-development@lists.sourceforge.net;
QA
Subject: jbossws-testsuite Build
Failed
Importance: High





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




 
  
  BUILD
  FAILED
  
 
 
  
  Ant
  Error Message:/services/cruisecontrol/work/scripts/build-jbossws-testsuite.xml:41:
  Exit code: 1 See compilejbossws.log in Build Artifacts for details.
  
 
 
  
  Date
  of build:06/08/2006 20:45:54
  
 
 
  
  Time
  to build:3 minutes 29 seconds
  
 









 
  
  
  
   

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

   
   



 
  
  
  
 













   
   












   
   









   
  
  
  
  
  
   

Modifications
since last build: (first 50 of 0) 

   
  
  
  
  
  
   



   
  
  
  
  
 











___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] JBossCache 1.4.0.Beta2 released

2006-06-02 Thread Rajesh Rajasekaran










JBossCache 1.4.0.Beta2 has been released and is available on
sourceforge at

http://sourceforge.net/project/showfiles.php?group_id=22866package_id=102339release_id=421930



JBossCache 1.4.0.Beta2 has also been updated in the repository.





Thanks

Rajesh

JBoss QA








___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] JBossSerialization 1.0.1.GA released

2006-05-24 Thread Rajesh Rajasekaran








JBossSerialization 1.0.1.GA has been released and is
available for download on SourceForge at

http://sourceforge.net/project/showfiles.php?group_id=22866package_id=188754release_id=419385



JBossSerialization 1.0.1.GA is also updated in the repository.





Thanks

Rajesh

JBoss QA








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

2006-05-23 Thread Rajesh Rajasekaran









The testsuite is compiled irrespective of
the main builds success or failure.

The actual failures are in the
compile-build.log

http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-1.6/20060523061707/compile-build.log





_default:compile-classes: [mkdir] Created dir: /services/cruisecontrol/checkout/jboss-4.0-testsuite-1.6/jmx/output/classes [javac] Compiling 600 source files to /services/cruisecontrol/checkout/jboss-4.0-testsuite-1.6/jmx/output/classes/services/cruisecontrol/checkout/jboss-4.0-testsuite-1.6/jmx/src/main/test/implementation/modelmbean/AttributeCacheTEST.java:256: unmappable character for encoding UTF8 assertTrue(notif.getNewValue().equals(mitvaan)); ^/services/cruisecontrol/checkout/jboss-4.0-testsuite-1.6/jmx/src/main/test/implementation/modelmbean/AttributeCacheTEST.java:266: unmappable character for encoding UTF8 server.setAttribute(name, new Attribute(Something, mitvaan)); ^2 errorsBUILD FAILED/services/cruisecontrol/checkout/jboss-4.0-testsuite-1.6/tools/etc/buildmagic/buildmagic.ent:435: Compile failed; see the compiler error output for details.













From: Scott M Stark 
Sent: Tuesday, May 23, 2006 9:15
AM
To: [EMAIL PROTECTED]; Alexey
Loubyansky; Anil Saldhana; Bill Decoste; Bill Burke; Brian Stansberry; Clebert
Suconic; jboss-development@lists.sourceforge.net; [EMAIL PROTECTED];
QA; Ruel Loehr; Thomas Diesler
Subject: RE:
jboss-4.0-testsuite-1.6 Build Failed





the error seen in the
compile-testsuite.log:



/services/cruisecontrol/checkout/jboss-4.0-testsuite-1.6/testsuite/build.xml:294:
Reference ${webservice.classpath} not found.



does not match what I see. The errors I
see are due to expansion of the jdbc api, and the current mock objects not
implementing the extended interfaces:





compile-classes-only:
 [javac] Compiling 3090 source files to
C:\cvs\JBoss4.0\jboss-4.0.x\testsuite
\output\classes
 [javac] C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\src\main\org\jboss\test\jca\ad
apter\MockedXADataSource.java:50: org.jboss.test.jca.adapter.MockedXADataSource
is not abstract and does not override abstract method getQueryObjectGenerator()
in javax.sql.CommonDataSource
 [javac] public class MockedXADataSource
 [javac] ^
 [javac]
C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\src\main\org\jboss\test\jca\ad
apter\MockedXADataSource.java:123:
org.jboss.test.jca.adapter.MockedXADataSource
.MockedXAConnection is not abstract and does not override abstract method
remove
StatementEventListener(javax.sql.StatementEventListener) in
javax.sql.PooledConn
ection
 [javac] public class MockedXAConnection

[javac] ^
 [javac] C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\src\main\org\jboss\test\jca\ad
apter\MockedXADataSource.java:153:
org.jboss.test.jca.adapter.MockedXADataSource
.MockedXAConnection.MockedConnection is not abstract and does not override
abstr
act method createQueryObject(java.lang.Class) in java.sql.Connection
 [javac] class
MockedConnection
 [javac] ^
 [javac]
C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\src\main\org\jboss\test\jca\jd
bc\TestConnection.java:45: org.jboss.test.jca.jdbc.TestConnection is not
abstrac
t and does not override abstract method createQueryObject(java.lang.Class) in
ja
va.sql.Connection
 [javac] public class TestConnection implements Connection {
 [javac] ^
 [javac]
C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\src\main\org\jboss\test\jca\jd
bc\TestStatement.java:41: org.jboss.test.jca.jdbc.TestStatement is not abstract
and does not override abstract method isClosed() in java.sql.Statement
 [javac] public class TestStatement
 [javac] ^
 [javac]
C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\src\main\org\jboss\test\jca\jd
bc\TestPreparedStatement.java:47: org.jboss.test.jca.jdbc.TestPreparedStatement
is not abstract and does not override abstract method isPoolable() in
java.sql.P
reparedStatement
 [javac] public class TestPreparedStatement extends
TestStatement
 [javac] ^
 [javac]
C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\src\main\org\jboss\test\jca\xa
ds\TestXADataSource.java:36: org.jboss.test.jca.xads.TestXADataSource is not
abs
tract and does not override abstract method getQueryObjectGenerator() in javax.s
ql.CommonDataSource
 [javac] public class TestXADataSource implements
XADataSource
 [javac] ^
 [javac]
C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\src\main\org\jboss\test\securi
ty\test\LoginModulesUnitTestCase.java:361: org.jboss.test.security.test.LoginMod
ulesUnitTestCase.TestDS is not abstract and does not override abstract method
cr
eateQueryObject(java.lang.Class) in javax.sql.DataSource
 [javac] static class TestDS implements
DataSource, Serializable

[javac] ^























From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, May 23, 2006 3:44
AM
To: Alexey Loubyansky; Anil
Saldhana; Bill Decoste; Bill Burke; Brian Stansberry; Clebert Suconic;
jboss-development@lists.sourceforge.net; [EMAIL PROTECTED]; QA; Ruel Loehr;
Scott M Stark; Thomas Diesler
Subject: jboss-4.0-testsuite-1.6
Build Failed
Importance: High

View results here - 

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

2006-05-23 Thread Rajesh Rajasekaran








Yes. Both jdk5 and jdk6 use the same lang
settings. Jdk5 just gives a warning whereas jdk6 gives an error for the same.

I ve unset the LANG settings. This seems
to fix this problem locally.



But now I get this error with jdk6

/home/rrajasekaran/jboss-4.0.x/server/src/main/org/jboss/ejb/plugins/cmp/jdbc/ByteArrayBlob.java:46:
org.jboss.ejb.plugins.cmp.jdbc.ByteArrayBlob is not abstract and does not
override abstract method getBinaryStream(long,long) in java.sql.Blob

public final class ByteArrayBlob
implements Blob

 ^













From: Scott M Stark 
Sent: Tuesday, May 23, 2006 9:28
AM
To: Rajesh Rajasekaran;
'jboss-development@lists.sourceforge.net'; '[EMAIL PROTECTED]'
Subject: RE:
jboss-4.0-testsuite-1.6 Build Failed





Ok, I see. We seem to be seeing this
encoding problem only on the linux systems. Is this box using the same lang env
as the jdk5 build? I don't see why jdk6 should fail if jdk5 is not.











From: Rajesh
Rajasekaran 
Sent: Tuesday, May 23, 2006 7:20
AM
To:
jboss-development@lists.sourceforge.net; '[EMAIL PROTECTED]'
Subject: RE:
jboss-4.0-testsuite-1.6 Build Failed

The testsuite is compiled irrespective of
the main builds success or failure.

The actual failures are in the
compile-build.log

http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-1.6/20060523061707/compile-build.log





_default:compile-classes: [mkdir] Created dir: /services/cruisecontrol/checkout/jboss-4.0-testsuite-1.6/jmx/output/classes [javac] Compiling 600 source files to /services/cruisecontrol/checkout/jboss-4.0-testsuite-1.6/jmx/output/classes/services/cruisecontrol/checkout/jboss-4.0-testsuite-1.6/jmx/src/main/test/implementation/modelmbean/AttributeCacheTEST.java:256: unmappable character for encoding UTF8 assertTrue(notif.getNewValue().equals(mit�vaan)); ^/services/cruisecontrol/checkout/jboss-4.0-testsuite-1.6/jmx/src/main/test/implementation/modelmbean/AttributeCacheTEST.java:266: unmappable character for encoding UTF8 server.setAttribute(name, new Attribute(Something, mit�vaan)); ^2 errorsBUILD FAILED/services/cruisecontrol/checkout/jboss-4.0-testsuite-1.6/tools/etc/buildmagic/buildmagic.ent:435: Compile failed; see the compiler error output for details.













From: Scott M Stark 
Sent: Tuesday, May 23, 2006 9:15
AM
To: [EMAIL PROTECTED]; Alexey
Loubyansky; Anil Saldhana; Bill Decoste; Bill Burke; Brian Stansberry; Clebert
Suconic; jboss-development@lists.sourceforge.net; [EMAIL PROTECTED];
QA; Ruel Loehr; Thomas Diesler
Subject: RE:
jboss-4.0-testsuite-1.6 Build Failed





the error seen in the
compile-testsuite.log:



/services/cruisecontrol/checkout/jboss-4.0-testsuite-1.6/testsuite/build.xml:294:
Reference ${webservice.classpath} not found.



does not match what I see. The errors I
see are due to expansion of the jdbc api, and the current mock objects not
implementing the extended interfaces:





compile-classes-only:
 [javac] Compiling 3090 source files to C:\cvs\JBoss4.0\jboss-4.0.x\testsuite
\output\classes
 [javac]
C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\src\main\org\jboss\test\jca\ad
apter\MockedXADataSource.java:50: org.jboss.test.jca.adapter.MockedXADataSource
is not abstract and does not override abstract method getQueryObjectGenerator()
in javax.sql.CommonDataSource
 [javac] public class MockedXADataSource
 [javac] ^
 [javac]
C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\src\main\org\jboss\test\jca\ad
apter\MockedXADataSource.java:123: org.jboss.test.jca.adapter.MockedXADataSource
.MockedXAConnection is not abstract and does not override abstract method
remove
StatementEventListener(javax.sql.StatementEventListener) in
javax.sql.PooledConn
ection
 [javac] public class MockedXAConnection

[javac] ^
 [javac]
C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\src\main\org\jboss\test\jca\ad
apter\MockedXADataSource.java:153:
org.jboss.test.jca.adapter.MockedXADataSource
.MockedXAConnection.MockedConnection is not abstract and does not override
abstr
act method createQueryObject(java.lang.Class) in java.sql.Connection
 [javac] class
MockedConnection
 [javac] ^
 [javac]
C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\src\main\org\jboss\test\jca\jd
bc\TestConnection.java:45: org.jboss.test.jca.jdbc.TestConnection is not
abstrac
t and does not override abstract method createQueryObject(java.lang.Class) in
ja
va.sql.Connection
 [javac] public class TestConnection implements Connection {
 [javac] ^
 [javac] C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\src\main\org\jboss\test\jca\jd
bc\TestStatement.java:41: org.jboss.test.jca.jdbc.TestStatement is not abstract
and does not override abstract method isClosed() in java.sql.Statement
 [javac] public class TestStatement
 [javac] ^
 [javac]
C:\cvs\JBoss4.0\jboss-4.0.x\testsuite\src\main\org\jboss\test\jca\jd
bc\TestPreparedStatement.java:47: org.jboss.test.jca.jdbc.TestPreparedStatement
is not abstract and does not override abstract method isPoolable() in
java.sql.P
reparedStatement
 [javac] public class TestPreparedStatement extends

[JBoss-dev] JBossTest 1.0.0.CR1 released

2006-05-16 Thread Rajesh Rajasekaran








JBossTest 1.0.0.CR1 has been released and is available for
download on Sourceforge at

http://sourceforge.net/project/showfiles.php?group_id=22866package_id=21938release_id=416399



Its available in the repository under jboss/test



This is the standalone release of the test module under JBAS
project. It is based on the junit test framework 

that lets you write test cases that run against the JBoss
Application Server.



This could be used by other JEMS projects like Portal, IDE
which requires to run tests against the JBoss App server.

Some of the features include:

- Create custom server configurations and control server
tasks like starting and stopping server from your test suite.

- Create multiple junit reports for the same test run
against different server configurations.



For more information, refer http://jboss.com/index.html?module=bbop=viewtopict=77475



Thanks

Rajesh

JBoss QA










[JBoss-dev] RE: jboss-4.0-testsuite Build Completed With Testsuite Errors

2006-05-13 Thread Rajesh Rajasekaran








This run is with JDK5.













From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Saturday, May 13, 2006 2:34
PM
To: jboss-development@lists.sourceforge.net;
QA; Scott M Stark
Subject: jboss-4.0-testsuite Build
Completed With Testsuite Errors
Importance: High





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




 
  
  TESTS
  FAILED
  
 
 
  
  Ant
  Error Message:/home/cruisecontrol/work/scripts/build-jboss-common.xml:235:
  The following error occurred while executing this line:
  /home/cruisecontrol/work/scripts/build-common-targets.xml:26: Build
  Successful - Tests completed with errors or failures.
  
 
 
  
  Date
  of build:05/13/2006 11:43:43
  
 
 
  
  Time
  to build:186 minutes 45 seconds
  
 
 
  
  Last
  changed:05/13/2006 10:46:21
  
 
 
  
  Last
  log entry:Get rid of the IOE
  logging as its being thrown
  
 









 
  
  
  
   

Unit Tests:
(3590) Total Errors and Failures: (11) 

   
   



 
  
  testSendMimeImageGIF
  
  
  org.jboss.test.webservice.attachment.AttachmentDIITestCase
  
 
 
  
  testSendMimeImageGIF
  
  
  org.jboss.test.webservice.attachment.AttachmentProxyTestCase
  
 
 
  
  test401Compatibility
  
  
  org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase
  
 
 
  
  testRMMResourceImplementsMBean
  
  
  org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase
  
 
 
  
  testMalformed
  
  
  org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase
  
 
 
  
  testMBeanInfoMarshalling
  
  
  org.jboss.test.jmx.test.RMIAdaptorUnitTestCase
  
 
 
  
  testSendMimeImageJPEG
  
  
  org.jboss.test.webservice.attachment.AttachmentDIITestCase
  
 
 
  
  testSendMimeImageJPEG
  
  
  org.jboss.test.webservice.attachment.AttachmentProxyTestCase
  
 
 
  
  testEchoMimeImageJPEG
  
  
  org.jboss.test.webservice.attachment.AttachmentProxyTestCase
  
 
 
  
  testSendMimeImageGIF
  
  
  org.jboss.test.webservice.attachment.AttachmentSAAJTestCase
  
 
 
  
  testSendMimeImageJPEG
  
  
  org.jboss.test.webservice.attachment.AttachmentSAAJTestCase
  
 













   
   












   
   









   
  
  
  
  
  
   

Modifications
since last build: (first 50 of 2) 

   
   

1.10.4.10


modified


starksm


security/src/main/org/jboss/security/ssl/DomainServerSocketFactory.java


Get rid of the IOE
logging as its being thrown

   
   

1.10.4.9


modified


starksm


security/src/main/org/jboss/security/ssl/DomainServerSocketFactory.java


Throw the IOE created
if there is a failure of the SSLServerSocket proxy

   
  
  
  
  
  
   



   
  
  
  
  
 













RE: [JBoss-dev] jbpm-db2-testsuite Build Failed

2006-05-12 Thread Rajesh Rajasekaran
Yes. They have been failing for a while now.
jBPM is undergoing a build restructuring (HEAD) and until Tom lets us
know when that would be ready and what the new structure looks like
these builds would be failing. I could disable them for the time being
until they are fixed.


Thanks
Rajesh

-Original Message-
From: Alexey Loubyansky 
Sent: Friday, May 12, 2006 6:45 AM
To: jboss-development@lists.sourceforge.net
Cc: Koen Aers; QA; Tom Baeyens
Subject: Re: [JBoss-dev] jbpm-db2-testsuite Build Failed

These are sent at least once a day for each db. Has it ever worked? Does

anyone care?

Thanks,

alex

[EMAIL PROTECTED] wrote:
 View results here - 

http://cruisecontrol.jboss.com/cc/buildresults/jbpm-db2-testsuite?log=lo
g20060512053729
 
 BUILD FAILED
 Ant Error 
 Message:
/home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:116: 
 The following error occurred while executing this line: 
 /home/cruisecontrol/work/scripts/build-jbpm-db-matrix.xml:41: Exit
code: 
 1 See build.log in Build Artifacts for details.
 Date of build: 05/12/2006 05:37:29
 Time to build: 55 seconds
 Last changed: 05/11/2006 08:39:55
 Last log entry: update the map file to accommodate new structure
 
  Unit Tests: (0)  Total Errors and Failures: (0)
 
  
 
  Modifications since last build:  (first 50 of 1727)
 1.3   deleted tbaeyens 
 src/java.jbpm/org/jbpm/persistence/JbpmPersistenceException.java
jbpm 
 new project structure
 1.10  deleted tbaeyens 
 src/java.jbpm/org/jbpm/persistence/PersistenceService.javajbpm new

 project structure
 1.15  deleted tbaeyens 
 src/java.jbpm/org/jbpm/persistence/db/DbPersistenceService.java
jbpm new 
 project structure
 1.9   deleted tbaeyens 
 src/java.jbpm/org/jbpm/persistence/db/DbPersistenceServiceFactory.java

 jbpm new project structure
 1.2   deleted tbaeyenssrc/java.jbpm/overview.html jbpm new
project structure
 1.26  deleted tbaeyens
src/java.jbpm/org/jbpm/JbpmConfiguration.java   jbpm 
 new project structure
 1.23  deleted tbaeyenssrc/java.jbpm/org/jbpm/JbpmContext.java
jbpm new 
 project structure
 1.4   deleted tbaeyens
src/java.jbpm/org/jbpm/JbpmException.java   jbpm new 
 project structure
 1.7   deleted tbaeyens
src/java.jbpm/org/jbpm/default.jbpm.cfg.xml jbpm 
 new project structure
 1.2   deleted tbaeyenssrc/java.jbpm/org/jbpm/package.html
jbpm new 
 project structure
 1.1   added   tbaeyens
jpdl/userguide/en/images/new.execution.jpg  jbpm new 
 project structure
 1.1   added   tbaeyens
jpdl/userguide/en/images/node.execute.method.gifjbpm 
 new project structure
 1.1   added   tbaeyens
jpdl/userguide/en/images/node.transition.classes.gif 
 jbpm new project structure
 1.1   added   tbaeyensjpdl/userguide/en/images/overview.gif
jbpm new 
 project structure
 1.1   added   tbaeyens
jpdl/userguide/en/images/persistence.api.gifjbpm new 
 project structure
 1.1   added   tbaeyens
jpdl/userguide/en/images/pluggable.architecture.gif 
 jbpm new project structure
 1.1   added   tbaeyens
jpdl/userguide/en/images/pojo.command.executor.gif 
 jbpm new project structure
 1.1   added   tbaeyens
jpdl/userguide/en/images/responsibility.matrix.gif 
 jbpm new project structure
 1.1   added   tbaeyens
jpdl/userguide/en/images/scheduler.classes.gif  jbpm 
 new project structure
 1.1   added   tbaeyens
jpdl/userguide/en/images/scheduler.overview.gif jbpm 
 new project structure
 1.1   added   tbaeyens
jpdl/userguide/en/images/service.orchestration.jpg 
 jbpm new project structure
 1.1   added   tbaeyens
jpdl/userguide/en/images/task.controllers.jpg   jbpm 
 new project structure
 1.1   added   tbaeyens 
 jpdl/userguide/en/images/traditional.bpm.approach.jpg jbpm new project

 structure
 1.1   added   tbaeyens
jpdl/userguide/en/images/transition.take.method.gif 
 jbpm new project structure
 1.1   added   tbaeyens
jpdl/userguide/en/images/two.dim.fragmentation.jpg 
 jbpm new project structure
 1.1   added   tbaeyens
jpdl/userguide/en/images/update.erp.example.gif jbpm 
 new project structure
 1.1   added   tbaeyensjpdl/userguide/en/images/wait.state.jpg
jbpm new 
 project structure
 1.1   added   tbaeyens
jpdl/userguide/en/images/workflow.landscape.gif jbpm 
 new project structure
 1.1   added   tbaeyensjpdl/userguide/en/modules/async.xml
jbpm new project 
 structure
 1.1   added   tbaeyensjpdl/userguide/en/modules/calendar.xml
jbpm new 
 project structure
 1.1   added   tbaeyens
jpdl/userguide/en/modules/configuration.xml jbpm new 
 project structure
 1.1   added   tbaeyensjpdl/userguide/en/modules/context.xml
jbpm new 
 project structure
 1.1   added   tbaeyensjpdl/userguide/en/modules/database.xml
jbpm new 
 project structure
 1.1   added   tbaeyensjpdl/userguide/en/modules/deployment.xml
jbpm new 
 project structure
 1.1   added   tbaeyensjpdl/userguide/en/modules/developers.xml
jbpm new 
 project structure
 1.1   added   tbaeyens

[JBoss-dev] RE: JBossTest 1.0.0.CR1 released

2006-05-12 Thread Rajesh Rajasekaran
Yes I could write an article explaining the features of the server
controller tasks and the other functionalities in the package. Is there
anything specific I should stress on?


Thanks
Rajesh

-Original Message-
From: Bill Burke 
Sent: Friday, May 12, 2006 3:03 PM
To: Rajesh Rajasekaran
Cc: jboss-development@lists.sourceforge.net; QA
Subject: Re: JBossTest 1.0.0.CR1 released

Great work Rajesth.  We have needed this for a *LONG* time.  Now you 
need to write an article about this stuff.  Interested?  I'm sure we can

get OnJava.com to publish it.

Bill

Rajesh Rajasekaran wrote:
 
 
 JBossTest 1.0.0.CR1 has been released and is available for download on

 Sourceforge at
 

http://sourceforge.net/project/showfiles.php?group_id=22866package_id=2
1938release_id=416399 

http://sourceforge.net/project/showfiles.php?group_id=22866package_id=
21938release_id=416399 
 
 
  
 
 Its available in the repository under jboss/test
 
  
 
 This is the standalone release of the test module under JBAS project.
It 
 is based on the junit test framework
 
 that lets you write test cases that run against the JBoss Application 
 Server.
 
  
 
 This could be used by other JEMS projects like Portal, IDE which 
 requires to run tests against the JBoss App server.
 
 Some of the features include:
 
 - Create custom server configurations and control server tasks like 
 starting and stopping server from your test suite.
 
 - Create multiple junit reports for the same test run against
different 
 server configurations.
 
  
 
 For more information, refer 
 http://jboss.com/index.html?module=bbop=viewtopict=77475 
 http://jboss.com/index.html?module=bbop=viewtopict=77475
 
  
 
 Thanks
 
 Rajesh
 
 JBoss QA
 
  
 

-- 
Bill Burke
Chief Architect
JBoss Inc.


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] JBossCache 1.4.0.Beta released

2006-05-11 Thread Rajesh Rajasekaran








JBossCache 1.4.0.Beta has been released and is available on
sourceforge at

http://sourceforge.net/project/showfiles.php?group_id=22866package_id=102339release_id=416206



JBossCache 1.4.0.Beta has also been updated in the
repository.





Thanks

Rajesh

JBoss QA










[JBoss-dev] JBossCache 1.3.0.SP2 released

2006-05-09 Thread Rajesh Rajasekaran








JBossCache 1.3.0.SP2 has been released and is available on
sourceforge at

http://sourceforge.net/project/showfiles.php?group_id=22866package_id=102339release_id=415758



JBossCache 1.3.0.SP2 has also been updated in the
repository.





Thanks

Rajesh

JBoss QA








[JBoss-dev] RE: JBossCache 1.3.0.SP2 released

2006-05-09 Thread Rajesh Rajasekaran








Has anybody had problems downloading from osdn.dl.sourceforge.net
immediately after the release.

I was able to verify this only from a few
mirrors which had picked up the release and I had to wait for a while.





Thanks

Rajesh











From: Rajesh
Rajasekaran 
Sent: Tuesday, May 09, 2006 3:30
PM
To:
jboss-development@lists.sourceforge.net
Cc: QA
Subject: JBossCache 1.3.0.SP2
released





JBossCache 1.3.0.SP2 has been released and is available on
sourceforge at

http://sourceforge.net/project/showfiles.php?group_id=22866package_id=102339release_id=415758



JBossCache 1.3.0.SP2 has also been updated in the
repository.





Thanks

Rajesh

JBoss QA








[JBoss-dev] jBPM 3.1.1 released

2006-05-08 Thread Rajesh Rajasekaran








jBPM 3.1.1 and jBPM Process Designer 3.0.9.1 was released on
Friday.

They can be downloaded from the following locations:



http://sourceforge.net/project/showfiles.php?group_id=70542package_id=145174release_id=414797

http://sourceforge.net/project/showfiles.php?group_id=70542package_id=116692release_id=414820





Thanks

Rajesh

JBoss QA










[JBoss-dev] JBossSerialization 1.0.0.GA released

2006-05-03 Thread Rajesh Rajasekaran








JBossSerialization 1.0.0.GA has been released and is
available for download at 



http://sourceforge.net/project/showfiles.php?group_id=22866package_id=188754release_id=414632



JBossSerialization 1.0.0.GA has also been updated in the
repository.





Thanks

Rajesh

JBoss QA








[JBoss-dev] RE: Change to HEAD Build. Microcontainer now binary dependency.WASRE: jboss-head-jdk-matrix Build Failed

2006-05-02 Thread Rajesh Rajasekaran
Are the container and kernel modules jboss-container 
jboss-microkernel as explained in the checkout instructions in the
wiki, or are they just container  microkernel 



-Original Message-
From: Adrian Brock 
Sent: Tuesday, May 02, 2006 4:37 PM
To: Ryan Campbell
Cc: Adrian Brock; Scott M Stark; QA;
jboss-development@lists.sourceforge.net
Subject: RE: Change to HEAD Build. Microcontainer now binary
dependency.WASRE: jboss-head-jdk-matrix Build Failed

You will just need to checkout the container/dependency/kernel projects
manually (they are no longer a part of the jboss-head alias).
Using whatever tag was added for that release. 

Other than that, it will be the same.

It shouldn't affect AOP. Only AOP2.0 (which hasn't been released yet)
has a dependency on container.

On Tue, 2006-05-02 at 16:20 -0500, Ryan Campbell wrote:
 Will removing these modules from jboss-head prevent previous releases
of
 ejb3, aop  microcontainer from being built?
 
 I guess the answer is no, but the checkout instructions have changed?
 
 -Original Message-
 From: Adrian Brock 
 Sent: Tuesday, May 02, 2006 2:21 PM
 To: Scott M Stark
 Cc: Adrian Brock; Ryan Campbell; QA;
 jboss-development@lists.sourceforge.net
 Subject: Change to HEAD Build. Microcontainer now binary dependency.
 WASRE: jboss-head-jdk-matrix Build Failed
 
 This has been done, except the cruisecontrol changes.
 I've left some other issues open for a more complete standalone build:
 http://jira.jboss.com/jira/browse/JBMICROCONT-87
 
 The updated build instructions are here:
 http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMicrocontainer
 if you already have a previous head checked out, the only change
 is that these projects won't automatically be a part of the main
build.
 
 The version of the microcontainer used is a snapshot from
 earlier this afternoon. Which will be updated to 2.0.0M1
 when that is finalised.
 
 On Tue, 2006-05-02 at 16:26 +0200, Adrian Brock wrote:
  On Tue, 2006-05-02 at 09:07 -0500, Scott M Stark wrote:
It would potentially be possible to require the MC projects 
to be developed against head while still being thirdparty 
binaries in the main jboss-head build.
i.e. You would checkout the projects separately into the head
 tree.
   Meaning just dropping them from the jboss-head module alias and
 manually
   checking
   them out into it? If that is the case this should just be done
   independent of the svn move just to decouple the mc code from
jboss5
 as
   currently the only user of these is ejb3 as far as I can see. We
 just
   need the mc artifacts pushed out to the repository.
   
  
  Ok, I'll do this. If you want to use JDK5 features, we
  should also look at make jboss retro binaries.
  
  I'll make JBoss-Head build on the JBossMC-1.0.2.GA
  binaries. Besides the bean deployer in varia, only EJB3
  is using it until JBossMC-2.0.0M1 is finished.
  
  Then I'll update the WIKI page on how to develop
  the microcontainer until we have a proper standalone build.
  
  Cruisecontrol will also need updating once this is done.
-- 

Adrian Brock
Chief Scientist
JBoss Inc.




---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid0709bid3057dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] JBossCache 1.4.0.Alpha released

2006-05-01 Thread Rajesh Rajasekaran








JBossCache 1.4.0.Alpha has been released and is available
for download at 

http://sourceforge.net/project/showfiles.php?group_id=22866package_id=102339release_id=414179



JBossCache 1.4.0.Alphahas also been updated in the
repository.





Thanks

Rajesh

JBoss QA










[JBoss-dev] JBossCache 1.3.0.SP1 released

2006-04-18 Thread Rajesh Rajasekaran










JBossCache 1.3.0.SP1 has been released and is available for
download at 

http://sourceforge.net/project/showfiles.php?group_id=22866package_id=102339release_id=410896



JBossCache 1.3.0.SP1 has also been updated in the
repository.





Thanks

Rajesh

JBoss QA










[JBoss-dev] RE: jbossweb build.29 Build Fixed

2006-04-06 Thread Rajesh Rajasekaran








Please ignore this mail. We are still
working on getting the JBossWeb builds on different platforms.





Thanks

Rajesh











From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 06, 2006
11:01 AM
To:
jboss-development@lists.sourceforge.net; QA
Subject: jbossweb build.29 Build
Fixed





View results here - http://cruisecontrol.jboss.com/cc/buildresults/jbossweb?log=log20060406114538Lbuild.29




 
  
  BUILD
  COMPLETE- build.29
  
 
 
  
  Date
  of build:04/06/2006 11:45:38
  
 
 
  
  Time
  to build:14 minutes 53 seconds
  
 









 
  
  
  
   

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

   
   



 
  
  
  
 













   
   












   
   









   
  
  
  
  
  
   

Modifications
since last build: (first 50 of 0) 

   
  
  
  
  
  
   



   
  
  
  
  
 













[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

RE: [JBoss-dev] jboss-head-jdk-matrix Build Failed

2006-04-03 Thread Rajesh Rajasekaran
The quiet period of activity on cruisecontrol is 7 mins. 
The change to build-distr.xml was not in the quiet period but after the
modification check for the last jboss-head-jdk-matrix build.
Last changed: 04/03/2006 05:57:42
Last log entry: Make this compile

The change should be picked up in the next build.

Thanks
Rajesh

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott M Stark
Sent: Monday, April 03, 2006 11:59 AM
To: jboss-development@lists.sourceforge.net
Cc: Jason T. Greene; Thomas Diesler
Subject: RE: [JBoss-dev] jboss-head-jdk-matrix Build Failed

The current build-distr.xml looks to have been corrected. I really doubt
that the crusecontrol detection of a quiet period of activity is either
broken or not long enough as these transient build breaks happen often.

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Clebert Suconic
 Sent: Monday, April 03, 2006 9:39 AM
 To: jboss-development@lists.sourceforge.net
 Cc: Jason T. Greene; Thomas Diesler
 Subject: RE: [JBoss-dev] jboss-head-jdk-matrix Build Failed
 
 Geez... still broken:
 
 http://cruisecontrol.jboss.com/cc/artifacts/jboss-head-jdk-mat
 rix/200604
 03061941/compile.log
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Tim Fox
 Sent: Friday, March 31, 2006 10:14 PM
 Cc: jboss-development@lists.sourceforge.net; Jason T. Greene; 
 Thomas Diesler
 Subject: Re: [JBoss-dev] jboss-head-jdk-matrix Build Failed
 
 ok, hacked it to make it build.
 
 lucky we're not using web services
 
 Tim Fox wrote:
  It's 5am, we're going through the release procedure for 
 JBossMessaging
 
  1.0, updated from CVS to build the release bundle, and HEAD 
 is broken!
  
  If any one from web services is listening please *fix this* 
 we are NOT
 
  very happy bunnies right now
  
  [EMAIL PROTECTED] wrote:
  
  View results here -
 
 http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-
 matrix?log
 =log20060331153535 
 
 
  BUILD FAILED
  Ant Error Message: 
  
 /services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The 
  following error occurred while executing this line:
  
 /services/cruisecontrol/work/scripts/build-jboss-common.xml:64: Exit
  code: 1 See compile.log in Build Artifacts for details.
  Date of build: 03/31/2006 15:35:35
  Time to build: 19 minutes 25 seconds
  Last changed: 03/31/2006 15:28:35
  Last log entry: convert jbws383 to wstools
 
   Unit Tests: (0)  Total Errors and Failures: (0)
 
   
 
   Modifications since last build:  (first 50 of 77)
  1.3deletedjgreene 
  testsuite/src/resources/webservice/jbws383/config.xmlconvert 
  jbws383 to wstools
  1.1addedjgreene 
  testsuite/src/resources/webservice/jbws383/wstools-config.xml
  convert jbws383 to wstools
  1.3modifiedjgreene 
  
 testsuite/src/resources/webservice/jbws383/WEB-INF/jaxrpc-mapping.xml
 
  convert jbws383 to wstools
  1.3modifiedjgreene 
  testsuite/src/resources/webservice/jbws383/WEB-INF/webservices.xml
  convert jbws383 to wstools
  1.3modifiedjgreene 
 
 testsuite/src/resources/webservice/jbws383/WEB-INF/wsdl/TestSe
 rvice.wsdl
 
  convert jbws383 to wstools
  1.3modifiedjgreene 
 
 testsuite/src/main/org/jboss/test/webservice/jbws381/WeatherFo
 recastSoap
 Impl.java 
  Convert jbws381 to wstools
  1.3modifiedjgreene 
 
 testsuite/src/main/org/jboss/test/webservice/jbws381/WeatherFo
 recasts.ja
 va 
  Convert jbws381 to wstools
  1.3deletedjgreene 
  testsuite/src/resources/webservice/jbws381/config.xmlConvert 
  jbws381 to wstools
  1.1addedjgreene 
  testsuite/src/resources/webservice/jbws381/wstools-config.xml
  Convert jbws381 to wstools
  1.3modifiedjgreene 
  
 testsuite/src/resources/webservice/jbws381/WEB-INF/jaxrpc-mapping.xml
 
  Convert jbws381 to wstools
  1.3deletedjgreene 
  testsuite/src/resources/webservice/jbws377/config.xmlconvert 
  jbws377 to wstools
  1.1addedjgreene 
  testsuite/src/resources/webservice/jbws377/wstools-config.xml
  convert jbws377 to wstools
  1.3modifiedjgreene 
  
 testsuite/src/resources/webservice/jbws377/WEB-INF/jaxrpc-mapping.xml
 
  convert jbws377 to wstools
  1.3modifiedjgreene 
  testsuite/src/resources/webservice/jbws377/WEB-INF/webservices.xml
  convert jbws377 to wstools
  1.3modifiedjgreene 
 
 testsuite/src/resources/webservice/jbws377/WEB-INF/wsdl/HelloS
 ervice.wsd
 l 
  convert jbws377 to wstools
  1.1addedjgreene 
  testsuite/src/resources/webservice/jbws358/wstools-config.xml
  convert jbws358 to wstools
  1.3modifiedjgreene 
 
 testsuite/src/resources/webservice/jbws358/META-INF/jaxrpc-map
 ping.xml 
  convert jbws358 to wstools
  1.3modifiedjgreene 
  testsuite/src/resources/webservice/jbws358/META-INF/webservices.xml
  convert jbws358 to wstools
  1.3modifiedjgreene 
 
 

[JBoss-dev] JBossCache 1.3.0.GA released

2006-04-03 Thread Rajesh Rajasekaran








JBossCache 1.3.0.GA Wasabi has been released
and is available for download at 

http://sourceforge.net/project/showfiles.php?group_id=22866package_id=102339release_id=406920



JBossCache 1.3.0.GA has also been updated in the
repository.





Thanks

Rajesh

JBoss QA








[JBoss-dev] JBossCache 1.3.0.CR1 released

2006-03-21 Thread Rajesh Rajasekaran








JBossCache 1.3.0.CR1 has been released.

This can be downloaded from http://sourceforge.net/project/showfiles.php?group_id=22866package_id=102339release_id=403608





Thanks
Rajesh

JBoss QA








[JBoss-dev] jboss-4.0 testsuite failures

2006-03-15 Thread Rajesh Rajasekaran










Heres a list of the tests that have been failing in the
4.0 branch for more than a few weeks.

Along with that is the JIRA task associated with each failure.

These issues would be included in the 4.0.4.CR2 release.



org.jboss.test.cmp2.audit.test.AuditUnitTestCase(JACC+SecurityMgr)

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



org.jboss.test.naming.test.SimpleUnitTestCase

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



org.jboss.test.security.test.WebConstraintsUnitTestCase

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



org.jboss.test.util.test.PropertyEditorsUnitTestCase

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



org.jboss.test.webservice.jbws309.JBWS309TestCase(JACC)

org.jboss.test.webservice.jbws309.JBWS309TestCase(JACC+SecurityMgr)

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





Thanks

Rajesh








[JBoss-dev] JBossCache 1.3.0 Beta1 Released

2006-03-02 Thread Rajesh Rajasekaran








JBossCache version 1.3.0 Beta1 has been released.



This can be downloaded from https://sourceforge.net/project/showfiles.php?group_id=22866package_id=102339release_id=398120







Thanks

Rajesh

JBoss QA








RE: [JBoss-dev] FW: Could not run jacorb on 64 bit jdk

2006-02-22 Thread Rajesh Rajasekaran
We were able to run the tests which uses Jacorb on a 64-bit JVM. We
compiled the JBoss build using a 32-bit JVM to avoid the Jacorb
compilation problem and used a 64-bit JVM to run the testsuite. 
We were not getting the VerifyError at runtime. This happens only during
IDL compilation.

The compilation error occurs with SUN jdk1.4 and jrockit-1.4 64-bit
JVM's.
It does not occur with jrockit-1.5 64 bit JVM.

Thanks
Rajesh

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Francisco Reverbel
Sent: Tuesday, February 14, 2006 1:08 PM
To: Ryan Campbell
Cc: jboss-development@lists.sourceforge.net; Francisco Reverbel
Subject: RE: [JBoss-dev] FW: Could not run jacorb on 64 bit jdk

Yes, I see that the VerifyError is thrown when you run the IDL compiler.
It looks like a JVM bug.

Even though I know JacORB's implementation of the ORB run-time library
fairly well, I have never looked at the IDL compiler. Do you know if a
VerifyError also happens at run time, with JacORB's ORB on a 64-bit JVM?
Or the problem happens only during IDL compilation?
 
On Mon, 2006-02-13 at 17:11 -0600, Ryan Campbell wrote:
 Francisco,
 
  
 
 Just to make it clear, we are trying to build JBoss on 64bit JVM's and
 we get this fatal exception when trying to run the jacorb parser:
 
  
 
 Exception in thread main java.lang.VerifyError: (class:
org/jacorb/idl/parser,
 method: clinit signature: ()V) Call to wrong initialization method 
 
  
 
 Can you patch this?  We aren't getting a response from the jacorb
 list.
 
  
 

 __
 From:[EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
 Rajesh Rajasekaran
 Sent: Monday, February 13, 2006 5:04 PM
 To: jboss-development@lists.sourceforge.net
 Cc: Francisco Reverbel
 Subject: [JBoss-dev] FW: Could not run jacorb on 64 bit jdk
 
 
  
 
  
 
  
 

 __
 From: Rajesh Rajasekaran 
 Sent: Friday, February 10, 2006 12:05 PM
 To: '[EMAIL PROTECTED]'
 Subject: Could not run jacorb on 64 bit jdk
 
 
  
 
 This is related to the bug #468
 
 http://www.jacorb.org/cgi-bin/bugzilla/long_list.cgi?buglist=468
 
  
 
 We are trying to support Jboss on 64 bit jdk's and this bug is a major
 blocker.
 
 A fix for this ASAP would help us proceed with our process.
 
  
 
 Thanks
 
 Rajesh 
 
 JBoss QA
 
 



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


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

2006-02-22 Thread Rajesh Rajasekaran
I will put jboss-head to the end and rearrange the list as Julien had
requested.
The portlet tests against jboss-head had failed and the report XML's
were not well-formed, hence the failures not reported by CC.
I have opened a task for this. Here s the link.
http://jira.jboss.com/jira/browse/JBPORTAL-679


Thanks
Rajesh

-Original Message-
From: Ryan Campbell 
Sent: Wednesday, February 22, 2006 3:54 PM
To: Julien Viet; Rajesh Rajasekaran
Cc: QA; jboss-development@lists.sourceforge.net
Subject: RE: jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors

Rajesh, can we put jboss-head at the end?

If there is only one failure on jboss-head, perhaps we could raise the
issue for the portal team to fix.  Having Portal 2.4 compatible with
Jboss 5.0 would be a nice thing to have if it's easy.

If it's a big deal to fix, we should remove jboss-head from the matrix
so we can have a clean build.

-Original Message-
From: Julien Viet 
Sent: Wednesday, February 22, 2006 3:38 PM
To: Rajesh Rajasekaran
Cc: QA; Anil Saldhana; [EMAIL PROTECTED]; Chris Laprun;
jboss-development@lists.sourceforge.net; QA; Julien Viet;
[EMAIL PROTECTED]; Thomas Heute
Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors

jboss-head (JBoss 5) is not today a target for us but we can test it of 
course.

Here is the list that I would like to see :

- Branch_4_0
- 4.0.4RC1 (later 4.0.4)
- 4.0.3SP1 (already done)


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


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

2006-02-20 Thread Rajesh Rajasekaran
I guess portal uses an old version of junit(from 2001). The newer
version might solve the problem. 
Anyways these are the errors I get.

[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.dispatcher.spec.DispatcherTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletconfig.PortletConfigTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletinterface.PortletInterfaceTestCase.xml is not a
valid XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletmode.PortletModeTestCase.xml is not a valid XML
document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletrequest.PortletRequestTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletsession.PortletSessionTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.preferences.PreferencesTestCase.xml is not a valid XML
document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.renderresponse.RenderResponseTestCase.xml is not a valid
XML document. It is possibly corrupted.



-Original Message-
From: Julien Viet 
Sent: Monday, February 20, 2006 4:41 PM
To: Rajesh Rajasekaran
Cc: QA; [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA; Julien
Viet
Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors

how can we do to improve that (i.e fix the wellformedness) ?

Rajesh Rajasekaran wrote:
 The junit reports (xml) for the portlet tests are not well formed.
 
 Hence the portlet test results are not accounted in the HTML reports
shown.
 
 The common and format tests pass 100%.
 
 Please refer the link below for the portlet test reports.
 

http://cruisecontrol.jboss.com/cc/artifacts/jboss-portal-2.4-testsuite/2
0060220170427/jboss-4.0.3SP1-logs/results/testfailures
 
  
 
 Please let me know if you have the same problem.
 
  
 
 Thanks
 
 Rajesh
 
  
 
  
 


 
 *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 *Sent:* Monday, February 20, 2006 4:07 PM
 *To:* [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA; Julien 
 Viet; QA
 *Subject:* jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors
 *Importance:* High
 
  
 
 View results here - 

http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.4-testsuit
e?log=log20060220170427
 
 *TESTS FAILED*
 
 *Ant 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:199: 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/20/2006 17:04:27
 
 *Time to build: *1 minute 58 seconds
 
 *Last changed: *02/20/2006 09:17:02
 
 *Last log entry: *JBPORTAL-608 : Timed content is not serializable and

 raise issues in http session replication
 
  
 
  Unit Tests: (84)  Total Errors and Failures: (0)
 
 All Tests Passed
 
   
 
  
 
   
 
  
 
  
 
   
 
  
 
   
 
  
 
   
 
  
 
  
 
   
 
  
 
   
 
  
 
   
 
  
 
  
 
   
 
  
 
   
 
  
 
  
 
  Modifications since last build:  (first 50 of 26)
 
 1.4
 
   
 
 modified
 
   
 
 julien
 
   
 

server/src/main/org/jboss/portal/server/output/cache/SoftTimedContent.ja
va
 
   
 
 JBPORTAL-608 : Timed content is not serializable and raise issues in 
 http session replication
 
 1.3
 
   
 
 modified
 
   
 
 julien
 
   
 

server/src/main

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

2006-02-20 Thread Rajesh Rajasekaran
The xml reports are generated. The error from the junitreport task
deletes the contents of the malformed xml's.


-Original Message-
From: Ryan Campbell 
Sent: Monday, February 20, 2006 5:37 PM
To: Rajesh Rajasekaran; Julien Viet
Cc: QA; '[EMAIL PROTECTED]'; 'jboss-development@lists.sourceforge.net'
Subject: RE: jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors

I see two things here:

1. The xml reports are empty, causing the XML validation errors.  I
guess no one has even looked at these yet?!

2.  The Portlet test cases don't extend org.junit.TestCase, they extend
java.lang.Object.  That might work in your IDE, but I doubt we should
expect AntRunner to put it up with it.

-Original Message-
From: Rajesh Rajasekaran 
Sent: Monday, February 20, 2006 5:22 PM
To: Julien Viet
Cc: QA; [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA
Subject: RE: jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors

I guess portal uses an old version of junit(from 2001). The newer
version might solve the problem. 
Anyways these are the errors I get.

[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.dispatcher.spec.DispatcherTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletconfig.PortletConfigTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletinterface.PortletInterfaceTestCase.xml is not a
valid XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletmode.PortletModeTestCase.xml is not a valid XML
document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletrequest.PortletRequestTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.portletsession.PortletSessionTestCase.xml is not a valid
XML document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.preferences.PreferencesTestCase.xml is not a valid XML
document. It is possibly corrupted.
[junitreport] [Fatal Error] :-1:-1: Premature end of file.
[junitreport] The file
/home/test_cc/work/checkout/jboss-portal-2.4/portlet/TEST-org.jboss.port
al.test.portlet.renderresponse.RenderResponseTestCase.xml is not a valid
XML document. It is possibly corrupted.



-Original Message-
From: Julien Viet 
Sent: Monday, February 20, 2006 4:41 PM
To: Rajesh Rajasekaran
Cc: QA; [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA; Julien
Viet
Subject: Re: jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors

how can we do to improve that (i.e fix the wellformedness) ?

Rajesh Rajasekaran wrote:
 The junit reports (xml) for the portlet tests are not well formed.
 
 Hence the portlet test results are not accounted in the HTML reports
shown.
 
 The common and format tests pass 100%.
 
 Please refer the link below for the portlet test reports.
 

http://cruisecontrol.jboss.com/cc/artifacts/jboss-portal-2.4-testsuite/2
0060220170427/jboss-4.0.3SP1-logs/results/testfailures
 
  
 
 Please let me know if you have the same problem.
 
  
 
 Thanks
 
 Rajesh
 
  
 
  
 


 
 *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 *Sent:* Monday, February 20, 2006 4:07 PM
 *To:* [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net; QA; Julien 
 Viet; QA
 *Subject:* jboss-portal-2.4-testsuite Build Completed With Testsuite
Errors
 *Importance:* High
 
  
 
 View results here - 

http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.4-testsuit
e?log=log20060220170427
 
 *TESTS FAILED*
 
 *Ant 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:199: The 
 following error occurred while executing this line: 
 /services/cruisecontrol

[JBoss-dev] FW: Could not run jacorb on 64 bit jdk

2006-02-13 Thread Rajesh Rajasekaran




















From: Rajesh
Rajasekaran 
Sent: Friday, February 10, 2006
12:05 PM
To: '[EMAIL PROTECTED]'
Subject: Could not run jacorb on
64 bit jdk





This is related to the bug #468

http://www.jacorb.org/cgi-bin/bugzilla/long_list.cgi?buglist=468



We are trying to support Jboss on 64 bit jdks and
this bug is a major blocker.

A fix for this ASAP would help us proceed with our process.



Thanks

Rajesh 

JBoss QA








RE: [JBoss-dev] Re: FW: jboss-remoting-testsuite-1.5 Thread Dump

2006-01-24 Thread Rajesh Rajasekaran
);
 
}
 
  
 
  
 


 
 *From:* Rajesh Rajasekaran
 *Sent:* Monday, January 23, 2006 4:54 PM
 *To:* Ryan Campbell
 *Subject:* RE: jboss-remoting-testsuite-1.5 Build Completed With 
 Testsuite Errors
 
  
 
 Stack trace of thread dump
 
  
 
 [junit] Running org.jboss.test.remoting.util.PortUtilTestCase
 
 [junit] Full thread dump Java HotSpot(TM) Server VM (1.5.0_03-b07 
 mixed mode):
 
  
 
 [junit] Low Memory Detector daemon prio=1 tid=0x8df3a4e0 
 nid=0x4ec5 runnable [0x..0x]
 
  
 
 [junit] CompilerThread1 daemon prio=1 tid=0x8df39140 nid=0x4ec4 
 waiting on condition [0x..0x8da79788]
 
  
 
 [junit] CompilerThread0 daemon prio=1 tid=0x8df38200 nid=0x4ec3 
 waiting on condition [0x..0x8dafa708]
 
  
 
 [junit] AdapterThread daemon prio=1 tid=0x8df37280 nid=0x4ec2 
 waiting on condition [0x..0x]
 
  
 
 [junit] Signal Dispatcher daemon prio=1 tid=0x8df36460
nid=0x4ec1 
 waiting on condition [0x..0x]
 
  
 
 [junit] Finalizer daemon prio=1 tid=0x8df2cad0 nid=0x4ec0 in 
 Object.wait() [0x8de7e000..0x8de7e770]
 
 [junit] at java.lang.Object.wait(Native Method)
 
 [junit] - waiting on 0x925138d0 (a 
 java.lang.ref.ReferenceQueue$Lock)
 
 [junit] at 
 java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
 
 [junit] - locked 0x925138d0 (a
java.lang.ref.ReferenceQueue$Lock)
 
 [junit] at 
 java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
 
 [junit] at 
 java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
 
  
 
 [junit] Reference Handler daemon prio=1 tid=0x8df2be90
nid=0x4ebf 
 in Object.wait() [0x8deff000..0x8deff6f0]
 
 [junit] at java.lang.Object.wait(Native Method)
 
 [junit] - waiting on 0x9254a538 (a
java.lang.ref.Reference$Lock)
 
 [junit] at java.lang.Object.wait(Object.java:474)
 
 [junit] at 
 java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
 
 [junit] - locked 0x9254a538 (a java.lang.ref.Reference$Lock)
 
  
 
 [junit] main prio=1 tid=0x0805d188 nid=0x4eb7 waiting on
condition 
 [0xbfffb000..0xbfffc118]
 
 [junit] at java.lang.Thread.sleep(Native Method)
 
 [junit] at 

org.jboss.test.remoting.util.PortUtilTestCase.testFindingFreePorts(PortU
tilTestCase.java:83)
 
 [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native

 Method)
 
 [junit] at 

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
 
 [junit] at 

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
 
 [junit] at java.lang.reflect.Method.invoke(Method.java:585)
 
 [junit] at junit.framework.TestCase.runTest(TestCase.java:154)
 
 [junit] at junit.framework.TestCase.runBare(TestCase.java:127)
 
 [junit] at
junit.framework.TestResult$1.protect(TestResult.java:106)
 
 [junit] at 
 junit.framework.TestResult.runProtected(TestResult.java:124)
 
 [junit] at junit.framework.TestResult.run(TestResult.java:109)
 
 [junit] at junit.framework.TestCase.run(TestCase.java:118)
 
 [junit] at
junit.framework.TestSuite.runTest(TestSuite.java:208)
 
 [junit] at junit.framework.TestSuite.run(TestSuite.java:203)
 
 [junit] at 

org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTe
stRunner.java:289)
 
 [junit] at 

org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUni
tTestRunner.java:656)
 
 [junit] at 

org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitT
estRunner.java:558)
 
  
 
 [junit] VM Thread prio=1 tid=0x8df29310 nid=0x4ebe runnable
 
  
 
 [junit] GC task thread#0 (ParallelGC) prio=1 tid=0x080e3930 
 nid=0x4eba runnable
 
  
 
 [junit] GC task thread#1 (ParallelGC) prio=1 tid=0x080e3d18 
 nid=0x4ebb runnable
 
  
 
 [junit] GC task thread#2 (ParallelGC) prio=1 tid=0x080e4100 
 nid=0x4ebc runnable
 
  
 
 [junit] GC task thread#3 (ParallelGC) prio=1 tid=0x080e48e0 
 nid=0x4ebd runnable
 
  
 
 [junit] VM Periodic Task Thread prio=1 tid=0x8df3ba00 nid=0x4ec6

 waiting on condition
 
  
 


 
 *From:* Ryan Campbell
 *Sent:* Monday, January 23, 2006 2:57 PM
 *To:* Tom Elrod
 *Cc:* QA
 *Subject:* RE: jboss-remoting-testsuite-1.5 Build Completed With 
 Testsuite Errors
 
  
 
  
 
 I guess this is an intermittent problem?  
 



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=kkid3432bid#0486dat1642

Re: [JBoss-dev] jboss-seam-testsuite Build Failed

2006-01-09 Thread Rajesh Rajasekaran
jboss-seam builds are set up on cruisecontrol. Currently the build and the test targets are run.Since the build is failing i am not able to gather the test results and have them on cruisecontrol.Once the build succeeds i can put the testsuite results on cruisecontrol.
ThanksRajeshOn 1/9/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:



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

BUILD FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-seam-testsuite.xml
:34: Exit code: 1   See compile.log in Build Artifacts for details.Date of build:01/09/2006 12:31:21Time to build:20 seconds





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

Modifications since last builds:(first 50 of 0)