| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.1.0) for Microsoft Windows B31012-02 |
|
 Previous |
 Next |
| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.1.0) for Microsoft Windows B31012-02 |
|
Previous |
Next |
This chapter describes issues associated with Oracle Enterprise Service Bus. It includes the following topics:
This section describes general issue and workaround. It includes the following topic:
Section 7.1.3, "Memory Usage Grows Gradually in Default Installation at High Volume"
Section 7.1.5, "External Dependencies Used at Design Time Must Be Available at Deployment Time"
Section 7.1.6, "Multibyte Characters Are Not Supported in Some ESB Component Names"
The Oracle Application Server SOA Suite Basic Install type should be used for development and pre-production testing. The Oracle Enterprise Service Bus standalone Developers installation type is not a supported option.
For information on installing the SOA Suite Basic Install type, see Oracle Application Server Installation Guide or Oracle Application Server Installation Guide for Linux x86.
When there is a large number of outstanding messages (more than 100K) in an AQ queue, dequeuing in the AQ adapter can be very slow with an Oracle 10.2.0.2 database.
You can remedy the problem by running dbms_stats.gather_table_stats or dbms_stats.gather_schema_stats to analyze the queue tables for query optimization.
In high volume, high throughput environment, you might notice that the memory usage of the container is growing gradually. This might be a result of the instance tracking data not being flushed from the in-memory data structure fast enough. You can tune (reduce, in this case) the flush interval with a SQL statement executed against the ESB_PARAMETER table in the ORAESB schema as follows:
INSERT INTO ESB_PARAMETER (PARAM_NAME, PARAM_VALUE)
VALUES ('TrackingMessageFlushInterval', '500');
The PARAM_VALUE in the SQL statement represents 500 milliseconds.
If a value already exists, use the SQL UPDATE statement to update the parameter value, as follows:
UPDATE ESB_PARAMETER SET PARAM_VALUE = '500'
WHERE PARAM_NAME = 'TrackingMessageFlushInterval';
After modifying the ESB_PARAMETER table, you need to restart the ESB Server.
Filter expressions, XSL data transformations, and tracking fields do not support any XPath functions that are not part of the XPath 1.0 specification. The header support functions are an exception and are supported as Preview features. For information about Preview features, see Section 7.3.1, "Some Oracle Enterprise Service Bus Features are in Preview Mode".
Ensure that all external dependencies that are used at design time, such as hosted WSDLs and XSDs, are available at the time of deployment. The deployment engine uses these artifacts to generate metadata. The deployment engine will try to access the artifacts until they are available or the engine times out.
The Oracle Enterprise Service Bus project, schema, service, and system names do not support multibyte characters. Use ASCII characters for those names.
Oracle Enterprise Service Bus does support multibyte character set payloads (data). The restriction on multibyte characters only applies to configuration data.
This section describes configuration issues and their workarounds. It includes the following topics:
Section 7.2.1, "ESB Server Displays a Warning Message When Shut Down"
Section 7.2.2, "Oracle ESB Control Does Not Display Correctly For Some Window Sizes"
Section 7.2.3, "Access Problem After Logging into Oracle ESB Control Using Internet Explorer"
Section 7.2.4, "Timeout Exceptions When Using Oracle Enterprise Service Bus"
Section 7.2.5, "Missing pc.properties After Completing the ESB Standalone Installation"
Section 7.2.9, "Non-transactional MQ Adapter Incorrectly Configured as Transactional"
A warning message might be displayed when the ESB Server shuts down. This occurs because the ESB runtime process interrupts the worker threads while shutting down.
The warning message has no impact and is safe to ignore.
When resizing Oracle ESB Control, sometimes the scroll bar is missing and other layout issues might occur. To display the correct layout, maximize the Oracle ESB Control window.
If you are having problems accessing the Oracle ESB Control with Internet Explorer, you can reconfigure the security options to add your domain to the local intranet zone.
From the Internet Explorer toolbar, select Tools > Internet Options > Security > Local intranet > Sites > Advanced, then add your domain in the entry field. For example, if your server hostname is esbserver.oracle.com, add *.oracle.com to the local intranet zone.
You should make both of the updates described in this section to avoid time out errors when either ESB or another application, such as BPEL, starts a transaction. The time out error for an OC4J transaction applies to all applications and the time out error while deploying from Oracle JDeveloper only applies to Oracle Enterprise Service Bus. Note that the time out value set in the esb_config.ini file takes precedence when ESB starts the transaction.
If an OC4J transaction time out error occurs while importing metadata into the ESB Server, you need to increase the value of the transaction-timeout parameter in the Oracle_Home/j2ee/home/config/transaction-manager.xml file. The error can occur for various reasons, such as a BPEL or an external service WSDL is not available or slow.
If a time out error occurs while deploying from Oracle JDeveloper, you need to increase the value of the xa_timeout parameter in the Oracle_Home/integration/esb/esb_config.ini file. After modifying the file, you need to restart the ESB Server.
After completing the Oracle Enterprise Service Bus standalone installation, the following error message might occur:
Could not locate file pc.properties in classpath
To create the pc.properties file for your system, perform the following:
Copy Oracle_Home\integration\esb\config\pc.properties.esb to Oracle_Home\integration\esb\config\pc.properties.
Edit pc.properties according to your system requirements.
Restart the ESB Server.
An inbound adapter service and its corresponding routing services are considered peer entities that should be deployed together in the same ESB system.
If you install multiple ESB repositories against the same database, the second repository installation overwrites the existing ESB metadata configuration residing in the ESB_PARAMETER table. In order to preserve the old values, you need to export the ESB_PARAMETER table before installing the second repository, then import the ESB_PARAMETER table after completing the installation of the second repository.
For information about exporting and importing the ESB_PARAMETER table, see "Updating the ESB Metadata" in Oracle Application Server Enterprise Deployment Guide.
When using a non-default JMS setup, you need to specify several parameters in the ESB_PARAMETER table to indicate JNDI locations for the topic and connection factory. The parameters are:
PROP_NAME_ERROR_XATCF_JNDI
Description: XA JMS connection factory for error topic
Example: OracleOJMS/XATCF
PROP_NAME_ERROR_TCF_JNDI
Description: Non-XA JMS connection factory for error topic
Example: OracleOJMS/TCF
After modifying the ESB_PARAMETER table, you need to restart the ESB runtime and design time servers.
At installation time, the MQ Adapter is incorrectly registered with Oracle Enterprise Service Bus as transactional. This leads to the display of an incorrect status in Oracle ESB Control when transactions are rolled back.
The IS_TRANSACTIONAL columns in the ESB_SERVICE_TYPE table should be set to N (not Y) when SERVICE_TYPE is equal to MQ. You can fix the ESB service configuration in the ESB_SERVICE_TYPE table using the following SQL statement:
UPDATE ESB_SERVICE_TYPE SET IS_TRANSACTIONAL = 'N' WHERE SERVICE_TYPE = 'MQ';
After modifying the table, you need to restart the ESB Server.
This section describes documentation errata. It includes the following topic:
Section 7.3.1, "Some Oracle Enterprise Service Bus Features are in Preview Mode"
Section 7.3.2, "Oracle Enterprise Service Bus and Oracle Application Server Integration B2B"
Some Oracle Enterprise Service Bus features are available in Preview mode and will be supported in a later release.
Preview features in this release are:
Endpoint properties
Adapter Endpoint properties
SOAP Endpoint properties
Header Support
Header support for Adapters
Header support for SOAP Headers, such as security, encryption, and WS-Addressing
Oracle Enterprise Service Bus to Oracle Application Server Integration B2B integration
The B2B WSIL Browser enables interoperability between Oracle Enterprise Service Bus and Oracle Application Server Integration B2B and is available through patch 5105622.
This feature are available in Preview mode and will be supported in a later release.
|
See Also:
|
