Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10
Scott M Stark wrote: If you look at the Embedded usage in the JBoss service it is not doing much. Being able to run off a sar with the minimum elements from tomcat would be good, but I want to keep the ability to run with a pristine tomcat dist. Using the normal Tomcat startup code directly instead of Embedded should allow it, but what's the rationale behind that ? I'm asking since that's not the policy with Jetty. Why is Tomcat handled differently ? Remy --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10
Because more people use Tomcat and want to be able to integrate with existing distributions that they can run standalone. No one has asked for this with Jetty as yet. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Remy Maucherat [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, October 08, 2002 12:25 AM Subject: Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10 Scott M Stark wrote: If you look at the Embedded usage in the JBoss service it is not doing much. Being able to run off a sar with the minimum elements from tomcat would be good, but I want to keep the ability to run with a pristine tomcat dist. Using the normal Tomcat startup code directly instead of Embedded should allow it, but what's the rationale behind that ? I'm asking since that's not the policy with Jetty. Why is Tomcat handled differently ? Remy --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10
Liam Magee wrote: Hi Thomas, I haven't looked deeply into Tomcat MBean support, this is the next natural step for integration b/w JBoss and Tomcat. I think it would be beneficial to stop using Embedded eventually (whatever JBoss needs to do should be doable using a host configurator and similar hooks), so that little or no code duplication is needed. I'll make changes on the Tomcat side (either in future 4.1.x releases, or in Tomcat 5.0.x) and the JBoss/Tomcat build script to allow customizing the classloader and directory structure if people are interested in getting an integration with a neater packaging ala Jetty/JBoss (many components and libraries are also not useful to JBoss and could be removed, thus making the download archive much smaller). Remy --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10
This would be excellent if you could do this Nick Remy Maucherat wrote: Liam Magee wrote: Hi Thomas, I haven't looked deeply into Tomcat MBean support, this is the next natural step for integration b/w JBoss and Tomcat. I think it would be beneficial to stop using Embedded eventually (whatever JBoss needs to do should be doable using a host configurator and similar hooks), so that little or no code duplication is needed. I'll make changes on the Tomcat side (either in future 4.1.x releases, or in Tomcat 5.0.x) and the JBoss/Tomcat build script to allow customizing the classloader and directory structure if people are interested in getting an integration with a neater packaging ala Jetty/JBoss (many components and libraries are also not useful to JBoss and could be removed, thus making the download archive much smaller). Remy --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10
I would be happy to assist with any future integration efforts with Tomcat. Is there a to-do list of any kind for this? Regards, Liam. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Remy Maucherat Sent: Monday, October 07, 2002 6:19 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10 Liam Magee wrote: Hi Thomas, I haven't looked deeply into Tomcat MBean support, this is the next natural step for integration b/w JBoss and Tomcat. I think it would be beneficial to stop using Embedded eventually (whatever JBoss needs to do should be doable using a host configurator and similar hooks), so that little or no code duplication is needed. I'll make changes on the Tomcat side (either in future 4.1.x releases, or in Tomcat 5.0.x) and the JBoss/Tomcat build script to allow customizing the classloader and directory structure if people are interested in getting an integration with a neater packaging ala Jetty/JBoss (many components and libraries are also not useful to JBoss and could be removed, thus making the download archive much smaller). Remy --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10
If you look at the Embedded usage in the JBoss service it is not doing much. Being able to run off a sar with the minimum elements from tomcat would be good, but I want to keep the ability to run with a pristine tomcat dist. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Remy Maucherat [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, October 07, 2002 1:19 AM Subject: Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10 Liam Magee wrote: Hi Thomas, I haven't looked deeply into Tomcat MBean support, this is the next natural step for integration b/w JBoss and Tomcat. I think it would be beneficial to stop using Embedded eventually (whatever JBoss needs to do should be doable using a host configurator and similar hooks), so that little or no code duplication is needed. I'll make changes on the Tomcat side (either in future 4.1.x releases, or in Tomcat 5.0.x) and the JBoss/Tomcat build script to allow customizing the classloader and directory structure if people are interested in getting an integration with a neater packaging ala Jetty/JBoss (many components and libraries are also not useful to JBoss and could be removed, thus making the download archive much smaller). Remy --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10
Hello Liam! Liam Magee wrote: I've uploaded the patch via the link below. Let me know if there are any problems with this. At the moment there is no integration between the Tomcat Mbeans and JBossJMX. I tried to attach the Catalina MBeans to the JBoss-MBeanServer. I got some parts to work. Now I am stuck because org.apache.catalina.startup.Embedded emits not the same Lifecycle-events as org.apache.catalina.core.StandardServer would do. Maybe we have to ask the Jakarta-guys to implement those events in Embedded. CU Thomas -- AIM-Nickname : tpeuss Homepage : http://www.peuss.de/ PGP-Public-Key : http://www.peuss.de/PublicKey.asc --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10
Hi Thomas, I haven't looked deeply into Tomcat MBean support, this is the next natural step for integration b/w JBoss and Tomcat. Regards, Liam. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Thomas Peuss Sent: Sunday, October 06, 2002 6:54 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10 Hello Liam! Liam Magee wrote: I've uploaded the patch via the link below. Let me know if there are any problems with this. At the moment there is no integration between the Tomcat Mbeans and JBossJMX. I tried to attach the Catalina MBeans to the JBoss-MBeanServer. I got some parts to work. Now I am stuck because org.apache.catalina.startup.Embedded emits not the same Lifecycle-events as org.apache.catalina.core.StandardServer would do. Maybe we have to ask the Jakarta-guys to implement those events in Embedded. CU Thomas -- AIM-Nickname : tpeuss Homepage : http://www.peuss.de/ PGP-Public-Key : http://www.peuss.de/PublicKey.asc --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10
I've fixed the problem I was having earlier, and have a version of tomcat-service.jar which integrates JBoss3.0.2 and Tomcat4.1.12. What is the process for posting/committing the code for review? Regards, Liam Magee. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Liam Magee Sent: Thursday, September 26, 2002 9:28 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10 I've put together a working version of JBoss3.0.2-Tomcat4.1.12 (using the Digester class instead of XmlMapper). Everything works fine (a new tomcat4-service.jar gets built), except that I'm having trouble with deployment. When a war contains a jar file, I get the following exception: java.net.MalformedURLException: invalid url: jndi:/localhost/struts-documentation/WEB-INF/lib/jakarta-oro.jar!/ (java.net.MalformedURLException: unknown protocol: jndi) at java.net.URL.init(URL.java:613) at java.net.URL.init(URL.java:476) at java.net.URL.init(URL.java:425) at org.apache.catalina.startup.ContextConfig.tldScanJar(ContextConfig.java: 902) at org.apache.catalina.startup.ContextConfig.tldScan(ContextConfig.java:868 ) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:647) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.j ava:243) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu pport.java:166) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3493 ) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.ja va:821) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:579) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.createWebContext(Embedd edCatalinaServiceSX.java:427) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.performDeploy(EmbeddedC atalinaServiceSX.java:302) at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:300) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:802) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:616) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:580) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi spatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy4.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentSc anner.java:427) at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeplo ymentScanner.java:648) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScan ner.java:499) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(Abst ractDeploymentScanner.java:261) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:164) at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi spatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController .java:967) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:396) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi spatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy3.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:249) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:802) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:616) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:580) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:564) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method
Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10
Liam Magee wrote: I've fixed the problem I was having earlier, and have a version of tomcat-service.jar which integrates JBoss3.0.2 and Tomcat4.1.12. What is the process for posting/committing the code for review? Great job on putting that stuff together so fast. I think you could submit a patch to the SF patch handing system. http://sourceforge.net/tracker/?group_id=22866atid=376687 Remy --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10
I've uploaded the patch via the link below. Let me know if there are any problems with this. At the moment there is no integration between the Tomcat Mbeans and JBossJMX. Regards, Liam. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Remy Maucherat Sent: Thursday, September 26, 2002 7:09 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10 Liam Magee wrote: I've fixed the problem I was having earlier, and have a version of tomcat-service.jar which integrates JBoss3.0.2 and Tomcat4.1.12. What is the process for posting/committing the code for review? Great job on putting that stuff together so fast. I think you could submit a patch to the SF patch handing system. http://sourceforge.net/tracker/?group_id=22866atid=376687 Remy --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10
Thanks Liam! Could you post the file somewhere (no files were attached to your patch post). -Original Message- From: Liam Magee [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 2:48 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10 I've fixed the problem I was having earlier, and have a version of tomcat-service.jar which integrates JBoss3.0.2 and Tomcat4.1.12. What is the process for posting/committing the code for review? Regards, Liam Magee. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Liam Magee Sent: Thursday, September 26, 2002 9:28 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10 I've put together a working version of JBoss3.0.2-Tomcat4.1.12 (using the Digester class instead of XmlMapper). Everything works fine (a new tomcat4-service.jar gets built), except that I'm having trouble with deployment. When a war contains a jar file, I get the following exception: java.net.MalformedURLException: invalid url: jndi:/localhost/struts-documentation/WEB-INF/lib/jakarta-oro.jar!/ (java.net.MalformedURLException: unknown protocol: jndi) at java.net.URL.init(URL.java:613) at java.net.URL.init(URL.java:476) at java.net.URL.init(URL.java:425) at org.apache.catalina.startup.ContextConfig.tldScanJar(ContextConfig.java: 902) at org.apache.catalina.startup.ContextConfig.tldScan(ContextConfig.java:868 ) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:647) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.j ava:243) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu pport.java:166) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3493 ) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.ja va:821) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:579) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.createWebContext(Embedd edCatalinaServiceSX.java:427) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.performDeploy(EmbeddedC atalinaServiceSX.java:302) at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:300) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:802) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:616) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:580) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi spatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy4.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentSc anner.java:427) at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeplo ymentScanner.java:648) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScan ner.java:499) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(Abst ractDeploymentScanner.java:261) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:164) at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi spatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController .java:967) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:396) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi spatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy3.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:249) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:802
RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10
My apologies - it has now been uploaded against the patch. Please download from: http://sourceforge.net/tracker/index.php?func=detailaid=614927group_id =22866atid=376687 Regards, Liam. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Simpson, Mike W Sent: Friday, September 27, 2002 8:19 AM To: '[EMAIL PROTECTED]' Cc: '[EMAIL PROTECTED]' Subject: RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10 Thanks Liam! Could you post the file somewhere (no files were attached to your patch post). -Original Message- From: Liam Magee [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 2:48 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10 I've fixed the problem I was having earlier, and have a version of tomcat-service.jar which integrates JBoss3.0.2 and Tomcat4.1.12. What is the process for posting/committing the code for review? Regards, Liam Magee. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Liam Magee Sent: Thursday, September 26, 2002 9:28 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10 I've put together a working version of JBoss3.0.2-Tomcat4.1.12 (using the Digester class instead of XmlMapper). Everything works fine (a new tomcat4-service.jar gets built), except that I'm having trouble with deployment. When a war contains a jar file, I get the following exception: java.net.MalformedURLException: invalid url: jndi:/localhost/struts-documentation/WEB-INF/lib/jakarta-oro.jar!/ (java.net.MalformedURLException: unknown protocol: jndi) at java.net.URL.init(URL.java:613) at java.net.URL.init(URL.java:476) at java.net.URL.init(URL.java:425) at org.apache.catalina.startup.ContextConfig.tldScanJar(ContextConfig.java: 902) at org.apache.catalina.startup.ContextConfig.tldScan(ContextConfig.java:868 ) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:647) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.j ava:243) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu pport.java:166) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3493 ) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.ja va:821) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:579) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.createWebContext(Embedd edCatalinaServiceSX.java:427) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.performDeploy(EmbeddedC atalinaServiceSX.java:302) at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:300) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:802) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:616) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:580) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi spatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy4.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentSc anner.java:427) at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeplo ymentScanner.java:648) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScan ner.java:499) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(Abst ractDeploymentScanner.java:261) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:164) at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi spatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController .java:967) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:396) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324
RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10
) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221) at org.jboss.Main.boot(Main.java:142) at org.jboss.Main$1.run(Main.java:375) at java.lang.Thread.run(Thread.java:536) I assume its because JNDI is not getting set up properly for Tomcat. This area doesn't seem too different to Tomcat 4.0.x, but I can't find anything in the catalina module which sets up JNDI for Tomcat. Can anyone help? Liam Magee. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Remy Maucherat Sent: Tuesday, September 24, 2002 5:08 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10 Scott M Stark wrote: No, I have no time for this right now. Remy Maucherat will be looking at it shortly. I plan to help out after Tomcat 4.1.12 is out of the door (it should be tomorrow). Given that 4.1 includes a lot of performance improvements, as well as the new Jasper 2, it should be worth it. Remy Any chance Scott or Alain can take a look at this? I think Josh Davis and a few others have been clamoring for this as well. thanks, Mike -Original Message- From: Simpson, Mike W Sent: Friday, September 20, 2002 3:34 PM To: '[EMAIL PROTECTED]' Subject: [JBoss-dev] JBoss3.2-Tomcat4.1.10 For a variety of 'business reasons', we're running tomcat instead of jetty, and would very much benefit from being on the 4.1.10 release. I've been working on getting jboss 3.2 integrate with tomcat 4.10, and for the most part, it's an easy upgrade. On 9/16, I checked out Branch_3_2, and pulled Tomcat 4.1.10 from Apache. org.apache.catalina.util.xml has been deprecated and removed, in favor of Apache's commons digester package. Rather than port all of the xml digester code, I jarred up the old package, added to build classpaths, and all but a handful of compilation errors were removed. The following additional changes were necessary to get the bundle to build: --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10
Any chance Scott or Alain can take a look at this? I think Josh Davis and a
few others have been clamoring for this as well.
thanks,
Mike
-Original Message-
From: Simpson, Mike W
Sent: Friday, September 20, 2002 3:34 PM
To: '[EMAIL PROTECTED]'
Subject: [JBoss-dev] JBoss3.2-Tomcat4.1.10
For a variety of 'business reasons', we're running tomcat instead of jetty,
and would very much benefit from being on the 4.1.10 release. I've been
working on getting jboss 3.2 integrate with tomcat 4.10, and for the most
part, it's an easy upgrade.
On 9/16, I checked out Branch_3_2, and pulled Tomcat 4.1.10 from Apache.
org.apache.catalina.util.xml has been deprecated and removed, in favor of
Apache's commons digester package. Rather than port all of the xml digester
code, I jarred up the old package, added to build classpaths, and all but a
handful of compilation errors were removed. The following additional
changes were necessary to get the bundle to build:
Add this code to org.jboss.web.catalina.session.ClusteredSessionValve:
/**
* The lifecycle event support for this component.
*/
protected LifecycleSupport lifecycle = new LifecycleSupport(this);
/**
* Get the lifecycle listeners associated with this lifecycle. If this
* Lifecycle has no listeners registered, a zero-length array is
returned.
*/
public LifecycleListener[] findLifecycleListeners() {
return lifecycle.findLifecycleListeners();
}
Add this code to org.jboss.web.catalina.EmbeddedService:
private org.apache.catalina.Server catalinaServer=null;
public org.apache.catalina.Server getServer() {
return catalinaServer;
}
public void setServer(org.apache.catalina.Server server) { //the current
setServer method has a different param type
catalinaServer=server;
}
It looks like none of this code gets called at runtime, but interface
additions required the additional methods to be present.
build bundle
build works, but container won't start
edit org.jboss.web.catalina.ConfigHandler, change the FIRST occurrence of
org.apache.catalina.core.DefaultContext to
org.apache.catalina.core.StandardDefaultContext
and the second occurrence to org.apache.catalina.DefaultContext
Bundled container then starts successfully.
I then tried to deploy the test.ear, which successfully deploys after
putting the (once optional, now required) doctype into tomcat-test.jar's
ejb-jar.xml.
Unfortunately, add goes awry when a jsp page tries to instantiate a session
bean.
09:41:06,115 INFO [MainDeployer] Deployed package:
file:/D:/jboss-3.2.0beta/server/default/deploy/tomcat-test.ear
09:41:19,099 ERROR [LogInterceptor] RuntimeException:
java.lang.IllegalStateException
at
org.jboss.ejb.StatelessSessionContainer.createHome(StatelessSessionContainer
.java:388)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invokeHome(Stat
elessSessionContainer.java:569)
at
org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invokeHome(Statele
ssSessionInstanceInterceptor.java
:57)
at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor
.java:112)
at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.
java:184)
at
org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:58)
at
org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.jav
a:105)
at
org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:131)
at
org.jboss.ejb.StatelessSessionContainer.invokeHome(StatelessSessionContainer
.java:291)
at org.jboss.ejb.Container.invoke(Container.java:692)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at
org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:100)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:88)
at
org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:77
)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:80)
at
org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:175)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:82)
at $Proxy35.create(Unknown Source)
at org.jboss.test.tomcat.servlet.HelloEJB.testBean(HelloEJB.java:71)
at org.jboss.test.tomcat.servlet.HelloEJB.doGet(HelloEJB.java:40)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853
Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10
No, I have no time for this right now. Remy Maucherat will be looking at it shortly. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Simpson, Mike W [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 23, 2002 10:02 AM Subject: RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10 Any chance Scott or Alain can take a look at this? I think Josh Davis and a few others have been clamoring for this as well. thanks, Mike -Original Message- From: Simpson, Mike W Sent: Friday, September 20, 2002 3:34 PM To: '[EMAIL PROTECTED]' Subject: [JBoss-dev] JBoss3.2-Tomcat4.1.10 For a variety of 'business reasons', we're running tomcat instead of jetty, and would very much benefit from being on the 4.1.10 release. I've been working on getting jboss 3.2 integrate with tomcat 4.10, and for the most part, it's an easy upgrade. On 9/16, I checked out Branch_3_2, and pulled Tomcat 4.1.10 from Apache. org.apache.catalina.util.xml has been deprecated and removed, in favor of Apache's commons digester package. Rather than port all of the xml digester code, I jarred up the old package, added to build classpaths, and all but a handful of compilation errors were removed. The following additional changes were necessary to get the bundle to build: --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10
Scott M Stark wrote: No, I have no time for this right now. Remy Maucherat will be looking at it shortly. I plan to help out after Tomcat 4.1.12 is out of the door (it should be tomorrow). Given that 4.1 includes a lot of performance improvements, as well as the new Jasper 2, it should be worth it. Remy Any chance Scott or Alain can take a look at this? I think Josh Davis and a few others have been clamoring for this as well. thanks, Mike -Original Message- From: Simpson, Mike W Sent: Friday, September 20, 2002 3:34 PM To: '[EMAIL PROTECTED]' Subject: [JBoss-dev] JBoss3.2-Tomcat4.1.10 For a variety of 'business reasons', we're running tomcat instead of jetty, and would very much benefit from being on the 4.1.10 release. I've been working on getting jboss 3.2 integrate with tomcat 4.10, and for the most part, it's an easy upgrade. On 9/16, I checked out Branch_3_2, and pulled Tomcat 4.1.10 from Apache. org.apache.catalina.util.xml has been deprecated and removed, in favor of Apache's commons digester package. Rather than port all of the xml digester code, I jarred up the old package, added to build classpaths, and all but a handful of compilation errors were removed. The following additional changes were necessary to get the bundle to build: --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss3.2-Tomcat4.1.10
For a variety of 'business reasons', we're running tomcat instead of jetty,
and would very much benefit from being on the 4.1.10 release. I've been
working on getting jboss 3.2 integrate with tomcat 4.10, and for the most
part, it's an easy upgrade.
On 9/16, I checked out Branch_3_2, and pulled Tomcat 4.1.10 from Apache.
org.apache.catalina.util.xml has been deprecated and removed, in favor of
Apache's commons digester package. Rather than port all of the xml digester
code, I jarred up the old package, added to build classpaths, and all but a
handful of compilation errors were removed. The following additional
changes were necessary to get the bundle to build:
Add this code to org.jboss.web.catalina.session.ClusteredSessionValve:
/**
* The lifecycle event support for this component.
*/
protected LifecycleSupport lifecycle = new LifecycleSupport(this);
/**
* Get the lifecycle listeners associated with this lifecycle. If this
* Lifecycle has no listeners registered, a zero-length array is
returned.
*/
public LifecycleListener[] findLifecycleListeners() {
return lifecycle.findLifecycleListeners();
}
Add this code to org.jboss.web.catalina.EmbeddedService:
private org.apache.catalina.Server catalinaServer=null;
public org.apache.catalina.Server getServer() {
return catalinaServer;
}
public void setServer(org.apache.catalina.Server server) { //the current
setServer method has a different param type
catalinaServer=server;
}
It looks like none of this code gets called at runtime, but interface
additions required the additional methods to be present.
build bundle
build works, but container won't start
edit org.jboss.web.catalina.ConfigHandler, change the FIRST occurrence of
org.apache.catalina.core.DefaultContext to
org.apache.catalina.core.StandardDefaultContext
and the second occurrence to org.apache.catalina.DefaultContext
Bundled container then starts successfully.
I then tried to deploy the test.ear, which successfully deploys after
putting the (once optional, now required) doctype into tomcat-test.jar's
ejb-jar.xml.
Unfortunately, add goes awry when a jsp page tries to instantiate a session
bean.
09:41:06,115 INFO [MainDeployer] Deployed package:
file:/D:/jboss-3.2.0beta/server/default/deploy/tomcat-test.ear
09:41:19,099 ERROR [LogInterceptor] RuntimeException:
java.lang.IllegalStateException
at
org.jboss.ejb.StatelessSessionContainer.createHome(StatelessSessionContainer
.java:388)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invokeHome(Stat
elessSessionContainer.java:569)
at
org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invokeHome(Statele
ssSessionInstanceInterceptor.java
:57)
at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor
.java:112)
at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.
java:184)
at
org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:58)
at
org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.jav
a:105)
at
org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:131)
at
org.jboss.ejb.StatelessSessionContainer.invokeHome(StatelessSessionContainer
.java:291)
at org.jboss.ejb.Container.invoke(Container.java:692)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at
org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:100)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:88)
at
org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:77
)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:80)
at
org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:175)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:82)
at $Proxy35.create(Unknown Source)
at org.jboss.test.tomcat.servlet.HelloEJB.testBean(HelloEJB.java:71)
at org.jboss.test.tomcat.servlet.HelloEJB.doGet(HelloEJB.java:40)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.servlets.InvokerServlet.serveRequest(InvokerServlet.java
:451)
at
org.apache.catalina.servlets.InvokerServlet.doGet(InvokerServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
