MustGather: Object Request Broker (ORB) for all releases
 Technote (FAQ)
 
Problem
MustGather for problems with the WebSphere® Application Server Object Request Broker. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
 
Cause
 
Solution
The ORB manages the interaction between clients and servers, using the Internet Inter-ORB Protocol (IIOP). It enables clients to make requests and receive responses from servers in a network-distributed environment.

If you have already contacted support, continue on to the component-specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Application Server products.


Object Request Broker specific MustGather information
  1. What version is the WebSphere application server?

  2. What are the versions of ORBs and JDK™ from both client and server environments?

    install_root/java/bin/java -version
    install_root/java/bin/java -fullversion
    install_root/java/bin/java -Xbootclasspath/p:install_root/java/jre/lib/ext/ibmorb.jar com.ibm.CORBA.iiop.Version

  3. Where does the problem occur? Between what components?

  4. Is your application making the ORB calls, or is it made from the WebSphere base code?

  5. Is Security or Work Load Management (WLM) enabled?

  6. Is the client remote or local to the server?

  7. Is there a firewall installed between the failing components?

  8. Can you successfully ping the server from the remote client? Can you ping the client from the remote server?

  9. Has this problem always occurred has it just started to occur? If it just started, what changes were made?

  10. Clear out the logs in the install_root/logs directory, then recreate the problem.

  11. Collect the following files:
    • The newly created logs.
    • Answers to the preceding questions.
    • For releases of WebSphere Application Server V4.0
      • Xmlconfig -export file
    • For releases of WebSphere Application Server V5 and V6
      • collector.[sh/bat] output
    • Any additional information you think might relate (topology, symptoms, and so on) to IBM.

    Note: Additional ORB, Security, or WLM traces might be required.

  12. Follow instructions to send diagnostic information to IBM support.


Additional MustGather information for ORB interoperability problems

  1. What third-party ORB are you trying to use?

  2. What version is the third-party ORB using?

  3. What language is the third-party ORB using? (C++ or Java)

  4. What platform is the third-party ORB running on?

  5. What platform is WebSphere Application Server running on?

  6. Does the problem or error occur consistently or randomly?

  7. Is the problem reproducible? If so, what are the steps?

  8. Is WebSphere being used as the server or client to the third-party ORB?

  9. Has this worked before, or is this a new configuration?

  10. Have you tried using the approach recommended in the CORBA Interop samples?

  11. Where was the IDL compiled (what tool was used)?


If specific ORB traces have been requested by the WebSphere support team, use the following instructions:

  • Stand Alone Java Client ORB Trace Instructions
    1. Start the client program with the "-D" arguments to specify the trace settings.

      -Dcom.ibm.CORBA.Debug=true -Dcom.ibm.CORBA.CommTrace=true

    2. The ORB trace output is captured in a unique trace file named orbtrc.<timestamp>.txt in the current directory of execution.

    3. Collect the following file:

      orbtrc.<timestamp>.txt

    4. Follow instructions to send diagnostic information to IBM support.

  • V6.0 ORB Trace Instructions
    1. From the Administrative Console, select Servers > Application Servers > server_name > Change Log Details Levels.

    2. Remove any previous entries in the text field type the following:

      ORBRas=all=enabled

    3. Apply and save changes.

    4. Select Servers > Application Servers > server_name > Diagnostic Trace Service.

    5. Change the Maximum Number of Historical Files to 10.

    6. Apply and save changes.

    7. Select Servers > Application Servers > server_name> Container Services > ORB Service.

    8. Select the Orb Tracing check box to enable Comm Tracing.

    9. Apply and save changes.

    10. Restart the sever and recreate the problem.

    11. Collect the following file:

      <PROFILE_ROOT>/logs/server_name/trace.log
      Note: If your trace rolls over (timestamp appended), please send all files with the trace prefix
    12. Follow instructions to send diagnostic information to IBM support.

  • V5.0 and V5.1 ORB Trace Instructions
    1. From the Administrative Console, select Servers > Application Servers > server_name > Diagnostic Trace Service.

    2. Specify the Trace Specification with the following:

      ORBRas=all=enabled

    3. Change the Maximum Number of Historical files to 10.

    4. Apply and save changes.

    5. Select Servers > Application Servers > server_name> Orb Service

    6. Select the Orb Tracing check box to enable Comm Tracing.

    7. Apply and save changes.

    8. Restart the sever and recreate the problem.

    9. Collect the following file:

      install_root/logs/server_name/trace.log


      Note: If your trace rolls over (timestamp appended), please send all files with the trace prefix
    10. Follow instructions to send diagnostic information to IBM support.

  • V4.0 Administrative Server Trace Instructions
    1. Make a backup copy of the install_root/bin/admin.config file.

    2. Open the install_root/bin/admin.config file.

    3. Add or update the following lines:

      com.ibm.ejs.sm.adminServer.traceString=ORBRas=all=enabled
      com.ibm.ejs.sm.adminServer.traceOutput=
      <fully_qualified_pathname>
      com.ibm.CORBA.Debug=true
      com.ibm.CORBA.CommTrace=true

      The following is an example of <fully_qualified_pathname>:

      /opt/WebSphere/AppServer/logs/admintrace.log

    4. Restart the Administrative Server and recreate the problem.

    5. Collect the following file:

      admintrace.log

    6. Follow instructions to send diagnostic information to IBM support.

  • V4.0 Application Server ORB Trace Instructions
    1. Run the Administrative Console, expand the topology frame and highlight the application server which is going to be traced to display its properties, and click on the Services tab.

    2. Click on Trace Service in the services table, and click Edit Properties.

    3. Put the following in the Trace Specification field:

      ORBRas=all=enabled

    4. Select the Specify radio button and type the fully qualified pathname to where the trace should be output

      install_root/logs/apptrace.log

    5. Click OK and then click Apply.

    6. Next to the System Properties table, click Add. Then add the following names and corresponding values:

      com.ibm.CORBA.Debug true
      com.ibm.CORBA.CommTrace true

    7. Click Apply.

    8. Restart the Application Server and recreate the problem.

    9. Collect the following file:

      install_root/logs/apptrace.log

    10. Follow instructions to send diagnostic information to IBM support.


For a listing of all technotes, downloads, and educational materials specific to the ORB component, search the WebSphere Application Server support site.
 
Related information
Submitting information to IBM support
Steps to getting support
MustGather: Read first
Troubleshooting guide
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Object Request Broker (ORB)
Operating system(s): HP-UX
Software version: 4.0
Software edition:
Reference #: 1157005
IBM Group: Software Group
Modified date: Oct 13, 2005