Kbase P178621: AppServer server log continues to increase in size even though there was a roll over to a new log fi
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/4/2011 |
|
Status: Unverified
SYMPTOM(s):
AppServer server log continues to increase in size even though there was a roll over to a new log file.
Log threshold set at 5 MB
Number of logs set to 6
Log 1 reached 168 MB and log 5 reached 191 MB
In order to stop the logging, it was required that they kill the processes still attached to those log files.
Error connecting to the JMS AppServer service.
[10/12/05@10:24:49.427-0600] P-007788 T-006272 1 AS -- ** ABL Debug-Alert Stack Trace **
[10/12/05@10:24:49.427-0600] P-007788 T-006272 1 AS -- --> handleError jms/impl/errorhndlr.p (D:\Progress\oe102a\jms\impl\errorhndlr.r) at line 165
[10/12/05@10:24:49.427-0600] P-007788 T-006272 1 AS -- beginSession jms/impl/session.p (D:\Progress\oe102a\jms\impl\session.r) at line 1605
[10/12/05@10:24:49.427-0600] P-007788 T-006272 1 AS -- startSonicSession si/sim320-mt.p (D:\EPICOR905\Server\si\sim320-mt.r) at line 1187
[10/12/05@10:24:49.427-0600] P-007788 T-006272 1 AS -- si/sim320-mt.p (D:\......\Server\si\sim320-mt.r) at line 1106
[10/12/05@10:24:49.427-0600] P-007788 T-006272 1 AS -- si/sim320.p (D:\.....\Server\si\sim320.r) at line 4733
[10/12/05@10:24:49.427-0600] P-007788 T-006272 1 AS -- agent/RunTask.p (D:\.....5\Server\agent\RunTask.r) at line 1947
javax.jms.JMSException: The broker is not accepting messages at this priority
Multi-Company Server Process is implementing flow control.
javax.jms.IllegalStateException: The session is closed.
FACT(s) (Environment):
Windows
OpenEdge 10.2A 64-bit
OpenEdge Category: Database
OpenEdge Server Technology Category: AppServer
CAUSE:
This is expected behavior if an AppServer process is still connected to the log file when the switch to the next log file happens.
FIX:
The process that is still writing to the old log file needs to be stopped.