TIBCO ActiveMatrix(R) Service Grid 3.1.2 Hotfix, TIB_amx_3.1.2_hotfix005, is now available.
Article ID: KB0104003
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix Service Grid | - |
| Not Applicable | - |
Description
Description:
You can download this HotFix from the TIBCO Product Support FTP server using your eSupport username and password, at
ftp://support-ftp.tibco.com
Once you have successfully logged into the server, you will find the hotfix packages under
available_downloads/ActiveMatrix/ActiveMatrixServiceGrid/3.1.2/TIB_amx_3.1.2_hotfix005
Listed below is a summary of updates included. Please refer to the hot fix readme document for any additional information.
================================================================================
Closed Issues in 3.1.2_hotfix005 (This Release)
AMRP-3514
Applications are now able to use third-party web service and JAXP libraries.
AMRP-3560
The "Thread already associated with another transaction" error is no longer
thrown when the at least once policy is configured with a transactional error
queue.
AMRP-3567
Multi-part messages in WSDL files are now handled correctly
AMRP-3585
A NullPointerException is no longer thrown when a BWSE component invokes a Java
component that uses JAXB data binding.
AMX-9971
Upgrade no longer fails when the Administrator server is replicated.
BJMS-1122
A node stops when terminate immediately is invoked from Administrator and no
longer waits indefinitely for JMS bindings to complete processing all messages.
CL-2188
The log client no longer truncates the message field to 2000 characters.
The "cl_logservice_LargerMessagesToPayload" property was added to allow you to
control the log service's behavior. The property is set to false by default to
maintain consistency in behavior from the previous releases.
Message fields are still truncated to 2000 characters before insertion
to the log service's table.
To enable a message field to be saved to the payload service's table without truncation:
1. In the Administrator UI, select SystemEnvironment in the Environment drop-down list.
2. Select the amx.logservice.app application.
3. Click the Properties tab.
4. Click cl_logservice_LargerMessagesToPayload and select true in the Property Value column.
5. Click Save.
5. Click Deploy.
DSS-592
The Password History record being deleted in some cases from the Administrator
server's authentication database no longer occurs so the log in failures also
don't occur.
DSS-633
SAML verfication no longer damages the original SAML assertion when it issues
a new one.
PER-1300
The Credential Mapping policy now selects the SAML assertion based on the
priority of the assertion.
PER-1402
The SAML assertion sequence is now consistent after sending multiple requests
when using SAML Credential Mapping For SSO and SAML Authentication policies.
SDS-5586
The keystore URL picker now displays files with the extension .p12.
SDS-5590
A validation rule that prevented setting a threading policy and a global managed
transaction is now disabled by default.
TAP-8519
Group permissions invalidated by 3.1.2 HF2 are restored.
TAP-8557
The value of the Max Connections field can now be set for an Administrator
server's JDBC resource template.
TAP-8851
A regression was introduced in the script that upgraded 3.1.2 runtime objects
after applying a previous hotfix.
This issue affects only replicated Administrator server configurations.
It causes some actions related to application management to fail when executed
from a different Administrator instance. For example if you created an
application from Admin-instance-1, then deployment from Admin-instance-2 fails.
Running applications are not affected.
The issue occurred the because the upgrade script changed the configured
location of a folder. Files that were supposed to get created under the
original folder location <config-home>/admin/<enterprise>/shared/repo
instead were created under <config-home>/tibcohost/Admin-<enterprise>-<instance>
/nodes/SystemNode/bin/SCMDetails-location.
The "shared" folder is the only folder on a shared file system accessible to
both Administrator replicas. Files created under "SystemNode/bin" are not
accessible by the second Administrator instance, and this causes deployment
actions to fail.
This issue is addressed by running the ant script described in the Upgrade
section. The script:
a) Corrects the configured folder location to again point to "shared/repo".
b) Moves files erroneously created under SystemNode/bin back to "shared/repo"
folder.
c) Makes corresponding changes to the folder paths recorded in the
Administrator database.
TAP-8862
Applications created from composites with embedded composites can now be updated.
TAP-8917
When upgrading applications, the link between dependent applications and the
applications that they depend on is now maintained.
TAP-8936
An HTTP Connector resource template can now be configured to use a Thread Pool
resource instance when SSL is enabled.
TAP-9036
Administrator now correctly handles simultaneous deployment and undeployment of
multiple applications to the same nodes. Administrator's database now gets properly
synchronized with the runtime for feature and component state updates.
TAP-9048
Temporary files under CONFIG_HOME\admin\<enterprisename>\shared\temp are
now deleted.
================================================================================
Closed Issues in 3.1.2_hotfix004
AMRP-3417
SOAP reference bindings no longer drop XML prefixes.
AMRP-3416
Under load SOAP bindings no longer throw NPE when context parameters exist.
AMRP-3408
Redeployment of an application with a dependency now succeeds and does
not indefinitely display "In Progress". Unnecessary component JAR files are
correctly cleaned up from the node.
AMRP-3365
NPE is no longer thrown when attempting to undeploy a component in configured
state after node restart.
AMX-9590
A post-install script has been provided that removes duplicate plug-ins from
TIBCO Business Studio to resolve issues when multiple products are installed in
the same <TIBCO_HOME>. See the section Post-Installation.
BJMS-1035
If an application has a SOAP-JMS reference, the SOAP binding now reconnects to
a JMS server if the server is restarted.
BJMS-1038
Stopping an application or node now completes, even if a reference with a JMS
binding with a long timeout is waiting for a response from an unavailable service.
The fix causes a reference with a JMS binding to stop immediately. If you need
the reference with a JMS binding to stop gracefully while all the outstanding
requests are processed, add the following property to the node TRA file:
com.tibco.amf.binding.jms.closeEndpoint.gracefulShutdown=true
BJMS-1039
JMS bindings now correctly handle reply messages with empty body.
SDS-5359
Generated DAA for SOA projects can now be marked as derived in the preferences
page Window > Preferences > TIBCO SOA Platform > Runtime Artifacts, which
exposes a single checkbox (checked by default) that toggles whether
generated DAAs are marked as derived.
If a DAA is marked as not derived, Subversion will identify a changed DAA as a
candidate for checkin.
To verify if a generated DAA is derived, do the following:
1) Right-click the DAA in the Project Explorer and select Properties.
The dialog that displays has a checkbox Derived which should be
checked if the resource is derived, and unchecked if not.
SDS-5335
Installation of other products in the same <TIBCO_HOME> as ActiveMatrix Service
Grid no longer causes Administrator CLI generation to fail.
SDS-5295
The option to force refresh of the target platform from command line
when TIBCO Business Studio starts is now enabled.
To set the target platform, open
<TIBCO_HOME>/studio/3.5/eclipse/TIBCOBusinessStudio.ini in a text editor and
add the following line:
-DTARGET_PLATFORM_FILE_LOCATION=<absolute path to the .target file>
SDS-5276
TIBCO Business Studio is now able to launch applications with optional
properties in RAD.
TAP-7995
A WSDL file can now be generated for a deployed application after an upgrade to
the application fails.
TAP-8040
Wiring a reference to a virtual service in the Administrator GUI no longer
requires significant time to complete.
TAP-8610
Administrator now correctly handles an update action for a component that is
waiting for dependencies.
TAP-8612
Whitespace changes to a WSDL file no longer prevents an application from being
upgraded.
Note: The fix applies only to newly-built DAAs. After applying the hotfix,
you must regenerate existing DAAs for the projects affected by the defect.
TAP-8614
Warnings of type "Cannot resolve capabilities" are no longer issued when
performing application upgrade from TIBCO Business Studio.
TAP-8458
Internal application deployment files now get cleaned up from the disk on the
machine running the Administrator server.
TAP-8443
An application can now be undeployed even if the deploy or undeploy actions
did not complete successfully.
TAP-8239
In rare situations installing a new node in an existing environment or
deleting an existing environment fails. These actions now succeed.
TAP-8125
Editing a SOAP binding in the Administrator GUI to set a part ("hdr") to header
part type and then saving the binding configuration no longer results in an error.
================================================================================
Closed Issues in 3.1.2_hotfix003
TAP-8166
Binding is now mapped to the node when an application is deployed from TIBCO
Business Studio.
AMRP-3391
When a threading policy is configured in a provider application, a
NullPointerException is no longer thrown at runtime.
AMRP-3390
When a threading policy is configured in a provider application, under heavy
load, applications no longer become unresponsive.
AMRP-3371
The prepareForUndeploy and getServiceTarget callbacks for BPM components
are now called upon node restart.
================================================================================
Closed Issues in 3.1.2_hotfix002
INST-446
The installer now picks the correct configuration directory.
AMX-9218
Every other reply message is no longer lost when an application is upgraded and
two versions of the application's components are running.
AMX-9182
Upgrade no longer fails if the Administrator server is using HTTPS.
BJMS-943
When a Mediation invoke task is used with JMS Reference binding a JMS binding
timeout is now propagated back to Mediation component.
DSS-565
A PartialResultException no longer occurs with Microsoft ActiveDirectory if
"Group has Users" is specified.
DSS-566
A NullPointerException no longer occurs with Microsoft ActiveDirectory if a
Global Catalog is used with "GroupHasUser".
DSS-567
The credential server now starts during Administrator server creation.
DSS-568
Creating a new user in an LDAP authentication realm creation no longer times out
with the error: "Failed to retrieve top-level groups because of LDAP server
error".
DSS-572
A FileNotFoundException is no longer returned from a Keystore Provider while
replicating the Administrator server.
SDS-5155
The name of a promoted composite property no longer has an integer appended to
it.
SDS-5154
The sds.createProject command now behaves the same as the new TIBCO SOA Project
wizard and creates only the correct project assets for a specified project type.
TAP-8075
Removing superusers using the Administrator CLI now works correctly.
To apply the fix to samples in <CONFIG_HOME>/admin/<enterpriseName>/samples,
edit samples/admin-scripts-base.xml and replace these lines:
<import file="${admin.cli.scripts.directory}/classpath_amxadministrator_3.1.2.xml" />
<import file="${admin.cli.scripts.directory}/classpath_credentialserver_3.1.2.xml" />
<import file="${admin.cli.scripts.directory}/classpath_uddi_amxintg_3.1.2.xml" />
with these lines:
<import file="${admin.cli.scripts.directory}/classpath_amxadministrator_3.1.2.HF2.xml" />
<import file="${admin.cli.scripts.directory}/classpath_credentialserver_3.1.2.HF2.xml" />
<import file="${admin.cli.scripts.directory}/classpath_uddi_amxintg_3.1.2.HF2.xml" />
TAP-8059
If you upgrade an application that has SOAP binding and deploy using resolve
mode the appplication is no longer left in a "Partially Deployed" state.
TAP-7935
In Administrator > Governance > Enterprise Permissions you can now add a group
that is member of at least one other group.
MED-2617
Mediation tasks Input / Output that refer to WSDL inline schemas that in turn
refer to each other now resolve correctly.
MED-2670
WSDL files with inline schemas having attributes inside an element will now
show the attributes in the mapper.
MED-2685
Namespace declaration for a prefix used in an attribute of type QName is now
defined properly.
MED-2684
If an optional element of abstract type is used in a Mediation component,
the mapper in Mediation Flow no longer displays an error.
================================================================================
Closed Issues in 3.1.2_hotfix001
TAP-7830
Administrator no longer adds an extra "/" to a SOAP endpoint URI whenever a
a SOAP binding is created or edited.
TAP-7781
When an application with an outgoing reference is upgraded, the mapping of the
binding to the node is no longer lost. When the application is deployed, the
endpoints for the reference are no longer removed.
TAP-7764
Application upgrade now works when WSDL definition of a service provider is
changed but the service name is not changed.
SDS-5033
Exporting a custom feature as DAA no longer fails with the exception
"The feature xxxxxxx.feature was not resolved and is required for packaging".
SDS-5023
Business Studio now allows you to set the 'replyTo' property of an inbound
destination
MED-2618
A JDBC connection leak exception is no longer thrown during initialization when
the JDBC property of a Mediation flow with a QueryDB task is read.
CL-1992
When there are more than 100k logrecords in the logservice database, the node
that runs logservice no longer goes out of memory with default heap size
setting when the logservice is restarted.
CL-1981
When using the Log Viewer you are now able to run queries after exporting log
entries.
BJMS-810
A JMS reference with an In-only operation without any part in the input message,
and XMLBytes as Message Type no longer creates an incorrect JMS message type in
the reference queue
BJMS-804
When reference with a JMS binding is configured with
fixed-reply queue (for in-out MEP), the request message now sends the
correlation ID that has been set in in the context of the request message.
AMRP-3218
A TIBCO Host instance now requires all nodes to be running when you perform an
action to secure the communication to its nodes. If any of the nodes is not
running, the action will return an error without making any changes.
================================================================================
You can download this HotFix from the TIBCO Product Support FTP server using your eSupport username and password, at
ftp://support-ftp.tibco.com
Once you have successfully logged into the server, you will find the hotfix packages under
available_downloads/ActiveMatrix/ActiveMatrixServiceGrid/3.1.2/TIB_amx_3.1.2_hotfix005
Listed below is a summary of updates included. Please refer to the hot fix readme document for any additional information.
================================================================================
Closed Issues in 3.1.2_hotfix005 (This Release)
AMRP-3514
Applications are now able to use third-party web service and JAXP libraries.
AMRP-3560
The "Thread already associated with another transaction" error is no longer
thrown when the at least once policy is configured with a transactional error
queue.
AMRP-3567
Multi-part messages in WSDL files are now handled correctly
AMRP-3585
A NullPointerException is no longer thrown when a BWSE component invokes a Java
component that uses JAXB data binding.
AMX-9971
Upgrade no longer fails when the Administrator server is replicated.
BJMS-1122
A node stops when terminate immediately is invoked from Administrator and no
longer waits indefinitely for JMS bindings to complete processing all messages.
CL-2188
The log client no longer truncates the message field to 2000 characters.
The "cl_logservice_LargerMessagesToPayload" property was added to allow you to
control the log service's behavior. The property is set to false by default to
maintain consistency in behavior from the previous releases.
Message fields are still truncated to 2000 characters before insertion
to the log service's table.
To enable a message field to be saved to the payload service's table without truncation:
1. In the Administrator UI, select SystemEnvironment in the Environment drop-down list.
2. Select the amx.logservice.app application.
3. Click the Properties tab.
4. Click cl_logservice_LargerMessagesToPayload and select true in the Property Value column.
5. Click Save.
5. Click Deploy.
DSS-592
The Password History record being deleted in some cases from the Administrator
server's authentication database no longer occurs so the log in failures also
don't occur.
DSS-633
SAML verfication no longer damages the original SAML assertion when it issues
a new one.
PER-1300
The Credential Mapping policy now selects the SAML assertion based on the
priority of the assertion.
PER-1402
The SAML assertion sequence is now consistent after sending multiple requests
when using SAML Credential Mapping For SSO and SAML Authentication policies.
SDS-5586
The keystore URL picker now displays files with the extension .p12.
SDS-5590
A validation rule that prevented setting a threading policy and a global managed
transaction is now disabled by default.
TAP-8519
Group permissions invalidated by 3.1.2 HF2 are restored.
TAP-8557
The value of the Max Connections field can now be set for an Administrator
server's JDBC resource template.
TAP-8851
A regression was introduced in the script that upgraded 3.1.2 runtime objects
after applying a previous hotfix.
This issue affects only replicated Administrator server configurations.
It causes some actions related to application management to fail when executed
from a different Administrator instance. For example if you created an
application from Admin-instance-1, then deployment from Admin-instance-2 fails.
Running applications are not affected.
The issue occurred the because the upgrade script changed the configured
location of a folder. Files that were supposed to get created under the
original folder location <config-home>/admin/<enterprise>/shared/repo
instead were created under <config-home>/tibcohost/Admin-<enterprise>-<instance>
/nodes/SystemNode/bin/SCMDetails-location.
The "shared" folder is the only folder on a shared file system accessible to
both Administrator replicas. Files created under "SystemNode/bin" are not
accessible by the second Administrator instance, and this causes deployment
actions to fail.
This issue is addressed by running the ant script described in the Upgrade
section. The script:
a) Corrects the configured folder location to again point to "shared/repo".
b) Moves files erroneously created under SystemNode/bin back to "shared/repo"
folder.
c) Makes corresponding changes to the folder paths recorded in the
Administrator database.
TAP-8862
Applications created from composites with embedded composites can now be updated.
TAP-8917
When upgrading applications, the link between dependent applications and the
applications that they depend on is now maintained.
TAP-8936
An HTTP Connector resource template can now be configured to use a Thread Pool
resource instance when SSL is enabled.
TAP-9036
Administrator now correctly handles simultaneous deployment and undeployment of
multiple applications to the same nodes. Administrator's database now gets properly
synchronized with the runtime for feature and component state updates.
TAP-9048
Temporary files under CONFIG_HOME\admin\<enterprisename>\shared\temp are
now deleted.
================================================================================
Closed Issues in 3.1.2_hotfix004
AMRP-3417
SOAP reference bindings no longer drop XML prefixes.
AMRP-3416
Under load SOAP bindings no longer throw NPE when context parameters exist.
AMRP-3408
Redeployment of an application with a dependency now succeeds and does
not indefinitely display "In Progress". Unnecessary component JAR files are
correctly cleaned up from the node.
AMRP-3365
NPE is no longer thrown when attempting to undeploy a component in configured
state after node restart.
AMX-9590
A post-install script has been provided that removes duplicate plug-ins from
TIBCO Business Studio to resolve issues when multiple products are installed in
the same <TIBCO_HOME>. See the section Post-Installation.
BJMS-1035
If an application has a SOAP-JMS reference, the SOAP binding now reconnects to
a JMS server if the server is restarted.
BJMS-1038
Stopping an application or node now completes, even if a reference with a JMS
binding with a long timeout is waiting for a response from an unavailable service.
The fix causes a reference with a JMS binding to stop immediately. If you need
the reference with a JMS binding to stop gracefully while all the outstanding
requests are processed, add the following property to the node TRA file:
com.tibco.amf.binding.jms.closeEndpoint.gracefulShutdown=true
BJMS-1039
JMS bindings now correctly handle reply messages with empty body.
SDS-5359
Generated DAA for SOA projects can now be marked as derived in the preferences
page Window > Preferences > TIBCO SOA Platform > Runtime Artifacts, which
exposes a single checkbox (checked by default) that toggles whether
generated DAAs are marked as derived.
If a DAA is marked as not derived, Subversion will identify a changed DAA as a
candidate for checkin.
To verify if a generated DAA is derived, do the following:
1) Right-click the DAA in the Project Explorer and select Properties.
The dialog that displays has a checkbox Derived which should be
checked if the resource is derived, and unchecked if not.
SDS-5335
Installation of other products in the same <TIBCO_HOME> as ActiveMatrix Service
Grid no longer causes Administrator CLI generation to fail.
SDS-5295
The option to force refresh of the target platform from command line
when TIBCO Business Studio starts is now enabled.
To set the target platform, open
<TIBCO_HOME>/studio/3.5/eclipse/TIBCOBusinessStudio.ini in a text editor and
add the following line:
-DTARGET_PLATFORM_FILE_LOCATION=<absolute path to the .target file>
SDS-5276
TIBCO Business Studio is now able to launch applications with optional
properties in RAD.
TAP-7995
A WSDL file can now be generated for a deployed application after an upgrade to
the application fails.
TAP-8040
Wiring a reference to a virtual service in the Administrator GUI no longer
requires significant time to complete.
TAP-8610
Administrator now correctly handles an update action for a component that is
waiting for dependencies.
TAP-8612
Whitespace changes to a WSDL file no longer prevents an application from being
upgraded.
Note: The fix applies only to newly-built DAAs. After applying the hotfix,
you must regenerate existing DAAs for the projects affected by the defect.
TAP-8614
Warnings of type "Cannot resolve capabilities" are no longer issued when
performing application upgrade from TIBCO Business Studio.
TAP-8458
Internal application deployment files now get cleaned up from the disk on the
machine running the Administrator server.
TAP-8443
An application can now be undeployed even if the deploy or undeploy actions
did not complete successfully.
TAP-8239
In rare situations installing a new node in an existing environment or
deleting an existing environment fails. These actions now succeed.
TAP-8125
Editing a SOAP binding in the Administrator GUI to set a part ("hdr") to header
part type and then saving the binding configuration no longer results in an error.
================================================================================
Closed Issues in 3.1.2_hotfix003
TAP-8166
Binding is now mapped to the node when an application is deployed from TIBCO
Business Studio.
AMRP-3391
When a threading policy is configured in a provider application, a
NullPointerException is no longer thrown at runtime.
AMRP-3390
When a threading policy is configured in a provider application, under heavy
load, applications no longer become unresponsive.
AMRP-3371
The prepareForUndeploy and getServiceTarget callbacks for BPM components
are now called upon node restart.
================================================================================
Closed Issues in 3.1.2_hotfix002
INST-446
The installer now picks the correct configuration directory.
AMX-9218
Every other reply message is no longer lost when an application is upgraded and
two versions of the application's components are running.
AMX-9182
Upgrade no longer fails if the Administrator server is using HTTPS.
BJMS-943
When a Mediation invoke task is used with JMS Reference binding a JMS binding
timeout is now propagated back to Mediation component.
DSS-565
A PartialResultException no longer occurs with Microsoft ActiveDirectory if
"Group has Users" is specified.
DSS-566
A NullPointerException no longer occurs with Microsoft ActiveDirectory if a
Global Catalog is used with "GroupHasUser".
DSS-567
The credential server now starts during Administrator server creation.
DSS-568
Creating a new user in an LDAP authentication realm creation no longer times out
with the error: "Failed to retrieve top-level groups because of LDAP server
error".
DSS-572
A FileNotFoundException is no longer returned from a Keystore Provider while
replicating the Administrator server.
SDS-5155
The name of a promoted composite property no longer has an integer appended to
it.
SDS-5154
The sds.createProject command now behaves the same as the new TIBCO SOA Project
wizard and creates only the correct project assets for a specified project type.
TAP-8075
Removing superusers using the Administrator CLI now works correctly.
To apply the fix to samples in <CONFIG_HOME>/admin/<enterpriseName>/samples,
edit samples/admin-scripts-base.xml and replace these lines:
<import file="${admin.cli.scripts.directory}/classpath_amxadministrator_3.1.2.xml" />
<import file="${admin.cli.scripts.directory}/classpath_credentialserver_3.1.2.xml" />
<import file="${admin.cli.scripts.directory}/classpath_uddi_amxintg_3.1.2.xml" />
with these lines:
<import file="${admin.cli.scripts.directory}/classpath_amxadministrator_3.1.2.HF2.xml" />
<import file="${admin.cli.scripts.directory}/classpath_credentialserver_3.1.2.HF2.xml" />
<import file="${admin.cli.scripts.directory}/classpath_uddi_amxintg_3.1.2.HF2.xml" />
TAP-8059
If you upgrade an application that has SOAP binding and deploy using resolve
mode the appplication is no longer left in a "Partially Deployed" state.
TAP-7935
In Administrator > Governance > Enterprise Permissions you can now add a group
that is member of at least one other group.
MED-2617
Mediation tasks Input / Output that refer to WSDL inline schemas that in turn
refer to each other now resolve correctly.
MED-2670
WSDL files with inline schemas having attributes inside an element will now
show the attributes in the mapper.
MED-2685
Namespace declaration for a prefix used in an attribute of type QName is now
defined properly.
MED-2684
If an optional element of abstract type is used in a Mediation component,
the mapper in Mediation Flow no longer displays an error.
================================================================================
Closed Issues in 3.1.2_hotfix001
TAP-7830
Administrator no longer adds an extra "/" to a SOAP endpoint URI whenever a
a SOAP binding is created or edited.
TAP-7781
When an application with an outgoing reference is upgraded, the mapping of the
binding to the node is no longer lost. When the application is deployed, the
endpoints for the reference are no longer removed.
TAP-7764
Application upgrade now works when WSDL definition of a service provider is
changed but the service name is not changed.
SDS-5033
Exporting a custom feature as DAA no longer fails with the exception
"The feature xxxxxxx.feature was not resolved and is required for packaging".
SDS-5023
Business Studio now allows you to set the 'replyTo' property of an inbound
destination
MED-2618
A JDBC connection leak exception is no longer thrown during initialization when
the JDBC property of a Mediation flow with a QueryDB task is read.
CL-1992
When there are more than 100k logrecords in the logservice database, the node
that runs logservice no longer goes out of memory with default heap size
setting when the logservice is restarted.
CL-1981
When using the Log Viewer you are now able to run queries after exporting log
entries.
BJMS-810
A JMS reference with an In-only operation without any part in the input message,
and XMLBytes as Message Type no longer creates an incorrect JMS message type in
the reference queue
BJMS-804
When reference with a JMS binding is configured with
fixed-reply queue (for in-out MEP), the request message now sends the
correlation ID that has been set in in the context of the request message.
AMRP-3218
A TIBCO Host instance now requires all nodes to be running when you perform an
action to secure the communication to its nodes. If any of the nodes is not
running, the action will return an error without making any changes.
================================================================================
Issue/Introduction
TIBCO ActiveMatrix(R) Service Grid 3.1.2 Hotfix, TIB_amx_3.1.2_hotfix005, is now available.
Environment
Product: TIBCO ActiveMatrix Service Grid
Version: 3.1.2
OS: All
--------------------
Feedback
Yes
No
Powered by
