addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-crosscrosseditemptyheartfacebookfolderfullheartglobegmailgoogleimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartrashtriangle-downtriangle-uptwitteruseryahoo

Lab: Java Production Debugging 101, Tomer Gabel

If you're register to Day 2 you may also register to this lab. If you're not registered to Day 2, then we're sorry...

Space is limited to 50.



One of the unfortunate truths of software development is that, sooner or later, shit hits the fan and something breaks on production. The Java platform (and the JDK specifically) has a whole set of debugging and analysis tools that can be used to diagnose a large variety of production issues with no prior setup and nothing but SSH access to the server and a bit of common sense.

This lab will focus on common Java server production issues (including deadlocks, memory leaks and thread starvation), and introduce some of these tools by demonstrating how they can be used to analyze and resolve each scenario.

Duration: 1:50


Join or login to comment.

  • A former member
    A former member

    Very well-prepared and invested lab. Thanks, Tomer!

    February 21, 2013

    • DD


      February 21, 2013

  • Nati C.

    Great talk and hands-on exercises.
    Too bad we started late (due to important pizza issues)

    1 · February 19, 2013

    • Dan

      Pizza rules!

      1 · February 19, 2013

  • Tomer G.

    To everyone attending the Java production debugging lab: we're going to either pair or group up, so as long as most of you show up with laptops we'll be good to go. Although obvious, please make sure you have the following set up on your machine:

    * Install a recent JDK (6 or 7, doesn't matter);
    * Place the <JAVA_HOME>/bin directory in the path.

    That's pretty much it. The sample codebase is only a few megabytes, so we'll distribute it just prior to starting the lab via wireless network or USB drives. The example code will include startup scripts for both Windows and UNIX (Linux/Mac) so hopefully we won't waste any time on trivialities.

    Thanks for attending and see you on Tuesday!

    1 · February 16, 2013

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy