Question

7
Replies
808
Views
SaadullahK Member since 2014 5 posts
Virtusa
Posted: 1 year ago
Last activity: 4 months 1 week ago

Tomcat server hangs after asynchronous processing starts

This is for a fresh installation of Pega 8.2.2

During deployment of the WAR file on Tomcat, (on server startup), I see the following log message and the Tomcat server gets stuck at this point:

2019-07-11 02:16:51,101 [groundProcessing]:14] [ STANDARD] [ ] [ ] (.DataFlowDiagnosticsFileLogger) INFO - {"type":".ProcessingThreadLifecycleMessage","senderNodeId":"e1ace989de0e382529169b7cd9308ff7","timestamp":1562825810673,"runId":"pyBatchIndexClassesProcessor","threadName":"DataFlow-Service-PickingupRun-pyBatchIndexClassesProcessor:36, Access group: [PRPC:AsyncProcessor]","event":"PICKED_UP_PARTITIONS","partitions":["11","7","1","10"]}
2019-07-11 02:16:51,109 [groundProcessing]:14] [ STANDARD] [ ] [ ] (.DataFlowDiagnosticsFileLogger) INFO - {"type":".RunStatusTransitionMessage","senderNodeId":"e1ace989de0e382529169b7cd9308ff7","timestamp":1562825810628,"runId":"pyBatchIndexClassesProcessor","previousStatus":"RESUMING","newStatus":"IN_PROGRESS","originator":"MultiplePartitionExecution","reason":"Run is in progress"}
2019-07-11 02:16:51,121 [groundProcessing]:14] [ STANDARD] [ ] [ ] (.DataFlowDiagnosticsFileLogger) INFO - {"type":".ProcessingThreadLifecycleMessage","senderNodeId":"e1ace989de0e382529169b7cd9308ff7","timestamp":1562825810750,"runId":"pyBatchIndexClassesProcessor","threadName":"DataFlow-Service-PickingupRun-pyBatchIndexClassesProcessor:35, Access group: [PRPC:AsyncProcessor]","event":"PICKED_UP_PARTITIONS","partitions":["19","9","12","3"]}

Even after 24 hours, there is no progress from this point and the application is also unaccessible.

***Edited by Moderator: Lochan to update platform capability tags***

System Administration Low-Code App Development Installation and Deployment
Share this page LinkedIn