Deploy Java components  Chapter 12: Creating CORBA Java Clients

Chapter 11: Creating CORBA Java Components

Debug Java components

You can debug Java components that are executing in EAServer.

Before you start

Debugging Java components requires the following:

Steps to debug an executing component

StepsDebugging Java components

  1. Make sure that you have followed the requirements in “Before you start”.

  2. Make sure no one else is debugging components using the same server. The server-side debugger supports only one remote-debugger connection at a time.

  3. Run your debugger. The debugger JDK version must match the server’s JDK version. You must specify the server’s host name and JPDA port, the JDPA port is specified on the JDPA tab in the server properties window. For example, using jdb to connect to a server running on machine “myhost,” using port 11000 for JPDA connections:

    jdb -connect com.sun.jdi.SocketAttach:hostname=myhost,port=11000
  4. Once connected, you can specify breakpoints for the debugger to stop at in your component implementation. Set the breakpoint before running any client applications that will exercise the target line of code. For example (the following must be entered on one line):

    stop at Sample.SVU.javaComp.
  5. Run a client application that will invoke the target component code. For example, to debug the CreateStudentRecord method in the Java_Enrollment component, run the SVU Java example client in your Web browser and create a new student record on the login screen. In the debugger, you should see some indication that the breakpoint has been reached.

    NoteYou may need to change the debugger’s active thread before the component breakpoint is indicated. EAServer runs each Java component instance in a separate Java thread. The component thread must be the active debugger thread in order to step through the component’s code. In jdb, use the threads command to list the executing threads. You can then use the thread command to switch to the thread that is running the component.

  6. Once the breakpoint is tripped, you can step through the code, inspect fields and variables, and so forth. For example, in jdb:

    Thread-21[1] where 6
      [1] Sample.SVU.javaComp.Enrollment_Java.Enrollment_JavaImpl.
    createStudentRecord (Enrollment_JavaImpl:74)
    Thread-21[1] print student_id
    student_id = 333-33-3333
    Thread-21[1] cont

Debugging class loading and unloading problems

EAServer Manager provides the following server properties to log information about Java class loading and unloading. You can set these properties on the Advanced tab in the Server Properties dialog box:



When this property is set to true, the server logs all Java classes that are loaded and the location where each class file was read.

When this property is set to true, the server logs information when memory is freed by the Java garbage collector.

When this property is set to true, the server logs information about loading classes from custom class lists defined for the component, package, application, or server.

The default for all of these properties is false.

Copyright © 2005. Sybase Inc. All rights reserved. Chapter 12: Creating CORBA Java Clients