Problems with apache-2.0.47 + jakarta-tomcat-4.1.24

From: Ashwin (ashly007_at_rediffmail.com)
Date: 01/06/04

  • Next message: Naresh Agarwal: "difference between client, server, classic and hotspot jvms"
    Date: 6 Jan 2004 01:55:34 -0800
    
    

    Hello Everyone,
         I have been facing this problem for last 6 months...I am using
    apache-2.0.47 configured with jakarta-tomcat-4.1.24 + Logs4j(Logging)
    + Jotm(Transaction Management) + postgresql-7.3.3(Data Base).All the
    integration is being done properly as far the best of my knowledge.But
    after the server is started and after some 2-3 hours of hit the Tomcat
    server stops...i don't have any clue abt it I did checked the logs but
    it was not of much help.Initally i thought it might be a memory
    problem & checked it with OptimizeIt but there were no memory leaks at
    application level.Earlier the server used to stop after 2-3 days due
    to out of memory for which we did found out a bug in out server.xml
    where all unnecessary parameters were kept so after removing it the
    server works atleast for a weak or so.But now-a-days though there is
    enough memory left for the server the Tomcat suddenly gets killed.Is
    this a general issue or might be any configration parameter missing or
    any patches are available for this combination.

    please help as the site is Live.

    Thanks in advance
    Ashwin


  • Next message: Naresh Agarwal: "difference between client, server, classic and hotspot jvms"

    Relevant Pages

    • RE: server problems
      ... This newsgroup only focuses on SBS technical issues. ... >Thread-Topic: server problems ... >> web proxy service or SQL Server will normally use large memory. ...
      (microsoft.public.windows.server.sbs)
    • Re: Allocated Memory alerts
      ... If you do not encounter any real server performance issue, ... the high memory usage is expected. ... The Health monitor is running on the SBS server. ... A memory allocation threshold is configured on the particular monitored ...
      (microsoft.public.windows.server.sbs)
    • Re: FTS Performance in SQL 2005
      ... I don't think you have left enough memory for the OS and MSSearch. ... Looking for a SQL Server replication book? ... Looking for a FAQ on Indexing Services/SQL FTS ...
      (microsoft.public.sqlserver.fulltext)
    • RE: server problems
      ... > web proxy service or SQL Server will normally use large memory. ... > the SBS server and sends the alert when the value reaches the threshold. ...
      (microsoft.public.windows.server.sbs)
    • Re: Alocated Memory Error (SQLSERVR)
      ... but my understanding is that the MSDE instances are designed to ... and you don't want it grabbing all that RAM. ... running but non ever going about 200mb of memory usage. ... Server 2000 SP4, ...
      (microsoft.public.windows.server.sbs)