The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Tomcat restart after context changes

Discussion in 'General Discussion' started by steele, Nov 10, 2003.

  1. steele

    steele Active Member

    Joined:
    Aug 27, 2003
    Messages:
    35
    Likes Received:
    0
    Trophy Points:
    6
    Hi,
    I am running Tomcat 3.2.4 on my Cpanel server. I have following problem:
    Whenever the user changes any of his class files, I have to restart the Tomcat for the changes to take effect.
    When he adds a new file, this file is immediately working, but when he changes an existing file, I have to restart the Tomcat for the context changes to work.
    I am a newbie in this area, and I'd be happy if anybody could give me suggestions how to fix this. I've read in one post that the solution would be to set up a cron job to restart Tomcat for example every 5 minutes, but I don't think this is the smartest thing to do.
    Here's an example of entry in my server.xml config file:

    <Host name="www.$domain.com" appBase="/home/$domain/public_html/">
    <Context path="/"
    docBase="/home/$domain/public_html/"
    reloadable="true"
    debug="1"
    />
    </Host>

    Thanks a lot for any help or suggections.
     
  2. casey

    casey Well-Known Member

    Joined:
    Jan 17, 2003
    Messages:
    2,303
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    If there is trouble, it will find me
    I had a cron job set up for restarting at 2 am every day. I told my customers that they would see the changes reflected after the restart.

    Recently I upgraded to 4.1.12, so I hope that I don't have to restart it anymore...
     
  3. steele

    steele Active Member

    Joined:
    Aug 27, 2003
    Messages:
    35
    Likes Received:
    0
    Trophy Points:
    6
    Casey,

    thanks for input. I guess I'm not the only one with this problem.
    Unfortunatelly, this is not solution for me. Client is developing and testing constantly, he needs to see changes instantly.

    how is it with version 4.1.12?
    do I need to uninstall the old version to upgrade, or can I simply install it over the old one?


    Any other suggestions?

    Thanks!
     
Loading...

Share This Page