Dispatch caught exception in run loop: null

Has anyone encountered the following error in their wM 7.1.2 environment?

2011-01-06 09:02:48 EST [ISS.0053.0003D] Dispatch caught exception in run loop: null

If so, what was done to resolve?

We see this every once in a while when a customer connects to a https service.

Thanks,
Mark

I am getting the same error when a partner is trying to post a https request to our server. The request is getting Denied on our HTTPS port. The port has the service name in the Allow List, the service execute ACL is also set to Anonymous. The IP access is set to Global Access.

Any help would be appreciated.

2014-12-11 13:31:37 MST [ISC.0039.0001D] POST /invoke/folderName.subFolderName.Services:invokeService
2014-12-11 13:31:37 MST [ISS.0053.0003D] Dispatch caught exception in run loop: 0
2014-12-11 13:31:38 MST [ISC.0039.0001D] POST /invoke/folderName.subFolderName.Services:invokeService
2014-12-11 13:31:38 MST [ISS.0053.0003D] Dispatch caught exception in run loop: 0
2014-12-11 13:31:41 MST [ISC.0039.0001D] GET /
2014-12-11 13:31:41 MST [ISC.0038.0002D] --> HTTP/1.0 401 [ISS.0084.9004] Access Denied

What about the Access Mode? Is it set to Allow by Default.

It is Allow by Default but I have added the service in the Allow List

Sorry Deny by Default…But service added to Allow List

Can you set to Allow by Default and do the test.

Sorry for resurrecting an old post:

We encountered this error when attempting to access an HTTPS service that had basic authentication from a .NET WCF client. WCF does not sent a User-Agent.

It seems webMethods requires a User-Agent header.

To workaround the issue, we had to add a message inspector to inject the User-Agent header

Thanks Jason for updating back this old thread and giving more life to it :smiley:

Cheers!
RMG