Jargon Tunnel Broker
Debugging Guide

This document provides tips and guidelines for testing and investigating any problems with the setup or operation of the Jargon Tunnel Broker.

TESTING

To obtain the best debugging information, it is very useful to do a "clean" test with all tracing and logging options turned on.

1. Shut down all brokers and servers:

Use Jargon GUI panel to stop tunnel broker
Close Jargon GUI panel
Use Progress Explorer to stop AppServer broker(s) and the database server(s)
Disconnect localhost
Close Progress Explorer
Use Windows Explorer or DOS commands to rename all the log files listed above (if they exist), so the programs will create new empty ones when they are started again

2. Reboot

reboot Windows NT/2000/2003 (this by itself cures many problems!)

3. Start Databases and Appservers

Go into Progress Explorer (see above)
Make sure the AppServer broker(s) and the database server(s) are running, start them if not, and check their status.
If the problem seems related to the AppServer, try removing any startup parameters for database connections and test a "bare" AppServer using only programs that don't do any database access, such as the "statusas.p" test program. This may highlight a problem with the connection parameters.

4. Enable Tracing

Turn on all the trace options in the jsihttp.ini and tunnel.ini files.

5. Start Tunnel Broker

Use the Jargon GUI panel or the server script to start the Tunnel Broker. Check its status.

6. Run Tests

To see if the jsihttp.dll script is working, try running the "ConfigData" query:

To see if the jsihttp.dll script is communicating successfully with the Tunnel Broker, try running statusas.p from a web browser. Type in a URL like:

If this does not work, try using an actual numeric IP address instead of the hostname (www.abc.com)

To see if the Tunnel Broker is communicating successfully with AppServer, use the "test.bat" or "test.sh" script, which runs directly against the Tunnel Broker (does not use the web server or jsihttp script)
Test your application, using the Jargon Reader deployment engine.
After each test, if unsuccessful, check the status and log files again, including the astrace.log.

Investigation

1. Check Web Server Status

Is the web server running and accessible?
Use a web browser from a PC to view the web server home page
ex: http://www.jargonsoft.com

2. Check Script Configuration

Is the jsihttp.ini file configured correctly?
Query the script with a web browser for the configuration data. In a web browser URL location box, enter a command such as: http://www.abc.com/scripts/jsihttp.dll/ConfigData and it will echo all the configurations from the ini file that were present at startup. This will show how the settings were interpreted by the script. (Windows only)

3. Check Tunnel Broker Status

Is the Jargon Tunnel Broker running?
Use the GUI control panel on WinNT/2000 to check the tunnel broker status and the status of its agents.
To start the GUI control panel if it is not running, run the gui.bat or gui.sh script.
If it doesn't run, is java 1.2 or 1.3 loaded on server?
Can the gui startup command find java in the Unix or Windows PATH?
If not, change the gui.bat or gui.sh command to use a full pathname for the "java" startup command (using java install directory) ex: d:\java\jre130\bin\java -classpath ...
If java 1.2 or higher is not available, use the status.bat or status.sh script from the command line.

4. Check Script Log Files

If the Tunnel Broker is running and the agents are available, look at the log files for the tunnel script (jsihttp.dll) that routes incoming requests between the web server and the tunnel broker.
Use Notepad to view the log files that are specified in the jsihttp.ini configuration file.

5. Check Tunnel Broker Log Files

If no errors, check the tunnel broker log files.
Use Notepad to view tunnel\logs\tunnel.log and tunnel\logs\tunnel.err

6. Check AppServer Log Files

If no errors, check the AppServer status and log files.
if Progress Explorer is not running, start it.
If the tree on left only shows localhost with nothing under it, rightclick localhost and click "connect"
Click the + button by localhost to expand it
Click the + button by appserver to expand that node
Right-click the broker (such as "asbroker1") to view its status
See if broker and servers are available
Look at broker and server log files (latest entries)

7. Check Database Log Files

If it all looks ok, check the database status and log files, also with Progress Explorer, using similar steps.

8. Other Suggestions

Note exact content of any errors displayed on screen.
Is the Progress program getting compile errors? Try compiling in RDU.
Is the Progress program getting runtime errors? Look in the appserver "broker" and "server" logs.
Does the host program always return something to the client? It must do return something.
Are there any errors in the database (.lg) log files?
Are any database schema triggers being invoked but not found?

9. Contact Jargon Software Support

If you cannot find the problem using the above steps, email Jargon Software for support assistance.

If so, please create a ZIP file containing all the following files and send it as an email attachment:

error log and trace log(s) for the jsihttp script (see jsihttp.ini for file locations)
tunnel\logs\tunnel.log
tunnel\logs\tunnel.err
tunnel\logs\astrace.log
broker and server logs for Progress AppServer
the xml file for the client app being tested
the Progress ".p" that contains the procedure for the host task
all the related ".i" files for that ".p"

Jargon Tunnel Broker Debugging Guide