TIBCO ActiveMatrix BusinessWorks 6.4.1 Hotfix-02 is available
book
Article ID: KB0102315
calendar_today
Updated On:
Products
Versions
TIBCO ActiveMatrix BusinessWorks
6.4.1
Description
You can download this HotFix from TIBCO Support Portal (https://support.tibco.com). You will need to provide your TIBCO Support Portal credentials. Once logged in you can the download the hotfix by selecting the “Downloads” -> “Hotfixes” option. Then go to the AvailableDownloads/BusinessWorks/6.4.1/hotfix-02.
================================================================================ Closed Issues in 6.4.1_HF-002 (This Release)
AMBW-29448 When an AppNode or an Application took more than 60 seconds to start,a warning message stating that the AppNode/Application did not start was displayed. To configure the timeout value,set the timeout property, bw.agent.technology.requestTimeout in the bwagent.ini file and restart the agent.
AMBW-29374 If the XSD file includes an import and the relative location in the import includes the name of the bundle, problems were reported in the runtime cache when resolving the XSD file.
AMBW-29366 The show apps command displayed the incorrect status of the application in BWAdmin CLI.
AMBW-29364 The Internal Server Error was displayed in the bwappnode logs when the application was in the Impaired state. This exception was displayed when the appnode attempted to update the status in the database.
AMBW-29354 Variables defined in previous version of Tibco Business Studio workspaces were not resolved and were displayed with the 'Not Found' error at runtime.
AMBW-29274 Schema loading issues were reported when the referenced shared modules with multiple schemas used the same targetnamespace.
AMBW-29252 When input to the RenderXML activity or the tib:render-xml()function contained the greater-than sign (>), it was always replaced with lower-than sign (<).
AMBW-29134 If the data type of the property defined in the DynamicProperties field of the JMS Send Message activity was not specified or if the type specified was not in the lower case, then the dynamic properties were not published as a part of the JMS header.
AMBW-26099 When using the XML Transform activity the resulting XML output lost the XML declaration. The prolog info was lost even when the XML declaration was forced in the xslt.