Trigger Resource Monitor invoked “wm.prt.admin:monitorPRTDB”. Status of resource is “not available”.
Any ideas?
This is a standard Process Engine behaviour. When the Process Engine database looks to be unavailable, triggers for process models go into the suspended state and the IS starts running the monitorPRTDB service, resuming the triggers when this indicates the Process Engine database (i.e. Process RunTime database) is available. It’s a standard feature of triggers - have a look in the Pub Sub Guide, or in the JMS Client Developer’s Guide for ‘resource monitor’ for more info.
The message you see is, I think, the output from the monitorPRTDB service indicating that the database was identified as still not available.
Regards,
Rob D.