Kbase P117934: How to debug SonicMQ adapter startup problems?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/08/2006 |
|
Status: Unverified
GOAL:
How to debug SonicMQ adapter startup problems?
GOAL:
How to trace which Java classes are loaded by the SonicMQ adapter?
FACT(s) (Environment):
Linux Intel
OpenEdge 10.1A
FIX:
1. The SonicMQ adapter needs to be started in verbose mode from the command line.
2. Before being able to run the SonicMQ adapter from the command line as Java process
you need to get the command line from the output file when starting the AdminServer with the jvmstart.debug=1
option.
3. The produced jvmStart.log file will will contain the command line to use for starting the adapter as Java process.
4. On Unix you will also have to set the LD_LIBRARY_PATH environment variable as to see within jvmStart.log
because native libraries are needed as well.
5. To get a list of all classes loaded by the SonicMQ adapter you need to start the Java process in verbose mode.
You need then add as Java argument -verbose:
Example for Unix:
/usr1/java/j2sdk1.4.2_11/jre/bin/java -classpath /usr1/v101A/dlc/sonic/MQ6.1/lib/sonic_Client.jar:/usr1/v101A/dlc/java/progress.jar -verbose -DInstall.Dir=/usr1/v101A/dlc -Djava.security.policy=/usr1/v101A/dlc/java/java.policy -DCanonicalName="local.localhost:ID=SonicMQ Adapter" com.progress.ubroker.broker.ubroker -t AD -i sonicMQ1 -r rmi://soave:20931/sonicMQ1 -f /usr1/v101A/dlc/properties/ubroker.properties