Product Name    : TIBCO ActiveMatrix(R) Platform 
Release Version : 3.3.0_hotfix024 
Release Date    : June 2019
 

================================================================================
Hotfixes are cumulative. This hotfix includes all previous generally
available hotfixes for TIBCO ActiveMatrix(R) Platform 3.3.0.
================================================================================

This hotfix applies to the following products and versions:

   - TIBCO ActiveMatrix Service Bus 3.3.0 
   - TIBCO ActiveMatrix Service Grid 3.3.0 
   - TIBCO ActiveMatrix BPM 2.2.0, 3.0.0, 3.1.0, 4.0.0, 4.1.0, 4.2.0 
   - TIBCO Business Studio BPM Edition 3.6.0, 3.7.0, 3.8.0, 3.9.0, 4.0.0, 4.1.0
     4.2.0    
   - TIBCO ActiveMatrix BusinessWorks Service Engine 5.11.0 + Hotfix 005 (or
     higher).
   - TIBCO ActiveMatrix Policy Director 1.0.1 + Hotfix 001, 1.1.0
   - TIBCO Hawk ActiveMatrix(R) Plug-in for TIBCO Hawk(R) 5.2.0 with 
     TIBCO ActiveMatrix 3.3.0 Hotfix 018 and above. Platforms supported 
     are Microsoft Windows, Linux, and Solaris. For AIX support, refer to the
     "Known Issues" section of the TIBCO ActiveMatrix Readme Addendum.

NOTE: 
- With TIBCO ActiveMatrix 3.3.0 Hotfix 013 and above as the platform, 
  TIBCO ActiveMatrix BusinessWorks Service Engine 5.11.0 + Hotfix 006 (or higher) 
  can now use TIBCO Enterprise Message Service(TM) 8.2.2 for TLS 1.2 Support.
- TIBCO Service Performance Manager (SPM) Dashboard, that was originally
  part of TIBCO SPM Server is moved to TIBCO ActiveMatrix Platform, and 
  can now be installed using the TIBCO ActiveMatrix 3.3.0 Hotfix 010 or higher.
- TIBCO Service Performance Manager (SPM) Dashboard supports TIBCO Service
  Performance Manager versions 2.2.1 and 2.3.0.
- Existing TIBCO Service Performance Manager (SPM) Dashboard installations 
  can be upgraded using TIBCO ActiveMatrix 3.3.0 Hotfix 012 or higher. While
  upgrading, the existing Dashboard configuration is used, eliminating 
  the need for reconfiguring the Dashboard. To upgrade, install TIBCO 
  ActiveMatrix 3.3.0 Hotfix 012 or higher on the same <TIBCO_HOME> where the
  Dashboard has been installed. For more information, refer to the "Upgrading 
  TIBCO ActiveMatrix SPM Dashboard" section in the "TIBCO ActiveMatrix SPM 
  Dashboard" chapter in the TIBCO ActiveMatrix Administration Addendum.
- Existing TIBCO ActiveMatrix 3.3.0 customers who have been using
  TIBCO ActiveMatrix with TIBCO Service Performance Manager 2.1.0 are
  affected by Hotfix 010 or higher. After Hotfix 010 or higher is applied to the 
  TIBCO ActiveMatrix 3.3.0 installation, it is required that you use TIBCO
  Service Performance Manager 2.2.1.
- For TIBCO ActiveMatrix BusinessWorks Service Engine 5.11.0, HF005
  or above must be installed. TIBCO ActiveMatrix BusinessWorks 
  Service Engine 5.11.0 HF005 fixed issue BWSE-3886 (BWSE application went in a 
  'Start failed' state after applying 3.3.0 Hotfix-008).
- The Administrator and Runtime for TIBCO ActiveMatrix 3.3.0 Hotfix 023
  and higher support JRE 1.8 (certified with updates 172, 181, and 192). 
  Refer to AMX-16650 for additional steps. Refer to the TIBCO ActiveMatrix 
  Updater Tool for Java Runtime Environment (JRE) Documentation to update 
  the JRE version to JRE 1.8.
- The Administrator and Runtime for TIBCO ActiveMatrix 3.3.0 Hotfix 024
  and higher support JRE 1.8 (certified with update 212). Refer to the 
  TIBCO ActiveMatrix Updater Tool for Java Runtime Environment (JRE) 
  Documentation to update the JRE version to JRE 1.8.
- TIBCO ActiveMatrix 3.3.0 Hotfix 024 and higher requires TIBCO Universal 
  Installer 3.6.6 for installation. Refer to the Installation section below 
  for more information.


=====================================================================================
Closed Issues in 3.3.0_hotfix024 (This release)

AMRP-5645    
In TIBCO ActiveMatrix BPM setup involving ActiveMatrix BPM 4.2.0, a 
NullPointerException was intermittently seen when the user's Oracle 12.1.0.2 
database was in a particular state with in-progress database transactions. This 
was a result of erroneous creation of a global transaction with a "null" GLOBALID 
in the DBA_PENDING_TRANSACTIONS table by one of the database users, which caused 
failures, and the subsequent retries every 5 minutes eventually resulted in 
connection pool exhaustion, as seen in the BPM logs. 

With this fix, the retry is skipped for transactions with a "null" GLOBALID and 
the NullPointerException is no longer seen. As a result the connection pool is no 
longer exhausted.

AMRP-5666    
Previously in a TIBCO ActiveMatrix BPM setup (with TIBCO ActiveMatrix 3.3.0 
Hotfix 018 or higher), when the Java property 
"com.tibco.amx.cf.enable.virtualizationAddress.versioning" was set to "true" for 
the BPMNode, a NullPointerException was seen in the BPM Node logs when a business 
operation was invoked immediately following the undeployment and deployment of the 
user's BPM Application, or following a BPMNode restart. 

With this fix, the issue is no longer seen and the operation invocation proceeds 
without errors.

AMRP-5677, AMX-15962    
TIBCO ActiveMatrix now provides the capability to customize the request log files 
for the incoming requests processed by the HTTP Connector Resources via the 
underlying Jetty layer. 

This capability can be enabled by setting the 
"com.tibco.amf.hpa.tibcohost.jetty.enableJettyLoggingProperties" Java property for 
the ActiveMatrix Runtime Node's TRA file to a comma-separated combination of values 
namely "logCookies" (logging request cookies), "logServer" (logging request host 
name), "preferProxiedForAddress" (controls whether to log actual IP address of the 
connection, or from the X-Forwarded-For header) and "logLatency" (logging request 
processing time). "extended" is not provided as one of the value options as it is 
enabled by default in Jetty.

The Java property can be set as follows:
java.property.com.tibco.amf.hpa.tibcohost.jetty.enableJettyLoggingProperties=
logCookies,logServer,preferProxiedForAddress,logLatency

The property can also be set for the Runtime Node using the Administrator UI via 
Infrastructure > Nodes > Select Node > Configuration > JVM Configuration
property: com.tibco.amf.hpa.tibcohost.jetty.enableJettyLoggingProperties
value: logCookies,logServer,preferProxiedForAddress,logLatency

NOTE: The logger "org.mortbay.jetty.Request" must be set to DEBUG level for the 
Runtime Node in order to view the log entries. This can be set using the 
Administrator UI via Infrastructure > Nodes > Select Node > Configuration > Logging 
screen. Once configured correctly, the log entries can be viewed in 
<TIBCO_CONFIG_HOME>/tibcohost/<TH_INSTANCE_FOLDER>/data_3.2.x/nodes/
<RUNTIME_NODE_NAME>/logs/jetty.<DATE>.request.log.

Sample log entry:
Server Name: 0.0.0.0 Remote Address: 127.0.0.1 - - [ <DATE>:<TIME> -0700] 
"POST /helloWorldPT/ HTTP/1.1" 200 205 "-" "Apache-HttpClient/4.1.1 (java 1.5)" 
- 230265ms
    
AMX-17164    
Previously, TIBCO Administrator server did not support SSL-enabled TIBCO Enterprise 
Messaging Server (EMS) fault-tolerant (FT) servers using JSON configuration, and 
failed with the error "com.tibco.tibjms.admin.TibjmsAdminSecurityException: 
Command unavailable on a server not in active state and using a JSON configuration 
file" during EMS failover, as seen in the SystemNode logs. 

With this fix, the failure is no longer seen, and SSL-enabled EMS FT servers 
configured with JSON is supported for failover in a fault tolerant manner.

AMX-17192
This issue was observed when failover happens in a TIBCO ActiveMatrix setup with 
Administrator configured with TIBCO Enterprise Messaging Server (EMS) 
fault-tolerant (FT) servers, Runtime Nodes configured with the 
"tibco.tibjms.connect.attempts" Java property, and the EMS server specified 
first in the FT URL is not running. The user actions of starting or stopping 
the SystemNode and Runtime Nodes took a long time, due to the fact that when 
starting or stopping System Node or Runtime Nodes with EMS FT configured, the 
Nodes kept trying to connect to the inactive primary EMS server, instead of 
connecting to the active, secondary EMS server. 

With this fix, the issue is no longer seen and the Nodes will now connect to the 
active EMS server while starting or stopping without any delay.

AMX-17221
This issue was observed when failover happens in a large scale TIBCO ActiveMatrix 
setup with Administrator configured with TIBCO Enterprise Messaging Server (EMS) 
fault-tolerant (FT) servers, Runtime Nodes configured with the 
"tibco.tibjms.connect.attempts" Java property, and the EMS server specified 
first in the FT URL is not running. The user Applications on the Runtime Nodes 
cannot be stopped or started, due to the fact that after the failover, the 
Runtime Nodes were unable to send their status after successfully reconnecting 
to the EMS Server. This was evidenced by the following error message in the 
Runtime Node logs: 
"com.tibco.amx.hpa.notification.NotificationGroup - TIBCO-AMX-HPA-000308: cannot 
send status update message, notification service is unavailable and sending is 
suspended until notification service is restored". 

As a result, ActiveMatrix Administrator marked these Runtime Nodes as "Offline" 
and was unable to deploy any application on these Nodes. 

With this fix, the Runtime Nodes are able to successfully transmit their status 
upon connecting to the EMS server, and Administrator is able to mark the Nodes 
as "Online" as a result, consequently allowing successful Application 
deployment. 

AMX-17283, AMX-17284
This issue was observed when failover happens in a TIBCO ActiveMatrix setup 
with Administrator configured with TIBCO Enterprise Messaging Server (EMS) 
fault-tolerant (FT) servers, Runtime Nodes configured with the 
"tibco.tibjms.connect.attempts" Java property, and the EMS server specified 
first in the FT URL is not running. The Runtime Nodes were unable to send 
their status after successfully reconnecting to the EMS Server. This is because 
the notifications in the runtime Nodes were not processed in the correct 
order and as a result, the Notification Group was suspended and Nodes could not 
send any status notifications as evidenced by the following Runtime Node logs:
"com.tibco.amx.hpa.notification.NotificationGroup - TIBCO-AMX-HPA-000308: 
cannot send status update message, notification service is unavailable and 
sending is suspended until notification service is restored".

With this fix, Runtime nodes will be able to send status notifications after 
successfully reconnecting to EMS server following the failover.

PD-4422
This issue was observed when failover happens in a TIBCO ActiveMatrix setup 
with Policy Director (PD), with Administrator configured with TIBCO 
Enterprise Messaging Server (EMS) fault-tolerant (FT) servers, Runtime Nodes 
configured with the "tibco.tibjms.connect.attempts" Java property (with value 
set to 600,500), and the EMS server specified first in the FT URL is not 
running. The Governance Control (GC) deployment was failing after EMS failover 
and went into "DeployError" state. This is because after the failover, the 
Runtime Nodes kept trying to connect to the stopped EMS server until all the 
attempts were exhausted. 

As a result, Nodes were unable to send the deployment notification to 
Administrator, which in turn marked their status as "DeployError".

This issue is now fixed and the runtime Nodes now connect to the active EMS 
server immediately following the failover. Deployment of Governance Control 
is also completed successfully after the failover.

PER-2182    
Previously in TIBCO ActiveMatrix BPM setup when a Load Balancer was in place, 
the "X-Forwarded-For" header was not being logged for successful as well as 
failed authentication login attempts. With this fix, the "X-Forwarded-For" 
header will be logged for all authentication attempts so as to identify the 
originating client's IP address when attempting to connecting to the server 
via HTTP proxy or a load balancer.

NOTE: The loggers "com.tibco.amx.login.success" and 
"com.tibco.amx.login.failure" must be set to "INFO" level for the BPMNode 
in order to view the log entries. This can be set using the Administrator UI 
via Infrastructure > Nodes > Select Node > Configuration > Logging screen. 
Once configured correctly, the log entries can be viewed in 
<TIBCO_CONFIG_HOME>/tibcohost/<TH_INSTANCE_FOLDER>/data_3.2.x/nodes/
<BPM_NODE_NAME>/logs/BPM.log.

Sample log entries for successful and failed login attempts:
[INFO ] com.tibco.amx.login.success - TIBCO-OGS_PA-901431: Request is 
successfully authenticated. Properties - [ Principal=system administrator, 
ForwardedFor=<IPAddress>, RemoteHost=0:0:0:0:0:0:0:1, 
RemoteAddr=0:0:0:0:0:0:0:1, RequestURI=/helloWorldPT/AuthenticationService ]

[ERROR] com.tibco.amx.login.failure - TIBCO-OGS_PA-901402: Authentication 
failed. Properties - [ ForwardedFor=<IPAddress>, RemoteHost=<IPAddress>, 
RemoteAddr=<IPAddress>, RequestURI=/helloWorldPT/AuthenticationService ]

TAP-13518    
Previously in TIBCO ActiveMatrix, if a Runtime Node's installation fails for 
any reason, then any subsequent attempt to install the Node again would also 
fail as the Platform Application already exists in the Node, and as a 
result the following error was seen: "Error invoking bulk action install on 
Node: TIBCO-AMX -ADMIN-012368: The application key already exists!". 

With the fix, the Node installation retry attempt first removes the existing 
Platform Application, due to which the Node's installation completes 
successfully.

TAP-15649
Previously in TIBCO ActiveMatrix SOA setup (not involving TIBCO ActiveMatrix 
BPM) when upgrading an SOA Application, Administrator was using the 
"Prepare For Undeploy (PFU)" mode to remove the old components, which is 
not needed for SOA Application components. As a result, Administrator was 
failing to remove the old component, which was in START_FAILED state, from 
runtime. 

With this fix, the PFU mode is no longer used to remove the old component, 
which even in START_FAILED state, can be removed successfully from both 
Administrator and runtime.

TAP-15771
In TIBCO ActiveMatrix BPM setup when upgrading a BPM Application, Administrator 
sets the "Prepare For Undeploy (PFU)" flag to "true" for the components' old 
versions. Previously, Administrator set the PFU flag back to "false" if 
"UNCONFIGURE" task failed during upgrade, thus blocking further upgrade. With 
this fix, Administrator doesn't set the PFU flag back to "false" even if 
"UNCONFIGURE" task fails, thus allowing further Application upgrade to proceed 
successfully.

TAP-15897    
In TIBCO ActiveMatrix SOAP/JMS Binding Type (BT) or JMS Binding Type (BT), the 
underlying JMS Connection Factory Resource Instance (RI) intermittently failed 
to start upon Runtime Node or TIBCO Host restart, when Authentication was 
enabled on the JMS Connection Factory Resource Template (RT), and the JNDI 
Connection Configuration RT name was a substring of the JMS Connection Factory 
RT name. 

This issue has now been fixed and there will be no start failure for newly 
created JNDI Connection Configuration and JMS Connection Factory Resource 
Instances.

NOTE: For the fix to take effect, all affected Resource Templates and their 
respective Resource Instances must be removed, recreated and reinstalled. 

TAP-15934
With this fix, the ability to upload DAA to TIBCO Administrator is governed by 
the extent of the user's authorization level.

================================================================================

See attached Readme document (TIB_amx_3.3.0-HF-024_readme.txt) for installation instructions
and issues resolved in previous hotfix releases.

Hotfix TIB_amx_3.3.0_hotfix024 is available for TIBCO ActiveMatrix BusinessWorks Service Engine 5.11

All Supported Operating Systems

The TIB_amx_3.3.0_hotfix024, can be downloaded from the SFDC Customer Portal Web User Interface
using your username and password for the TIBCO Support Web.

Once logged on you can find the hotfix under the Downloads Menu:

AvailableDownloads/BusinessWorks/BW_Service_Engine/5.11/TIB_amx_3.3.0_hotfix024

TIB_amx_3.3.0-HF-024_readme.txt