http://bassistance.de/2010/02/10/java-tricks-find-out-who-invoked-you/ Jörn Zaefferer on Bass, Geeks and Rock'n'Roll Tue, 31 Jan 2012 11:18:41 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://bassistance.de/2010/02/10/java-tricks-find-out-who-invoked-you/comment-page-1/#comment-182625 Jörn Fri, 12 Feb 2010 23:10:46 +0000 http://bassistance.de/?p=613#comment-182625 Thanks for the info Mike. So the behaviour is at least consistent on Sun JVMs? Thats usually good enough, at least for the stuff I'm working on. Thanks for the info Mike. So the behaviour is at least consistent on Sun JVMs? Thats usually good enough, at least for the stuff I’m working on.

]]> http://bassistance.de/2010/02/10/java-tricks-find-out-who-invoked-you/comment-page-1/#comment-182617 Mike Fri, 12 Feb 2010 20:25:20 +0000 http://bassistance.de/?p=613#comment-182617 Be warned that the result of getStackTrace() is not specified and behaves differently on other JVMs, e.g. sometimes the invoker is at index[2] and sometimes at index[1]. Also, from my findings the performance impact is severe, esp. in logging. You should therefore always use s.th. like log.isDebugEnabled() around such calls. Be warned that the result of getStackTrace() is not specified and behaves differently on other JVMs, e.g. sometimes the invoker is at index[2] and sometimes at index[1]. Also, from my findings the performance impact is severe, esp. in logging. You should therefore always use s.th. like log.isDebugEnabled() around such calls.

]]>