These won't create high memory consumption. I would suggest to generate a heap dump at the time of this situation and analyze it using MAT or any similar to identify the root cause.

what's the error ? Can you post the full error.log

Can you try to stop the acs commons bundle and retry to reveal the actual error ?

Are you on 6.3 or 6.3.2.1 ?

That doesn't help either and looks like there is something bigger to just replication. Can do the following or maybe open a support case with Adobe as this might require deeper investigation- Stop the instance- Rename the logs folder- Start the instance- Share the error, stdout.log

I wasn't expecting this one. Can you check the error.log at publish instance http://h0001995:4503​ once you do this test connection

Response: 503 ServletResolver service missing, cannot service requests\There should be a error/warn message in the error.log as well. Can you attach the same ?

Agreed but that is the consequence that the repository can't be initiated and the reasons could be many. So fresh set of logs from the start of the instance would help.- Stop the instance- Rename the logs folder- Start the  instance- Share the error, stdout.log

Not sure if you are on the latest 6.3 patch release, I just tested it on 6.3.2.1 and I see the workflow as expected.You might want to update your local machine to 6.3.2.1 to test it out

Couple of questions on what led to this occurrence :Was this instance ever working ? Did we do any updates to the platform ? OS, JDK etc. ? Do we have valid backup before this issue occurred so that we can restore to previous state ?Any network or abrupt shutdown before this issue happenned ?