Products | Versions |
---|---|
TIBCO ActiveMatrix Service Grid | - |
TIBCO ActiveMatrix Policy Director | - |
TIBCO ActiveMatrix Service Bus | - |
Description:
======================================================================
NOTE: See attached Readme document for installation instructions and issues resolved in previous hotfix releases.
================================================================================
================================================================================
Closed Issues in 3.2.0_hotfix010 (This Release)
This hotfix contains fixes that apply to the following types of installations:
- Administration
- Runtime Host
- TIBCO Business Studio
AMRP-4813
A specific use-case that involves a SOAP/JMS or JMS binding with a
"JMS Transacted OneWay" policy wired to several components and managed
by a single transaction is now supported. In this use-case, a transaction
starts at the SOAP/JMS binding and spans several components. It is
expected that if the transaction rolls back, the incoming messages are
returned to the external JMS queue. Prior to this Hotfix, this behavior
could not be guaranteed because in some cases the TIBCO ActiveMatrix
runtime node would use virtualization queues to route messages. In
those cases, incoming messages would be left in an internal
virtualization queue, and not the external JMS queue.
AMRP-4852
TIBCO ActiveMatrix Runtime Nodes no longer hang intermittently due to
the thread deadlock that occurs while updating the Node's Logging
Configuration, or potentially while logging via System.out.
AMRP-4875
This applies to applications that directly use the LDAP Connection shared
resource. The user application code can now leverage the connection pooling
facility of the LDAP shared resource. It enables the application to close
a stale LDAP connection and acquire a new and functional connection.
AMRP-5046
Threading policy timeout values are set in TIBCO Business Studio
during application design. Per existing system behaviour, no facility was
provided to modify these values during or after deployment time.
A new functionality has been provided that enables certain modifications
to update the timeout values. The units for timeout values must be
specified in milliseconds. This is enabled through a set of modifiable
system properties. The syntax for these properties
is "java.property.<prefix>.invocationTimeoutInMilliseconds".
The value of the "<prefix>" determines the granularity at which the
timeout values are applied.
AMSG-9698
For JMS Service Bindings that contained a single In-Only Operation, the JMS
Message Selector was not applied correctly in the runtime. As a result,
messages were not consumed by the JMS Service Binding and caused a failure.
With this fix, the JMS Message Selector is applied correctly for a WSDL
containing a single In-Only operation and the messages are consumed by
the JMS Service Binding as expected.
BJMS-1578
With this fix, the JMS connection pool no longer grow beyond the "maxsize"
as a result of closed idle connections.
PD-3755/MED-3327
When TIBCO ActiveMatrix Policy Director uses a Proxy Application generated
using the AutoMediate tool, duplicate SOAP Header elements were being
generated for WSDL Operations containing Declared Headers. This was causing
the Proxy Application to add duplicate SOAP Headers in the request. With
this fix, duplicate SOAP header elements are no longer generated by the
AutoMediate tool.
SDS-7052
While creating a DAA using the TIBCO Business Studio Command Line
Interface (CLI) script, if the includeApplicationReferences option
was set to "false", it did not prevent the inclusion of the referenced
resource templates in the DAA. With this fix, the referenced resource
templates are excluded from the DAA when includeApplicationReferences
is set to "false". In this case, to package the resource templates in
the DAA, you must explicitly specify them using the appropriate
nested child elements of the application.
TAP-12981
Partially fixes the issue that some user interface (UI) dialogs in
TIBCO ActiveMatrix Administrator do not function correctly when
using a HTTP Load Balancer with a URL prefix. For example,
"http://<load-balcr-host>:8080/production/amxadministrator",
where "/production" is the prefix. The UI dialogs for JMS-related
resource templates, UDDI servers, and SOAP and JMS binding
configuration now work correctly through the prefix. The UI
dialogs that do not work are the login screen, log viewer,
and dashboard. You must define Load Balancer routing/mapping
rules to ensure these dialogs work correctly.
TAP-13063
With TIBCO ActiveMatrix Administrator, a replicated setup now can be
created successfully in the following scenario:
- Primary instance has this hotfix applied.
- The replicated instance is created after this hotfix is installed.
TAP-14199
Previously, when applications with the same name were distributed
to different environments and an application was deleted from one
environment, applications with the same name in other environments
went into a stopped state. With this fix, the applications in other
environments do not go into a stopped state.
WSBT-1002
Previously, the TIBCO ActiveMatrix HTTP Connector did not return
compressed HTTP messages. This resulted in performance issues for
large payloads. With this enhancement, the HTTP Connector can now
respond with a compressed HTTP response message when the request
message's "Accept-Encoding" header is "gzip,deflate".
================================================================================
Closed Issues in 3.2.0_hotfix009
This hotfix contains fixes that apply to the following types of installations:
- Administration
- Runtime Host
- TIBCO Business Studio
AMRP-4841
Service request processing no longer stalls when using the virtualize and
threading policies together under concurrent high load. The request processing
now uses a dedicated thread pool with the same configuration as the threading
policy.
TAP-13050
HTTP Client Resource template with SSL configuration now shows correctly as
SSL enabled even when the machine name and port are specified with
substitution variables.
================================================================================
Closed Issues in 3.2.0_hotfix008
This hotfix adds fixes that apply to the following types of installations:
- Administration
- Runtime Host
- TIBCO Business Studio
BJMS-1568
When using JMS Transacted One-way policy, the first transaction no longer fails
with the error 'Specified transaction is already associated with another thread'.
DSS-835
TIBCO ActiveMatrix nodes that existed for more than two years no longer produce
the following error when invoking services:
"...TrinityRuntimeException: TCSConnection object is null:; \85"
An internal identity certificate that expires two years after the node
creation is now successfully renewed.
================================================================================
Closed Issues in 3.2.0_hotfix007
This hotfix contain fixes that apply to the following types of installations:
- Administration
- Runtime Host
- TIBCO Business Studio
AMRP-4712
Messages are no longer delivered repeatedly to error queue in case of Mediation
timeout.
AMRP-4759
The SystemNode no longer hangs and gets stuck in Starting state during an
upgrade. This occurred because the node was prematurely processing the RDA
command before the RDA command file was written to disk. The node no longer
prematurely reads the RDA command file to prevent this issue.
BJMS-1561
If the temporary reply destination on the service side is invalid, the JMS
binding reply delivery no longer goes into an infinite loop.
BJMS-1562
Requests with multiple operations are no longer intermittently routed to
incorrect operations.
DSS-808
An incorrect signature is no longer chosen for the authenticated principle
when a message has both valid sender-vouches and holder-of-key signatures.
DSS-822
Kerberos-authenticated security context is now correctly propagated across
virtualized bindings
PER-1793/PER-1908
Now there is more information available related PER-1908 that was fixed in
3.2.0_hotfix006. See below for information on configuring the appearance
of Nonce and Created elements in the UsernameToken element when a Basic
Credential Mapping or WS-Security Credential Mapping policy was used to
insert a UsernameToken in a SOAP security header.
SDS-6797
TIBCO Business Studio can now be used with Oracle Java Runtime Environment 1.7.
When importing projects from ActiveMatrix 3.2.0 or 3.1.X for the first time,
an error will be reported but a Quickfix ("JAR file incompatible with JRE/JDK
1.7 due to containing entries with empty name") will be available to repair the
offending JAR file(s).
SDS-6926
If TIBCO Business Studio fails to start after upgrading the Oracle Java Runtime
Environment to 1.7 on a Windows 64-bit system, the following steps can be
taken to correct it:
TAP-12454
Upgrading an application twice no longer results in a NullPointerException.
TAP-12779
Upgrading an application no longer fails if the user is not granted the
"Create Resource Template" permission. New resource templates are imported
while upgrading an application, provided the user is granted
'Create Resource Template' permission. Warnings are displayed for the
Application upgrade if there are new resource templates in a DAA but
the user had not been granted the permission.
In addition, existing resource templates are no longer overwritten with
those from the DAA, while upgrading an application.
TAP-12837
Deleting a node no longer fails with an integrity constraint violation
error that manifests with the error: "ConstraintViolationException:
could not delete: RequiredCapability#179".
TAP-12892
The configuration property "User Attribute with Group Names" of the
LDAP Authentication resource template is now saved and applied correctly.
Note: If the 'User has groups' option is selected in LDAPAuthentication
Resource Template, you must escape commas when specifying group names in
the configuration field "Roles" which is under \93Governance -> Governance
Control\94 of type \93Authorization by Role\94 in TIBCO ActiveMatrix
Policy Director. For example: CN=Managers\,OU=Groups\,O=Company.
TAP-12928
The Messaging Bus configuration can now be changed for an environment
after upgrading from TIBCO ActiveMatrix version 3.1.5 to version 3.2.0.
While this change can be normally done from Admin UI, you may see an
error while viewing the Messaging Bus configuration from the UI (this
error occurs in a few cases after the upgrade). If you have this situation,
you must perform the change from an Admin CLI script. After running the
CLI script once successfully, subsequent changes can be done from the
Admin UI as the display error will no longer occur.
TAP-12938
TIBCO Policy Director with TIBCO BusinessWorks governance agent no longer
fails to enforce Username Token Authentication because of incorrect
admin_default_keystore URL.
TRUP-364
Publishing to a UDDI registry where bindings are distributed across multiple nodes no longer
results in an exception.
================================================================================
Closed Issues in 3.2.0_hotfix006
AMRP-4649
InvalidTransactionException no longer occurs during the processing of the reply
message when a component that requires a global transaction has a reference that
is virtualized; the transaction is now properly suspended on the request thread
and resumed on the reply thread.
PER-1908
The Nonce and Created elements can now be optionally added when a Basic
Credential Mapping or WSS Credential Mapping policy is used to insert a
UsernameToken in the SOAP security header.
PER-1913
SOAP requests that have a signed SAML token with bearer confirmation method are
now validated correctly.
================================================================================
Closed Issues in 3.2.0_hotfix005
AMX-13875
Installing the hotfix on top of TIBCO BusinessWorks Service Engine installed
with SOA Development profile (Design-time), no longer results in the warning
"ANT Task: Installing TIBCO Business Studio using p2 provisioning has failed".
This issue was introduced with HF-003.
MED-3266
For a one-way MEP operation, invoke tasks on the fault path no longer
fail, and tasks after the invoke task are now processed.
WSBT-828
The "Endpoint URI" field defined in the SOAP Binding with HTTP Transport now may
contain a single token or no token at all, for example, "/sample" or "/".
================================================================================
Closed Issues in 3.2.0_hotfix004
CL-2639
An integrity constraint violation error in the SystemNode.log no longer occurs
when an application uses a log service or payload service created using provided
scripts.
CL-2640
The provided scripts for creating additional log service and payload service
applications no longer fail while installing resource instances.
PER-1786
The Authorization policy template now allows comma separated values in the role
attribute.
TAP-11591
"Force Uninstall" of resource instances no longer fails when applications are
using them.
TAP-11854
Undeploying an application no longer fails with the error "deleted object would
be re-saved by cascade" when Action History shows "In Progress."
TRUP-354
ActiveMatrix services are now published correctly in the registry of TIBCO
ActiveMatrix Lifecycle Governance Registry Foundation.
================================================================================
Closed issues in 3.2.0_hotfix003
AMX-12816
After installing this hotfix on TIBCO ActiveMatrix Administrator SystemNode or
other runtime nodes with Platform Hotfix-001 or Hotfix-002 already installed,
the Hotfix-002 issue fixes will now be in place.
AMX-12817
After installing this hotfix on TIBCO Business Studio with Platform Hotfix-001
or Hotfix-002 already installed, you can now configure a service or reference
binding transport for SOAP over JMS.
================================================================================
Closed issues in 3.2.0_hotfix002
AMX-12254
Using console mode to install an ActiveMatrix 3.2.0 hotfix is now supported.
AMX-12491
Creating an application from TIBCO Business Studio or ActiveMatrix Administrator
no longer fails when WSDL and XSD files have namespaces that contain '#'
characters.
DSS-750
When using a replicated ActiveMatrix Administrator, resource instances no
longer fail to install if the primary Administrator is down.
PER-1793
When a Basic Credential Mapping or WSS Credential Mapping policy is used to
insert a UsernameToken in a SOAP security header, the Nonce and Created element
now appears in the UsernameToken element.
TAP-10974
Deleting applications from ActiveMatrix Administrator after a deployment failure
no longer fails with integrity constraint violation errors.
TAP-11181
When an LDAP directory contains a large number of users, the super users can
now be displayed and edited correctly in ActiveMatrix Administrator.
TAP-11219
After upgrade to ActiveMatrix 3.2.0, keystore errors no longer prevent editing
of JDBC resource templates in ActiveMatrix Administrator.
TAP-11309
ActiveMatrix Administrator UI no longer has slow response times when displaying
the applications list.
WSBT-539
When parameterOrder is specified in the portType, client requests to the SOAP
endpoint no longer fail.
================================================================================
Closed issues in 3.2.0_hotfix001
MCR-1939, MCR-1945
Redeployment of an application no longer results in policy enforcement failures
for policies distributed through TIBCO ActiveMatrix Policy Director.
MCR-1947
When an already deployed application is redeployed to an additional node,
policy enforcement for policies distributed through TIBCO ActiveMatrix Policy
Director now works for newly created bindings on the additional node.
MED-3063
The composite generated by the AutoMediate tool now contains context parameters
for the header elements. WSDLs are now generated correctly through Business
Studio as well as with the ActiveMatrix Administrator.
MED-3149
WSDLs can reference other WSDLs, as well as schemas. The AutoMediate tool used
to generate proxy services is now able to handle dependent schemas that
reference one another in a cycle, such as when a WSDL depends on schema A,
which depends on schema B, while schema B also depends on schema A.
MED-3152
Requirements for composite services created using WSDL port types with
At-Least-Once operation input/output/faults message parts that have references
to external schemas are now getting created correctly, so those services will
now work correctly.
MED-3156
The default non-trivial namespace is now explicitly declared if it is followed
by a child in no namespace, and the DOM is now created with the correct default
prefix.
PER-1746
TIBCO ActiveMatrix Policy Director can now create Governance Controls and
Object Groups on AIX 6.1 64-bit systems.
PER-1757
A Username Token Credential Mapping policy can now be configured without
specifying default credentials. The policy will be deployed and enforced
correctly.
PER-1758
An Authorization policy can now be configured with multiple roles in a comma-
separated list. The policy will correctly check all specified roles, not just
the first one.
PER-1759
A Username Token Credential Mapping policy can now be configured to map
credentials for a specified role. The policy will correctly set the outgoing
credentials as configured for the specified role.
SDS-5060
Validation rules now check property names for hyphen characters for Java,
Spring and WebApp component types only, and no longer erroneously check
them for other composite or component types.
TAP-10914
Re-installation of a Resource Instance while the node is being stopped no longer
fails and corrupts the Resource Instance state (preventing it from being
uninstalled or reinstalled thereafter). Further, after this hotfix is applied
to the ActiveMatrix Administrator server, previously-corrupted Resource Instance
states can be fixed by re-installing the affected Resource Instances once or
twice (if the same error is observed the first time, re-install it a second
time).
TOOL-1341
TIBCO configuration using the console mode now works correctly.
WSBT-536
The SOAP/JMS Binding on the reference-side now supports time-out. Users can
configure the timeout through the "Threading Policy" on the component reference.
Once logged on you can find the hotfix under:
/AvailableDownloads/AMX_Service_Grid/3.2.0/TIB_amx_3.2.0_hotfix010