Sun Java Composite Application Platform Suite 6.2 Release Notes

Sun Java Composite Application Platform Suite 6.2 Release Notes

Sun Java Composite Application Platform Suite (Java CAPS) combines technologies from Sun to form a modular and pluggable business integration platform that supports the complete spectrum of service integration requirements. Java CAPS includes repository-based core components and Adapters along with JBI Service Engines and Binding Components, giving you more options and greater flexibility in designing your composite applications. It uses NetBeans as the visual development environment, and the applications you create are deployed on the GlassFish Enterprise Server. This combination allows you to develop custom composite applications, Java EE applications, web applications, mobile applications, and web services using Java EE, JBI, and repository-based components.

The changes for this release are described in the following topics:

To access all the Java CAPS documentation in HTML and PDF format, go to the Sun Java Composite Application Platform Suite documentation page at

Operating System, External System, and Platform Updates

Java CAPS 6.2 supports newer versions of NetBeans and GlassFish Enterprise Server. In addition, release 6.2 provides support for new operating systems and external systems.

The following sections list the newly supported systems and platforms:

For a complete list of supported operating systems and external systems, see Java CAPS 6.2 Supported Operating Systems in Planning for Java CAPS Installation and Java CAPS 6.2 Components and Supported External Systems in Planning for Java CAPS Installation .

Design-Time and Runtime Platform Changes

This release of Java CAPS uses the following versions of NetBeans and GlassFish:

The supported JDK versions are 1.5.0_14 or later and 1.6.0_03 or later. For JDK version information for specific platforms, see Java CAPS 6.2 Supported JDK Versions in Planning for Java CAPS Installation .

Note –

JDK 1.6.0_13 and 1.6.0_14 are not recommended for use with Java CAPS.

Operating System Changes

This release of Java CAPS provides new support for the following operating systems:



Note –

Java CAPS 6.2 no longer supports AIX 5L 5.2. Red Hat Enterprise Linux is supported on both the basic Server and the Advanced Platform versions.

Browser and External System Changes

This release of Java CAPS adds support for the following browsers and external systems:


There are two paths to upgrade the Repository-based Java CAPS components from previous versions of release 6. In the first method, you install Java CAPS 6.2, export all projects from the older release 6 environment, and then import them into the new 6.2 environment. In the second method, you install Java CAPS 6.2, install a patch to update the older release 6 Repository, and then connect to the older Repository from the Java CAPS 6.2 environment. With the second option, you have a side-by-side installation, but you do not use the new Repository. Instead you continue to use the existing upgraded Repository.

The patch to upgrade the Repository is included on your installation media in patches/ The patch file is named For full upgrade instructions, see Upgrading to Java CAPS 6.2.

Changes and Enhancements to Java CAPS Components

The changes listed in the following sections provide enhanced functionality to the products or address issues in such a way that affects general usability of the components.

For a list of additional fixes to existing issues, see Issues Addressed in Java CAPS 6.2.

Java EE Component Changes and Enhancements

JBI Component Changes and Enhancements

Java CAPS includes the following new JBI features and components in this release. In addition, GlassFish clustering is supported for JBI components in Java CAPS 6.2; clustering support does not extend to Repository-based applications.

Changes and Enhancements to Repository–Based Components

Java CAPS includes the following changes and enhancements to repository-based components in this release:

Issues Addressed in Java CAPS 6.2

The following sections list the issues addressed by this Java CAPS release. The repository-based issues are listed in this document; links are provided for the JBI issues.

JBI Issues Addressed

Numerous updates were made to the JBI design-time and runtime components for this release. Below are links to the issues addressed for both design-time and runtime components.

The issues in the following table were also addressed for JBI components:

Issue ID 



Support for the following Data Integrator operators was not carried forward into Java CAPS 6: 

  • Normalize Name

  • Parse Address

  • Parse Business Name

  • Null If

  • Number to Hex

  • String to Hex


Runtime fails for a Data Integrator project if the ETL Collaboration contain flat-file tables. 


Refreshing database table metadata from an ETL Collaboration does not refresh the primary keys. 


When you launch the ETL Monitor, a blank page appears. 


When you select Purge All on the Data Integrator (eTL) Monitor, there is no confirmation dialog box for you to verify or cancel the purge. 


You cannot modify an application configuration for the FTP BC using the Admin Console. 


When using the HTTP BC and Access Manager, an error occurs when you try to authenticate against the Access Manager running on the HTTPS port. 


If you uninstall the LDAP BC from the GlassFish ES, you cannot reinstall it using the Admin Console.  


The CASA Editor does not allow you to disable all consumer ports in Binding Components.  

Repository-Based Issues Addressed

The following table lists and provides brief descriptions for the issues addressed for the repository-based components for this release.

Issue ID 



If the first patch installation for a given version uses the –basedir and –type arguments, subsequent patch installations fail if those two arguments are not used. 


For the Alert Agent, if “localhost” is used instead of “FQDN” for the application server host, the email alerts incorrectly indicate that the server is down. 


In the Alert Agent notification window, the text “undefined” appears where the alert type of component should appear. 


The alerts sent by a Collaboration are not correctly sent to the Alert Agent. 


The configagent URL (http://hostname:portnumber/configagent) throws an HTTP 403 error.

6741432, 6791279, 6817248, 6818090, 6721528, 6793310, 6688669, 6818531, 6795512, 6813828 

Code completion does not work correctly in several cases: 

  • For database OTDs

  • For the Batch Adapter

  • For IDocs for the SAP ALE Adapter

  • When an Adapter throws a codegen exception while creating OTD JAR files

  • When a JCD calls another JCD

  • In projects created prior to R5.1.3U4 that use XSD OTD with repeating nodes

  • For Excel OTDs and the COM/DCOM Adapter

  • With certain users or certain subpackages


Duplicate modules are installed in separate directories during the Java CAPS installation. 


The location of common library files is changed to be relative to the installation path for Java CAPS R6U1. If you import projects created in one Java CAPS environment into a different Java CAPS environment, they will have reference errors. 


A null pointer exception occurs when you open a Java Collaboration in a project that was imported from a previous version. 


The Java debugger does not stop on the specified breakpoints in Java Collaboration Definitions (JCDs). The debuggers throws an illegal state exception. 


When using JDK 1.6.0 with the Japan locale, Java CAPS fails to create a Logical Host and produces an XML error. 


A null pointer exception occurs during the build process. 


After a JAR file is exported and checked-in, an error occurs when you check out the exported file. 


When a Connectivity Map is copied, the UUID is reused for the Batch Adapter. The Adapter uses the UUID to store the state file. 


An Adapter developed using the Sun Adapter Development Kit throws a null pointer exception when the Adapter properties are modified on the Connectivity Map. 


An illegal state exception occurs when an imported JAR file is updated. 


With both NetBeans and GlassFish ES running on Solaris, an IAS deployment exception occurs when deploying an application. 


Compiling a JCD that uses a WSDL document throws a JaxRpcCodelet exception.


If you edit the HL7, File, or Batch external system properties and then check in the components, you cannot view the properties again. 


Large Java Collaboration Definitions take a long time to open in the Java Collaboration Editor. 


An incorrect class named used by the Java Collaboration Editor causes compilation to fail. 


When a method in a JCD throws an exception and does not include the throw clause, the Java Collaboration Editor does not detect the missing clause. The build process fails. 


A stack overflow error might occur when you try to import a JAR file to a JCD. 


The validation window for the JCD code validation no longer includes links that take you to the location of the error in the JCD code. 


JCD validation fails for some SAP BAPI RFC OTD methods when the JCD is relaunched. 


When you expand OTD nodes to add a string literal to a field, the OTD tree collapses when you select String Literal and you have to expand the nodes again. 


The New Project Wizard is displayed in English when using the Japan locale. 


The CAPS repository menu is displayed in English when using the Japan locale. 


The OTD Tester and JCD Editor cannot be opened when Shift_JIS, EUC_JP, MS932, UTF-8, or ASCII is set for antecoding, encoding, decoding, and postcoding. An unknown encoding name error occurs. 


The XSD OTD Tester hangs intermittently. 


When using the OTD Tester on custom HL7 OTDs with imported nodes, extra fields appear in the OTD nodes and messages are mapped incorrectly. 


In the XSD and DTD OTD Testers, Big5 encoding does not appear in the encoding list. 


When using Java CAPS on Japanese Windows 2003, you cannot select Topic in the Enterprise Manager. 


Email alerts are not generated when the application server stops responding. 


When you shut down Enterprise Manager, not all related processes are stopped. 


Enterprise Manager is slow to display the list of servers. 


Enterprise Manager continues to display the old server log from the original location after the location is changed. 


Enterprise Manager needs to support publishing messages to a JMS Grid daemon that is configured for SSL. 


Custom alerts sent by a JCD cannot be viewed on the Enterprise Manager. 


On the Manager Servers window of the Enterprise Manager, the application server username and password appear in text instead of being encrypted. 


When several domains are being monitored in Enterprise Manager, the domains' status may change to “UNKNOWN” and Enterprise Manager must be restarted in order to continue monitoring services. 


The Enterprise Manager displays “NA” for the Last Published Date/Time for queues and topics when Enterprise Manager is in a different locale from the Logical Host. 


The server log displays the following error as a result of miscommunication between Event Management and Application Deployer: 

Access denied for user: Password is invalid.


Enterprise Manager no longer received alerts after the domain is restarted. 


An email alert should be generated when the application server starts up. 


When running Java CAPS on the Traditional Chinese locale, most components show English language messages on the GlassFish Admin Console. 


When you delete a queue in a Sun Message Server using Enterprise Manager, the message server pauses and does not recover. All subsequent connection attempts fail. 


You cannot use Enterprise Manager to republish journalled messages. 


An email alert should be generated when the application server shuts down. 


The new Enterprise Manager web application, Configurator, requires Japanese translation. 


Command line codegen fails on Linux platforms. 


Importing a Web Service Definition fails with a runtime validation exception. 


When a WSDL document from a JCD is factored into a BPEL project (so the business process can invoke the JCD web service), the WSDL document that is generated by building and deploying the BPEL project is incorrect. 


Running the asadmin extract-caps-application-configuration command does not generate the Connectivity Map properties file.


When you expose a web service hosted on GlassFish, the WSDL file is redirected to an incorrect file. 


When a SOAP fault response contains non-ASCII characters, those characters are transmitted incorrectly, generating the following error: Invalid byte 2 of 3–byte UTF-8 sequence. 


There is a JMQ login failure between GlassFish ES and the remote JMQ broker if the passwords in the Connector Connection Pools are encrypted. 


JAX RPC does not handle the nillable attribute “xsi:nil” correctly, causing a namespace error after a call to an external web service. 


The delay in milliseconds and the number of encounters for JMS JCA redelivery attempts is restricted to 5000. This limit should be removed. 


JMS JCA activation fails with a connection leak, which in turn causes a memory leak in JMS Grid. 


On the JMS JCA Wizard, the concurrency mode options are incorrect. They should be serial, cc, and sync. 


It is not possible to use JMS JCA message-driven beans to look up managed connection pools using lookup://ResourceName in repository-based projects.


Expired JMS messages still appear in Enterprise Manager and the control utility for a short time. 


You cannot change the default stcms.log file location because the log file name is overridden during initialization.


After an in-doubt transaction is rolled back for a queue receiver, the messages are included in the message count for the queue again but they are not redelivered. 


After an in-doubt transaction is recovered, database references for the transactions are not cleaned up. This causes the size of the database files to increase. 


After messages fill a database file and a new file is created, the synchronization might not be up to date. This means that if the server is restarted, messages are redelivered resulting in the following error: Duplicate Message On Restart.


When using an older stcjms.jar client to receive JMS messages from an STCMS queue, a persistence optimization fault occurs when the client commits on receiving. Also, when the domain hosting the STCMS is restarted, the consumed messages are not marked as having been consumed.


When the JMS service is shut down using stcmsctrlutil, the application server interrupts all blocking JMS client threads and the clients throw an interrupted exception.


Running stcmsctrlutil.exe against the STCMS server generates poller errors.


The circular list on which the backlog manager's log action list is based is not thread safe. 


An STCMS client Ping Runner might incorrectly close sockets that it does not own when socket pooling is enabled. 


The TxLogManager is unable to delete an empty database file, causing a break in sequence numbers on startup. The STCMS log shows a broken pipe error. 


The raunifiedjms.jar file needs to be updated with the latest version of stcjms_453.jar.


Several JMS Ping Runner threads cause an out of memory error. 


Running the command asadmin restore-stcms does not restore the STCMS instance on Solaris and Linux.


The STCMS IQ Manager stops processing messages and eventually crashes with a core dump. 


STCMS might have excessive memory usage due to memory fragmentation under heavy loads, and the server will stop responding. 


When journalling is enabled, the following message appears in stcms.log on startup:

StartupMessageLists() : MessageQueue with id=xxx was deleted


Include Java Message Queue 4.2 or later with Java CAPS. 


During heavy stress tests, the application server might experience ping timeouts and forcibly disconnect client connections. 


If you undeploy and redeploy a business process while a transaction is in process, the application server becomes stuck in a continuous loop until the domain is restarted. 


When the network connection on a JMS client is disabled before the STCMS server receives a ping message on the socket, the socket remains established and is not cleaned up. 


When the number of messages in the JMS server reaches the ServerMaxMessage value, throttling begins and the insert rate is reduced.


Duplicate JMS message are produced because in-doubt transactions are not recovered properly. 


The journaller might incorrectly overwrite the backup LSN for a queue or topic in the backup.log file, causing duplicate backups of the same messages.


Java Message Queue message redelivery does not work when the destination is a queue and the source is a topic. 


Messages are not picked up from a JMS queue when the receive method is used with multiple client instances.


When the setClientId method tries to change the client ID, an exception (javax.jms.IllegalStateException) should occur.


JMS is unable to process large messages on Windows Server 2003 running in 64–byte mode. 


JMS messages are lost on restart when multiple subscribers with different message selectors subscribe to the same topic. 


The JMS server duplicates sequence numbers when message selectors subscribe to the same topic. 


When message selector is used and some subscribers do not match the selector, the server might use invalid message location information on restart to skip these messages, causing the server to stop responding. 


When using the ESB API Kit in a request/reply scenario, the IQ Manager leaks memory and requires frequent restarts. 


When an ESB API Kit for C/C++ client connects using SSL, the QueueReceiver.receive and QueueReceiver.receiveNoWait methods throw exceptions.


For the ESB API Kit for COBOL, the JMSEMAP.COB and JMSOMAP.COB files are in EBCDIC but should be in ASCII.


An error occurs while running the ESB API Kit for COBOL sample, JMSRQRP. 


An error occurs when you import an OTD template using the OTD Editor. 


Data is parsed incorrectly in DTD OTDs created from a DTD that contains an element of the type “ANY”. 


In NetBeans, the copy option from the drop-down menu does not work for HL7 OTDs. 


The methods for an Oracle OTD table node do not appear in the auto-completion list in the Java Collaboration Editor. 


If you add elements from external templates to a user-defined OTD, the OTD Editor fails to load the OTD. 


The EDIFACT OTC Library cannot be accessed from NetBeans. 


Unmarshalling for an EDIFACT message does not work when special mask characters appear in the message. 


The marshal process for an EDIFECT OTD does not preserve the leading zero before a decimal point. 


The Oracle OTD Wizard displays duplicate rows for a table if the table has multiple synonyms. 


When you modify an Oracle or Sybase prepared statement in an OTD, the parameter names all reset to param1, param2, and so on. This breaks any code that uses the prepared statement. 


When you modify an Oracle or Sybase prepared statement in an OTD, the updates are not saved. 


An exception occurs when you select the java.sql.ARRAY type for the return parameter when using the OTD Wizard to create an OTD from a procedure.


In an ASC_X12 OTD, an unmarshall exception is thrown when trying to unmarshal a node defined as “ANY” with xsi:type=”ST”. 


XSD OTD unmarshal process runs slowly. 


Using to relaunch an XSD OTD from the command line fails.


Relaunching an XSD OTD from the command line checks out the OTD automatically. 


After the marshal process for an XSD OTD, additional characters appear in the parsed data. 


If you import a project that includes a custom OTD and a business process from Java CAPS 5.1.1, a runtime exception occurs when you run the deployed project. 


Multiple enhancements to the validation OTD and Collaborations for SWIFT. 


Some private methods are used by not generated in validation Collaborations for MT fields in the SWIFT OTD libraries. 


There are parsing errors for the following two similar patterns: “cv/ 160–288h ls” and “CV/ 160–288h )”. 

6765321 6755499 6867642 

Multiple fixes to MT fields in the SWIFT 2008 OTD Library. 


In the SWIFT OTD Library, field 40E fails to parse for MT700, MT710, and MT720. 


The command-line build process fails for a project that contains a MT541 OTD from the 2008 SWIFT OTD Library.  


SVR rules in SWIFT OTDs need to be updated. 


Multiple fixes to the SWIFT 2008 OTD Library. 


The SWIFT OTD Library is not working in a BPEL use case scenario.  


An error occurs when unmarshalling a SWIFT MT300 message using the Unmarshal From String button on the OTD Editor. 


The SEF OTD Wizard does not generate the SEF OTD. 


The COBOL Copybook Converter handles “OCCURS” incorrectly in a redefined item, which might result in wrong data being unmarshalled to a repeating node in the generated OTD. 


Extra fields appear in the OTD Editor after dragging the same OTD from the external templates twice. 


When an OTD contains recursive nodes, NetBeans stops responding when you try to map the fields. A severe heap-size error occurs. 


A Java Collaboration Definition (JCD) cannot be created for the COM/DCOM Adapter. 


Weblogic OTD methods are not available to be called from a JCD. 


When using an XSD OTD with two elements, each having a child and sharing the same name, changing an attribute in one of the elements also changes the attribute in the other element. 


A compiling error occurs when a remove method is called in an OTD generated from an XSD, even though the method appears in the generated OTD class and appears in the method completion dialog box.


The Command Line Branch Installer Tool needs to be added to version 6.2.  


The SwiftOTDLibrary2008.sar file cannot be installed on a machine that has multiple IP addresses.


Patch installation fails when a custom administrator username and password are used. This release adds two new options to the patch installer: -repuser and -reppwd.


When you import a project that uses Java CAPS components that are not installed, the import process fails with no warning. 


When there are multiple repository branches running on the Chinese locale, you cannot change to a different branch in NetBeans. 


The repository project import tool is not working correctly, either from the command line or IDE. 


Performance is slow on the NetBeans IDE when working with a remote Java CAPS repository. 


You cannot use “data” as part of the repository name. 


A “missing port information” exception occurs when a project contains a JCD exposed as a web service, which in turn invokes a second JCD exposed as a web service. 


A null pointer exception occurs when trying to view WSDL provider details in the UDDI Registry. 


The tool buttons on the WSDL Binding Editor are not visible. 


SQL 2000 and SQL 2005 stored procedure result sets always display 0 (zero) and cannot be edited in the WSDL Wizard. 


Invoking an SSL-enabled web service from a JCD client fails because it attempts to invoke the incorrect ENDPOINT_ADDRESS_PROPERTY.


When working with the Chinese or Japanese locale, you cannot create a correlation set for a business process. 


When working with a Chinese locale, you cannot set the Use Correlations property in the Business Process Manager Editor.


On AIX domains, log messages change depending on the logging levels and the SOAP response does not match it's defining WSDL file in a Business Process Manager project. 


In NetBeans, you cannot save changes to a BPM database script that was modified externally. 


Building a project containing a business process fails with a codegen exception. 


If a JCD in a business process throws an exception, the Enterprise Manager does not show the failed JCD in red. 


Tasks are not listed on the Worklist Manager for any user with the Manager role. 


After making changes to a Composite Page Designer page flow, you cannot save the changes. 


A Composite Page Designer page-flow applications stop responding after a popup window is closed. 


When you create non-JMS connector connection pools using asadmin commands with the default properties, the connection pools do not appear under the CAPS node on the GlassFish Admin Console. 


When an Adapter throws a CodeGenException, code completion is disabled without any information about the cause of the exception.


A null pointer exception occurs when you import a 5.0.5 project and try to migrate a Batch eWay module. 


The Batch SFTP Adapter stops responding when the server is unresponsive. The get method performs slowly.


The JCD Tester does not work for Collaborations that contain a Batch FTP OTD. 


The Batch SFTP Adapter stops responding when the application server becomes unresponsive. The Adapter is also experiencing delays when calling the get method.


The get method in the Batch Local File OTD does not perform post-transfer commands if Synchronization is set to “no” in the Connectivity Map.


A Batch SFTP project stops responding after processing 1000 messages, and the domain main process stops responding as well. 


When the specified file is not found by the Batch Adapter, the FileNotFoundException is not captured when the TargetFileNameIsPattern property is set to false.


When using a Batch SFTP External Application to connect to a Serv-U SFTP server, the connection fails and an SftpStatusException is thrown.


Batch Local File External Applications incorrectly concatenate the drive letter to the UNC path, so the Adapter is unable to write the file to the specified location. 


The Batch SFTP External System throws an exception when connecting to MySecureShell SFTP server. Part of the solution to this is to set SFTP version 3 as the maximum SFTP protocol version to be used by the client. 


The sample provided for the Adapter Development Kit does not work correctly. 


Projects created with Adapter Development Kit components cannot be opened in Java CAPS 6.2. 


The NBM files for Adapters created by the Adapter Development Kit fail to build. 


When the Adapter Development Kit is used to create a new Adapter with custom icons (that is, not the default image files), the code generation fails. 


When the Adapter Development Kit is used to create a new Adapter, the Adapter SAR file fails to build. 


A null pointer exception occurs when DB2 Connect Type 4 drivers are used to access a result set returned from a stored procedure. 


The Statement.setQueryTimeout method is not supported for mainframe DB2 drivers.


Connections to DB2, SQL Server, and Oracle intermittently experience very long delays. 


A BPEL project with an eMail Adapter fails at runtime with the following error: NoClassDefFoundError:PersistentBeanMEssageWrapper


The eMail Adapter throws an exception when processing multipart/related messages and does not process subsequent messages. 


For the HTTP Adapter, a call to input.getRequest.getText returns null even if the message contained text.


For the HTTP Adapter, a call to the post method throws a null pointer exception.


Under heavy loads, the HTTP Adapter produces the following error: Internal Server Error – 500. 


When using an HTTP Adapter server project with basic authentication, deployment fails with an exception. 


When a JCD connects to Informix, the JCD does not reconnect if the connection to Informix is broken. 


When Sun Java System Application Server is the deployment target, the Connection Pool Settings properties for the LDAP Adapter are ignored. 


The build process fails for a Composite Application that includes a JBI Bridge project. 


The application server throws an “instance not found” exception when deploying a Composite Application that includes a JBI Bridge project. 


The Admin Console stops responding when you create a Connector Connection Pool on Solaris 10, zh_TW locale (Traditional Chinese). 


When using the JDBC/ODBC Adapter to invoke a DB2 procedure with several IN and OUT parameters, a SQL error occurs. This is due to the clearParameters method.


The command asadmin extract-caps-application-configuration does not work for the WebSphere MQ Adapter.


With JDK 1.6 versions, Environment Override does not work for the Oracle Adapter after running the asadmin extract and asadmin import commands on the project's EAR file.


When you import a 5.0.5 project that includes a SAP eWay, the import process stops responding and has to be ended manually. 


The SAP Wizard fails and throws an exception due to an issue with sapjco3.jar backward compatibility.


When the SAP BAPI Global RAR is used in inbound mode with JCo 3, an abstract method error occurs. 


The SAP BAPI Adapter does not auto-commit when used in non-transactional/Transactional (tRfc) mode. 


When a SAP BAPI OTD is relaunched, the JCD using that OTD no longer works. 


When a SAP project is imported from ICAN 5.0.5, the JCD fails validation and cannot be built. 


On the SAP IDoc Wizard, the List IDocs button does not display all IDocs in the system. 


The Sap IDoc Wizard allows you to select unsupported versions of SAP. 


TCP/IP Adapter projects fail with a NotSerializableException.


The order of the database columns in a business process is different than the order in the SQL Server OTD. 


The TCP/IP Adapter methods app.getSocket().getInputStream() and app.getSocket() dispose of the first 1024 bytes passed to it.


Port numbers for the TCP/IP Adapter are logged incorrectly (they include a comma). 


An invalid descriptor error occurs when deploying some Composite Applications. 


Frequent class cast exceptions are thrown on HL7 connections when multiple HL7 projects are running on the same server. 


With the TCP/IP HL7 Adapter installed, projects that were upgraded from Release 6 fail to deploy with an “invalid archive descriptor” error. 


Autoboxing is supported in Java CAPS, but the code does not compile for JCDs in repository-based projects.  


Deploying a project that uses the Unified Resource Adapter (URA) is deployed throws a an exception, ClassNotFound Exception.


The ECRC file needs to be synchronized in all user's userid directory. This file should be stored in one location in the NetBeans home directory.


The Scheduler might start at an incorrect time when set to Weekly by Day. 


An Access Control List (ACL) cannot be removed from a project. 


When a user is removed through User Management in NetBeans, the user persists after the IDE is restarted because the ACL is not updated. 


If you select the spreadsheet view on a Deployment Profile, all fields display “Invalid Data”. 


An out of memory exception occurs during deployment and redeployment of a Batch Adapter project. 


The logical host randomly fails with an index out of bounds exception. 


If on the Admin Console you select Application Server, the Monitor tab, the Runtime tab, and then any View option other than JVM, an HTTP 404 error occurs. 


A generated WSDL document does not create SLL and user token elements. 


A web services project imported from version 5.0.5 fails to build in Release 6.2. 


When using a token and SSL connection, the web service throws a socket exception. 


The response from a web service operation cannot be parsed due to “nil” dateTime elements, and an unmarshal exception occurs. 


An error occurs when sending a web service request that contains the text xsi:nil="true" on AIX.


An LDAP reference used in a web service client environment property is interpreted literally. 


A web service client project throws a null pointer exception during runtime. 


Web service response time is slow. 


Escape characters contained within XML elements of SOAP requests are being escaped twice,  


When multiple web services are invoked from JCDs and each WSDL document has the same target namespace, the projects cannot be built due to non-unique package and class names.  


You cannot send nullable elements to a web service. 


Unable to retrieve the SOAP fault message after invoking a web service from a JCD. 


Invoking an external web service fails when the response contains a datetime element with an empty value. 

Master Data Management Issues Addressed

The following tables list and provide brief descriptions for the issues addressed for master index components for this release.

Table 1 Sun Master Index (Repository) Issues

Issue ID 



When using keyless child objects, the SBR duplicates some of the child objects. 


The getEUID method throws inappropriate null pointer exceptions. With this fix, getEUID behaves as follows:


  • Given a valid facility and LID, getEUID returns the EUID.

  • Given a valid facility and invalid LID, getEUID returns null.

  • Given a valid facility and an LID that does not match the required format, getEUID throws a validation exception.

  • Given an invalid facility, getEUID throws a validation exception.


If an identifier that is too long is passed to getEUID, a null pointer exception is thrown instead of a validation exception.


You have to modify runed.bat in order to run a Master Index client project.


The value of the max-result-size property for EDM reports is being overridden by a default value of 100.


From NetBeans, you cannot save changes to the database or configuration files. 


After importing a 5.1.3 eView project, the Sun Master Index External Application is not recognized in the client deployment profile. 


The Enterprise Data Manager (EDM) does not display fields that contain double-quotes correctly. 


Installing Sun Master Patient Index creates multiple eView.Person objects beneath the Master Patient Index projects. 


The resolved date for potential duplicates is not stored in the Master Index database. 


Serialization of MergeResult and TransactionObject objects does not work when the client is run from a different JVM.


The ObjectNode.equals(Object o) method does not take the class into account when comparing objects, resulting in false positives.


Master Index has trouble initializing when running with a JRE version 1.5.0_14. 


An EJB exception is thrown when trying to create the first record in a master index from the EDM. This occurs with JRE 1.5.0_14. 


The cursor is not positioned correctly when a new page on the EDM is displayed. 

Table 2 Sun Master Index Issues

Issue ID 


Issue 160

Outbound messages from Master Index are missing the create date and update date values. 

Issue 189

The MIDM Audit Log currently displays the create date as a date rather than a timestamp. There can be many transactions within a short period, so a timestamp would be more useful. 

Issue 212

When an address field is added with an apostrophe in the text, the field cannot be edited. 

Issue 219

The banner for the Information dialog box that appears when you tab away from the Edit Source Record window is partially hidden. 

Issue 222

The generated outbound.xsd file is unusable in NetBeans. The following lines were added to address this:

xmlns:tns="uri:PersonOutMsg" targetNamespace="uri:PersonOutMsg"

Issue 229

The transaction reconstruction for Master Index is inefficient. In addition, the timestamp is only to the second, which can lead to an exception when two transactions are processed in the same second. 

Issue 237

The Transaction Detail does not display when the EPath parser finds invalid characters. 

Issue 240

If the same code list is being used for more than one field on the MIDM, then the generated codelist.sql file will contain that code list more than once. This causes an error when running the script.

Issue 255

The update.xsd file that is used to validate update.xml does not allow fields to be specified in the system-fields element in the survivor calculator.

Issue 257

Fields that are defined as not editable can be modified through the Source Record View/Edit window. 

Issue 272

The resolved date for potential duplicates is not stored in the database. 

Issue 278

The outbound JMS message XML does not have a namespace. 

Issue 287

The Clear buttons for child objects on the Source Record window do not work consistently.  

Issue 293

A remote call to the Master Controller EJB fails on merge methods because the result object cannot be instantiated on the client. 

Issue 295

Data enclosed in square brackets cause a validation error in the FieldDescriptor.validate method.

Issue 298

When a field contains data of the type Long, the text covers the next record. To prevent this, Long data fields only display 20 characters. If the field contains more characters, an ellipsis (...) appears at the end of the data. Mousing over the ellipsis displays the full text. 

Issue 304

The generated outbound,xsd file has maxOccurs=”1” for the SBR element. Some transaction types have two SBR elements.

Issue 309

The Print button on the Transactions window does not appear correctly. 

Issue 312

Transaction History on the MIDM does not work correctly with Firefox 2.0.x. 

Issue 322

When the system and local ID are displayed on the Transaction History and Audit pages, the local ID is displayed first. Since the formatting of the local ID is dependent on the selected system, the system field should appear first. 

Issue 324

The MIDM does not allow variable local ID lengths. 

Issue 325

The topic connection is not closed when the EJB call that triggers an outbound message completes, resulting in too many open connections. A processing exception is thrown. 

Issue 332

Non-updateable fields do not appear on the Potential Duplicate report. 

Issue 334

When Master Index generates outbound messages, it includes deleted child objects in the message even though they are flagged as being removed. 

Issue 335

When you clean and build an MDM project, the properties are rest for the corresponding EJB project, which removes any custom changes including the additional of JAR files. The EJB project will no longer compile. 

Issue 341

The error message is not displayed in certain cases of SEQException, so the cause of the exception is not apparent.

Issue 344

The SBYN_MERGE database table should have an index on the merged_euid column. 


Range search fields should be arranged more clearly on the MIDM search windows. 


A record's history displays incorrectly after an unmerge transaction.  


When a record is updated while you are viewing its transaction history on the MIDM, you are not alerted that you are no longer viewing the most current information. 


When you enter a field name with more than 20 characters, a message appears warning of an Oracle limitation. This limitation also exists for MySQL databases, but can be removed since MySQL does not have the same limit. 


The field labels and field values look too similar on the MIDM Records Detail page.  


When you enter an invalid local ID on the Duplicate Records page on the MIDM, an error message appears. When the error message is closed, you cannot click on the local ID field to fix it and the System field is cleared. 


A null pointer exception occurs as a result of a multi-threading issue in the Sun Match Engine and on TransactionObjectDB. 

Known Issues in Java CAPS 6.2

The following sections list and describe the known issues in this release. Work-arounds are also documented where applicable. In the following sections, links are provided to issues that originated in the OpenESB project, and “CR” refers to the change request number for an issue.

Known Issues for Adapters

The following are known issues for Sun Adapters:

Known Issues for the BPEL Service Engine

Note –

For BPEL SE stop and restart issues, see Known JBI Management Issues.

The following are known issues for the BPEL Service Engine:

Known Issues for Composite Page Designer

The following is a known issue for the Composite Page Designer:

Known Issues for the Data Integrator Service Engine

The following are known issues for the Sun Data Integrator Service Engine:

Known Issues for the Data Mashup Service Engine

The following are known issues for the Data Mashup Service Engine:

Known Issues for the Database Binding Component

The following are known issues for the Database Binding Component:

Known Issues for the Enterprise Service Bus

The following are known issues for the Enterprise Service Bus:

Known Issues for the File Binding Component

The following are known issues for the File Binding Component:

Known Issues for the FTP Binding Component

The following are known issues for the FTP Binding Component:

Known Issues for the IEP Service Engine

The following are known issues for the IEP Service Engine:

Known Issues for Java Application Projects for JAXB

The following is a known issue for Java Application projects with JAXB:

Known Issues for the JBI Bridge

The following are known issues for the projects containing a JBI Bridge:

Known Issues for the LDAP Binding Component

The following are known issues for the LDAP Binding Component:

Known Issues for Sun Master Index

The following is a known issue for Sun Master Index projects:

Known Issues for the XSLT Service Engine

The following are known issues for the XSLT Service Engine:

Known Issues for Composite Applications

The following are know issues for Composite Application (CA) projects:

Known JBI Management Issues

The following are known issues in managing JBI components:

Known Localization Issues

The following are known localization issues:

Known Installation and Startup Issues

The following are known installation issues:

Known Interoperability Issues

The following are known interoperability issues:

Known NetBeans Issues

Known GlassFish Enterprise Server Issues

Known Issues for JBI Clustering

The following are known issues for working with Java CAPS JBI components in a clustered environment:

Other Known Issues