[JBoss-user] Catalina Context Path setting

2002-04-03 Thread Lex
I understand that 2.4.4 + Catalina doesn't support parsing the server.xml file. I am trying to setup a Context path that would normally be in the server.xml. From what I have read I am thinking I should be able to do this in the jboss.jcml. I took a shot at getting it to work (cuz I don't see

[JBoss-user] Catalina Context Path setting

2002-04-03 Thread Lex
I understand that 2.4.4 + Catalina doesn't support parsing the server.xml file. I am trying to setup a Context path that would normally be in the server.xml. From what I have read I am thinking I should be able to do this in the jboss.jcml. I took a shot at getting it to work (cuz I don't see

[JBoss-user] HTTP Request Logs

2001-08-02 Thread Lex
What are people generally doing to log HTTP requests when running Tomcat 3.x in same VM as JBoss (ie not using Apache)?   Are we forced to wite our own logfiles?   Regards

RE: [JBoss-user] JBoss Shutdown - On its own??

2001-07-20 Thread Lex
No such luck - we always start it with the run.sh which runs it in the background.  Good thought though. Thanx for the reply, Mike   > Maybe you logged in, started JBoss in the foreground, then logged > out? > --- > Michael R. Maraya > ------ >> From: Lex[SMTP:[EMAIL

[JBoss-user] JBoss/Tomcat - Monitoring Requests

2001-07-20 Thread Lex
Is there any way to monitor the number of current number of http requests and see things like the URL they are requesting and what IP they are coming from?  I know Apache has such a status page that can be hit to show this type of info.   Also, is there any way to have a log of these http re

RE: [JBoss-user] Out of memory error

2001-07-19 Thread Lex
Yep - we are using RedHat Linux 7.0 -Mike > I think it's more of a Linux with JDK1.3.1 thing, assuming you're> > using Linux, of course. As far as I know, there were no major > memory-related architectural changes between 1.3 and 1.3.1. --- Michael R. Maraya >>

RE: [JBoss-user] Out of memory error

2001-07-19 Thread Lex
We found the same problem during stress testing with JBoss 2.4 Beat/ Tomcat 3.2.2 JDK1.3.1.  We had another amchine with JDK 1.3.0 that did not have the problem.  We Downgraded the problem machine to 1.3.0 and the problem went away.  Is there some explaination for this?  Is this a JBoss vs.