What steps will reproduce the problem?
1. View $CORUS_HOME/deployment/*/*/*/processes/*/stderr.out
2. No timestamps :)
Ideally like we do with stdout.txt - we would have timestamps. Currently when
investigating potential problems you can't tell what errors in stderr.txt are
current, old, or whenever :)
Problem exists in versions up to 4.1.3
Original issue reported on code.google.com by c...@maxnet.eu.org on 15 May 2014 at 2:39
Original issue reported on code.google.com by
c...@maxnet.eu.org
on 15 May 2014 at 2:39