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
The all server starts with an error in
HAJNDI:
2006-03-29 09:05:40,711 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=HAJNDI2006-03-29 09:05:40,711 DEBUG [org.jboss.ha.jndi.HANamingService] Creating jboss:service=HAJNDI2006-03-29 09:05:40,711 DEBUG
I've just fixed it.
The problem was the regular expression changes in JMX.
Why HAJNDI needs to run a query to find the partition beats me. ;-)
On Wed, 2006-03-29 at 10:01 -0600, Ryan Campbell wrote:
The all server starts with an error in HAJNDI:
2006-03-29 09:05:40,711 DEBUG
Its only integrated when building with j2se1.4.x which is
why I was not seeing it. Can you trigger another testsuite run as I have not
seen one since I have updated the jacc configs.
From: Ryan Campbell Sent: Thursday,
March 23, 2006 5:44 PMTo: Scott M Stark; '[EMAIL PROTECTED]';
I just triggered a testsuite run.
From: Scott M Stark
Sent: Friday, March 24, 2006 11:00
AM
To: Ryan Campbell; '[EMAIL PROTECTED]'; 'jboss-development@lists.sourceforge.net'
Subject: RE: jboss-4.0-testsuite
Build Completed With Testsuite Errors
Its only integrated when
Hmmm, probably related to the EJB3 jacc failures?
Ryan Campbell wrote:
All these JACC tests are failing, and the jacc-security-mgr logs show this:
java.lang.NoSuchMethodException:
org.jboss.security.jacc.SecurityService.setObjectName(javax.management.ObjectName)
at
That is an irrelevant debug level log message indicating
that the does not have a setter for injecting the xmbean object name. It has no
affect on the jacc service. I'm looking at the failures.
From: Ryan Campbell Sent: Thursday,
March 23, 2006 3:03 PMTo: [EMAIL PROTECTED];
This is failing under 1.4.2 because javassist is not
getting pulled into the jacc config:
2006-03-23
15:59:02,535 ERROR [org.jboss.deployment.MainDeployer] Could not create
deployment:
I'm not seeing the
jbossretro-rt.jar anywhere in the current 4.0 build, and my workspace is up to
date. Has this been integrated into the dist structure yet?
http://fisheye.jboss.com/changelog/JBoss/build/jboss?cs=Branch_4_0:rcampbell:20060323050136
I see it in the cruisecontrol
The txtimer errors are due to previous deployments not getting cleaned
up due to OOMEs:
2006-03-20 13:20:21,455 WARN [org.jboss.system.ServiceController]
Problem start
ing service jboss.j2ee:jndiName=test/txtimer/TimerTest,service=EJB
java.lang.OutOfMemoryError
...
2006-03-20 13:20:25,895 INFO
I don't see these txtimer errors running the tests by
itself. I'll check the run logs to see if there is something
obvious.
[EMAIL PROTECTED] testsuite]$ run_tests.shant
-Dtest=org.jboss.test.txtimer.test.CreateCancelTestCase -Dnojars=t
-Djunit.timeout=180
11 matches
Mail list logo
