Skip navigation.

Release Notes

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents View as PDF   Get Adobe Reader

BEA AquaLogic Service Bus Release Notes

BEA AquaLogic Service Bus Release: 2.0
Release Date: July 2005

Table 1 Document Revision History

Revision Date


Sept 01, 2005

Add information for CR238756 combo patch; see AquaLogic Service Bus 2.0 Software and Patches

August 22, 2005

Correct links to Supported Configurations for AquaLogic Service Bus and BEA AquaLogic Service Bus Concepts and Architecture

July 22, 2005

Release of AquaLogic Service Bus 2.0 software

This document includes the following topics:

For the latest release note information for AquaLogic Service Bus and other BEA products, go to the BEA documentation Web site at the following URL:


About This Release of BEA AquaLogic Service Bus

BEA AquaLogic Service Bus is designed to simplify the life cycle costs and complexities of integrating and managing shared services in an enterprise Service-Oriented Architecture (SOA) environment. It combines intelligent message brokering with service monitoring and administration to provide a unified software product for implementing and deploying your SOA.

AquaLogic Service Bus is policy-driven and enables loose coupling between service clients (the service consumers) and business services (the service providers), providing a point of security control, monitoring and Service Level Agreement (SLA) enforcement. Changes to service integration relationships are implemented dynamically through configuration, not code, allowing you to evolve your service architectures with respect to security, service location, availability, data formats, monitoring, transports, communications, and so on.

As part of an enterprise's messaging fabric, AquaLogic Service Bus can be used horizontally across many applications and systems, potentially spanning service implementations (built by different teams) in different departments. AquaLogic Service Bus separates a set of management functions from the service implementations, thus allowing the implementations to evolve independently and dynamically as driven by the needs of the business without requiring costly infrastructure development efforts.

For more information about AquaLogic Service Bus concepts and architecture, see BEA AquaLogic Service Bus Concepts and Architecture.


AquaLogic Service Bus 2.0 Software and Patches

To download AquaLogic Service Bus 2.0, go to the BEA Downloads site:

For AquaLogic Service Bus 2.0, BEA provides the following combo patch on the BEA Downloads site: CR238756. BEA recommends that you apply this patch to your AquaLogic Service Bus 2.0 installation. You can download the CR238756 combo patch from the following URL:

The following table lists the CRs that are addressed in the CR238756 combo patch:

Problem ID



SOAP fault handling.

This patch changes the default system property from JMS_BEA_Error to SERVER_ERROR. For information about the JMS_BEA_Error property, see "Handling Errors" in Modeling Message Flow in AquaLogic Service Bus.

If you want to use a property other than the default SERVER_ERROR property, you can do so by adding the following command line argument to JAVA_PROPERTIES in the bin\setDomainEnv script for your domain.

where myProperty is the name you assign to this error property.

Note: For backward compatibility, you can assign the name JMS_BEA_Error.


Routing to external Web service (business service) raises a "no SOAPAction header" fault


Error encrypting the outbound message if the inbound message is signed


AquaLogic Service Bus cluster throws NameNotFoundExceptions at re-startup


Alert Summary portlet is not displayed in the Mozilla Firefox browser


Interval Statistics calculation over a cluster is not correct


Null pointer exception (NPE) when user clicks on an alert rule link in the Dashboard after deleting that rule


HTTP inbound response metadata is not initialized when a malformed SOAP envelope is received


When you restart managed servers in a cluster the Server Summary Panel may not display a managed server on which an aggregation server is deployed


The rule run-time state must be cleared when the rule becomes INACTIVE


Workaround WLS security bug CR234126: new credential provider is available via the run-time tree (without reboot)


Cancel button In Alert Rule General Configuration causes exception for a specific navigation sequence


XML Beans does not preserve the namespace declaration for the prefix used in QName values


The Alert Rule configuration UI allows you to specify only one of Start and End Times


Managed Server is unable to start in MSI (Managed Server Independent) mode


Null pointer exception (NPE) when using empty default namespace


Reverting the code workaround for not preserving namespace declaration for prefix used in QName values. Issue handled by XBeans


Validate action does not flag empty results


Assigning an attribute result from an XQuery to a context variable results in an incorrect value


Cannot activate import of config.jar file overlaying some existing objects


Deleting a project deletes objects from another project with same prefix


For up-to-date information about other fixes for known limitations, contact your BEA Customer Support representative. For information about known limitations in AquaLogic Service Bus 2.0, see Known Limitations.


Supported Configurations and System Requirements

This section summarizes the supported configurations for AquaLogic Service Bus 2.0. It includes the following topics:

Operating Systems, Databases and Drivers, and Browsers and Plug-Ins

For information about operating systems, databases and drivers, browsers and plug-ins, and other hardware and software requirements, see Supported Configurations for AquaLogic Service Bus.

For information installing BEA products, including the BEA Products Installation and Configuration Release Notes, see BEA Products Installation and Configuration Documentation at the following URL:

Web Services Interoperability (WS-I) Compliance

AquaLogic Service Bus supports a broad compliance with messaging standards for SOAP 1.1, HTTP, JMS, SMTP/POP/IMAP, FTP, SSL, XML 1.0, XML Schema, WSDL 1.1, and WS-Security. This includes WS-I compliance. However, in some cases, AquaLogic Service Bus does not reject SOAP/HTTP messages that are not WS-I compliant. This enables you to build implementations with service endpoints which are not strictly WS-I compliant.

Data Transformation Tools

The following data transformation tools are installed when you install AquaLogic Service Bus 2.0: The BEA XQuery Mapper plug-in for Eclipse 3.0 and Format Builder. Eclipse 3.0 and Format Builder are supported on Windows platforms only (see Operating Systems, Databases and Drivers, and Browsers and Plug-Ins).

The BEA XQuery Mapper is a set of plug-ins in Eclipse. Note that the installation of Eclipse with the AquaLogic Service Bus product does not include the Java Development Tooling (JDT) plug-ins or the Plug-in Development Environment (PDE) toolkit. You can add other plug-ins to the Eclipse IDE provided with AquaLogic Service Bus. However, when you attempt to install a plug-in, any plug-ins that it depends on must already be installed. Likewise, if the plug-in you want to install depends on the JDT or the PDE, you must install these first. You can download the PDE and JDT plug-ins from

Support for RPC and Document Encoded WSDL-Based Web Services

Web services can expose one of two styles for binding to their Web operations in the Web Service Description Language (WSDL) contract that describes them: Document or RPC. AquaLogic Service Bus does not support encoding and decoding aspects for RPC or Document encoded proxy or business services, but does support RPC literal and Document literal.

If a WSDL specifies an encoded binding, an error is not returned—instead, AquaLogic Service Bus uses literal encoding. However, straight passthrough of encoded envelopes without manipulation in the message flow does work.

(Reference CR234886)


Known Limitations

This section describes known limitations in the BEA AquaLogic Service Bus 2.0 Release software. The limitations are grouped in the following sections:

AquaLogic Service Bus Run Time

Problem ID



Do Not Specify the Same Directory for Polling as is Specified for Archiving Files

In general, it is not advisable to specify the same directory location for your poller and archive file locations when you design a proxy service with a file transport. If you need to specify the same directory location that is specified for the poller and archive files, you must specify an appropriate mask for the files to be polled; for example, you can specify *.txt, *.bmp, and so on.


Version Utility weblogic.version Does Not Display Version Information for AquaLogic Service Bus

Version information for AquaLogic Service Bus is contained in the version.jar file that is located at BEA_HOME/weblogic90/servicebus/lib, but it is not displayed by the utility java weblogic.version.


    1. Set up your environment by running domain/bin/setDomainEnv.cmd, where domain is the name you gave your domain when you created it. For Windows, use setDomainEnv.cmd; for UNIX, use domain\bin\

    2. Add BEA_HOME/weblogic90/servicebus/lib/version.jar to your CLASSPATH, where BEA_HOME is the directory in which you installed your BEA product.

    3. Invoke java weblogic.version. The version information for AquaLogic Service Bus is now displayed.

Alternatively, you can open the servicebus/lib/version.jar file and manually examine the version information in the manifest file,

Note: The Service Bus version.jar file contains the temporary product name and version "WebLogic Service Bus 9.0". The correct name and version is "AquaLogic Service Bus 2.0".


A WSDL Cannot Have Two Operations with the Same Input Message when you Select the SOAP Body Type Selection Algorithm While Creating a Proxy Service Based on the WSDL Template

If you have a WSDL that has two operations with the same input message, do not choose the SOAP Body Type selection algorithm for operations, because the operation cannot be uniquely identified by inspecting the input message. AquaLogic Service Bus' validation algorithm does not identify this scenario, and does not prevent users from selecting this algorithm. Therefore, when you use the SOAP Body Type selection algorithm, make sure that the WSDL does not have two operations with the same input.


Recursive XQueries are Not Supported

Do not write recursive XQuery statements when you design your proxy services.


Some Updates to Policies in the AquaLogic Service Bus WS-Policy Repository are not Picked up by Proxy or Business Services that Depend on the Policy

When a proxy service or business service depends on a WS-Policy in the WS-Policy repository via a reference in the WSDL of the form policy:<policyId>, updates to the WS-Policy are not reflected on the proxy or business service.

Workaround: Make a change to the WSDL that references the policy. Any inconsequential change to the WSDL will do (for example, add a space).


Keep the Name and Path of Proxy Services Short for Successful Deployment on Windows Machines

Keep the name and path of proxy services short for successful deployment on Windows machines, as there is a system path length limitation on Windows machines.

Note: To learn about maximum path lengths, see the following information: "Maximum Path Length" at the following URL:


AquaLogic Service Bus Domain Cannot be Started with weblogic.transaction.loggingresource.LoggingResourceException

You cannot start an AquaLogic Service Bus domain with weblogic.transaction.loggingresource.LoggingResourceException when you move a domain template to a different machine and use the template to create the new domain. The scenario is as follows:

    1. Create the original domain.

    2. Start the server for the original domain. At this point, the domain is now "used"—a domain is considered used once you have started the server for a domain after you have created it.

    3. Create the domain template. You can create it in several different ways—use the Domain Template Builder tool and the Configuration Wizard, the pack\unpack command, or the Weblogic Scripting Tool in offline mode.

    4. Move the domain template to a different machine.

    5. Create a new domain using the template. Again, you can create it in several different ways—use the Domain Template Builder tool and Configuration Wizard, the pack\unpack command, or the Weblogic Scripting Tool in offline mode.

    6. Start the server for the domain. If the new domain does not have the same name as the initial domain, the new domain cannot be started. This is because the JMS Reporting Provider provided with AquaLogic Service Bus uses the Logging Last Resources (LLR) option. The new domain is attempting to use the same database, schema, and LLR table name to store LLR transaction records. LLR does not allow this to prevent different domains from corrupting each other's tables. To learn more about the LLR feature, see Configuring JDBC Data Sources in Configuring and Managing WebLogic JDBC.

Note: You can access the Domain Template Builder, Configuration Wizard, and the WebLogic Scripting Tool from the BEA Products—>Tools menu on your machine. The tools and the pack and unpack commands are located in the BEA_HOME/weblogic90/common/bin directory.

Workaround: You must use the same domain name when you create the new domain using the same template on a different machine. Alternatively, change the name of the LLR table that the new domain uses. You can configure this on the WebLogic Server Administration Console on a per Server basis, using the JDBCLLRTableName attribute on the ServerMBean.

CR231843 (cond.)

Note: There is no protection mechanism similar to LLR's for standard WebLogic JDBC store tables. Therefore, if you replicate a domain that has WebLogic JDBC stores configured without renaming the store tables or without using a different database user and schema for the new store's connection pool, data corruption occurs if both the old and the new domains remain active. Similarly, corruption (without warnings) may occur if same-named WebLogic file stores share the same directory.


If the Administration Server Crashes When a Session Activation is in Progress, a WebLogic Server Change Lock Prevents Further Session Activations

When a session is activated, AquaLogic Service Bus acquires a WebLogic Server lock that is held throughout the activation, and then released when the activation completes (successfully or not). However, if the administration server crashes before the session activation completes, the lock is not released automatically when you restart the server. This lock prevents further session activations.

Workaround: Log on to the WebLogic Server Administration Console, and release the lock held by WebLogic Server.


The Response Destination May Not be a WebLogic Server Distributed Destination in the Same Cluster as AquaLogic Service Bus for JMS Business Services

The response destination may not be a WebLogic Server distributed destination in the same cluster as AquaLogic Service Bus for JMS business services.

Workaround: WebLogic Server regular (pinned) destinations, WebLogic Server distributed destinations in a different cluster, and non-WebLogic Server destinations may be configured as response destination.


A Messaging Proxy Service Still Receives and Routes Messages After it has been Deleted if the User Sends Messages to it

A Messaging Proxy Service still receives and routes messages after it has been deleted if the user sends messages to it.

Workaround: Do not use the JMS destination to which the deleted Messaging Proxy Service was listening.



Do Not Use the Default System Prefix (soap-env) when Constructing a Non-System Fault in AquaLogic Service Bus

When you create a non-system fault in AquaLogic Service Bus, you cannot use the default system prefix (soap-env) for the namespace. You must declare a new namespace prefix and use it in the faultcode.

Workaround: To construct a non-system fault in AquaLogic Service Bus:

    1. Assign the soap body with the desired fault format to the body context variable ($body).

    2. When creating <faultcode>, you must declare a new namespace prefix for
    and use the new prefix in the faultcode. For example:



Update: This limitation is fixed in Combo Patch CR238756. For information about the patch, see AquaLogic Service Bus 2.0 Software and Patches.




Namespace Declarations May be Dropped if They are Only Declared at the <Envelope> Level And if They are Only Used in QName Values Such As xsi:type

Namespace declarations may be dropped if they are only declared at the <Envelope> level and if they are only used in QName values such as xsi:type. This problem prevents interoperating with encoded web services, either RPC encoded or Document encoded. In addition, this is a factor that causes problems in interoperating with .NET.

Workaround: Contact your BEA Customer Support Representative and request patch numbers CR234549 and CR232996.

Update: This limitation is fixed in Combo Patch CR238756. For information about the patch, see AquaLogic Service Bus 2.0 Software and Patches.

AquaLogic Service Bus Security

Problem ID



Delete all Transport-Level and Service-Level Access-Control Security Policies Before Deleting a Proxy Service

Before you delete that service from AquaLogic Service Bus, you must delete all transport-level (HTTP and HTTPS) and service-level security policies associated with a proxy service. Failure to do so will leave the security policy in the authorization-provider database and potentially cause unexpected results and potential security vulnerabilities.


Service Account Usernames and Passwords may be Recovered by Administrators

When using the built-in XQuery function fn-bea:lookupBasicCredentials, the username and password associated with a service account is sent in clear-text in the SOAP envelope. This risk is reduced by the fact that only AquaLogic Service Bus administrators can edit Proxy service message flows and deploy configurations to AquaLogic Service Bus.


Inbound Web Service Security Limitation

Inbound Web Service Security does not work on the same operation if the WS-Policy on the request specifies digital signature and the WS-Policy on the response specifies encryption. This limitation applies to active intermediary scenarios only, it does not apply to pass-through scenarios.

Workaround: This limitation is fixed in Combo Patch CR238756. For information about the patch, see AquaLogic Service Bus 2.0 Software and Patches.


Inbound Web Services Security Authentication with X.509 Token Limitation

A bug exists in the client-side Web Service Security run time that causes X.509 token authentication to fail in certain cases. Make sure to include a dummy username token CredentialProvider (see source code that follows) along with a ClientBSTCredentialProvider in the list of credential providers passed to the JAX-RPC client. The credential provider list is passed to the client as the value of the property named

For more information, see "Updating a Client Application to Invoke a Message-Secured Web Service" under "Configuring Message-Level Security (Digital Signatures and Encryption)" in Configuring Security in Programming Web Services for WebLogic Server.

import weblogic.xml.crypto.wss.WSSConstants;
import weblogic.xml.crypto.wss.provider.CredentialProvider;
import weblogic.xml.crypto.wss.provider.Purpose;

public class DummyUNTCredentialProvider implements CredentialProvider {

    public DummyUNTCredentialProvider() {

    public String[] getValueTypes() {
        return WSSConstants.UNT_VALUETYPES;

    public Object getCredential(String tokenType,
                                String issuerName,
                                ContextHandler ctxHandler,
                                Purpose p) {
        return null;



Insufficient Error Message if Mismatch Exists in the Encryption Key Between the Client Service and Endpoint Service

When encryption is used with Web Service Security between a proxy service and a business service, AquaLogic Service Bus retrieves the business service's certificate from the business service's WSDL in the WSDL repository. The certificate must be embedded in a WS-Policy that is inlined in the WSDL. It is possible for this certificate to get out-of-sync with the actual certificate used by the business service. In this case, the proxy service encrypts (with the wrong key) and routes the message to the business service. However, the business service is unable to decrypt the message. This scenario is difficult to debug. If the target service is a WebLogic Server 9.0 Web Service, you may get an error in the target server log that includes the following text:

<CertPathBuilder does not support building cert path from class [Security:090596]The WebLogicCertPathProvider was passed an unsupported CertPathSelector.

To help diagnose this type of error, retrieve a fresh copy of the business service's WSDL by dereferencing the <service>?WSDL URL or some other out-of-band method. Then, by comparing the base64-encoded strings in the fresh copy to the WSDL in the AquaLogic Service Bus WSDL repository, you can determine if the certificates match. To fix the problem re-import the WSDL into the WSDL repository.


If you Add or Delete a Security Provider, You Must Reboot the Server for the Security Changes to Take Effect

If you add or delete a security provider, you must reboot the server for the security changes to take effect. In particular, if you configure a new PKI credential mapper and fail to reboot the server, you will get an exception whenever you access any page in the Credentials section of the AquaLogic Service Bus. The Credentials section will be available again after you reboot the server.


AquaLogic Service Bus Servers Must Have the Clear-Text Listen Port Enabled

AquaLogic Service Bus Servers are configured with a clear-text listen port by default. An additional SSL listen port can be configured. The clear-text listen port is required—do not disable it.


Unbound JMS Service Account Leads to Continuous Run-Time Exceptions

When a service account is specified for a proxy service or business service to access the JMS server and/or JNDI lookup, you must first associate the service account with a username and password before invoking the service. Failure to do so results in AquaLogic Service Bus continually reporting the error as an exception. You can correct this problem in the AquaLogic Service Bus Console by assigning the username and password to the service account in the Credentials section of the Security Configuration module. The administration server does not have to be restarted.

Note: There are other conditions that can cause the same problem of continuous run-time exceptions. To avoid this problem again, we recommend that you configure JMS queues to have a limited number of retries.

AquaLogic Service Bus Interoperability

Problem ID



Problems Using the WebLogic Workshop JMS Control to Send Messages to a Queue in Another Domain

A problem exists when using a JMS Control to send and receive messages to and from remote queues on a server in a WebLogic 8.1 domain. If your use case requires this functionality, contact your BEA Customer Support representative and request patch number CR205484.


Enabling WebLogic Server 8.1 JMX Interoperability with AquaLogic Service Bus 2.0

To achieve full interoperability between WebLogic 8.1SP4 domains and AquaLogic Service Bus 2.0 or WebLogic Server 9.0, the following patch is required for WebLogic Platform 8.1SP4: CR214028. Contact your BEA Customer Support representative and request the patch number CR214028.


Problem Sending SOAP 1.1 Attachments From AquaLogic Service Bus 2.0 to WebLogic Workshop 8.1 Services

A known problem exists when sending SOAP 1.1 attachments from AquaLogic Service Bus to WebLogic Workshop 8.1 Web Services—the javax.activation.DataHandler always returns null.

Workaround: A patch is not available at the time of the AquaLogic Service Bus 2.0 release. However, if your use case requires this functionality, contact your BEA Customer Support representative and request an update on the status of CR229661.


WSDLs Generated for XML Web Services in WebLogic Workshop Cannot be Used in AquaLogic Service Bus

Because of a problem retrieving the correct part name and therefore the expected schema type of the message from WSDLs generated for XML Services in WebLogic Workshop, you cannot use these WSDLs in AquaLogic Service Bus.

Workaround: Use a SOAP Web service to generate the WSDL or edit the WSDL generated by WebLogic Workshop from the XML Web service before using it in AquaLogic Service Bus. Replace <mime:mimeXml part="Body"/> with <mime:mimeXml />.

AquaLogic Service Bus Console

Problem ID



A "Graphics Library Disabled" Image is Displayed Instead of Charts in the Monitoring Module if the Graphics Library Cannot Be Initialized

A "Graphics Library Disabled" image is displayed instead of pie and bar charts in the Monitoring module if the Graphics Library cannot be initialized in a Linux environment. Links on the Server Summary, Server Detail, Alert Summary, and Alert Detail pages are also removed. The problem may be that the graphics library support (X11) toolkit is not installed on your machine.

Workaround: Linux requires the X11 modules installed as a precursor to the installation of AquaLogic Service Bus. Isolate the libraries required for installing the X11 toolkit or the native graphics library for Linux. You can fix this problem by setting the proper "DISPLAY" environment variable.


Your Browser Continues to Display the Same Page When You Click Save on the View Policy Details Page for Transport Access Control Policy or Service Access Control Policy

When you click Save on the View Policy Details page for transport policies or service policies in the Security Configuration module, your browser continues to display the same page instead of returning to the Access Control for Proxy Services page.

Workaround: From the left navigation pane, select Access Controls from under Security Configuration. The Access Control for Proxy Services page is displayed. You can also click a navigation link on the top of the page, then navigate to the Access Control for Proxy Services page.


Only WebLogic Server Administrators Can Define Access Control Policies

Only users in the WebLogic Server built-in Administrator role are allowed to manage access control policies on AquaLogic Service Bus resources; that is, transport-level HTTP or HTTPS proxy service access control policies and proxy service policies. To configure these policies, users must log in to the AquaLogic Service Bus Console as the WebLogic Server Administrator and select Access Controls in the Security Configuration module.


Deleting An Alert May Not Immediately Reduce the Alert Count on the Alert Summary Page

When you delete an alert in the Monitoring module, the alert count on the Alert Summary page may not be immediately reduced. This behavior is seen in situations where a large number of alerts are being generated. The reason for this is when an alert is generated, the data record is stored in a memory cache before it is written to a repository after a time interval. When you delete an alert on the console, the alert record is marked in the memory cache for deletion in the alert repository. Because there is a delay in flushing out this marked record to the repository from memory cache, the deleted alert is displayed on the console until it is flushed from the memory cache.

Workaround: Refresh the console after you delete the alert. After 2-3 minutes, the deleted alert is no longer included in the alert count.


Blank Page Displayed When An Invalid Selection is Made for the Purpose of a Credential

A blank page is displayed when you make an invalid selection in the Purpose of this Credential dropdown list in the Credentials section of the Security Configuration module.

Workaround: Click the Back button in your browser, then make a different selection in the Purpose of this Credential dropdown list.


Request Encoding Value is Required for JMS Proxy Services

It is not necessary to specify a value in the Request Encoding field for JMS proxy services that send TextMessages. The default for text/XML proxy services is UTF-8. However, for inbound request, a JMS proxy service may receive a Bytes or Text message. Because a proxy service may receive BytesMessage, encoding information is required to correctly interpret those bytes. To avoid this problem, we recommend that you use one that is Unicode-based such as UTF-8 or UTF-16.


The Start and End Times Must Be At Least One Minute Apart When You Filter Messages in the Reporting Module

When you use the search filter to retrieve or purge messages in the Reporting module, if you specify the same start and end times to filter messages for a specific minute, the search filter returns zero messages even if there are reporting messages with that timestamp. For example, if you specify 7.10pm as the start and end time, the search filter does not return the messages that are marked with that timestamp. The reason for this issue is that messages are persisted in the database with timestamps up to the second, whereas on the AquaLogic Service Bus Console the messages are displayed with timestamps up to the minute only.

Workaround: Specify the end time at least one minute after the start time. For example, if you specify the start time as 7.10pm and the end time as 7.11pm, then the search filter returns all messages that are marked with a timestamp from 7.10pm up to but not including 7.11pm.


Fewer Message and Alert Counts May Be Reported After A Managed Server Is Restarted

In the event that a managed server in your cluster is stopped and then restarted, fewer message counts and alert counts may be displayed in the Dashboard Monitoring Summary page than were displayed before the managed server went down. Because only statistic summary information is written to disk and recovered after a failure, it is necessary to approximate some of the data during the server restart. This can result in the slightly reduced counts. The accurate counts are available again after a full aggregation interval has elapsed.



The Expiration Date for Alert Rules Only Accepts the Last Two Digits of the Year

The Rule Expiration Date field on the New Alert Rule - General Configuration page has a format of MM/DD/YY. If you enter a four digit number for the year, it is persisted correctly and the rule is evaluated correctly against the entered date. However, the AquaLogic Service Bus Console interprets only the last two digits of the date entered and can incorrectly flag the rule as Expired. Therefore, an expiration date entered as 12/21/2100 is interpreted as 12/21/00 and marked as Expired in the AquaLogic Service Bus Console even though the rule is evaluated correctly at run time.

Reference CR235412

Additionally, if you enter a two digit number for the year and the entered date occurs in the past, the date is correctly displayed as Expired in the AquaLogic Service Bus Console but is incorrectly persisted as belonging to the next century and the rule is not considered expired at run time. For example, a date entered as 06/28/05 is correctly displayed as Expired in the AquaLogic Service Bus Console but incorrectly persisted as 06/28/2105 for run-time evaluation.

Reference CR234878


Web Service Security Errors Not Counted by Message Error Counter

If a WS-Security error occurs for a business service, it increments only the security error count on the Service Monitoring Details page and is not counted in the overall error counter. This means that the displayed success rate is higher than it should be because the WS-Security errors are not taken into account.


When You Restart Managed Servers in a Cluster the Server Summary Panel May Not Display a Managed Server on Which an Aggregation Server is Deployed

In the event that managed servers in a cluster are stopped and then restarted, a managed server on which an aggregration server is deployed may not be displayed on the Server Summary panel on the Dashboard.

Workaround: First, shut down the managed servers, then shut down and restart the Administration Server, followed by the managed servers. The Server Summary display will then include the managed server on which the aggregation server is deployed.

Update: This limitation is fixed in Combo Patch CR238756. For information about the patch, see AquaLogic Service Bus 2.0 Software and Patches.


The Default Browser Options for Windows 2003 Server Cause a Browser JavaScript Error When You Click a Link in the Left Navigation Pane of the AquaLogic Service Bus Console

The default Internet Options—>Security Settings for Windows 2003 Server are set to High, which disables active scripting. This causes a browser error when you click a link in the left navigation pane of the AquaLogic Service Bus Console.

Workaround: Modify the Internet Options—>Security Settings to Active Script: Enable. Because AquaLogic Service Bus uses JavaScript in the console pages, make sure JavaScript is enabled in your browser.

BEA WebLogic Server Administration Console

Problem ID



Ensure that You Select the `Use Default User Name Mapper' Option When You Configure a Default Identity Asserter in the WebLogic Server Administration Console

To generate a vaild config.xml file, you must specify the Use Default User Name Mapper option when you configure a DefaultIdentityAsserter from the following page in the WebLogic Server Administration Console:

Security Realms—>realm—>Provider—>DefaultIdentityAsserter —>Provider.

If you do not select the Use Default User Name Mapper option, you must have specified the User Name Mapper Class Name.

Workaround: If you set neither the Use Default User Name Mapper nor the User Name Mapper Class Name option, you can fix the problem at run time as follows:

    1. Shut down the Administration Server.

    2. Manually edit the config.xml file and set the Use Default User Name option to true.

    3. Start the Administration Server.

    4. Log on to the WebLogic Server Administration Console and configure the identity asserter correctly.

BEA XQuery Mapper

Problem ID



Pasting Expressions in the Expression Boxes in Constraint View Causes Error

When expressions are pasted in the left-hand or right-hand expression box in the Constraints view, a compilation error occurs.

Workaround: Instead, type expressions in the left-hand or right-hand expression box.


Undoing a Delete Operation of a Disabled Node Link Does Not Bring it Back

Disable a Target Node, which has a mapped link. Delete the mapped link of the disabled node. Now hit the Undo button in the XQuery Mapper. The Disabled Target Node link is not retrieved back. It is lost.

Workaround: Press CTRL Z a few times and the Undo will happen.


For a Recursive Element, Resultant Data is Not Properly Generated

The generated data for a recursive element is empty. Therefore, when you use such a generated recursive element, the resultant data is empty in the Test View on Run too.

Workaround: Correct the generated data and then run the Query.


Property Editor is Not Displaying the Properties of Variables in the Expression Variable Pane

The Property Editor does not refresh to display the properties for a variable when a variable is clicked in the Expression Variable pane—unlike the Design view nodes.

Workaround: You can obtain the property by hovering the mouse over the variable in the Expression Variable pane.


Closing and Relaunching of Expression Variable Pane Does Not Refresh with the Current Variables in the File

Open an XQuery file. Now close the Expression Variable pane alone by clicking the "x" button in it, and then relaunch the view. The view is blank and does not display the variables of the current XQuery file.

Workaround: Click on any target node in the Design view to refresh the Expression Variable pane.


Design View Is Not Able to Recover a Namespace Change

If an XQuery file is kept open while the schema files (used in the XQuery file) are modified with namespace changes, the Design view is not able to recover if the user switches to this view.

Workaround: Close the XQuery file and reopen the XQuery file after refreshing the project.


MFL Data Testing Unnecessarily Mandates the Availability of Unused XML Files

When the transformation file involves both XML and non-XML schema as inputs—even if the XML schema are not mapped for output—testing of such MFL transformation requires both the XML and MFL (non-XML types) source data to be available in order to perform testing. However, this is not the case with XML-only transformations.

Workaround: No workaround available at this time.


No Resultant Data for a Non-XML Element When Join Link is Present

The resultant data for a non-XML element is not correct when there is a join link. When the join link is removed, the resultant data is generated properly.

Workaround: No workaround available at this time.


The Signature of Built-in XQuery Functions Is Not Updated to the Latest Signature in the User Interface

The XQuery Mapper still displays old signatures for built-in functions as in the old engine—not the latest signature.

Workaround: No workaround available at this time.


Generate Data Generates Data for All the Choices

A choice element accepts only one data choice among the many choices at a given time. In the Test view, when you select Generate Data, data is generated for all the cases of a choice element. So a validation error occurs when data is generated for the choice element.

Workaround: Delete all elements except the one for which you wish to generate data.


Problems Opening Large XQuery Files in the Test View

The XQuery Mapper may hang, displaying the following message when attempting to open large XQuery files in the Test view: "Initializing... Please wait."

Workaround: Close the XQuery file and reopen it. Do not switch views while the file is being opened.


XQuery Mapper Online Help Example Document Displays Incorrect Output Data

A documentation error exists in Transforming Data Using the XQuery Mapper.
"Listing 3-3: Example Output Data" in the Creating Group By Key Fields XQuery Constructs example in the Eclipse XQuery Mapper Online Help displays incorrect data.

Workaround: The error is fixed in the version of the document available on See the Creating Group By Key Fields XQuery Constructs example at the following URL:


Changing a Join Condition from OR to AND Works Intermittently

In Eclipse, click on a target node item and right-click on any OR; then select Change Join condition to And in from the pop-up menu. Nothing happens.

Workaround: No workaround available at this time. However, this problem does not always occur. It is an occasional bug.


Back to Top Previous Next