Known Issues for Oracle SOA Products and Oracle AIA Foundation Pack for 11g Release 1 (11.1.1.5.0)

 

This document lists issues and workarounds for Oracle SOA and Oracle AIA Foundation Pack 11g Release 1 (11.1.1.5.0).

For a list of issues and workarounds pertaining to Oracle SOA Installation, Upgrade, High Availability, Enterprise Deployment, Performance Tuning, and Web Services, as well as SOA on IBM Websphere, see the Oracle Fusion Middleware Release Notes.

For known issues and workarounds for other Oracle SOA and AIA Foundation Pack releases, see Known Issues for Oracle SOA Products and AIA Foundation Pack.

On this page: (Last updated: 21-June-2012)

AIA Foundation Pack

SOA and BPM Suite Common Functionality

Technology Adapters

Adapter for Oracle Applications (Oracle E-Business Suite Adapter)

Application Adapters for WebLogic Server

Application Server Legacy Adapters

BPEL Process Manager

Business Activity Monitoring

Business Process Analysis Suite

Business Process Management

Business Rules

Business-to-Business Integration (B2B)

Complex Event Processing

Enterprise Repository

Human Workflow

Mediator

Service Bus

Service Registry

Enterprise Scheduling Service



AIA Foundation Pack


 

Layered Customization Information Missing from Developer's Guide


Bug: 13701898
Updated: 09-Feb-2012
Platform: All

Information on Layered Customizations is missing from Oracle® Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1 (11.1.1.5.0) guide.

Workaround: Information on Layered Customization is given below.

What are layered customizations?
Oracle application composites are created for specific industry needs. Oracle also provides options to further customize these components for business specific needs of individual organizations. Customization refers to modification of delivered artifacts to produce new behavior. You can use this option to customize the out-of-box composites delivered by Oracle and also and deploy them in place of original composites. When you customize a few composites, you create a specific solution for your organization.
However, these customizations can be overwritten when you apply a patch or upgrade when there is a new version. To ensure customization at a higher layer is not lost during an upgrade the customized layer and the base process are kept in their own metadata files. This externalization of customizations away from the base composite is possible only when the base version has been enabled for customization. Only when you want to deploy a solution the layers are merged with the base process for creating a single executable process.
For more information about layered customizations, see Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite, “Customizing SOA Composite Applications”.

Can all composites be customized?

For the services that are delivered in the certain set of Out of the Box Prebuilt Integration, customizable scopes have been added in the BPEL flow. Refer to your pre-built integration implementation guide to check whether your pre-built integration allows customization of services. You can add the custom logic in these scopes when you open the BPEL in JDeveloper using customization developer role. These customizations are kept separate from the base definition. The advantage of adding the custom logic in these scopes is that, the customization is safe when you upgrade. When you uptake the subsequent patches or new releases, they can merge these customizations on top of the new base definition and deploy the BPEL.
Note:

  • Pre-built integrations that do not have services containing customizable scopes cannot be customized inline by the customers.
  • You must adhere to following guidelines while doing the customizations.
    • Customizations are allowed only for BPEL based AIA artifacts that have customizable scopes. Inline customizations done to any other artifacts are overwritten when you apply a patch or upgrade to a newer.
    • Do not customize a composite which is not marked as customizable because they encounter merge conflicts when the composite is patched at a later point in time.
    • Do not modify the out of the box defined variables or messages as these variables may have been used in the section following customized code resulting in adverse impact on the behavior of the BPEL flow.

Deploying services after customizations

  1. Select the customized composite in JDeveloper.
  2. Right click the customized composite in the tree.
  3. Select Make<customized composite name>.jar to compile the changes.
  4. Open the CustomizeApp folder from the Jdeveloper work location.
  5. You can see the folder named merged that contains Out of the box code and Customized Code.
  6. Copy this merged folder to your server and deploy the composite using Application Deployment Driver.
    For instruction on how to deploy the changed services see, Generating Deployment Plans and Deploying Artifacts in Oracle® Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1 (11.1.1.5.0) guide.

Customizing the Customer Version

If you want to customize customer version of the SOA composite application, refer to Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite, "Customizing the Customer Version."

Applying patches after customization

To apply patches after you have customized, refer to Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite, "Upgrading the Composite" to apply their layers to the new base composite.

 

Validation of Security Policies Content Missing from the Install and Upgrade Guide


Bug: 13701932
Updated: 09-Feb-2012
Platform: All

Information on Validation of Security Policies is missing from Oracle® Fusion Middleware Installation and Upgrade Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1 (11.1.1.5.0) guide.

Workaround: Information on Validation of Security Policies is given below.

Validating Security Policies

All SOA composites are protected by Global Policies provided by Foundation Pack as defined in the Security section of the Developer Guide.

To validate locally attached security policies:

  1. Login to EM Console.
  2. Navigate to WebLogic Domain, soa_domain, Web Services, Policies.
  3. Verify Service Policy attachment.
    1. Find the service policy in the list of policies.
    2. Click the number in Attachment Count column.
      This opens Usage Analysis screen.
    3. Change the Subject Type list box to SOA Service.
    4. Validate that all the composites are listed with local attachment to this service policy.

Composite

Service

Security Policy

AIAAsyncErrorHandlingBPELProcess

client

oracle/aia_wss_
saml_or_username_token_
service_policy_OPT_ON

AIAB2BErrorHandlerInterface

ReadB2BError

N/A

 AIAB2BErrorHandlerInterface

ReadOracleB2BError

N/A

 AIAB2BErrorHandlerInterface

enrichaiafaultprocess_client

None

AIAB2BInterface

ProcessB2BDocument_ep

oracle/aia_wss_
saml_or_username_token_
service_policy_OPT_ON

 AIAB2BInterface

receiveMessageFromB2B

N/A

AIAErrorTaskAdministrationProcess

aiaerrortaskadministrationprocess_ep

oracle/aia_wss_
saml_or_username_token_
service_policy_OPT_ON

AIAReadJMSNotificationProcess

ConsumeFaultMessage

N/A

ReloadProcess

reloadconfigurationprocess_client_ep

oracle/aia_wss_
saml_or_username_token_
service_policy_OPT_ON

  1. Verify Client Policy attachment.
    1. Navigate back to Policies screen and find the client policy.
    2. Click the number in Attachment Count column.
      This opens Usage Analysis screen.
    3. Change the Subject Type list box to SOA Service.
    4. Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.

Composite

Reference

Security Policy

AIAAsyncErrorHandlingBPELProcess

N/A

N/A

AIAB2BErrorHandlerInterface

ReadOracleB2BErrorDetails

N/A

 AIAB2BErrorHandlerInterface

AIAAsyncErrorHandling
ProcessingService

None

 AIAB2BErrorHandlerInterface

EchoServletService

None

AIAB2BInterface

SendMessageToB2B

N/A

 AIAB2BInterface

X12ProcessSalesOrderReq
B2BCSImplService

oracle/aia_wss10_
saml_token_client_
policy_OPT_ON

AIAErrorTaskAdministrationProcess

N/A

N/A

AIAReadJMSNotificationProcess

AIAErrorTaskAdministrationProcess

oracle/aia_wss10_
saml_token_client_
policy_OPT_ON

 

AIA_OracleApps_Adapter Is Missing in the PS4 Upgraded Instances


Bug: 11934106
Added: 01-May-2011
Platform: All

The AIA_OracleApps_Adapter resource adapter is missing in the instances that are upgraded to PS4 from PS1 or PS2, or from an upgraded PS3 instance (upgraded to PS3 from PS1 or PS2).

Workaround: Install "AIA_OracleAppsAdapter_Config.rar" under <AIA_HOME>/Infrastructure/Install/templates/ as an application from the Weblogic console. After installation, change the Deployment Order of AIA_OracleAppsAdapter_Config to 500.


AIA FP Install Stops Responding When the Weblogic Home Properties Are Not Set Properly


Bug: 11906201
Added: 01-May-2011
Platform: All

AIA FP Install stops responding when the Weblogic home is not set up with the default name and location.

Workaround: During Weblogic installation, select "Typical" install mode and set up using the default home name and home location. If Weblogic has already been installed with the custom location, do the following:

  1. Create a wlserver_10.3 directory under the Middleware home and copy all the files from the Weblogic home under the directory.
  2. Under the DOMAIN_ROOT/bin directory, you should find a SetDomainEnv.sh file. In the file, change the existing WL_HOME variable to point to the wlserver_10.3 directory that you just created.

Configuration Wizard Stops Responding for Non-well-formed PIPManifest.xml files


Bug: 11881847
Added: 01-May-2011
Platform: All

Configuration Wizard stops responding when it encounters PIPManifest.xml files that are not well-formed.

Workaround: The Configuration Wizard logs point to the error in the PIPManifest.xml file. Terminate the process and rerun after fixing the issue.


DataSource Creation Fails When the JDBC_URL Field Contains Blank Spaces


Bug: 11936403
Added: 01-May-2011
Platform: All

The DataSource creation process fails when the JDBC_URL field contains blank spaces.

Workaround: If using the GUI install and entering "custom jdbc-url" ensure that there are no spaces present. If performing a silent install, ensure that the JDBC-URL fields in the response file do not contain any spaces.


AIA Schema Users and JMS Schema Users Are Given Privileges to Create Any View


Bug: 12338571
Added: 01-May-2011
Platform: All

AIA Schema and JMS Schema users are given privileges to create any view, which may not conform to DBA standards.

Workaround: As a part of the postinstallation process, the CREATE ANY VIEW privileges granted to the AIA Schema and JMS schema users need to be revoked and replaced with CREATE VIEW privileges. This is applicable to the AIA, XREF, JMS, and the AIALifecycle schema users.


Unable to Change Default Error User for AIA Error Assignment


Bug: 10649908
Added: 01-May-2011
Platform: All

The How to Create Error Handling User Roles section of Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1 should include the following information:
In the case of error handling, the error task users can be changed dynamically using AIAConfigurationProperties.xml, but the error task owner is fixed to AIAIntegrationAdmin. If you are using a corporate LDAP, ensure that you register AIAIntegrationAdmin to your LDAP.


Password Properties Need to Be Added to the ResubmissionParams.properties File When Using the Resubmission Script


Bug: 12366061
Added: 01-May-2011
Platform: All

You need to add the following parameters to the <AIA_HOME>/util/AIAMessageResubmissionUtil/ResubmissionParams.properties file:

  • jms.app.password=
  • aq.db.password=

Once you use the preceding values, after using the resubmission utility, delete these properties and then reenter them when running the utility again.

Back to top


SOA Suite and BPM Suite Common Functionality


New Location for Oracle SOA Suite Samples


Bug: 13452689
Added: 06-December-2011
Platform: All

The location for Oracle SOA Suite samples has changed from:

https://soasamples.samplecode.oracle.com

to

http://java.net/projects/oraclesoasuite11g/

If you are in the 11gR1 11.1.1.5.0 Oracle SOA Suite documentation and click https://soasamples.samplecode.oracle.com, you receive an untrusted connection error.

As a workaround, perform one of the following steps:

  1. Enter the new Oracle SOA Suite samples URL in your browser:

    http://java.net/projects/oraclesoasuite11g/

or

  1. Connect to the old URL without using secure HTTP (that is, remove the s in http):

    http://soasamples.samplecode.oracle.com

    This displays the Sample Code for Developers and Admins page.

  2. Scroll down the page to the Middleware & Tools section, and click the SOA (at Java.net) link.

    The Official Oracle SOA Suite 11g Samples page is displayed.


Restrictions on Changing Log File Directories


Bug: 12746127
Added: 25-July-2011
Platform: All

Do not change the location of log directories unless absolutely necessary. If an absolute path for the log directory is specified, and not a relative path, composite deployment fails.

Workaround:If any change to the SOA server log path is required, then the new path must be a relative path (relative to the SOA server directory), and not an absolute path.


Encryption and Decryption in Oracle Fusion Middleware 11g


Bug: 9646299
Added: 25-July-2011
Platform: All

There are no equivalent properties for encryption and decryption in Oracle Fusion Middleware release 11g that are similar to those provided in Oracle BPEL Process Manager release 10.1.3.5. Instead, encryption and decryption can be achieved by attaching Oracle Web Services Manager (OWSM) policies. OSWM is included in Oracle SOA Suite release 11g.

For more information about policies, see the following documentation:


Fusion Order Demo JMS Adapter Destination Value in Deployment Plan is Hard-Coded


Bug: 12316777
Updated: 6-May-2011
Platform: All

The deployment plan shipped with the Fusion Order Demo ignores the JMS adapter destination value and replaces it with a hardcoded value:

<wsdlAndSchema name="FulfillmentBatch_jms.jca">
   <jca:property name="DestinationName">
      <replace>jms/DemoSupplierTopicUdd</replace>
   </jca:property>
</wsdlAndSchema>

Therefore, if you change the destination value used by the JMS adapter, the JCA file included in the composite's JAR file reflects the changed value. However, when you deploy the new version of the composite and select the corresponding reference in Oracle Enterprise Manager Fusion Middleware Control, the old destination value in the deployment plan is still displayed.

Workaround: Change the destination value in the deployment plan or in the build.properties file.


Selection of Identity Service Function Parameters in the Expression Builder Dialog May Cause a Compilation Error


Bug: 12326444
Updated: 6-May-2011
Platform: All

The method by which you select the parameters to use with an identity service function in the Expression Builder dialog of an assign activity determines if the ids namespace prefix is correctly added. For example, the following selection method causes a compilation error.

  1. Select an identity service function in an assign activity.
    1. In the Copy Rules dialog of an assign activity, drag the Expression Builder icon to the target variable. The Expression Builder dialog is displayed.
    2. From the Functions list, select Identity Service Functions.
    3. Select and insert a function into the Expression field (for example, getManager).
    4. Place the cursor inside the parentheses of the function.
    5. From the BPEL Variable list, select and insert the variable parameters.
    6. Click OK to close the Expression Builder dialog.
    7. Click Apply and OK to close the Copy Rules dialog.
  2. Create and design a human task in the Human Task Editor.
  3. In Oracle BPEL Designer, drag and drop a human task activity into the BPEL process.
  4. Double-click the human task to display the Human Task dialog.
  5. From the Task Definition list, select the human task activity you created in Step 2.
  6. In the Task Title field, enter an expression such as the following:
  7. task for <%ids:getManager(bpws:getVariableData('inputVariable','payload','/
    client:process/client:input'))%>

  8. Complete modeling of your application.
  9. Compile the application, and note that you receive the following error:
    [scac] error: in BPELProcess1.bpel(108): namespace prefix "ids" can not be resolved

Workaround: Instead of using the BPEL Variables section of the Expression Builder dialog described in Step 1.e to assign parameters to he identity service function, place the cursor inside the function in the Expression field and select Control+Space to invoke the XPath Expression Builder. Then, select the parameters to use. This action correctly adds the ids namespace prefix and causes the BPEL process to compile successfully.

 


ant Compilation Error with SOA Composite Applications on Linux


Bug: 10255512
Updated: 6-May-2011
Platform: Linux

You can receive the following compilation error when using ant to compile a SOA composite application.

Error(12,61): Parse of component type files failed, check the adf-config.xml
file : "java.lang.NoSuchMethodError:
org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar([Lorg/apache/xerces/xni/
parser/XMLInputSource;)V:
org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar([Lorg/apache/xerces/xni/
parser/XMLInputSource;)V" 

This can occur if you have a .ant directory with older versions of JAR files that gets added to the classpath. The ${user.home}/.ant/lib directory is a standard location used by ant that is always added to the classpath when running ant.

Workaround: Perform one of the following steps:

  • Rename the .ant directory (for example, to .ant_old).
  • Specify the -nouserlib option when running ant from the Linux command prompt. In Oracle JDeveloper, this option is accessible by right-clicking your project, selecting Project Properties > Ant > Classpath, and deselecting the Include Jar Files from User Home checkbox.

The composite then compiles successfully.


Mediator Instances Can Display as Running After Transaction Completion


Bug: 8420049
Updated: 6-May-2011
Platform: All

An Oracle Mediator service component relies on a successful commit of a local transaction to know whether an instance is recoverable. Even if a graceful shutdown is correctly implemented, and all transactions are allowed to complete (within the given time out window), there can still be a local transaction that is denied because it fails to occur within the time out window. For example, assume the following:

  1. A database adapter posts a message.

  2. An Oracle Mediator service component receives the message, sets its state to running, and invokes a BPEL process service component, whose state is also set to running.

  3. A JMS adapter is invoked, and encounters and throws an exception. The reference fault tables are updated.

  4. The BPEL process receives the exception, marks its state as completed with a fault, and rethrows the exception to the Oracle Mediator.

  5. The BPEL process triggers an asynchronous persistence of its audit information as the global transaction is rolled back.

  6. Oracle Mediator receives the exception and persists the fault information in its error tables (in a separate local transaction).

  7. Oracle Mediator sets its state to faulted.

If the server is shut down before the transaction can complete (for example, between Steps 5 through 7), the Oracle Mediator instance can remain in a running state. The corresponding composite instance whose state is inferred from the components also displays as running. As the global transaction is rolled back, the message can be retried and reprocessed by the inbound adapter. Note that in this scenario, no mediator instances are lost.


Importing Shared Schema from MDS Does Not Copy the Schema Imports


Bug: 9587562
Updated: 6-May-2011
Platform: All

If you import shared schema from MDS (with schema imports within), only the base schema is copied and the schema imports are ignored.

Workaround: Manually localize the schema.


National Language Support Date Format and the Looped Purge Script


Bug: 12358938
Updated: 6-May-2011
Platform: All

You may encounter error ORA-01861 while running the looped purge script due to a mismatch in the date format. If your NLS_LANG setting represents a non-English language (for example, Japanese_Japan.AL32UTF8), set NLS_DATE_FORMAT to "YY-MON-DD" temporarily for the session in which you are running the purge script.

NLS_DATE_FORMAT = "YY-MON-DD"

For information about the looped purge script, see Chapter "Managing Database Growth" of the Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle BPM Suite.


PermGen Space Out-of-Memory Error when Using the Sun JDK


Bug: 8589284
Updated: 6-May-2011
Platform: All

When the Sun JDK is used as the JVM for the SOA managed server, Oracle recommends that the following memory settings be used. If proper memory settings are not used, repeated operations on task detail applications (human workflow) can result in PermGen space out-of-memory errors.

  1. For UNIX operating systems, open the $DOMAIN_HOME/bin/setSOADomainEnv.sh file.

  2. For Windows operating systems, open the DOMAIN_HOME\bin\setSOADomainEnv.cmd file.

  3. Increase the following values:

    if [ "${JAVA_VENDOR}" != "Oracle" ] ; then 
      DEFAULT_MEM_ARGS="${DEFAULT_MEM_ARGS} -XX:PermSize=128m 
    -XX:MaxPermSize=256m" 
      PORT_MEM_ARGS="${PORT_MEM_ARGS} -XX:PermSize=256m -XX:MaxPermSize=512m" 
    fi 
    

    to these values:

    if [ "${JAVA_VENDOR}" != "Oracle" ] ; then 
      DEFAULT_MEM_ARGS="${DEFAULT_MEM_ARGS} -XX:PermSize=512m 
    -XX:MaxPermSize=1024m" 
      PORT_MEM_ARGS="${PORT_MEM_ARGS} -XX:PermSize=256m -XX:MaxPermSize=512m" 
    fi
    

Increasing the XA Transaction Timeout Value


Bug: 8576274
Updated: 29-April-2011
Platform: All

If you send notifications for parallel task assignments in human workflow, you can see the transaction close, SQL exceptions appear, and notification processing take a long time at runtime. If this occurs, increase the XA transaction timeout for an XA data source in Oracle WebLogic Server Administration Console. When set, this value overrides the value of the global transaction timeout.

  1. Click Lock and Edit.

  2. Choose Services > Data Sources.

  3. Click the specific data source.

  4. Click the Transaction tab.

  5. Select Set XA Transaction Timeout.

  6. In the XA Transaction Timeout field, specify the value of the transaction timeout.

  7. Click Save.

  8. Log into SQL*Plus.

  9. Set the distributed_lock_timeout value.

    SQL> alter system set distributed_lock_timeout=value scope=spfile;
    

    Oracle recommends that you set distributed_lock_timeout to a value greater than or equal to that set in Step 6.

  10. Shut down and restart your database after running this command.

  11. Verify that the setting has changed.

    SQL> show parameter distributed_lock_timeout;
    
  12. Set this parameter to the same value for all instances in an Oracle Real Application Cluster.


Handling Business and Remote Faults in the Calling BPEL Processes


Bug: 8578316
Updated: 6-May-2011
Platform: All

Oracle recommends that you handle both business and remote faults in BPEL processes during design time. If remote exceptions are not handled in the calling BPEL process, you can see discrepancies in the overall SOA composite application instance state and the server component instance states associated with the composite. For example, assume the composite instance is in a faulted state, while the service component instances are in a completed state. If the caller handles the remote exceptions, then the states of composite and component instances are accurate.


Storing Artifacts in Source Control and Deploying Them with the ant Utility


Bug: 8599824
Updated: 6-May-2011
Platform: All

If you store application artifacts in a source control system that you later want to reuse for deployment with ant, the following changes are required if the application has metadata service (MDS)-based references.

Assume the original Oracle JDeveloper application has file-based MDS references, such as the following:

<metadata-store-usage id="mstore-usage_1"> 
            <metadata-store 
class-name="oracle.mds.persistence.stores.file.FileMetadataStore">
              <property value="${oracle.home}/integration" 
                        name="metadata-path"/>   
              <property value="seed" name="partition-name"/> 
            </metadata-store> 

Modify this code to use database-based MDS references in the Application_Directory/.adf/META-INF/adf-config.xml file, as shown below:

<metadata-store-usage id="mstore-usage_1"> 
            <metadata-store 
class-name="oracle.mds.persistence.stores.db.DBMetadataStore"> 
              <property name="jdbc-userid" value="${mdsuser}"/> 
 <property name="jdbc-password" value="${mdspassword}"/> 
              <property name="jdbc-url" 
value="jdbc:oracle:thin:@${db.host.name}:${db.host.port}:${db.sid}"/> 
               <property name="partition-name" value="soa-infra"/> 
            </metadata-store> 

Check the modified application with these adf-config.xml entries into a source control system. The following concrete example of a modified adf-config.xml file is provided.

 <metadata-store-usage id="mstore-usage_1"> 
            <metadata-store 
class-name="oracle.mds.persistence.stores.db.DBMetadataStore"> 
              <property name="jdbc-userid" value="soainfra_mds"/> 
              <property name="jdbc-password" value="soainfra_mds"/> 
              <property name="jdbc-url" 
value="jdbc:oracle:thin:@myhost56.us.oracle.com:15739:db2825"/> 
              <property name="partition-name" value="soa-infra"/> 
            </metadata-store> 

You can use a variable for the user ID and password and replace the values prior to ant deployment in the application.

If the MDS database has a JNDI name, then use the following entries in adf-config.xml:

<metadata-store 
  class-name="oracle.mds.persistence.stores.db.DBMetadataStore"> 
     <property name="jndi-datasource" value="${db.jndi.name}"/> 
     <property name="partition-name" value="soa-infra"/> 
</metadata-store> 

XML_DOCUMENT_REF Table is Not Purged When the Looped or Parallel Purge Script is Run in an Upgraded 11.1.1.5 Oracle SOA Sute Environment


Bug: 11797953
Updated: 6-May-2011
Platform: All

When you run the looped or parallel purge script in an Oracle SOA Suite 11.1.1.5 environment that was upgraded from 11.1.1.3, the XML_DOCUMENT_REF table is not purged.

For example, assume you perform the following steps:

  1. Upgrade an 11.1.1.3 Oracle SOA Suite environment with initiated instances to version 11.1.1.5 and create additional instances of all SOA composite applications.
  2. Run the following scripts in your 11.1.1.5 environment:
    • soa_purge_scripts.sql
    • common/debug_on.sql
  3. Check the records in the XML_DOCUMENT_REF table.
  4. Run the looped or parallel purge script and recheck the XML_DOCUMENT_REF table.
  5. Note that the XML_DOCUMENT_REF table has not been purged.

Workaround: You can use a DELETE or TRUNCATE SQL query to remove records from this table only after running the looped or parallel purge script.


SOA Composites Do Not Deploy for an SSL-enabled Database on Windows


Bug: 11060696
Updated: 6-May-2011
Platform: Windows

When SSL is configured between the database and Oracle Fusion Middleware on Windows, SOA composite applications do not deploy to the SOA Server. This issue only occurs on Windows; composites deploy correctly on Linux.


Google Chrome Browser Limitation on Displaying XML


Bug: 11897467
Updated: 6-May-2011
Platform: All

Consider the following:

  1. At the top of the home page for a SOA composite application, click the Show WSDL and endpoint URI icon. The Service Endpoint and WSDL dialog displays with links for the endpoint and WSDL.
  2. Click the WSDL link. Instead of the WSDL file contents being displayed, only a link is displayed.

Workaround: Right-click and select View Page Source to display the WSDL. Alternatively you can install a plug-in to see XML in the Google Chrome browser.


Cannot Undeploy All Composites at the Partition Level with the Undeploy SOA Composite Wizard in SSO-enabled Environments


Bug: 11825391
Updated: 6-May-2011
Platform: All

You cannot undeploy all composites at the partition level with the Undeploy SOA Composite wizard in Oracle Enterprise Manager Fusion Middleware Control in SSO-enabled environments. You can only undeploy a single composite at a time with this wizard.

Workaround: Perform the following steps:

  1. Delete the partition and create a new one.
  2. Go to the SOA composite application home pages for each composite
  3. and undeploy each composite one-by-one.

Message Schema in UTF-16 Encoding Can Cause a Runtime Exception


Bug: 10178726
Updated: 6-May-2011
Platform: All

You may encounter the following runtime parsing error if a message schema is encoded in UTF-16.

Unable to parse schema <name>.xsd

To resolve this error, change the schema encoding to UTF-8. In Source view in Oracle JDeveloper, set the encoding declaration in the XML prologue to encoding='UTF-8' for the message schema.


Maximum Heap Memory Size Recommendations on Windows 2008 Server


Bug: 12377414
Updated: 29-April-2011
Platform: Windows 2008 Server

If you are running Oracle SOA Suite on a 64-bit Windows Server 2008 host, setting the heap memory size to 2G in the DOMAIN_HOME\bin\setSOADomainEnv.cmd file causes the server to crash.

Workaround: Set the heap memory size to 1.5G. For example:

-Xmx:1536M –Xms:1536M –Xgc:genpar

where -Xmx is the maximum heap memory size.

Google Chrome Browser Limitations with SOA User Interface Tools


Bug: 12347025
Updated: 29-April-2011
Platform: All

The Google Chrome Browser is not supported for use with the following user interface tools:
  • Oracle BPM Worklist - Approval Management extension (AMX) history graphs do not properly display.
  • Oracle B2B user interface - B2B metadata fails to be imported.
  • Oracle Enterprise Manager Fusion Middleware Control - BPEL 2.0 onAlarm and sequence activities do not display in the flow diagram. Also, multiple nested loops do not properly display in the flow diagram. In addition, if you click an activity in the flow diagram and then click Copy details to Clipboard, an error message is displayed.
  • Oracle SOA Composer

Removing Extra Set Text Dialog Characters


Bug: 9062901
Updated: 29-April-2011
Platform: All

Adding amp; to the Text field of the Edit Text dialog in Oracle JDeveloper adds extra characters to the XSL file. For example, perform the following steps:

  1. In the XSLT Mapper, right-click a string element in the target pane.

  2. Select Set Text > Enter Text.

  3. In the Edit Text dialog, enter &amp; in the Text field, and click OK.

  4. Go to the Source view of the XSL file, and see that an extra amp; is appended.

    <xsl:text disable-output-escaping="no">&amp;amp;</xsl:text>
    

Workaround: In Source view of the XSL file, remove the extra character amp; that was appended in the previous steps. The source view now looks as follows:

<xsl:text disable-output-escaping="no">&amp;</xsl:text>

Composites with Large While Loop Cases Cause Time Outs and Memory Errors


Bug: 9477914
Updated: 29-April-2011
Platform: All

If your SOA composite application includes large while loop cases, you can receive time outs and out-of-memory errors due to large numbers of audit events accumulating. To support these environments, you can decouple the audit trail from the BPEL process service engine transaction by tuning the following properties at the BPEL process service engine level:

  • auditFlushEventThreshold: Controls how often the service engine flushes the audit events. When the audit event limit is reached, the service engine triggers a store call. Tune this size based on the application. The default value is 300 audit events.

  • auditFlushByteThreshold: Controls the approximate size of the batch. After each event, the size is calculated, including the details size. If the sum of the batch byte size exceeds the value of this property, a flush is triggered. The default value is 2 MB.

To set this property at the BPEL process service engine level:

  1. Right-click soa-infra and select SOA Administration > BPEL Properties.

  2. Click More BPEL Configuration Properties.

  3. Click the properties described above.

  4. In the Value field, specify an appropriate value and click Apply.

Note: These properties only impact the BPEL process audit trail. Human workflow, business rules, and Oracle Mediator are not affected by these settings.

Extra Business Event with Oracle Database 11.2.0.1 and One and Only One Level


Bug: 9558493
Updated: 29-April-2011
Platform: All

If you subscribe to a business event with Oracle Mediator, select a consistency level of one and only one, and use a release 11.2.0.1 Oracle database for the SOA Infrastructure schema, the first event published produces two business events.

For example, if 20 messages are published, the subscriber receives 21 messages.

This issue occurs only with release 11.2.0.1 of the Oracle database and only one time after a restart of both the SOA Infrastructure database and the SOA Server. After that, the correct number of business events are inserted.

Inconsistent States for SOA Composite Application Instances in Recovery


Bug: 9574804
Updated: 29-April-2011
Platform: All

When a SOA composite application instance is being recovered, callback messages and activities are displayed as Running, but invocation messages are displayed as Faulted in the State column of the Dashboard tab of a SOA composite application.

SOAP 1.2 <stackTrace> Fault Element is Not Returned to the Caller


Bug: 9528496
Updated: 29-April-2011
Platform: All

A fault from a SOAP 1.2 Web service contains a <stackTrace> element as part of the <exception> element. The <stackTrace> element provides debug information and assistance in understanding a fault. If you invoke a Web service directly from a client and a fault occurs, the <stackTrace> element is provided.

However, if a SOA composite application invokes a Web service (for example, through a BPEL process or Oracle Mediator) and a fault occurs, the <stackTrace> element is not passed back to the caller.

This is the expected behavior.

Composite State Not Updated After BPEL Recovery Of Faulted Instance


Bug: 9035478
Updated: 29-April-2011
Platform: All

The state of a failed SOA composite application instance is not updated after you successfully perform a recovery from the Recovery page of the BPEL service engine. For example, assume you perform the following steps.

  1. Enable payload validation on the SOA Infrastructure Common Properties page in Oracle Enterprise Manager Fusion Middleware Control Console.

  2. Invoke an instance of a SOA composite application. If payload validation fails (for example, because required elements in the schema are missing), a failure occurs at the BPEL service component level during execution of an invoke activity.

    The instance is displayed as faulted in the Dashboard and Instances pages of the composite.

  3. Go to the Recovery page of the BPEL service engine and note that the same instance is pending recovery.

  4. Disable payload validation on the SOA Infrastructure Common Properties page.

  5. From the Recovery page of the BPEL service engine, select the instance and click Recover. This recovers the instance.

  6. View the completed instance in the flow trace. However, note that the instance state is not updated and is still shown as faulted, whereas the instance has actually recovered and completed successfully.

    This is the expected behavior. BPEL recovery created a new BPEL instance, which completed successfully. However, the previous BPEL instance (the one that failed schema validation) is still shown as faulted. The overall composite instance is counted as faulted, since one of its two component instances (the previous BPEL instance) is faulted.

Purge Scripts Do Not Delete Spring Component Rows in Nonproduction Environments


Bug: 10638072
Updated: 29-April-2011
Platform: All

In nonproduction environments (for example, when selecting Development from the Audit Level list on the SOA Infrastructure Common Properties page in Oracle Enterprise Manager Fusion Middleware Control Console), the purge scripts do not delete rows related to the spring service component from the following database tables:

  • xml_document

  • instance_payload

  • component_instance

For information about the purge scripts, see Chapter "Managing Database Growth" of Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle BPM Suite.

WSDL Interface and EJB Version 2 are Not Supported During Runtime


Bug: 10266818
Updated: 29-April-2011
Platform: All

The Create EJB Service dialog enables you to select the following combination:

  • The WSDL radio button selection in the Interface section.

  • The EJB2 selection from the Version dropdown list.

This combination is not supported during runtime.

Composite Instance is Flagged as Faulted Even After Fault is Caught


Bug: 9941332
Updated: 29-April-2011
Platform: All

After manually recovering a fault, a composite instance state in Oracle Enterprise Manager Fusion Middleware Control Console can still display as faulted. For example, assume you perform the following steps:

  1. Deploy a SOA composite application.

  2. Test the web service from the Test Page in Oracle Enterprise Manager Fusion Middleware Control Console by deliberately passing a float value for an input string.

    A fault is correctly generated and the fault policy is applied. The composite instance is in a state requiring recovery.

  3. Recover the fault by modifying the payload and passing an integer value for input.

    The composite instance state changes to faulted.

  4. Check the flow trace and it shows that the fault has actually recovered.

The instance tracking infrastructure does not maintain the relationship of upstream and downstream components. When an upstream component recovers from the recovery required state and a downstream component is in the faulted state, the faulted state cannot be reset; only the recovery required state is reset by the component of the recovery required instance. The downstream component of the faulted instance does not know that the message is replayed; therefore, the composite instance is not reset from the faulted state.

Manual Recovery of Wait and OnAlarm Branch of Pick Activities Is Unsupported


Bug: 9578082
Updated: 29-April-2011
Platform: All

You cannot manually recover wait activities or the OnAlarm branch of pick activities from the Recovery tab of the BPEL process service engine in Oracle Enterprise Manager Fusion Middleware Control Console. There is nothing restricting you from retrieving these pending activities and then attempting a recovery. However, recovery is not successful.

Instead, these pending activities are automatically scheduled and retried by the BPEL process service engine as part of the daily auto recovery or by restarting the SOA server. You can also click the Refresh Alarm Table button on the Recovery page of the BPEL process service engine to resynchronize the pending jobs.

Faulted Instances Waiting for Manual Recovery are Shown as Running


Bug: 9474574
Updated: 29-April-2011
Platform: All

Faulted instances that are waiting for manual recovery are shown when you search for running instances. For example, if you go to the Instances page of the SOA composite application and specify a search criteria to find running instances, the faulted instances waiting for manual recovery are shown.

Composites Calling Other Composites with Concrete WSDL Files


Bug: 9585631
Updated: 29-April-2011
Platform: All

If you use concrete WSDL files, be aware that the order of startup for SOA composite applications is not guaranteed.

For example, if one SOA composite application calls a second SOA composite application with a concrete WSDL file, and the first SOA composite application gets started before the second SOA composite application, an error occurs. This is because the first SOA composite application cannot load the second SOA composite application's WSDL file.

Transactional Adapter Status Displays as Complete Even If Rollback Occurs


Bug: 9298953
Updated: 29-April-2011
Platform: All

If a transaction rollback occurs because of a business fault or exception, the instance trial for a transactional adapter does not indicate whether or not there was a rollback.

For example, assume you have an asynchronous BPEL process invoking a database adapter service. An assert expression is defined in the invoke activity. If the assert expression returns false, then all transactional invocations should roll back. However, the flow trace shows a status of completed for the database adapter service.

Accessing Components from SSO-Enabled Oracle Enterprise Manager


Bug: 8498628
Updated: 29-April-2011
Platform: All

If you log in to an SSO-enabled Oracle Enterprise Manager Fusion Middleware Control Console and click the links to the following components, you are directed to non-SSO URLs for these components, and prompted to log in again.

  • Oracle BPM Worklist

  • Oracle B2B

  • Oracle BAM

  • SOA Composer

Failure to Add and Update WSDL Binding After Migration


Bug: 9012064
Updated: 29-April-2011
Platform: All

When you open Oracle JDeveloper and attempt to migrate a 10.1.3 application that includes WSIF binding information to version 11g, migration creates a web service reference with no WSDL binding information (binding.wsif) in the composite.xml file. When you then attempt to update the reference with the same WSDL in Oracle JDeveloper, the binding information is not saved, and you receive a compilation error.

This is because Oracle JDeveloper is handling the typical migration use case in which the reference is updated with a new WSDL location (same WSDL, but in a different location). Therefore, when you do not change the WSDL location, nothing happens.

Workaround: Perform either of the following steps:

  1. Delete the reference and create a new one using the same WSDL.

  2. (Easiest) Copy the WSDL to a different file name, but do not change its contents. Then, update the reference using this WSDL copy. This changes the location of the WSDL and correctly creates the binding.ws.

Understanding BPEL Global Transaction and Adapter Local Transaction Issues


Bug: 8476752
Updated: 29-April-2011
Platform: All

BPEL processes run in global transactions, while other Oracle SOA Suite components, such as adapters, run in local transactions. This can cause inconsistencies with the information displayed in Oracle Enterprise Manager Fusion Middleware Control Console.

For example, assume you have a main synchronous BPEL process that invokes an asynchronous BPEL process. There is one database adapter insert in the main synchronous BPEL process before the invocation of the asynchronous BPEL process. There is a second database adapter insert in the asynchronous BPEL process, at which point a fault is expected to be thrown.

The expected behavior is as follows:

  • An initial insert into the database is performed from the main process that completes successfully as expected.

  • The second insert also executes in the asynchronous process, but after encountering the fault, the BPEL process rolls back the initial insert.

However, in Oracle Enterprise Manager Fusion Middleware Control Console, the second database insert also shows as having completed successfully, instead of the having faulted.

This is because the database adapter invocation is logged (instance tracked) in a local transaction that is not part of the global BPEL JTA transaction. Therefore, the database adapter invocation completes successfully, but the subsequent BPEL process incurs a global rollback.

<invoke name="Invoke_1" inputVariable="Invoke_1_insert_InputVariable" 
   partnerLink="db" portType="ns1:db_ptt" operation="insert"/> 
. . .
. . .
   <throw name="Throw_2" faultName="bpelx:rollback"/>

At that point, instance tracking has already recorded the outbound invocation as successful (in a local transaction). If the adapter throws an exception, instance tracking logs this as a fault. Also note that some partner links may invoke a file adapter, which cannot be rolled back, even if the BPEL process later throws a bpelx:rollback.

Descriptions for Data Source JNDI Fields are Interchanged


Bug: 8399320
Updated: 29-April-2011
Platform: All

In the SOA Infrastructure Common Properties page of Oracle Enterprise Manager Fusion Middleware Control Console, the descriptions for Server Data Source JNDI and Server Transaction Data Source JNDI are interchanged. However, the Configure links go to the correct locations.

Granting the Same Role to the Same User Twice Causes Unclear WLST Message


Bug: 8454184
Updated: 29-April-2011
Platform: All

  1. Create a domain with Oracle WebCache and extend it with Oracle SOA Suite.

  2. Associate the Oracle WebCache application with LDAP and grant the admin role to a user (for example, user name test) in Oracle Internet Directory using the WebLogic Scripting Tool (WLST).

  3. Grant the same role (admin role) to the same user again (test).

    You expect to see a WLST error message such as the following:

    This particular user already has admin role to access your application
    

    Instead, you receive the following message, which is inaccurate:

    Command FAILED, Reason: Cannot add principal to application role
    

Flow Trace Fails to Load with Numerous Correlated Composite Instances


Bug: 10077813
Updated: 29-April-2011
Platform: All

The flow trace in Oracle Enterprise Manager Fusion Middleware Control Console can fail to load in scenarios in which you have numerous correlated composite instances (for example, 100). This is because multiple midprocess receive activities result in separate ECIDs. Creating a consolidated audit trail involves sending separate requests for each ECID (for example, 100 separate queries for audit trails).

Workaround: Perform the following steps to increase the transaction timeout parameter.

  1. Open the fabric-ejb.jar file.

  2. Within this JAR file, open the weblogic-ejb-jar.xml file.

  3. Set the transaction timeout parameter to a higher value.

Back to top


Technology Adapters


 

Updating Required JAR List When Accessing IBM MQ SERVER 7.0 with SOA JMS Adapter


Bug: 12349381
Added: 01-May-2011
Platform: All

You must use the following required jar list when you use JMSadapter with MQ version 7.x.

  • Non-XA Data Sources
    • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mq.jar
    • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mq.jmqi.jar
    • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mqjms.jar
    • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/dhbcore.jar
  • XA Data Sources
    • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mq.jar
    • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mq.jmqi.jar
    • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mqjms.jar
    • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/dhbcore.jar
    • /<YOUR-MQSERIES-INSTALL-LOCATION>/java/lib/com.ibm.mqetclient.jar

See the "Configuring Oracle JMS Adapter with IBM WebSphere MQ JMS" section in the Oracle Fusion Middleware User's Guide for Technology Adapters for more information.


Managed Connection Factory Name Has to Be Modified in Case of Migrated AQ Adapter Composites


Bug: 12369977
Added: 01-May-2011
Platform: All

If you have migrated AQ Adapter projects from Release 10.1.3.x to Release 11g, to use AQadapter in non-managed mode, you need to manually update the managed connection factory from <non-managed-connection managedConnectionFactoryClassName= "oracle.tip.adapter.aq.AQManagedConnectionFactory"> to <non-managed-connection managedConnectionFactoryClassName= "oracle.tip.adapter.aq.v2.jca.AQManagedConnectionFactory">. Note that the non-managed mode is not recommended and is not supported in a production environment.


WAS:SetmanagedConnection() Fails with IllegalStatementException for AQ Adapter


Bug: 10414974
Added: 01-May-2011
Platform: All

While running Oracle AQ adapter cases on the IBM WebSphere Application Server, you might encounter the following error:
javax.resource.spi.ResourceAllocationException:
setManagedConnection: illegal state exception. State = STATE_ACTIVE_FREE MCW = 28392839


Malfunction of Request/Reply Operation Under Small Load


Bug: 12397296
Added: 01-May-2011
Platform: All

Adapters (AQ,JMS and MQ) request reply case fails to correlate if many messages are processed in an outbound request reply case simultaneously.

Back to top


Adapter for Oracle Applications (Oracle E-Business Suite Adapter)


No issue has been discovered at the time of this release. As additional issues and workarounds are discovered after the release, they will be listed here.

For known issues and workarounds for earlier releases, see Known Issues for Oracle SOA Products and AIA Foundation Pack.

Back to top


Application Adapters for WebLogic Server


Missing Libraries in setDomainEnv Causes Application Adapters AE to Fail

Bug: 13929048
Added: 08-June-2012
Platform: All

This problem affects every release the adapters are certified for: 11.1.1.4.0, 11.1.1.5.0, and 11.1.1.6.0.

The following two libraries are missing when starting the starting the design tool for the Application Adapters WLS (Application Explorer) after installation:

  1. $MWH/Oracle_SOA1/soa/modules/oracle.soa.adapter_11.1.1/jca-binding-api.jar
  2. $MWH/Oracle_SOA1/soa/modules/oracle.soa.adapter_11.1.1/adapter_xbeans.jar

In the Oracle Fusion Middleware Application Adapters Installation Guide for Oracle WebLogic Server, section 2.3.1 Starting Application Explorer, the guide states that users must run the setDomainEnv.sh to set the environment accordingly. The two libraries need to be added to the setDomainEnv scripts to avoid class loading exceptions.

The following exceptions may occur when using the Application Explorer to generate EIS adapter artifacts:

20120405-11:51:04 INFO com.ibi.bse.gui.BseFrame:read manifest for iwae.jar
20120405-12:12:30 ERROR
com.ibi.bse.ConfigWorker:java.lang.NoClassDefFoundError:
oracle/tip/adapter/api/exception/PCResourceException
at
com.ibi.afjca.cci.IWAFConnection.createInteraction(IWAFConnection.java:81)
at
com.iwaysoftware.iwae.common.JCATransport.initJCA(JCATransport.java:100)
at
com.iwaysoftware.iwae.common.JCATransport.<init>(JCATransport.java:87)
at
com.iwaysoftware.iwae.common.AdapterClient.<init>(AdapterClient.java:85)
at com.ibi.bse.ConfigWorker.run(ConfigWorker.java:41)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.ClassNotFoundException:
oracle.tip.adapter.api.exception.PCResourceException
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
... 6 more

Exception occurred during event dispatching:

java.lang.NoClassDefFoundError:
oracle/integration/platform/blocks/adapter/fw/metadata/AdapterConfigDocument$Factory
at
com.iwaysoftware.af.container.tools.wsdl.oracle.InboundWSDLGenerator.get11g_jca
at
com.iwaysoftware.af.container.tools.wsdl.oracle.IWayWSILBrowser.writeFiles
(IWayWSILBrowser.java:137)
at
com.iwaysoftware.af.container.tools.wsdl.oracle.IWayWSILBrowser.generateIWayWSDL
(IWayWSILBrowser.java:132)
at
com.iwaysoftware.af.container.OracleAEManager.generateWSDL
(OracleAEManager.java:83)
at
com.iwaysoftware.af.container.OracleAEManager.generateWSDL
(OracleAEManager.java:64)
at
com.iwaysoftware.af.container.ae.AEComponentMessage.buildEXPORTWSDL
(AEComponentMessage.java:185)
at
com.iwaysoftware.af.container.ae.AEComponentMessage.build
(AEComponentMessage.java:89)
at
com.iwaysoftware.af.container.ae.AEComponentMessage.<init>(AEComponentMessage.java:61)
at
com.iwaysoftware.af.container.AEManager.dispatch(AEManager.java:134)
at
com.iwaysoftware.af.container.IWAFContainer.dispatchAERequest
(IWAFContainer.java:876)
at
com.ibi.afjca.cci.IWAFInteraction.execIWAE(IWAFInteraction.java:286)
at
com.ibi.afjca.cci.IWAFInteraction.exec(IWAFInteraction.java:182)
at
com.ibi.afjca.cci.IWAFInteraction.execute(IWAFInteraction.java:107)
at
com.iwaysoftware.iwae.common.JCATransport.execute(JCATransport.java:166)
at
com.iwaysoftware.iwae.common.AdapterClient.generateWSDL(AdapterClient.java:437)
at
com.ibi.bse.gui.ExportWSDLDialog.saveWSDL(ExportWSDLDialog.java:590)
at
com.ibi.bse.gui.ExportWSDLDialog.okButtonActionPerformed(ExportWSDLDialog.java:476)
at
com.ibi.bse.gui.ExportWSDLDialog.access$000(ExportWSDLDialog.java:36)
at
com.ibi.bse.gui.ExportWSDLDialog$2.actionPerformed(ExportWSDLDialog.java:417)
at
javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at
javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at
javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at
javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at
javax.swing.plaf.basic.BasicButtonListener.mouseReleased
(BasicButtonListener.java:236)
at java.awt.Component.processMouseEvent(Component.java:6267)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
at java.awt.Component.processEvent(Component.java:6032)
at java.awt.Container.processEvent(Container.java:2041)
at java.awt.Component.dispatchEventImpl(Component.java:4630)
at java.awt.Container.dispatchEventImpl(Container.java:2099)
at java.awt.Component.dispatchEvent(Component.java:4460)
at
java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
at
java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
at
java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
at java.awt.Container.dispatchEventImpl(Container.java:2085)
at java.awt.Window.dispatchEventImpl(Window.java:2478)
at java.awt.Component.dispatchEvent(Component.java:4460)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:178)
at java.awt.Dialog$1.run(Dialog.java:1046)
at java.awt.Dialog$3.run(Dialog.java:1098)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Dialog.show(Dialog.java:1096)
at
com.ibi.bse.ComponentNodeData.actionPerformed(ComponentNodeData.java:406)
at
javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at
javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at
javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at
javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at javax.swing.AbstractButton.doClick(AbstractButton.java:357)
at
javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1223)
at
javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased
(BasicMenuItemUI.java:1264)
at java.awt.Component.processMouseEvent(Component.java:6267)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
at java.awt.Component.processEvent(Component.java:6032)
at java.awt.Container.processEvent(Container.java:2041)
at java.awt.Component.dispatchEventImpl(Component.java:4630)
at java.awt.Container.dispatchEventImpl(Container.java:2099)
at java.awt.Component.dispatchEvent(Component.java:4460)
at
java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
at
java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
at
java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
at java.awt.Container.dispatchEventImpl(Container.java:2085)
at java.awt.Window.dispatchEventImpl(Window.java:2478)
at java.awt.Component.dispatchEvent(Component.java:4460)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.lang.ClassNotFoundException:
oracle.integration.platform.blocks.adapter.fw.metadata.
AdapterConfigDocument$Factory
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
... 73 more

The exceptions are related to missing libraries in the classpath when starting the Application Explorer.

The following libraries must be added to the classpath via the setDomainEnv script prior starting the Application Explorer:

  • • jca-binding-api.jar
  • • adapter_xbeans.jar

Workaround: The installation guide will be updated in a future release.


Back to top


Application Server Legacy Adapters


No issue has been discovered at the time of this release. As additional issues and workarounds are discovered after the release, they will be listed here.

For known issues and workarounds for earlier releases, see Known Issues for Oracle SOA Products and AIA Foundation Pack.

Back to top


BPEL Process Manager


Oracle BPEL Process Manager 2.0 Limitations


Bug: 9735542
Added: 01-May-2011
Platform: All

The following BPEL 2.0 features are not implemented in Oracle BPEL Process Manager:

  • Termination handlers

  • Message exchanges

  • Fault handlers and termination handlers in an invoke activity.
    Note: This is the same as the BPEL 1.1 implementation of Oracle BPEL Process Manager.
    The workaround for this issue is to include the invoke activity in a scope activity.

  • Atomic assign activities. If an error occurs in the middle of an assign activity, all the changes roll back. This is the same as the BPEL 1.1 implementation of Oracle BPEL Process Manager.


Checkpoint Activity Wrongly Appears in Oracle BPEL Designer Context Menu


Bug: 10229577
Added: 01-May-2011
Platform: All

If you right-click inside your BPEL process in Oracle BPEL Designer and select Insert Into > Activities, note that checkpoint is incorrectly displayed in the list of activities. This activity is not supported, and selecting it does not insert it into the BPEL process.

The checkpoint activity has been replaced by the dehydrate activity, which is also available for selection in the same context menu.


Second XSD Created for API-Created, PL/SQL Partner Links with Complex Parameters


Bug: 10246232
Added: 01-May-2011
Platform: All

If you create a PL/SQL partner link with complex parameters from the API, a new XSD file is generated. If you then open the partner link in Oracle JDeveloper and make no modifications other than completing the flow and clicking the Apply button in the Edit Partner Link dialog, a second XSD file is also created.

Workaround: You must use the second XSD file.


Audit Trail Details Display in Server Language Instead of Browser Language


Bug: 9298375
Added: 01-May-2011
Platform: All

Audit trail information for a BPEL instance displays in the language of your server instead of the language of your web browser.


Do Not Specify the wsa and bpel Property Prefixes with the bpelx:property


Bug: 9124369
Added: 01-May-2011
Platform: All

Tables H-1 and H-2 of Appendix H, "Normalized Message Properties" of the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite describe the Oracle BPEL Process Manager and Oracle Web Services Addressing properties.To use these properties correctly with the bpelx:property in activities such as a receive activity, ensure that you do not include the wsa. or bpel. prefixes. For example:

<receive name="receiveInput" partnerLink="bpelprocessb_client"
portType="client:BPELProcessB" operation="process" variable="inputVariable"
 createInstance="yes">
           <bpelx:property name="action" variable="v1"/>
           <bpelx:property name="messageId" variable="v2"/>
           <bpelx:property name="relatesTo" variable="v3"/>
           <bpelx:property name="replyToAddress" variable="v4"/>
           <bpelx:property name="replyToPortType" variable="v5"/>
           <bpelx:property name="replyToService" variable="v6"/> 
</receive>

Selecting the Key for an Entity Variable in the Browse Entity Variable Dialog


Bug: 9066090
Added: 01-May-2011
Platform: All

When selecting the local part of an entity key by browsing entity variables, entity icons display in the expanded element tree. These icons are identified by a blue x inside parentheses, and indicate which elements include entity keys. Selecting these elements does not update the Key Local Part or Key Namespace URI fields in the Specify Key dialog. Instead, you must expand these elements to select the actual key to get the key's local part and namespace. For example:

  1. In the Bind Entity dialog, click the Add icon to invoke the Specify Key dialog.

  2. To the right of the Key Local Part field, click the Browse Entity Variable icon.

  3. Note that a blue x inside parentheses indicates which elements include entity keys. Do not select these elements.

  4. Expand these elements to display the entity keys available for selection.

  5. Select an entity key, and click OK.

    The Key Local Part and Key Namespace URI fields of the Specify Key dialog are populated with information about your selection.


MIME Type for Voice Notification in BPEL Voice Activity Requires Modification


Bug: 9023004
Added: 01-May-2011
Platform: All

In a BPEL voice activity, the MIME type for message content generated in the source code is in text/vxml format. However, the message sent from the composite to the voice XML driver must be in text/plain format. This is because the voice XML driver adds the voice XML wrapper to the message before sending it to the destination point.

If the message content sent to the driver is in text/vxml format for the MIME type, a message delivery failure occurs.

Workaround: Manually change the MIME type for the voice payload content to be text/plain in Source mode in Oracle JDeveloper.

<scope name="VoiceApproval">
. . .
. . .
   <copy>
      <from expression="string('text/plain')"/>
      <to variable="varNotificationReq" part="VoicePayload"
      query="/VoicePayload/ns1:Content/ns1:MimeType"/>
   </copy> 
. . .
. . .
</scope>

Client Java API Is Not Backward Compatible


Bug: 8554297
Added: 01-May-2011
Platform: All

Custom applications coded with the Oracle BPEL Process Manager 10.1.3 Client Java API cannot currently be upgraded to the 11g Release 1 (11.1.1.3, 11.1.1.4, and 11.1.1.5) Client Java API. Programs coded to the Oracle BPEL Process Manager 10.1.3 API must be rewritten. In addition, the current API is not compatible with the versions of the 11g Release 1 11.1.1.1 and 11.1.1.2 API, although the differences are minimal.

The version of the API in 11g Release 1 11.1.1.3 has been finalized. It has been fully supported since that release and is backward compatible from that release onwards.

Visit the following URL for details:

http://www.oracle.com/technology/products/soa/bpel/collateral/documentation.html

Back to top


Business Activity Monitoring


No issue has been discovered at the time of this release. As additional issues and workarounds are discovered after the release, they will be listed here.

For known issues and workarounds for earlier releases, see Known Issues for Oracle SOA Products and AIA Foundation Pack.

Back to top


Business Process Analysis Suite


No issue has been discovered at the time of this release. As additional issues and workarounds are discovered after the release, they will be listed here.

For known issues and workarounds for earlier releases, see Known Issues for Oracle SOA Products and AIA Foundation Pack.

Back to top


Business Process Management


 

Incomplete sentence in online help for Oracle BPM Workspace and Oracle BPM Process Spaces


Bug: 10194052
Updated: 25-May-2011
Platform: All

Online help for Oracle BPM Workspace and Oracle BPM Process Spaces contains an incomplete sentence. The incomplete sentence is located in Sample 1 of the section "Creating Custom ADF Applications with Oracle Business Process Management Workspace Task Flows". The sentence now reads, "Select HTTP Basic Authentication as shown in". It should read "Select HTTP Basic Authentication as shown in Figure: Selecting HTTP Basic Authentication," in which the words "Figure: Selecting HTTP Basic Authentication" are linked to the graphic that immediately follows.

 

BPM Workspace dashboard interface does not display languages zh-cn or zh-tw as specified in browser


Bug: 12405605
Updated: 23-May-2011
Platform: All

If you are using dashboards in Oracle BPM Workspace, and your browser is set to display in either zh-CN (Simplified Chinese) or zn-TW (Traditional Chinese), then the LOV (list of values) of the dashboard interface will display in neither. Instead, that LOV will display whatever language is specified for the server locale.


Using the Translation Option When Specifying the Title of a Human Task


 

Bug: 11822702
Added: 01-May-2011
Platform: All

When specifying the title of a human task, in addition to specifying Plain Text and Text and XPath, you can also specify Translation. This latter option enables you to localize the task title to a user's locale. For example, a user in the United States can see the task title in American English, while another user in Germany can see the same title in German.

Select a key in the resource bundle and specify the parameters for various placeholders in the message. For example if the message is Expense report {1}, then specify the parameters as xpath.


In Upgraded Task Details, Reassign Action Completes but Throws an Error


Bug: 12347043
Added: 01-May-2011
Platform: All

In task details upgraded from earlier release, when executing the Reassign action, an error says "Request Failed". Actually, the reassign completes. When you click on the OK button again, a popup says the task is already assigned.

Workaround: Upgrade your taskflow applications by opening them in JDev and redeploying the taskform.


Migration Properties Documentation for T2P for Dashboards


Bug: 11832683
Added: 08-April-2011
Platform: All

The T2P Migration document for Dashboards needs to explicitly specify the migration.properties supported for the T2P utility for objectType DASHBOARD.


Refresh Needed to View Process Instance After Invocation from Applications Panel in BPM Process Workspace


Bug: 11060337
Added: 08-February-2011
Platform: All

In BPM Process Workspace, after you invoke a process instance from the Applications panel, the instance does not appear in the Process Instance table in the Process Tracking tab.

Workaround: To view the process instance in the Process Instance table, refresh the browser.


Process Tracking Page Refreshes Continuously


Bug: 11066631
Added: 08-February-2011
Platform: All

At times, in BPM Process Workspace when there are no process instances running, the Process Tracking page refreshes continuously. This is a known issue.


Error Creating a Business Object from an External XSD File


Bug: 11678299
Added: 11-Febrary-2011
Platform: All

Creating a Business Object based on a schema type using a schema type that is not contained in the BPM project, causes a IllegalStateException.

Workaround: The following procedure shows you how to modify a Business Object based on a schema type contained in the project to reference an external schema type:

  1. Create a Business Object based on an XSD type contained in the BPM project.
  2. Close JDeveloper.
  3. Edit the BPM project WSDL file to reference the external XSD:
    1. In the definitions element replace the xmlns:oj value with the namespace of the external type.
    2. In the xsd:import element replace the namespace and location with the values corresponding to the external type.
    3. In the bpmo:binding element replace the type value with the name of the external type.
  4. Save the BPM project WSDL file.
  5. Reopen JDeveloper.

 


Do Not Edit the BPMN Process WSDLs Directly


Bug: 8925528 and 8976614.
Added: 29-April-2011
Platform: All

You must always use the Process Editor to edit a BPMN process. Do not edit the BPMN process WSDLs directly. Doing so does not allow you to save the changes and causes multiple error messages.


Cannot Edit Link Between BPMN Process and Business Rules in composite.xml


Bug: 9113859
Added: 29-April-2011
Platform: All

The business rules task is used to incorporate Oracle Business Rules within a BPMN process. You can specify the business rule used as part of the configuration properties for the business rules task.

However, you cannot edit this property in composite.xml. Use the Oracle BPM Studio user interface to edit or remove the reference to the business rule.


Deleting Services or References from the SOA Composite Does Not Delete the Customized Service or Reference


Bug: 9125336
Added: 29-April-2011
Platform: All

When you delete a customized service or a reference from the SOA Composite, Oracle BPM Studio does not delete the customized component from the business catalog. Before building the BPM project you must manually delete the customized component from the business catalog.


The XPath Data Association Editor Does Not Validate Expressions


Bug: 9125830
Added: 29-April-2011
Platform: All

The XPath Data Association Editor does not validate the expressions you use to assign values to arguments and data objects. You must ensure that the XPath expressions you use in an XPath data association are valid. Using invalid XPath expressions causes errors at run time.


Deleting a Reference from the SOA Composite Does Not Remove It from the Human Task Payload Configuration


Bug: 9126659
Added: 29-April-2011
Platform: All

Deleting a reference from the SOA Composite does not delete the reference from the payload of the Human Tasks that use the reference.

After you delete a reference, you must remove the deleted reference from the Human Tasks using it.


Data Associations for Elements of a Collection Are Not Available


Bug: 9165384
Added: 29-April-2011
Platform: All

Data associations for elements of a collection are not available in this release. To assign a value to an element of a collection, use XLS transformations.


Do Not Define Multiple Catch Events for the Same Error or Message


Bug: 9165488
Added: 29-April-2011
Platform: All

Do not define multiple catch events for the same error or message. Only the first catch event fires; the remaining catch events are ignored.


Changes to a Deployed Organizational Unit Not Supported


Bug: 9217073
Added: 29-April-2011
Platform: All

When a BPM Project is deployed, any organizational units that do not exist are created. However, when redeploying a project, if any existing organizational units are changed, the changes will not be updated.

These changes must be made by a business administrator using Oracle BPM Workspace as described in Oracle Fusion Middleware User's Guide for Oracle Business Process Management.


enableAutoClaim Property Is Set to True in Human Tasks Created Using Oracle BPM Suite


Bug: 9222851
Added: 29-April-2011
Platform: All

When you create a Human Task using Oracle BPM Suite, the enableAutoClaim property is set to true by default.


Configuring Data Associations for XML Schema Elements Based on Simple Data Types


Bug: 9223361
Added: 29-April-2011
Platform: All

When configuring data associations for a flow object, you can map simple XML elements based on simple types to compatible basic data objects.


The Initiator Node List Shows the Names of the Possible Initiator Flow Objects


Bug: 9229890
Added: 29-April-2011
Platform: All

In the implementation properties of message events and send and receive tasks, the Initiator Node list shows the name of the initiator flow object. A BPMN process might contain multiple flow objects with the same name. It is a good practice to use a different name for all of the flow objects in the process. Not doing so causes the Initiator Node list to contain multiple items with the same name, making it difficult to identify the one you want to select.


The Pushback Task Operation Is Not Supported in an Aggregation Context


Bug: 9451036
Added: 29-April-2011
Platform: All

The Approval Management pushback task operation is not supported in an aggregation context. Use the request for information task operation instead.


Must Assign Application Roles from the OracleBPMProcessRolesApp Context


Bug: 9474544
Added: 29-April-2011
Platform: All

Using Oracle BPM Studio, you can map the roles defined in your process to application roles defined by Oracle WebLogic Server.

However, you must ensure that the application roles you use are defined as part of the OracleBPMProcessRolesApp application context. Only application roles defined in OracleBPMProcessRolesApp are used at run time.


Adding Counter Marks to Subprocesses Is Not Available


Bug: 9552475
Added: 29-April-2011
Platform: All

Adding counter marks to subprocesses is not available for this release.

The available workaround is to add the counter mark to add an activity immediately after the start event in the subprocess and add a counter mark to this activity.


You Must Manually Remove Additional Slashes from the XSD file When Defining Human Tasks Assignments Based on Business Rules


Bug: 9580664
Added: 29-April-2011
Platform: All

In BPM Suite if you define a human task assignments based on Business Rules, then you must edit the XSD of the decision service to remove the additional slashes from the import statements.

For example, you must replace the following statement:

schemaLocation="oramds:///soa/shared/workflow/TaskEvidenceService.xsd"

with the following import statement:

schemaLocation="oramds:/soa/shared/workflow/TaskEvidenceService.xsd"


The Number of Business Indicators Per Project Is Limited


Bug: 9645599
Added: 29-April-2011
Platform: All

You must not define more than twenty business indicators per project. The average length of the name of the business indicator must be 15 characters.


Oracle BPM Studio Permits Users to Assign Invalid Application Roles to Swimlanes


Bug: 9474544
Added: 29-April-2011
Platform: All

When assigning roles to swimlanes using Oracle BPM Studio, users can assign roles based on application roles that are not part of OracleBPMProcessRolesApp. This causes errors when deploying the Oracle BPM project.

Workaround: You should ensure that the application roles you assign to swim lane roles uses OracleBPMProcessRolesApp only.


Cannot Import a BPEL Process to a BPA Server Multiple Times


Bug: 9726300
Added: 29-April-2011
Platform: All

You can only import a BPEL process to a BPA server one time. After you import a BPEL process to a BPA Server, it is associated to that particular BPA instance.


Starting an Event Subprocess from the BPM Process That Contains It Is Not Supported


Bug: 9785681
Added: 29-April-2011
Platform: All

You cannot start an event subprocess by sending a message event from within the BPM process that contains the event subprocess. Because this release does not support correlations, a process instance cannot send event messages to itself.

If you start an event subprocess by sending a message event from within the BPM process that contains it, then the BPM Engine does not run the event subprocess and it may stop responding.


Sorting the Process Instances in a Guided Business Process by Instance ID Does Not Order Them in Numerical Order


Bug: 9794067
Added: 29-April-2011
Platform: All

Sorting the list of process instances in a guided business process by their ID does not order them in numerical order.

The sorting algorithm used to order process instances in guided business processes does not compare the whole number. It compares the first digit in the number ID.

For example, sorting the following list of process IDs: 1, 2, 3, 5, 11, 12 produces the following result: 1, 11, 12, 20, 3, 5


Timer Start Events That Specify Dates Previous or Equal to the Deployment Date Are Not Triggered


Bug: 10404509
Added: 29-April-2011
Platform: All

The BPM Engine does not trigger timer start events that specify a date previous or equal to the deployment date.


Limitations When Calling a BPMN Process from a Spring Component


Bug: 9840691
Added: 29-April-2011
Platform: All

The following limitations apply when calling a BPMN process from a Spring component:

  • You cannot call a BPMN process from a Spring component that does not declare an interface.
  • You cannot create a Spring component reference based on a BPMN process interface. Currently Oracle BPM Studio does not provide a way to create Java classes based on BPMN process instances.
  • You must name the WSDL used to represent the Java interface of a Spring component with the same name of the Java interface. For example, if the name of the Java interface is SpringInterface.java then the name of the WSDL must be SpringInterface.wsdl.
  • The option Append Suffix in the Update WSDL Interface action is not supported because the name of the WSDL must match the name of the Java interface. If the user selects this option, then BPM Studio shows an error message stating this feature is not enabled.

Patching an SOA Application with Shared Resource Bundles


Bug: 10636799
Added: 29-April-2011
Platform: All

You can patch an SOA application with shared resource bundles so that you can reference resources in a shared location, instead of creating new resource bundles.

To patch an SOA application with shared resource bundles:

  1. Create the java resource bundle files containing key-value pairs of the display fields.
  2. Compile the files and bundle the resource bundle classes into a jar.
    The following example shows a packaging structure:
    resource/oracle/bpel/activityguide/resource/AGResourceBundle.class
    
    resource/oracle/bpel/activityguide/resource/AGResourceBundle_fr.class
  3. Deploy the resource bundle to MDS:
    1. In Oracle JDeveloper, create a new Project deployment profile of archive type Jar.
    2. In the Contributors section, add the resource bundle you created.
    3. Save the profile.
    4. Create a new application deployment profile of archive type SOA Bundle.
    5. In the Contributors section, add the Jar profile you created to this SOA Bundle.

      If required, combine with SOA-SAR profile for combined deployment.

    6. Save the profile.
    7. Deploy the SOA bundle from Oracle JDeveloper to an SOA Server.

      Note: For details on how to deploy a resource bundle to MDS, see "Deploying and Using Shared Metadata Across SOA Composite Applications in Oracle JDeveloper" in Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

  4. In Oracle JDeveloper edit the composite.xml file.
  5. In the Structure window, right click the composite element.
  6. Select Insert Inside Composite.
  7. Select Property.
  8. Set name of the property to oracle.soa.composite.classloader.ext.dir and the value of the property to the package structure of the jar you created.

    The following XML fragment shows how to set the required property:

    <property name="oracle.soa.composite.classloader.ext.dir">
    /apps/resource
    </property>

  9. Localize the display fields of the Guided Business Process in Oracle JDeveloper.
    • Choose External option during translation to indicate that an external resource bundle is used.
    • Provide the fully qualified name of the class in the resource bundle field. For example:

      oracle.bpel.activityguide.resource.AGResourceBundle

Deploy Option Not Available in Approval WorkFlow Browser


Bug: 9197923
Added: 29-April-2011
Platform: All

When you specify an approver who also has deployment permissions, the user will not initially see the deployment option. To be able to deploy the Oracle BPM project, the project must first be approved for deployment using the Oracle BPM WorkSpace application. Once the approval workflow is complete, the option to deploy the project is available.


Chinese, Korean, and Character Input Problems in Flow Object Labels


Bug: 9464997
Added: 29-April-2011
Platform: All

The Adobe Flash Player has a bug related to input for Chinese, Korean, and Japanese characters. This causes problems in Oracle Business Process Composer when editing flow object labels within the process editor.

For more information see: http://bugs.adobe.com/jira/browse/FP-501. To resolve this issue, use Microsoft Internet Explorer version 7.


Initiator Pattern Not Permitted Within a Subprocess


Bug: 10330870
Added: 29-April-2011
Platform: All

You should not use a user task with an initiator pattern within a subprocess. This is currently allowed during design and deployment using Oracle Business Process Composer and Oracle BPM Studio. Oracle BPM WorkSpace will show a link within a running process, but this link is invalid.


Supported Version of Adobe Flash on Linux Systems


Bug: 10198949
Added: 29-April-2011
Platform: All

Some Oracle Business Process Composer user interface elements are not displayed when using Linux.

Workaround: You must install Adobe Flash, version 10.1 or greater.


Text Field Does Not Display Full Value for Participant Names


Bug: 10193619
Added: 29-April-2011
Platform: All

When creating or editing human tasks using Oracle Business Process Composer, the text filed displaying the Value column is not wide enough to display the all the data.

Workaround: You can view the full text by positioning the mouse over the cell to display the tooltip.


Process Workspace Login Error When Using External LDAP Directory


Bug: 10008507
Added: 29-April-2011
Platform: All

If you are using an external LDAP directory, you may receive the following error message when logging in to Process Workspace: "No Role found matching the criteria".

This may occur under the following conditions:

  • You have used Oracle WebLogic Server Console to configure a user base and a group base to search for and authenticate users.
  • The user base or group base has a referral to another user base or group base.

In this case, the Process Workspace identity service does not list the users or groups and, as a result, the login to Process Workspace fails to authenticate the user.

This can occur when there are two bases to be searched, one for users and one for groups, but the UR API is not properly set.

To resolve this, in the Oracle WebLogic Server Console, provide a root-level search base for both users and groups so that referrals are resolved automatically since you are providing a higher node in the search tree.

If this solution degrades performance as a result of a substantially larger search base, you can limit this search by editing specific property in the jps-config.xml located at domain-home/config/fmwconfig/.

The following is an example of an edited jps-config.xmlfile:

jps-config.xml
<extendedProperty>
<name>user.search.bases
<values>
<value>cn=users1,dc=us,dc=oracle,dc=com
<value>cn=users2,dc=us,dc=oracle,dc=com
...........
</values>
</extendedProperty>
<extendedProperty>
<name>group.search.bases
<values>
<value>cn=groups1,dc=us,dc=oracle,dc=com
<value>cn=groups2,dc=us,dc=oracle,dc=com
..................
</values>
</extendedProperty>

Taskflow Links for Undeployed Processes Are Visible in Process Workspace


Bug: 10353724
Added: 29-April-2011
Platform: All

If a project is deployed with its taskflows and then it is undeployed, it remains visible in the Applications panel of Oracle Business Process Management Workspace. To make it no longer visible, clear it from either Oracle Enterprise Manager Fusion Middleware Control Console or the WFTASKDISPLAY table in the SOAINFRA schema.


Oracle WebCenter 11g Patchset 2 with Process Spaces Does Not Work with Process Workspace Patchset 3


Bug: 10163188
Added: 29-April-2011
Platform: All

Both components must be 11g Patchset 3.


When Documentation Server is Down, Launching a Group Space for an Instance Causes Error "Instance 'null' is not available"


Bug: 9502887
Added: 29-April-2011
Platform: All

If you have a Process Spaces group space open and you bring down the documentation service, then, when you launch instance group space for an instance, you see that an instance group space is created. However, when you open the instance group space, you receive the error message "Instance 'null' is not available". This happens because the newly created group space does not have the custom attribute instanceId.

For the workaround, the administrator should do the following:

  1. Navigate to Settings in the process instance group space.
  2. Navigate to custom attributes.
  3. Create the custom attribute instanceId and associate the process instance identifier as the value.

File Size Limit for Process Attachment Is 2 MB


Bug: 9556656
Added: 29-April-2011
Platform: All

If you attach a file to a process, the file must be no larger than two megabytes.


For Large Number of Users Set Timeout to 5 Minutes Maximum


Bug: 9593950
Added: 29-April-2011
Platform: All

If you have a large number of users, set the timeout to no more than 5 minutes. To do this, expand the BPM Workspace .ear file, open the web.xml file, and update the timeout parameter.


Migration Properties Document for T2P for Dashboards


Bug: 11832683
Added: 29-April-2011
Platform: All

The T2P Migration document for Dashboards needs to explicitly specify the migration.properties supported for the T2P utility for objectType DASHBOARD.


ORA-00001: Unique Constraint (SH_SOAINFRA.BPM_AUDIT_QUERY_PK) Violated When Exceeding the Quota


Bug: 9580853
Added: 29-April-2011
Platform: All

If you encounter the following error in the log file:

java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (SH_SOAINFRA.BPM_AUDIT_QUERY_PK) violated when exceeding the Quota

then increase the quota by doing the following:

  1. Run the following SQL command:

    update BPM_AUDIT_SEQUENCE set seq_count = ( select max(query_id) from bpm_audit_query) +1 where seq_name = 'AUDIT_QUERY_SEQ';

  2. Restart the server.

Discrepancy Between Message Recovery Status and Composite Status


Bug: 9776952
Added: 29-April-2011
Platform: All

In some contexts, when a message recovery is performed successfully, the composite status displayed in Oracle Enterprise Manager is still show as Faulted.

This occurs in the following context:

  1. Process A calls Process B with the DenyAll policy attached.
  2. Process A is invoked, but any messages to Process B are not delivered due to the DenyAll setting.
  3. The DenyAll policy on Process B is disabled, and the errors are recovered.
  4. The audit trail shows that the recovery was successful, however the composite status is still marked as Faulted.

There is no workaround for this issue.

Back to top


Business Rules


 

Error When Trying to Locate a Schema in Projects Migrated from PS1 to PS3


Bug: 12868234
Added: 06-December-2011
Platform: All

When you open a Oracle SOA Suite (11.1.1.2.0) project in Oracle SOA Suite (11.1.1.3.0) and click Reload All Facts, an error is displayed when you try to locate the schema in the Project directory and not in the XSD directory (where it is available). This is because the schemaLocation has not been updated to reflect the correct location.

This error also occurs when you open Oracle SOA Suite (11.1.1.2.0) project and create a testsuite.

Workaround: You need to delete the facts pertaining to Oracle SOA Suite (11.1.1.2.0) projects and regenerate them again from their source schemas.


notserializableexception Is Thrown on Opening Dictionary in Oracle SOA Composer


Bug: 12415315
Added: 06-December-2011
Platform: All

In a clustered environment, when you open a dictionary in SOA Composer by clicking a ruleset name in the Select a dictionary to open dialog box, a NotSerializableException is thrown.

There is no loss of functionality because of the exception; the dictionary opens, however the selected ruleset is not displayed by default.

Workaround: Select the dictionary by clicking the row and click the Open button.


The Copy to Project Checkbox is Not Selected by Default While Using URL Location for a Schema


Bug: 11675232
Updated: 03-February-2011
Platform: All

While creating business rules, in the Import schema file dialog box, when you point to the URL location for a schema, the Copy to Project checkbox is not selected by default.

Workaround: In the Import Schema File" dialog box, manually select the Copy to Project checkbox. This is the default selection for schemas imported from local file system (file:/......).

 

RL.contains is Incorrectly Displayed in the List of Operators in Oracle SOA Composer


Bug: 11062184
Updated: 03-February-2011
Platform: All

In Oracle SOA Composer, when writing the "if" part of a if-then rule, RL.contains is incorrectly displayed as one of the relational operators in the operator list.


Too Many Open Files Message When Deploying a Business Rules Project


Bug: 9102568, 7418258
Added: 16-November-2009
Platform: IBM AIX on POWER Systems (64-Bit), HP-UX Itanium, HP-UX PA-RISC (64-Bit), Oracle Solaris

If you see the error "Too Many Open Files" while deploying an Oracle Business Rules Decision Component, you might need to increase the file descriptor limit.

The "Too many open files" issue is due to JDK6 bugs. These bugs could occur at runtime or at compile time, depending on the number of JAR files used and a few other variations around the use of file descriptors by the JDK/JRE.

Workaround: Increase the limit of file descriptors. Per-process, per-user file descriptor limit can be preconfigured by default to the value 1024. If you increase this limit to 4096 or larger, the new value should resolve this issue.

These are the potentially relevant JDK6 bugs:


And a blog entry describes this issue at:

http://coldfused.blogspot.com/2007/02/mystery-of-too-many-open-files.html

The command to increase per-process, per-user file descriptor differs across Operating Systems and shells. It is typically done with ulimit on UNIX platforms so consult the man pages for ulimit for your Operating System and shell.

For example:

$ ulimit -n 4096

Back to top


Business-to-Business Integration (B2B)


 

Change in Names of Configuration Parameters


Bug: 12918690
Added: 06-December-2011
Platform: All

The configuration parameter names FA Handled By B2B and Functional Knowledgement by B2B have been changed to FA Handled Automatically and Functional Knowledgement Automatically. There is no change in functionality.


Oracle B2B Commandline Utility b2bvalidate Uses -dmdsreference as an Option


Bug: 12794661
Added: 06-December-2011
Platform: All

The option -Dargs is not supported in the b2bvalidate commandline utility. Use -dmdsreference instead.


WLST Command reassociatesecuritystore Works Differently in Oracle B2B


Bug: 12396118
Added: 01-May-2011
Platform: All

The WLST command reassociatesecuritystore that is used to reassociate a policy store with an LDAP Server works differently than what is described in Reassociation of Credentials and Policies in "Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite".

For the command to work properly in Oracle B2B:

Instead of using cn="jpsroot" or cn=<cn>, use jpsroot="dc=us,dc=oracle,dc=com".

For example:

reassociateSecurityStore(domain="soainfra",admin="cn=orcladmin",password="welcome1",
ldapurl="ldap://adc2100613.us.oracle.com:3060",servertype="OID",jpsroot="dc=us,dc=oracle,dc=com");

Clicking Deploy Tab under Oracle B2B Displays Spurious Warnings in the Managed Server Console Log


Bug: 11887721
Added: 01-May-2011
Platform: All

Clicking the Deploy tab results in several instances of the following warning in the Managed Server Console log:

Could not find selected item matching value "" ...


Incorrect Date Format in Command-line Purge Destroys Repository


Bug: 11701338
Added: 13-February-2011
Platform: All

A user can destroy the entire Oracle B2B repository (both the design-time and run-time data) if an incorrect fromdate value is entered while executing a command-line purge.

Incorrect:

ant -f ant-b2b-util.xml b2bpurge -Dfromdate="sddsdsd"

Correct:

ant -f ant-b2b-util.xml b2bpurge -Dfromdate="01/02/2009 12:00 AM"


Setting the b2b.syncappdelivery Property


Bug: 10429627
Added: 06-December-2011
Platform: All

When using callouts, to enable delivery of messages to the back-end message queue, set this property to true. By default, this property is enabled (set to >code>true). To disable the message delivery, set this property to false.


Oracle B2B User Interface Does Not Have Provision for the 'readonly' Parameter


Bug: 9669427
Added: 06-December-2011
Platform: All

While creating a delivery or listening channel for a Trading Partner in the Oracle B2B UI, currently, you do not have any provision for specifying a ReadOnly parameter. This feature was present in Oracle SOA Suite 10g.

Workaround: You can achieve the same functionality by setting the File Archival directory parameter available in the Oracle B2B UI.


Back to top


Complex Event Processing


 

java.net.SocketException on IBM AIX on POWER Systems (64-Bit) When Using IPv6


Bug: 9089644
Added: 22-November-2009
Platform: IBM AIX on POWER Systems (64-Bit)

When executing the Oracle CEP server using the IBM JVM on IBM AIX on POWER Systems (64-Bit) with IPv6, the server throws java.net.SocketException.

Workaround: Perform the following steps:

  1. Execute the following commands (using super user privileges or sudo) to modify the AIX network options:
    no -o rfc1323=1
    no -o sb_max=4194304

    For more information, see "Socket Buffer Size" in the Oracle Coherence Developers Guide.

  2. Go to the domain directory.
    For example, <ORACLE_CEP_HOME>/user_projects/domains/domain_name/bin
  3. Edit the setDomainEnv.sh script, and add the following line:
    export IBM_JAVA_OPTIONS="-Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false"

    For more information, see "Multicast and IPv6" in the Oracle Coherence Developers Guide.

Back to top


Enterprise Repository


 

Unable to Access the Operational Data URL to Link Back to Enterprise Manager


Bug: 9694669
Added: 01-May-2011
Platform: All

In the EM Integration configuration file, there is an XML element called URLBase. If you have an EM Console server that is set up for HTTPS with the element set to HTTP, then the link that is created in Oracle Enterprise Repository, which is used to point back to the EM Console, does not work. This is a known issue in 11g Release 1 (11.1.1.5.0).


DTMConfiguration Exception When Running Oracle Enterprise Repository with WebLogic Server 10.3.3 on IBM JDK for AIX


Bug: 9729380
Added: 24-May-2010
Platform: IBM AIX on POWER Systems (64-Bit)

When you run Oracle Enterprise Repository server with WebLogic Server version 10.3.3 on IBM JDK for AIX, then the following exception message is displayed:

org.apache.xml.dtm.DTMConfigurationException: No default implementation found
at org.apache.xml.dtm.DTMManager.newInstance(DTMManager.java:177)
at org.apache.xpath.XPathContext.<init>(XPathContext.java:125)
at org.apache.xalan.transformer.TransformerImpl.<init>(TransformerImpl.java:398)
at org.apache.xalan.templates.StylesheetRoot.newTransformer(StylesheetRoot.java:197)

Workaround: Before starting the Oracle Enterprise Repository server set the JAVA_OPTIONS parameter in setOERDomainEnv.sh as follows:

JAVA_ OPTIONS="-Dorg.apache.xml.dtm.DTMManager=org.apache.xml.dtm.ref.DTMManagerDefault $JAVA_OPTIONS"
export JAVA_OPTIONS

Back to top


Human Workflow


No issue has been discovered at the time of this release. As additional issues and workarounds are discovered after the release, they will be listed here.

For known issues and workarounds for earlier releases, see Known Issues for Oracle SOA Products and AIA Foundation Pack.

Back to top


Mediator


 

Faults Continue to Appear on Faults Tab After Recovery


Bug: 11894501
Added: 01-May-2011
Platform: All

If you recover a faulted resequencer instance for Oracle Mediator and the first recovery fails, two recoverable faults appear in the instance flow trace of the Faults tab. If you then retry and succeed in recovering the instance, that instance still has the Recovery Required status on the Instances tab and the two recoverable faults still appear in the flow trace of the Faults tab.

This only occurs when using the resequencer, and it does not affect runtime performance.


Oracle Mediator Logs Errors After Daylight Savings Time Change


Bug: 12328625
Added: 01-May-2011
Platform: All

Oracle Mediator's container ID processes use timestamps that are regularly updated in a database table by each container in a cluster to determine whether they are alive or not. After changing to daylight savings time (that is, the clock moves forward) it is possible that some timestamps become invalid; for example, when the clock is moving forward from 2:00 AM to 3:00 AM, 2:10 AM is an invalid time. This can result in the following for Oracle Mediator runtime components:

  • Existing running containers report ORA-01878 SQL errors in the log files for the duration of the container ID lease timeout interval, and they recover automatically after the timeout interval is over.

  • If a container stops responding during the invalid time period, on restart that container might report the SQL error continuously and not recover automatically. This results in messages becoming stuck in the running state for resequencer and parallel routing mediator components.

Workaround: Run one of the following SQL commands against the SOAINFRA schema in your database after the change to daylight savings time.

  • For an Oracle database: UPDATE MEDIATOR_CONTAINERID_LEASE SET RENEWAL_TIME = SYSTIMESTAMP

  • For a SQL Server database: UPDATE MEDIATOR_CONTAINERID_LEASE SET RENEWAL_TIME = GETDATE()

  • For a DB2 database: UPDATE MEDIATOR_CONTAINERID_LEASE SET RENEWAL_TIME = current timestamp


Oracle Mediator Locks all Groups on Restart


Bug: 9932333
Added: 01-May-2011
Platform: All

If there are a large number of groups waiting to be processed in the resequencer tables and all the containers are restarted, the first container to restart locks all the groups for processing. Even if the other containers are started, the first container has already locked all the groups and those groups are processed on the first node only. Note that each time a container restarts, it is assigned a new container ID so it loses the association with the groups that were previously assigned to it.

As an example, if there are five containers, each associated with ten groups, and the containers are restarted, all 50 groups are associated with the first container to restart. The 50 groups continue to be processed by the first container even after the remaining containers start up. If all five containers restart simultaneously, the groups are still likely to be associated with only one or just a few containers.


Recoverable Case Instances for the Resequencer Are Tracked Incorrectly


Bug: 9574644
Added: 01-May-2011
Platform: All

In Enterprise Manager, the number of recoverable case instances shown for the Oracle Mediator resequencer equals the number of retries made to that instance rather than the number of actual recoverable instances. This information is for tracking purposes only, and does not result in duplicate messages being sent.


Limits on Streaming Attachments


Bug: 10043603
Added: 01-May-2011
Platform: All

You can pass attachments as a stream using Oracle Mediator, but currently only point-to-point with pass-through is supported. Inbound stream attachments can be routed to only one reference, and no assign or transformation rules can be applied.


Multilingual Support Depends on Database Character Set


Bug: 8369798
Added: 01-May-2011
Platform: All

To avoid any unexpected results when using the multi-language support feature for some functions in Oracle Mediator, ensure that these characters are supported by the character set of the database you are using. For example, for the Unit Test function, if the initial message payload in the unit test includes characters that are not supported by the database character set, the characters fail to display correctly in the unit test section of the Oracle Enterprise Manager Fusion Middleware Control Console. This issue does not occur for a database that supports Unicode characters.


Oracle Mediator - BPEL Process Manager Callback Processing


Bug: 8472652
Added: 01-May-2011
Platform: All

If Oracle Mediator calls a BPEL process with callback processing and timeout, the best practice is to explicitly handle the callback exceptions returned from Oracle Mediator in the BPEL process. This ensures that the global transaction associated with callback processing gets committed and is not rolled back. This way, the timeout handler configured in Oracle Mediator will not kick in even if the callback handling in Oracle Mediator fails.


Oracle Mediator Components May Cause SOA Suite Server to Run Out of Memory


Bug: 9067255
Added: 01-May-2011
Platform: All

Oracle Mediator applications may run out of memory under heavy loads. For example, if the rate of incoming messages to Oracle Mediator is faster than the rate of callback messages, memory accumulation occurs in the Oracle Mediator cache.

Workaround: To fix this issue, change the cache size through the Oracle Enterprise Manager Fusion Middleware Control Console by adding the following property in the Parameters attribute of the Oracle Mediator configuration properties:

mediator.runtime_cache.limit=value

For example, if you set the value of the mediator.runtime_cache.limit property to 100, the number of objects that can be stored in the cache is limited to 100. You can switch off caching completely by setting this property to zero.


Oracle Mediator Advanced Functions Do Not Work in Design Time


Bug: 9072259
Added: 01-May-2011
Platform: All

Oracle Mediator advanced functions, such as mhdr:getCompositeName() and mhdr:getHeader, require a runtime context to execute. If these functions are run using the Mapper Test feature during design time, the target XML file is not generated and the following error is thrown:

XML-22044: (Error) Extension function error: Error invoking 'getComponentName':'

java.lang.IndexOutOfBoundsException: Index: 0, Size: 0'

These functions work correctly in the runtime environment.


A Null Pointer Exception Occurs When There Are No Routing Rules


Bug: 9557297
Added: 01-May-2011
Platform: All

To have a valid configuration, each Oracle Mediator component must include routing rules. If a component has no routing rules, Oracle Mediator does nothing at runtime and a null pointer exception occurs at mediator.dispatch.CaseExecutionPlan.getEffectiveExecutableCases.

Back to top


Service Bus


Oracle Enterprise Pack for Eclipse Support


Bug: 12879815
Updated: 16-August-2011
Platform: All

For the Oracle Service Bus 11.1.1.5.0 development environment, use Oracle Enterprise Pack for Eclipse (OEPE) version 11.1.1.7.2.


Patches to Apply for Exalogic Support


Bug: 12830557
Updated: 3-August-2011
Platform: Linux, Solaris

On Linux and Solaris, to run Oracle Service Bus on Exalogic, apply the following patches:

For information on supported versions of Oracle Service Bus and Exalogic, see the System Requirements and Supported Platforms for Oracle Service Bus 11gR1.


Updates to Supported Interoperability


Bug: 12544742
Updated: 11-May-2011
Platform: All

Following are corrections to the "Interoperability Scenarios and Considerations" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus:

  • IBM WebSphere MQ 7.0 support for MQ 7.0 client libraries
  • Tibco Enterprise Message Service support for all versions that meet the JMS 1.2 specification through Oracle WebLogic Server

Installation and Upgrade Guides Remain at Version 11.1.1.4.0


Bug: 12381638
Added: 01-May-2011
Platform: All

The Oracle Fusion Middleware Installation Guide for Oracle Service Bus and the Oracle Fusion Middleware Upgrade Guide for Oracle Service Bus will remain at their 11.1.1.4.0 versions for 11.1.1.5.0. For 11.1.1.5.0 installation and upgrade, replace any references to 11.1.1.4.0 with 11.1.1.5.0.

One exception may apply to downloading and installing the latest patch set. At the time this note was published, the latest patch set was 11.1.1.4.0.


Documentation Correction to OSB.coherence.ttl Description


Bug: 12371516
Added: 01-May-2011
Platform: All

In the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus, "Table 36-7 osb-coherence-override.xml Default Settings for an 'Oracle Service Bus for developers' Domain Topology," the documentation incorrectly describes the OSB.coherence.ttl override as a cache expiration setting. Instead, the setting overrides the multicast network time-to-live tangosol.coherence.ttl property. For more information on this setting, see "Network" in the Oracle Coherence Developer's Guide.


Existing Server Extended with Oracle Service Bus for Developers Template Fails to Start


Bug: 12343853
Added: 01-May-2011
Platform: All

After extending an Oracle WebLogic Server domain with the "Oracle Service Bus for developers" domain template, and using Derby as the data source for the JMS reporting provider, the extended server fails to start because of errors related to Derby database initialization.

Workaround: Set the DERBY_FLAG to true in your DOMAIN_HOME/bin/setDomainEnv.cmd(.sh) script. For example:

set DERBY_FLAG = true

For Derby best practices and troubleshooting information, see "Running Multiple Development Domains with Derby" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.


Errors Running Multiple Servers on a Development Machine


Bug: 12340850
Added: 01-May-2011
Platform: All

When trying to run multiple Oracle Service Bus servers on a development machine, you receive JDBC errors when each server attempts to connect the Derby instance. The issue occurs after one server is created with the default Derby database settings in the Oracle Fusion Middleware Configuration Wizard. Even though the original server starts successfully, subsequent development servers created with the default Derby database on the same machine cannot start even when the original server is not running. This is because only one server can be associated with a specific Derby database.

Workaround: For Derby best practices and troubleshooting information, see "Running Multiple Development Domains with Derby" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.


Console Logout Does Not Work When Logging In Through OAM


Bug: 11729325
Added: 01-May-2011
Platform: Linux

When using Oracle Access Manager 10g or 11g to log in to the Oracle Service Bus Administration Console, clicking Logout does not end the session. It returns you to the Oracle Service Bus Administration Console home page, still logged in, rather than logging you out and returning you to the Oracle Access Manager login page.

Workaround: To end the Oracle Service Bus Administration Console session, close your browser.


Starting Managed Server with IPv6 Host and Port Throws BEA-000000 Error


Bug: 10029204
Added: 01-May-2011
Platform: All

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.

Workaround: Create a key-pair, and 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.


Session Activation Error Message in Firefox


Bug: 9958876
Added: 01-May-2011
Platform: All

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.


Password Field Not Editable in Domain Template on Linux


Bug: 10394900
Added: 01-May-2011
Platform: Linux

On Linux, when creating a new domain using a developer template in the Oracle Fusion Middleware Configuration Wizard, the password and confirm password fields are not editable, and you cannot enter a password to create a domain.

Workaround: Do one of the following:

  • To work around the issue each time it occurs: Click the close window "x" button in the upper right corner of the Configuration Wizard. In the confirmation dialog that appears, click "No" to return to the Configuration Wizard. Now you can enter the password and confirmation password.
  • To fix the issue permanently:
    1. Kill a scim processes. For example, kill "pgrep scim"
    2. Modify (or create) the file ~/.scim/config to include the following line:
      /FrontEnd/X11/Dynamic = true (follow case sensitivity)
    3. If you are running VNC, restart the VNC server.
    4. Run the Configuration Wizard again.

JAVA_HOME Incorrect in setDomainEnv After Domain Upgrade on 64-Bit Install


Bug: 10404384
Added: 01-May-2011
Platform: All

On 64-bit installations of Oracle Service Bus, after upgrading a domain from 11g Release 1 Patch Set 2 (11.1.1.3.0) to 11g Release 1 Patch Set 3 (11.1.1.4.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.

Workaround: Edit the setDomainEnv.cmd/sh in the upgraded domain with the correct JAVA_HOME for the JDK you are using.


Oracle Application Adapter Installation Failure on Windows


Bug: 10424957
Added: 01-May-2011
Platform: Windows

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.

Workaround: Perform the following steps:

  1. Back up your Windows registry.
  2. In Windows, choose Start > Run, enter regedit in the Run dialog box, and click OK.
  3. In the registry editor, go to the following registry folder:
    HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\version_number
  4. 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.

Inbound Adapters Throw Error on Payload Size Limit


Bug: 9969535
Added: 01-May-2011
Platform: All

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.

Workaround: Increase the size of the payloadSizeThreshold property on the JCA adapter endpoint configuration.


MQ Transport in Binding Mode Throws Error on Linux


Bug: 10020344
Added: 01-May-2011
Platform: Linux

When Oracle Service Bus and IBM WebSphere MQ are installed on the same Linux system, configuring the Oracle Service Bus MQ transport to run in binding mode causes an error.

Workaround: Perform the following steps:

  1. Make sure Oracle Service Bus and IBM WebSphere MQ are installed using the same user credentials.
  2. Add the MQ Java library path to the Oracle Service Bus DOMAIN_HOME/bin/setDomainEnv.sh file. For example:
    -Djava.library.path=/opt/mqm/java/lib
  3. Oracle JRockit: When using Oracle JRockit on Linux, add the LD_PRELOAD property to setDomainEnv.sh as well. For example:
    LD_PRELOAD=${JAVA_HOME}/jre/lib/i386/libjsig.so

Publishing Services to IPv6 Server Fails


Bug: 10032879
Added: 01-May-2011
Platform: All

Publishing services from the development environment to a domain that uses IPv6 addressing results in a MalformedURLException error.

Workaround: 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].


Resources Disappear When Server Encoding Changes


Bug: 9488927
Added: 01-May-2011
Platform: All

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.

Workaround: Switch back to the original server encoding and restart the server. Oracle Service Bus does not support server encoding changes.


Oracle Service Bus Product Download Location


Bug: 11064754
Added: 01-May-2011
Platform: All

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.

http://www.oracle.com/technetwork/middleware/service-bus/downloads/index.html

Back to top


Service Registry


No issue has been discovered at the time of this release. As additional issues and workarounds are discovered after the release, they will be listed here.

For known issues and workarounds for earlier releases, see Known Issues for Oracle SOA Products and AIA Foundation Pack.

Back to top


Enterprise Scheduling Service


No issue has been discovered at the time of this release. As additional issues and workarounds are discovered after the release, they will be listed here.

For known issues and workarounds for earlier releases, see Known Issues for Oracle SOA Products and AIA Foundation Pack.

Back to top