Known Issues
The following known issues have been introduced in TIBCO BusinessWorks™ Container Edition and are listed by release.
| Key | Description |
|---|---|
| BWCE-2571 | Summary: Service Discovery fails with SSL applications on Pivotal Platform.
Workaround: None. |
| BWCE-2556 | Summary: When an application containing Netsuite plugin activities is deployed in
TIBCO BusinessWorks Container Edition Container, a
SSLHandShakeException is thrown.
Workaround: Copy the libsunec.so library found in jre-8u<no>-linux-x64.rpm/tar.gz which is available in Oracle resource library to /resources/addons/lib folder before you create the base image or buildpack. |
| BWCE-2548 |
Summary: When a monitoring application is started with any database other than Oracle, the Oracle libraries are getting downloaded.
Workaround: None. |
| BWCE-2393 | Summary:
TIBCO BusinessWorks Container Edition Monitoring does not work with Oracle Database on Docker.
Workaround: In the Dockerfile, add RUN npm rebuild on line number 29. |
| BWCE-2367 | Summary: Application Monitoring using Opentracing with HTTP connection is not working with
TIBCO BusinessWorks Container Edition applications.
Workaround: Use Opentracing with UDP connection. The Jaeger and TIBCO BusinessWorks Container Edition containers should be present in the same docker network. |
| BWCE- 2270 | Summary: When -Xmx and -Xms values are passed through BW_JAVA_OPTS variable on Cloud Foundry, the -Xmx and -Xms settings on the JVM are duplicated.
Workaround: None. |
| BWCE-2073 | Summary: Marketo application generates run time
SSLHandshakeException for
TIBCO BusinessWorks Container Edition.
Workaround: Copy the libsunec.so library found in jre-8u<no>-linux-x64.rpm/tar.gz which is available in Oracle resource library to /resources/addons/lib folder before you create the base image or buildpack. |
| BWCE-2072 | Summary: When a module property has inputs with combinations of special characters like
$,% &, the complete input provided is not reflected in the output. Some part of the input is omitted.
Workaround: None. |
| BWCE-2008 | Summary: FTL application does not work in windows container because of absense of FTL client libraries for windows.
Workaround: None. |
| BWCE-1832 | Summary: In some cases, catch block, reference binding, service binding is misaligned in the process diagram in Monitoring UI.
Workaround: None. |
| BWCE-1810 | Summary: When Process Monitoring is enabled for an application, in PCF, all historical records will also appear when observing process monitoring data when an application is deleted and same application is pushed again.
Workaround: None. |
| BWCE-1795 | Summary: Once you enable Process Monitoring, if your application completes all its jobs, before process monitoring is enabled, then you wont see any process instances in the Monitoring UI.
Workaround: You will need to add sleep in your process or hit REST/SOAP/HTTP endpoints if any to see newly created process instances. |
| BWCE-1740 |
Summary:
TIBCO BusinessWorks Container Edition Application throws
java.net.UnknownHostException when deployed in Docker Swarm
Workaround: None. |
| BWCE-1433 | Summary: In the FTL application logs, an
Invalid message type received from peer 'NULL' error message occurs.
Workaround: None. These errors can be ignored. |
| BWCE-1396 | Summary: You have to edit the
logback.xml every time you restart the application.
Workaround: None. |
| BWCE-1239 | Summary: An error, related to
libcrypto.so, is displayed in the logs when the application is pushed to the Cloud Foundry or Docker.
Workaround: None. These errors can be ignored. |
| EPAS-748 | Summary: When importing the
ZipCodeLookup sample errors are seen in the workspace log file.
Workaround: None. These errors can be ignored. |
| EPAS-103 | Summary: When specifying Application Properties, if invalid login credentials are specified in the
Configure Container Connection Dialog, the dialog asking for valid login credentials repeatedly pops up even after valid login credentials are specified.
Workaround: Press the Cancel button on the dialog. |
| EPAS-79 | Summary: Exceptions are seen when you import a project that contains a JDBC shared resource.
Workaround: Restart TIBCO Business Studio™ for BusinessWorks™ and open the project in a new workspace. If the issue persists, recreate and reconfigure the JDBC shared resource. |
Bindings
| Key | Description |
|---|---|
| AMBW-36113 | Summary: A multipart message where one part points to type and the other part points to element and a message using mixed security mode is not supported.
Workaround: Change mixed security mode in a given WSDL. |
| AMBW-34508 | Summary: The following error occurs for the concrete WSDL at design time:
src-import.1.1: The namespace attribute ..
Workaround: Convert the statement from import to include where you get this error. |
| AMBW-32951 | Summary: A SOAP service responding with mustUnderstand attribute as
true is ignored irrespective of selecting or deselecting the
Ignore mustUnderstand check box on the SOAP Reference binding. This behavior does not affect the client and server communication.
Workaround: None |
| AMBW-32760 | Summary: On creating SOAP Reference Binding with the concrete WSDL generated at run time with multilevel schema imports, the java.lang.NullPointerException is displayed when clicking the reference binding.
Workaround: None |
| AMBW-29098 |
Summary: When creating a concrete WSDL by right-clicking on the
Service Descriptor folder, the following error is generated at design time:
WSDL import error.
Workaround: None |
| AMBW-27870 | Summary: On importing WSDL with RPC Encoded style, a validation error is generated at design time since the underlying schema with namespace http://schemas.xmlsoap.org/soap/encoding/ is not generated.
Workaround: To remove the validation error and create the SOAP Reference Binding, download the encoding schema with the said namespace and ensure that schema is a part of the application module or the shared module. |
| AMBW-27435 | Summary: When module properties used from a shared module project were renamed, the changes made were not reflected at the SOAP binding level.
Workaround: Select the updated module property from the drop down in the SOAP binding. |
| AMBW-26806 |
Summary: When a REST service with a schema that uses a type which was imported from another XSD is invoked in a REST Reference Binding, it fails with the ServiceRuntimeException. Workaround: None |
| AMBW-23104 | Summary: When the WSDL uses multiple parts in the Request body of an operation, a design time validation error occurs on the generated SOAP reference binding. The application works fine at run time.
Workaround: None |
| AMBW-22981 | Summary: When the REST Service which is implemented with GET Operation with Response as String, then the content-type of the response is changed from application/json to text/plain.
Workaround: Use XSD Element in Response instead of String. |
| AMBW-21363 |
Summary: REST Call failed on run-time under non-UTF8 locale environment. Workaround: Set the default encoding of the AppNode to UTF-8 by adding "-Dfile.encoding=UTF-8" to java.extended.properties of "bw/6.3/config/bwappnode-an. tra_template". |
| AMBW-13607 |
Summary: REST Doc UI is not supported on Firefox browser. Workaround: Use other browsers for the Doc UI. |
| AMBW-13572 | Summary: For some use cases, REST Doc UI does not show the correct error code in case of Internal Server errors on the Server side.
Workaround: Check the raw message that contains the correct error code. |
| AMBW-13485 | Summary: REST Doc UI does not support browsers like Internet Explorer.
Workaround: Use Chrome browsers for the Doc UI. |
| AMBW-8982 | Summary: Changing the
Resource name in the REST service
Bindings tab, does not update the
Resource Service Path.
Workaround: None |
General
| Key | Description |
|---|---|
| AMBW-37594 | Summary: Breakpoints are not working when execution flow goes from one process to another.
Workaround: Select an activity where debugging with the breakpoint is halted. It enables the Resume button. Click the button to resume debugging. |
| AMBW-37521 | Summary: Unit testing is not working when providing an input schema with nested elements to the start activity.
Workaround: None |
| AMBW-34526 | Summary: LDAP authentication test connection button displays error when using admin user credential selected.
Workaround: None |
| AMBW-34416 | Summary: Failed to connect to AppNode using SSH client
Workaround: Use HTTP client. Preffered way is using curl. |
| AMBW-34404 | Summary: Incorrect trace is generated for the invoke process with default jaeger properties.
Workaround: Set JAEGER_SAMPLER_TYPE=const, and JAEGER_SAMPLER_PARAM=1 properties in the AppNode or AppSpace config.ini file. |
| AMBW-34343 | Summary: An application fails to start in
TIBCO Business Studio™ for BusinessWorks™ when you install the latest EMS driver.
Workaround: Restart TIBCO Business Studio for BusinessWorks. |
| AMBW-32878 | Summary: Exceptions are seen when generating the
manifest.json file from the existing EAR on a Linux platform.
Workaround: Though exceptions are displayed on the terminal, the manifest.json file will be generated successfully.
|
| AMBW-32792 | Summary: Serialization of an attribute '$bx_rootSpan' failed' for
Checkpoint activity. This issue occurs when the open tracing is used with the
Checkpoint activity.
Workaround: None |
| AMBW-32761 | Summary: The user will not be able to create the references for the custom operations like Merge, Update, Trace etc. using the drag and drop swagger file approach.
Workaround: Users can create the references for the custom operations using the REST Reference wizard.
|
| AMBW-31897 | Summary: The Process In-line schema namespace collision error is displayed when creating a sample.
Workaround: None
|
| AMBW-28941 | Summary: Ungrouping nested groups created inside a catch block of a group may not ungroup as expected.
Workaround: None |
| AMBW-28780 | Summary: While generating EAR for the sample
tibco.bw.sample.core.conversation.CrossProcessConversation, the following exception occurs in
TIBCO Business Studio for BusinessWorks
java.lang.NullPointerException.
Workaround: None |
| AMBW-28663 | Summary: The
tibco.bw.sample.policy.samlcredentialmapping.SoapHttpBinding sample fails intermittently with the error:
com.tibco.governance.agent.action.ActionException.
Workaround: None |
| AMBW-28448 | Summary: Current element of the Iterate group is not removed after ungrouping.
Workaround: The user needs to remove current element manually after ungrouping the Iterate group. |
| AMBW-28378 | Summary: When a Process Property is renamed , the change is not reflected in the activity and an error is displayed.
Workaround: None |
| AMBW-28319 | Summary: WSDL interface fails to resolve correctly if multiple WSDLs share the same target namespace and the SOAP invoke is created with an external binding reference.
Workaround: Instead of an external reference binding, use binding reference. |
| AMBW-28285 | Summary: In a shared module and shared module-application module combination, multiple WSDLs with the same target namespace are not supported at design time and run time.
Workaround: None |
| AMBW-28264 | Summary: When groups with the On Catch, Catch All and the OnEvent faults are created inside a constructor or a proxy operation, the activities inside them are lost after ungrouping.
Workaround: None |
| AMBW-27253 |
Summary: The
Identity Provider field in the WSSConsumer Policy resource does not support module properties.
Workaround: None |
| AMBW-25073 | Summary: The option to test connections, for example JMS or sFTP, in a shared resource that has a profile is not supported in
TIBCO Business Studio for BusinessWorks.
Workaround: Specify the server configuration details as literal value or module properties. |
| AMBW-24508 | Summary: TIBCO-THOR-FRWK-CMN-500001:Error while renaming bundle file to final location: - error could be due to low disk space.
Workaround: None
|
| AMBW-19746 | Summary: When you initialize the module shared variable of XSD type with the select value option to point the XML instance, application fails to start at run time.
Workaround: Enforce the default encoding of AppNode JVM to UTF-8 by adding -Dfile.encoding=UTF-8 in the bwappnode.tra file.
|
| AMBW-19540 |
Summary: When a project contain abstract and concrete WSDL using same target namespace, a validation error is generated. Workaround: None |
| AMBW-18459 | Summary: The ability to reference from a standalone (external) schema to an inline schema is not supported. If your project contains such a reference, a validation error is generated.
Workaround: Externalize the WSDL-inline schema and change the import statements to reference the newly created (external) schema. |
| AMBW-17998 | Summary: The EAR file generated using
bwdesign utility does not support non-ASCII characters.
Workaround: None |
| AMBW-16256 |
Summary: The first attempt to change the data type of an Operator's input or output schema element fails and the change is not committed. Subsequent attempts complete without any failure.
Workaround: To commit the change, you must press the return key after every change. |
| AMBW-14861 | Summary: Unable to enter an XPath expression on a transition using the XPath Builder. This issue is observed on Mac OS only.
Workaround: Enter the XPath expression directly in the Properties tab > Expression field for the transition without using the XPath Builder. |
| AMBW-13823 | Summary: Directory browser dialog in BW Context Sensitive Help preference setting page does not consistently popup on Mac OS X 10.9.2
Workaround: Copy and paste the directory path into the configuration field instead of using directory browser to pick it. |
| AMBW-12490 | Summary: Under certain circumstances, substitution types do not resolve properly in the mapper. The mapper shows errors for them.
Workaround: Try closing and reopening the project. If that does not solve the issue, try closing and reopening Eclipse. If the errors still persist, perform a project clean (that is, go to the Project menu and click Clean...). |
| AMBW-11624 | Summary:
TIBCO Business Studio for BusinessWorks hangs when opening SQL Builder if the database details on the
JDBC shared resource are changed from PostgreSQL to MySQL after a query has been created using SQL builder.
Workaround: None |
| AMBW-11534 | Summary:
TIBCO Business Studio for BusinessWorks crashes occasionally on Windows 2012 R2 platform when switching workspace from
.
Workaround: Retry by switching the workspace. |
Mocking Support
| Key | Description |
|---|---|
| AMBW-35856 | Summary: If an application has multiple sub processes and you apply mocking in those sub processes, then the Mocking symbol and
Tests tab are not visible when you revisit the sub process. However, this functionality works fine at run time.
Workaround: Click in the Process Editor. Once the Tests tab is visible, click the tab and then select the activity to be mocked. |
| AMBW-35855 | Summary: When an application has more than two sub processes and if you apply mock on the activity in both sub processes, then you cannot delete the mock.
Workaround: None |
| AMBW-35851 | Summary: Mocking does not work for SendHTTPRequest, RenderJSON, FTPGet, and FTPPut when there are no namespaces present for direct child elements of the root element.
Workaround: Add xmlns="" attribute for direct child element of root element. |
| AMBW-35841 | Summary:: Mocking is not supported for Send HTTP Request with MIME attachments.
Workaround: None |
Migration
| Key | Description |
|---|---|
| AMBW-37570 | Summary: The exceptions are visible on the console, but the project executes correctly.
Workaround: None |
| AMBW-36077 | Summary: After migration, if the migrated project contains any SOAP service or client binding that uses SOAP RPC Encoded arrays, the following WSDL validation error occurs:
WSDL In-line schema SOAP encoded array type error. In-line schema in WSDL file contains SOAP encoded array type which requires a fix pattern. Workaround: Download the SOAP Encoding schema from 'http://schemas.xmlsoap.org/soap/encoding/', and put it into the TIBCO BusinessWorks Container Edition project. |
| AMBW-35926 | Summary: The migration tool does not support external schema for multi-part message in the bindings.
Workaround: Create wrapper schemas for all multi-part messages of WSDL. |
| AMBW-35899 | Summary: Currently, only copy-of mapping is supported for context mapping of headers.
Workaround: You can either create One-to-one mapping manually or use a copy-of option for context mappings. |
| AMBW-33749 | Summary: After migration, additional round brackets in the names of the folder for externalized schema creates issues at run time.
Workaround: Remove the special characters after migration in the folder names. |
| AMBW-30656 |
Summary: A schema cannot contain two global components with the same name.
Workaround: Modify one of the schema namespaces or element names, so that the names are unique. |
| AMBW-30476 | Summary: After migration, the input mapping for the
End activity which refers to a multi-part WSDL message displays validation errors.
Workaround: A WSDL message is not supported by a mapper. Create a new .xsd schema element with the structure similar to associated WSDL message, and then map the schema element in place of WSDL message. |
| AMBW-26746 | Summary: The
TransformXML activity from
TIBCO BusinessWorks Container Edition 5.x did not migrate correctly if the Input/Output style of the activity was set to
TREE in the
TIBCO BusinessWorks Container Edition 5.x project.
Workaround: None |
| AMBW-14547 |
Summary: When you migrate an TIBCO ActiveMatrix BusinessWorks 5.x project containing in-built functions in the
JDBC Query activity, an Invalid Column name error is thrown in the
JDBC Query activity.
Workaround: Use an Alias instead of the in-built functions in the TIBCO BusinessWorks Container Edition 5.x project. |
| AMBW-14295 | Summary: After migration, the output of project with Rest and JSON activities does not match with the input of the other activities in the migrated project.
Workaround: None |
| AMBW-13683 | Summary: Shared resource module property references in the migrated TIBCO ActiveMatrix BusinessWorks 5.x projects do not show up correctly on non-Windows platforms.
Workaround: Close and reopen the project. |
| AMBW-9969 |
Summary: ActiveMatrix BusinessWorks 5.x projects with SOAP headers configuration in SOAP activities are not properly migrated to
TIBCO BusinessWorks Container Edition
6.x.
Workaround: SOAP functionality in TIBCO BusinessWorks Container Edition 6.x is achieved through SOAP Binding where its detail configuration is outside of TIBCO BusinessWorks Container Edition Process. The SOAP headers definition are defined at the Binding configuration and configured as generic context parameters for the Process. In the Process, you can use the Get Context activity (from Basic Palette) to retrieve and process the headers as context data. You can do this manually to complete the migrated project. |
HTTP Palette
| Palette HTTP | |
|---|---|
| Key | Description |
| AMBW-36777 | Summary:Error occured on
Send HTTP Request activity with client SR using HTTP1 Apache HttpComponents and connector SR using HTTP2.0 with Follow HTTP1 Compliance checked.
Workaround: Use the Jetty client as the client library for implementation under HTTP client shared resource. |
JDBC Palette
| JDBC Palette | |
|---|---|
| Key | Description |
| AMBW-36229 | Summary: Unnecessary error logs are displayed in the log file.
Workaround: None |
| AMBW-23464 | Summary: The Oracle DataDirect driver does not support cursor datatype.
Workaround: Use native drivers instead of DataDirect drivers. |
| AMBW-23260 | Summary: MySQL Community Edition is not supported for Data Direct drivers
Workaround: Use native drivers instead of DataDirect drivers. |
| AMBW-23193 | Summary: When using DataDirect drivers with a JDBC Shared Resource, that is linked to a JDBC process, the SQL Builder Wizard does not work correctly.
Workaround: Use native drivers. |
| AMBW-20130 | Summary: The login timeout value is not effective when connecting to a Windows OS database. The
JDBC Query activity fails with the error,JDBCConnectionNotFoundException at runtime without honoring the
Login Timeout
value specified in the
JDBC Connection Shared Resource.
Workaround: None |
| AMBW-14624 | Summary: The
Set Explicit Nil check box for Objects and Collections in
JDBC Call Procedure activity is disabled.
Workaround: None |
| AMBW-14547 | Summary: When you migrate an TIBCO ActiveMatrix Business works™ 5.x project containing in-built functions in the
JDBC Query activity, an invalid column name error is thrown in the
JDBC Query
activity.
Workaround: Use an Alias instead of the in-built functions in the ActiveMatrix Business works 5.x project. |
| AMBW-11667 | Summary: Using any in-built function in
JDBC Query activity without "Alias" fails to execute the application and throws an
Invalid Column name error at run time.
Workaround: Use "Alias" to work with any in-built function in JDBC Query activity. |
| AMBW-11624 | Summary:
TIBCO Business Studio™ for BusinessWorks™ hangs when opening SQL Builder if the database details on the JDBC shared resource are changed from PostgreSQL to MySQL after a query has been created using SQL builder.
Workaround: None |
| AMBW-8855 |
Summary: The localized error messages of JDBC connection are not displayed correctly in
TIBCO Business Studio for BusinessWorks.
Workaround: None |
XML Palette
| XML Palette | |
|---|---|
| Key | Description |
| AMBW-14292 | Summary:
Parse XML activity displays blank ErrorCode and ErrorMessage for activity output data validation error.
Workaround: None. |
| AMBW-28657 | Summary: When the
Format Using Default Namespace option is enabled for the
Render XML activity,
TIBCO Business Studio for BusinessWorks displayed an error at runtime.
Workaround: None |
REST and JSON Palette
| REST and JSON Palette | |
|---|---|
| Key | Description |
| AMBW-28795 | Summary: The
Parse JSON activity fails to pick up the prefixes defined in the namespace registry and provides the output with the default namespace prefixes.
Workaround: None |
| AMBW-14292 | Summary:
Parse XML activity displays blank ErrorCode and ErrorMessage for activity output data validation error.
Workaround: None |
Policies
| Key | Description |
|---|---|
| AMBW-34607 | Summary: Marketo plugin container edition breaks with the recent JRE upgrade.
Workaround: Please refer Marketo plug-in documentation for more information. |
| AMBW-19513 | Summary: If a SOAP binding is not configured with Transport, the
Add New Policy icon should be disabled, the
Policy field should not be displayed in the tree view, and a NULL pointer exception is generated if you try to add a policy on the binding.
Workaround: None |