Re: Running tomcat on Debian Sarge

2005-06-09 Thread Oto Bossert
Yoo,

What dit you do untill now?
Do you have a firewall?

Greetings O.

On 6/8/05, blijblijblij [EMAIL PROTECTED] wrote:
 All,
 
 Anybody here who knows a foolproof site for setting up tomcat under
 debian?! I'm an newbie when it come to tomcat on linux, but I really
 would like this to work... Al I seem to be getting is an connection
 refused on my localhost... Some pointer could be handy, but I seem to be
 having problems googling for the correct manuals/howto's.
 
 Thanks in advance!
 
 Blijblijblij
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Apache+Tomcat

2005-05-11 Thread Oto Bossert
Yoo,

If you need PHP than standalone tomcat is not an option you want, to my opinion!

Greetings O.

On 5/11/05, Anoop kumar V [EMAIL PROTECTED] wrote:
 We use tomcat standalone on production - most of our pages are dynamic (95%)
 and the user load is ~7000 and it has been behaving awesome - we use 4.1.31.
 
 hth,
 Anoop
 
 On 5/11/05, Nikola Milutinovic [EMAIL PROTECTED] wrote:
 
  Praveen KUMAR wrote:
 
   Hello,
  
   I am little bit confuse in following decision:
  
   Should be use
  
   1- Apache (2.0.54) + Tomcat (5.0.28) in production with tomcat
   listener (through Coyote connector) configured with mod_jk (1.2.12)
   with apache
   2- Or Standalone Tomcat (with their standard apache provided by tomcat)
  
   What would be difference in both the scenarios in terms of performance
   and reliability?
 
  Scenario 2 is easier to implement, there are fewer things that can break
  and less config files to maintain. Scenario 1 gives you a unified
  setting of your web space. You just simply know that you have one
  front-end, Apache. In that case Apache receives the initial HTTP request
  and can handle parts of it.
 
  The most interesting aspect of such a setup are authentication and
  redirection. While Tomcat has some rudimentary aliasing, Apache is
  superrior when it comes to URL rewriting, redirections and proxying. On
  the field of authentication, Tomcat supports HTTP-Basic, HTTP-Digest and
  SSL-based authentication. Apache can add to that SPNEGO (Kerberos5, read
  Microsoft Active Directory Service), plus several backend mechs for the
  Basic and Digest (LDAP, MySQL, PostgreSQL,...). Tomcat can only benefit
  from that.
 
  My advice to you, if you're learning or experimenting, use Tomcat
  StandAlone. If you're thinking production, gather your requrements and
  see what fits you best. It could again very well be TC standalone.
 
  Nix.
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 --
 Thanks and best regards,
 Anoop
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Want to run servlets from other directory than webapps

2005-05-11 Thread Oto Bossert
Yoo,

Do you use tomcat stand-alone? Or with Apache

Putting a context in server.xml should work, but this is not the
prevered way in tomcat 5!

Greetings O.


On 5/11/05, Raueber Hotzenplotz [EMAIL PROTECTED] wrote:
 Hi
 
 I've got Tomcat-5.0.27-r5 installed. Running servlets
 (localhost) located in
 /opt/tomcat5/webapps/ROOT/WEB_INF/classes is no
 problem.
 
 What do I need to do to run servlets from my user
 directory (e.g. /home/user/myapp)?
 
 I've tried to use http://localhost:8080/admin to add
 an additional context, setting path and docbase to
 /home/user/myapp, but this doesn't work.
 
 I've also tried to change appbase to /home/user/myapp
 in conf/server.xml, but again no success.
 
 I've uncommented the 'invoker' lines in conf/web.xml -
 for the moment anyway:
 
 servlet
 servlet-nameinvoker/servlet-name
 servlet-class
   org.apache.catalina.servlets.InvokerServlet
 /servlet-class
 init-param
 param-namedebug/param-name
 param-value0/param-value
 /init-param
 load-on-startup2/load-on-startup
 /servlet
 
 servlet-mapping
 servlet-nameinvoker/servlet-name
 url-pattern/servlet/*/url-pattern
 /servlet-mapping
 
 How do you configure Tomcat? Do you use the admin tool
 or do you do it manually? The admin tool works strange
 e.g. after deleting some context it was still in the
 list.
 
 Thanks!
 
 Regards, Rudi
 
 
 ___
 How much free photo storage do you get? Store your holiday
 snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat 5 slow, it's in production, please help!

2005-05-07 Thread Oto Bossert
Yoo,

Yes switch to jk2 is faster!

set parameters in OPT_CATALINA with -server Xmx=? and Xms=?

Sorry values depend on your available memory on the server, parameters
could be different with your version, check or google for correct parameters,
should improve performance...

Another option could be your code, have a good look at it and try to optimize...

Greetings O.

On 5/6/05, Jeffrey [EMAIL PROTECTED] wrote:
 I use just mod_jk, not jk2 I believe. I do have
 connectionTimeout=2 set to AJP connector in
 server.xml
 
 Is there any performance issues with jk? Should I
 switch to jk2?
 
 Thanks.
 
 --- e [EMAIL PROTECTED] wrote:
  What JK version do you use?  To quote Mladen:
 
  You are probably using prefork mpm, so there is no
  way to
  control the number of connections to Tomcat in any
  way, trough
  mod_jk. You can limit it only by setting MaxClients
  in the httpd.conf
  to the maximum number desired.
  Because of pre-forking mechanism each child process
  will eventually
  establish a single connection to Tomcat, thus the
  number of connections
  will rise from StartServers to MaxClients.
 
  So there are two solutions for prefork.
  1. Make maxThreads==MaxClients
  2. Add connectionTimeout=2 to AJP connector.
 
  On 5/6/05, Jeffrey [EMAIL PROTECTED] wrote:
   I have a apache/tomcat environment that has some
   problems recently. The environment has the
  following:
   1.  Apache 1.3
   2.  Tomcat 5.0.28 (Max memory 384mb)
   3.  JDK 1.4.2_06
  
   My apache has MaxClient set to 256 (apache
  default).
   The maxThread for tomcat is 500. The site is a
   database driven site.
  
   It seems working fine when load is low. But when
  there
   are more than 150 threads (from the sever status
  view
   of the tomcat manager), it's response time is very
   slow (5 - 10 minutes). I have tested the database
   connections, they seem responding fairly well.
  
   Interesting thing is that most of time the slow
   response time only happens when a user login. Once
  the
   user login and get the main menu page, the user
  will
   get a good response time. Is it related to
  KeepAlive
   connections.
  
   Another strange thing is that many threads always
  show
   up in the server status view on the tomcat html
   manager page even though I am sure the request has
   gone (I tested this by making a request, then
  close
   the browser).
  
   My CPU usage is low when the slowdown is
  experienced
   (Using the top command on this solaris box which
  has
   old solaris operating system 2.6? with 1GB memory.
  
   I set the session timeout time to 5 minutes, but
  in
   the session view of tomcat manager, I see message
  30
   - 40 minutes:136 sessions. How a session that is
   more than 30 minutes is still there. Maybe I don't
   understand this message correctly.
  
   Please advice. This is a production machine. Helps
  are
   greatly appreciated.
  
   Thanks.
  
   Jeffrey.
  
   Discover Yahoo!
   Get on-the-go sports scores, stock quotes, news
  and more. Check it out!
   http://discover.yahoo.com/mobile.html
  
  
 
 -
   To unsubscribe, e-mail:
  [EMAIL PROTECTED]
   For additional commands, e-mail:
  [EMAIL PROTECTED]
  
  
 
 
 -
  To unsubscribe, e-mail:
  [EMAIL PROTECTED]
  For additional commands, e-mail:
  [EMAIL PROTECTED]
 
 
 
 __
 Do You Yahoo!?
 Tired of spam?  Yahoo! Mail has the best spam protection around
 http://mail.yahoo.com
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat 5 slow, it's in production, please help!

2005-05-06 Thread Oto Bossert
Yoo,

Probably you already looked at it but :

1) Make sure not to use reloadable in context descriptions.
2) Start tomcat with optimal java parameters, concerning memory heap and stack
3) Make sure that connections to database are minimal, do requery if
answer is always the
same...

Good luck,

Greetings O. 

On 5/6/05, Jeffrey [EMAIL PROTECTED] wrote:
 I have a apache/tomcat environment that has some
 problems recently. The environment has the following:
 1.  Apache 1.3
 2.  Tomcat 5.0.28 (Max memory 384mb)
 3.  JDK 1.4.2_06
 
 My apache has MaxClient set to 256 (apache default).
 The maxThread for tomcat is 500. The site is a
 database driven site.
 
 It seems working fine when load is low. But when there
 are more than 150 threads (from the sever status view
 of the tomcat manager), it's response time is very
 slow (5 - 10 minutes). I have tested the database
 connections, they seem responding fairly well.
 
 Interesting thing is that most of time the slow
 response time only happens when a user login. Once the
 user login and get the main menu page, the user will
 get a good response time. Is it related to KeepAlive
 connections.
 
 Another strange thing is that many threads always show
 up in the server status view on the tomcat html
 manager page even though I am sure the request has
 gone (I tested this by making a request, then close
 the browser).
 
 My CPU usage is low when the slowdown is experienced
 (Using the top command on this solaris box which has
 old solaris operating system 2.6? with 1GB memory.
 
 I set the session timeout time to 5 minutes, but in
 the session view of tomcat manager, I see message 30
 - 40 minutes:136 sessions. How a session that is
 more than 30 minutes is still there. Maybe I don't
 understand this message correctly.
 
 Please advice. This is a production machine. Helps are
 greatly appreciated.
 
 Thanks.
 
 Jeffrey.
 
 Discover Yahoo!
 Get on-the-go sports scores, stock quotes, news and more. Check it out!
 http://discover.yahoo.com/mobile.html
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat 5 slow, it's in production, please help!

2005-05-06 Thread Oto Bossert
Yoo, 

Sorry bas typo, in 3) I meant, do NOT requery ;)

Greetings O.


On 5/6/05, Oto Bossert [EMAIL PROTECTED] wrote:
 Yoo,
 
 Probably you already looked at it but :
 
 1) Make sure not to use reloadable in context descriptions.
 2) Start tomcat with optimal java parameters, concerning memory heap and stack
 3) Make sure that connections to database are minimal, do requery if
 answer is always the
 same...
 
 Good luck,
 
 Greetings O.
 
 On 5/6/05, Jeffrey [EMAIL PROTECTED] wrote:
  I have a apache/tomcat environment that has some
  problems recently. The environment has the following:
  1.  Apache 1.3
  2.  Tomcat 5.0.28 (Max memory 384mb)
  3.  JDK 1.4.2_06
 
  My apache has MaxClient set to 256 (apache default).
  The maxThread for tomcat is 500. The site is a
  database driven site.
 
  It seems working fine when load is low. But when there
  are more than 150 threads (from the sever status view
  of the tomcat manager), it's response time is very
  slow (5 - 10 minutes). I have tested the database
  connections, they seem responding fairly well.
 
  Interesting thing is that most of time the slow
  response time only happens when a user login. Once the
  user login and get the main menu page, the user will
  get a good response time. Is it related to KeepAlive
  connections.
 
  Another strange thing is that many threads always show
  up in the server status view on the tomcat html
  manager page even though I am sure the request has
  gone (I tested this by making a request, then close
  the browser).
 
  My CPU usage is low when the slowdown is experienced
  (Using the top command on this solaris box which has
  old solaris operating system 2.6? with 1GB memory.
 
  I set the session timeout time to 5 minutes, but in
  the session view of tomcat manager, I see message 30
  - 40 minutes:136 sessions. How a session that is
  more than 30 minutes is still there. Maybe I don't
  understand this message correctly.
 
  Please advice. This is a production machine. Helps are
  greatly appreciated.
 
  Thanks.
 
  Jeffrey.
 
  Discover Yahoo!
  Get on-the-go sports scores, stock quotes, news and more. Check it out!
  http://discover.yahoo.com/mobile.html
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]