Known Issues and Workarounds

3.1 Longer startup time when more alerts

Issue

Bug Number: 28249908

Impacted Releases: All

Impacted Platforms: All

It is expected that startup times for managed servers will be longer when more alerts are generated.

3.2 OSB REST service returns empty string instead of null

Issue

Bug Number: 27848408

Impacted Releases: 12c

Impacted Platforms: All

OSB REST service returns empty string instead of null after upgrade to 12.2.1.3, for example {"date": ""} because Fabric bug 24309280 changed the behavior.

Workaround

There is a new system property, oracle.osb.json.nillable.supportThe default is false, which disables the nillable feature of JSon Translator when calling it from Service Bus. When this variable is not set, or is set to false, an empty value is returned as null. When this property is set to true, an empty value is returned as “ “.

3.3 ZipFileIndex leak after import/delete jejb transport proxy service

Issue

Bug Number: 27618545

Impacted Releases: 12c

Impacted Platforms: All

If there is leak in ZipFileIndex after importing or deleting jejb transport proxy service, the workaround is to turn off compiler argument value="-XDuseOptimizedZip=false".

Workaround

Set the compiler option for build.xml in jejb-transport.jar.

find ~/ -name "jejb-transport.jar" -ls 1454243  336 -rw-r-----   1 oracle   oracle     340486 Aug 20  2017
 /refresh/home/Oracle/Middleware/Oracle_Home/osb/lib/transports/jejb-transport.jar 

cd $ORACLE_HOME/osb/lib/transports/ 

cp -p jejb-transport.jar jejb-transport.jar.ori 

jar -xvf jejb-transport.jar com 

cd com/bea/wli/sb/transports/jejb/ 

vi build.xml

Start the AdminServer.

Import or delete several times.

/refresh/home/Oracle/Middleware/Oracle_Home/oracle_common/common/bin/wlst.sh 
import.py 
/refresh/home/Oracle/Middleware/Oracle_Home/oracle_common/common/bin/wlst.sh 
delete.py

Get the heap dump.

/etc/alternatives/jdk1.8.0_141/bin/jmap   
-dump:format=b,file=/refresh/home/temp6/heap_20180411.hprof 15228

There is no ZipFileIndex object.

3.4 Setting of Proxy Service: cannot modify managed server

Issue

Bug Number: 27674034

Impacted Releases: 12c

Impacted Platforms: All

When you set the proxy service in JDeveloper, the Managed Server field is grayed out and cannot be modified. This causes OSB-381612 error at deploying the Service Bus project from JDeveloper, and the deployment fails.

The Managed Server field is only enabled if Service Bus is running in cluster mode. However, JDeveloper cannot determine whether Service Bus is running in a cluster or a non-cluster environment because the Weblogic server details are only given at deployment.

Workaround

Edit the proxy service source code in a text editor and add the managed server name to the pollerTargetManagedServer element.
Example: <sftp:pollerTargetManagedServer>osb_server1</sftp:pollerTargetManagedServer>
Save the source code.
Refresh the JDeveloper code.
The value for the proxy server appears in the Managed Server field.
Retry the deployment

3.5 WSA headers removed on outbound request

Issue

Bug Number: 27229077

Impacted Releases: 12c

Impacted Platforms: All

Patch 23133629 contains a fix for Bug 21659900 which would change Service Bus to remove WSA headers from a request message only for OWSM policies with RM policy assertions. In the case when no RM policy assertions are used in the OWSM policy, all WSA headers on a request message are preserved. This is the correct behavior.

Workaround

Disable WSA headers for JDE web services from the SOA side after Patch 23133629 is applied, because the JDE web services cannot handle all of the preserved WSA headers on an incoming request message.

3.6 Bean has null package error when importing aproject with a JEJB transport in PS

Issue

Bug Number: 27473892

Impacted Releases: 12c

Impacted Platforms: All

“"Bean has null package" error when importing a project with a JEJB transport in PS. There is no product issue. The system is logging a warning and returning “false” which determines that the proxy is not a JAX-RS component. You can ignore this warning.

3.7 Encryption login is not implemented for static user name/ password of Service Account of OSB composite

Issue

Bug Number: 27068755

Impacted Releases: 12c

Impacted Platforms: All

Encryption login is not implemented for static user name and password of Service Account of OSB composite. The user name and password are saved as plain text in service account artifact.

Workaround

Encryption and decryption of static username and password of Service Account of OSB composite is available now through OSB Bundle Patches 12.2.1.1.0 and 12.2.1.3.0. When you apply the patch, username and password are saved as encrypted strings in service account artifact and decrypted to render on the UI when you open service account editor. Download and apply the OSB Bundle Patch 12.2.1.3.0 or 12.2.1.1.0 for your version.

3.8 JMS Transport When Using MQ Series as Foreign JMS Server Requeues Empty Messages

Issue

Bug Number: 27240842

Impacted Releases: 12c

Impacted Platforms: All

When you post a poison message (for example, an empty message), you can see the same message is dequeued and moved to backout queue, then is enqueued back to messaging queue and this continues in a loop as it is being redelivered forever.

Workaround

This is an known issue when using MQ Series for Foreign JMS server. The MQ backout queue feature does not complete/ commit message to the backout queue until the next successful message is processed/ committed.

3.9 MQ Channel Abended Due to Incorrect OSB XA Sequence

Issue

Bug Number: 27144719

Impacted Releases: 12c

Impacted Platforms: All

IBM MQSeries 7.1+ no longer requires the AsyncTimeoutDelist workaround to prevent a memory leak. As a result the AsyncTimeoutDelist workaround is now causing the MQ channel to become abended in certain situations.

Workaround

There is a new system property to allow you to revert to the original behavior if necessary, if you are running an older version of MQ. The new property is Dweblogic.transaction.enableAsyncTimeoutDelist=true.

-

3.10 SOAP Content validation not being enforced

Issue

Impacted Releases: 11g, 12c

SOAP 1.1 content validation is not being enforced in 11g. In 12c, it is not enforced unless OWSM is enabled.

3.11 System Property to enforce restriction

Issue

Bug Number: 27178408

Impacted Releases: PS2, PS3

Impacted Platforms: All

During server startup, xmlbeans does stricter checking than other tools. This can cause recurse errors.

Workaround

To turn off particle restriction checking, pass the following system property during domain startup:

-Dxmlbean.particlerestriction=false.

3.12 Generated WSDL has different port name

Issue

Bug Number: 27178665

Impacted Releases: 12c

Impacted Platforms: All

When you create a WSDL based proxy service based on WSDL binding type, the Service Bus runtime automatically generates the service and port names when the effective WSDL is generated. Prior to release 12c, the service name was similar to $WSDL_Binding_Name+Service+index, where the index ranged from 1 to Integer.MAX_VALUE. Index was appended to ensure the uniqueness.

As part of the OWSM policy metadata decoupling project in release 12c, OWSM API required Service Bus to pass the service and port name for a service attached with OWSM policies. The code generating uniqueness became redundant given that an effective WSDL only has one single service and one single port. The logic was changed to remove the index. Currently, the Service/Port in the effective WSDL is similar to $WSDL_Binding_Name+Service / $WSDL_Binding_Name+Port.

The existing external system should be updated to point to the new service name and port.

3.13 Siebel component not supported for Oracle Service Bus Console

Issue

Bug Number: 25540557

Impacted Releases: PS1, PS2

Impacted Platforms: All

When creating a Proxy or Business Resource in the OSB Console, the Siebel adapter is not listed. The Siebel adapter is supported only on Design time on SOA and OSB JDeveloper.

Workaround

You can design the composite on JDeveloper and deploy on the server to execute. After deployment, you can create the endpoint and the SOAP UI to execute the use case.

3.14 JMS resource cannot be deleted (Dynamic Cluster)

Issue

Bug Number: 23729629

Impacted Releases: PS2

Impacted Platforms: All

In Service Bus, in the case of a dynamic cluster environment, you cannot delete JMS-related resources from the console. As a result, you cannot import an OSB configjar file. This is a known limitation in this release.

Workaround

There is no workaround at this time.

3.15 XQuery failed — Pipeline Exception

Issue

Bug Number: 24914440

Impacted Releases: PS1, PS2, PS3

Impacted Platforms: All

An exception may occur in the pipeline if you are using XQuery to extract information from an XPath. In previous versions, a pipeline supported taking an xml element as a whole to extract the value for an XQuery transformation. In this version, the pipeline needs stricter instructions to obtain the value.

Workaround

Add /text() to the statement to specify the value of the of the XML element rather than the node itself. For example:

$body/_pr:PROCESS_PO_007[1]/oag1:CNTROLAREA[1]/oag1:SENDER[1]/oag:LOGICALID[1]/text()

3.16 OSB-DC Requests fail during ScaleDown

Issue

Bug Number: 24804809

Impacted Releases: PS2

Impacted Platforms: All

In a Service Bus Dynamic cluster with multiple servers, there could be failures during scaledown. As an example, assume Http clients are sending http requests to the application deployed on the dynamic cluster, and 200 users are sending requests simultaneously at about one request per second. When scaledown starts, which takes several minutes, about 100 requests from clients could fail to get responses.

Workaround

There is no workaround at this time.

3.17 Properties window not showing property of selected component for the two edge scenarios

Issue

Bug Number: 24518332

Impacted Releases: PS2

Impacted Platforms: All

When you first create a SOA Application & Project, do not close composite editors, and then create an Service Bus application and project, the properties window does not show the property of the selected component. When this happens, the workaround is to close JDEV and re-open to work with the Service Bus Application.

Workaround

This is no workaround at this time.

3.18 NetSuite Adapter is not displayed in the Design view of JDev

Issue

Bug Number: 24561618

Impacted Releases: PS2

Impacted Platforms: All

When you create a project in Service Bus Console that only has the Netsuite adapter as a BusinesService without any ProxyService configured, and the composite is imported from OSB Console to JDEV,the NetSuite Adapter in the Jdev is not listed in the External service area.

Workaround

There is no workaround at this time.

3.19 JAX-RPC template is now optional for Service Bus Domains

Issue

Bug Number: 23289709

Impacted Releases: PS1

Impacted Platforms: All

When you create a Service Bus domain, you select various templates to apply to the domain. The JAX-RPC option is no longer required. The only reason to use this option in new domains is to continue to use reliable WLS 9 policies. Upgraded domains will still require the JAX-RPC template, however, so dynamic clusters will not be available for upgraded domains.