POA 6.0.4 status shows Busy 50

[jb8691]

Seemingly randomly, the POA will jump up to show Busy 50. Users will
start timing out and be unable to use their clients if in online mode.
Caching and remote users will get connection failed, and the status
window shows "The server is busy. GroupWise will try to connect again in
X minutes."

The server will stay this way for 15 to 45 minutes and then slowly the
Busy state will drop back to 0 to 1 as normal.

While this is happening, I can not find any thing obviously wrong with
the server. The GWIA, MTA, and WebAccess modules all seems to be
functioning normally.

Can anyone tell me what or where to look for a log of events likely to
be related to this?

[Automatic Reply]

jb8691,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://support.novell.com/forums/

[Tommy Mikkelsen]

Switch the POA into verbose logging, and then look into that asap when
it happens

[Michael Bell]

Post by Tommy Mikkelsen
Switch the POA into verbose logging, and then look into that asap when
it happens

If I was going to guess, some auto-cleanup up options or manual deletion.

[Tommy Mikkelsen]

Post by Michael Bell
If I was going to guess

Same here....but the log should tell...

[jb8691]

ok I have the verbose logs enabled now, I will wait for it to happen
again and follow up here in this thread.