Known Issues

Summary: On AMX 3.4.2, while executing the following scenario:

• Application: SOAP(HTTP) -> JAVA(XMLBeans)

• DataSize - 1K

• Node and application settings - default

It is observed that the below-blocked call time is increased and an error is observed in node log in AMX 3.4.2 as compared to AMX 3.4.1.

71.1% - 103 s java.util.UUID.randomUUID blocked call time is increased and an error is observed in node log

Workaround: None

Summary: On AMX 3.4.2, while executing the following scenario:

• Application: REST(JSON) → JAVA (Post method)

• DataSize - 1K

• Node and application settings - default

It is observed that the below-blocked call time is increased in AMX 3.4.2 as compared to AMX 3.4.1.

94.3% - 287 s org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass blocked call time is increased.

Workaround: None

Summary: On AMX 3.4.2, while executing the following scenario:

• Application: SOAP(HTTP) -> JAVA(JAXB)

• DataSize - 1K

• Node and application settings - default

It is observed that the below-blocked call time is increased in AMX 3.4.2 as compared to AMX 3.4.1.

40.1% - 264 s java.util.concurrent.ArrayBlockingQueue.poll
28.6% - 189 s java.util.concurrent.ArrayBlockingQueue.offer
18.3% - 120 s java.util.concurrent.ArrayBlockingQueue.take

Workaround: None

Summary: Load tests were executed with increasing concurrency and it is observed that the memory utilization for the Policy Director scenario is higher compared to the Default scenario in AMX3.4.2. Also for 5 users concurrency Out of memory is observed for the default heap and 4 GB heap, while executing the following scenario:

• Application: SOAP(HTTP) -> JAVA(XMLBeans)[Basic Authentication]

• DataSize - 1K

• Node and application settings - default

Workaround: None

Workaround: None

Workaround: Re-install the Node as the Node is in a corrupt state.

Workaround: Specify the timeout value using the application-level property. For example, if the name of an application is weatherApp, the following property can be specified for the promoted service or component service that is promoted: java.property.weatherApp.invocationTimeoutInMilliseconds.

For example, the following property sets the timeout value to 2 minutes:

java.property.weatherApp.invocationTimeoutInMilliseconds=12000

Workaround: Separate the service consumer and the service provider so that they are both in two separate user applications.

Workaround: If you encounter this issue:

1. Open a command prompt where tibcohost.exe is located.
2. Uninstall existing TIBCO® BPM Enterprise Windows service by running:

   tibcohost.exe --uninstall

3. Install the Windows service again by running:

   tibcohost.exe --install

    

Workaround: Edit the HTTP Connector resource template to use blocking IO. For more information, see the section "Managing Resource Templates" in TIBCO ActiveMatrix Service Grid Administration.

Workaround: Configuring the connection pool using system properties specified for the target node applies them to all instances deployed to that node.

Refer to the Oracle documentation for more information: http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html.

Summary: Logging configuration changes takes time to get effectively applied, as compared with earlier BPM 4.3.2 version.

For Instance, if log appender level changed from Trace to Info, it takes 15-20 mins to print respective level logs.

Workaround: None

Summary: After upgrading from older versions (3.3 or 3.4), the TIBCO Configuration Tool still offers the option to configure the TIBCO Service Performance Manager (SPM) dashboard. However, it's important to note that SPM functionality has been removed and is no longer supported in AMX 3.4.2. End user is requested not to use this option.

Workaround: None

Summary: SPM folder under AMX_Home/admin/amxadmin/samples path is obsolete. Users are requested to refrain from referring the SPM folder as this feature is removed and not supported any more from AMX 3.4.2

Workaround: None

Workaround: After applying the logger at application level, re-start the respective application.

Workaround: Upgrade BPM 4.3.2 to 4.3.3 to resolve this expected behavior.

Workaround: Upgrade BPM 4.3.2 to 4.3.3 to resolve this expected behavior.

Summary: Support for the TIBCO enabled JDBC driver for IBM DB2 4.32.28 is added in TIBCO ActiveMatrix® Service Grid 3.4.2 but it is not visible in the TCT Third-party Driver Configuration Wizard List.

Workaround:

1. Open a Third-party Driver Configuration Wizard from TCT.

2. Select TIBCO enabled JDBC driver for IBM DB2 4.24.92 Driver.

3. Download the latest JDBC Third-Party Driver Jar of DB2 11.5.x (Jar name: db2jcc4.jar and Version: 4.32.28).

4. Give the path of the db2jcc4.jar folder in TCT and Configure.

Summary: After the successful upgrade from AMX330 HFx to AMX342, in the SystemNode log, you see the following errors related to logservice, if you have selected Deploy log service and monitoring service in AMX330:

1. [com.tibco.amx.commonlogging.logservice.app] com.tibco.amx.cf.logger.lifecycle -  java.lang.IllegalStateException: org.springframework.beans.factory.BeanCreationException
2. [com.tibco.amx.platform] com.tibco.amx.it.webapp.WebAppImplementationAdapter - Exception occurred during webApp un-deployment of component 'WTPLogService'
3. com.tibco.amx.cf.logger.lifecycle -  java.lang.NullPointerException: null at com.tibco.governance.mcr.aggregator.runtime.core.GovernanceAggregator.registerExtensionPoint(GovernanceAggregator.java:567) ~[?:?]

Workaround: None

Summary: Test Connection with SQL Server 2019 is failing with the following error "sun.security.validator.ValidatorException: PKIX path building failed".

Workaround: To configure the third-party driver mssql-jdbc-11.2.3.jar for Microsoft SQL Server 2019 or any backwards compatible Microsoft SQL Server database, you must add trustServerCertificate=true in the JDBC URL.

Example JDBC URL:

jdbc:sqlserver://test-localhost:1433;DatabaseName=dbname;trustServerCertificate=true

When you download the Microsoft JDBC Driver for SQL Server (version 11.2.3), the default JAR name is mssql-jdbc-11.2.3.jre8, but when configuring the third-party driver by using TCT, you must rename mssql-jdbc-11.2.3.jre8.jar to mssql-jdbc-11.2.3.jar.

Summary: When AMX 3.3.0 HF27 with an Admin server configured with Deploy Log Service and Deploy Monitoring Service is upgraded to AMX 3.4.2, JMS Appenders appear on the Logging Appenders page.

Workaround: None

Summary: User applications with IT plug-in scenarios that contain the old javax.jms version fails and displays the following error:

Import-Package: javax.jms;version="[1.1.0,2.0.0)"			  

Workaround: Fix all instances of Import-Package error by upgrading javax.jms;version="[1.1.0,2.0.0)" to javax.jms;version="[2.0.0,3.0.0)".

Workaround:

1. Go to this location:

   <ConfigHome>\tibcohost\Admin-amxadmin-instanceOne\data_3.2.x\host\plugins\ri_tibco.admin.default.ssl.server_SystemNode_1.0_1686560749194.jar.

2. In the file ri_tibco.admin.default.ssl.server_SystemNode_1.0_1686560749194.jar, change the TLS (Transport Layer Security) version information from 1.2 to 1.3.

3. Save this file.

4. Restart the administrator.

5. Check if the admin SSL protocol is showing TLS (Transport Layer Security) Version 1.3.

Workaround:

When upgrading from AMX 3.3.0 HF27 to AMX 3.4.2, do not select the Deploy Log Service and Deploy Monitoring Service when creating an admin. However, if they were selected while creating the admin, remove the "LogService" and "Payloadservice" applications from the system applications explicitly from the GUI and CLI.

Summary: Host node installation fails after upgrading fromTLS (Transport Layer Security) Version from 1.2 to TLS (Transport Layer Security) Version 1.3.

Workaround:

1. Go to this location:

   <ConfigHome>\tibcohost\Admin-amxadmin-instanceOne\data_3.2.x\host\plugins\ri_admin.default.jmx.ssl.sip_SystemNode_.jar

2. Open sr_admin.default.jmx.ssl.sip_SystemNode.xml file and change the TLS (Transport Layer Security) version information from 1.2 to 1.3.

3. Save this file.

4. Restart the administrator.

5. Create a host.

Summary: (Linux RHEL 9) For AMX 3.4.2, TCT fails and displays the following error.

Error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory.

Workaround: Install the libnsl package using the command:

$ sudo yum install libnsl

Summary: Consider the following upgrade path:

1. TIBCO ActiveMatrix Service Grid 3.3.0 (including hotfixes) with TIBCO ActiveMatrix Binding Type for REST 3.3.0 (hotfix 005) is installed.

2. Upgrade to TIBCO ActiveMatrix Service Grid 3.4.0 (including hotfixes).

3. Upgrade to TIBCO ActiveMatrix Service Grid 3.4.1 hotfix 01.

4. Install TIBCO ActiveMatrix Service Grid 3.4.1 hotfix 02.

5. Run Enterprise Deployment Health Check. The following fails on this setup.

Workaround:

1. Navigate to <TIBCO_HOME>/amx/3.4/bin and edit ant.tra.

2. Replace [[path.separator]] in tibco.class.path.extended with;

(Semicolon).

tibco.class.path.extended=%TIBCO_HOME%/components/shared/1.0.0/plugins/com.tibco.tpcl.org.apache.tools.ant_1.9.9.001[[path.separator]]%TIBCO_HOME%/tools/lib/antpackage.jar

Updated:

tibco.class.path.extended=%TIBCO_ HOME%/components/shared/1.0.0/plugins/com.tibco.tpcl.org.apache.to ols.ant_1.9.9.001;%TIBCO_HOME%/tools/lib/antpackage.jar

Summary: After installing TIBCO ActiveMatrix Service Grid hotfix 02 in the replicated Administrator setup, the following error is observed in the following scenario:

1. Create a runtime host and node.

2. Change the shared folder location by using the following command:

   ant -f sharedWorkFolder_build.xml -Dadmin.shared.folder="<NEW SHARED FOLDER LOCATION>" -Dconfig.home="<CONFIG_HOME>" -Denterprise.name="<ENTERPRISE_NAME>"

   The following error occurs:

   [AMXAdminTask] 14 Mar 2023 01:52:31 ERROR - Resource Instance Update failed
   [AMXAdminTask] 14 Mar 2023 01:52:31 ERROR - TIBCO-AMX-CLI-000343:
   Install resource instance 'tibco.admin.default.keystore' failed :
   Please see the cause for more details
   			  

Workaround: None.

Workaround: None.

Workaround: None.

Upgrade from ActiveMatrix Service Grid 3.1.5 to version 3.3.0 by using scripts. Then upgrade from version 3.3.0 to version 3.4.0. Then upgrade from version 3.4.0 to version 3.4.1.

Workaround:

• Before upgrading to ActiveMatrix Service Grid 3.4.1, update java.heap.size.max=512M to java.heap.size.max=1024M in the <TIBCO_HOME>/amx/3.4/bin/nodeutil.tra file.
• After performing the preceding step, upgrade to version 3.4.1 is successful but some runtime host fails to start after upgrade and the com.tibco.amx.platform.artifactserver application in the SystemEnvironment is in the Start failed state.
  
  In this case, manually start Host and Nodes OR undeploy and deploy the com.tibco.amx.platform.artifactserver application.

Workaround: None. This issue does not have a functional impact. Everything works as expected.

java.lang.RuntimeException: XPathFactory#newInstance() failed to create an XPathFactory for the default object model: http://java.sun.com/jaxp/xpath/dom with the XPathFactoryConfigurationException: javax.xml.xpath.XPathFactoryConfigurationException: java.util.ServiceConfigurationError: javax.xml.xpath.XPathFactory:

Workaround: None

Workaround: None

javax.net.ssl.SSLHandshakeException: DH ServerKeyExchange does not comply to algorithm constraints

Workaround: Update your keystore to use the DH key size larger than 1024.

OR

jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1, RC4, DES, MD5withRSA, \
DH keySize < 768

Workaround: When the hosts are secured, SystemNode is configured with TLSv1, which is the supported TLSv1 in versions of ActiveMatrix Service Grid prior to 3.4.0. Starting from ActiveMatrix Service Grid 3.4.0 and later, TLS1.2 is supported, and all the Hosts are updated to automatically use TLSv1.2 when upgraded to 3.4.1, except the Administrator (SystemNode).

When you encounter this issue, run the following command after upgrading to ActiveMatrix Service Grid 3.4.1 to update Administrator (SystemNode) to support TLSv1.2.

Navigate to <TIBCO_HOME>/amx/3.4/bin folder and run the following command:

tibamx_hostmanager updateAdminToTLSv12 -configHomeLocation <TIBCO_CONFIG_HOME>

Workaround: None

Workaround:

1. Set the following property:

   java.property.com.tibco.amx.decouple.Manual.Nodes=false

2. Restart ActiveMatrix Administrator.
3. Upgrade SystemHost to 3.4.0 and downgrade again.

Workaround: Stop the TIBCO Configuration Tool and provide correct information for ActiveMatrix Administrator configuration. For example, port, SSL information. Run the downgrade wizard again.

Workaround: Log out from the previous browser session.

Summary: After upgrading to ActiveMatrix 3.4.0, the ActiveMatrix 3.3.0 Hotfix<x> runtime host fails to downgrade with the following error:

product feature com.tibco.amf.sharedresource.extensions.runtime.tibcohost.product.feature 3.3.xx.000 contains a release unit com.tibco.amf.hpa.core.runtime.services.feature 1.5.0.003 that does not exist in the machine model

Workaround: Always select the Mediation Runtime option while installing the Runtime Host profile for the remote host.

Workaround: None. Do not click the Configure TIBCO Service Performance Manager - V2.3 option.

Workaround: Reconnect the EMS connections by clicking Admin Configuration > Admin Server > Transport Configuration tab > Administrator Reconnect. After the reconnection, all the entities are shown as online.

Summary: The TIBCO ActiveMatrix Governance Agent for TIBCO BusinessWorks Notification screen of the Create TIBCO ActiveMatrix Policy Director Administrator Server - V3.4 wizard is removed in 3.4.0. However, some shared resources related to this screen (EMS ConnectionFactory, JMS Destination, JNDI Connection) are created in ActiveMatrix Administrator. These shared resources are added as an application property and can be viewed from the ActiveMatrix Administrator UI:

• Application name: com.tibco.ampd.ogp.de
• Properties: bwJmsSharedResource and bwAgentAdapterJmsDestination

Workaround: The shared resources created by the screen are not used. You can ignore them.

Workaround: None

Summary: In the TIBCO Configuration Tool, host names or DNS names cannot have underscores in their names. As a result, TIBCO Configuration Tool fails if the name of the Available Group Listener contains underscores while configuring the AlwaysOn Database Setup in SQL Server 2017.

Workaround: Do not use underscores in the name of the Available Group Listener while configuring the AlwaysOn Database Setup on SQL Server 2017.

Summary: On Microsoft Windows, when you try to update JRE by using the TIBCO Configuration Tool, occasionally the following error occurs:

Caused by: TIBCO-AMX-TOOLS-JREUPDATER-000048: Cannot write to the file. TIBCOHOME\amx\3.4\scripts\rpflauncher_classpath_3.4.0.tra.

Workaround: Run the command two or three times until it succeeds.

Summary: Occasionally, because of manual intervention or execution of certain scripts, the network time of the machine where Active Directory Federation Services (ADFS) or WebApp is hosted might be out of sync and result in an authentication failure for a response being too old.

Workaround: The network time of the machine must be synchronized. For Linux, the synchronization must happen with the Network Time Protocol server. For Windows, use the Windows time service. There are standard operating system level procedures for synchronizing the machine network time.

Summary: If you invoke a REST service binding with an OpenID Policy through a SOAP client such as SoapUI, it always sends an Access Token, which is an opaque token. Access Tokens are not currently supported.

Workaround: Use the ID Token (which is a JWT token) generated by the Access Token URI to send the request in SoapUI.

Workaround: Restart the ActiveMatrix Administrator server.

TIBCO-AMX-CLI-000944: Failed to downgrade TIBCO Host instance(s).
TIBCO-AMX-CLI-000942: Downgrade TIBCO Host instance <instance name> is not possible.

Workaround: None

Workaround: None

Workaround: None

Workaround: None

Workaround: To generate the DAA file, make sure that the RequiredExecutionEnvironment field in the Manifest.MF file is empty. It allows you to create the DAA and deploy it at run time.

Workaround: Ensure that all the runtime hosts that are in the selection CONFIG_HOME must be bound to the ActiveMatrix Administrator Server from the CONFIG_HOME.

TIBCO-AMX-ADMIN-021085: Failed to update the notification transport!, Caused by:
TIBCO-AMX-ADMIN-021281: The number of hosts in this enterprise is more than 10. 
Please use the Administrator Command Line Interface for updating the Notification Transport.

Workaround: None

Workaround: None

Workaround: Re-create the DAA in 3.4.0.

For an internal HTTP connector, if the Use Non-Blocking IO Sockets checkbox is cleared and a value greater than 1 is specified in the Acceptor Threads field, all except one of the Acceptor Threads is in a blocked state.

Workaround: Keep the Use Non-Blocking IO Sockets checkbox on the Advanced tab cleared.

Workaround: Install using the silent installation mode if you want to specify an environment name.

Caused by: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

Workaround: Avoid using quotes (“ ”) and hyphen (-) in the username.

Workaround: Start a Microsoft Windows NT host or service manually.

• Upgrade ActiveMatrix TIBCO Host Instance
• Upgrade ActiveMatrix Administrator
• Upgrade Nodes Hosting TIBCO® BPM Enterprise Instance
• Upgrade TIBCO® BPM Enterprise Instance Application [Upgrading Database]

Workaround:

1. Stop tibcohost.
2. Apply the TIBCO ActiveMatrix 3.3.0 Hotfix again by running the patch manager.
3. Start tibcohost.
4. From ActiveMatrix Administrator, check Systemnode and bpmnode. The expected hotfix version is displayed.
5. Open TIBCO Configuration Tool to upgrade to TIBCO® BPM Enterprise 4.0.0. Select the last two options:

   • Upgrade Nodes Hosting TIBCO® BPM Enterprise Instance

   • Upgrade TIBCO® BPM Enterprise Instance Application [Upgrading Database]

Workaround In addition to providing the JDBC URL of the mirrored servers in SQL Server 2012, you must set the IP and hostname of both the primary and secondary database servers in the hosts file. The location of the host file depends on the operating system:

• Windows: ROOT_DIR\system32\drivers\etc\hosts
• UNIX/Linux: /etc/hosts

For example, you have two database servers. The primary server's IP is 192.167.71.42 and its hostname is amx-db42. The secondary server's IP is 192.167.71.60 and its hostname is amx-db60. You would provide the following JDBC URL for these two mirrored primary and secondary servers:

jdbc:sqlserver://192.167.71.42:1433;databaseName=db1;failoverPartner=192.167.71.60

To ensure that the ActiveMatrix Administrator successfully connects to both servers and allows for seamless switching between them using SQL statements, you must add the following entries to the host file:

192.167.71.42 amx-db42
192.167.71.60 amx-db60

Workaround: First undeploy and then redeploy these applications after upgrading all System Nodes.

Workaround: Provide a URL in the Provider URL field on the Resource Template.

Workaround: None

Workaround: None

Workaround: Restart the Enterprise Message Service server. As there is no locking in messaging associated with an XA resource, this issue is not serious.

Workaround: Manually create JNDI resource templates required for defining inbound and outbound destination configurations.

Workaround: Recover the requests from the error queue.

Workaround: Do not use a type Message for Context Provisioning related to JMS Binding.

Workaround: None

Workaround: Ensure that the JMS binding that has a JMS Transacted One-Way Policy is deployed on the same node as that of one or more components it is wired to.

javax.jms.IllegalStateException: Not allowed to use transacted session on routed queues

Workaround: Enterprise Message Service does not support transactions on routed queue consumers. Enterprise Message Service 6.0 added an explicit check to prevent this. You can restore the old behavior by setting the following configuration parameter:

allow_unsupported_tx_routed_q_consumers = true

Workaround: Create a JMS binding after renaming the WSDL operation or reassign the WSDL file to an existing JMS binding.

Workaround: None

[ERROR]com.tibco.trinity.runtime.base.provider.identity.CipherSupport

Workaround: Such errors are harmless and do not mean that the upgrade failed. No action is required.

Workaround: None.

Summary: Hawk Console does not display alerts for newly created Rulebase for the below mentioned Node microagent methods.

 a)getBindingInfo
 b)getBindingOperationStats
 c)getComponentOperationStats
 d)onBindingOperationStats
 e)onComponentOperationStats

Workaround:

1. Open hawkconsole.cfg and uncomment the property sql_schema_path.

2. Go the path on disk mentioned in the property sql_schema_path. For ex: <HAWK_HOME>/<HAWK_CONFIG>/cfgmgmt/hawk/sql/

3. In this folder you will find 2 files data.sql and schema.sql. Open schema.sql and update the table named "alert" and adjust the size of the column name which throws an error from 28 to 768 -> data_index varchar(768).

4. Restart Hawk Console.

Summary: After the successful upgrade from AMX330 HF27 to AMX342, on Hawk Console, invoking method changeMonitoringConfig() for microagents fails with the following error.

"class java.lang.Integer cannot be cast to class java.lang.Long (java.lang.Integer and java.lang.Long are in module java.base of loader 'bootstrap')"

Workaround: Please refer to changeMonitoringConfig section in the Hawk ActiveMatrix® Plug-in User’s Guide, to troubleshoot this issue.

Workaround:

1. In the HAWK-HOME\hawk\7.1\lib from HawkHome\hawk\7.1\lib\ext\console-ext file, replace the below-mentioned jars with version 5.1.8 jars.

   spring-beans.jar > spring-beans-5.1.8.RELEASE.jar
   spring-context.jar > spring-context-5.1.8.RELEASE.jar
   spring-core.jar > spring-core-5.1.8.RELEASE.jar

2. Finally, start tibhawkconsole.

Workaround: None

Workaround: Before upgrading to ActiveMatrix 3.4.0, apply ActiveMatrix 3.3.0 Hotfix 10 or higher.

Summary: When a Hawk ActiveMatrix Plug-in (HKAM) is used for large-scale systems, tibhawkagent stops automatically with the following error:

RV: DrainQueue: out of memory.

Workaround: If HKAM is configured with more than 10 hosts, increase the memory of tibhawkagent.

To change the memory of tibhawkagent:

1. Open tibhawkagent.tra located at <hawk.config.home>/tibco/cfgmgmt/hawk/bin.
2. Change values of -XX:MaxPermSize, java.heap.size.initial and java.heap.size.max based on the number of hosts.

For 60 hosts, the following values are recommended:

• java.heap.size.max = 4 GB
• -XX:MaxPermSize = 1 GB

Workaround: After a Notification Transport Server Configuration update, you must manually update the TIBCOHost's HKAM rulebases.

Workaround: Change the default HKAM rulebase for host and node. Make it event-driven rather than polling at a fixed interval.

• changeMonitoringConfig
• getBindingOperationStats
• getComponentOperationStats
• getConfig

Workaround: None

Workaround: Change the EMS values for -user, -encryptedPassword, and -server of the new notification server manually in the hawkems-<host_name>.hma file.

<arg>-user</arg>
<arg>${new_username}</arg>
<arg>-encryptedPassword</arg>
<arg>${new_password}</arg> 				
<arg>-server</arg>
<arg>${new_notification_server_url}</arg>

Error loading microagent from com.tibco.hawk.microagent.commonlogging.publisher.CLEventPublisherMicroAgent: java.lang.IllegalArgumentException

Workaround: None

Workaround: None

Workaround: None

Workaround: Use Hawk 4.9 instead of Hawk 5.0.

Workaround: None

Workaround: Click Done, and open the microagent again. Alternatively, restart Hawk Display.

Workaround: Prefix powershell.exe in the rulebase of the TibcoHost with the absolute path of powershell.exe.

Workaround: Remove the slf4j jars and jars with different versions of slf4j from the agent classpath.

Workaround: None

Workaround: Prefix powershell.exe in the rulebase of the TibcoHost with the absolute path of powershell.exe.

Workaround: Manually delete the rulebase to avoid error entries in the HAWK.log file.

Workaround: Restart Hawk Agent to clear the cache.

[ERROR] com.tibco.n2.rtc.ap.ActionProcessor - [ERROR] - {WS_REQUEST_EXCEPTION} - Workspace caught an Exception ¬{extendedMessage=`Invalid Security Context: Missing requested attribute

Workaround: Redeploy the application and restart Workspace and Openspace.

Workaround: Deselect the newly added WebApp component (by selecting any area on the canvas that is not the original WebApp component from the imported project), then select the newly added WebApp component again. The Thread Context Class Loader Type dropdown list is enabled.

Workaround: None

Workaround: To configure or change the connector name in TIBCO ActiveMatrix Administrator:

1. In TIBCO Business Studio, open the project containing the Web Application component.
2. Promote the defaultConnector property to a composite level:
   1. Select the defaultConnector property on the component.
   2. Right-click and select Promote.
3. Make the composite property a substitution variable so it can be substituted in TIBCO Administrator before deployment.
4. Right-click on composite and select Create DAA.
5. In ActiveMatrix Administrator, make sure that a connector with the same name is created in ActiveMatrix Administrator and deployed on to the node before the Web Application DAA is deployed.

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Violation of UNIQUE KEY constraint "UQ__Mcr2Stat__1C012A471DC5DDE4".
Cannot insert duplicate key in object 'dbo.Mcr2StatisticsMetric'. 
The duplicate key value is (93, 21, 22, 3, -1).
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement SQLServerPreparedStatement.java:404)					 

Workaround: None

Retrying database transaction after error: Processing of metric requestsIn for event com.tibco.governance.amxserviceprobe.ServiceProbeInstruments.ServiceRequestIn failed for measure Total and time window Since Started Time Window 
Retrying database transaction after error: Processing of metric faults for event com.tibco.governance.amxserviceprobe.ServiceProbeInstruments.ServiceExecutionTime failed for measure Total and time window Since Started Time Window	 

Workaround: Such exceptions are benign and do not require any action.

Workaround: Replicate your configuration before upgrading to ActiveMatrix release 3.3.0.

If an application is deployed and not used, the value for uptime is 0.

Workaround: None

Workaround: Either make sure that the system node is running using admin replication or restart the applications for which incorrect statistics are seen.

Workaround: None

Workaround: The correct average component processing time is available in the Components and Applications tabs.

[ERROR] org.apache.axis2.engine.AxisEngine - bean:name=govObjFilterServiceMBean

Workaround: None. This error can be safely ignored.

Caused by: java.lang.RuntimeException: Statistics aggregator is closing down, rolling back transaction

Workaround: Ignore the error.

Workaround: None

Workaround: Change the application name during deployment. The application name must be unique for an enterprise. The dashboard shows the correct status and uptime.

Workaround: View the metrics on the promoted reference.

Workaround: None

Workaround: Configure the ActiveMatrix Administrator server in fault tolerant mode.

Workaround: Re-create all JMS Connection Factory and Destination resources in TIBCO Business Studio.

Workaround: To resolve this:

1. Import all projects into the workspace.
2. Restart TIBCO Business Studio.
3. Run Project > Clean > Clean all projects.

Workaround: Open the style sheet in a text editor and save it manually in a format without using BOM.

Workaround: None

Workaround: Select Project > Clear from the menu bar and the validation restarts. The error markers disappear unless there are actual problems that remain.

Receive Wrong Transfer data 

Workaround: None

Workaround: Once the schema is created, you can browse and select the schema in the wizard to set it for both Input and Output Schemas in the plug-in wizard.

Workaround: Only select unbound message elements for context properties.

• TIBCO ActiveMatrix Operations Governance Platform Administrator plug-in
• TIBCO ActiveMatrix Administrator Governance Policy Director Admin plug-in

Workaround: This issue does not have a functional impact. Everything works as expected.

Workaround: None

Workaround: None

Workaround: None

Workaround: None

Governance > New > Authentication By OpenID

Workaround: None

PolicyEnforcement Failed to Authenticate the request.

Workaround: Modify the WSDL generated by ActiveMatrix to add the following schema, WSDL message, and WSDL input in binding to successfully invoke an TIBCO® BPM Enterprise service from TIBCO ActiveMatrix BusinessWorks.

Schema

<xsd:schema elementFormDefault="qualified" targetNamespace="http://schemas.xmlsoap.org/ws/2002/07/secext">
<xsd:import namespace="http://schemas.xmlsoap.org/ws/2002/07/utility"/>
<xsd:element name="Security" type="s2:Security"/> <xsd:complexType name="Security">
<xsd:sequence>
<xsd:element minOccurs="0" maxOccurs="1" name="UsernameToken" type="s2:UsernameToken"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="UsernameToken">
<xsd:sequence>
<xsd:element minOccurs="0" maxOccurs="1" name="Username" type="xsd:string"/>
<xsd:element minOccurs="0" maxOccurs="1" name="Password" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

WSDL Message

<wsdl:message name="PUTSecurity">
<wsdl:part name="Security" element="s2:Security"/>
</wsdl:message>

WSDL Input in Binding

<soap:header message="tns1:PUTSecurity" part="Security" use="literal"/>

For example:

<wsdl:binding name="ProcessPackageProcess_EP" type="tns1:ProcessPackageProcess">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="CatchMessageEvent">
<wsdl:documentation/>
<soap:operation style="rpc" soapAction="CatchMessageEvent"/>
<wsdl:input>
<soap:header message="tns1:PUTSecurity" part="Security" use="literal"/>
<soap:body use="literal" parts="in1"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" parts="out1"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<soap:header message="tns1:PUTSecurity" part="Security" use="literal"/>

Workaround: You can either:

• Deploy these references in different nodes
• Configure these references with different HTTP client resource instance configurations

Workaround: None

UsernameTokenAuthentication authenticates using only the username token in the WS-Security header.

WSSProvider authenticates using any available information in the WS-Security header.

Both policies remove the WS-Security header from the message after successful authentication. If both policies are in effect at the same service, when the first one (WSSProvider) succeeds, the second (UsernameTokenAuthentication) must fail, because the WS-Security header is no longer available. This failure causes request messages with proper credentials to fail erroneously.

Workaround: Do not apply the policies WSSProvider and UsernameTokenAuthentication together at the same SOAP service.

Workaround: Redeploy the application after reinstalling one or more resource instances.

Suppose user A is a member of group B, which is a subgroup of group C. If group C has access permission to request an operation, and user A attempts to request that operation, then the request fails. That is, members of group B do not inherit access permission from group C.

Workaround: Configure access permissions directly in each subgroup (in this example, in group B).

Workaround: When configuring an LDAP Authentication resource template, accept the default setting to generate SAML 2.0 tokens.

Workaround: None

Workaround: None

TypeError: Failed to fetch

Workaround: Add the certificate as an exception in the browser.

Workaround: You can manually form the request payload of type Badgerfish ( JSONapplication/bjson) to get a proper response.

Workaround: Manually provide a namespace for such elements.

Erroneous usage: 

{"addRequestOperation": {"Arrays":[{"Key":"key1", "Value": "value1"}]}} 

Workaround: In the RRC file, specify multiple elements in the JSON Array element as follows:

Correct usage:

{"addRequestOperation": {"Arrays":[{"Key":"key1", "Value": "value1"},{"Key":"key2", "Value": "value2"}]}}

With this change, the Array object is treated as a JSON array at runtime and the NullPointerException is not seen.

Workaround: Deploy the project in ActiveMatrix Administrator.

Workaround: None

Workaround: None

Workaround: None

Regenerated context parameter mappings

Workaround: Clean the project.

Workaround: None

Workaround: Click Finish.

1. unsignedByte mapped to short
2. nonpositiveinteger mapped to float
3. nonnegativeinteger mapped to float
4. unsignedshort mapped to int
5. gYear mapped to short
6. negativeinteger mapped to float
7. unsignedlong mapped to float
8. positiveinteger mapped to float
9. boolean mapped to string

Workaround: Perform a clean operation.

Workaround: None

Workaround: None

Workaround: Create an HTTP connector resource instance in the ActiveMatrix Administrator GUI. While configuring the REST binding in TIBCO Business Studio, the name of the resource instance must match the user-specified HTTP connector name.

Workaround: A Null Pointer Exception is raised because this is related to the WSDL created in previous versions of Studio. Rebuild the projects after regenerating the WSDL from the studio.

Workaround: Select update, re-provision and resolve check box if you are upgrading from SDS. Alternatively, undeloy and deploy the application again, it will reflect the updated application version.

Workaround: After adding a new server, click on the Refresh button.

Workaround: None

Workaround: None

Workaround: None

JAR file incompatible with JRE/JDK 1.7 due to containing entries with the empty name.

Workaround:

1. Open the Problems view.
2. Look for instances of the following error message:

   JAR file incompatible with JRE/JDK 1.7 due to containing
   entries with empty name. 

   One such message is generated for each offending JAR file.
3. Right-click all these messages and select a quick fix to apply.

Workaround: None

Launching <projectName><ant.deployment-build.xml' has encountered a problem,  
Launch configuration <projectName><ant.deployment-build.xml references non-existing project <projectName>

This is because of a bug in the Eclipse platform 4.7.1a (https://bugs.eclipse.org/bugs/show_bug.cgi?id=522581).

Workaround: Run the Ant file using the Run in the same JRE as the workspace option in the Create, manage, and run configurations dialog. Alternatively, change the project containing the build.xml to a Java project by adding <nature>org.eclipse.jdt.core.javanature</nature> to the list of <natures> in the .project file and then restart Eclipse.

Unsupported minor version

Workaround: Change the workspace JRE to Java 1.8.

Workaround: To generate the DAA file with Java 8 code, make sure the RequiredExecutionEnvironment field in the Manifest.MF file is empty. This allows you to create the DAA and deploy it at run time.

• For a newly created project, the RequiredExecutionEnvironment field in the Manifest.MF file is empty.
• For an existing project, if Java 8 specific code is added, remove the RequiredExecutionEnvironment entry in the Manifest.MF file.

Summary: For a Custom Mediation task, generation of the DAA fails.

Workaround: While creating the Custom Mediation task, make sure the RequiredExecutionEnvironment field in the Manifest.MF file is empty. This allows you to create the DAA and deploy it at runtime.

Workaround: In the SystemNode.tra file, set the following property:

java.property.com.tibco.amx.admin.application.update.description.contact.during.upgrade=true

Exporting bundles failed

Workaround: To generate the DAA file with Java 8 code, make sure the RequiredExecutionEnvironment field in the Manifest.MF file is empty. This allows you to create the DAA and deploy it at runtime.

Summary: ActiveMatrix projects created in versions prior to 3.2.0 that use Java, Spring, or WebApp components encounter a Null Pointer Exception (NPE) dialog when imported into any ActiveMatrix version running on JRE 1.7 or later. This is caused by the incompatibility of JRE 1.7 with the JAR format of the DataBinding JARs generated by ActiveMatrix versions prior to 3.3.0. This may happen if you have upgraded to JRE 1.7 or installed an ActiveMatrix version that includes JRE 1.7, such as version 3.3.0.

Workaround:

1. Open the Problems view.
2. Look for instances of the following error message:

   JAR file incompatible with JRE/JDK 1.7 due to containing
   entries with empty name.

   One such message is generated for each offending JAR file.
3. Right-click on one of these messages and select a quick fix to apply. There are three quick fixes available (all three back up old JARs):
   • Fix JAR for JRE/JDK 1.7 compatibility-This option fixes only the selected JAR (that is, the JAR you clicked to apply the quick fix).
   • Fix all library JARs in project for JRE/JDK 1.7 compatibility-This option fixes all of the offending JARs in the same project as the selected JAR (that is, the JAR you clicked to apply the quick fix).
   • Fix all library JARs in workspace for JRE/JDK 1.7 compatibility-This option fixes all of the offending JARs in the workspace.
4. After applying a quick fix, some errors related to the component class may still be seen. To clean up these errors, select the project that has the errors and select Project > Clean.

Workaround: Select the Web Application component, right-click, and select Generate Servlet Implementation.

Workaround: Deploy the application from ActiveMatrix Administrator. The application state is in a partially running state instead of running - which is the expected behavior.

Unbanded EventLoop Exception

Workaround: None. Ignore the error.

Workaround: None

Workaround: None

Workaround: Refresh the browser and then check the resource template details.

Summary: After deploying application with OpenID Authentication policy, If OpenID Authentication resource template is updated in between, then accessing OpenID application Redirect URI fails with the following error:

Failed to get connection. Exception: ManagedConnection pool has been destroyed			  

Workaround: Redeploy the application or restart the node.

Summary: After deploying application with SAML SSO Web Profile Authentication Policy, If SAML SSO Web Profile Authentication resource template is updated in between, then accessing application Redirect URI fails with the following error:

Failed to get connection. Exception: ManagedConnection pool has been destroyed

Workaround: Redeploy the application or restart the node.

Workaround: When deploying an application, set the force attribute to false in the deploy-application target of application_build.xml file. Setting the force attribute to false checks for all dependencies required by an application.

Dashboard Bundle not Available. Please reload the browser. TypeError: Cannot read
property 'Container' of undefined

Workaround: None

Workaround: None

Workaround: None

Summary: If you have upgraded to ActiveMatrix 3.4.0, and then created a Host or Node, some default loggers are missing on the newly created Host or Node.

Workaround: Before creating the Host, copy the DefaultLogConfiguration.properties file on every TibcoHost instance on which the ActiveMatrix Administrator server is running.

Copy the file from <TIBCO_HOME>\administrator\3.4\templates\ and paste it into <CONFIG_HOME>\admin\amxadmin\private\<instanceName>\.

Workaround: None

Workaround: None

Couldn't obtain phys addr

Workaround: None

404 page not found

Workaround: Periodically, refresh the ActiveMatrix Administrator web page to determine whether ActiveMatrix Administrator was completely initialized and is ready for service.

Workaround: Start or stop the host by using the tibcohost command.

Workaround: Open http://localhost:8120/amxadministrator/amxmonitor.jsp in a new tab to view the Health Check page.

Workaround: None

Workaround: None

Cause: java.util.concurrent.TimeoutException.

Workaround: None

Workaround: None

Workaround: None

TIBCO-AMX-ADMIN-021085: Failed to update the notification transport!, Caused by:
TIBCO-AMX-ADMIN-021281: The number of hosts in this enterprise is more than 10. 
Please use the Administrator Command Line Interface for updating the Notification Transport. 

Workaround: None

If SystemHost is not updated first, while updating Remote TIBCOHosts, ActiveMatrix Administrator CLI might show the update as having been completed successfully, but the TIBCOHosts might not be updated.

Workaround: Update the Notification Transport for the SystemHost first.

Workaround: None

Workaround: None

In a wildcard behavior, the following behavior is observed:

If the user has two versions for the same featureId in the form of 1.0.0 (Strict version without qualifier) and 1.0.0.001 (Strict version with qualifier), precedence is given to 1.0.0.001 only and 1.0.0 is not uninstalled.

Workaround: To uninstall 1.0.0 explicitly, perform the same action again.

Workaround: None

Workaround: On the Details pane of <Host> -> <ResourceInstance> page and Shared Objects > Resource Templates > Resource Instances tab, navigate to the tree view in the left side pane. This tree view provides the exact node name: <Environment Name>_<node name>.

• The host name of the replicated admin server is changed from the default SystemHostReplica to a custom name.
• Include System Objects option is NOT selected.

Workaround: None

Workaround: Refer to the most recent state displayed in the Action History column instead of the Node State column.

Workaround: None

Workaround: None

Workaround: After the resource template is imported (to Global scope), change its scope as required (to Application scope, for example) in the ActiveMatrix Administrator UI. To do this:

1. Go to Shared Objects > Resource Templates.
2. Select the imported resource template.
3. Click Change Scope, and change the scope to the Application or Environment level as required.

TIBCO-AMX-ADMIN-012430: Provided capability 'com.example.my.subprocess.pe.capability' provided by component 'MySubAppProcessFlow' cannot be removed. It is being used by the following components:Component 'MyMainAppProcessFlow' from application 'com.example.my.mainapp.process

This warning is issued erroneously and can be safely ignored. The subprocess is upgraded successfully and the main processes runs as expected, provided the subprocess maintains the same major version number as before.

Workaround: None

Changing the configuration of the internal HTTP connector (for example, to enable SSL or change the port number) causes the URL configured in the logging configuration (log4j.xml) to become invalid or out of sync. The logging configuration of each affected node, host, or application needs to be updated or it fails to connect to EMS. Currently this is not done automatically.

Workaround: You must manually save and apply the logging configuration for each node, host, or application that uses a JMS appender. To do this:

1. In the ActiveMatrix Administrator UI, go to the logging configuration for the node, host, or application that is in the situation described above.
2. Change a value in the logging configuration that makes the node, host, or application go out of sync. Then, click Save.
3. To push the new logging configuration with a new HTTP URL to the node, host, or application, click Apply.

Workaround: To avoid this issue, go to Node > Configuration > Features and remove the feature with Marked for Install and a blank value for Type.

Could not open Hibernate Session for transaction. 

Workaround: None

Workaround: For HTTP connector port conflicts, use substitution variables to assign different port numbers for each node to avoid port conflicts. Then uninstall the application and redeploy it.

Workaround: Manually restart the stopped application.

Error generating the WSDL for binding SOAPService_Binding1, Caused by: Could not find resource instance with name httpConnector when generating WSDL for binding SOAPService_Binding1 on service NewService

Workaround: Create the HTTP connector before creating the application.

SystemNode 30 Jul 2012 16:42:48,287 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - Unsuccessful: create index AdmnCnfig_sttsNtifictinTrnsprt on "ADMINCONFIG" ("NTFCTNTRNSPRT_STTSNTFCTNTRNS_D")
SystemNode 30 Jul 2012 16:42:48,287 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - ORA-00955: name is already used by an existing object
SystemNode 30 Jul 2012 16:42:48,303 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - Unsuccessful: create index AMXdminsrPrfrncs_prvisnvslctin on "AMXADMINUSERPREFERENCES" ("PRVISNVSLCTIN_PRVISNVSLCTIN_ID")
SystemNode 30 Jul 2012 16:42:48,303 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - ORA-00955: name is already used by an existing object
SystemNode 30 Jul 2012 16:42:48,319 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - Unsuccessful: create index ApplicationFolder_childFolders on "APPLICATIONFOLDER" ("APPLICATIONFOLDER_PARENT_E_ID")
SystemNode 30 Jul 2012 16:42:48,319 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - ORA-01408: such column list already indexed

Workaround: These errors can be safely ignored as the indexes are created.

Also, you can delete any such HTTP Connector even when it has dependent applications.

Workaround: Use property names such as HttpInboundConnectionConfig or httpConnect to refer to HTTP Connectors resource instances. Additionally, when deleting HTTP Connector resource instances, manually check whether other applications are dependent on it.

Also, even if the generated scripts are not used, error messages are seen in the SystemNode log file logged in SystemNode.log regarding failure to create foreign key constraints.

Workaround: None. These errors can be ignored as a failure to create foreign key constraints that do not impact product functionality.

Workaround: Ensure that, TibcoHost instances, and nodes are all using JREs provided by the same vendor.

[ERROR] com.tibco.amf.admin.server.axis2.RPCMessageReceiver -
Error occurred in Administrator... about to throw AxisFault for this exception 

Workaround: Refresh the browser. This error message can be safely ignored.

Workaround: Permissions to view the node have to be explicitly granted by a superuser.

Workaround: Click OK to proceed using the Dashboard. This error message can be safely ignored.

Workaround: Refresh the browser.

Workaround: Undeploy and deploy the application.

Workaround: Reenter the text filter.

Workaround: In the Application Screen, check the properties of the reference or service bindings.

Workaround: None

Workaround: None

For example, if the body of the SOAP response is configured with Message="GetSOAPResponse"/Part = "param1" in the WSDL and the context parameter of Type "Message" is defined with the same Message/Part Definition "GetSOAPResponse/param1", the generated SOAP response message might contain an empty <Header> or <Body> element.

Workaround: None. However, if distinct "Message/Part" pairs are used for SOAP header and body, this issue does not occur. For example, if the body of the SOAP response is configured with Message="GetSOAPResponse"/Part = "param1" in the WSDL and the context parameter of Type "Message" is defined with Message/Part Definition "GetSOAPHeader/headerparam1", the generated SOAP response message contains both <Header> and <Body> elements.

Workaround: At present, this field is not disabled for SOAP bindings containing all in-only operations and, if selected, does not have any effect.

• Enable Request Message Validation
• Enable Response Message Validation
• Sender Identified Expression

On the Reference side, Substitution Variables are supported for the following fields:

• Enable Request Message Validation
• Enable Response Message Validation
• Filespec of Endpoint URL

Workaround: None

Workaround: Edit policy sets and properties in TIBCO Business Studio.

• The DAA or application was created in TIBCO Business Studio prior to version 3.6.0.
• The DAA or application contains a Web Service invocation (that is, the application is a consumer).
• The application has a User nameToken policy type in its security.

Workaround: Open the project in TIBCO Business Studio 3.6.0, build the DAA, and upgrade the existing application.