|
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
- What version is the WebSphere application server?
- 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 |
|
- Where does the problem occur? Between what components?
- Is your application making the ORB calls, or is it made from the
WebSphere base code?
- Is Security or Work Load Management (WLM) enabled?
- Is the client remote or local to the server?
- Is there a firewall installed between the failing components?
- Can you successfully ping the server from the remote client? Can you
ping the client from the remote server?
- Has this problem always occurred has it just started to occur? If it
just started, what changes were made?
- Clear out the logs in the install_root/logs
directory, then recreate the problem.
- Collect the following files:
- The newly created logs.
- Answers to the preceding questions.
- For releases of WebSphere Application Server V4.0
- 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.
|
- Follow instructions to send
diagnostic information to IBM support.
Additional MustGather information for ORB interoperability problems
- What third-party ORB are you trying to use?
- What version is the third-party ORB using?
- What language is the third-party ORB using? (C++ or Java)
- What platform is the third-party ORB running on?
- What platform is WebSphere Application Server running on?
- Does the problem or error occur consistently or randomly?
- Is the problem reproducible? If so, what are the steps?
- Is WebSphere being used as the server or client to the third-party
ORB?
- Has this worked before, or is this a new configuration?
- Have you tried using the approach recommended in the CORBA Interop
samples?
- 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
- Start the client program with the "-D" arguments to specify the trace
settings.
-Dcom.ibm.CORBA.Debug=true
-Dcom.ibm.CORBA.CommTrace=true |
|
- The ORB trace output is captured in a unique trace file named
orbtrc.<timestamp>.txt in the current directory of execution.
- Collect the following file:
- Follow instructions to send
diagnostic information to IBM support.
- V6.0 ORB Trace Instructions
- From the Administrative Console, select Servers > Application
Servers > server_name > Change Log Details
Levels.
- Remove any previous entries in the text field type the following:
- Apply and save changes.
- Select Servers > Application Servers > server_name
> Diagnostic Trace Service.
- Change the Maximum Number of Historical Files to 10.
- Apply and save changes.
- Select Servers > Application Servers >
server_name> Container Services > ORB
Service.
- Select the Orb Tracing check box to enable Comm Tracing.
- Apply and save changes.
- Restart the sever and recreate the problem.
- 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 |
- Follow instructions to send
diagnostic information to IBM support.
- V5.0 and V5.1 ORB Trace Instructions
- From the Administrative Console, select Servers > Application
Servers > server_name > Diagnostic Trace
Service.
- Specify the Trace Specification with the following:
- Change the Maximum Number of Historical files to 10.
- Apply and save changes.
- Select Servers > Application Servers >
server_name> Orb Service
- Select the Orb Tracing check box to enable Comm Tracing.
- Apply and save changes.
- Restart the sever and recreate the problem.
- 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 |
- Follow instructions to send
diagnostic information to IBM support.
- V4.0 Administrative Server Trace Instructions
- Make a backup copy of the
install_root/bin/admin.config file.
- Open the install_root/bin/admin.config file.
- 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 |
|
- Restart the Administrative Server and recreate the problem.
- Collect the following file:
- Follow instructions to send
diagnostic information to IBM support.
- V4.0 Application Server ORB Trace Instructions
- 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.
- Click on Trace Service in the services table, and click Edit
Properties.
- Put the following in the Trace Specification field:
- Select the Specify radio button and type the fully qualified
pathname to where the trace should be output
|
install_root/logs/apptrace.log |
|
- Click OK and then click Apply.
- 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 |
|
- Click Apply.
- Restart the Application Server and recreate the problem.
- Collect the following file:
install_root/logs/apptrace.log |
|
- 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. |
|
|