Announcement Announcement Module
Collapse
No announcement yet.
TCServer (tomcat 6) - Logfile size Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • TCServer (tomcat 6) - Logfile size

    Hi,

    I'm using tcServer with the instances created with Tomcat 6v. I have an issue with logfile size.

    When catalina.out file size reaches 2GB, my application is not responding.
    I can see the application status as 'running'.

    1) Is there any restriction in TCServer on logfile size restriction?
    2) Do I need to do any config changes in conf/logging.properties file?


    Thanks

  • #2
    First, with proper logging configuration, catalina.out should never get that big. Even if it does, the 2GB limit is likely imposed by your OS or filesystem. See http://stackoverflow.com/questions/1...ith-tomcat-6-0

    Comment


    • #3
      Originally posted by baarod View Post
      First, with proper logging configuration, catalina.out should never get that big. Even if it does, the 2GB limit is likely imposed by your OS or filesystem. See http://stackoverflow.com/questions/1...ith-tomcat-6-0
      Thanks for the reply.

      I'm ok with the huge content logging by the application and don't want to reduce the logging in conf/logging.properties. So, let the application create logs more than 2 GB..

      I have other standalone Non-Java programs running in the same server that creates log files more than 2 GB.

      My concern is about "why TCServer instance is not able to log more than 2 GB in a file and the application is not responding?"

      Is there any restriction in TCServer config?

      Thanks

      Comment


      • #4
        What if I told you that by default you are logging two copies of each log record and that you would be likely to alleviate the 2GB catalina.out that's causing the application to stop responding.

        Please see: http://tomcat.apache.org/tomcat-7.0-...oductive_usage

        So the only thing that will end up in catalina.out are uncaught exception traces, thread dumps you've requested by signal, and log output of code that explicitly calls System.out or System.err .

        Also please note: http://pubs.vmware.com/vfabric53/top...asynch-logging

        "By default, the tc Runtime thread that handles incoming Web requests is the same thread that writes to the log file, such as catalina.out. Thus if a resource issue causes the thread writing to the log file to block, the incoming Web request is also blocked until the thread is able to finish writing to the log file."

        So in addition to reducing the duplicate log volume going to catalina.out, potentially avoiding the 2GB file size that seems to cause tc Server to stop responding for you, you can implement async logging that should eliminate the possibility of that occurring again.

        Comment

        Working...
        X