RE: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
Hi, --- Jason Dillon [EMAIL PROTECTED] wrote: This is so retarded. Shutdown does work, it is the automation which is whacked out. The automation is not shutting it down, it is the jboss_redhat_init script. After you shutdown, wait and if it is still running after n seconds then kill it, This is being done. no need to keep wasting bits to email this rather useless notification. But then why waste time trying the shutdown if no one is going to know the difference? If perhaps it was a problem with the container not shutting down properly because the jvm is locked up in socket io and needs to be forcefully exited, there is nothing that Shutdown can do. This is the job of the user and or application which makes use of it. This latest problem is with the jboss_init_redhat script. It calls the Shutdown class directly - it needs to be redone to use the Shutdown.sh or vice versa. Regards, Chris = __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
Ok. Why don't you fix the init script? Or open a bug and I will eventually get around to it. --jason -Original Message- From: [EMAIL PROTECTED] [mailto:jboss- [EMAIL PROTECTED]] On Behalf Of Chris Kimpton Sent: Thursday, June 13, 2002 11:44 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work Hi, --- Jason Dillon [EMAIL PROTECTED] wrote: This is so retarded. Shutdown does work, it is the automation which is whacked out. The automation is not shutting it down, it is the jboss_redhat_init script. After you shutdown, wait and if it is still running after n seconds then kill it, This is being done. no need to keep wasting bits to email this rather useless notification. But then why waste time trying the shutdown if no one is going to know the difference? If perhaps it was a problem with the container not shutting down properly because the jvm is locked up in socket io and needs to be forcefully exited, there is nothing that Shutdown can do. This is the job of the user and or application which makes use of it. This latest problem is with the jboss_init_redhat script. It calls the Shutdown class directly - it needs to be redone to use the Shutdown.sh or vice versa. Regards, Chris = __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
Hi, The org.jboss.Shutdown class does not seem to work. This is failing because the jnet.jar has moved. I presume that shutdown.sh also fails too - since that has not changed etiher. jnet.jar is now in several places (ie the configs) - all, default, minimal and client. Is it safe to assume that one of these directories will always be present? Or perhaps jnet.jar should be moved into the lib directory - or even the bin directory - since we have a shutdown.jar which relies on it... See ya, Chris PS Come on Engurrland (and Ireland) = __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
Shutdown just does an http post and does not use JNDI so why should it need jnet.jar? I am able to run shudown with a 1.3 vm without the jnet.jar in my classpath so post the error you are seeing bin 609shutdown.sh Shutting down server localhost:8082 Shutdown complete Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Chris Kimpton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, June 13, 2002 12:01 AM Subject: Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work Hi, The org.jboss.Shutdown class does not seem to work. This is failing because the jnet.jar has moved. I presume that shutdown.sh also fails too - since that has not changed etiher. jnet.jar is now in several places (ie the configs) - all, default, minimal and client. Is it safe to assume that one of these directories will always be present? Or perhaps jnet.jar should be moved into the lib directory - or even the bin directory - since we have a shutdown.jar which relies on it... See ya, Chris ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
Alright, the main version has been completely rewritten to use the RMI connector. The invariant location for client libs is the jboss-home/client directory. I have updated the scripts to refer to this. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Chris Kimpton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, June 13, 2002 11:09 AM Subject: Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work Hi, This is with the IBM jdk on linux: Exception in thread main java.lang.NoClassDefFoundError: javax/net/SocketFactory at org.jnp.interfaces.NamingContextFactory.getInitialContext(NamingContextFacto ry.java:38) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:669) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.init(InitialContext.java:179) at org.jboss.Shutdown.main(Shutdown.java:172) HTH, Chris PS I'll switch to running one ibm jdk and one sun one to see if that affects it. ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
This is so retarded. Shutdown does work, it is the automation which is whacked out. After you shutdown, wait and if it is still running after n seconds then kill it, no need to keep wasting bits to email this rather useless notification. If perhaps it was a problem with the container not shutting down properly because the jvm is locked up in socket io and needs to be forcefully exited, there is nothing that Shutdown can do. This is the job of the user and or application which makes use of it. --jason -Original Message- From: [EMAIL PROTECTED] [mailto:jboss- [EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, June 13, 2002 6:40 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work = ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.3.1_03 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03) Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE Hello, The org.jboss.Shutdown class does not seem to work. That is, the jboss_redhat_init.sh script called it and the jboss server did not stop... Please could we get this fixed... Or tell me what I should be calling to get the server shutdown... Now I will return to the old faithful method - kill -9 See ya, Chris PS This is automated - just to make it really annoying... ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
Hi, This should be fixed now - it seems jnet.jar is now required as well as the shutdown.jar. Regards, Chris = -- http://www.soccer2002.org.uk - The Game is On! __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
You may have to explicity `shutdown.sh --server localhost` or `shutdown.sh --shutdown` when working from HEAD, as help will be displayed with no arguments. --jason Quoting [EMAIL PROTECTED]: = ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.3.1 Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.3.1-02a-FCS) Java HotSpot(TM) Client VM (build Blackdown-1.3.1_02a-FCS, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE Hello, The org.jboss.Shutdown class does not seem to work. That is, the jboss_redhat_init.sh script called it and the jboss server did not stop... Please could we get this fixed... Or tell me what I should be calling to get the server shutdown... Now I will return to the old faithful method - kill -9 See ya, Chris PS This is automated - just to make it really annoying... ___ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development - This mail sent through IMP: http://horde.org/imp/ ___ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
Can someone look into why this started happening again. And if it is a problem on the server side can we fix it so that it accuratly reports when the server does not shutdown. Please. --jason [EMAIL PROTECTED] wrote: = ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.3.1 Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.3.1-02a-FCS) Java HotSpot(TM) Client VM (build Blackdown-1.3.1_02a-FCS, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE Hello, The org.jboss.Shutdown class does not seem to work. That is, the jboss_redhat_init.sh script called it and the jboss server did not stop... Please could we get this fixed... Or tell me what I should be calling to get the server shutdown... Now I will return to the old faithful method - kill -9 See ya, Chris PS This is automated - just to make it really annoying... ___ 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
RE: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
ok, I'm new to the list, but this strikes me as nuts, can we ban this gimp from the list? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 22 April 2002 05:58 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work = ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.4.0 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92) Java HotSpot(TM) Server VM (build 1.4.0-b92, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE Hello, The org.jboss.Shutdown class does not seem to work. That is, the jboss_redhat_init.sh script called it and the jboss server did not stop... Please could we get this fixed... Or tell me what I should be calling to get the server shutdown... Now I will return to the old faithful method - kill -9 See ya, Chris PS This is automated - just to make it really annoying... ___ 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
RE: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
Yes, sure!, simply submit a patch that corrects the bug ;) (see detail of the problem below) -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de [EMAIL PROTECTED] Envoyé : lundi, 22 avril 2002 15:51 À : [EMAIL PROTECTED] Objet : RE: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work ok, I'm new to the list, but this strikes me as nuts, can we ban this gimp from the list? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 22 April 2002 05:58 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work = ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.4.0 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92) Java HotSpot(TM) Server VM (build 1.4.0-b92, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE Hello, The org.jboss.Shutdown class does not seem to work. That is, the jboss_redhat_init.sh script called it and the jboss server did not stop... Please could we get this fixed... Or tell me what I should be calling to get the server shutdown... Now I will return to the old faithful method - kill -9 See ya, Chris PS This is automated - just to make it really annoying... ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
I mean the fact that he is automating his mail, this list has enough traffic without that. -Original Message- From: Sacha Labourey [mailto:[EMAIL PROTECTED]] Sent: 22 April 2002 06:55 To: Sean O'Donnell; [EMAIL PROTECTED] Subject: RE: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work Yes, sure!, simply submit a patch that corrects the bug ;) (see detail of the problem below) -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de [EMAIL PROTECTED] Envoyé : lundi, 22 avril 2002 15:51 À : [EMAIL PROTECTED] Objet : RE: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work ok, I'm new to the list, but this strikes me as nuts, can we ban this gimp from the list? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 22 April 2002 05:58 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work = ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.4.0 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92) Java HotSpot(TM) Server VM (build 1.4.0-b92, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE Hello, The org.jboss.Shutdown class does not seem to work. That is, the jboss_redhat_init.sh script called it and the jboss server did not stop... Please could we get this fixed... Or tell me what I should be calling to get the server shutdown... Now I will return to the old faithful method - kill -9 See ya, Chris PS This is automated - just to make it really annoying... ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
on 1-12-22 16.51, [EMAIL PROTECTED] at [EMAIL PROTECTED] wrote: Please could we get this fixed... It is just the snobosish code genius that hinders this ! ... hehe ... haha hohoho ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
I recall back when i was looking at the undependencys that : -the callchain used by jboss_redhat_init.sh stop is using these MBeans JMX:name=Connector,type=RMI Adaptor:name=html JBOSS-SYSTEM:service=Naming and when they go out of scope (naming) ... no more is logged ? ... --so those MBeans should be excluded in a shutdown from the JBOSS-SYSTEM:spine=ServiceController ... then this AUTOMATED message will disappear ... ---one way would be to defer unloading those, to lastly unload from main ? ... so maybe introduce a exclude list in ServiceController and also use the same list to close those last and after the ServiceController is unloaded ... as I recall not closing them explicitly did not disturb logging or restart (hanged ServerSockets) ... so Just exluding them works ! ... /peter_f If we knew what it was we were doing, it would not be called research, would it? -Einstein ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
Hi, --- Scott M Stark [EMAIL PROTECTED] wrote: Send the VM a SIGQUIT to generate a thread dump to help establish what it hanging up the shutdown. I've done that - the results are here: http://lubega.com/javacore18046.1007985620.txt Although I am not sure what to look for I've changed the build to save up to 3 of the server.log files - also the console and the above javacore output, from now on... HTH, Chris = Need somewhere to Live in London? - Then go to http://freeflats.com __ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
Hi, The Sun test is still running... For the record, the sun test failed the same as the IBM one... Chris ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
on 1-12-09 11.06, Chris Kimpton at [EMAIL PROTECTED] wrote: The message The database is closed as Embbeded HSQLDB is writing out this message for every channel connection it has ... when the JVM decides to GC ... I will update HypersonicDatabase so it identifyes itself throught its own log instance ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
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
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
[EMAIL PROTECTED] wrote: 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. I had the webIntegration test timeout yesterday... I ctrl-c the batch and then ran it again and it was fine. I cant replicate reliably the timeout myself. :( Although initially it happened when I excluded the XAUnitTest, although that makes no sense at all. Al ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
So you are saying that the Sun VM hangs? I am not understanding this completly... and well, these logs don't really help to clearify it for me. I have checked on my Linux + Sun 1.3.1 VM that org.jboss.Shutdown works. I simply started up a new VM, then shut it down again. The problem could be that the VM is getting the shutdown command, but hangs durring shutdown... which is another problem altogether. Can you check through the logs and make sure there are messages from org.jboss.system.Shutdown. If all vms are getting these messages and at least attempt to shutdown, then org.jboss.Shutdown is not the problem. --jason On Sun, 9 Dec 2001, Chris Kimpton wrote: 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
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
Please make this email stop. --jason On Mon, 10 Dec 2001 [EMAIL PROTECTED] wrote: = ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = HERE ARE THE LAST 50 LINES OF THE LOG FILE Hello, The org.jboss.Shutdown class does not seem to work. That is, the jboss_redhat_init.sh script called it and the jboss server did not stop... Please could we get this fixed... Or tell me what I should be calling to get the server shutdown... Now I will return to the old faithful method - kill -9 See ya, Chris PS This is automated - just to make it really annoying... ___ 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
Re: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
Send the VM a SIGQUIT to generate a thread dump to help establish what it hanging up the shutdown. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, December 09, 2001 8:46 PM Subject: [JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work = ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = HERE ARE THE LAST 50 LINES OF THE LOG FILE Hello, The org.jboss.Shutdown class does not seem to work. That is, the jboss_redhat_init.sh script called it and the jboss server did not stop... Please could we get this fixed... Or tell me what I should be calling to get the server shutdown... Now I will return to the old faithful method - kill -9 See ya, Chris PS This is automated - just to make it really annoying... ___ 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
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? --jason On Sun, 9 Dec 2001 [EMAIL PROTECTED] wrote: = ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = HERE ARE THE LAST 50 LINES OF THE LOG FILE Hello, The org.jboss.Shutdown class does not seem to work. That is, the jboss_redhat_init.sh script called it and the jboss server did not stop... Please could we get this fixed... Or tell me what I should be calling to get the server shutdown... Now I will return to the old faithful method - kill -9 See ya, Chris PS This is automated - just to make it really annoying... ___ 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
