I am presenting at JavaOne again this year, My session is TS-1669 entitled " Unhappily ever after: support, maintenance and troubleshooting of Java applications in production environments "
It covers more topics than the one I did in 2004. It also seems to have been marked as more interesting by Sun. Last time I remember having about 300 people in the room. This time, the earmarked room is for 700 people.
Andrew is confused why his ‘drab’ article on speeding up JBoss is much more popular than his repost of a deep voodoo article asking other people to implement someting that he finds interesting. I wonder!
I have linked to the speeding up article when I saw it, because it was something useful either immediately or later if I do have strange slow-downs/memory issues to troubleshoot. It (as I mentioned originally) was also useful beyond JBoss and I knew that because I had to explain the same issues to the customers using Weblogic.
Ever tried running multiple Tomcat on the same machine and have that fail because of the port conflict. And not because of the HTTP listen port conflict - because you did know about that one and changed it. But, rather, because of the other ports that are open out of the box as well that even Tomcat’s documentation does not mention.
So, turns out that Tomcat 5, has 3 ports open and what interesting ports they are:
Recently, I had been contacted by one of the Chainsaw’s developers - Scott Deboy (no blog yet). He asked if I had any feedback on the tool’s new iteration as it would seem to be a good match to my interests and blog’s goal.
I had looked at the Chainsaw a while ago, but it was not quite up to scratch then. Looking at it again, the tool feels much better and if you have to look at the log files, I strongly recommend to check it out (and/or Splunk).
What is a server access log and how much information can one actually extract from it? If you don’t know, read this good introductory article on the subject.
And if you find the article interesting, look for other logs your server/application produces. The easiest way to find out what log files you have is to run ProcessExplorer on Windows or lsof on *nix and see what .log files the program is keeping open and where.