Closed Issues
The following issues have been closed since the last major release of TIBCO ActiveMatrix® Service Grid 3.4.2.
Key | Summary |
---|---|
AMRP-5788 |
Previously, the user could not append (merge) new JVM arguments to the existing JVM arguments for a Node using the command line. With this fix, the user can append (merge) new JVM arguments to the existing JVM arguments for a Node using the 'update' build target of node_build.xml with a task attribute 'options="mergeJvmArgs". |
AMRP-5804 |
Previously, in the AMX Admin GUI, there was no field to specify "max pool size" for the Kerberos Authentication Resource Template. Along with that, in the command-line scripts (AMX XML schemas for build data file 'resourcetemplate_data.xml') there was no 'max pool size' for Kerberos Authentication. With this fix, users can specify "max pool size" for the Kerberos Authentication Resource Template in the Admin GUI and command-line scripts. If not provided, the default value is "20". Below is the command-line script sample: <ResourceTemplate xsi:type="amxdata:KerberosAspResourceTemplate" name="kerberosAspRT"> |
AMRP-5790 |
When the 'Timeout' property of an SMTP shared resource has been configured, but the target email server does not respond with code 220 ("SMTP Service Ready"). This causes the thread calling the SMTP shared resource to wait forever. With this fix, the timeout value for the SMTP shared resources work as expected. |
AMRP-5791, AMRP-5765 |
Stopping one WebApp component stops the Node JVM property "allowed.referers" for other WebApp components that run on the same node. With this fix, this does not happen. |
AMRP-5792 |
To specify the "Pool Idle Timeout" attribute for LDAP Authentication shared resources on a particular Node, add the following JVM property to the Node tra file, and restart the Node. java.property.com.sun.jndi.ldap.connect.pool.timeout=<value> (timeout is in milliseconds) For example, java.property.com.sun.jndi.ldap.connect.pool.timeout=180000 A pooled LDAP Authentication connection is recycled after it has been idle for the above specified timeout period. |
AMRP-5787,TAP-16588,TAP-16586,TAP-16579 |
Previously in the ActiveMatrix Admin GUI, there is no field to specify 'max pool size' for the Kerberos Authentication Resource Template. Also in command-line scripts (AMX XML schemas for building data file 'resourcetemplate_data.xml') there is no 'max pool size' for Kerberos Authentication. With this fix, users can specify 'max pool size' for the Kerberos Authentication Resource Template in the Admin GUI and also in command-line scripts (AMX XML schemas for build data file 'resourcetemplate_data.xml'). If not provided, the default value is "20". Below is the command-line script sample: <ResourceTemplate xsi:type="amxdata:KerberosAspResourceTemplate" name="kerberosAspRT"> <GeneralConfiguration xsi:type="amxdata:Kerberos_ResourceTemplate_General" Description="This is kerberosAsp RT generalConfiguration" maxPoolSize="20" KerberosRealm="KerberosRealm" KeyDistributionCenter="KeyDistributionCenter"/> ... </ResourceTemplate> |
AMRP-5760 |
To specify the "Pool Idle Timeout" attribute for LDAP Authentication shared resources on a particular Node, add the following JVM property to the Node tra file, and restart the Node. java.property.com.sun.jndi.ldap.connect.pool.timeout=<value> (timeout is in milliseconds) For example, java.property.com.sun.jndi.ldap.connect.pool.timeout=180000 A pooled LDAP Authentication connection is recycled after it has been idle for the above specified timeout period. |
AMRP-5764 |
Previously, the user was not able to append (merge) new JVM arguments to the existing JVM arguments for a Node using the command line. With this fix, the user is able to append (merge) new JVM arguments to the existing JVM arguments for a Node using the 'update' build target of node_build.xml with a task attribute 'options="mergeJvmArgs"'. |
AMRP-5766/AMRP-5786 |
The target email server does not respond with code 220 ("SMTP Service Ready"), even if the 'Timeout' property of an SMTP shared resource has been configured, the timeout does not happen, and consequently the thread calling this SMTP shared resource waits forever. With this fix, the timeout value for the SMTP shared resources work as expected. |
AMX-18722 |
Previously in AMX 3.4.1, the TCS Server used TLS v1 as the default security protocol. When lower TLS versions (1.0, 1.1) were disabled by users, SSL handshakes with the TCS Server would fail as the protocols do not match. With this fix, the TCS Server uses the higher version TLS as default for secure connections, and it supports the lower TLS versions as well. Even if lower versions of TLS (1.0, 1.1) are disabled by the user, there is no handshake errors with the TCS server. |
AMX-18771 |
Previously, if the name of an application bundle archive under the Node work cf folder is not of the default or original form "bundle", then the AMX 3.4.1 Platform upgrade may fail. With this fix, even if an application bundle archive has a non-default name such as "bundle2", "bundle3", etc., the AMX 3.4.1 Platform upgrade does not fail. |
AMX-18723 |
Previously When accessing the SOAP/JMS operation from BW, the UserName Authentication was failing after the SSO login. With this fix, users are able to enable dual Authentication mode for UserName Token and SAML WebProfile SSO Authentication. When accessing the SOAP/JMS operation from BW, the UserName Authentication with SSO login works fine as expected. |
AMX-18772 |
Assume that in a BPM environment (version 4.3.1 or previous) there is a ProcessFlow application that has a dependency on a BDS application v1. When the BDS application is upgraded from v1 to v2, the v1 changes to PFU, and v2 is in running state, and by our BPM product design, the ProcessFlow application still has its dependency on v1 of the BDS application. After upgrading the AMX platform to 3.4.1, the amx.bpm.app should be stopped by our upgrade scripts - but for some reason this does not happen. So amx.bpm.app is in a partially running state. Under this circumstance, it makes the wrong decision that the v1 version of the BDS application should be removed. Consequently v1 is removed in BPM 4.3.2 upgrade, which leads to the child ProcessFlow app bundle 'does not resolve' and thus the app 'START_FAILED'. With this fix, the amx.bpm.app is in the expected "Stopped" rather than the "Partially Running" state before the AMX platform upgrade happens. This prevents previous version BDS applications from being removed incorrectly. |
AMX-18948 | Previously, when trying to provision an IBM MQ 7.x driver on AMX 3.4.1 Nodes, it fails with an error of Import-Package: javax.jms. With this fix, the IBM MQ 7.x driver can be successfully provisioned on AMX 3.4.1 Nodes. |
AMX-18859 |
Previously, the HTTP Client would not close the TCP connection and the pool 'Idle Timeout' setting does not work as expected when connection pooling is enabled. Added support for the 'Idle timeout' field on the Advanced configuration tab of HTTP Client RT. HTTP Client closes the TCP connection when connection pooling is enabled based on the Idle Timeout value. The Idle Timeout is specified in the xxx time unit. The default value is "-1" which means 'Never timeout'. Previously in the admin GUI, there is an 'Idle timeout' field that comes under the General configuration tab that is now renamed to 'Linger Timeout'. Below is the command-line script sample: <ResourceTemplate xsi:type="amxdata:HttpClientResourceTemplate" name="HttpclientRT" isAcceptRedirect="true" connectionTimeout="8888" host="test-host" port="80" description="This is HttpClient RT" sslJNDIName="JdbcNonXaTx_Identity" idleTimeout="-1"> <AdvancedConfiguration xsi:type="amxdata:HttpClientResourceTemplate_Advanced" localSocketAddress="localhost"> <EnableConnectionPooling xsi:type="amxdata:EnableConnectionPooling" maximumTotalConnections="5" maximumTotalConnectionsPerHost="10"/> </AdvancedConfiguration> </ResourceTemplate>
|
AMX-18281 |
Previously, when accessing the SOAP/JMS operation from BW, the UserName Authentication was failing after the SSO login. With this fix, the users are able to enable dual Authentication mode for UserName Token and SAML WebProfile SSO Authentication. When accessing the SOAP/JMS operation from BW, the UserName Authentication with SSO login works fine as expected. |
AMX-18322 |
Previously in AMX 3.4.0, the TCS Server used TLS v1 as the default security protocol. When lower TLS versions (1.0, 1.1) were disabled by users, SSL handshakes with the TCS Server would fail as the protocols do not match. With this fix, the TCS Server uses the higher version TLS as default for secure connections, and it supports the lower TLS versions as well. Even if lower versions TLS (1.0, 1.1) is disabled by the user, there is handshake errors with the TCS server. |
AMX-17860 |
Previously, the user was not able to perform JDBC Test Connection for JDBC XA RT type. With this fix, the user can perform JDBC Test Connection for JDBC XA RT type. Note: If the CLI attribute "disableValidateConnectionOnInit" is "true" in the JDBC Resource Template build data file, or the SystemNode TRA property "java.property.com.tibco.admin.jdbc.disable.validate.connection.oninit" is "true" while creating JDBC RT then JDBC Test Connection is not called and RI installation is successful. |
AMX-18629 |
Previously, when running Enterprise Deployment Health Check it fails with errors like below: "Failed to parse machineUsedPhysicalMemorySize: 8,1 GB" With this fix, now ","(comma) is also a supported decimal separator and we are not seeing this error now. Note: Decimal separators (symbols) have region (country)-specific formats, and can be configured at OS level Regional Settings. |
AMX-18661 |
The HTTP Client does not close TCP connection and the 'Pool Idle Timeout' setting does not work as expected when connection pooling is enabled. Added support for the 'Idle timeout' field on the Advanced configuration tab of HTTP Client RT. HTTP Client closes TCP connection when connection pooling is enabled based on the Idle Timeout value. The Idle Timeout is specified in xxx time unit. The default value is "-1" which means 'Never timeout'. Note: Previously, in the admin GUI there is an 'Idle timeout' field that comes under the General configuration tab that is now renamed to 'Linger Timeout'.
Below is the command line script sample: <ResourceTemplate xsi:type="amxdata:HttpClientResourceTemplate" name="HttpclientRT" isAcceptRedirect="true" connectionTimeout="8888" host="test-host" port="80" description="This is HttpClient RT" sslJNDIName="JdbcNonXaTx_Identity" idleTimeout="-1"> <AdvancedConfiguration xsi:type="amxdata:HttpClientResourceTemplate_Advanced" localSocketAddress="localhost"> <EnableConnectionPooling xsi:type="amxdata:EnableConnectionPooling" maximumTotalConnections="5" maximumTotalConnectionsPerHost="10"/> </AdvancedConfiguration> </ResourceTemplate> |
AMX-17498 |
In an ActiveMatrix setup when secure SystemHost and RemoteHosts (host for which the JMX port is secured) were successfully upgraded to ActiveMatrix Service Grid 3.4.0, the Administrator UI did not show the updated Hosts' versions correctly. This is because when the hosts are secured, SystemNode is configured with TLSv1, which is the supported TLS in versions of ActiveMatrix prior to 3.4.0. Starting TIBCO ActiveMatrix 3.4.0 TLSv1.2 is supported, and all the Hosts are updated to automatically use TLSv1.2 when upgraded to 3.4.0, except the Administrator (SystemNode). When you encounter this issue, please run the following command after applying TIBCO ActiveMatrix 3.4.0 Hotfix 001, or upgrading directly to TIBCO ActiveMatrix 3.4.0 Hotfix 001, to update the Administrator (SystemNode) to support TLSv1.2. Go to <TIBCO_HOME>/amx/3.4/bin folder and run the following command: tibamx_hostmanager updateAdminToTLSv12 -configHomeLocation <TIBCO_CONFIG_HOME> NOTE: Hosts and nodes must be stopped before running the above command. After running the command, restart the Administrator (SystemNode). The above command must be run only on the machine where SystemNode is running. |
SDS-7796 |
When an application with a SSL-enabled HTTP connector tries to connect to a deployment server, the connection fails. Now for the SSL enabled HTTP connector, a connection gets established. |
TAP-16601 | Previously, setting the node JVM property with a value containing the special character '(' (left parenthesis) causes the node to be "Out of Sync" and stuck in an "Install failed" state. With this enhancement, the special character "(" (left parenthesis) is supported in Node tra. |
TAP-16602 | Previously, the special character % (percent symbol) was not supported to be part of a
JVM property value in the Node tra file.
With this enhancement, the special character "%" (percent symbol) is supported in the Node
tra file.
|
TAP-16619 |
When trying to create/update a substitution variable from the Admin UI with a value containing a special character "'" (single quote), and when saving the changes, the Admin UI generates the following error:
With this fix, users are able to add/update SVar that has special characters "'" (single quotes) via the admin UI. |
TAP-16620 |
Previously, the ActiveMatrix Administrator was not able to handle special characters in the TaskResult table, and consequently did not display the application's State and Synchronization correctly, and components status were partially missing for some nodes. In the Node log there were errors like below: java.lang.NumberFormatException: For input string: " " With this fix, the special characters are filtered out when storing data in the TaskResult table, the Administrator can display the state of an application and its components properly. |
TAP-16406 |
When trying to create/update a substitution variable from the Admin UI with a value containing a special character "'" (single quote), and when saving the changes, the Admin UI generates the following error: "There are one or more errors in Substitution Variables" "User Input for Local Value is invalid!. It contains an invalid character: '''." With this fix, users are able to add/update SVar that has special characters "'" (single quotes) via the admin UI. |
TAP-16621 |
Previously, the 'updateJDBCDriver' AMX Administrator CLI action was used to update JDBC drivers of all nodes under the enterprise in a single AMX Administrator backend action. Due to this, DB concurrency issue was seen most of the time. With the fix, the action 'updateJDBCDriver' AMX Administrator CLI action is done for 5 nodes at a time under a given entity (Host/Environment/Enterprise). |
TAP-16622 |
When a user tries to run the 'updateJDBCDriver' CLI target to upgrade the JDBC driver for all nodes of a very large AMX setup, the command-line script failed with an error like below: ERROR - SQL State[42000], Error code[1,795], Message[ORA-01795: maximum number of expressions in a list is 1000 With this fix, the above SQL error is no longer seen and the updateJDBCDriver command-line script runs successfully. |
TAP-16623 |
Previously, before each build target within a CLI command was actually run, the AMX Admin Server and Enterprise state would be checked and the summaries were generated. For a large AMX 3.4 setup (for example, hundreds or even thousands of nodes), fetching such information would take a long time. With this fix, a cache mechanism is introduced, which significantly reduces the unnecessary Admin Server and Enterprise queries, and thus improves user experience. |
TAP-16662 |
Previously, it was possible to set 'max pool size' for SiteMinder shared resource using a CLI approach, there was no GUI approach to do the same (in the AMX Admin GUI there was no field 'max pool size' for SiteMinder Resource Template). Having a CLI but no GUI approach causes some troubles such as being not easy/straightforward to inspect or view the currently specified max pool size for a particular SiteMinder shared resource, and special attention/care needs to be taken to avoid incorrectly overwriting any existing configurations each time you try to update some configuration(s) of a SiteMinder shared resource. With this fix, users can specify and view 'max pool size' for the SiteMinder Resource Template connection pool from the Admin GUI. Also the SiteMinder Resource Template configurations can be updated without worrying about existing configurations being overwritten incorrectly. If not specified, it is set to the default value "20" in both GUI or CLI. |
TAP-16665 |
Previously, when the node on the 'Node Health' column had an 'In progress' state, sometimes hovering the mouse over the 'In progress' column did not show the user the reason why it was in_progress. With this fix, now if the nodes on the "Node Health" column has 'In progress' state, then hovering the mouse over the 'In progress' column shows the exact reason why the 'Node Health' column keeps on 'In progress' state. |
TAP-16676 |
The user was unable to create a substitution variable from the AMX Admin UI, whose value contains special characters <(less than), >(greater than), "(Double quotes), '(single quotes). With this fix, users can create a substitution variable from AMX UI or CLI, whose value contains special characters <(less than), >(greater than), "(Double quotes), '(single quotes). NOTE: There is one limitation - if a user wants to create a substitution variable whose value contains the special character '<(less than)' through the command line, then use '<' instead of '<' in the command line build data file. Below is the command-line script sample <SVar xsi:type="amxdata_base:SubstitutionVariable" name="enterprise-svar1" type="String" value='<' description="less than symbol"/> |
TAP-16381 | Previously, during accessing Internal HTTP Connector in RT via Administrator GUI getting exception as 'Mapping name not fond for the package: org.hibernate.exception'. With this fix, during accessing the Internal HTTP Connector in RT via the Administrator GUI, no exceptions are seen. |
TAP-16573 |
When the node on the 'Node Health' column had an 'In progress' state, sometimes hovering the mouse over the 'In progress' column did not show the reason why it was in progress. With this fix, if the nodes on the 'Node Health' column keep an 'In progress' state, then hovering the mouse over the 'In progress' column shows the exact reason. |
TAP-16581 |
Previously, when a user deletes application level loggers of an application from the Admin UI, the reference binding log4j.xml was not deleted and consequently the corresponding log entries still get printed. With this fix, application level logging is removed completely after application level loggers are deleted from an application. |
TAP-15963 |
Previously, before each build target within a CLI command was actually run, the AMX Admin Server and Enterprise state would be checked and the summaries were generated. For a large AMX 3.4 setup (for example, hundreds or even thousands of nodes), fetching such information would take a long time. With this fix, a cache mechanism is introduced, which significantly reduces the unnecessary Admin Server and Enterprise queries, and thus improves user experience. |
TAP-16109 |
When a user tries to run the "updateJDBCDriver" CLI target to upgrade the JDBC driver for all nodes of a very large AMX setup, the command-line script failed with an error like below: ERROR - SQL State[42000], Error code[1,795], Message[ORA-01795: maximum number of expressions in a list is 1000 With this fix, the above SQL error is no longer seen and the updateJDBCDriver command-line script runs successfully. |
TAP-16370 | Previously, the special character % (percent symbol) was not supported to be part of a JVM property value in the Node tra file. With this enhancement, the special character "%" (percent symbol) is supported in the Node tra file. |
TAP-16377 |
Previously, the 'updateJDBCDriver' AMX Administrator CLI action was used to update JDBC drivers of all nodes under the enterprise in a single AMX Administrator backend action. Due to this DB concurrency issue was seen most of the time. With the fix, the action 'updateJDBCDriver' AMX Administrator CLI action is done for 5 nodes at a time under a given entity (Host/Environment/Enterprise). |
TAP-16393 |
Previously, setting a node JVM property with a value containing the special character '(' (left parenthesis) caused the node to be "Out of Sync" and stuck in an "Install failed" state. With this enhancement, the special character "(" (left parenthesis) is supported in Node tra. |
TAP-16402 |
Previously, the ActiveMatrix Administrator was not able to handle special characters in the TaskResult table and consequently did not display the application's State and Synchronization correctly, and components status were partially missing for some nodes. In the Node log there were errors as shown below: java.lang.NumberFormatException: For input string: " " With this fix, the special characters are filtered out when storing data in the TaskResult table, the administrator can display the state of an application and its components properly. |