This chapter describes issues associated with Oracle Service Bus. It includes the following topics:
Note:The issues and workarounds listed here are those that were known at the time of the product's initial release to the public. Additional issues and workarounds may have been discovered since the initial release. To view the latest known issues associated with Oracle SOA Suite, BPM Suite, and related SOA technologies, go to the Oracle Technology Network (OTN) at:
This section describes new features and enhancements in Oracle Service Bus 11g Release 1 Patch Set 3 (188.8.131.52.0).
This section describes security enhancements provided in this release.
For services protected with OWSM policies, Oracle Service Bus lets you specify the version of WS-Policy and WS-Security Policy to use for security policies in advertised WSDLs.
For more information, see "Advertising WSDLs to Support WS Standards" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
In business services, you can find and attach compatible client OWSM policies for standard security policies embedded in the WSDL that the business service is based on.
On the business service policy configuration page, when you select the "From OWSM Policy Store" option and click Add Compatible, Oracle Service Bus attempts to locate and return compatible OWSM policies to replace unsupported WSDL-embedded WS-Policies.
For more information on this feature, and for information on using Oracle Web Services Manager with Oracle Service Bus, see "Securing Oracle Service Bus with Oracle Web Services Manager" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
For proxy services, the default value for the "Process WS-Security Header" option has changed to "Yes." The new default setting applies when the WSDL contains a supported WLS 9 security policy, an OWSM security policy, or a custom policy configured for the proxy service. This change makes the proxy service an active security intermediary by default.
Oracle Service Bus now provides support for Oracle Web Services Manager authorization policies.
"Securing Oracle Service Bus with Oracle Web Services Manager" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus lists assertions and seed policies that are unsupported. Any assertions and seed policies not listed are supported.
Oracle Service Bus provides support for the Oracle JCA Adapter for Files/FTP.
For more information, see "JCA Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
The JMS transport has been enhanced to provide high availability and failover for inbound JMS messages received on a topic. When a JMS proxy service listening on a topic is deployed to a cluster, you can configure the proxy to use the "One Copy Per Application" option on the "Topic Messages Distribution" property. This option ensures that an incoming JMS message is processed on one available managed server in the cluster.
For more information, see "Transport Configuration" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
The Oracle Service Bus HTTP transport has been enhanced to provide access to individual query parameters in the query string. In turn, this allows Oracle Service Bus to propagate query strings with encoded characters (such as & and #) correctly between proxy services and business services.
For more information on the "parameters" metadata element that was added to the HTTP transport schema to enable this enhancement, see "HTTP Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
Result caching in Oracle Service Bus can now be used with a stand-alone Coherence-only server.
For more information, see "Using an Out-of-Process Coherence Cache Server" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus.
This section describes general issue and workarounds. It includes the following topics:
In the development environment, when starting a managed server by passing the managed server's IPv6 address and port, Oracle Service Bus throws a BEA-000000 "Cannot contact Admin server" error.
To work around this issue, create a new key-pair, then reconfigure SSL on the Admin server so that the key-pair in the server-side SSL certificate uses the host name of your IPv6 managed server. Then restart your managed server.
For more information on SSL, see "Configuring SSL" in Oracle Fusion Middleware Securing Oracle WebLogic Server.
When activating an Oracle Service Bus session in Firefox, session activation takes longer than three minutes and you see an error message stating, "Another session operation is in progress. Please retry later."
The error message is harmless, and you can ignore it. The server is still processing the session activation, and you can wait for activation to finish.
The error message occurs when the Firefox network connection is set to "Manual proxy configuration" and the "HTTP Proxy" value is used for all listed protocols. The message is triggered by Firefox's auto-refresh occurring in conjunction with the proxy settings.
If you want to ensure the error message does not appear rather than ignoring it, change the Firefox proxy settings to another option, such as "Auto-detect proxy settings for this network" or "Automatic proxy configuration URL." To access these options in Firefox, choose Tools > Options > Advanced > Network > Settings.
On 64-bit installations of Oracle Service Bus, after upgrading a domain from 11g Release 1 Patch Set 2 (184.108.40.206.0) to 11g Release 1 Patch Set 3 (220.127.116.11.0), the JAVA_HOME value in the upgraded domain's setDomainEnv.cmd/sh file is incorrect.
The reason JAVA_HOME is not set correctly on 64-bit installations is because the 64-bit installer does not include a JDK.
To work around this issue, edit the setDomainEnv.cmd/sh in the upgraded domain with the correct JAVA_HOME for the JDK you are using.
Included per bug 10424957.
When installing the Oracle Application Adapters for use with Oracle Service Bus, such as the Oracle Application Adapter for SAP R/3, you receive the following error:
"The ORACLE_HOME doesn't have the right version of SOA or OSB. The adapters cannot be installed."
Because the Oracle Application Adapters installer gets the JAVA_HOME value from the Windows registry, any space in the JAVA_HOME value in the registry causes the installation failure. For example, if the JavaHome value is C:\Program Files\Java\jre6, the space between "Program" and "Files" causes the failure.
To work around the issue:
Back up your Windows registry.
In Windows, choose Start > Run, enter regedit in the Run dialog box, and click OK.
In the registry editor, go to the following registry folder:
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\version_number
Modify the JavaHome and RuntimeLib values so that they point to a path that does not contain spaces in the directory names.
Changing the value may require you to either point to a different Java home without spaces in the directory names or rename the path of a Java home to remove spaces.
This section describes configuration issues and their workarounds. It includes the following topics:
When using the Oracle JCA adapters with Oracle Service Bus, Oracle Service Bus throws an error when the inbound payload size (DOM size) exceeds what is allowed by the payloadSizeThreshold adapter endpoint property.
To work around this issue, increase the size of the payloadSizeThreshold property on the JCA adapter endpoint configuration.
Publishing services from the development environment to a domain that uses IPv6 addressing results in a MalformedURLException error.
To work around this issue, when specifying the host name in the "Define New Server" window in the Servers view of the IDE, use either the server host name or specify the IPv6 server address in square brackets. For example: [2001:0db8:ffff:ffff:ffff:ffff:ffff:ffff].
After creating resources in the Oracle Service Bus Console, then changing the server encoding and restarting the server with the different encoding, only English language resources (if any) appear in the Oracle Service Bus Console. Non-English resources do not appear.
For example, if you start the server using ja_JP.utf8 encoding and create resources in the Oracle Service Bus Console with Japanese, Korean, and English names, then restart the server using a different encoding such as ko_KR.euckr, only the English-name resources appear in the Oracle Service Bus Console.
In this situation, the missing resources still exist but are not displayed because of the encoding change.
To work around this issue, switch back to the original server encoding and restart the server. Oracle Service Bus does not support server encoding changes.
This section describes documentation errata. It includes the following topics:
Included per bug 10181085.
This section describes how to configure your environment in order to start an Oracle Service Bus domain as a Windows service. Because this procedure requires a modification to your Windows registry, you should back up your Windows registry before proceeding.
Set your Oracle Service Bus domain to start as a Windows service by running the WL_HOME\server\bin\installSvc.cmd script, as described in "Setting Up a WebLogic Server Instance as a Windows Service" in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server.
Add the required environment variables to the Windows registry. Before proceeding, you must know the name of the Windows service you created. The service name is typically "beasvc [DOMAIN_NAME]_[SERVER_NAME]."
Back up your Windows registry.
Run the Windows regedit utility. Choose Start > Run in Windows. Enter regedit in the Run dialog box, and click OK.
Locate the following registry key for your Windows service:
Create a new Multi-String Value called
Edit the new Environment value by adding the following entry:
where C:\oracle11g is the root of your Oracle Fusion Middleware installation.
Windows XP 32-bit only: In a command window, change directories to a location where you want to generate a temporary file, then run the following command:
set > env.txt.
Open the env.txt file, copy its entire contents, and paste the contents into the Environment registry value you created, below the ALSB_HOME entry.
Click OK in the multi-string value dialog box and close the Windows registry editor.
Before starting the service, be sure to start any databases used by the Oracle Service Bus domain.
Note:This section will be added to the Oracle Service Bus security topics in a future release.
If you are using a plug-in security provider with Oracle WebLogic Server to store policies for use with Oracle Service Bus, you may encounter an error that says Oracle Service Bus cannot determine whether or not required policies are available; for example, error BEA-387896, as described in the Oracle Fusion Middleware Messages for Oracle Service Bus.
An error message like that does not necessarily mean the policies do not exist, or that you have a connection or configuration problem with the security provider. Oracle Service Bus uses an Oracle WebLogic Server SSPI to read policies that security providers can implement. However, the SSPI read functionality is optional. It is possible that a security provider does not allow read access by not implementing this SSPI. In such a case, Oracle Service Bus cannot reliably determine whether or not the security provider contains the required policies, even when the required policies could very well exist in the security provider.
To determine whether or not such a warning indicates a real problem, try creating or modifying resources in the Oracle Service Bus Console. Also, try securing a proxy service with an access control policy and test it. See "Editing Message-Level Access Policies" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus for more details on how to configure an access control policy on a proxy service. If you can successfully create or manipulate resources as well as test a secured proxy service while using the security provider, then the security provider is configured correctly and you can safely ignore the error message.
Note:Following is a modified version of the existing "Adding WSDLs" section of the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus. The updated content is the "Before You Begin" paragraph.
Before You Begin: If the WSDL resource you want to create contains URL references to external schemas that do not currently exist in Oracle Service Bus, such as http://www.w3.org/2001/XMLSchema.xsd, you must import those URL-referenced schemas—and any dependent schemas—into Oracle Service Bus by creating XML Schema resources. WSDL resources in Oracle Service Bus can only reference locally available schemas. For more information, see "Adding XML Schemas" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus.
To add a WSDL:
If you have not already done so, click Create to create a new session or click Edit to enter an existing session.
Select Project Explorer, then select a project or folder in which to add the WSDL. The Project/Folder View page is displayed.
From the Create Resource list, select WSDL from under Interface to display the Create a New WSDL Resource page.
In the Resource Name field, enter a unique name for this WSDL. This is a required field.
In the Resource Description field, enter a description for the WSDL.
In the WSDL field, do one of the following:
Enter text for the new WSDL.
Click Browse to locate and import an existing WSDL.
Copy and paste text from an existing WSDL into this field.
This is a required field.
Click Save. The new WSDL is saved in the current session.
When you click Save, if there any unresolved references for the new WSDL, the system displays them.
To end the session and deploy the configuration to the run time, click Activate under Change Center.
Following is the direct link to the Oracle Service Bus product download page. The Oracle Fusion Middleware Installation Guide for Oracle Service Bus will be updated to include this link.