This is somewhat preliminary but I got to this point: [1] (`always use
BouncyCastle in KeyGenUtils`)
Found some (old) posts about memory leaks with dynamic
providers[2][3][4]. In [2] it's mentioned a statical method to install
providers.
I'm still running test against those commits [1] and the pr
On 2018-10-08 18:00, Arne Babenhauserheide wrote:
> DC* writes:
>
> Do you have experience with profiling Java for memory leaks?
>
No, I have no experience but I'm trying to triangle the issues commit by
commit to see where the issue was introduced and reduce the scope.
> The only lead I have r
DC* writes:
> Here are my logs (log.level DEBUG). My node restarted several times at
> 15m, 20m, 30m. The log named `check-alive.log` is the output from the
> gist (it's cut off ubut shows enough information).
Thank you! Yours is the first reproduction outside my own machines. I
was short of con
DC* writes:
> Are there any debug/logging/stack trace setting we could enable to see where
> it died?
You can set logging in wrapper.conf, see the wrapper.logfile.loglevel
and wrapper.console.loglevel lines.
> I'm gonna setup an container to try this out.
Thank you!
Best wishes,
Arne
--
Unp
