I have this architecture whereby I have two machines a1 and a2. They are currently clustered but without broker configured. I have discovered the following.
- if process is triggered from a2 and finished at a2, the process is completed successfully.
- if process is triggered from a2 and finished at a1, the process is completed but at later stage, the process will timeout.
I have tried to use pub.prt.admin:changeProcessStatus and uses pub.remote:invoke but still the process is being timeout. Anyone can suggest a way to bypass the use of broker?