Version 2

    Actional Release 2013.0.0.12

    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 2013.0.0.12

     

    Intermediary
    • 24485 - Support for Oracle Access Manager (OAM) 11G

    Issues resolved in Release 2013.0.0.11

     

    Management Server / Agent
    • 24201 - SAG IS service not recognized, shown as (unknown)
    Intermediary
    • 23959 - WSDL update in Intermediary block does not work when wsdl is updated via URL
    • 23506 - Startup takes up to ~4 minutes
    • 24478 - Upgrading AI from 8.2.5 to 2013 and sending a request to an AP causes an NPE
    • 24641 - Using OAM Cookie Provisioner on the Application Security Contract causes an NPE
    Interceptors
    • 23917 - Error when using FastInfoSet with CXF interceptors
    • 24316 - Convert CXF Interceptor settings to use ISettings.  This updates the way interceptor settings are pushed from AMS thus no longer requiring a reload of the Application Server
    • 24345 - Update CXF Interceptor property for backwards compatibility for outbound JAX-RS calls

    Issues resolved in Release 2013.0.0.10

     

    Management Server / Agent
    • 23325 - Unable to create Analyst Studio views in MS SQL
    • 23391 - Dynamic URL filtering not kicking in on ClientInteractions
    • 23709 - BP Archiver throws ORA-01795: maximum number of expressions in a list is 1000
    • 23759 - NPE thrown when using AMS to browse BPs
    • 23770 - AMS upgrade fails for TimeRangeCondition with INTEGRITY0164
    • 23844 - Provisioning stats to CentraSite for a SAG Mediator service resulted in a NPE
    • 23901 -  Analyzer ClassCastException
    • 24004 - Change the wording in UI for 'Audit Only if Alarm is Raised' to 'Audit Only for "flowmapped" alarms'
    Intermediary
    • 23255 - Actional is exposing sensitive information in payload when a wrong URL is accessed
    • 23287 - XML Bomb Security vulnerability
    • 23991 - When AI is asked to return 'application/json' content type and a fault is thrown (security or others), the returned message is not proper JSON format
    • 24183 - AI SOAP over JMS protocol throws NPE
    Interceptors
    • 23639 - HTTP response code report for .NET HTTP-based interceptors

    Issues resolved in Release 2013.0.0.9

     

    Management Server / Agent
    • 23322 - NPE in AMS logs
    • 23394 - Agents do not persist audit entries for a flowmap
    • 23509 - AnalyzerOpenCall memory usage issue
    • 23560 - ClassCastException on auditing request to chained service group
    Intermediary
    • 23097 - Unable to set/modify/add REST parameters using interceptor plugin
    • 23256 - Sensitive information is exposed in HTTP responses
    • 23504 - Information Filter can consume a large amount of CPU

    Issues resolved in Release 2013.0.0.8

     

    Management Server / Agent
    • 22965 - Unable to show FlowMap for an alert
    • 23000 - Transaction Lookup links generates error and does not show flowmap
    Intermediary
    • 20721 - Restrict AI Admin Port
    • 22790 - NPE - When viewing the Transports page in the AI GUI
    • 22907 - AI restriction for Admin Console transport does not work for transport objects that is not assigned to the AP
    • 22989 - "NoClassDefFoundError: sun/security/x509/X500Signer" when trying to create a CSR
    • 23035 - Transformation in AI (Interceptor or Transformation Block) sometimes does not apply the XSL
    • 23076 - AI fails to start if the HTTP/S transport is configured from SoapAPI without a listener
    • 23079 - HTTP/S Transport page throws nullpointerexception for transport that is created using SOAP API without a listener
    Interceptor
    • 22537 - JMS interceptor reports receive+OnMessage for Spring use cases
    • 22734 - Add hookpoints to spring workmanager taskexecutor
    • 22896 - Support for webMethods Integration Server 9.0
    • 22896 - Support for webMethods Mediator 9.0
    • 22896 - Support for webMethods Broker 9.0

    Issues resolved in Release 2013.0.0.7

     

    Management Server / Agent
    • 22245 - java.io.EOFException: Unexpected end-of-data while processing the reply
    • 22466 - Tomcat start-up error
    • 22473 - Illegal characters found in ActionalServer.xml file
    • 22474 - External watchdog policy does not work when the policy target site matcher selected node as Watchdogs
    • 22478 - "WARN!! null null null HttpException(414,Request URI Too Large,null)" + wrong URL reported in AMS logs
    • 22484 - AI causing 100% CPU usage on a 16 core server
    • 22488 - Instrumented system blocked by UplinkConfig.isAlive() call if Agent ran OOM
    • 22492 - Instrumented system causes a huge number of of extra file system access
    • 22527 - Policy import does not trigger provisioning nor updates policy target properly
    • 22542 - Information Filter generating OperationNotSupportedException
    • 22544 - AMS login failure with Active Directory users that have many groups.
    • 22548 - Failure in AMS upgrade when upgrading to 2013 with error 'CFGMGR0072: Field 'enterprise' must NOT have a value of FALSE.'
    • 22569 - JMS Transport UI details page hangs when management broker down
    • 22577 - Provisioing with Watchdog policies fails
    • 22581 - Message fields created in AI loses its configuration when AI is provisioned from AMS
    • 22635 - AA Out Of Memory Due to FDR Size Computation
    • 22638 - Provisioning is not audited as part of configuration change
    • 22642 - JMS Producer Status is incorrect
    • 22765 - FDRManager is holding onto more memory than required, which cause Agent OOM
    Intermediary
    • 22243 - AI does not pass through simple JMS-to-JMS request and does not log any error
    • 22441 - SSLv3 vulnerability for Actional deployed in Jetty, allow Jetty to exclude SSL protocols
    • 22464 - Creating a service group using the compound wizard leads to loss of header information.
    • 22467 - Issues with bringing AI under management if AI has cluster members
    • 22469 - NPE when sending a REST POST request with HTTP Content-Length=0
    • 22470 - AI adds charset=null after the TRANSFORM before Managed Service
    • 22471 - WSDL Operations are not exposed if there are changes in the headers definition when a new WSDL is imported
    • 22477 - Support for custom mapping of LDAP account attribute with certificate
    • 22575 - Some properties of SAML Issuer configuration not displayed on AI portal
    • 22646 - Changes to LDAP certificate mappings requires a AI restart for the change to be valid
    • 22714 - AI cannot match incoming certificate if the user account contains a list of certificates.>
    • 22717 - Import statement in the WSDL causes an error at the access point.
    • 22723 - Sporadic java.lang.ClassNotFoundException in AI plugin
    • 22725 - Transformation in AI (Interceptor or Transformation Block) sometimes does not apply the XSL
    • 22726 - Support for Oracle DS certificate and multiple certificate matching
    • 22742 - Enhance flexible LDAPv3 certificate mapping to support other fields other than subject DN
    Interceptor
    • 22495 - Karaf OSGI container instrumentation errors with CXF interceptor

    Issues resolved in Release 2013.0.0.6

     

    Management Server / Agent
    • 20088 - Alert Visualizer: Perspective configuration icon/button appears in Transaction Lookup page
    • 20094 - Alert Visualizer: clearing the Quick Text filter leaves an empty criteria
    • 20264 - Error thrown when try to send the request with ReplyTo is set to JMSTransport which does not have Producer configured
    • 20273 - Transfer Ownership does not transfer ownership of public filters in Alert UI
    • 20295 - Editing the JMS Transport produces and NPE
    • 20318 - NullpointerException in com.actional.util.MessageContentTypes.defaultCharset
    • 20320 - Aler Notifier should call destroy rather than create a new plugin instance for every alert
    • 20326 - Unable to bring an agent under management using JMS
    • 20333 - Application fails to deploy in Tomcat after enabling Actional
    • 20345 - ClientID on the JMS Transport is settable but it is not being used.
    • 20372 - Instrumented application produces large number of file access related system calls
    • 20386 -  java.lang.IllegalArgumentException: object is not an instance of declaring class
    • 20393 - issues with com.actional.sql.LongWaitTimeout for Data Direct drivers
    • 20420 - Support for webMethods 9.6
    • 20425 - Support for CentraSite 9.6  (Requires running Actional on a 1.7 JVM.  See Notes section.)
    • 20434 - AMS config file corruption
    • 20436 - AI causing 100% CPU usage on a 16 core server
    • 20445 - BA: Unable to create Node icons in AMS using Actional SOAP API
    • 20687 - Transform fails on Multi-line Content-Type
    • 20761 - ClassCastException occurs when persisting legacy flows
    • 20762 - Transaction Lookup times out
    • 20766 - Alert Analyzer should allow drilling down to Transaction Details
    • 20808 - Errors generating sequence Map
    • 20931 - Alert Visualizer: Alert list toolbar with disabled buttons is confusing
    Interceptor
    • 20261 - start_wmb_interceptor.sh fails with error "Missing parameter for argument '2' "
    • 20299 - Glassfish interceptor reports wrong URL
    • 20344 - Glassfish interceptor fails for SOAP/JMS use cases
    Intermediary
    • 20178 - No confirmation page found while deleting service groups or applications pages in Actional Intermediary
    • 20285 - NullpointerException if a Access Point is added to a custom Service group using a file:// referenced WSDL
    • 20310 - AI WSDL import does not recognize xs:refdine
    • 20330 - XSL of an information filter  becomes invalid if edited in AI
    • 20336 - SOAP API does not expose task to create WADL/REST service group
    • 20374 - Wrong HTTP Response Codes Returned for Access Denied/Authentication Exceptions
    • 20377 - WSDL parsing fails if first Policy in WSDL is referencing another policy
    • 20381 - AI does not set Content-Length for POST REST requests that does not have a body
    • 20383 - Unable to finish REST Security Contract Wizard using custom plugin
    • 20403 - AI does not pass through simple JMS-to-JMS request and does not log any error
    • 20424 - AI not picking up published URLs from UDDI
    • 20694 - If more than one deployment thread is running exceptions are thrown while importing WSDLs using SOAP API
    Notes
    • Intermediary:   When AI using being used in standalone mode (using Jetty as the Application Server), the HTTP headers field name is reported with the same casing as the first request for all matching HTTP header field name on subsequent requests even if on the subsequent HTTP request headers field has different casing than the first request. Example: First request had a header called myheader. AI will report the HTTP header field name as myheader. Second request had a header MYHEADER. AI will report the HTTP header field name as myheader.
    • CentraSite 9.6: When configuring the plugin the location of the Centrasite redist directory must be specified. In CentraSite 9.6, that directory contains jars that are compiled against Java 1.7.  Therefore, in order to use the CentraSite 9.6 plugin, AMS must be running AMS on a 1.7 JVM. Running AMS 2013 in its default (1.6) environment will result in the following exception when attempting to configure the plugin: UI0016: Error: java.lang.UnsupportedClassVersionError: com/centrasite/jaxr/ConnectionFactoryImpl : Unsupported major.minor version 51.0 Running AMS on a 1.7 environment will allow to load the CentraSite classes.

    Issues resolved in Release 2013.0.0.5

     

    Management Server / Agent
    • 3227 - Request/Reply payload is being audited as well when using "on Request" Policy Group rule for auditing message field only
    • 20242 - "java.lang.IllegalStateException: Unread input" in the console logs
    • 20248 - NullpointerException after installing Actional Management Server 2013 HF3
    • 20253 - separate out disable rollup stat setting for hour from the other mega intervals (day, week, month, quarter, year) in settings.jsp
    • 20287 - Deploying any Actional war file in JBoss 5.1.2 (EAP) fails with 'java.lang.ExceptionInInitializerError'
    • 20294 - Configuring JMS Auditing Fails if AMS can not validate the JMS Config
    • 20212 - Support for CentraSite 9.0
    • 20274 - Support for CentraSite 9.5
    • 20237 - Support for webMethods 9.5
    • 20271 - Locale of Actional Server can cause publishing to CentraSite to fail
    • 20280 - NPE seen interceptor log in webMethods IS
    • 20281 - webMethods Integration Server instrumentation prints a warning
    • 20283 - Improper correlation of virtualized services in webMethods Mediator
    • 20290 - [SAG IS] incorrect SOAP over JMS correlations
    • 20291 - [SAG IS] Plugmaker warnings appear regarding JMSMessageConsumer hookpoints not found when running under SAG 8.0
    Intermediary
    • 20227 - Stackoverflow on request validation
    • 20258 - AI Application SOAP Header option adds multiple headers which cause error
    • 20308 - Wrong HTTP Response Codes Returned for Access Denied/Security Exceptions
    • 20327 - Some authentication exception messages contains catalog values holder (i.e.: {0}, {1}, etc...)

    Issues resolved in Release 2013.0.0.4

     

    Intermediary
    • 20229 - Allow Request message JMS transport to be used to send reply rather than Request AP transport

    Issues resolved in Release 2013.0.0.3

     

    Management Server / Agent
    • 20198 - Unable to define filter using a Oracle DB on /ui/ interface
    • 20217 - Actional Management Server deployment fails with missing dependencies

          In order to make the fix effective, The sequence of steps mentioned below should be followed
          * Select All or select some from Platform Configuration component.
          * Select All or select some for Policy Groups Component, if any policies required to be exported.
          * Select rest of components as per your requirement.
    Intermediary
    • 20214 - Errors while reducing the numbers of Sonic JMS durable subscriptions
    • 20228 - Error 405 when a AP WADL contains more than one variable element
    • 20230 - REST Operations only show HTTP method name
    Interceptor
    • 20204 - .net SDK causes w3wp.exe to spin with 100%CPU usage
    • 20213 - Partial uninstallation of BizTalk interceptor finished with errors

    Issues resolved in Release 2013.0.0.2

     

    Management Server / Agent
    • 20187 - SNMP MIBs does not match the trap data
    Intermediary
    • 20163 - To prevent the message loss (in case of an Intermediary failure) when used with Shared Subscriptions on the Access Points an enhancement is provided to have Durable Subscription wherein a support is added to have multiple durable subscriptions based on a listener index.
    • 20144 - When Actional Intermediary is gracefully stopped, then it will stops listening on all destinations. However, it waits for all the pending requests received over JMS to be processed or until all replies have timed out before continuing with the shutdown process.
    • 19740 - For AMS managing multiple AIs with the 'ALL MANAGED NODES' option, a new property 'SoapstationSettings.reportServiceNameAsServiceID' has been introduced to control how the service group ids are reported.When set to true, AI will report groupID derived from service group name instead of service group revision key id
    • 20187 - SNMP MIBs does not match the trap data
    • 20200 - AI Cannot create REST AccessPoint for which the operation name contains underscores (or anything other than alphanumeric characters)
    • 20201 - AI Cannot access any ServiceGroup WSDL/WADL after creating a REST AccessPoint

     

    Issues resolved in Release 2013.0.0.1

     

    Management Server / Agent
    • 5504 - Stabilizers show up for all nodes even if the policy is applied one on node.
    • 20007 - Cluster status not properly detected after one node failed/killed.
    • 20040 - SQL exceptions causing auditing to fail.
    • 20130 - OOM can occur in AMS when using ConfigProvisioning.
    Intermediary
    • 20109 -  AI Clusters need to persist the JMS Destinations and if applicable the SonicMQ Temporary Destination name in the database so any cluster member can return the AccessPoint Response.
    • 20120 - Changing "Content-Type" header to "Content-type" on reply triggers "Content is not allowed in prolog" error in AI.
    • 20122 - AI 2013 fails to connect to Sonic 2013 using ESB transport.
    • 20126 - The life cycle of plug-in interceptor should be explicit.
    • 20129 - Allow the JMS Transport to support SonicMQ Shared Subscriptions with multiple listeners for JMS Transport consumers. JMS transports have been enhanced to support Aurea Sonic's SonicMQ Shared Subscriptions feature.  Shared Subscriptions groups topic subscribers so that messages are delivered to the group, with each message consumed by only one member of the group. A new destination type was added to Actional Intermediary, called Shared Topic, which identifies the topic as one using Shared Subscriptions. When Shared Topic is selected, Actional Intermediary automatically adds a group name to the topic name and allows multiple listeners to be specified for the topic instead of restricting it to one.
    • 20161 - Operator (+ a custom role with Stabilizers permissons) cannot change the stabilizer state.
    • 20168 - Nullpointer exception on JMS layer after HF was applied
    Interceptor
    • 20110 - Unable to filter Webmethods event

     

    Top