Re: [JBoss-user] jboss-jetty problem - stack traces
Hhmmm... That's the trouble, you add code to make something more robust, and end up just introducing a new problem. I'll stick up a new build tonight and this one will fly ! I don't understand how I managed to deploy onto my copy last night - perhaps we are using very different config files. My listener started fine. Speak to you later, Jules --- David Castro-Diephouse [EMAIL PROTECTED] wrote: Hi Jules. We've still got a hitch in the new version. Now the web server is not starting up at all. Here's what is happening. In JettyService.startService, you added a check to Jetty.isStarted = HttpServer.isStarted. This call is not doing what you want though. HttpServer.isStarted checks with its LogSink, its Listeners, and its Contexts. If ANY of the above are started, it returns true. I have a JBoss-deployed war. JBoss WarDeployer service runs before the Jetty service, and when it deploys my context Jetty.deploy starts the context. Then, when Jetty goes to start up, it finds out that one context is started, and concludes that the server is started. Unfortunately no listeners are started so we are screwed. It occurs to me though that I could work around by moving the Jetty service above the WarDeployer in jboss.jcml. Checking... Yes. The workaround fixes the problem. It still would be better if it would work without tweaking the jboss.jcml file though. I guess you could have Jetty explicitly keep track of whether or not it has been started. Maybe you will see something better. I have to get to bed! Thanks for the quick turnaround Jules. Dave Julian Gosnell wrote: Scott, David and Matt, I am just checking JBoss-2.2.2_Jetty-3.1.RC5-4.tgz into jboss/binaries. It should appear at : http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/binaries/JBoss-2.2.2_Jetty-3.1.RC5-4.tgz in an hour or so. If you would like to give it a whirl, click on Revision 1.1 and it should start to download (Netscape) failing this try Save as on the link. If I get feedback from you that your problem is fixed we will make this a release. Thanks for all your interest. Jules Scott M Stark wrote: Neither trace 3 or 4 are correct as they originate from the org.jboss.util.ServiceControl class. Looking at the 2.2 branch I see the change in service life-cycle management I mentioned was not incorporated into that release and this is the problem. If there is enough demand a 2.2.3 release could be made. The 2.4 release beta will start tomorrow. - Original Message - From: David Castro-Diephouse [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 20, 2001 8:52 PM Subject: Re: [JBoss-user] jboss-jetty problem - stack traces Here are 4 stack traces: 1. From ServiceControl.handleNotification, registering an MBean for the HttpServer. 2. From ServiceControl.handleNotification, registering an MBean for the WebApplicationContext. 3. HttpServer.start calls start on the WebApplicationContext. 4. JMX starts up my WebApplicationContext a second time. (this is probably what you are looking for Scott) ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jboss-jetty problem - stack traces
Julian Gosnell wrote: I don't understand how I managed to deploy onto my copy last night - perhaps we are using very different config files. My listener started fine. I think all you should need to reproduce is: jboss.jcml has JettyService mbean at the bottom. Put a war in the jboss/deploy directory BEFORE starting the server. tomcat-test.ear will do for testing purposes. Start the server. ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jboss-jetty problem - stack traces
I'll try this tonight. Jules --- David Castro-Diephouse [EMAIL PROTECTED] wrote: Julian Gosnell wrote: I don't understand how I managed to deploy onto my copy last night - perhaps we are using very different config files. My listener started fine. I think all you should need to reproduce is: jboss.jcml has JettyService mbean at the bottom. Put a war in the jboss/deploy directory BEFORE starting the server. tomcat-test.ear will do for testing purposes. Start the server. ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jboss-jetty problem - stack traces
I had a look at this on the train this morning. Scott is right. In 2.2.2 any MBean registering is presumed to be a JBoss Service and JBoss takes over it's lifecycle, calling init(), start(), stop() and destroy() whenever it deems necessary. This is pretty disastrous for internal Jetty MBeans, which unfortunately have methods of the same name, which would rather have their lifecycles managed by Jetty ! On the Main CVS line, MBean Services must now explicitly register() if they want JBoss to manage their lifecycles. I shall try to do a new JBoss-2.2.2-Jetty release this evening, in which externalisation of internal Jetty MBeans will be pulled, awaiting a JBoss release which supports them - a shame, but I doubt it will actually affect anyone... Thanks to everyone who has reported this problem, Jules --- Scott M Stark [EMAIL PROTECTED] wrote: Neither trace 3 or 4 are correct as they originate from the org.jboss.util.ServiceControl class. Looking at the 2.2 branch I see the change in service life-cycle management I mentioned was not incorporated into that release and this is the problem. If there is enough demand a 2.2.3 release could be made. The 2.4 release beta will start tomorrow. - Original Message - From: David Castro-Diephouse [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 20, 2001 8:52 PM Subject: Re: [JBoss-user] jboss-jetty problem - stack traces Here are 4 stack traces: 1. From ServiceControl.handleNotification, registering an MBean for the HttpServer. 2. From ServiceControl.handleNotification, registering an MBean for the WebApplicationContext. 3. HttpServer.start calls start on the WebApplicationContext. 4. JMX starts up my WebApplicationContext a second time. (this is probably what you are looking for Scott) ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jboss-jetty problem - stack traces
--On Thursday, June 21, 2001 9:47 AM +0100 Julian Gosnell [EMAIL PROTECTED] wrote: I shall try to do a new JBoss-2.2.2-Jetty release this evening, in which externalisation of internal Jetty MBeans will be pulled, awaiting a JBoss release which supports them - a shame, but I doubt it will actually affect anyone... Yes, but didn't Scott also say it would be fixed in jBoss 2.4? They are frozen, so I expect we'll see that in a few weeks (just a guess everyone - I have nothing to do with it). So that's not long at all. Good things come to those who wait! Thanks Jules and Scott! Jim I shall be telling this with a sigh Somewhere ages and ages hence: Two roads diverged in a wood, and I - I took the one less traveled by, And that has made all the difference. - Robert Frost, 1916 ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jboss-jetty problem - stack traces
Scott, David and Matt, I am just checking JBoss-2.2.2_Jetty-3.1.RC5-4.tgz into jboss/binaries. It should appear at : http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/binaries/JBoss-2.2.2_Jetty-3.1.RC5-4.tgz in an hour or so. If you would like to give it a whirl, click on Revision 1.1 and it should start to download (Netscape) failing this try Save as on the link. If I get feedback from you that your problem is fixed we will make this a release. Thanks for all your interest. Jules Scott M Stark wrote: Neither trace 3 or 4 are correct as they originate from the org.jboss.util.ServiceControl class. Looking at the 2.2 branch I see the change in service life-cycle management I mentioned was not incorporated into that release and this is the problem. If there is enough demand a 2.2.3 release could be made. The 2.4 release beta will start tomorrow. - Original Message - From: David Castro-Diephouse [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 20, 2001 8:52 PM Subject: Re: [JBoss-user] jboss-jetty problem - stack traces Here are 4 stack traces: 1. From ServiceControl.handleNotification, registering an MBean for the HttpServer. 2. From ServiceControl.handleNotification, registering an MBean for the WebApplicationContext. 3. HttpServer.start calls start on the WebApplicationContext. 4. JMX starts up my WebApplicationContext a second time. (this is probably what you are looking for Scott) ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jboss-jetty problem - stack traces
Hi Jules... I just installed the newest and started and I get the exception pasted below... Jim [Container factory] Starting [Container factory] Started [JBossMQ] Starting [JBossMQ] Cannot start the JMS server ! Invalid configuration. [JBossMQ] javax.jms.JMSException: Invalid configuration. [JBossMQ] at org.jbossmq.server.PersistenceManager.init(PersistenceManag er.java:107) [JBossMQ] at org.jbossmq.server.StartServer.run(StartServer.java:170) [JBossMQ] at org.jbossmq.server.StartServer.start(StartServer.java:70) [JBossMQ] at org.jbossmq.server.JBossMQService.startService(JBossMQService .java:66) [JBossMQ] at org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport. java:93) [JBossMQ] at java.lang.reflect.Method.invoke(Native Method) [JBossMQ] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl .java:1628) [JBossMQ] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl .java:1523) [JBossMQ] at org.jboss.util.ServiceControl.start(ServiceControl.java:97) [JBossMQ] at java.lang.reflect.Method.invoke(Native Method) [JBossMQ] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl .java:1628) [JBossMQ] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl .java:1523) [JBossMQ] at org.jboss.Main.init(Main.java:217) [JBossMQ] at org.jboss.Main$1.run(Main.java:121) [JBossMQ] at java.security.AccessController.doPrivileged(Native Method) [JBossMQ] at org.jboss.Main.main(Main.java:117) [JBossMQ] Linked Exception: [JBossMQ] javax.jms.JMSException: Could not open the queue's tranaction log: /C: /JBoss-2.2.2_Jetty-3.1.RC5-4/jboss/db/jbossmq/transactions.dat [JBossMQ] at org.jbossmq.persistence.SpyTxLog.throwJMSException(SpyTxLog.j ava:95) [JBossMQ] at org.jbossmq.persistence.SpyTxLog.init(SpyTxLog.java:35) [JBossMQ] at org.jbossmq.server.PersistenceManager.init(PersistenceManag er.java:104) [JBossMQ] at org.jbossmq.server.StartServer.run(StartServer.java:170) [JBossMQ] at org.jbossmq.server.StartServer.start(StartServer.java:70) [JBossMQ] at org.jbossmq.server.JBossMQService.startService(JBossMQService .java:66) [JBossMQ] at org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport. java:93) [JBossMQ] at java.lang.reflect.Method.invoke(Native Method) [JBossMQ] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl .java:1628) [JBossMQ] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl .java:1523) [JBossMQ] at org.jboss.util.ServiceControl.start(ServiceControl.java:97) [JBossMQ] at java.lang.reflect.Method.invoke(Native Method) [JBossMQ] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl .java:1628) [JBossMQ] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl .java:1523) [JBossMQ] at org.jboss.Main.init(Main.java:217) [JBossMQ] at org.jboss.Main$1.run(Main.java:121) [JBossMQ] at java.security.AccessController.doPrivileged(Native Method) [JBossMQ] at org.jboss.Main.main(Main.java:117) [JBossMQ] Started [DefaultJMSProvider] Starting [DefaultJMSProvider] JMS provider Adapter DefaultJMSProvider bound to java:/Defa ultJMSProvider [DefaultJMSProvider] Started [StdJMSPool] Starting [StdJMSPool] JMS provider Adapter StdJMSPool bound to java:/StdJMSPool [StdJMSPool] Started [J2EE Deployer Default] Starting [J2EE Deployer Default] Cleaning up deployment directory [J2EE Deployer Default] Started --On Thursday, June 21, 2001 11:36 PM +0100 Julian Gosnell [EMAIL PROTECTED] wrote: Scott, David and Matt, I am just checking JBoss-2.2.2_Jetty-3.1.RC5-4.tgz into jboss/binaries. It should appear at : http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/binaries/JBoss-2.2.2 _Jetty-3.1.RC5-4.tgz in an hour or so. If you would like to give it a whirl, click on Revision 1.1 and it should start to download (Netscape) failing this try Save as on the link. If I get feedback from you that your problem is fixed we will make this a release. Thanks for all your interest. Jules Scott M Stark wrote: Neither trace 3 or 4 are correct as they originate from the org.jboss.util.ServiceControl class. Looking at the 2.2 branch I see the change in service life-cycle management I mentioned was not incorporated into that release and this is the problem. If there is enough demand a 2.2.3 release could be made. The 2.4 release beta will start tomorrow. - Original Message - From: David Castro-Diephouse [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 20, 2001 8:52 PM Subject: Re: [JBoss-user] jboss-jetty problem - stack traces Here are 4 stack traces: 1. From ServiceControl.handleNotification, registering an MBean for the HttpServer. 2. From ServiceControl.handleNotification, registering an MBean for the WebApplicationContext. 3. HttpServer.start calls start
Re: [JBoss-user] jboss-jetty problem - stack traces
Hi Jules. We've still got a hitch in the new version. Now the web server is not starting up at all. Here's what is happening. In JettyService.startService, you added a check to Jetty.isStarted = HttpServer.isStarted. This call is not doing what you want though. HttpServer.isStarted checks with its LogSink, its Listeners, and its Contexts. If ANY of the above are started, it returns true. I have a JBoss-deployed war. JBoss WarDeployer service runs before the Jetty service, and when it deploys my context Jetty.deploy starts the context. Then, when Jetty goes to start up, it finds out that one context is started, and concludes that the server is started. Unfortunately no listeners are started so we are screwed. It occurs to me though that I could work around by moving the Jetty service above the WarDeployer in jboss.jcml. Checking... Yes. The workaround fixes the problem. It still would be better if it would work without tweaking the jboss.jcml file though. I guess you could have Jetty explicitly keep track of whether or not it has been started. Maybe you will see something better. I have to get to bed! Thanks for the quick turnaround Jules. Dave Julian Gosnell wrote: Scott, David and Matt, I am just checking JBoss-2.2.2_Jetty-3.1.RC5-4.tgz into jboss/binaries. It should appear at : http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/binaries/JBoss-2.2.2_Jetty-3.1.RC5-4.tgz in an hour or so. If you would like to give it a whirl, click on Revision 1.1 and it should start to download (Netscape) failing this try Save as on the link. If I get feedback from you that your problem is fixed we will make this a release. Thanks for all your interest. Jules Scott M Stark wrote: Neither trace 3 or 4 are correct as they originate from the org.jboss.util.ServiceControl class. Looking at the 2.2 branch I see the change in service life-cycle management I mentioned was not incorporated into that release and this is the problem. If there is enough demand a 2.2.3 release could be made. The 2.4 release beta will start tomorrow. - Original Message - From: David Castro-Diephouse [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 20, 2001 8:52 PM Subject: Re: [JBoss-user] jboss-jetty problem - stack traces Here are 4 stack traces: 1. From ServiceControl.handleNotification, registering an MBean for the HttpServer. 2. From ServiceControl.handleNotification, registering an MBean for the WebApplicationContext. 3. HttpServer.start calls start on the WebApplicationContext. 4. JMX starts up my WebApplicationContext a second time. (this is probably what you are looking for Scott) ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jboss-jetty problem - stack traces
Here are 4 stack traces: 1. From ServiceControl.handleNotification, registering an MBean for the HttpServer. 2. From ServiceControl.handleNotification, registering an MBean for the WebApplicationContext. 3. HttpServer.start calls start on the WebApplicationContext. 4. JMX starts up my WebApplicationContext a second time. (this is probably what you are looking for Scott) Stack Trace 1. [Default] MBean Register: com.mortbay.Jetty:name=Jetty,Jetty=0 [Default] java.lang.Exception [Default] at org.jboss.util.ServiceControl.handleNotification(ServiceControl.java:244) [Default] at com.sun.management.jmx.MBeanServerNotificationListener.handleNotification(MBeanServerNotificationListener.java:48) [Default] at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:142) [Default] at javax.management.MBeanServerDelegate.sendNotification(MBeanServerDelegate.java:176) [Default] at com.sun.management.jmx.MBeanServerImpl.sendNotification(MBeanServerImpl.java:2645) [Default] at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:2368) [Default] at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:874) [Default] at org.jboss.jetty.JettyService.ensureMBean(JettyService.java:209) [Default] at org.jboss.jetty.JettyService.ensureService(JettyService.java:239) [Default] at org.jboss.jetty.JettyService.initService(JettyService.java:282) [Default] at org.jboss.util.ServiceMBeanSupport.init(ServiceMBeanSupport.java:67) [Default] at java.lang.reflect.Method.invoke(Native Method) [Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) [Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) [Default] at org.jboss.util.ServiceControl.init(ServiceControl.java:59) [Default] at java.lang.reflect.Method.invoke(Native Method) [Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) [Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) [Default] at org.jboss.Main.init(Main.java:216) [Default] at org.jboss.Main$1.run(Main.java:121) [Default] at java.security.AccessController.doPrivileged(Native Method) [Default] at org.jboss.Main.main(Main.java:117) [Jetty] Registered com.mortbay.Jetty:name=Jetty,Jetty=0 Stack Trace 2. [Default] MBean Register: com.mortbay.Jetty:name=Jetty,Jetty=0,context=/workbench,WebApplicationContext=0 [Default] java.lang.Exception [Default] at org.jboss.util.ServiceControl.handleNotification(ServiceControl.java:244) [Default] at com.sun.management.jmx.MBeanServerNotificationListener.handleNotification(MBeanServerNotificationListener.java:48) [Default] at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:142) [Default] at javax.management.MBeanServerDelegate.sendNotification(MBeanServerDelegate.java:176) [Default] at com.sun.management.jmx.MBeanServerImpl.sendNotification(MBeanServerImpl.java:2645) [Default] at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:2368) [Default] at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:874) [Default] at com.mortbay.Jetty.JMX.HttpServerMBean.childrenAdded(HttpServerMBean.java) [Default] at java.beans.beancontext.BeanContextSupport.fireChildrenAdded(BeanContextSupport.java:1253) [Default] at java.beans.beancontext.BeanContextSupport.add(BeanContextSupport.java:449) [Default] at com.mortbay.HTTP.HttpServer.addContext(HttpServer.java:423) [Default] at com.mortbay.Jetty.Server.addWebApplication(Server.java:204) [Default] at com.mortbay.Jetty.Server.addWebApplication(Server.java:170) [Default] at java.lang.reflect.Method.invoke(Native Method) [Default] at com.mortbay.XML.XmlConfiguration.call(XmlConfiguration.java:440) [Default] at com.mortbay.XML.XmlConfiguration.configure(XmlConfiguration.java:187) [Default] at com.mortbay.XML.XmlConfiguration.configure(XmlConfiguration.java:120) [Default] at com.mortbay.Jetty.Server.configure(Server.java:99) [Default] at org.jboss.jetty.JettyService.ensureMBean(JettyService.java:224) [Default] at org.jboss.jetty.JettyService.ensureService(JettyService.java:239) [Default] at org.jboss.jetty.JettyService.initService(JettyService.java:282) [Default] at org.jboss.util.ServiceMBeanSupport.init(ServiceMBeanSupport.java:67) [Default] at java.lang.reflect.Method.invoke(Native Method) [Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) [Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) [Default] at
Re: [JBoss-user] jboss-jetty problem - stack traces
Neither trace 3 or 4 are correct as they originate from the org.jboss.util.ServiceControl class. Looking at the 2.2 branch I see the change in service life-cycle management I mentioned was not incorporated into that release and this is the problem. If there is enough demand a 2.2.3 release could be made. The 2.4 release beta will start tomorrow. - Original Message - From: David Castro-Diephouse [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 20, 2001 8:52 PM Subject: Re: [JBoss-user] jboss-jetty problem - stack traces Here are 4 stack traces: 1. From ServiceControl.handleNotification, registering an MBean for the HttpServer. 2. From ServiceControl.handleNotification, registering an MBean for the WebApplicationContext. 3. HttpServer.start calls start on the WebApplicationContext. 4. JMX starts up my WebApplicationContext a second time. (this is probably what you are looking for Scott) ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
