If you are using a JBoss 3.0.x or higher, even if you did not get a Tomcat bundle, you will have an equivalent servlet container bundle using Jetty.
I'll assume you have one of these distributions. In your deploy directory for your run-time instance there will be a SAR deployment for the Jetty servlet container, usually server/default/deploy/jbossweb.sar or server/default/deploy/jbossweb-jetty.sar. YMMV.
In this will be a META-INF/jboss-service.xml. This will have the default listeners for HTTP/HTTPS/AJP13. Modify the port binding values appropriately so they do not clash with existing infrastructure.
Thanks a lot for the tip jonlee!!!! It worked like a dream...
I also found in the jboss-service.xml file that another option to change the default 8080 port would be using: java -Djetty.port=<a port number>
Just one more tiny question: is Jetty included for management purposes or does it provide full servlet container functionality to use it, let's say, instead of Tomcat in a production enviroment?
Again: Thanks a lot!!!
Jetty is a full-fledged servlet engine. You will find faster and more scalable performance for your web-apps that access EJBs if you use the JBoss embedded servlet engines (either Tomcat or Jetty). The reason is that they don't perform their accesses over a network interface - servlet -> EJB is performed internal to the JVM. Also objects are not duplicated at the servlet (client) and the EJB when in the same JVM so memory usage is minimised.
You're totally right: the JBoss-Tomcat/Jetty bundle for production enviroment would be the obvious choice to deploy J2EE applications.
I'm not familiar with Jetty buy it seems like a good Tomcat competitor and since JBoss can couple with either, What do you think should be considered to choose over the two?
I like Jetty as it is lightweight, has a smaller in-memory size and has some flexibilities for complex configurations. Some people like Tomcat because of support for advanced servlet specs (most people don't use them). YMMV.
Try it. For advanced high-load support you may want to get the Jetty full-bundle with the SocketChannelListener with non-blocking IO - the standard JBoss 3.2.x build supports Java JDK 1.3.x and so does not have the non-blocking IO component of Java JDK 1.4.x.
See http://www.webperformanceinc.com/library/ServletReport/ for performance details.
Ultimately, your choice but Jetty is worth trying. Having choice is always good. ;)