{"id":354,"date":"2013-11-29T00:43:58","date_gmt":"2013-11-28T16:43:58","guid":{"rendered":"https:\/\/www.techcoil.com\/blog\/?p=354"},"modified":"2018-09-04T13:16:07","modified_gmt":"2018-09-04T05:16:07","slug":"configurations-that-i-set-in-my-java-control-panel-to-get-my-java-plug-in-to-tell-me-more-about-the-java-applets-and-binaries-that-it-is-running","status":"publish","type":"post","link":"https:\/\/www.techcoil.com\/blog\/configurations-that-i-set-in-my-java-control-panel-to-get-my-java-plug-in-to-tell-me-more-about-the-java-applets-and-binaries-that-it-is-running\/","title":{"rendered":"Configurations that I set in my Java Control Panel to get my Java Plug-in to tell me more about the Java applets and binaries that it is running"},"content":{"rendered":"

Right after I took over the maintenance work for Java applets that are a decade old, I did an important tweak to my Java Runtime Environment: I applied some configurations for the Java Plug-in on my computer to be as verbose as possible when it had to run my Java applets. <\/p>\n

This post shows how I had configured in my Java Control Panel in my windows machine for the sake of performing diagnostic tasks when trouble brews.<\/p>\n

Accessing the Java Control Panel<\/h2>\n

I found my Java Control Panel in the windows control panel. <\/p>\n

\"Java<\/p>\n

Clicking on the icon in the blue box, the Java Control Panel appeared to do my bidding.<\/p>\n

Five things that I had configured in my Java Control Panel to aid me in diagnosing Java applet issues<\/h2>\n

When my Java Control Panel appeared, I clicked on the Advanced<\/strong> tab. I then applied the following settings via the Advanced<\/strong> tab:<\/p>\n

    \n
  1. Under the Debugging<\/strong> section, I checked the Enable tracing<\/strong> option. This enable log messages from the Java Plug-in to appear in a file in the Java deployment log folder.<\/li>\n
  2. Under the Debugging<\/strong> section, I checked the Enable logging<\/strong> option. This allows me to look at console outputs from writes to System.out<\/code> and System.err<\/code> in my Java applets.<\/li>\n
  3. Under the Debugging<\/strong> section, I checked the Show applet lifecycle exceptions<\/strong> option. This option allows me to peep into what the Java Plug-in is doing to bring up my Java applets.<\/li>\n
  4. Under the Java Console<\/strong> section, I switched to the Show console<\/strong> option. With this option in place, a Java console will appear whenever my Java applet runs.<\/li>\n
  5. Under the Miscellaneous<\/strong> section, I checked the Place Java icon in system tray<\/strong> option. This option allows me to reopen my Java console window in the event that I accidentally closed it.<\/li>\n<\/ol>\n

    The following are two screenshots after I had applied the above mentioned configuration settings at my Java Control Panel. <\/p>\n

    These configuration settings are highlighted by boxes with blue borders. <\/p>\n

    <\/p>\n

    Configuration settings above the fold. <\/p>\n

    <\/p>\n

    Configuration settings below the fold.<\/p>\n\n