You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Using Emacs JDEE

Starting an aida server in JDEE (JDE->Debug App)

M-x customize-variable

  • jde-db-option-vm-args. Note the DEV in these - change it to PROD for a production server.
    -Xbootclasspath/p:/afs/slac/package/iona/orbacus/prod/JOB/lib/OB.jar
    -DAIDA_DATABASE_USERID=AIDADEV
    -DAIDA_NAMESERVER_IOR_FILE=/afs/slac.stanford.edu/package/aida/slaconly/NameServerDEV.ior
    -DAIDA_NAMESERVER_IOR_URL=http://www.slac.stanford.edu/grp/cd/soft/slaconly/aida/NameServerDEV.ior

Orbacus Diagnostics

Both Aida servers, and the test clients (test.java) pass on command line arguments to the ORB init. So one can use, for instance -ORBtrace_connections to diagnose Orbacus: Eg Using the Aida command line aliases to start a server, specify level 3 tracing with:

aidaproc ${AIDA_NAME_NAME} ${AIDA_NAME_DBGADDR} sys.daNameServer.NameServer -ORBtrace_connections 3

Test clients from test.java also pass on -ORB options, but any arguments are interpreted as to the test client, the following will execute tests 1 and 3, not use level 3 tracing:

aidatest daDpTestHistTest 1 -ORBtrace_connections 3

VMS Data Provider Debugging

The regular VMS debugger works fine for debugging the native code parts of an Aida server running in an interactive process (which for a production aida server is not the norm). So, start the server in a decterm, and then do the usual ctrl-y debug on it to set break points.

 

  • No labels