Don't ever try to do anything sneaky when you're programming. It will always bite you in the ass. If you still want to be sneaky, read the documentation.
Last week, we had a problem with one of our processes hanging and burning 100% CPU. The first time it happened we chalked it up to mysteries of the universe and restarted the process (a time-honored startup tradition), but the second time, I actually got off my ass and investigated.
Through the miracle of
jstack, I could look at the stack trace of a currently running Java process. This is what I found:Read full article from Java subList Gotcha
No comments:
Post a Comment