Version 1

    Actional Release 2015.0.1.9

    1. Release Installation Instructions

    2. Issues Addressed in this Release

    1. Release Installation

    Installation instructions are covered in detail in the appropriate Installation Guides.

    • Actional Management Server Installation Guide
    • Actional Agent Installation Guide
    • Actional Intermediary Installation Guide

    Top

    2.Issues addressed in this Release

    Issues resolved in Release 2015.0.1.9

     

    UPGRADE AND COMPATIBILITY
    • Database schema updates were required to support the new feature to trigger preserve audit log persistence on demand.
    • Database migration scripts must be run when upgrading to 2015 SP1 HF9 from a version of 2015 SP1 prior to 2015 SP1 HF7.
    • Database migration scripts must be run when upgrading to 2015 SP1 HF9 from a version of 2015 that is prior to 2015 HF8. If upgrading from 2015 HF8 or higher, creation failure messages may occur in the logs. This is expected as there is a table and index that will already exist (related to act_monitored_flow_*). These creation failures can be ignored.
    • Database migration scripts must be run when upgrating to 2015 SP1 HF9 from a version of 2013 that is prior to 2013 HF17. If upgrading from 2013 HF17 or higher, creation failure messages may occur in the logs. This is expected as there is a table and index that will already exist (related to act_monitored_flow_*). These creation failures can be ignored.
    Management Server / Agent
    • 27997 - com.actional.util.Util.getEnv(String) not working on non-Windows platforms
    • 28045 - Error "LGSERVER0224: Field none not applicable as filter" occurs when click on alert visualizer table
    • 28090 - Interceptor SDK Sample9 packaged JAR does not contains the AAL
    • 28176 - Number of JMS connections setting is not functional for JMS 1.1 ConnectionFactory
    • 28229 - NPE in JMSTransportConfigServlet occurs when temporary destination is used for Consumer
    • 28289 - Webmethods Integration Server Correlation is not functional when Univeral Messaging Document is used with ProtocolBuffer encoding type
    • 28338 - Webmethods Integration Server Document name is not used when Univeral Messaging Document is using 'ProtocolBuffers' encoding
    • 28388 - ActionalBrokerDocumentType property appears as encoded event data if the receiver is not using Integration Server services
    Intermediary
    • 28175 - Actional Intermediary starts too many JMS connections per transport

    Issues resolved in Release 2015.0.1.8

     

    UPGRADE AND COMPATIBILITY
    • Database schema updates were required to support the new feature to trigger preserve audit log persistence on demand.
    • Database migration scripts must be run when upgrading to 2015 SP1 HF8 from a version of 2015 SP1 prior to 2015 SP1 HF7.
    • Database migration scripts must be run when upgrading to 2015 SP1 HF8 from a version of 2015 that is prior to 2015 HF8. If upgrading from 2015 HF8 or higher,  there is a table and index that will already exist (related to act_monitored_flow_*). These creation failures can be ignored.
    • Database migration scripts must be run when upgrating to 2015 SP1 HF8 from a version of 2013 that is prior to 2013 HF17. If upgrading from 2013 HF17 or higher, there is a table and index that will already exist (related to act_monitored_flow_*). These creation failures can be ignored.
    Management Server / Agent
    • 20106 - Remove the "show all" option in event logs as it can cause a hang if the number of event logs is high.
    • 27289 - Address errors thrown in oracle migration script from version 2013 to 2015
    • 27314 - Disallow custom file download from eventlog UI
    • 27952 - Handle cases where webServices watchdog throws exception:  'IOException OutputStream is closed'
    • 27965 - Unable to use policy "distributing alert with notifier" option with SNMP plugin
    • 28014 - LogBackup servlet erroneously allows the download of any files
    • 28015 - SnmpPlugin itsAddrMap is not thread-safe
    Intermediary
    • 27302 - Handle NPE when AI raises soap fault with NPE for invalid request
    • 27812 - Enforce an upper bound for uncorrelated replies background buffer
    • 27914 - Log "JMS Producer keyID is not found for the JMS reply" messages as normal debug messages.
    • 27950 - Handle LicenseManager NPE on startup

    Issues resolved in Release 2015.0.1.7

     

    UPGRADE AND COMPATIBILITY
    • Database schema updates were required to support the new feature to trigger preserve audit log persistence on demand.
    • Database migration scripts must be run when upgrading to 2015 SP1 HF7 from a prior version of 2015 SP1.
    • Database migration scripts must be run when upgrading to 2015 SP1 HF7 from a version of 2015 that is prior to 2015 HF8. If upgrading from 2015 HF8 or higher,  there is a table and index that will already exist (related to act_monitored_flow_*). These creation failures can be ignored.
    • Database migration scripts must be run when upgrating to 2015 SP1 HF7 from a version of 2013 that is prior to 2013 HF17. If upgrading from 2013 HF17 or higher, there is a table and index that will already exist (related to act_monitored_flow_*). These creation failures can be ignored.
    Management Server / Agent
    • 5466 - Implement separate warning and alert counters
    • 26505 - Oracle db creation scripts fail for Actional 2015 SP1 using Oracle 12c.
    • 26888 - Implement API to trigger preserved audit log persistence
    • 26948 - Implement Task API in Agent that keeps track of flow IDs that must be audited
    • 26949 - Implement Task API in Server that keeps track of flow IDs that must be audited
    • 26995 - Optimize flow monitoring SQL updates
    • 27074 - Implement flow monitoring support for older agents
    • 27107 - Persist flows to audit in database
    • 27139 - Editing the name for information filter can produce an error
    • 27156 - Each flow monitoring cache should have its own setting
    • 27160 - MONITORING0090: Audit request record update failed
    • 27213 - Setting admin roles in AI results in an error
    • 27223 - Flow monitoring does not properly clear out old flows
    • 27246 - Flow monitoring table is not properly cleaned up if size decreased before shutdown
    • 27321 - Provide metric about JMS.send directly in the interactions
    • 27325 - Agent are not persisting the agent event's details field in the SQL table act_agent_events
    • 27368 - Gzip Request compression throws XMLParseException
    • 27425 - Include a Clock Profile to track providers queue size
    • 27458 - Improve table existence check
    • 27788 - Audit records no longer sets the payload size if the audit body or reply is not set.
    Intermediary
    • 27137 - [REST] No REST header parameters are passed when "Passthrough Message Data" is turned on
    • 27142 - Clock Profiling for JMS operations in AI
    • 27303 - AI raises soap fault with NPE for malformed request
    • 27320 - Admin console denying access when request comes through a different port from firewall/proxy
    • 27428 - LDAP user caching does not work between different types of credentials
    • 27404 - LDAP Injection Vulnerability with AI HTTP BASIC Authentication Contracts

    Issues resolved in Release 2015.0.1.6

     

    Management Server / Agent
    • 26969 - Improve Flowmap capture logic
    • 26096 - SECU1022: The principal does not belong to one of the authorized roles error.</>
    • 27003 - Improve Flowmap gather locking logic
    • 27011 - Classpath issue when running JMS interceptor on JDK 1.4

    Issues resolved in Release 2015.0.1.5

     

    Management Server / Agent
    • 26057 - Provide ability for flow fields to allow specifying a part
    • 26190 - Support for CentraSite v9.10
    • 26190 - Support for webMethods Integration Server v9.10
    • 26190 - Support for webMethods Mediator v9.10
    • 26190 - Support for webMethods Universal Messaging v9.10
    • 26190 - Support for webMethods Broker 9.6 shipped with WebMethods 9.10
    • 26589 - Error generating support.zip if Cassandra is configured
    • 26628 - NPE when executing no-activity policies
    • 26758 - Establishing a JMS Connection can block connections to other brokers when fault tolerance is turned on
    • 26779 - Service Groups with a JMS broker in the middle can pausing when a broker goes down
    • 26800 - UI hang in JMS consumer status with failover and broker down
    Intermediary
    • 25422 - Provide ability for the IAuthenticateContext interface to obtain the Authenticated Identity
    • 26580 - Upgrading AI to 2013 and sending a request to an AP throws a NPE
    • 26674 - AI is unable to process messages when the broker used for JMS Audit is down
    • 26675 - Service Dispatcher issue occurring during AI Shutdown
    Interceptor
    • 26058 - Update java interceptor SDK to provide APIs that allow a xpath-capable interceptor to do its work
    • 26250 - webMethods Broker Documents fail validation with an unexpected node after interceptor injects a "_property" element into payload documents

    Issues resolved in Release 2015.0.1.4

     

    Management Server / Agent
    • 4288  - Provide Business Process name in the alert message
    • 25243 - Negative values during reconnect should be rounded to zero
    • 25326 - Add ability to define additional JMS transports for Agents to use during JMS Auditing
    • 26062 - JMS Audit task for AI throws exception in Audit write
    • 26143 - AMS logs flooded with "APPL0109: Invalid parameter: query.handle" error
    • 26158 - java.lang.ClassCastException while selecting Cassandra DB on audit logs
    • 26560 - ClassNotFoundException in AMS when running no activity policy
    • 26626 - NPE when executing no-activity policies
    Intermediary
    • 25660 - AI JMS reply lookup can lead to excessive latency in processing reply messages when message correlationID is not in the correlation map
    • 25955 - Unable to remove XSLT in Intercept block for unchecked behavior in Service group
    • 26099 - AI UI gets into a 'Please Wait' state in ESB Select Process

    Issues resolved in Release 2015.0.1.3

     

    Management Server / Agent
    • 25419 - Support for CentraSite v9.9
    • 25419 - Support for webMethods Integration Server v9.9
    • 25419 - Support for webMethods Mediator v9.9
    • 25419 - Support for webMethods Universal Messaging v9.9
    • 25419 - Support for webMethods Broker 9.6 shipped with WebMethods 9.9
    • 24785 - Discard JMS Audit events when the Audit broker is down
    • 25025 - Deadlock in Actional code when starting a cluster
    • 25790 - Reconnecting Flow Calls timing out after their processing has been delayed by the Analyzer
    Intermediary
    • 23497 - While configuring SG using PassThrough wizard, changes to the unique ID are not reflected in the read only URL.
    • 23500 - While configuring SG using PassThrough wizard, if the checkbox for "Use ID relative.." is checked, the changes in URl are not observed on revisting the same page."
    • 25382 - Extended Export: The dependency between Service Groups and Roles does not appear in the service group dependency tree
    • 25131 - AI cannot authentication and authorized LDAP users with "/" in the name.
    • 25349 - AI is unable to create temporary queues if the JMS 1.1 ConnectionFactory implementation is generic.
    • 25667 - Set AI “Disable ESB Interactor Proxy” flag default value to true.
    • 25800 - Request payload is incorrectly returned when ESB Process fault mapping is incorrect
    • 25842 - Initialization ordering issues between Service dispatcher and JMS Manager during AI startup
    • 25929 - Lucene indexer crash while closing indexes while other threads are still accessing it.
    • 25979 - Error provisioning AI as a JMS audit producer due to incorrect producer status validation check
    • 5225 - Class cast exception while switching between Sonic ESB instances
    Interceptor
    • 24778 - EOF exception in CXF interceptor payload capture
    • 25731 - java.io.IOException: mark/reset not supported in CXF payload capture
    • 25767 - Provde a new configuration property that allows to limit the message payload sizeor CXF interceptor.  Needed to properly handle message payload kept in memory

    Issues resolved in Release 2015.0.1.2

     

    Management Server / Agent
    • 24303 - Issues with correlation from CXF to Integration Server
    • 24334 - Misspelled procedure name while generating database purge scripts
    • 25026 - Performance problems with provisioning
    • 24951 - Management Server is publishing replicas of the same Server Interaction to CentraSite
    • 24250 - Include Cassandra installation creation scripts in the default deployment.
    Intermediary
    • 24485 - Support for Oracle Access Manager (OAM) 11G
    • 24787 - Incorrect Access Point details observed in Webservices Consumer Views
    • 24846 - All visibile operations appear twice causing failure when calling an access point.
    • 25173 - Cannot upload AI deployment profiles to AMS if AMS version is Actional 2015 or later
    • 25176 - java.util.ConcurrentModificationException encountered in AI
    Interceptor
    • 24271 - Interceptor should not be logging Interaction and Event related debug
    • 25186 - Create BizSolo interceptor
    • 24589 - NPE with JMS trigger when Management Server is instrumented in Integration Server

    Issues resolved in Release 2015.0.1.1

     

    Management Server / Agent
    • 23820 - Cannot manage Agents with JMS transport
    • 23734 - Global search does not list any elements
    • 23739 - Clickjacking vulnerability observed during a security scan of Actional Management Server
    • 23522 - Change the wording in the UI from  ‘Audit Only if Alarm is Raised’ to "Audit Only for Flow Mapped Alarm"
    • 24201 - SAG IS service not recognized, shown as ‘unknown’
    • 23506 - Agent startup takes upto ~4 minutes
    • 23479 - Item Breakdown Information is no longer displayed when node is deselected
    • 24641 - Using OAM Cookie Provisioner on the Application Security Contract causes a NPE
    Intermediary
    • 23286 - XML Bomb Security vulnerability
    • 23739 - 'Clickjacking' security issue found during a security scan on actional AMS
    • 23990 - Actional Intermediary JSON fault response is not well-formed
    • 23251 - Actional is exposing sensitive information in payload when a wrong URL is accessed
    • 23977 - Unexpected exception for certificate expiry check
    • 23939 - All operations are added when adding more operations to Access Points
    • 23959 - WSDL update in Intermediary block does function when wsdl is updated via URL
    Interceptor
    • 23917 - Error when using FastInfoSet with CXF interceptors

     

    Top