Due to a exe4j/com4j bug the normal launcher we use leaks memory and cannot be
used. The current launcher was built with launch4j but lacks the ability to
log sysout and syserr to files, which makes debugging the tracking server
extremely hard.
Possible solutions:
1) Either logging has to be built directly in the tracking server.
2) Launch4j has to configured to use logging (is that possible?)
3) The exe4j launcher has to stop leaking (I already spent 3-4 days on that and
didn't succeed)
I guess that 1) will be the most efficient solution.
Original issue reported on code.google.com by r.biedert on 8 Jul 2010 at 8:33
Original issue reported on code.google.com by
r.biedert
on 8 Jul 2010 at 8:33