tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <>
Subject Re: Permgen issue?
Date Thu, 03 Sep 2015 09:58:35 GMT
maybe try with johnzon or jackson as provider to check the behavior is the
same. Clearly johnzon doesnt keep any reference.

About your async: the task is under you control (means the container will
not kill it if it is not done) so you need to cancel it if it is running
while the app is undeployed. This is relatively unlikely in prod but in dev
it happens.

Romain Manni-Bucau
@rmannibucau <> |  Blog
<> | Github <> |
LinkedIn <> | Tomitriber

2015-09-03 11:49 GMT+02:00 tonywestonuk <>:

> Ok.... I think I have a couple of places where this memory could be
> leaking.
> When I remove the async, this no longer appears in the heap dump.   I dont
> have a @PreDestroy, but I wouldn't know what to put in that method anyhow.
> All I want is for my async method to run outside the main HTTPRequest
> thread
> so it doesn't slow up the response, and once that method is done (it only
> takes a second or so to run), then that is the end of that!...  There is no
> cancelling anything....   Or is there something I do have to do to destroy
> the background thread that processes these async methods?
> Anyhow,  as I say, this is only one of my permgen issues.  After removing
> the async method, the application still didn't GC on redeploy.   I tracked
> this down to using JAXRS.  I made a very simple webapp that simply returns
> a
> java object serialised as JSON, in a get request.  This GC's ok on
> redeploy.
> However, if I add the configuration according to adam-bien,
> This stops it hot deploying, it appears that the JSONProvider doesn't GC,
> and this retains a reference to the JAXB class that is serialised to
> JSON......
> --
> View this message in context:
> Sent from the TomEE Users mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message