DMLProc during rollback trying to communicate with DISABLE PM MODULE

When doing failover testing where PM2 instance is stopped. When DMLProc went into Rollback state, it tried to communicate with the WES on PM2 that was OFFLINE.

Should have code check for status on pm's and not try to communicate for PMs or WES that is offline.

Logs from um1

Nov 28 16:31:36 ip-172-31-35-86 DMLProc[29576]: 36.789937 |0|0|0| I 20 CAL0002: DMLProc starts rollbackAll.
Nov 28 16:32:43 ip-172-31-35-86 joblist[29576]: 43.939027 |0|0|0| E 05 CAL0000: /data/buildbot/bb-worker/centos7/mariadb-columnstore-engine/writeengine/client/we_clients.cpp @ 307 Could not connect to pm2_WriteEngineServer: InetStreamSocket::connect: connect() error: No route to host to: InetStreamSocket: sd: 12 inet: 172.31.44.128 port: 8630
Nov 28 16:32:43 ip-172-31-35-86 joblist[29576]: 43.939360 |0|0|0| E 05 CAL0000: /data/buildbot/bb-worker/centos7/mariadb-columnstore-engine/writeengine/client/we_clients.cpp @ 307 Could not connect to pm2_WriteEngineServer: InetStreamSocket::connect: connect() error: No route to host to: InetStreamSocket: sd: 13 inet: 172.31.44.128 port: 8630
Nov 28 16:32:44 ip-172-31-35-86 oamcpp[29576]: 44.963434 |0|0|0| E 08 CAL0000: OamCache::checkReload shows state for pm2 as AUTO_DISABLED
Nov 28 16:32:45 ip-172-31-35-86 messagequeue[29576]: 45.018124 |0|0|0| E 31 CAL0000: MessageQueueClient::setup(): Name or service not known
Nov 28 16:32:45 ip-172-31-35-86 DMLProc[29576]: 45.018646 |0|0|0| I 20 CAL0002: DMLProc will rollback 0 tables.
Nov 28 16:32:45 ip-172-31-35-86 DMLProc[29576]: 45.037501 |0|0|0| I 20 CAL0002: DMLProc finished rollbackAll.