At various intervals and in diverse environments, GroupWise WebAccess discontinues to function. The threads seem to be available, but no one can log in past the 'Go' page.
A. JAVA page faults in the LOGGER.TXT
B. JAVA stops functioning altogether.
C. Tomcat stops functioning.
D. Server may abend in LIBC.NLM
E. Server may experience long term high utilization in JAVA.
These are not all the symptoms that may occur and the symptoms may change over time for, as yet, undetermined reasons.
Currently there are only workarounds for this issue. The main problem, JAVA faulting, has been reported to development.
As of 2.20.08 the current workarounds and patches have helped to alleviate the issue:
A. The latest winsock patch for NetWare 6.5 helps to alleviate the problem to a great degree.
B. Manually exiting JAVA and restarting Tomcat most often gives relief for periods of time.
* Many administrators put this into a CRON job to perform this function at varying intervals.
This has worked well for the vast majority of customers. (see TID - 10024685 for suggestions)
C. In a Windows Server environment, an easy step to use is the Task Scheduler to stop and restart services.
The Scheduler can run a .bat file intermittently.
As of 2.20.08 the presumption given all of the data found is that the problem lies in JAVA. However, the environment change was made in WebAccess. Something changed in the way GroupWise WebAccess works with JAVA that may cause it to fault over the course of time. Both camps are investigating the issue and in almost all circumstances the workarounds are more than sufficient to significantly reduce or eliminate unnecessary outage.