WARNING is no good reason for stopping a flow, but it's a heads up if any other issue happens later.
CRITICAL should be the most alarming log you're ever going to receive, it should be a good excuse to wake you up at 3 am to resolve.
To debug lock timeout errors, set derby.locks.monitor=true and derby.locks.deadlockTrace=true in derby.properties. This will print the lock table information to the derby.log when the timeout happens. If you also set derby.language.logStatementText=true, then all the statements executed on the system will be written out to the derby.log
The log file containing the information referenced will usually be the one named with the hostname on which Tomcat is running. On a simple server (e.g. development environment) this is localhost.<datestamp>.log
With Subversion 1.5 or later the merge is recorded on your local working copy in the svn:mergeinfo property. So this information is not lost.
You can see the merged revisions if you use svn log -g
Award-winning data science platform for open technologies: Pig, Python, MongoDB and more. Easily run a custom recommender system, analyze logs, or do NLP.
Learn the response to the thirteenth question in SearchSAP.com's exclusive security quiz. Read the answer and more detailed information on user history.
R. White, and J. Huang. Proceedings of the 33rd International ACM SIGIR Conference on Research and Development in Information Retrieval, page 587--594. New York, NY, USA, ACM, (2010)
A. Paranjape, R. West, L. Zia, and J. Leskovec. Proceedings of the Ninth ACM International Conference on Web Search and Data Mining, page 615--624. ACM, (2016)
M. Atzmueller, and B. Kloepper. Proc. International Conference on Intelligent Data Engineering and Automated Learning, Workshop on Methods for Interpretation of Industrial Event Logs, Heidelberg, Germany, Springer Verlag, ((accepted) 2018)