Salesforce

Can PASOE Agent logs be rolled over based on file size?

« Go Back

Information

 
TitleCan PASOE Agent logs be rolled over based on file size?
URL NameCan-PASOE-agent-logs-be-rolled-over-based-on-file-size
Article Number000187540
EnvironmentProduct: OpenEdge
Version: 11.7, 12.0 and later
OS: All supported platforms
Other: PASOE
Question/Problem Description
Can PASOE agent logs be rolled over based on file size?
Is it possible to configure the PASOE MSAgent log to roll over to a new log once a size threshold is reached? 
How to break up or split PASOE agent logs before they reach an unmanageable size ?
What parameter is used to configure MSAgent Session Manager agent.log files?
Why does the PASOE MSA agent.log not roll based on size in the conf/logging.xml file ?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement NumberOPENEDGE-I-757
Cause
Resolution

Prior to OpenEdge 11.7, there was no support for PASOE log file roll-over. Since version 11.7.0, this feature is described in the following Article:

Support for MSAgent log file roll-over was also implemented in OpenEdge as of version 11.7:

  • The PASOE Multi-Session Agent log (*.agent.log) can be configured to roll-over every day at midnight like the other log files.
  • This is configured in the {catalina.base}/conf/openedge.properties file by setting: agentLogFile (location, name, and roll-over)
Example:  oepas1 would be the "<ablappname>"
[AppServer.SessMgr.<ablappname>]
agentLogEntryTypes=ASPlumbing,DB.Connects
agentLogFile=${catalina.base}/logs/<ablappname>.agent.{yyyy-mm-dd}.log
  • Since OpenEdge 12.0 the new agentLogFile file format is populated by default as part of the oabl tailoring
  • Further information is provided in:<CATALINA_BASE>\conf\openedge.properties.README 

There is no rollover option for the PASOE Multi-Session Agent based on Size. An enhancement request has been submitted as an Idea on the Progress Community. To promote the Idea, click on this link: https://openedge.ideas.aha.io/ideas/OPENEDGE-I-757. Customer feedback is valuable and Idea submissions are monitored by our Product Management team. Enhancement requests are reviewed during the planning phase of each new product release and a list of the enhancements chosen for implementation can be found in the Release Notes documents that accompany each release. Once an Idea is submitted the Progress Software Community will have the opportunity to comment on and vote for the Idea. It's priority will be evaluated as customer demand weighs in through Article Feedback and through vote count in the Ideas Portal

1.  Like other PASOE oeabl web application logfiles; the multisession's log needs to roll over at the same time to not overly complicate log-file analysis in the related PASOE (Tomcat) oeabl web application environment where the logging of client request executions can span multiple log files. 

2. Before 11.7.1 it is important to note that both of the following properties are not used for PASOE, but cannot be removed for legacy reasons from the openedge.properties or the agent will not start.

  • agentLogThreshold
  • agentNumLogFiles 

From 11.7.1 onwards the two properties above were removed and do not affect agents to start. 

3.  Current PASOE logfiles can otherwise be manually rolled at any time with "tcman clean -A", where the archive (-A) is optional.
Before OpenEdge 11.7, this logfile clean feature can be used to manage all the current PASOE server instance's log files manually or through a cron job or Windows task scheduler as required.

4.  Eventually archived log files can be purged with OS utilities. For further information refer to Article:

For the MSA configuration change to be recognized in the server instance's openedge.properties file :

  • Prior to OpenEdge 11.7.2 and in version 12.0, the PASOE instance will need to be restarted
  • Since OpenEdge 11.7.2, 12.1 - the next agent logfile rollover will trigger if the dynamic property updates feature is enabled: allowRuntimeUpdates=1 
  • Only in OpenEdge 11.7.5 and 11.7.6, additional MSA Session Manager configurations are needed. For further configuration detail instructions, refer to Article:
Workaround
Notes
Keyword Phrase
Last Modified Date11/18/2024 11:30 AM

Powered by