Did anyone come across, the state of schedulers going to hanging during their second run after performing any migration activities like hardware/version ?
I mean to say that after hardware upgrade, we move all schedulers to new hardware, when schedulers kick-off during their run, all got hanged.
Kindly share your experiences to solve this problem.
What is your webMethods version now? From which version did you migrate.
What do you mean by hardware upgrade? After the scheduler kick-off did you check the server log, do you find some useful information to investigate?
YES please check the error/server logs for more information and also try to tune or increase the IS Settings–>Resources for server thread pool and also the JDBC pool for max connections.