Web Home

SDK Home


Test PHP

Test ASP









Contact Us


JavaSonics ListenUp is no longer for sale.

How to Debug Applications that use ListenUp

Script Debugging

You can print extra debug information to the output of your "uploadURL" server scripts . The extra text will be echoed to the Java Console.

How To Turn On the Java Console


Internet Explorer using the Microsoft JVM: select "Java Console" from the "View" menu. If there are no "Java Console" menu items, then you must first enable it by selecting the "Internet Options" menu item from the "Tools" menu. Select the "Advanced" tab, then check the "Java console enabled" under the "VM" section. Then restart Internet Explorer.

Internet Explorer using the Sun Java Plugin: select "Sun Java Console" from the "Tools" menu. If there are no "Sun Java Console" menu items, then you must first enable it by opening the "Java Plugin" Control Panel, selecting the "Basic" tab, and checking the "Show Console" tab.

For Mozilla Firefox: install the excellent "Web Developer" plugin. Then select "Open Java Console" from the "Miscellaneous" toolbar menu.

Sun Java Plugin: If you cannot view the JavaConsole using the above techniques, you can still see it as a file. My name is "Phil" and I found the logs in the folder "C:\Documents and Settings\Phil\Application Data\Sun\Java\Deployment\log". Look for the most recent "*.trace" file.

If your computer has training wheels then you won't be able to see the "Application Data" folder. To remove the training wheels on Windows XP:

  1. Open the File Explorer.
  2. Select "Folder Options..." from the Tools menu.
  3. Select "Show Hidden Files and Folders"
  4. Click "Apply to All Folders"

Mac OS X

  1. Launch "Application/Utilities/Console". (I keep a shortcut in my Dock.)
  2. Click "Logs" icon to see list of Logs.
  3. Select "console.log" for basic output
  4. Or "~/Library/Logs" then "Java Console.log" to see ListenUp Output plus info from the JVM.

Internal Debug Messages

The ListenUp Applet can print its own debugging messages to the Java Console. These may or may not mean much to you but they might help diagnose a problem. You can control how many debug messages are printed to the Java Console by setting the "debugLevel" Applet parameter. Set it to "0" for terse, "1" for informative, and "2" for verbose output. For example, for verbose debugging output.

<param name="debugLevel" value="2">

Diagnostic Logging to the Server

You can log information to your server when a user starts the applet, starts and stops playing or recording, or has an exception. This is helpful when tracking long term performance of the Applet. You can turn on diagnostic logging by passing a "diagnosticURL" parameter. This should be the URL of a server script that can accept POSTed data and log it to a file. An example is included in the SDK at "listenup/php_test/logstatus.php".

The following variables may be sent by the applet to the server using a POST command:

POSTed variable
When Passed
This is set to the value passed in the "sessionID" Applet parameter.
This reflects the state of the Applet. Values might be "init", "start_ok", "start_failed". When an "exception" is received, the errorMsg will be set the exception message.
For example "Windows XP"
on "init" and "exception"
For example "5.1"
on "init" and "exception"
For example "Sun Microsystems Inc."
on "init" and "exception"
For example "1.4.2_03".
on "init" and "exception"
on "exception"

[Top] [Previous] [Next]

© 2001-2006 Mobileer, Inc.   This page is from the ListenUp SDK. You can download the SDK from here.