Originally Posted by Craig
|
Also, GWWEBUP.
"Jim Michael" <jkmichael@myrealbox.com> wrote in message
news:PH13e.16$hI5.4@prv-forum2.provo.novell.com...
> Stormy Maddux wrote:
>
>> Occassionally although the webaccess agent appears to be running, but no
>> one can log in - the page does not respond. Does anyone else see these
>> hangups? Any fix.
>
> We never saw hangups like that with 6.5.2 (we're on 6.5.4 now). You would
> be wise to upgrade to 6.5.4, but I doubt that is your problem.
>
>> Otherwise, is there a graceful way to unload webaccess, the
>> apache/tomcat components and start them back up?
>
> When webaccess stops responding, I would restart each component
> separately, to see which one is the culprit... my guess is that it's
> Tomcat... see below.
>
>> ap2webup
>
> ap2webup starts the instance of Apache that webaccess uses. You can do
> ap2webdn to stop it.
>
>> tomcat4
>
> tomcat4 starts the instance of tomcat that webaccess uses. It can be
> stopped via tomcat4 stop
>
>> Right now I am doing a complete reboot....
>
> No need to... just try apache first, then tomcat.
>
>
> --
> Jim
> NSC SYsop
|
tried the starting and stopping of the tomcat and apache, but still the only apparent fix is downing the server as a whole - heard that the document viewer might be the trigger for the java issues at the root - any ideas?