> Can you please post some more details on your exact scenario, viz:
Will try.
> + is this a hot redeploy of Jetty, especially is it a hot redeploy
> when some webapps were already deployed?
Not a redeploy.
> + have you modified your jetty jboss-service.xml file to include a
> webapp (long shot, but I have to ask)?
Yes, before </Configure> there is
<Call name="addWebApplication">
<Arg>/</Arg>
<Arg><SystemProperty name="jboss.home.dir" default="."/></Arg>
</Call>
> + what code base are you running off?
JBoss HEAD
> + what kind of log trace do you see?
I mailed that already but here you go again:
23:56:35,547 INFO [Jetty] ResourceHandler started in
file:/C:/home/jason/workspace/jboss/jboss-all/build/output/jboss-3.0.0beta2/
23:56:35,547 INFO [Jetty] Started ResourceHandler in
WebApplicationContext[/,C:\home\jason\workspace\jboss\jboss-all\build\output\jboss-3.0.0beta2]
23:56:35,547 INFO [Jetty] Started NotFoundHandler in
WebApplicationContext[/,C:\home\jason\workspace\jboss\jboss-all\build\output\jboss-3.0.0beta2]
23:56:35,567 INFO [Jetty] Started SocketListener on 0.0.0.0:8080
23:56:35,567 ERROR [JettyService] multipule exceptions...
23:56:35,577 ERROR [JettyService] exception
java.lang.ClassCastException: org.jboss.system.MBeanClassLoader
at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:269)
at
org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:203)
at
org.mortbay.jetty.servlet.ServletHandler.start(ServletHandler.java:380)
at
org.mortbay.jetty.servlet.FilterHandler.start(FilterHandler.java:160)
at org.mortbay.http.HttpContext.startHandlers(HttpContext.java:1449)
at org.mortbay.http.HttpContext.start(HttpContext.java:1420)
at
org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:365)
at org.mortbay.http.HttpServer.start(HttpServer.java:186)
at org.jboss.jetty.JettyService.startService(JettyService.java:236)
at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162)
at java.lang.reflect.Method.invoke(Native Method)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:779)
at $Proxy0.start(Unknown Source)
at
org.jboss.system.ServiceController.start(ServiceController.java:343)
at java.lang.reflect.Method.invoke(Native Method)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:78)
at $Proxy3.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:270)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:470)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:347)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:327)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:309)
at java.lang.reflect.Method.invoke(Native Method)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:78)
at $Proxy2.deploy(Unknown Source)
at
org.jboss.deployment.scanner.DirectoryDeploymentScanner.deploy(DirectoryDeploymentScanner.java:176)
at
org.jboss.deployment.scanner.DirectoryDeploymentScanner.scan(DirectoryDeploymentScanner.java:138)
at
org.jboss.deployment.scanner.DirectoryDeploymentScanner.startService(DirectoryDeploymentScanner.java:607)
at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162)
at java.lang.reflect.Method.invoke(Native Method)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:779)
at $Proxy0.start(Unknown Source)
at
org.jboss.system.ServiceController.start(ServiceController.java:343)
at
org.jboss.system.ServiceController.start(ServiceController.java:360)
at java.lang.reflect.Method.invoke(Native Method)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:331)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:211)
at org.jboss.Main.boot(Main.java:127)
at org.jboss.Main$1.run(Main.java:335)
at java.lang.Thread.run(Thread.java:484)
23:56:35,577 INFO [JettyService] Started
23:56:35,577 INFO [MainDeployer] Successfully completed deployment of
package:
file:/C:/home/jason/workspace/jboss/jboss-all/build/output/jboss-3.0.0beta2/server/master/deploy/jetty-service.xml
> Jetty does not do anything with JSP unless we have got webapp contexts
> already registered when we receive a start. This could occur, for
> example, if you deployed Jetty, deployed some webapps, did a stop and
> restart on the Jetty service using JMX.
All I wanted was for Jetty to server up the files under jboss.home.dir,
so I could test net boot, so I needed to modify the config to add a
simple web app, as there isn't anything to deploy here.
I took the generated jetty-plugin.sar, copied it to
jboss/lib/jetty-plugin.jar and then copied the jboss-service.xml (which
is used inside of the sar) to servers/default/deploy.
It starts up, but it complains. I had to unwrap the MultiException to
make sence of it too...
Hope this is enough.
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development