When the problem occurs, can you check to see the number of sessions you have that are connected. Go to the BrokerAdmin page and drill down to the clients on the broker. Find the trigger that isn’t working and check the number of sessions. You can click on sessions and check to see if you have more than 1. We had this problem and webMethods TS got us to install BrokerCoreFix-1. Prior to install the fix, we would get rid of the “old” session and this would then allow the triggers to continue processing. webMethods TS explained that our triggers were setup to process sequentially and the first session was in a “hung” or “disconnected” state. By deleting that session, it allowed the next one to pick up the document and process it.
Please note that we did install BrokerCoreFix-1 and the fix corrected the problem of multiple sessions, however, we now have a different flavor of the problem. My triggers go to a disconnected state. I’m currently working with webMethods TS to resolve this issue.
We had the error that you had and that was thrown by the WmLogUtil package. WebMethods TS believes there was a fix for this in 6.0.1 but not in 6.1. The messages are just that… messages. In our case everything was up and working. (I published documents and the broker was receiving them.) TS had us stop the log util process by going to the Package Mgmt screen and going to the WmLogUtil home. From there we clicked on the “stop” link and this eliminated the messages. We are still investigating with webMethods TS why this starting happening …