Hi all,
Just upgraded to 7.1.1 and eventhough WF_QUEUE_DEPTH_DURATION_WARNING is set to 7500, admin errors keep coming.
The message is below and it says 0 ms. So, I do not think that is a problem.
OK: Monitor[jobq#Normal] has taken 0 ms to process an item.
What should I do to avoid these admin errors? Any help would be appreciated.
Hi Azam,
Thanks for your reply. The variables you mentioned are not defined on the Custom tab. I'm going to add them and observe the results. Is there any other attribute for queue depth or any document which explains all useable attributes?
Hello Emre,
You may check below document for all other variables
IGL Online Help > Administration > Viewing and Managing Admin Errors > Workflow System Status
- Customize Thresholds for System Status Indicators
Couldn't get rid of below admin error.
Error ID: 192769
Description: Queue Depth
Type: System Status Event
Created On: 4/19/19 10:31 AM
Details
OK: Monitor[alertq#Normal] has taken 0 ms to process an item.
Hello Emre,
By default, Root Logger's log level is configured to INFO. The message you're seeing is an INFO level. If you're using WildFly with RSA Supplied database, you may change log level through the UI.
Navigate to UI > Admin > Settings > Logs > click Settings then set Root Logger's Level from INFO to WARN. Or you may click Advanced, choose Group: com.aveksa, Category: com.aveksa.server.workflow.statistics.QueueDepthProcessor then click Add, set log level to WARN so it would only log WARN and above(ERROR, FATAL etc) for QueueDepthProcessor related messages.
However please note that the above settings will be reset to default if RSA IGL service is restarted as it's based from Apache Log4j configuration file /home/oracle/wildfly/standalone/configuration/aveksa-log4j.properties
If you're using WildFly with Customer's Supplied database, you may modify above file so QueueDepthProcessor will only log WARN and above messages and restart RSA IGL service.
Example:
log4j.logger.com.aveksa.server.workflow.statistics.QueueDepthProcessor=WARN
Hi Azam,
Thanks for your replies but modifying aveksa-log4j-properties didn't work too
Have you restarted aveksa service? Could you share your aveksa-log4j-properties and the latest aveksaServer.log
Sure, server was restarted.
04/28/2019 20:04:01.599 INFO (Exec Task Consumer#0 - Sequence) [com.aveksa.server.xfw.TaskExecutor] Setting thread Thread[Exec Task Consumer#0 - Sequence,5,Execution Task] on 1798370859 method=Execute
04/28/2019 20:05:46.847 INFO (NotificationConsumer:SystemStatus) [com.aveksa.server.workflow.notification.NotificationEngine] Starting method=run subTask=Processing Event NotificationEvent[WorkflowEvent[id = 1594263 creationDate = Sun Apr 28 20:05:46 EET 2019 eventState = New eventType = SystemStatusIndicatorChangedEvent] notificationObjectId = 98 notificationObjectType = SystemStatus]
04/28/2019 20:05:46.856 INFO (NotificationConsumer:AdminException) [com.aveksa.server.workflow.notification.NotificationEngine] Starting method=run subTask=Processing Event NotificationEvent[WorkflowEvent[id = 1594264 creationDate = Sun Apr 28 20:05:46 EET 2019 eventState = New eventType = NewAdminExceptionEvent] notificationObjectId = 196121 notificationObjectType = AdminException]
04/28/2019 20:05:46.860 INFO (NotificationConsumer:SystemStatus) [com.aveksa.server.workflow.notification.NotificationEngine] Starting method=run subTask=Processing Event NotificationEvent[WorkflowEvent[id = 1594265 creationDate = Sun Apr 28 20:05:46 EET 2019 eventState = New eventType = SystemStatusIndicatorChangedEvent] notificationObjectId = 97 notificationObjectType = SystemStatus]
04/28/2019 20:05:46.896 INFO (NotificationConsumer:SystemStatus) [com.aveksa.server.workflow.notification.NotificationEngine] Starting method=run subTask=Processing Event NotificationEvent[WorkflowEvent[id = 1594267 creationDate = Sun Apr 28 20:05:46 EET 2019 eventState = New eventType = SystemStatusIndicatorChangedEvent] notificationObjectId = 99 notificationObjectType = SystemStatus]
04/28/2019 20:05:46.913 INFO (NotificationConsumer:AdminException) [com.aveksa.server.workflow.notification.NotificationEngine] Starting method=run subTask=Processing Event NotificationEvent[WorkflowEvent[id = 1594266 creationDate = Sun Apr 28 20:05:46 EET 2019 eventState = New eventType = NewAdminExceptionEvent] notificationObjectId = 196122 notificationObjectType = AdminException]
04/28/2019 20:05:46.924 INFO (NotificationConsumer:AdminException) [com.aveksa.server.workflow.notification.NotificationEngine] Starting method=run subTask=Processing Event NotificationEvent[WorkflowEvent[id = 1594269 creationDate = Sun Apr 28 20:05:46 EET 2019 eventState = New eventType = NewAdminNotificationEvent] notificationObjectId = 196121 notificationObjectType = AdminException]
04/28/2019 20:05:46.934 INFO (NotificationConsumer:AdminException) [com.aveksa.server.workflow.notification.NotificationEngine] Starting method=run subTask=Processing Event NotificationEvent[WorkflowEvent[id = 1594268 creationDate = Sun Apr 28 20:05:46 EET 2019 eventState = New eventType = NewAdminExceptionEvent] notificationObjectId = 196123 notificationObjectType = AdminException]
04/28/2019 20:05:47.136 INFO (NotificationConsumer:AdminException) [com.aveksa.server.workflow.notification.NotificationEngine] Starting method=run subTask=Processing Event NotificationEvent[WorkflowEvent[id = 1594270 creationDate = Sun Apr 28 20:05:46 EET 2019 eventState = New eventType = NewAdminNotificationEvent] notificationObjectId = 196122 notificationObjectType = AdminException]
04/28/2019 20:05:47.145 INFO (NotificationConsumer:AdminException) [com.aveksa.server.workflow.notification.NotificationEngine] Starting method=run subTask=Processing Event NotificationEvent[WorkflowEvent[id = 1594271 creationDate = Sun Apr 28 20:05:47 EET 2019 eventState = New eventType = NewAdminNotificationEvent] notificationObjectId = 196123 notificationObjectType = AdminException]
04/28/2019 20:05:56.867 INFO (Exec Task Consumer#0 - Sequence) [com.aveksa.server.xfw.EntitlementDataTaskSequencer] Completed DataRelationshipProcessing for source [ENT_COL_WINDOWSLOCAL_SUPERONLINE]
04/28/2019 20:05:56.867 INFO (Exec Task Consumer#0 - Sequence) [com.aveksa.server.xfw.TaskExecutor] UNSetting thread on 1798370859 method=Execute
04/28/2019 20:05:56.872 INFO (Exec Context Runner#1086368 EntitlementLoad) [com.aveksa.server.xfw.ExecutionRequest] Notify execution request for ExecutionContext[ID=1086512 Type=ChangeVerification Status=New NumTasks=1 tasks=ExecutionTask[TaskID=1244493 RunID=1086512 Source=76 Type=ChangeVerification Status=New]]
04/28/2019 20:05:56.874 INFO (Thread-208 (ActiveMQ-client-global-threads-579409477)) [com.aveksa.server.xfw.ExecutionServiceProvider] Notified execution request for ExecutionContext[ID=1086512 Type=ChangeVerification Status=New NumTasks=1 tasks=ExecutionTask[TaskID=1244493 RunID=1086512 Source=76 Type=ChangeVerification Status=New]]
04/28/2019 20:05:56.876 INFO (Exec Context Runner#1086368 EntitlementLoad) [com.aveksa.server.xfw.ExecutionRequest] Notify execution request for ExecutionContext[ID=1086513 Type=BusinessDescriptionCalculation Status=New NumTasks=1 tasks=ExecutionTask[TaskID=1244494 RunID=1086513 Source=76 Type=BusinessDescriptionCalculation Status=New]]
04/28/2019 20:05:56.878 INFO (Thread-207 (ActiveMQ-client-global-threads-579409477)) [com.aveksa.server.xfw.ExecutionServiceProvider] Notified execution request for ExecutionContext[ID=1086513 Type=BusinessDescriptionCalculation Status=New NumTasks=1 tasks=ExecutionTask[TaskID=1244494 RunID=1086513 Source=76 Type=BusinessDescriptionCalculation Status=New]]
04/28/2019 20:05:57.004 INFO (Exec Context Runner#1086368 EntitlementLoad) [com.aveksa.server.core.DBEventUtilities] Published 0 DB events for run 1086368
04/28/2019 20:05:57.006 INFO (Exec Context Runner#1086368 EntitlementLoad) [com.aveksa.server.xfw.ExecutionContext] Successful method=Execute 1086368, EntitlementLoad
04/28/2019 20:05:57.013 INFO (Exec Task Consumer#0 - Sequence) [com.aveksa.server.xfw.TaskExecutor] Setting thread Thread[Exec Task Consumer#0 - Sequence,5,Execution Task] on 1921200993 method=Execute
04/28/2019 20:05:57.141 INFO (Exec Task Consumer#0 - Sequence) [com.aveksa.server.xfw.TaskExecutor] UNSetting thread on 1921200993 method=Execute
04/28/2019 20:05:57.142 INFO (Exec Task Consumer#0 - Sequence) [com.aveksa.server.xfw.TaskExecutor] Setting thread Thread[Exec Task Consumer#0 - Sequence,5,Execution Task] on 106422972 method=Execute
04/28/2019 20:06:18.511 INFO (Exec Task Consumer#0 - Sequence) [com.aveksa.server.xfw.TaskExecutor] UNSetting thread on 106422972 method=Execute
Hi Emre,
Those are INFO level messages. If you want them to stop logging, change log4j.logger.com.aveksa category to WARN so it logs only WARN or above messages.
e.g.:
log4j.logger.com.aveksa=WARN
Hi Azam,
INFO level logging is not a problem but admin errors are. Eventhough info level is set to warn and aveksaServer.log file doesn't include info logs, admin errors didn't stop. Is there any other suggestion to stop them?
Could you click Table Options on UI - Admin Errors - Summary tab, then select Details then click Ok then share the screenshot.
You shouldn't see 'OK: Monitor[jobq#Normal] has taken 0 ms to process an item.' in Details column if you have changed log4j.logger.com.aveksa level to WARN.
Hi Emre,
You shouldn't see 'OK: Monitor[jobq#Normal] has taken 0 ms to process an item.' in Details column if you have changed log4j.logger.com.aveksa level to WARN. Not sure why it's still appearing in Admin Errors.
Please raise RSA Customer Support ticket so we could investigate this further.
Regards,
Azam
Hello Emre.
The value of error(WF_QUEUE_DEPTH_DURATION_ERROR) must be equal or greater than the value of warning. Similarly, the critical(WF_QUEUE_DEPTH_DURATION_CRITICAL) must be equal or greater than the value of error.
Please note the variables are custom variables and are prefixed with 'custom.' although you don't have to add 'custom.' explicitly.
What are configured for error and critical? Could you share the screenshot capture of UI > Admin > Systems > Custom ?