Classloading instigates OutOfMemoryError
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gearman Java |
New
|
Undecided
|
Unassigned |
Bug Description
Not sure if this project is being maintained, but thought I'd try in any case.
There appears to be a bug with the worker not releasing objects defined in GearmanWorkerIm
226 if (!functionList.
227 GearmanFunction fun = functionList.
228 submitFunction(
229 }
What ends up happening is new classes are constantly being instantiated but not being released, and thus the GC isn't cleaning them up. If a MaxMetaspaceSize is set, it'll instigate a OOM exception. If on the other hand, no MaxMetaspaceSize is set, it will deplete all the ram given enough time.
I suspect (yet to try) that setting "fun = null;" after submitFunction() will mark it for GC.
I am using JDK 10, and version 0.6 of the client.
Please advise.
description: | updated |
description: | updated |
description: | updated |
> Not sure if this project is being maintained
It doesn't look so.
Last release: /code.launchpad .net/~gearman- developers/ gearman- java/trunk
97. By Eric Lambert <email address hidden> on 2014-09-09
https:/