10 Troubleshooting

This chapter provides information for troubleshooting your Oracle Web Services Manager (Oracle WSM) deployment.

Limitations of Java Policy Enforcement Points

Policy enforcement points (PEP) that rely on Java resources (that is, gateways and most agents) have the following limitations:

Java PEPs do not support actors or roles inside SOAP messages. Java PEPs usually process security headers, even if those security headers include actor or role information, which ought to prevent such processing.
If a SOAP message (request) contains one security header that does not contain an actor, the Java PEP often adds a second security header, which also does not contain any actor information. This action violates the WS-Security specification.

SSL Does Not Work Properly on OC4J

If you are using Secure Sockets Layer (SSL) libraries, remove the jssl-1_1.jar file from the OC4J_Home/lib directory, and replace it with the jssl-1_2.jar file. If you are using some other SSL library, simply remove the jssl-1_1.jar file from the OC4J_Home/lib directory. Once you have completed this step, you can use any other vendor's implementation of Java Secure Socket Extension (JSSE).

Report Engine Does Not Display Properly

To enable the Report engine, verify that all of the following are true:

You have met the requirements listed in the sections on required X Window System (X11) packages for Linux and Solaris and the required DISPLAY variable for Linux and Solaris in Oracle Application Server Installation Guide for your platform.
You can verify that X-client is running on the computer pointed to by the DISPLAY variable for the computer running Corda.

Make certain that the Corda chart server is running. Solaris systems require X Server to display Operational Management charts and graphs. If X Server is not installed, the images will not display properly. For more information on X Server, refer to the following URL:

http://developers.sun.com/solaris/articles/solaris_graphics.html

Error When Importing WSIL

Problem

You are registering a service to a gateway by importing a Web service from a UDDI or a WSIL; you get an error similar to one of the following:

Could not establish a connection to the URL: URL_address
Error accessing the specified URL

Solution

The cause of this problem may be that your proxy server settings are not set. Follow the procedure that follows and set your proxy server settings.

For standalone Oracle WSM

Open the following file:

ORACLE_HOME/owsm/bin/coresv.properties

Edit the following parameters:

proxy.host = proxy_server

proxy.port = listen_port

noproxy.hosts = host_name

Table 10-1 describes how to set the values for the parameters.

Table 10-1 Parameter Settings for a Proxy Server

Parameter Value	Description of Value
`proxy_server`	Name of the proxy server. For example, `www-proxy.us.oracle.com`.
`listen_port`	The port number on the proxy server where you wish to connect. For example, 80.
`host_name`	Hosts that connect directly without intervention from the proxy server. This value can be a list of host names separated by a vertical bar (`\|)`, or an asterisk (``). For example, `localhosts\|oracle.com`

Restart the Oracle WSM server for the configuration changes to take effect.

For Oracle WSM when it is installed as part of Oracle Application Server 10g Release 3 (10.1.3.1.0)

Open the following file:

ORACLE_HOME/opmn/conf/opmn.xml
Find the process-type id whose value is the name of the instance in which Oracle Web Services Manager is installed. This may be "home", or it could be another instance name. For example:
```
...
<ias-component id="default_group">
   <process-type id="home" module-id="OC4J" status="enabled">
...
```

Find the data id="java-options" in the category id="start-parameters" section of the file.

...
<category id="start-parameters">
   <data id="java-options" value="-server -XX:MaxPermSize=128M .../>
</category>
...

Add the following parameters under java-options:

Dhttp.proxySet = true

Dhttp.proxyHost = proxy_server

Dhttp.proxyPort = listen_port

Dhttp.nonproxyHost = host_name

Table 10-2 Parameter Settings for Oracle WSM Installed as Part of Oracle Application Server

Parameter Value	Description of Value
`true/false`	The value `true` enables the proxy server.
`proxy_server`	Name of the proxy server. For example, `www-proxy.us.oracle.com`.
`listen_port`	The port number on the proxy server where you wish to connect. For example, 80
`host_name`	Hosts that connect directly without intervention from the proxy server. This value can be a list of host names separated by a vertical bar (\|) or an asterisk (``). For example, `localhosts\|oracle.com`

Restart the server for the configuration changes to take effect.

Example UDDI Registry Does Not Work

Problem

When you try to import a service using the example UDDI registry http://<oc4jhost>:<port>/registry/uddi/inquiry, you get the following error: Could not establish a connection to the URL: http://oc4jhost:port/registry/uddi/inquiry.

Solution

You must install the Oracle Registry in order to use this UDDI.

Error When Accessing WSDL

Problem

When you enter or paste the Web service WSDL URL in a browser, you get the following error:

Oracle Web Services Manager Gateway C0003001: No policies found for service "SID0003003". Make sure the service is registered correctly and the gateway policies are up-to-date.

Solution

One possible cause is that the component ID for the gateway is incorrectly set. Follow this procedure:

From the navigation pane, select Policy Management, then select Manage Policies.
Look for your gateway in the list of components, and get the component ID.
Open the following file:

ORACLE_HOME/owsm/config/gateway/gateway-config-installer.properties

Verify that the gateway.component.ID property is set to the same ID as the ID for your gateway. If they are not the same, then make the necessary change to the file.

If you change the component ID in the file, you must redeploy the gateway application for the changes to take effect. See Oracle Web Services Manager Deployment Guide for more information on deploying your application.

Error Testing Access to Web Service

Problem

You are using the Test Page to test access to your Web service. You enter the WSDL URL and click Submit Query, and get the following error: Failed to read WSDL from http://host_name:port/gateway/services/SID000300n?wsdl:WSDL not found.

Solution

One possible cause is that the component ID for the gateway is incorrectly set. Follow the procedure in "Error When Accessing WSDL".
Another possible cause is that the proxy server settings are not set. See the solution for "Error When Importing WSIL" .

Cannot Access Policy Management Menu

Problem

You are running standalone Oracle WSM. You log in to Web Services Manager Control, and you get the error: 500 Server Error. You are able to click on and access the Operational Management, Tools, and Administration menus. You see this error only when trying to access the Policy Management menu.

Solution

The problem is caused because the nonproxy hosts settings were not set during installation. See the solution for "Error When Importing WSIL" .

Web Services Manager Control Times Out

Problem

The Web Services Manager Control times out too quickly, and you have to log in to your session.

Solution

By default, the browser session is set to 60 minutes. Edit the ui.session.timeout parameter in the ORACLE_HOME/owsm/config/ccore/ui-config-common.properties file.

Metrics Data Does Not Appear in Web Services Manager Control

Problem

You see the metrics for a Web service invocation for a period of time. After some time, the metrics for that particular invocation stop appearing in Web Services Manager Control.

Solution

You can view metrics for Oracle Web Services Manager for different time periods ranging from the last 10 minutes up to 60 days. However, by default, Oracle WSM Database persists data only for the last 100 minutes. Therefore, to see historical data beyond 100 minutes, you must configure the monitor.aggregator.measurementStore.WindowSize parameter in the ORACLE_HOME/owsm/config/coreman/monitor-config-installer.properties file. For more information, see "Configuring Metrics Data Persistence".

Log Files Providing Wrong Level of Information

Problem

Log files do not contain the right level of information. More or less information is needed.

Solution

Each Oracle Web Services Manager application has its own logging configuration file.

For more information on changing the logging level, see "Low-Level Event and State Logs".

Resetting Log Levels Does Not Seem to Work

Problem

Changing the log level does not change the level of information in the log files.

Solution

Each application, Oracle WSM Policy Manager, Oracle WSM Monitor, Oracle WSM Gateway, Oracle WSM Server Agent, Oracle WSM Client, and Web Services Manager Control, has its own logging configuration file. Verify that you have configured the correct file.
You can set the log level for each class. In most instances, you will probably set the same log level for all classes for an application. But if you have set different log levels, verify that the log level is set as you desire for the correct class.
After you configure the log level, you must redeploy the application for the changes to take effect.

Addressing Performance Issues

A comprehensive treatment of performance issues within distributed systems involves a level of complexity that is beyond the scope of this book. There are many good reference guides that present guidelines, in addition to details about performance issues and performance tuning.

As an alternative to providing a comprehensive discussion of performance, this section offers some general guidelines on how to identify a performance bottleneck and how to approach addressing such problems.

If you discover a performance bottleneck, you should first check to see that you have addressed the expected traffic load throughout your Web services deployment. If there is a system in the critical path that is at 100% CPU usage, you may simply need to add one or more computers to the cluster.

If there is a bottleneck in your deployment, it is likely to be within one of the following:

Traffic through a slow connection with an agent
Traffic through a slow connection with a gateway
Unexpected high traffic volume through an Oracle WSM Monitor that is connected to a database
Latency in connections to third-party queueing systems like JMS or MQ

For any of these problems, check the following potential sources:

Problems with policy steps that include connections to outside resources, especially the following types:
- Database repositories
- LDAP repositories
- Secured resources
- Proprietary security systems
Problems with database performance

If you identify one of these as the cause of a bottleneck, you may need to change how you are handling your database or LDAP connections, the securing of your resources, or the details of how you are aggregating and persisting Oracle WSM monitoring data.

Error When Logging In to Web Services Manager Control

Problem

You log in to the Web Services Manager Control and get the following error:

The following exception occurred when processing the JSP:
org.xml.sax.SAXException: Bad envelope tag: HTML
Use your browsers "Back" button if you would like to try again.

Solution

This is a known bug that occurs after you deploy the Oracle WSM Policy Manager. Restart the Oracle Process Manager and Notification Server (OPMN) process (opmnctl restartproc) on the OC4J instance where the Oracle WSM components are installed. Then retry logging in to Web Services Manager Control.