[JBoss-dev] [ jboss-Bugs-710396 ] Deployed .war unaccessible in Tomcat 4.1
Bugs item #710396, was opened at 2003-03-26 15:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=710396group_id=22866 Category: CatalinaBundle Group: v3.2 Status: Closed Resolution: Works For Me Priority: 5 Submitted By: Stefan Reich (sreich) Assigned to: Scott M Stark (starksm) Summary: Deployed .war unaccessible in Tomcat 4.1 Initial Comment: Platform MacOSX 10.2.4, JDK 1.4.1, Jboss 3.2 latest CVS, Tomcat 4.1.24 (and 4.1.18). Some recent change broke tomcat deployment. Although there is no error during the deployment, the servlet can't be accessed. To reproduce try to access jmx-console. -- Comment By: Stefan Reich (sreich) Date: 2003-04-01 18:35 Message: Logged In: YES user_id=429729 i can't reproduce the problem with the latest CVS rev from today anymore. Closing. -- Comment By: Scott M Stark (starksm) Date: 2003-03-30 19:21 Message: Logged In: YES user_id=175228 I have tried starting the container with the ecperf.ear and emulator.ear deployed with the jboss-3.2.0RC5_tomcat-4.1.24 bundle and I'm not seeing this exception. I'm just pointing the ECPerfDS to the embedded hypersonic database to test the deployment. I have tried this on both my WinXP box and OSX with the 10.2.4 release and the current final 1.4.1 JDK: 18:51:38,031 INFO [ServerInfo] Java version: 1.4.1_01,Apple Computer, Inc. 18:51:38,032 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.1_01-14,Apple Computer, Inc. 18:51:38,032 INFO [ServerInfo] OS-System: Mac OS X 10.2.4,ppc -- Comment By: Remy Maucherat (remm) Date: 2003-03-29 12:46 Message: Logged In: YES user_id=24140 Let's start with the first issue (the NPE). Since you can build the bundle, could you try using the new SAR based packaging ? If there's a path related problem, it could help (or makes things worse, but in any case, it needs testing). Use the bundle-express target to create the SAR based bundle. -- Comment By: Stefan Reich (sreich) Date: 2003-03-28 15:26 Message: Logged In: YES user_id=429729 Great, the attachment is too long for SF. You can also check out and build ecperf from the jboss cvs, which will give you the same files. -- Comment By: Stefan Reich (sreich) Date: 2003-03-28 15:16 Message: Logged In: YES user_id=429729 When I launch run.sh from the local directory I am able to access jmx-console. That's fine. However, when I deploy emulator.ear and ecperf.ear from ECperf the servlet can't find the java:comp context. This used to work about two weeks ago. I attached the jar files. To reproduce: untar the attachment in your deployment dir and start the container. Don't worry if you see SQLException exceptions during deployment, the exception below happens regardless if the database is up or not: javax.servlet.ServletException: comp not bound at com.sun.ecperf.supplier.web.SupplierDomainServlet.init(SupplierDomainServlet.java:94) at javax.servlet.GenericServlet.init(GenericServlet.java:256) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:668) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) [..] 14:26:20,012 ERROR [STDERR] javax.naming.NameNotFoundException: comp not bound 14:26:20,014 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:495) 14:26:20,014 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:503) 14:26:20,014 ERROR [STDERR] at org.jnp.server.NamingServer.getObject(NamingServer.java:509) 14:26:20,015 ERROR [STDERR] at org.jnp.server.NamingServer.lookup(NamingServer.java:253) 14:26:20,015 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:492) 14:26:20,015 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:471) 14:26:20,016 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:347) 14:26:20,016 ERROR [STDERR] at com.sun.ecperf.supplier.web.SupplierDomainServlet.init(SupplierDomainServlet.java:86) 14:26:20,016 ERROR [STDERR] at javax.servlet.GenericServlet.init(GenericServlet.java:256) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:668) 14:26:20,017 ERROR [STDERR] at
[JBoss-dev] [ jboss-Bugs-710396 ] Deployed .war unaccessible in Tomcat 4.1
Bugs item #710396, was opened at 2003-03-26 15:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=710396group_id=22866 Category: CatalinaBundle Group: v3.2 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Stefan Reich (sreich) Assigned to: Scott M Stark (starksm) Summary: Deployed .war unaccessible in Tomcat 4.1 Initial Comment: Platform MacOSX 10.2.4, JDK 1.4.1, Jboss 3.2 latest CVS, Tomcat 4.1.24 (and 4.1.18). Some recent change broke tomcat deployment. Although there is no error during the deployment, the servlet can't be accessed. To reproduce try to access jmx-console. -- Comment By: Scott M Stark (starksm) Date: 2003-03-30 19:21 Message: Logged In: YES user_id=175228 I have tried starting the container with the ecperf.ear and emulator.ear deployed with the jboss-3.2.0RC5_tomcat-4.1.24 bundle and I'm not seeing this exception. I'm just pointing the ECPerfDS to the embedded hypersonic database to test the deployment. I have tried this on both my WinXP box and OSX with the 10.2.4 release and the current final 1.4.1 JDK: 18:51:38,031 INFO [ServerInfo] Java version: 1.4.1_01,Apple Computer, Inc. 18:51:38,032 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.1_01-14,Apple Computer, Inc. 18:51:38,032 INFO [ServerInfo] OS-System: Mac OS X 10.2.4,ppc -- Comment By: Remy Maucherat (remm) Date: 2003-03-29 12:46 Message: Logged In: YES user_id=24140 Let's start with the first issue (the NPE). Since you can build the bundle, could you try using the new SAR based packaging ? If there's a path related problem, it could help (or makes things worse, but in any case, it needs testing). Use the bundle-express target to create the SAR based bundle. -- Comment By: Stefan Reich (sreich) Date: 2003-03-28 15:26 Message: Logged In: YES user_id=429729 Great, the attachment is too long for SF. You can also check out and build ecperf from the jboss cvs, which will give you the same files. -- Comment By: Stefan Reich (sreich) Date: 2003-03-28 15:16 Message: Logged In: YES user_id=429729 When I launch run.sh from the local directory I am able to access jmx-console. That's fine. However, when I deploy emulator.ear and ecperf.ear from ECperf the servlet can't find the java:comp context. This used to work about two weeks ago. I attached the jar files. To reproduce: untar the attachment in your deployment dir and start the container. Don't worry if you see SQLException exceptions during deployment, the exception below happens regardless if the database is up or not: javax.servlet.ServletException: comp not bound at com.sun.ecperf.supplier.web.SupplierDomainServlet.init(SupplierDomainServlet.java:94) at javax.servlet.GenericServlet.init(GenericServlet.java:256) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:668) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) [..] 14:26:20,012 ERROR [STDERR] javax.naming.NameNotFoundException: comp not bound 14:26:20,014 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:495) 14:26:20,014 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:503) 14:26:20,014 ERROR [STDERR] at org.jnp.server.NamingServer.getObject(NamingServer.java:509) 14:26:20,015 ERROR [STDERR] at org.jnp.server.NamingServer.lookup(NamingServer.java:253) 14:26:20,015 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:492) 14:26:20,015 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:471) 14:26:20,016 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:347) 14:26:20,016 ERROR [STDERR] at com.sun.ecperf.supplier.web.SupplierDomainServlet.init(SupplierDomainServlet.java:86) 14:26:20,016 ERROR [STDERR] at javax.servlet.GenericServlet.init(GenericServlet.java:256) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:668) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 14:26:20,018 ERROR [STDERR] at
[JBoss-dev] [ jboss-Bugs-710396 ] Deployed .war unaccessible in Tomcat 4.1
Bugs item #710396, was opened at 2003-03-26 15:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=710396group_id=22866 Category: CatalinaBundle Group: v3.2 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Stefan Reich (sreich) Assigned to: Scott M Stark (starksm) Summary: Deployed .war unaccessible in Tomcat 4.1 Initial Comment: Platform MacOSX 10.2.4, JDK 1.4.1, Jboss 3.2 latest CVS, Tomcat 4.1.24 (and 4.1.18). Some recent change broke tomcat deployment. Although there is no error during the deployment, the servlet can't be accessed. To reproduce try to access jmx-console. -- Comment By: Remy Maucherat (remm) Date: 2003-03-29 12:46 Message: Logged In: YES user_id=24140 Let's start with the first issue (the NPE). Since you can build the bundle, could you try using the new SAR based packaging ? If there's a path related problem, it could help (or makes things worse, but in any case, it needs testing). Use the bundle-express target to create the SAR based bundle. -- Comment By: Stefan Reich (sreich) Date: 2003-03-28 15:26 Message: Logged In: YES user_id=429729 Great, the attachment is too long for SF. You can also check out and build ecperf from the jboss cvs, which will give you the same files. -- Comment By: Stefan Reich (sreich) Date: 2003-03-28 15:16 Message: Logged In: YES user_id=429729 When I launch run.sh from the local directory I am able to access jmx-console. That's fine. However, when I deploy emulator.ear and ecperf.ear from ECperf the servlet can't find the java:comp context. This used to work about two weeks ago. I attached the jar files. To reproduce: untar the attachment in your deployment dir and start the container. Don't worry if you see SQLException exceptions during deployment, the exception below happens regardless if the database is up or not: javax.servlet.ServletException: comp not bound at com.sun.ecperf.supplier.web.SupplierDomainServlet.init(SupplierDomainServlet.java:94) at javax.servlet.GenericServlet.init(GenericServlet.java:256) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:668) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) [..] 14:26:20,012 ERROR [STDERR] javax.naming.NameNotFoundException: comp not bound 14:26:20,014 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:495) 14:26:20,014 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:503) 14:26:20,014 ERROR [STDERR] at org.jnp.server.NamingServer.getObject(NamingServer.java:509) 14:26:20,015 ERROR [STDERR] at org.jnp.server.NamingServer.lookup(NamingServer.java:253) 14:26:20,015 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:492) 14:26:20,015 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:471) 14:26:20,016 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:347) 14:26:20,016 ERROR [STDERR] at com.sun.ecperf.supplier.web.SupplierDomainServlet.init(SupplierDomainServlet.java:86) 14:26:20,016 ERROR [STDERR] at javax.servlet.GenericServlet.init(GenericServlet.java:256) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:668) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 14:26:20,018 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 14:26:20,018 ERROR [STDERR] at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) 14:26:20,018 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 14:26:20,018 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 14:26:20,019 ERROR [STDERR] at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) 14:26:20,019 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) 14:26:20,019 ERROR [STDERR] at
[JBoss-dev] [ jboss-Bugs-710396 ] Deployed .war unaccessible in Tomcat 4.1
Bugs item #710396, was opened at 2003-03-26 15:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=710396group_id=22866 Category: CatalinaBundle Group: v3.2 Status: Pending Resolution: Works For Me Priority: 5 Submitted By: Stefan Reich (sreich) Assigned to: Scott M Stark (starksm) Summary: Deployed .war unaccessible in Tomcat 4.1 Initial Comment: Platform MacOSX 10.2.4, JDK 1.4.1, Jboss 3.2 latest CVS, Tomcat 4.1.24 (and 4.1.18). Some recent change broke tomcat deployment. Although there is no error during the deployment, the servlet can't be accessed. To reproduce try to access jmx-console. -- Comment By: Scott M Stark (starksm) Date: 2003-03-28 11:12 Message: Logged In: YES user_id=175228 How are you building the jboss/tomcat dist? If I create the dist using the tomcat4.1 module bundle target I'm able to access the jmx-console just fine. tomcat41 560wget -s http://localhost:8080/jmx-console/ --10:56:28-- http://localhost:8080/jmx-console/ = `index.html' Resolving localhost... done. Connecting to localhost[127.0.0.1]:8080... connected. HTTP request sent, awaiting response... 302 Moved Temporarily Location: http://localhost:8080/jmx-console/index.jsp [following] --10:56:29-- http://localhost:8080/jmx-console/index.jsp = `index.jsp' Connecting to localhost[127.0.0.1]:8080... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] [ = ] 51,174 1.81M/s 10:56:30 (1.81 MB/s) - `index.jsp' saved [51174] tomcat41 561head index.jsp HTTP/1.1 200 OK Set-Cookie: JSESSIONID=96E951A60FB3DB9CEA00510D580D8F9D; Path=/jmx-console Content-Type: text/html;charset=ISO-8859-1 Date: Fri, 28 Mar 2003 18:56:30 GMT Server: Apache Coyote/1.0 Connection: close -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=710396group_id=22866 --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-710396 ] Deployed .war unaccessible in Tomcat 4.1
Bugs item #710396, was opened at 2003-03-26 15:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=710396group_id=22866 Category: CatalinaBundle Group: v3.2 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Stefan Reich (sreich) Assigned to: Scott M Stark (starksm) Summary: Deployed .war unaccessible in Tomcat 4.1 Initial Comment: Platform MacOSX 10.2.4, JDK 1.4.1, Jboss 3.2 latest CVS, Tomcat 4.1.24 (and 4.1.18). Some recent change broke tomcat deployment. Although there is no error during the deployment, the servlet can't be accessed. To reproduce try to access jmx-console. -- Comment By: Stefan Reich (sreich) Date: 2003-03-28 12:07 Message: Logged In: YES user_id=429729 build/build.sh clobber build/build.sh # setup the link to the tomcat dist cd tomcat41; build.sh bundle When I run jboss from tomcat41/output/jboss-3.2.0.RC5, it starts up fine, and deployes jmx-console.war. When I try to access the console I get: The requested resource (/jmx-console/) is not available. However, if I try /jmx-console/HtmlAdapter, I get a NPE from the HtmlAdapterServlet -- Comment By: Scott M Stark (starksm) Date: 2003-03-28 11:12 Message: Logged In: YES user_id=175228 How are you building the jboss/tomcat dist? If I create the dist using the tomcat4.1 module bundle target I'm able to access the jmx-console just fine. tomcat41 560wget -s http://localhost:8080/jmx-console/ --10:56:28-- http://localhost:8080/jmx-console/ = `index.html' Resolving localhost... done. Connecting to localhost[127.0.0.1]:8080... connected. HTTP request sent, awaiting response... 302 Moved Temporarily Location: http://localhost:8080/jmx-console/index.jsp [following] --10:56:29-- http://localhost:8080/jmx-console/index.jsp = `index.jsp' Connecting to localhost[127.0.0.1]:8080... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] [ = ] 51,174 1.81M/s 10:56:30 (1.81 MB/s) - `index.jsp' saved [51174] tomcat41 561head index.jsp HTTP/1.1 200 OK Set-Cookie: JSESSIONID=96E951A60FB3DB9CEA00510D580D8F9D; Path=/jmx-console Content-Type: text/html;charset=ISO-8859-1 Date: Fri, 28 Mar 2003 18:56:30 GMT Server: Apache Coyote/1.0 Connection: close -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=710396group_id=22866 --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-710396 ] Deployed .war unaccessible in Tomcat 4.1
Bugs item #710396, was opened at 2003-03-26 15:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=710396group_id=22866 Category: CatalinaBundle Group: v3.2 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Stefan Reich (sreich) Assigned to: Scott M Stark (starksm) Summary: Deployed .war unaccessible in Tomcat 4.1 Initial Comment: Platform MacOSX 10.2.4, JDK 1.4.1, Jboss 3.2 latest CVS, Tomcat 4.1.24 (and 4.1.18). Some recent change broke tomcat deployment. Although there is no error during the deployment, the servlet can't be accessed. To reproduce try to access jmx-console. -- Comment By: Scott M Stark (starksm) Date: 2003-03-28 12:53 Message: Logged In: YES user_id=175228 I only see this if I run the jboss/tomcat bundle from outside of the bin directory. When starting the run script from within the tomcat41/output/jboss-3.2.0RC5/bin directory the jmx-console works fine. There has to be an issue with paths and entity references not resolving correctly when outside of the bin directory. -- Comment By: Stefan Reich (sreich) Date: 2003-03-28 12:07 Message: Logged In: YES user_id=429729 build/build.sh clobber build/build.sh # setup the link to the tomcat dist cd tomcat41; build.sh bundle When I run jboss from tomcat41/output/jboss-3.2.0.RC5, it starts up fine, and deployes jmx-console.war. When I try to access the console I get: The requested resource (/jmx-console/) is not available. However, if I try /jmx-console/HtmlAdapter, I get a NPE from the HtmlAdapterServlet -- Comment By: Scott M Stark (starksm) Date: 2003-03-28 11:12 Message: Logged In: YES user_id=175228 How are you building the jboss/tomcat dist? If I create the dist using the tomcat4.1 module bundle target I'm able to access the jmx-console just fine. tomcat41 560wget -s http://localhost:8080/jmx-console/ --10:56:28-- http://localhost:8080/jmx-console/ = `index.html' Resolving localhost... done. Connecting to localhost[127.0.0.1]:8080... connected. HTTP request sent, awaiting response... 302 Moved Temporarily Location: http://localhost:8080/jmx-console/index.jsp [following] --10:56:29-- http://localhost:8080/jmx-console/index.jsp = `index.jsp' Connecting to localhost[127.0.0.1]:8080... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] [ = ] 51,174 1.81M/s 10:56:30 (1.81 MB/s) - `index.jsp' saved [51174] tomcat41 561head index.jsp HTTP/1.1 200 OK Set-Cookie: JSESSIONID=96E951A60FB3DB9CEA00510D580D8F9D; Path=/jmx-console Content-Type: text/html;charset=ISO-8859-1 Date: Fri, 28 Mar 2003 18:56:30 GMT Server: Apache Coyote/1.0 Connection: close -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=710396group_id=22866 --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-710396 ] Deployed .war unaccessible in Tomcat 4.1
Bugs item #710396, was opened at 2003-03-26 15:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=710396group_id=22866 Category: CatalinaBundle Group: v3.2 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Stefan Reich (sreich) Assigned to: Scott M Stark (starksm) Summary: Deployed .war unaccessible in Tomcat 4.1 Initial Comment: Platform MacOSX 10.2.4, JDK 1.4.1, Jboss 3.2 latest CVS, Tomcat 4.1.24 (and 4.1.18). Some recent change broke tomcat deployment. Although there is no error during the deployment, the servlet can't be accessed. To reproduce try to access jmx-console. -- Comment By: Remy Maucherat (remm) Date: 2003-03-28 14:39 Message: Logged In: YES user_id=24140 This also runs fine for me. Maybe you should try to attach the full error message. -- Comment By: Scott M Stark (starksm) Date: 2003-03-28 12:53 Message: Logged In: YES user_id=175228 I only see this if I run the jboss/tomcat bundle from outside of the bin directory. When starting the run script from within the tomcat41/output/jboss-3.2.0RC5/bin directory the jmx-console works fine. There has to be an issue with paths and entity references not resolving correctly when outside of the bin directory. -- Comment By: Stefan Reich (sreich) Date: 2003-03-28 12:07 Message: Logged In: YES user_id=429729 build/build.sh clobber build/build.sh # setup the link to the tomcat dist cd tomcat41; build.sh bundle When I run jboss from tomcat41/output/jboss-3.2.0.RC5, it starts up fine, and deployes jmx-console.war. When I try to access the console I get: The requested resource (/jmx-console/) is not available. However, if I try /jmx-console/HtmlAdapter, I get a NPE from the HtmlAdapterServlet -- Comment By: Scott M Stark (starksm) Date: 2003-03-28 11:12 Message: Logged In: YES user_id=175228 How are you building the jboss/tomcat dist? If I create the dist using the tomcat4.1 module bundle target I'm able to access the jmx-console just fine. tomcat41 560wget -s http://localhost:8080/jmx-console/ --10:56:28-- http://localhost:8080/jmx-console/ = `index.html' Resolving localhost... done. Connecting to localhost[127.0.0.1]:8080... connected. HTTP request sent, awaiting response... 302 Moved Temporarily Location: http://localhost:8080/jmx-console/index.jsp [following] --10:56:29-- http://localhost:8080/jmx-console/index.jsp = `index.jsp' Connecting to localhost[127.0.0.1]:8080... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] [ = ] 51,174 1.81M/s 10:56:30 (1.81 MB/s) - `index.jsp' saved [51174] tomcat41 561head index.jsp HTTP/1.1 200 OK Set-Cookie: JSESSIONID=96E951A60FB3DB9CEA00510D580D8F9D; Path=/jmx-console Content-Type: text/html;charset=ISO-8859-1 Date: Fri, 28 Mar 2003 18:56:30 GMT Server: Apache Coyote/1.0 Connection: close -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=710396group_id=22866 --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-710396 ] Deployed .war unaccessible in Tomcat 4.1
Bugs item #710396, was opened at 2003-03-26 15:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=710396group_id=22866 Category: CatalinaBundle Group: v3.2 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Stefan Reich (sreich) Assigned to: Scott M Stark (starksm) Summary: Deployed .war unaccessible in Tomcat 4.1 Initial Comment: Platform MacOSX 10.2.4, JDK 1.4.1, Jboss 3.2 latest CVS, Tomcat 4.1.24 (and 4.1.18). Some recent change broke tomcat deployment. Although there is no error during the deployment, the servlet can't be accessed. To reproduce try to access jmx-console. -- Comment By: Stefan Reich (sreich) Date: 2003-03-28 15:16 Message: Logged In: YES user_id=429729 When I launch run.sh from the local directory I am able to access jmx-console. That's fine. However, when I deploy emulator.ear and ecperf.ear from ECperf the servlet can't find the java:comp context. This used to work about two weeks ago. I attached the jar files. To reproduce: untar the attachment in your deployment dir and start the container. Don't worry if you see SQLException exceptions during deployment, the exception below happens regardless if the database is up or not: javax.servlet.ServletException: comp not bound at com.sun.ecperf.supplier.web.SupplierDomainServlet.init(SupplierDomainServlet.java:94) at javax.servlet.GenericServlet.init(GenericServlet.java:256) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:668) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) [..] 14:26:20,012 ERROR [STDERR] javax.naming.NameNotFoundException: comp not bound 14:26:20,014 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:495) 14:26:20,014 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:503) 14:26:20,014 ERROR [STDERR] at org.jnp.server.NamingServer.getObject(NamingServer.java:509) 14:26:20,015 ERROR [STDERR] at org.jnp.server.NamingServer.lookup(NamingServer.java:253) 14:26:20,015 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:492) 14:26:20,015 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:471) 14:26:20,016 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:347) 14:26:20,016 ERROR [STDERR] at com.sun.ecperf.supplier.web.SupplierDomainServlet.init(SupplierDomainServlet.java:86) 14:26:20,016 ERROR [STDERR] at javax.servlet.GenericServlet.init(GenericServlet.java:256) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:668) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 14:26:20,018 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 14:26:20,018 ERROR [STDERR] at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) 14:26:20,018 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 14:26:20,018 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 14:26:20,019 ERROR [STDERR] at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) 14:26:20,019 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) 14:26:20,019 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 14:26:20,019 ERROR [STDERR] at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) 14:26:20,020 ERROR [STDERR] at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) 14:26:20,020 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) 14:26:20,020 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 14:26:20,020 ERROR [STDERR] at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) 14:26:20,021 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
[JBoss-dev] [ jboss-Bugs-710396 ] Deployed .war unaccessible in Tomcat 4.1
Bugs item #710396, was opened at 2003-03-26 15:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=710396group_id=22866 Category: CatalinaBundle Group: v3.2 Status: Open Resolution: Works For Me Priority: 5 Submitted By: Stefan Reich (sreich) Assigned to: Scott M Stark (starksm) Summary: Deployed .war unaccessible in Tomcat 4.1 Initial Comment: Platform MacOSX 10.2.4, JDK 1.4.1, Jboss 3.2 latest CVS, Tomcat 4.1.24 (and 4.1.18). Some recent change broke tomcat deployment. Although there is no error during the deployment, the servlet can't be accessed. To reproduce try to access jmx-console. -- Comment By: Stefan Reich (sreich) Date: 2003-03-28 15:26 Message: Logged In: YES user_id=429729 Great, the attachment is too long for SF. You can also check out and build ecperf from the jboss cvs, which will give you the same files. -- Comment By: Stefan Reich (sreich) Date: 2003-03-28 15:16 Message: Logged In: YES user_id=429729 When I launch run.sh from the local directory I am able to access jmx-console. That's fine. However, when I deploy emulator.ear and ecperf.ear from ECperf the servlet can't find the java:comp context. This used to work about two weeks ago. I attached the jar files. To reproduce: untar the attachment in your deployment dir and start the container. Don't worry if you see SQLException exceptions during deployment, the exception below happens regardless if the database is up or not: javax.servlet.ServletException: comp not bound at com.sun.ecperf.supplier.web.SupplierDomainServlet.init(SupplierDomainServlet.java:94) at javax.servlet.GenericServlet.init(GenericServlet.java:256) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:668) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) [..] 14:26:20,012 ERROR [STDERR] javax.naming.NameNotFoundException: comp not bound 14:26:20,014 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:495) 14:26:20,014 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:503) 14:26:20,014 ERROR [STDERR] at org.jnp.server.NamingServer.getObject(NamingServer.java:509) 14:26:20,015 ERROR [STDERR] at org.jnp.server.NamingServer.lookup(NamingServer.java:253) 14:26:20,015 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:492) 14:26:20,015 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:471) 14:26:20,016 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:347) 14:26:20,016 ERROR [STDERR] at com.sun.ecperf.supplier.web.SupplierDomainServlet.init(SupplierDomainServlet.java:86) 14:26:20,016 ERROR [STDERR] at javax.servlet.GenericServlet.init(GenericServlet.java:256) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:668) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) 14:26:20,017 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 14:26:20,018 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 14:26:20,018 ERROR [STDERR] at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) 14:26:20,018 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 14:26:20,018 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 14:26:20,019 ERROR [STDERR] at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) 14:26:20,019 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) 14:26:20,019 ERROR [STDERR] at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 14:26:20,019 ERROR [STDERR] at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) 14:26:20,020 ERROR [STDERR] at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) 14:26:20,020 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) 14:26:20,020 ERROR [STDERR] at
[JBoss-dev] [ jboss-Bugs-710396 ] Deployed .war unaccessible in Tomcat 4.1
Bugs item #710396, was opened at 2003-03-26 15:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=710396group_id=22866 Category: CatalinaBundle Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Stefan Reich (sreich) Assigned to: Scott M Stark (starksm) Summary: Deployed .war unaccessible in Tomcat 4.1 Initial Comment: Platform MacOSX 10.2.4, JDK 1.4.1, Jboss 3.2 latest CVS, Tomcat 4.1.24 (and 4.1.18). Some recent change broke tomcat deployment. Although there is no error during the deployment, the servlet can't be accessed. To reproduce try to access jmx-console. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=710396group_id=22866 --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
