Just to clarify this should be reproducable with any Java Debug tool (IntelliJ, Eclipse, etc) The slow down increases with the scope of the current Frame. If you have a simple scope of say 5 basic objects then things are slow but liveable. If you have a large scope of say 22 objects several of which are collections of a hundred or so objects then it takes literally an hour to step over one line of code.
So last night I cracked out my W R Stephens books and plowed through a few man pages, RFC's and other specs and do agree that Java is probably doing something that it shouldn't. However I'm a bit surprised that such a change occured in 2.6.15 when every kernel from 2.2 on that I've tested *doesn't* have this issue. I don't believe in changing an app to work round another apps issues so definitely agree that the JDK needs to get looked at. However if I put on my risk aversion corporate hat I'd be surprised that such a change occured this late in a kernel release. "sudo sysctl -w net.ipv4.tcp_abc=0" does seem to help with 2.6.15 but it still doesn't feel as fast as 2.6.14 or previous kernels. I'm not 100% sure that this is the only issue but I will post it as a workaround for now. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
