In their abstract for the presentation "Top 10 Causes for Java Issues in Production and What to Do When Things Go Wrong" (S314040), Cliff Click and SriSatish Ambati advertise this presentation as "an accumulated compendium of the top 10 things that can cause Java production heartburn and what to do when your Java production is on fire." This presentation is currently scheduled for 1 pm on Wednesday, September 22, in Hilton San Francisco's Continental Parlor 1/2/3. The complete abstract for this presentation is shown next.
It's Friday evening and you hear the first rumble . . . one java node has become slightly unresponsive. You lookup the process, get a thread dump, and for good measure restart it at 8 p.m. Saturday afternoon is when you realize that other nodes have caught the flu and you get the ugly call from the customer. In a matter of hours, you're on that conference bridge with support groups of different packages and Java vendors and one of your uberarchitects. Yes, production instances are up and down, and restarting like there's no tomorrow. Here's an accumulated compendium of the top 10 things that can cause Java production heartburn and what to do when your Java production is on fire. And yes, please have your tools belt on.
This presentation is currently listed as "Full," meaning that there's no more Early Seating available. However, I have noticed that some presentations move in and out of "Full" status as people adjust their schedules and figure out what they're going to attend.