- 
        1. Re: Configuration questionjoelvogt Oct 14, 2002 4:57 AM (in response to ashahata)yes, tomcat will start with jboss. The server.xml is not looked at though in this config, so it's not going to help you. 
 And jboss could be a jsp container as well if it wanted to. But why? when jetty and tomcat already do the job so well.
- 
        2. Re: Configuration questionashahata Oct 14, 2002 5:20 AM (in response to ashahata)Any idea which config file would I look at if I wanted to change the default listening port? I believe it should be under jboss somewhere!? 
 Thanks
- 
        3. Re: Configuration questionprabhakar Oct 14, 2002 11:04 AM (in response to ashahata)Edit the jboss-service.xml in: 
 $jboss_home\server\$type\deploy\jbossweb.sar\META-INF
 -prabhakar
- 
        4. Re: Configuration questionpope Oct 15, 2002 11:17 AM (in response to ashahata)$JBOSS_DIST/server/$CONF_NAME/conf/jboss-service.xml 
 There are only solutions !
 ---
 by Pope
- 
        5. Re: Configuration questiondlinuxt65 Oct 16, 2002 12:25 PM (in response to ashahata)Hi! 
 I downloaded Jboss-3.0.0 with Tomcat-4.0.3 and installed on RH 7.3. When I started Jboss with the run script, I see that port 8080 is open but when I tried with http://localhost:8080 I received the following error messages:
 Apache Tomcat/4.0.3 - HTTP Status 500 - No Context configured to process this request
 Instead, if I start manually Tomcat, after Jboss run, seems to work properly: I see index page of tomcat-jacarta project.
 Thanks
- 
        6. Re: Configuration questionprabhakar Oct 16, 2002 1:05 PM (in response to ashahata)JBoss does not come with any default webapps/context installed. So if you go to http://localhost:8080, you won't see anything. Deploy a webapp and try it. If you are checking to see if jboss is running, try http://localhost:8080/jmx-console. That will show you all the MBeans in the current server. 
 -prabhakar
- 
        7. Re: Configuration questiondlinuxt65 Oct 17, 2002 6:54 AM (in response to ashahata)Thanks for reply 
 I tried with http://localhost:8080/jmx-console but I received the following error messages:
 Apache Tomcat/4.0.3 - HTTP Status 500 - No Context configured to process this request
 Why the same reply of http://localhost:8080 ?
 Instead if I run http://localhost:8082/ I see then page with the Agent View.
- 
        8. Re: Configuration questionjendicott Oct 17, 2002 12:10 PM (in response to ashahata)I was having the same problem. The documentation (Quick Start Guide) says that http://localhost:8082 should show al JBoss components which are running. When I used that I got a "cannot find server" error. Using http://localhost:8080/jmx-console as suggested here did work. 
- 
        9. Re: Configuration questiondciarnie Oct 17, 2002 1:25 PM (in response to ashahata)I think that the change from 8082 to 8080/jmxconsole was made for 3.0.3. 3.0.0 still had the old behaviour. 
 Dan.
 
     
     
     
     
     
    