From: Peter T. A. <pt...@ps...> - 2002-07-30 19:39:58
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Jul 30, 2002 at 11:54:38AM -0700, Scott M Stark wrote: > That is correct. It uses the configuration embedded in the > tomcat4-service.xml > descriptor. thanks for the reply! i am unable to find a tomcat4-service.xml in the jboss directory structure. where is my jboss getting its tomcat config? i am using the integrated jb 2.4.4 w/ tc 4.0.1. > > xxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > Chief Technology Officer > JBoss Group, LLC > xxxxxxxxxxxxxxxxxxxxxxxx > ----- Original Message ----- > From: "Peter T. Abplanalp" <pt...@ps...> > To: <jbo...@li...> > Sent: Tuesday, July 30, 2002 11:38 AM > Subject: [JBoss-user] JBoss & Tomcat > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > hi all. i am trying to integrate jboss/tomcat with apache and after > > some research have come to the conclusion that the tomcat in > > jboss/tomcat does not use the server.xml file in ~jboss/catalina/conf. > > has anyone else noticed this? am i missing something? if this is > > true, what config does the tomcat in jboss/tomcat use? > > > > i came to this conclusion because tomcat did not start a listener on > > port 8009 after i defined a connector for that port in server.xml. i > > then put deliberate syntax errors in the file expecting jboss to > > complain when tomcat didn't start becasue the config was hosed but no, > > jboss and tomcat started fine. > > > > thanks. > > > > - -- > > Peter Abplanalp > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Dice - The leading online job board > for high-tech professionals. Search and apply for tech jobs today! > http://seeker.dice.com/seeker.epl?rel_code=31 > _______________________________________________ > JBoss-user mailing list > JBo...@li... > https://lists.sourceforge.net/lists/listinfo/jboss-user - -- Peter Abplanalp Email: pt...@ps... PGP: pgp.mit.edu -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9RuuJggA8sH0iRXQRAjk+AKC6XMDF3kxcHAJrupbCvpMqWVYefACfWduD CGnkhGrd5Pg2nEf81Y+Q9b8= =aAlI -----END PGP SIGNATURE----- |