permgen issue with tracing

[dajac]

Hello Zach,

We noticed a memory leak of the permgem space when using aleph's http client. After a while, we found that lamina.trace/canonical-probe keywordize all strings and http client use (str "http-connection:" (:server-name options)) as a part of the generated canonical-probe. So using the http client with a lot of different hosts causes a lot of different keywords to be stored into the pergem and finally causes an "java.lang.OutOfMemoryError: PermGen space".

So can we juste disable the keywordization there? What do you think?

As you know, we rely on lamina/aleph on production and would appreciate your help.

Regards,
David

[ztellman]

Specify a :name in the request, and it won't generate a new probe name each time. This should be prominently documented, and probably default to not being traced in the case of standalone http-requests. Leaving this open until we default to saner behavior.

[dajac]

Thank you! I really appreciate your help.

Le 1 févr. 2012 à 22:50, Zach Tellmanreply@reply.github.com a écrit :

Specify a :name in the request, and it won't generate a new probe name each time. This should be prominently documented, and probably default to not being traced in the case of standalone http-requests. Leaving this open until this defaults to saner behavior.

---

Reply to this email directly or view it on GitHub:
#26 (comment)

[ztellman]

This is not a problem in 0.5.0