-
1. Re: how to confgure JBoss to run without Jetty
juhalindfors Feb 6, 2003 8:28 PM (in response to jovial)remove jbossweb.sar directory from your server deploy dir
-
2. Re: how to confgure JBoss to run without Jetty
jovial Feb 6, 2003 9:49 PM (in response to jovial)thanks it helped.
together with it I had also to remove the following applications:
http-invoker.sar
jmx-console.war
web-client.war
This brings me to my next question.
In conf/jboss-service.xml file there is section called
"Class Loading" and the following is the configuration of MBean associated with it:
8083
false
If I take this service out of jboss-service.xml file
ejb-management.jar file on deployment complains it cannot find service=Webserver.
Webservice service should allow clients to download missing non EJB classes and resources over HTTP port 8083.
Do I really need this feature?
thanks,
dimitar -
3. Re: how to confgure JBoss to run without Jetty
juhalindfors Feb 7, 2003 8:11 PM (in response to jovial)no you don't really need that feature but unfortunately there's a hard dependency between ejb module and the 8083 right now so you can't really remove the service -- should be ok to block the port though.
-
4. Re: how to confgure JBoss to run without Jetty
kylev Feb 28, 2003 4:03 PM (in response to jovial)Ick. This hard dependancy periodically causes me deployment problems. Sometimes during deployment of my .ear, I get a runtime Thowable about "service=Webserver is not registered".
This is in a custom 3.0.6 server config that lacks Jetty and all .war files.
It seems to work fine some of the time (always on startup), but sometimes on hot-redeploy of the .ear this exception breaks deployment and I have to restart JBoss.
Sounds like a bad bug that should be filed and fixed. Off to sf.net I go. -
5. Re: how to confgure JBoss to run without Jetty
juhalindfors Mar 5, 2003 2:44 AM (in response to jovial)well if you're still looking at this, the problem is in the MBean proxy creation for WebService which throws an unchecked exception which is not caught, therefore failing the whole deployment