These VMs also failed to run all of the tests and the client log shows
several
timeout failures, some of which make no sense. For example, the
WebIntegrationUnitTestCase should run in ~ 10 seconds and yet it is
failing due to a timeout. The DynLoadingUnitTestCase should run in < 5
seconds and it is also timing out. After a point it seems that every unit
test simply failed with a timeout error, and yet the total run time is less
than
the run that completed 160 tests. It should be longer since the timeout per
unit test is 10 minutes.

http://lubega.com/testarchive/cronjob-test-20011209-1009.log

    [junit] TEST org.jboss.test.web.test.WebIntegrationUnitTestCase FAILED
(timeout)
    [junit] Running org.jboss.test.entityexc.test.EntityExcUnitTestCase
    [junit] TEST org.jboss.test.entityexc.test.EntityExcUnitTestCase FAILED
(timeout)

tests-client-unit:
    [junit] Running org.jboss.test.jrmp.test.DynLoadingUnitTestCase
    [junit] TEST org.jboss.test.jrmp.test.DynLoadingUnitTestCase FAILED
(timeout)

tests-security-basic-unit:
    [junit] Running org.jboss.test.security.test.EJBSpecUnitTestCase
    [junit] TEST org.jboss.test.security.test.EJBSpecUnitTestCase FAILED
(timeout)
    [junit] Running org.jboss.test.security.test.LoginContextUnitTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.748 sec
    [junit] Running
org.jboss.test.security.test.NamespacePermissionsUnitTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.996 sec
    [junit] Running org.jboss.test.security.test.PermissionNameUnitTestCase
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.888 sec

tests-standard-stress:
    [junit] Running org.jboss.test.bank.test.BankStressTestCase
    [junit] TEST org.jboss.test.bank.test.BankStressTestCase FAILED
(timeout)
    [junit] Running org.jboss.test.cts.test.StatelessSessionStressTestCase
    [junit] TEST org.jboss.test.cts.test.StatelessSessionStressTestCase
FAILED (timeout)
    [junit] Running org.jboss.test.hello.test.HelloTimingStressTestCase
    [junit] TEST org.jboss.test.hello.test.HelloTimingStressTestCase FAILED
(timeout)
    [junit] Running org.jboss.test.jbossmq.perf.JBossMQPerfStressTestCase
    [junit] TEST org.jboss.test.jbossmq.perf.JBossMQPerfStressTestCase
FAILED (timeout)
    [junit] Running org.jboss.test.lock.test.EnterpriseEntityStressTestCase
    [junit] TEST org.jboss.test.lock.test.EnterpriseEntityStressTestCase
FAILED (timeout)
    [junit] Running org.jboss.test.perf.test.PerfStressTestCase
    [junit] TEST org.jboss.test.perf.test.PerfStressTestCase FAILED
(timeout)

----- Original Message -----
From: "Chris Kimpton" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, December 09, 2001 2:06 AM
Subject: Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work


> Hi,
>
> ----- Original Message -----
> From: "Jason Dillon" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Sunday, December 09, 2001 5:24 AM
> Subject: Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not
work
>
>
> > This seems to work for me.  Why are you having trouble with it.  What
can
> we
> > do to get automated message to stop?
> >
>
> The easy answer is you stop the message by making it work - this is
nothing
> new.
>
> Looking at the log files - it failed for the IBM and Blackdown (native
> threads) JDKs, but worked for the Blackdown (green threads) version.
>
> The Sun test is still running...
>
>
> Both the IBM and Blackdown (native) logs end similarly:
>
> Blackdown (native):
> *************************
>
> 2001-12-09 06:40:16,687 INFO  [org.jboss.deployment.J2eeDeployer#Default]
> Destroying application entityexc.jar
> 2001-12-09 06:40:16,689 INFO  [org.jboss.deployment.J2eeDeployer#Default]
> Destroyed
> 2001-12-09 06:40:16,690 INFO  [org.jboss.deployment.J2eeDeployer#Default]
> Stopping module jbosstest-web.war
> 2001-12-09 06:40:16,692 INFO  [org.jboss.jetty.JettyService] Stopped
> JBossWebApplicationContext$JBossSXSecurityHandler in
>
WebApplicationContext[/jbosstest,file:/disk/orig/home/lubega/jbossro/jboss-a
> ll/build/output/testbuild/deploy/Default/jbosstest-web.ear/web1021/]
> 2001-12-09 06:40:16,694 INFO  [org.jboss.jetty.JettyService] Stopped
> SecurityHandler in
>
WebApplicationContext[/jbosstest,file:/disk/orig/home/lubega/jbossro/jboss-a
> ll/build/output/testbuild/deploy/Default/jbosstest-web.ear/web1021/]
> 2001-12-09 06:40:16,696 INFO  [org.jboss.jetty.JettyService] Stopped
> WebInfProtect
> 2001-12-09 06:40:16,699 INFO  [org.jboss.jetty.JettyService] Stopped
> FilterHandler in
>
WebApplicationContext[/jbosstest,file:/disk/orig/home/lubega/jbossro/jboss-a
> ll/build/output/testbuild/deploy/Default/jbosstest-web.ear/web1021/]
> 2001-12-09 06:40:16,705 INFO  [org.jboss.jetty.JettyService]
> SecureEJBServlet: destroy
> 2001-12-09 06:40:16,708 INFO  [org.jboss.jetty.JettyService]
> ClientLoginServlet: destroy
> 2001-12-09 06:40:16,710 INFO  [org.jboss.jetty.JettyService] ENCServlet:
> destroy
> 2001-12-09 06:40:16,712 INFO  [org.jboss.jetty.JettyService]
SecureServlet:
> destroy
> 2001-12-09 06:40:16,738 INFO  [Default] The database is closed as Embbeded
> 2001-12-09 06:40:16,740 INFO  [Default] hsqldb serverSocket closed
> 2001-12-09 06:40:16,741 INFO  [Default] Calling hsqldb
closeServerSocket();
> 2001-12-09 06:40:16,744 INFO  [org.jboss.jetty.JettyService]
> UserTransactionServlet: destroy
> 2001-12-09 06:40:16,746 INFO  [org.jboss.jetty.JettyService] EJBServlet:
> destroy
> 2001-12-09 06:40:16,749 INFO  [org.jboss.jetty.JettyService]
> UnsecureEJBServlet: destroy
> 2001-12-09 06:41:03,210 INFO  [Default] The database is closed as Embbeded
> 2001-12-09 06:41:45,877 DEBUG [org.jboss.pool.PoolGCThread] gc thread
> running gc
>
>
>
> IBM :
> ***************
>
> 2001-12-09 04:33:53,947 DEBUG [org.jboss.system.ServiceController]
> undeploying JBossMQ:service=MessageCache from server
> 2001-12-09 04:33:53,948 INFO  [org.jboss.mq.pm.file.CacheStore] Stopping
> 2001-12-09 04:33:53,948 INFO  [org.jboss.mq.pm.file.CacheStore] Stopped
> 2001-12-09 04:33:53,948 DEBUG [org.jboss.system.ServiceController]
> undeploying JBossMQ:service=CacheStore from server
> 2001-12-09 04:33:53,955 INFO  [org.jboss.jdbc.HypersonicDatabase] Stopping
> 2001-12-09 04:33:54,364 INFO  [org.jboss.jdbc.HypersonicDatabase] Database
> closed clean
> 2001-12-09 04:33:54,365 INFO  [org.jboss.jdbc.HypersonicDatabase] Stopped
> 2001-12-09 04:33:54,365 DEBUG [org.jboss.system.ServiceController]
> undeploying JBOSS-SYSTEM:service=Hypersonic from server
> 2001-12-09 04:33:54,366 INFO  [org.jboss.deployment.J2eeDeployer#Default]
> Stopping
> 2001-12-09 04:33:54,375 INFO  [org.jboss.deployment.J2eeDeployer#Default]
> Undeploying all applications.
> 2001-12-09 04:33:56,212 INFO  [Default] The database is closed as Embbeded
> 2001-12-09 04:33:56,212 INFO  [Default] hsqldb serverSocket closed
> 2001-12-09 04:33:56,213 INFO  [Default] The database is closed as Embbeded
> 2001-12-09 04:33:56,225 INFO  [Default] Calling hsqldb
closeServerSocket();
> 2001-12-09 04:34:07,557 DEBUG [org.jboss.pool.PoolGCThread] gc thread
> running gc
> 2001-12-09 04:34:56,511 INFO  [Default] The database is closed as Embbeded
>
>
> The message "The database is closed as Embbeded" only appears in these
> logs - not the working one - perhaps JBoss is thinking it is in an
Embedded
> environment and using different code - that does not work? - to shutdown?
>
> HTH,
> Chris
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to