We are having a scenario where there are two IS’s in organization (say IS1 and IS2). Both are clustered. Consider a scenario where there are two systems S1 as the source system and S2 as the destination system.
In a normal scenario messages sent from S1 reach S2 (lets say the key is workorder numbers) which are visible as a part of the contexid. (the package we are talking about, let it be called as P1. P1 is deployed on IS1 and IS2)
Everytime a message is sent from S1 to ESB (publish) or from ESB to S2(subscribe), it gets logged.
Whenever a message gets sent from S1 to ESB, an status acknowledgement is sent from ESB to S1.
For some reason, IS1 was not working properly and the P1 was not enabled/not loaded on that IS1.
When I tried enabling/loading the package, it gave an error of being locked. Finally I just had to restart IS1, when the acknowledgements started coming from ESB to S1.
Can anyone explain why this happened? I have checked the logs to see something unusual but couldn’t find anything.
On the previous day I performed a deployment, where another set of packages were deployed. This too took lot of time and I had to rollback and redeploy.