Closed Issues

The following are the closed issues in this release of TIBCO ActiveMatrix BusinessWorks™.

The closed issues are grouped by components:

Administration

Release 6.6.1

Key Description
AMBW-38710 External Profile failed to update application properties when some changes were made to the profile and the same profile was uploaded again.
AMBW-38598 Backup and restore of a domain did not preserve configuration settings for an AppSpace.
AMBW-38541 The Jetty server version was not hidden when a BWAgent's information was requested using a REST API.
AMBW-38465 The bwagent-access.log file was not created at BWAgent level in TIBCO ActiveMatrix BusinessWorks™ 6.5.x and 6.6.
AMBW-38291 BWAgent failed to start with the databases, where the permitted size of the primary key was less.
AMBW-38239 When an application was deployed on Admin UI, the complete XML tags in the log file were not displayed after clicking the View Online option available. Whereas, the Download option available for Log File displayed the values properly along with XML tags.
AMBW-37989 When a non-password type module property was updated, all fields of type password were changed to a garbage value on the Admin UI.
AMBW-37709 The REST API could not retrieve configuration details of an AppNode.
AMBW-37659 BWAgent did not work with FTL 6.x server.

Now BWAgent works with FTL 6.3 and higher versions.

AMBW-36954 After deleting the ActiveMatrix BusinessWorks™ application archive either from BWADMIN CLI or Admin UI, the corresponding entries from the bwprocess table were not deleted.
AMBW-33259 The creation of the appspace or appnode on the remote machine using REST API failed with the following errors:
  • For appspace: { "message": "Agent [bwin2k864b-54] is not part of the Domain [d2].", "code": "TIBCO-BW-ADMIN-500111" }
  • For appnode: { "message": "The registration of BW Agent to the domain [d65] failed. Cannot create AppNodes in the AppSpace [a65] on the remote BW Agent [bbwin2k1664b-65]", "code": "TIBCO-BW-ADMIN-500226" }

Release 6.6.0

Key Description
AMBW-36934 The running application instance details were not visible as App Instances view could not be expanded on the Application level 2 page on Admin UI.
AMBW-36739 OSGI commands failed to execute through Admin CLI when BWAgent was configured in DBEMS mode.
AMBW-36508 A module property of type password had a garbage value when it was just selected for modifying a value, but not modified, and any other module property was modified on the Admin UI.
AMBW-36208 An AppSpace property reverted to its original value when the other AppSpace properties were added or modified.
AMBW-35617 When an application was started or stopped multiple times, there was some discrepancy in displaying application status from Admin UI, Admin CLI, and REST API.
AMBW-35415 An incorrect error was displayed during BWAgent startup.
AMBW-35413 The Applications view on the Admin UI displayed errors even when application instances were running properly.
AMBW-35239 The name of the profile was reset to default in the Admin UI when a module property value was changed.
AMBW-35236 Applications failed to start on AppSpaces with the same name across different domains.
AMBW-35106 The BWAgent configured with DB or EMS took considerable time while running backup scripts.
AMBW-35063 When the EMS server was restarted, the machine status and the BWAgent status was changed to unreachable in the Admin UI.
AMBW-35006 The BWAgent failed to register when a TIBCO Enterprise Administrator(TEA) agent had a default value as 0.0.0.0, and the BWAgent was configured with Database with TIBCO Enterprise Message Service™.
AMBW-34936 An application endpoint URL was not populated in BWAgent REST API call when BWAgent was configured with DB and EMS. However, it was populated for BWAgent was configured with ActiveSpaces.
AMBW-34935 The Admin UI displayed promoted module properties for an application as undefined%.
AMBW-34929 The Deploy application REST API method returned a huge response.
AMBW-34423 The StatisticsProvider is not yet initialized error occurred on the BWAgent console when the AppNode was in the running state and the BWAgent was started.
AMBW-33978 The browse domains REST API call with the flag full=true returned different response than that of swagger document.
AMBW-33847 The incorrect response was received during the start or stop of an application using BWAgent REST API.
AMBW-33833 An application took more time to stop than anticipated and the REST API Stop command returned a response even when the application had not stopped completely.
AMBW-33765 A REST API call now generates a URL with applications instead of apps. For example: "href": "http://SERVER:8079/bw/v1/domains/Domain_PT_01/appspaces/AS_PT_01/applications/PT_OAUTH_Token_v1-service.application/1.0"
AMBW-33690 You can now update the agentrequesttimeout property using bwagent_db.json and bwagent_ftl.json and all other timeouts are derived from it.
AMBW-33203 After EMS failover, if EMS is configured using json file, and the bwagent is restarted after restarting the failed EMS server, the bwagent can not start, and displays Duplicate member error.

In the bwagent.ini file, the active EMS server should be the first one in the URL, and then restart the BWAgent.

AMBW-32706 If a BWAgent was configured to use process monitoring via UDP, then after closing BWAgent from console, an error was displayed on Admin CLI.
AMBW-32705 Unnecessary information is not displayed in a BWAgent log as it is now moved to DEBUG level.
AMBW-32699 The BWAgent REST API now has all the fields that bwadmin exposes. The new option -description is added in a swagger UI.
AMBW-31451 After performing any action on any page of Admin UI, pagination redirected to first page.
AMBW-27163 The unregisteragent command to unregister an agent from a domain did not work.
AMBW-22169 The BWAgent considered Windows Internet Explorer browser settings for a file path when uploading an .EAR file.

Release 6.5.1

Key Description
AMBW-34241 A REST API returned an incorrect response code when you tried to stop an application that was already in a stopped state.
AMBW-34005 An application failed to start with MySQL database installed on a Linux platform.
AMBW-33804 In the show command of bwadmin, the domain name was case sensitive.
AMBW-33803 An AppNode runtime information could not be retrieved on a non-domain agent's AppNode level 2 page in a graph view.
AMBW-33800 The custom OSGi plug-in could not retrieve data about process statistics from TIBCO ActiveMatrix BusinessWorks™ 6.5.0.

Bindings

Release 6.6.1

Key Description
AMBW-39809 A whitespace character was returned in the <soapenv:Header> element of a SOAP Response even though no SOAP header was configured on the SOAP service.
AMBW-39501 The HttpCommunicationFaultElementException was thrown for a SOAP reference binding when a SOAP request was sent after selecting the Confidentiality check box and the Apache HttpComponents implementation library in the HTTP Client shared resource.
AMBW-39308 Failed to create DocumentBuilderFactory for parsing xml schema source org.xml.sax.SAXException was thrown when a runtime concrete WSDL was retrieved repeatedly.
AMBW-39212 WstxParsingException was thrown on a SOAP reference binding when a SOAP request was sent by selecting Authentication and Confidentiality check boxes in the HTTP Client shared resource with Apache HttpComponents library.
AMBW-39072 Generating concrete WSDL from browsers created invalid WSDL when WSDL inline schema elements referred from namespace defined in WSDL definition.
AMBW-39064 The Null Pointer Exception was thrown during swagger to XSD conversion for an element of type : "object" without "properties".
AMBW-39063 If two or more REST applications shared the same HTTP Connector shared resource from a shared module, and whenever one of the applications was undeployed and redeployed again, then the REST service stopped working.
AMBW-38930 The job data for all activities after the Invoke activity was not displayed in the Debug perspective.
AMBW-38561 The MESSAGE_NOT_MATCHING_DEFINTION error occurred when a REST binding service returned a faulted response to the REST reference binding's Invoke activity and the Use HTTP Headers check box was selected at REST reference binding.
AMBW-38554 When a REST service was created from a swagger file, which had nested objects and those objects were referred from outside their parent object, a wrong XSD was generated with the following error:

REST Schema to XSD Schema conversion error: com.tibco.bw.swagger.model.exceptions.SwaggerError

The property called roles contains neither a 'type' nor '$ref' property, which is not supported.

AMBW-38478 TIBCO Business Studio™ for BusinessWorks™ displayed a Null Pointer Exception when a WSDL file location or a name was incorrect in the SOAP over JMS reference binding.
AMBW-35022 The service interface configuration was not visible when the concrete WSDL was generated at design time by clearing the Abstract WSDL check box on the Concrete WSDL Generation Wizard.
AMBW-26977 When a custom HTTP header for the Rest - OPAQUE implementation was added, the following error was displayed:

Description Resource Path Location Type REST Service Binding configuration error. The REST service binding [RestService1] specified for the process service [op] in the process [fasttesting.module.op] is not configured correctly.

The part [httpHeaders] configured for the input WSDL message in the operation [post] must be of type [{http://tns.tibco.com/bw/REST}httpHeaders]. module.bwm /Fasttesting.module/META-INF Unknown EMF Validation Problems .

Release 6.6.0

Key Description
AMBW-37322 Invalid format for type errors were thrown on creating a REST service from a swagger document. Also, null pointer exceptions were thrown when an element of object type was created, without populating its properties value.
AMBW-36994 The Reverse Proxy Host or Port was not updated in the endpoint URL, if a Concrete WSDL was generated at run time. To get the updated host/port at design time, we have configuration fields for host and port on the Concrete WSDL Generation Wizard.
AMBW-36863 When an unbound fault was added to the header in a SOAP service, the following exception occurred after invoking the service:

Failed to process Declared Fault Message for Operation.

AMBW-36269 When you create a REST service with Swagger file, which has a non-standard OpenAPI Specification format, the design-time errors were displayed.
AMBW-36057 When a Compression check box of the HTTP Connector shared resource was selected, POST responses for REST services were not compressed.
AMBW-35898 If the WSDL definition had a schema imported from a shared module, a concrete WSDL could not be generated from URL.
AMBW-35279 The HTTP Exceptions thrown by the SOAP Invoke activity were not caught in the Catch block of the particular HTTP Exception.
AMBW-34796 The security header was not available as the undescribed header for SOAP.

Set the property bw.governance.removesecurityheader.disabled to true in the config.ini file.

AMBW-34608 An error was generated and the SOAP request failed when there was a change in the order of soapenv:actor and soapenv:mustunderstand attributes.
AMBW-34379 Applications with SOAP Reference Binding failed to start when a SOAP service had a WSDL with <?Siebel-Property-Set EscapeNames="false"?> tag.
AMBW-34172 TIBCO Business Studio™ for BusinessWorks™ could not recognize REST service response with status codes 2xx other than 200, and displayed string instead of response objects when REST service was created using Swagger file .

Release 6.5.1

Key Description
AMBW-34259 Concrete WSDL file could not be retrieved at run time during SOAP service deployment on a web browser using the URL for an AIX platform.
AMBW-34010 At times, the concrete WSDL file could not be retrieved at run time and gave the following error: No service definition available.

This issue occurred when the SOAP service was deployed from a web browser and you tried to access the concrete WSDL file by using the domain name.

AMBW-34009 The <wsdl:types> tag was empty in the concrete WSDL generated at run time from the browser.
AMBW-34008 The schema elements in the run time concrete WSDL were duplicated when the concrete WSDL was fetched from two deployed applications sharing a common schema from a shared module.
AMBW-34002 SOAP requests failed when mapping optional nil element to optional empty element.
AMBW-33646 If a concrete WSDL file was accessed using a domain name during SOAP service deployment on a web browser, the file could not be retrieved at run time and the following error was generated: No Service Definition Available.
AMBW-33573 A REST service generated an error when multiple services were deployed on the same connector in a certain order.
AMBW-33440 The concrete WSDL added an extra forward slash (/) in the address location when a module property was used for the Endpoint URI field in a SOAP service binding.
AMBW-33282 TIBCO Business Studio™ for BusinessWorks™ displayed validation errors when generating concrete WSDL at design time and run time.
AMBW-33272 The Concrete WSDL file could not be retrieved at run time for a SOAP service deployed through a web browser by using the URL.
AMBW-33135 The NoHttpResponseException was intermittently displayed when invoking a REST service.

To ensure correct request processing, on the Advanced tab of the Invoke Rest API activity, set the Request Entity Processing field value to Buffered.

General

Release 6.6.1

Key Description
AMBW-39785 Failover did not occur when an AppNode was killed from a task manager in an AppSpace configured with the FTGroup persistence mode and an EMS as a transport.
AMBW-39221 The GetRecoverableProcesses() and RemoveRecoverableProcesses() methods for a check pointed job did not work.
AMBW-39132 The Add Required Processes operation in TIBCO Business Studio™ for BusinessWorks™ took more time when debugging an application.
AMBW-39057 TIBCO Business Studio for BusinessWorks displayed the Group Configuration Error even when an XPath version was changed.
AMBW-39022 The StackOverFlow error, which occurred when running the application, is now fixed.
AMBW-39017 The XSLT transformation error occurred in the Mapper activity while transforming the XPath expression of the data type unsigned short to the data of type integer.
AMBW-39016 A secondary AppNode became unresponsive when an application having an activator process that invoked a service from a shared module was executed with the FTGroup - FTL setup, and a primary AppNode was killed.
AMBW-38867 Failover did not occur when an AppNode was killed from a task manager in an AppSpace configured with the Group persistence mode and an FTL as a transport.
AMBW-38746 The JMS-related module properties fields were blank in the TIBCO Business Studio for BusinessWorks even after setting up the fields in the XML file.
AMBW-38720 The job data was not displayed in the Debug perspective when the Invoke activity used with REST reference binding was faulted.
AMBW-38339 TIBCO Business Studio for BusinessWorks displayed the Process not found error when running or debugging two or more applications that use the same shared module.
AMBW-38287 Swagger URL stopped working when an application was undeployed and redeployed again.
AMBW-38275 The obfuscated password for the FTL server was not resolved at runtime when used in the AppSpace's config.ini configuration file.
AMBW-38074 TIBCO Business Studio for BusinessWorks displayed a null pointer exception when a process was executed in the Debug mode using breakpoints.
AMBW-37498 Get the logs for the component states such as Start, Stop, and Resume by enabling the core runtime logger com.tibco.bw.core at INFO level.
AMBW-37310 The Mapper activity threw a null pointer exception and did not display any output when a process was executed in the Debug mode.
AMBW-36174 The TIBCO Business Studio for BusinessWorks debugger became unresponsive when the Step-Into option was selected post the breakpoint in the Debug view.
AMBW-33186 When TIBCO ActiveMatrix BusinessWorks™ 6.5.0 was installed on Windows operating system, in the TIBCO Business Studio for BusinessWorks Preferences > Plug-in Development > Target Platform, because of the TIBCO_HOME\bw\6.5\system\hotfix\lib\common missing directory, the default target definition called bw-runtime was reported as invalid.
AMBW-18429 The Iterate group for a schema element did not work when the element belonged to a no-namespace schema.

Release 6.6.0

Key Description
AMBW-37665 When an application was created with Docker and Cloud Foundry profile, and if the ContainerConfiguration value was selected, the Integer and Password field values were different from the String field.
AMBW-37664 When a <TIBCO_HOME> had spaces in its path, and there was a change in the logback.xml file in the Run/Debug Configuration dialog box, wrong arguments were generated in the arguments page, which did not let the internal appnode to start.
AMBW-37663 Exceptions occurred while adding input under Tests tab.
AMBW-37661 At design time, when an executable bwdesign encountered an error, it did not return non zero error code to the operating system on failure.
AMBW-37500 The Invalid comparison error is now shown in the Problems tab in addition to the Xpath builder.
AMBW-37461 TIBCO ActiveMatrix BusinessWorks™ generated Failed to parse configuration error at run time when a module property has hash (#) character in its value.
AMBW-37237 The Copy Of function added unused namespaces declared inside a source activity.

Select the copy-of target element. Open Show/Hide edit tab. Clear the copy-namespaces check box to not carry parent namespaces.

AMBW-36920 The duplicate property was created when importing properties from a property profile for a group and a nested group.
AMBW-36816 At design time, when a project with no warnings was exported from one workspace and imported into a different workspace lot of warnings were displayed.
AMBW-36776 ActiveMatrix BusinessWorks returned incorrect results when comparing the primitive type boolean values to functions true() and false() for the Parse XML activity having Validate Output check box was clear, and XPath and XSLT version was 1.0 in few cases.

To resolve this issue, select the Assume all inputs untyped check box under Windows > Preferences > Mapper dialog box and perform the Clean operation on the project.

AMBW-36552 A .EAR file was not generated when the ADB adapter was installed.
AMBW-36498 Applications failed to start on AIX platform.
AMBW-36477 The getcomponentdetail command displayed activation status as SingleNode on Admin CLI, even when a multi node application was running in a FTGroup with LB Mode.
AMBW-36421 In FTGroup mode, an AppNode became unresponsive when an application in a standby mode with an activator process was stopped.
AMBW-36318 The matches() XPath function did not work when partial regular expression was provided.
AMBW-36271 If the property bw.engine.start.all.applications.on.appnode.startup is set to true, then all the applications deployed on an AppNode are started once the AppNode starts irrespective of the last states of applications.
AMBW-36163 The XPath function format-dateTime() ignored the picture string for [MN,*-3] and generated incorrect output at runtime.
AMBW-36064 Considerable amount of time was required while building a workspace when there were multiple schemas in a workspace.
AMBW-36063 Building a workspace took a longer time when modifying REST bindings in a Components view.
AMBW-36053 TIBCO Business Studio™ for BusinessWorks™ became unresponsive in Components view intermittently when switching between REST Bindings.
AMBW-35962 Promoting a module property to an application property took an incorrect value at run time when a module property had a new line character (\n) in the value.
AMBW-35961 Fractional values were always present even though there was no fractional part in the mapping when the xsd:restriction condition was used with the base as xsd:decimal.

Add the following VM argument to omit the fractional part from the value: -Dbw.xml.decimal.omitDecimalPoint=true

AMBW-35863 Subprocess is now listed inside the main process span.
AMBW-35797 An application failed to restart as the config folder was corrupted.
AMBW-35725 A new frwk:startapp OSGI command is added to start an application gracefully.

This functionality is supported in TIBCO Business Studio for BusinessWorks only. Do the following configurations to Debugger in TIBCO Business Studio for BusinessWorks:

  1. Go to Debug Configurations > Bundles.
  2. Set Auto start for all the applications to false.
  3. If Apply button is not reflecting changes, you need to deselect one of the core bundles in target platform and then reselect it. Then changes are applied.
  4. Default Auto-start in the debug configurations has to be true.

When you start debugging, an application is loaded. To start that application, on the console, execute the following command:

startapp <ApplicationName>.application

AMBW-35430 Subprocess transition failed to process in few cases when XPath version was changed from 1.0 to 2.0.
AMBW-35417 An informative error message was not logged into the appnode.log file when a module property referred an incorrect keystore.
AMBW-35405 ActiveMatrix BusinessWorks generated a Null Pointer exception when an AppNode was shut down.
AMBW-35391 Jenkins jobs failed to build an .EAR file using the bwdesign command line utility for the projects containing SAP palette RFC activities.
AMBW-35375 A warning was displayed in a debug mode when unbounded string element had multiple values set.
AMBW-35334 Iterate group failed when using a schema with no target namespace.
AMBW-35108 During migration, the .xsd files took more time than expected to migrate.
AMBW-35058 A reference for original policy on binding broke when a policy resource was copied and renamed.
AMBW-35043 Atlassian Git did not track empty project folders, which were present in ActiveMatrix BusinessWorks, resulting in warning and error messages when a Git versioned ActiveMatrix BusinessWorks project was imported into TIBCO Business Studio™ for BusinessWorks™.
AMBW-35015 The bwdesign utility displayed Null Pointer error intermittently when exporting an .EAR file.
AMBW-34980 TIBCO ActiveMatrix BusinessWorks application took a longer time to start.
AMBW-34979 The Repeat on Error group executed even when a success condition occurred.
AMBW-34975 After migration, process memory and heap memory consumption increased substantially.
AMBW-34972 At run time, when a condition was matched, ActiveMatrix BusinessWorks wrongly evaluated the success with no matching condition as success.
AMBW-34943 A new Disable implicit-if existence checking check box is added in the Preferences > Mapper dialog box. Select the check box and clean the project to remove <xsl:if test="$Mapper/Element1"> elements from Optional to Optional mapping.
AMBW-34878 You can now export lapi OSGi command output to .CSV file.
AMBW-34869 The %DOMAIN_NAME% variable is now supported in the appnode_config.ini_template and bwappnode-an.tra_template files.
AMBW-34832 When the XSLT version was changed from 1.0 to 2.0, the empty tags were created in the activity output.
AMBW-34759 When an application had nested Repeat on Error groups, the inner group executed continuously in a loop and never exited, even though there was no error.
AMBW-34738 An application displayed all platform values of Deployment Target that were first selected and then cleared in the New BusinessWorks Application dialog box.
AMBW-34663 When module properties were added to the shared module and the application project was imported, the properties of the application were not updated after the import.

The following error was displayed: Application configuration error. A set of module properties included in the BW application are not in sync with the module properties configured for the module. Re-include module in the application.

AMBW-34565 Loop variable mapping for an iterate group was not correctly resolved.
AMBW-34505 The subprocess job status remained scheduled when a spawned subprocess completed after the main process.
AMBW-34482 The XPath function Prefix-from-QName() returned an empty value when the QName() function had an input as prefix.
AMBW-34377 The application did not start in TIBCO Business Studio for BusinessWorks and became unresponsive during an application startup with high memory usage, when specific schema was imported into a project.
AMBW-34338 Swagger files in a project were not in sync for local folders.
AMBW-34321 An error occurred when an .EAR file was generated using bwdesign utility.
AMBW-34312 Unable to open and view a .bwp process in the process editor.
AMBW-34179 The lapi OSGI command displayed all process instances instead of active process instances for all applications running at AppNode.
AMBW-34159 When a schema was imported during coercion, from a maven shared module, the schema location could not be resolved. Also, when multiple schemas, or a WSDL and a schema shared the same target namespace, errors were thrown in coercions using the schema.
AMBW-34014 An application became unresponsive when an error occurred while executing OnStartUp method of an application activator process.
AMBW-33915 The Success with Condition and Success with no matching Condition transitions were evaluated as true at the same time, when performing copy and paste operations.
AMBW-33742 The compare-dateTime() XPath function returned incorrect results when one of the parameters was the output of parse-dateTime() XPath function.
AMBW-33733 ActiveMatrix BusinessWorks returned incorrect results when comparing the primitive type boolean to functions true() and false() with a few cases. For example, the Parse XML activity.
AMBW-33618 The Export Profile utility in TIBCO Business Studio for BusinessWorks now generates the same profile as it is generated by exporting from an application archive.
AMBW-33598 Creating a complex value by combining two module properties did not work in the File Poller activity.
AMBW-33511 Support is added for suspending and resuming process instances via OSGi commands. The following two new commands are added:
  • suspendpi <input pid>
  • resumepi <input pid>
AMBW-33472 An application stopped receiving requests intermittently when using pageThreshold property in a config.ini file of an AppNode.
AMBW-33211 TIBCO Business Studio for BusinessWorks was unable to import the schemas from the external shared module libraries to the schemas inside application modules.
AMBW-33158 The bw.application.checkpoint.retainFaultedJob and bw.application.checkpoint.recoverOnRestart properties are now applicable for all applications without any configuration changes at AppSpace level.
AMBW-33103 The application did not start in TIBCO Business Studio for BusinessWorks and became unresponsive during an application startup with high memory usage, when the specific schema was imported into a project.
AMBW-33101 The Start, End, Eval, and Elapse time values were not displayed for process instance statistics and activity instance statistics.
AMBW-32852 TIBCO Business Studio for BusinessWorks displayed a warning when a schema without a namespace was present in a shared module, and was referred in an application module.
AMBW-32799 The definition of xs:key in the XSD generated an error even when the XML schema was valid.
AMBW-32656 Renaming of the schema element name did not automatically reflect in the SOAP service and reference Context parameters.
AMBW-32603 The changes performed in the Swagger file from the API Explorer view did not reflect in the process.
AMBW-32301 An element of type <Any> inside a choice block could not be coerced with the other element.
AMBW-32276 Unrelated error messages occurred when a shared resource outside a package was moved inside a package.
AMBW-31960 TIBCO Business Studio for BusinessWorks displayed incorrect icon for an operation's implementation type, when an abstract WSDL was dragged and dropped in the process editor to implement the operation.
AMBW-31928 When you use the mapper directly in the deep-equal() function, it always resulted as TRUE.
AMBW-31520 The variable %APPNODE_NAME% did not work in the bwappnode-an.tra_template file.
AMBW-31408 In a few cases, when you change the condition on transition , no job data was visible when debugging an application and generated a No namespace found error.
AMBW-31264 A component was created in a module when a direct sub-process, without any component, was copied and pasted.
AMBW-30910 Set the bw.engine.inline.subprocess.multiLogging.disable property to true in the config.ini file to avoid unnecessary logging at ERROR level.
AMBW-30573 When multiple endpoints were generated from the same Swagger file of the resource path to generate the Resource name, the full resource path was not considered.
AMBW-30432 The drop-down box in the Process Launcher pane on the Debugger view is now removed.
AMBW-30297 When a choice type was compared to an atomic or an element type in the mapping, an Invalid Comparison error occurred.
AMBW-30005 Transitions did not work as expected when validation was disabled.
AMBW-29963 Folders within a special folder could not be renamed.
AMBW-28838 TIBCO Business Studio for BusinessWorks displayed some files as modified for collaborative development even though there were no logical or structural changes made.
AMBW-28651 TIBCO Business Studio for BusinessWorks and runtime were unable to work with large schema file, threw OutOfMemory exception, and CPU usage was very high.
AMBW-26726 Changes made in logback.xml for logging parameters are applied even when AppNode is running.
AMBW-26499 TIBCO Business Studio for BusinessWorks could not resolve a schema and displayed an error, if the folder containing schema had special characters in the folder name.
AMBW-25561 On adding or removing coercion in the XPath Builder dialog box for transitions and groups, the coercion was not expanded to an appropriate level to view the coerced type.
AMBW-25449 Performance was degraded for spawned processes.
AMBW-23610 An error occurred when an application with an activator process was stopped.
AMBW-23609 The OnShutDown operation in an activator process was not executed when an AppNode was stopped.
AMBW-23422 Type or value of promoted application property was not updated when changing the type or value of the module property related to the promoted application property.
AMBW-22529 Logging was stopped when a log level of AppNode was changed while its running.
AMBW-19460 The input text is dynamically validated whenever the XPath is changed in the XPath Builder dialog box.

Release 6.5.1

Key Description
AMBW-34236 An error occurred when validating a WSDL.
AMBW-34235 A validation error occurred when an XSD schema without import location was imported.
AMBW-34233 A source process was changed and corrupted when copying a constructor and then deleting it from the target process.
AMBW-34194 An EAR failed to generate when the port type was missing in a WSDL interface.
AMBW-34113 Building a workspace took longer time than expected when modifying REST bindings in the Components view.
AMBW-34100 Complex schema elements could not be mapped when existing projects were imported without the Copy Projects into workspace option.
AMBW-34098 The format-dateTime() XPath function generated an incorrect result with the Z operator.
AMBW-34097 The format-dateTime() XPath function could not parse the picture string correctly.
AMBW-34096 TIBCO Business Studio™ for BusinessWorks™ displayed an error for anyElement and anyType element mappings when using an explicit XPath expression.
AMBW-34095 After migration, an assertion error occurred due to an external document.
AMBW-34091 The format-dateTime() XPath function returned AM instead of PM for the time between 12:00 and 12:59.
AMBW-34083 SOAP and REST endpoints were duplicated after restarting an application.
AMBW-34082 The application failed to start when it had a asterisk (*) in the XPATH, and the warning message Runtime binding is not synchronized was fixed with the Quick Fix option.
AMBW-34080 AppNode logs did not roll over.

For previously created AppNodes, replace the existing AppNode's logback.xml with {BW.HOME}/config/logback.xml.

Newly created AppNodes use the new logback.xml.

AMBW-34068 A NullPointerException occurred on a SOAP Reference Binding when refactoring an operation on a server side.
AMBW-33813 An application with JDBC Connection shared resource failed to start for the first time when an AppNode was configured in a group persistence mode with DB and EMS configuration.
AMBW-33795 Embedded policies were not enforced on the AIX platform, and the NoClassDefFoundError exception was logged in the AppNode log when you started the AppNode.
AMBW-33700 After deploying an application on TIBCO Cloud Integration™, an exception occurred at run time for the date-format function.
AMBW-33588 After migration, an incorrect validation error was displayed for a process inline schema when referring to WSDL inline schema without the schemaLocation attribute.
AMBW-33569 During migration, the Handle Variable Rename error message was displayed.
AMBW-33550 Values of the promoted application properties in different profiles were modified when a new module property was added.
AMBW-33510 The FaultDetails variable was not shown in the debugger when a Catch block was applied in the Scope group.
AMBW-33503 For a few migrated projects, building a workspace took a long time.
AMBW-33462 TIBCO Business Studio™ for BusinessWorks™ became unresponsive in Components view intermittently when switching between REST Bindings.
AMBW-33461 The application went into an impaired state when a shared resource was not placed inside a package in a shared module.
AMBW-33276 Main process was delayed as sub-processes could not be spawned.
AMBW-33246 Considerable amount was required while building a workspace when there were multiple schemas in a workspace.
AMBW-33219 An application without any dependency on JMS failed when an Enterprise Messaging Server (EMS) driver was uninstalled.
AMBW-33204 New process was created after renaming an existing process.
AMBW-33192 You could not completely remove an activity name when renaming an activity in the Properties tab with the backspace key.
AMBW-33118 The module property name could not be edited when clicking it too fast.
AMBW-33113 A validation error was generated during start of an application but not at the design time even when the type of the property inside the module descriptor did not match the type of the process property.

Migration

Release 6.6.1
Key Description
AMBW-39242 After migration, a process was migrated as an empty process and displayed the Argument cannot be null error when the process was opened.
AMBW-39049 After migration, TIBCO Business Studio™ for BusinessWorks™ took more time to build a workspace and load a project.
AMBW-31139 After migration, the if-else clause in the Iterate group was not recognized by the Variable List field.
AMBW-29073 Now global variable is resolved for the Keystore Provider As Trust Store field for mutual authentication for the SSL.
AMBW-18510 The document() now migrates as document() XPath function only.
Release 6.6.0
Key Description
AMBW-36740 The JDBC transaction group was migrated as a Scope group instead of JDBC.
AMBW-36526 After migration, some of the mappings or conditions were not migrated in the Generate Error activity.
AMBW-36476 The format-dateTime() or parse-dateTime() XPath functions in TIBCO ActiveMatrix BusinessWorks™ 5.x were migrated incorrectly.
AMBW-36462 Mapping was migrated partially for the Throw activity.
AMBW-36342 The Iterate group was migrated incorrectly and when the process was opened, the following error occurred:

Argument cannot be null.

AMBW-36297 The Activator process present in the shared module (during migration) was not visible during run time causing errors.
AMBW-36170 Not all Custom XPath functions migrated and led to errors in the project.
AMBW-36096 After migration, following error was generated while starting a soap service.

no xsd for this imported location

AMBW-35860 After migration, the XPath expression for For-Each current element value was incorrect.
AMBW-35769 After migration, the mapping errors were observed, because the target namespace was absent in the ActiveMatrix BusinessWorks™ 5.x schema file.
AMBW-35766 After migration, the union ("|") operator was converted to OR operator and could not return a value correctly.
AMBW-35753 The migration of the For-Each loop with complex XPath expression and global variables was incorrect.
AMBW-35511 The Invoke REST API activity was migrated as an empty activity.
AMBW-35395 The processes from ActiveMatrix BusinessWorks 5.x application were not migrated because of the invalid entries in the Process Name field in a call process.
AMBW-35226 While migrating ActiveMatrix BusinessWorks 5.x SOAP Client application using headers from WSDL, the migrated project automatically adds the SetContext/GetContext activities in the process.
AMBW-35223 After migrating projects with process properties mapped, the following exception occurred at run time:

[err:XPST0008] The expression refers to a variable name that is not defined in the static context.

AMBW-35170 After migration, an error was generated when the applications had inline schema with no namespace defined.
AMBW-35108 During migration, the .xsd files took more time than expected to migrate.
AMBW-34731 After migration to ActiveMatrix BusinessWorks 6.x, the system was unable to map any element with a given XPath.
AMBW-34704 After migration, a few optional elements that were not mapped were not migrated.
AMBW-34688 After migration, the local variable was not shown as repeating.
AMBW-34653 After migrating a project, the Error output schema for HttpCommunicationException, HttpClientException, and HttpServerException in the SOAP Request Reply activity was not available.
AMBW-34558 After migration, the starter process was migrated as a service subprocess.
AMBW-34519 After migration, a few DTD schema attributes were not migrated.
AMBW-34518 After migration, the subprocess was migrated as NULL.
AMBW-33997 When the ActiveMatrix BusinessWorks 5.x project was migrated to TIBCO ActiveMatrix BusinessWorks™ Container Edition, some of the shared variables were not migrated.
AMBW-33752 After migration, the global variables which were declared as a concatenation of a global variable and a literal value were not migrated properly, and the activity configuration data was lost.
AMBW-33665 After migration, an extra body element, bodyText, was displayed in the Send Mail activity, and displayed a validation error.
AMBW-33664 After migration, an .xsd file imported a .wsdl file and displayed validation errors.
AMBW-33663 After migration, one of the processes in the project was migrated as an empty process.
AMBW-33594 After migration, an error occurred because of an additional import statement.
AMBW-33473 After migration, the output of the subprocess containing a parse data activity was not shown in the main process.
AMBW-32880 After migration from ActiveMatrix BusinessWorks 5.x to TIBCO ActiveMatrix BusinessWorks™ Container Edition, the conditional transition having coerced XPath was not recognized.
AMBW-32847 After migration from ActiveMatrix BusinessWorks 5.x to TIBCO ActiveMatrix BusinessWorks™ Container Edition, shared variables containing an inline schema were not migrated.
AMBW-32742 After migration, validation errors were displayed since the ResultSets Use Schema check box on the JDBC Call Procedure activity was not selected.
AMBW-32372 An application migrated the File Poller activity incorrectly whenever it had the sequencing key value.
AMBW-32327 When the SOAP Request Reply activity referred a WSDL from the project library, its configuration failed to migrate correctly.
AMBW-31988 After migration, the unwanted process properties for shared resource were getting added into the process even when that shared resource was not used in the process.
AMBW-31886 After migration, an application failed to start.
AMBW-31848 After migration, the com.tibco.xml.xdata.bind.CommentBinding exception occurred in the migration report.
AMBW-31711 The inputs for the Mapper activity did not migrate properly.
AMBW-31610 In a project containing the shared modules, the global variables were not migrated to the respective module properties.
AMBW-31478 The comments at the beginning of an XPath Expression in a transition or group were ignored causing loss of information.
Note:

Transition/Group Level Comment Support: Comment at the start of an expression (on a transition/group) with design time validation error (unexpected token) present in ActiveMatrix BusinessWorks 6.6.0.

Activity Level Comment Support: Post migration, all the comments (at the start, in the middle, and at the end) in an activity are moved to a different line-set (Comment Binding) as a Comment.

AMBW-30839 After migration, the relative path in the Input tab of the Mapper activity was not working.
AMBW-30731 If the process variables had an element reference from the inline schema of WSDL then those process variables were not migrated.
AMBW-30689 After migration, the End activity displayed an error, when a SOAP Reference Binding was configured with a part name other than the default part name in the Message Part Configuration option.
AMBW-30387 The global variables were not migrated from ActiveMatrix BusinessWorks 5.x to TIBCO ActiveMatrix BusinessWorks™ Container Edition.
AMBW-29836 During migration, the Handle Variable Rename error pop up was displayed.
AMBW-29688 After migration, an inline schema with namespace collision was reported.
AMBW-29428 After migration, an input schema for the Throw activity was invisible and all the mappings were unavailable.
AMBW-29002 The migration tool failed to migrate processes for the large projects.
AMBW-28446 After migration, the process properties were not created.
AMBW-27266 After migration from ActiveMatrix BusinessWorks 5.x to TIBCO ActiveMatrix BusinessWorks™ Container Edition, the existing comments in the XPath expression were not migrated.
Release 6.5.1
Key Description
AMBW-34351 A main process could not pass mapped data to a subprocess.
AMBW-34187 After migration, the JMS Send Message activity could not reflect changes in a referenced schema.
AMBW-34078 After migration, the Process In-line schema namespace collision error was displayed which was incorrect.
AMBW-33959 After migration, the Rendezvous Subscriber activity could not pick up messages at run time and generated a null pointer exception.
AMBW-33880 After migration, a few exceptions were listed in the MigrationReport.log that broke some processes.
AMBW-33876 After migration, the Catch block and its associated activities executed only once.
AMBW-33856 After migration, a process migrated as empty due to some issue with its Iteration element's inline schema creation.
AMBW-33577 After migration, a few processes had duplicate WSDL or XSD entries on the Process Dependencies tab.
AMBW-33571 The mapping did not create a copy-of element for choice elements when a root element had choice elements.
AMBW-33520 When you ran a project after migrating to TIBCO ActiveMatrix BusinessWorks 6.5.0 HF-001, the Confirm activity remained in the starting status.
AMBW-33499 After migration, Generate Error activities that had choice elements with when-otherwise conditions were deleted.
AMBW-33492 After installing TIBCO ActiveMatrix BusinessWorks 6.4.2 HF-004, some projects displayed the StackOverFlow error during migration.
AMBW-33490 After migration, Parse XML and Mapper activities were migrated as Null when an input binding element schema was a part of WSDL and a resource URI had special characters.
AMBW-33488 The JMS Receiver activity was migrated as empty when JMS application properties were not mapped from design time libraries.
AMBW-33464 The </xsd:attribute name="xml:lang" type="xsd:language" use="optional"/> now migrates as </xsd:attribute ref="xml:lang" use="optional"/>.
AMBW-33443 Numbers in XPath expressions were wrongly migrated as "xsd:string(...)" instead of xsd:string().
AMBW-33437 After migration, the JMS Queue Requestor and JMS Queue Receiver activities had different target namespaces for inline schema, which resulted in some errors in the project.
AMBW-33433 An exception was generated when migrating the project due to which a process was migrated as an empty process.
AMBW-33389 After migration, the Activity input configuration error was generated on the Input tab of an End activity inside a Catch block.
AMBW-33369 After migration, XPath was missing from a Reply activity.
AMBW-33368 After migration, an error occurred at run time when the JMS Send Message and JMS Receive Message activities had inline schemas with different namespaces.
AMBW-33309 After migration, a process was migrated as an empty process.
AMBW-33308 After migration, when a process had JMS Queue Requester activity whose input and output was configured with an inline XML schema, the output inline schema replaced the input inline schema for that activity.
AMBW-33307 After migration, when a process had JMS Topic Requester activity whose input and output was configured with an inline XML schema, the output inline schema replaced the input inline schema for that activity.
AMBW-30921 A subprocess with a WSDL inline schema in the End activity could not be migrated.

Palettes

Release 6.6.1

HTTP Palette
Key Description
AMBW-39307 The Send HTTP Request activity did not send the content-id header in the MIME header part of an HTTP request.

The issue was observed when the Apache HttpComponents Implementation Library was configured in the HTTP Client shared resource.

AMBW-39063 If two or more REST applications shared the same HTTP Connector shared resource from a shared module, and whenever one of the applications was undeployed and redeployed again, then the REST service stopped working.
AMBW-38809 The Jetty server details were visible in the response headers if service replied with a fault message.

To hide the server details, following property must be added in the AppNode or AppSpace config.ini file :

com.tibco.bw.http.hideServerVersion=true

From TIBCO Business Studio™ for BusinessWorks™, pass the following property in the VM arguments :

-Dcom.tibco.bw.http.hideServerVersion=true

AMBW-38479 The HTTP Receiver activity did not preserve a URI encoding. This issue has been fixed now.

Pass the property -Dcom.tibco.plugin.http.encodedQuery=true in the VM arguments to retain the encoded query string on the service side.

JDBC Palette
Key Description
AMBW-39780 The JDBC palette activities timed out inside the JDBC local transaction group when concurrent requests were sent.
AMBW-39265 TIBCO ActiveMatrix BusinessWorks™ did not retrieve data of type timestamp from a database.
AMBW-39238 A null ('') value into a CLOB datatype was not inserted in an Oracle database.
AMBW-38741 The null error was generated in the AppNode logs with a custom TeraData JDBC Driver and when the connection idle timeout had passed.
AMBW-38725 The SQL Direct activity could not fetch data from the Teradata database after 15 iterations when the activity was configured with a custom JDBC driver.
AMBW-38352 The JDBC Query activity threw the "Numeric overflow" error.
AMBW-38331 After migrating an interface from ActiveMatrix BusinessWorks™ 5.13 to ActiveMatrix BusinessWorks 6.4.2 and TIBCO ActiveMatrix BusinessWorks™ Plug-in for Database 8.3.1, the Teradata database call failed with the following error:

"Response limit exceeded".

AMBW-38330 The JDBC Palette activities failed and displayed Null Pointer Exception after few iterations.
AMBW-35727 The use of recursion to acquire a connection caused the stackoverflow error after few iterations.
JMS Palette
Key Description
AMBW-39002 The Failed to set CLIENTID error occurred infinitely when an EMS connection was not responding
AMBW-38640 When the application failed to connect to the EMS server or the EMS server did not respond, the application went into the infinite loop and generated the logs infinite times.
AMBW-38071 When the data against dynamic properties or application properties were out of range in accordance with their data types, the following incorrect error message was displayed:

" Configuration Error - Expected Topic as Destination for Durable subscription".

AMBW-38070 The performance of the JMS Send Message activity is now improved.
AMBW-33975 An error occurred when starting an application in the FT mode that had Messaging Style as Topic, the Durable Subscriber check box selected, and a static client ID.

When a JMS connection has an empty client ID and an auto generated client id is de-selected, set the property bw.ft.mode.jms.clientID.empty.autogenerate=false in the config.ini file to create the only subscription with the subscription name set to JMS receiver.

REST and JSON Palette
Key Description
AMBW-37571

The Parse JSON activity could not add the <JSON> root for a single complex element XML transformation.

To add the <JSON> root element for the Generic schema type in the Parse JSON activity, add the com.tibco.plugin.restjson.json2xml.enforceJsonRoot property in the AppSpace config.ini file and set it to true. 

XML Palette
Key Description
AMBW-39069 The Parse XML activity did not show the fault details when debugging a project.
AMBW-39031 The Render XML activity, with the default namespace, generated an invalid XML document if the elements were imported from the schema.
AMBW-39030 The applications that use the Transform XML activity threw the JavaNullPointer exception when used with a dynamic XSLT source.
AMBW-39029 An Encoding attribute in an XML declaration was incorrect for the Render XML activity with the binary output style.

Release 6.6.0

General Activities Palette
Key Description
AMBW-35406 When the same coercion was applied on two or more sibling elements, all the elements were incorrectly renamed to the name of the very first sibling.
AMBW-31685 No data was accumulated for the Output Activity field marked as Assign.
HTTP Palette
Key Description
AMBW-34185 An error occurred intermittently when invoking REST APIs with Send HTTP Request activity.
JAVA Palette
Key Description
AMBW-34874 For Java Invoke activity inside a loop, memory leak occurred for a process that ran for a long time thus surpassing the max heap limit.
AMBW-34177 The XML To Java activity could not generate target namespace when dependency was specified as Maven Dependency.
JDBC Palette
Key Description
AMBW-37041 The JDBC connection for DB2 database driver using sslTrustStoreLocation property in URL generated errors at run time, but Test Connection was successful.
AMBW-36702 The JDBC Call Procedure activity displayed all input and output parameters for two different procedure and function, if the procedure and function have the same name.
AMBW-35531 The number of JDBCQuery threads increased significantly during application execution.
AMBW-35360 The JDBC Query activity and SQL Direct activity gave different output for numeric data types.
AMBW-34854 JDBC connection URL for PostgreSql database driver generated errors at run time, but displayed connection successful message at design time when a connection URL had the sslmode=require property.
AMBW-34853 The SQL Direct activity did not show error message code in the Job Data view.
AMBW-34852 The JDBC Update activity timed out when inserting records in the IBM AS400 custom database driver using the jt400.jar file.
AMBW-34721 An application did not consider the currentschema parameter from the JDBC Connection URL at run time.
AMBW-34720 The Override S/A DataType check box on the Advanced tab of the JDBC Call Procedure activity now supports inout and out object type at run time.
AMBW-34360 The JDBC Update activity did not consider the Timeout(sec) value set.
AMBW-29290 Installing TIBCO ActiveMatrix BusinessWorks™ under Program Files on Windows operating system caused installation errors with JDBC driver bundles at runtime.
AMBW-29072 The Maximum open cursors exceeded error occurred in the JDBC Updateactivity while inserting records.
AMBW-28204 Execution of JDBC activities were delayed due to the SharedResource thread being in sleep state.
AMBW-18192 The column name is not valid error occurred with JDBC Query activity when aggregate functions like avg,sum, and count are used in select query.
JMS Palette
Key Description
AMBW-37270 Memory growth and memory leak occurred for JMS Send Message activity from the JMS Local Transaction group.
AMBW-36565 The configuration of the AQjmsInitialContext is not complete error occurred during test connection in JMS connection with Oracle AQ as Tibco custom JMS provider.
AMBW-34802 When a message was not acknowledged in the Get JMS Queue Message activity and the Acknowledge Mode was set as EMS Explicit Mode, a message was not processed again unless the application was restarted.
AMBW-34701 The JMS message deserialization failed when both the JMS Send Message and the JMS Receive Message activities used the same schema, and when you set the field value for int, decimal, double, and float to NULL.
AMBW-22481 The session was blocked and messages were not retried by JMS Receive Message with XML Text message type in Non-Auto Ack modes like Client ,TIBCO EMS Explicit Client, and TIBCO EMS No Acknowledge when the Confirm activity was in exception block and incoming messages were of text type.
Mail Palette
Key Description
AMBW-36118 The Receive Mail activity displayed an error message for emails with attachment for Microsoft Outlook mail server.
Parse Palette
Key Description
AMBW-34145 The Line Length value in the Field Offset section of the Data Format shared resource was not correctly updated with respect to changes in the end field value.
AMBW-32644 TIBCO Business Studio™ for BusinessWorks™ failed to parse the CSV strings, and intermediate double quotes from input string were removed.
AMBW-32623 TIBCO Business Studio for BusinessWorks failed to parse the CSV strings, and double quotes were not processed correctly.
REST and JSON Palette
Key Description
AMBW-30857 The Parse JSON activity interpreted "null" value incorrectly.
Rendezvous Palette
Key Description
AMBW-36176 Timed out error occurred on the Rendezvous Request Reply activity for reply message received within timeout value.
XML Palette
Key Description
AMBW-36021 The Parse XML activity failed to parse data for multiple comments above the root element.
AMBW-34998 The parseXML validation error was not shown in the $error_ParseXML activity, but in the generic $_error activity.
AMBW-31697 The XSLT tag omit-xml-declaration did not work as expected.
AMBW-30050 The Catch block could not handle errors from the Parse XML activity.
AMBW-28176 The Parse XML activity failed to parse an XML when it contained processing instructions such as <?Siebel-Property-Set EscapeNames="true"?>.
AMBW-25223 When the XPATH functions, like trim, pad, and so on, were used inside the filter expression, the java.lang.UnsupportedOperationException exception was thrown.
AMBW-14549 Performance degradation was observed in the Render XML activity.

Release 6.5.1

HTTP Palette
Key Description
AMBW-34208 The Send HTTP Request activity sent responses with empty fields intermittently.
AMBW-33136 An application failed at run time but no error was displayed at design time when the Host field in the HTTP Connector shared resource had a literal value as localhost and the value of the Deployment Target for an application was Tibco Cloud.
General Activities Palette
Key Description
AMBW-33483 An application job was started as soon as an Application or an AppNode was restarted when the Interval Unit value was set to DAY in the Timer activity.
JAVA Palette
Key Description
AMBW-32756 The XML To Java activity could not reload newly added Java members in a Java class.
JDBC Palette
Key Description
AMBW-34293 An Activity output data validation error was displayed when the Use Nil and Resulsets Use Schema check boxes were selected on the Advanced tab of the JDBC Call Procedure activity, and a procedure returned records with null values.
AMBW-34027 All columns of the table were displayed only when one of the tables returned as a part of an SQL procedure response was completely empty and the Use Nil check box was selected.
AMBW-33475 The SQL Direct activity returned the value as true instead of empty when you mapped the output with nillable as true and selected the Use Nil option.
AMBW-33360 The JDBC Query activity returned the value as true instead of empty when you mapped the output with nillable as true and selected the Use Nil option.
AMBW-33359 The NVARCHAR data type was converted to the VARCHAR data type when the sendStringParametersAsUnicode property was set to false in the SQL Server URL.
AMBW-33330 Excess threads were created when there were maximum number of connections to the database. The threads created by JDBC activities went into sleep state for few seconds rather than going into the standing or the waiting state.
AMBW-31914 JDBC activities could not connect to a secondary server when a DataDirect driver was used and the connection URL had hyphen (-) character in the host name.
JMS Palette
Key Description
AMBW-34053 The JMS Receive Message activity failed to reconnect after TIBCO Enterprise Message Server (EMS) failover. This issue occurred only when EMS was configured with ftgroup or group mode with governance flag enabled.
AMBW-34050 The JMS Receive Message activity generated an exception multiple times and failed to reconnect to the IBM MQ server when there was a network outage.
AMBW-34028 In some scenarios for Client Ack mode, only the first JMS message was processed successfully and subsequent messages failed to process.
AMBW-33828 When a message was sent using the JMS Send Message activity, and fetched by using a Get JMS Queue activity, the property JMSXDeliveryCount was automatically added to the Dynamic Properties output.
AMBW-33812 The JMS Send Message activity failed to reconnect to the IBM MQ 8 server when the IBM MQ 8 server was restarted.
AMBW-33438 Messages were not moved to $sys.redelivery.delay queue because they were not confirmed in the Get JMS Queue activity with client acknowledge mode.
Rendezvous Palette
Key Description
AMBW-34389 After migration, the value for one of the elements was missing in the Rendezvous Subscriber activity at runtime.

Policies

Release 6.6.1

Key Description
AMBW-39090 A SAML message was not forwarded and generated the following error:

Error unmarshalling a SAML assertion.

AMBW-38857 The Heap Out of Memory message was thrown for faulted jobs while using the SOAP/HTTP Invoke activity with Policy Basic Authentication.
AMBW-37873 The performance was degraded when the authentication was done with LDAP.

Release 6.6.0

Key Description
AMBW-36553 The Authentication Failed error was displayed when a WSDL had namespaces that did not start with "http://".
AMBW-35852 TIBCO Business Studio™ for BusinessWorks™ displayed an error when a policy resource was in a shared module.
AMBW-35075 A REST service configured with LDAP basic authentication policy returned an incorrect error code when invoked with wrong credentials.
AMBW-34850 When a policy resource was in a shared module, a policy was not applied at run time and a plain request was sent.
AMBW-34795 The Timestamp was not sent intermittently in the SOAP security header.
AMBW-33977 TIBCO ActiveMatrix BusinessWorks 6.x could not generate errors for expired certificates.
AMBW-27423 The Invalid Property Exception occurred when a module property was used to search a user in base DN in LDAP resource.

Release 6.5.1

Key Description
AMBW-33460 SOAP requests were authenticated intermittently when the password in a request was empty.
AMBW-33336 The LDAP basic authentication policy did not work for Microsoft AD Server at runtime when the Admin user credentials check box was selected.