WebAccess becomes unavailable with a 503 error. This gets acknowledged by Novell as a Java issue. See TID# 3977129 GroupWise WebAccess Stops Working.
In here the writer mentions to help alleviate the problem one could set up a CRONjob and reference TID# 10024685 How to use CRON.NLM for a brief overview on how to use the CRONTAB file.
Novell does not support the use of CRON, so I'm sharing my CRONTAB file contents with you.
Just drop the following text in your CRONTAB file in sys:\etc\ on the WebAccess server and load up the CRON.NLM. This will stop WebAccess, Java, Tomcat and Apache at 2:00am and start them at 2:01am every day. If you do not have an existing CRONTAB file, don't worry, just create a blank .txt file and remove the .txt extension.
If this doesn't work, check the CRONLOG in the same directory and check the path of these files.
0 2 * * * stopweb.ncf
0 2 * * * java -exit
0 2 * * * ap2webdn.ncf
0 2 * * * tc4stop.ncf
1 2 * * * apache2.nlm
1 2 * * * tomcat4.ncf
1 2 * * * strtweb.ncf
NetWare 6.5sp7 GroupWise 7.0.3hp1.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.