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-devel
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
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 W
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
0
to temporarily workaround the issue.
>
> >
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
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 sensa
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 co
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
> Subjec
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 DE
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
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
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,
and this is also a problem in the 1.3.5 release of aop. We probably need a
1.4.0 release o
It looks like aop 1.3.4 is not compatible with javassist 3.2.0.CR1, but this is how I interpreted Kabir’s 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 t
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 i
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
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 didn’t include it for some reason?
http
It looks like javax.jws.WebService is
missing from jbossws14.jar. This was working yesterday, so I think this update
to the repository didn’t include it for some reason?
http://fisheye.jboss.com/changelog/JBoss/repository.jboss.com?cs=MAIN:tdiesler:20060324094641
stack trace:
The connectivity to the server is broken as these are
trivial tests that take little time, for example:
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 tests
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]
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/hiber
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.jbo
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
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]
23 matches
Mail list logo
