The ejb3 testsuite servers fail to start.
I guess they need to be updated to deal with the new location of javassist?
Caused by: java.lang.NoClassDefFoundError: javassist/NotFoundException at
Of
Ryan CampbellSent: 29 March 2006 15:34To:
jboss-development@lists.sourceforge.netSubject: [JBoss-dev] RE:
ejb3-4.0-testsuite Build Failed
The ejb3 testsuite
servers fail to start. I guess they need to be updated to deal with the
new location of javassist?
Caused
@lists.sourceforge.netSubject: RE: [JBoss-dev] RE:
ejb3-4.0-testsuite Build Failed
I removed javassist.jar from the jboss-aop.deployer and
jboss-aop-jdk50.deployer (in _module-aspects-most in
build-distr.xml).Itseems javassist is not getting copied to the
lib directory when building using jdk 5
Am finished adding the remoting-int module (see JBAS-2698). The jar
produced (and put in the lib directory of default and all server config)
is jboss-remoting-int.jar (instead of jbossas-remoting.jar, which is how
it is in HEAD).
I am not sure if/where there will need to be any adjustments
The ejb3-ssl-advanced test server is
broken:
2006-01-30 20:09:06,202 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package
The class that is not being found is within jbossas-remoting.jar. This
is part of JBossAS code base and not remoting. Only way this would be
called to be loaded is if was configured to use the JBossAS security
domain via configuration. So am guessing the jar was excluded from the
build?
I think I get the mis-match now. This is being build out of JBoss 4.x
branch, right? If so, then the code for jbossas-remoting.jar is not
there. There is an issue for this (JBAS-2698), which I will work on today.
Tom Elrod wrote:
The class that is not being found is within
] On
Behalf Of Scott M Stark
Sent: Saturday, January 21, 2006 10:12 PM
To: jboss-development@lists.sourceforge.net; Bill Burke
Subject: RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
So after profiling this the problem looks to be recent
changes in org.jboss.util.timeout.TimeoutFactory
10:12 PM
To: jboss-development@lists.sourceforge.net; Bill Burke
Subject: RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
So after profiling this the problem looks to be recent
changes in org.jboss.util.timeout.TimeoutFactory as the leaks
are related to transaction timeouts
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Scott M Stark
Sent: Saturday, January 21, 2006 10:12 PM
To: jboss-development@lists.sourceforge.net; Bill Burke
Subject: RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
So after profiling this the problem looks
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Scott M Stark
Sent: Saturday, January 21, 2006 10:12 PM
To: jboss-development@lists.sourceforge.net; Bill Burke
Subject: RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
So after profiling this the problem
10:12 PM
To: jboss-development@lists.sourceforge.net; Bill Burke
Subject: RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
So after profiling this the problem looks to be recent
changes in org.jboss.util.timeout.TimeoutFactory as the leaks
are related to transaction timeouts
@lists.sourceforge.net
Subject: Re: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
On Sun, 2006-01-22 at 08:30, Tom Elrod wrote:
So how should the be addressed when using 1.4? I just
added used of
Timer for client side leases within remoting.
I think we should reinstate the old code
the
java.util.Timer internals.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Scott M Stark
Sent: Saturday, January 21, 2006 10:12 PM
To: jboss-development@lists.sourceforge.net; Bill Burke
Subject: RE: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
So after
The current ejb3 testfailure is due to an incomplete
integration of the remoting:
http://jira.jboss.com/jira/browse/JBAS-2698
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Sunday, January 22, 2006
10:47 AM
To: Adrian Brock; Bill Decoste; Bill Burke; Gavin King;
This is just the org.jboss.ejb3.test.microbench.unit.BenchUnitTestCase
requiring too much memory. Memory usage during this test goes from 40m
to 130m even using the default config so the memory usage of this needs
to be looked at.
-Original Message-
From: Bill Burke
Sent: Sunday,
@lists.sourceforge.net
Subject: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed
This is just the org.jboss.ejb3.test.microbench.unit.BenchUnitTestCase
requiring too much memory. Memory usage during this test goes
from 40m to 130m even using the default config so the memory
usage of this needs
Looks like the tests are using HA-JNDI's multicast crap. I also have
trouble running on 64MB.
Scott M Stark wrote:
The tests are failing at the point of shutting down the server and I'm seeing this
test-with-jvmargs:
[delete] Deleting:
I should restate. The HA-JNDI multicast crap seems to leak memory and I
have problems with it with a low heap space. The build-test.xml is
looking for a node0.jndi.url and it is not set by default in
local.properties. This is QA's crap. Ask them about it.
Bill Burke wrote:
Looks like the
The tests are failing at the point of shutting down the server and I'm seeing this test-with-jvmargs:
[delete] Deleting: /services/cruisecontrol/work/checkout/ejb3-4.0-testsuite/ejb3/output/log/test.log
[junit] Running org.jboss.ejb3.test.microbench.unit.BenchUnitTestCase
[junit]
20 matches
Mail list logo
