Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Completed
-
3.8.3 (EE Only)
-
S3
-
Production Defect
-
0
-
Mule Tipas 4 08/17
Description
The problem might be caused by a combination of load and theads shortage, which might be causing processes to run on grizzly's timeout thread.
The leak itself, as seen from the reports, is the theadlocal of the timeout thread keeping a reference to a MuleEvent.