Progress Apama Release Notes

Release: 4.3
Ports: All
Date: October 2010
------------------------------------------------------
Copyright (c) 2002-2010 Progress Software Corporation.
All rights reserved.
All use, reproduction, transfer, publication or disclosure is
prohibited except as expressly permitted in the applicable
licence agreement.
Apama 4.3 is one of three products that make up the Progress(c) Responsive
Process Management(tm) (RPM) Suite. The other two products are the Progress(c)
Actional(c) Management Server and the Progress(c) Savvion(c) BusinessManager.
Each product in the RPM Suite provides best-of-breed solutions in its
specialized functional sphere:
- Apama provides complex event processing on real time data flows.
- Actional Management Server provides visibility into a business' IT
infrastructure.
- Savvion BusinessManager provides complex business process management.
Together, they make it possible to monitor all aspects of a business and effect
changes in real time. On a business user's desktop, the manifestation of the
RPM Suite is the Progress(c) Control Tower(tm). The Progress Control Tower is a
unified portal for visualizing and managing a business' operations. The Control
Tower:
- Aggregates data in real time from the IT systems, the business processes, the
external conditions, and the other data sources that drive a business'
operations
- Presents aggregated data to the business user in a clean and unified screen
This increases the business user's effectiveness and creates conditions for
business users to be more responsive to changing conditions. A single portal
also makes it easier for business users to notice inefficiencies in a business
and make process improvements.
New features added as part of the Apama 4.3 release allow the three products
to share information and alter the progression of business processes in
response to changes as they happen. Together, the Control Tower and the features
that combine Apama, Actional, and Savvion into the RPM suite make your business
more operationally responsive.
CONTENTS
========
1. Known Issues in 4.3
2. Known Issues in previous releases still relevant in 4.3
3. Trademark Notice
4. Proprietary Information Statement
For a list of supported platforms, platform-specific information and
installation information, see "Installing Apama" (installing_apama.pdf in the
same directory as this file). Adobe Acrobat reader version 8.0 or greater is
required to view the included PDF documentation.
For information about migrating your application to Apama Release 4.3, download
the Apama Migration Guide from the Progress Electronic Software Download (ESD)
site.
----------------------
1. Known issues in 4.3
----------------------
a.) Installation
----------------
Issue 15822 - (Environment dependent) Silent mode installation on Unix
platforms may terminate without X-Server running
======================================================
When installing Apama in silent or console mode, if your environment has a
DISPLAY variable defined but no valid X-Server running, the installer might
abort. To avoid this, start an X-Server or temporarily unset the DISPLAY
variable.
Issue 16244 - OEM Installer: Uninstall happens on first click of remove -
no warning given.
=====================================================
To uninstall an OEM installation of Apama 4.3, run the uninstall executable in
the [INSTALL_LOCATION]/uninstall directory. The removal of the software occurs
immediately once the program has been executed.
Issue 16379 - Solaris installer: "install.bin: !: not found" message
=============================================================
When running the install.bin executable on a Solaris machine, the console
displays an "install.bin: !: not found" message that appears to be an error.
However, the installation will continue and you can ignore the message.
b.) Apama Studio
Issue 13472 - Apama Doc fails to generate documentation if project build
not complete
=============================================================
Exporting Apama Doc will fail for a project if the project has not been
built or a build is underway. Ensure that a project build is complete
before exporting Apama Doc.
Issue 15482 - EPL editor fails to flag as invalid circular dependencies
created with the "using" keyword
==============================================================
The EPL editor fails to flag as invalid circular dependencies created with
the "using" keyword. For example having the files a.mon and b.mon where
a.mon references b.mon and b.mon references a.mon with the using keyword
will not be detected as invalid. The error will only be indicated when
the project is run.
Issue 16325 - Back button on Progress Apama Web Resources page may require
double click
==============================================================
Selecting Web Resources from the Welcome screen displays a link to Progress
Apama Web Resources. Selecting this link will display the web page for
Progress Apama support. When this page is displayed clicking on the back
arrow in the toolbar may not perform the back operation. If this occurs,
double clicking on the back arrow will navigate to the previous page.
Issue 16331 - EPL editor fails to flag as invalid forward references
in .mon files
=============================================================
The EPL editor fails to flag as invalid forward references in .mon files.
For example, the following EPL code contains a forward reference. The
invalid syntax is not detected until the project is run.
monitor M {
action onload {
E e := new E;
}
}
event E {
integer i;
}
Issue 16458 - Apama 4.2 projects with Apama Java Nature do not rebuild
automatically when opened with Apama Studio 4.3
=============================================================
Existing 4.2 projects with the Apama Java Nature must be manually rebuilt when
first opened with Apama Studio 4.3. This can be done by selecting "Clean..."
from the "Project" menu. Once rebuilt, projects will automatically build as
required by changes to a project.
Issue 16506 - Re-injecting a scenario may cause the scenario editor to
become unresponsive
=============================================================
When two projects are open in a workspace and a scenario is opened for edit
from the first project, running the second project and then re-injecting a
scenario from the second project can cause the open scenario editor to
become unresponsive. The only recourse is to stop the running project
and close the editor.
c.) Event Processing Language (EPL) (The new name for MonitorScript.)
Issue 15647 - The toString() representations of event types declared
inside monitors has changed
====================================================================
Event types that are declared internal to a monitor now have fully-qualified
names that include the fully-qualified name of the enclosing monitor in their
toString() output. For example, an event "E" defined inside a monitor "M"
would previously have been represented as a string of the form "E(...)" but
is now represented as "M.E(...)"."
d.) Dashboards
Issue 15037 - Redeploy of dashboard does not delete cached files
================================================================
If dashboard files were removed between two display server deployments
(that is, deploy foo.rtv, then delete foo.rtv from project and re-deploy),
the deleted dashboard files will still be available for the re-deployed
client. To workaround this, delete the reference directory:
<APAMA_WORK>/dashboards/<deployed_dashboard>
manually before re-deploying.
Issue 15433 - Flash wrapper not available
=========================================
The Dashboard Builder does not support Fx Objects on 64-bit platforms when
using a 64 bit JVM. These objects utilize the Adobe Flash player, which
requires a 32-bit executable on Windows. To create dashboards on 64-bit
platforms that use Fx Objects you must run the Dashboard Builder with a
32-bit JVM.
Issue 15802 - Dashboard SQL attachments cannot filter on IEEE specials
values such as NaN
================================================================
Dashboard Apama SQL attachments do not support filtering by NaN, Infinity, or
-Infinity. For example the following query is not supported:
SELECT value FROM "default.specialVals" WHERE "value" != 'NaN'
Issue 15910 - Memory leak for long running dashboard containing FX objects
==============================================================
The FX objects exhibit a small memory leak that can impact long running
dashboards. Refreshing the browser page will cause the FX object to refresh and
free any leaked memory. This may need to be done periodically.
Issue 16039 - Filters containing quotes are broken when running with
in-memory database
================================================================
Attachments where the filter value is a string containing a quote do not work
in enhanced query mode. In enhanced query mode, attachment filters are turned
into SQL WHERE clauses. When using enhanced query mode and having the need to
filter by values containing quotes you need to escape each quote with a quote.
Double quotes do not need to be escaped.
Issue 16060 - Flash objects do not display in Dashboard builder without
IE flash plug-in installed
=================================================================
Adobe Flash Player ActiveX version 9 or higher is required for using Flex
applications in the Apama Dashboard Builder. This version of the Adobe
Flash Player can only be installed using the Internet Explorer.
Issue 16156 - Harmless "Failed create command: GRANT SELECT ON in
dashboard log files when using enhanced queries
=================================================================
During scenario or data view instance discovery, the dashboard servers,
builder, or viewer might log the exception "Failed create command GRANT
SELECT ON <some table> TO public". This is due to an SQLException.
You can ignore this exception. The table will have been created.
Issue 16268 - FX objects may fail to render after rapid drilldowns
==================================================================
The dashboard FX objects may fail to render after multiple rapid drilldowns.
Refreshing the browser page will correct the problem causing the object to
render.
Issue 16382 - Panels deployments can save header when disconnected from
webserver
==================================================================
If panels.ini is used for display server dashboard, then an invalid http session
(for example, re-start tomcat) will result in a sessionExpired page inside the
main frame of the dashboard. Clicking on the login link on that page to re-login
will *not* clear the previously displaying tabs/trees. Refreshing the web
browser or re-visiting the dashboard URL will fix the problem.
Issue 16353 - Problems with FX LineTrendChart and LineChart objects
===================================================================
Setting the series_1_Name property does not result in the series name being
displayed.
Issue 16394 - Problems with FX RadarChart object
================================================
1. Setting labelDisplayType and slantLabels have no effect on the label.
2. x-axis label (time) is wrong when there is more than 1 series, and shows
24:00:00 (for default time format) and not the current time.
3. Value displayed is wrong for series 2 onwards, and always shows 0.
Issue 16396 - Problems with FX Cylinder object
==============================================
When the current value is zero, it is not displayed at the bottom of the widget.
Other current values (apart from zero) display properly at the bottom of the
cylinder.
Issue 16400 - DisplayServer deployed dashboard containing panels may fail to
update in Firefox 3.6.10
=====================================================================
A dashboard using tabs in a panels configuration file may fail to update
correctly in Firefox 3.6.10 in display server deployments. Tables inside
tabbed panels may not update when tabs are changed. This problem does not
occur in earlier version of Firefox or Internet Explorer.
Issue 16419 - Problems with FX Angular Widget and FX Angular Half Widget
===================================================================
1. When the current value is zero, it is not displayed in the middle of the
widget. Other current values (apart from zero) are displayed properly.
2. The valueVeryHighAlarm property is not used and is missing an associated
color.
3. The valueMin property is not used.
Issue 16463 - FX trend charts might not clear old trend data on drilldown
===================================================================
When using FX trend charts data might not be cleared on drilldown if the
timestamp on the newly selected scenario or dataview instance is in the
same range as the previously selected instance. Refresh the page to correct
the errant display.
e.) Correlator
Issue 13874 - Parsing events such as D({a:"alpha"a:"aardvark"}) leaks memory
===================================================================
Parsing dictionaries with duplicate keys such as {"a":"alpha" "b":"beta"
"a":"aardvark"} will now raise an error (the event will be dropped if being
received externally). This previously was allowed with a warning."
Issue 15472 - Remove deprecated Time Format plug-in methods and change the API
of LoggingManager
==================================================================
In Apama 4.2, the Time Format plug-in methods using percent-escaped strings
were deprecated and replaced with ICU-style strings to match the time-parsing
methods. In 4.3.0 these old methods have been removed and EPL code using those
methods will fail to inject. EPL code must be rewritten to use the newer,
more stable and more powerful methods on the TimeFormatPlugin.
Due to this Time Format plug-in change, the API of the LoggingManager also
changes in Apama 4.3. Use of the LoggingManager in 4.2 will have provoked
warning messages about using the deprecated TimeFormatPlugin API. The
LoggingManager uses a SetLogRotating control event, the first member of which
is the template filename to use to create log files.
The old format for the filename was to use the deprecated percent-escaped
strings in the filename, for example:
route SetLogRotating(correlator_%d%M%Y.log",...
In 4.3, the new ICU-based specifiers must be used and in addition any
characters that should be interpreted as a time-specifier must be escaped
with a single quote. For example:
route SetLogRotating("correlator_'ddMMyyyy'.log",...
As a result of this change, there is also a change to Event Modeler. See
Issue 15472 in the Event Modeler section later in this file.
Issue 15529 - getTypes -xmlRecursive on recursive types hangs the correlator
====================================================================
The "-xmlRecursive" argument to the "getTypes" engine management request has
been withdrawn.
Issue 16556 - correlator plug-in cpp sample on SUSE 11 (32-bit and 64-bit)
===================================================================
The simple_plugin.cpp sample in the <apama_install_dir>/samples/
correlator_plugin/cpp directory fails to build and generates the following
errors:
simple_plugin.cpp:55: error: 'strlen' was not declared in this scope
simple_plugin.cpp:56: error: 'strcpy' was not declared in this scope
To fix this, add the following statement to the top of the simple_plugin.cpp
file:
#include <cstring>
f.) Adapters
Issue 4305 - Support for NaN in Apama ADBC Adapter
==================================================
Support for storing and retrieving a NaN value is not supported with all
databases. The following databases have been tested:
- MS SQL Server 2005/2008 and MySQL 5.1 - No support. Database does not support
NaN values.
- DB2 9.5 - Full support for ODBC, not supported for JDBC.
- Oracle 10/11 - Full support for JDBC. Partial for ODBC, only storing of NaN
values is supported by ADBC, retrieval is not supported.
Issue 15257 - No Indication or error message when the adapter installation
does not install one of the files that has the date greater than the date
of the file to be installed.
==============================================================
Modified Apama Adapter Files Are Not Updated
If you need to modify any Apama adapter files, for example a .mon file, you
should back it up prior to installing an update. The update installer does not
overwrite a modified file.
Issue 16197 - JMS unsubscription acknowledgement clarification
==============================================================
The documentation for the JMS unsubscription notification events is potentially
misleading. For *durable topic* unsubscriptions, the UnsubscribeAcknowledgment
event will be sent *after* the JMS consumer identified in the request has been
*successfully closed*. However, for all other topic and queue unsubscription
requests, the UnsubscribeAcknowledgment event is merely a notification that the
*request* has been received, and this event is sent out immediately, before the
JMS consumer has actually been closed. A new event called
UnsubscribeCloseAcknowledgment has been added, which will only be sent after the
consumer specified in the unsubscription request has been successfully closed,
for all destination types. Customers are encouraged to use this new event from
now on. If multiple subscriptions have been made to the same destination then
the UnsubscribeCloseAcknowledgment event is only sent when the consumer is
actually closed, after the last unsubscription has been processed.
g.) Event Modeler
Issue 15472 - Event Modeler - change of functions and blocks
============================================================
The change described here is due to the Time Format plug-in change described
above in the Correlator section, Issue 15472 - Remove deprecated Time Format
plug-in methods and change the API of LoggingManager.
The old deprecated FORMAT_TIME and GET_CURRENT_TIME_FORMATTED methods in
the DateAndTime functions
in Event Modeler will no longer work. New versions that
use the new format string have been available since 4.2 and the old ones marked
as deprecated. Any code using the old versions will fail to inject to a 4.3 correlator and must be
upgraded to use the new functions. The old versions will remain in 4.3 to allow easy upgrades but
will be removed in a subsequent release.
Also due to the Time Format plug-in change above, the existing HistoryLogger
block will no longer work. New versions that use the new format string are
available in 4.3 and can be upgraded to in Event Modeler. Use of the old block
will be prominently marked in Event Modeler.
----------------------------------------------------------
2. Known issues in previous releases still relevant in 4.3
----------------------------------------------------------
a.) Installation
----------------
Issue 13141 (since 4.2) - Administrator privileges should be used on
Windows Server 2008R2 or Windows 7 in order to use Apama
==================================================================
When running Apama on Windows Server 2008R2 and Windows 7, User Account
Control (UAC) might cause errors. To avoid these errors, select "Run as
administrator" using the right mouse button when you install or run Apama.
The account must have administrator privileges to run as administrator.
b.) Apama Studio
Issue 14607 (4.2.2) Dynamic help not available for Apama Studio plug-ins
installed into Eclipse 3.5.
==================================================================
Dynamic help is not available for Apama Studio plug-ins when added to an
Eclipse 3.5 installation using the integrateApama.bat script.
Issue 14728 (4.2.2) Data Player single step timeout on queries taking
more than 2 minutes to return an event.
==================================================================
The Apama Studio Data Player step control will timeout on queries that
take more the 2 minutes to return an event. This will leave the play and
step buttons erroneously disabled. Use the play control to start queries
that will take more than 2 minutes to return an event.
Issue 10842 (since 4.2) - Profiler Method Invocations tab should be ignored
==================================================================
The Method Invocations tab in the Apama Studio MonitorScript Profiler does
not apply and should be ignored.
Issue 11027 (since 4.2) - Using multiple main windows causes memory leaks
=================================================================
Apama Studio leaks memory when multiple, separate main windows are used.
Multiple main windows can be created by selecting New Window from the
Window menu. This is typically only done when working on a system with
multiple displays. If you use multiple main windows you may need to restart
Apama Studio after several hours of use.
Issue 11058 (since 4.2) - Invalid name for lib files in Java-enabled project
===================================================================
For projects with Java support enabled, the Project View may periodically
display, "Error: no label provider for
org.eclipse.jdt.internal.ui.packageview.ClassPathContainer" in place of the
entries "JRE System Library" and "ApamaJavaLibrary". This can be corrected
by refreshing the Project View with F5 or right clicking on the project and
selecting Refresh from the popup menu.
Issue 12421 (since 4.2) - Refresh during profiling session can cause
NullPointerException
====================================================================
During an active profiling session, if you select Refresh from the Profiling
Monitor context menu and check the option "Refresh contents from file
system", a NullPointerException may occur when the contents have not been
saved. This behavior is not specific to the Studio profiler. It is also
observed with the standard Eclipse Java profiler.
Issue 12567 (since 4.2) - NullPointerException may occur during profiling
session
===================================================================
During an active profiling session, if you perform all the following steps,
a NullPointerException may occur:
1. Right click on Profiling agent and select Save.
2. Click on the Save button in the resulting message dialog.
3. Go to the Navigator view and expand the ProfileProject node.
4. Switch to Apama Developer Perspective.
5. Open each file under Profile Project using the Default editor
(double-click or use Open With...).
6. Close all editors.
Issue 12786 (since 4.2) - Running projects are not stopped if deleted
=====================================================================
Apama Studio does not stop a running project when the project is deleted.
If you delete the project while it is running, you may see errors when
you access the application. You should ensure a project is stopped before
you delete it.
Issue 12793 (since 4.2) - Some profiler column data not part of saved
session
=====================================================================
In the Apama Studio profiler, the data in the Idle, Non Idle, Runnable,
Blocked, and Plug-in columns is not saved when a profiler session is saved.
These values will not be available if the profiling session is re-opened.
Issue 12838 (since 4.2) - Dashboard deployment tool will not resign .jar
files
====================================================================
The dashboard deployment utility in Apama Studio will not resign jar files
that are already signed. If you add jar files to your dashboard deployment
that are already signed, you may see errors when you access the deployed
dashboards. When you use the dashboard deployment utility, sign all jars or
none of them (in which case they all must be signed already), or else(if
you have a mix of signed and unsigned jars) sign with the same certificate
that was used for the jars that have already been signed. To use the
deployment utility to sign jars that have been previously signed, you must
first remove their signatures.
Issue 13030 (since 4.2) - Text selection in tutorial cheat sheets behaves
incorrectly
=====================================================================
Text selection in Apama Studio tutorial cheat sheets behaves oddly when
the cheat sheet window is not scrolled to the top. This can make it
difficult to select text to cut and paste when running a tutorial. This
is a defect in the Eclipse cheat sheet facility.
Issue 13132 (since 4.2) - Apama Studio block editor allows text to be
entered after closing "</block>" element
=====================================================================
The Apama Studio block editor incorrectly allows code to be entered after
the closing </block> element in a block (.bdf) file. This is invalid
and should not be allowed. Opening a block with such an error with the
Apama Studio block editor generates an exception.
Issue 6713 (since 4.0) - Indentation broken in source edit of blocks
====================================================================
The fix indentation function is broken when editing Block code.
This happens when the selection includes the first line of a user
editable section.
Workaround: Indent the first line manually and then highlight the rest
of the indentation block and use the correct indentation functionality.
Issue 7138 (4.0) - Once all contents in user editable regions deleted in
the source editor for Blocks it is not possible to enter more.
====================================================================
In the source editor for Blocks, when all the content in the user editable
regions is deleted, you cannot enter any new content. To workaround this
issue, edit in text editor.
Issue 7210 (since 4.0) - Can't use Block Editor in multi window mode
===================================================================
The block editor is not synchronizing changes between metadata editor
and source editor if they were open in different editor windows.
If the same block is open in multiple editors and the source is changed
in one editor and the metadata in the other one which is then saved the
changes made in the first editor are lost.
Issue 7640 (since 4.0) - Apama Studio Welcome Page does not render CSS or PNG
transparency if your default browser is IE6
===================================================================
Apama Studio welcome pages use the installed Internet Explorer for rendering,
and these pages make use of HTML features that are not supported on old
browsers such as IE 6. Although the appearance of the welcome pages should
downgrade gracefully with old browsers, please note that for the best quality
experience IE7 or greater should be installed.

Issue 7873 (since 4.0) - Renaming a block in Apama Studio
=========================================================
Block renaming in Apama Studio is not fully supported. If you rename a block
in Apama Studio, you must manually edit the block's .bdf file to synchronize
between the filename and the block metadata.
Issue 7894 (since 4.0) - Convert project from native codepage to UTF-8
invalidates Internationalization (I18N) chars in EPL (MonitorScript)
===========================================================
Changing the file encoding to and from UTF-8 might cause file corruption
in comments and string literals. To work around this, ensure that
the desired encoding is set before adding content to the file.
Issue 8052 (since 4.0) - File list export excludes .sdf files
=============================================================
Apama Studio includes a Project Initialization File List export wizard
that creates a text file containing all files on a project's build path,
which can then be imported into EMM. At present this list does not
include any scenario (sdf) files on the build path. Scenarios should
therefore be exported to EPL manually (using Event Modeler),
and the EPL files added directly to EMM's initialization list
once the Apama Studio Initialization File has been imported.

Issue 8305 (since 4.0) - Superfluous/erroneous "Save Changes?" dialog
in Edit Configuration and Launch
============================================================
When the launch configuration dialog is closed without making any
changes, the dialog still prompts the user to save changes. The
correlator initialization list is automatically reconciled against
the current state of the project. This causes the unexpected
"Save Change" dialog.
Issue 8419 (since 4.0) - No JMON support in project parsing
===========================================================
JMON event definitions are not included in the project build.
To successfully build the project, create these corresponding event
definitions in EPL.
Issue 8688 (since 4.0) - Default location of apama-work directory might not be
suitable for PCs with multiple Apama users
=========================================================
The default location of apama-work is not a shared directory. For example, on
32-bit Windows systems it is:
C:\Documents and Settings\[USER]\apama-work
If multiple users share a single PC, the default location of the
apama-work directory might not be suitable since all users would share
the apama-work directory of the end-user who installed Apama.
Therefore, if you plan to share a single installation, Progress Software
recommends that you set the apama-work directory to a shared directory. For
example, on 32-bit Windows systems you might set it to:
C:\Documents and Settings\All Users
Issue 8810 (since 4.0) - Connecting correlators together
========================================================
Apama Studio provides basic support for launch configurations containing
multiple correlators, however there is currently no dialog to configure
connections between the correlators, so that one correlator can receive
events emitted by another. The best way to do this is to add
engine_connect as an External Process on the Components tab of the
launch configuration, specifying the ports (and if necessary the hosts)
of the components to be connected, for example:
${apama_home}/bin/engine_connect --sourcehost localhost
--sourceport 15903 --targethost localhost --targetport 15904
--channel my_event_channel_name --persistent --verbose
c.) Correlator
Issue 8753 (since 4.0) - Avoid time going backwards (i.e., virtual machines)
=========================================================
The correlator requires that the system's clock never goes backwards and flows
reasonably evenly (less than 1 second of jitter). In particular, some virtual
machine environments can exhibit this behavior. The behavior of EPL
timers is undefined in this case, and in extreme cases, time jumping may
trigger timeouts on communication channels, resulting in components being
disconnected from clients. We recommend the use of NTP on UNIX.
d.) Dashboards
Issue 4929 (4.2.2) - Extension of ini files for GUI tool configuration
changed to .l4j.ini.
===================================================================
The launch4j version used to wrap Apama GUI tools as Windows executables
has been upgraded. As part of this change the ini files used to configure
GUI applications will now have a new extension -- .l4j.ini. For example,
the ini file for dashboard_builder.exe is now dashboard_builder.l4j.ini.
Existing .ini files will be renamed to the new extension during the
installation of Apama 4.2.2.
Issue 14332 (4.2.2) - Apama commands in display server with large amounts
of string data may fail.
===================================================================
Executing Apama commands in display server deployments with large amounts
of string data may fail if the resulting HTTP GET request exceeds the
maximum allowed string length.
Issue 14533 (4.2.2) - WebStart deployments not supported on Progress
Control Tower.
===================================================================
Apama dashboards cannot be deployed to the Progress Control Tower as
Java webstart applications. When using the Progress Control Tower
Apama dashboards should be deployed as either Java applets or display
server.

Issue 14534: (4.2.2) - Applet and WebStart deployment not supported in
WebSphere 1.6.0.23
===================================================================
Apama dashboards cannot be deployed as applets or WebStart to WebSphere
1.6.0.23. This impacts deployments with the Progress Control Tower, which
is currently certified with only WebSphere 1.6.0.23. It is a WebSphere
defect that is addressed in WebSphere 1.6.0.27.
Issue 14569 (4.2.2) - Custom window title from Dashboard Builder options
not supported.
===================================================================
Setting window titles in the Dashboard Builder using "Custom Window
Title" in the Tools -> Options -> General tab is not supported. Window
titles can be set on the command line used to invoke the dashboard viewer.
Issue 14666 (4.2.2) - Cannot log in to Tomcat with I18N usernames or
passwords.
===================================================================
Apama's login servlet for Tomcat does not support I18N usernames or
passwords.
Issue 14692 (4.2.2) - Composite grid object does not properly handle
rtv files that have off canvas objects.
===================================================================
Dashboards that contain Composite Grid objects that display rtv files
with "off canvas" objects will exhibit errant scrolling behavior
when deployed to the Display Server. The "off canvas" objects will
sometimes display in the Composite Grid. Any rtv displayed in the
Composite Grid object should not include any "off canvas" objects. All
objects should reside within the visible boundaries of the dashboard.
Issue 14726 (4.2.2) - Improperly defined JDBC connection causes CPU spike
in SQL server when using Dashboard Builder.
===================================================================
Dashboards using the SQL datasource with invalid JDBC connection
parameters can sometimes cause high CPU usage due to numerous failed
JDBC connection attempts to the SQL Server. This issue can occur if an
invalid JDBC password is specified and the Dashboard Builder SQL option
"Get Tables and Columns" is enabled.
Issue 14866 (4.2.2) - Dashboard deployment names cannot contain spaces with
Progress Control Tower
===================================================================
When using an alias such as ${apama} to deploy dashboards for use with the
Progress Control Tower you cannot use spaces in the "Deploy name".
Dashboards with spaces in their deploy name will fail to appear in the
Progress Control Tower. Instead, specify a direct URL for the target
location.
Issue 10238 (since 4.1) - Dashboard deployed with webstart/applet
==================================================================
Dashboards deployed via Java applets have problems with .rtv files whose
names contain spaces. To deploy a dashboard use Java WebStart if you
want to include spaces in the names of any .rtv files. Or, if you are
using an applet, do not include spaces in the names of any .rtv files.
Issue 3844 (since 4.0) - Dashboard truncates paths to the first space
=====================================================================
When using the XML data source, the Dashboard Builder incorrectly truncates
the path name of XML files containing spaces. When using an XML data source,
do not use absolute path names containing spaces.
Issue 4852 (since 4.0) - Delete All with many instances blocks UI
===========================================================
Using the Dashboard Builder's "Delete All" command to delete large numbers
of scenario instances can make the dashboard user interface appear
blocked. This is because control is not returned to the user interface until
the "Delete All" operation has completed.
e.) Event Modeler
Issue 7325 (since 4.0) - Changing state while editing rule name
===============================================================
If you click on a state to change the current state while you are
editing a rule name, Event Modeler reverts to the saved rule name
instead of automatically committing the edited name. Always press enter
or tab after a rule name change for that change to take effect.
f.) Continuous Availability
Issue 8696 (since 4.0) - Avoid overflowing a DB when making very quick
changes to a large set of subscribed channels
===================================================================
The merger component of the Apama Continuous Availability system
persists the channels that clients subscribe to and change. Due to the
channel change mechanism, very quick changes to a large set of
subscribed channels may overflow the database. Connecting a scenario
service client (Dashboard Builder, Apama Studio or a custom
client) is particularly prone to this situation.
To avoid this, provide a larger value for the size of the database when
it is created; the default is 256kB. For example, for 10MB, you would
pass -XdbStringSize 10240 to the merger when it is started with the
--clearDB option.
g.) ADBC Adapter
Issue 12631 (since 4.2) - Empty strings improperly stored for some data
sources
===================================================================
The ADBC adapter does not properly store empty strings for some data
sources. For some data sources, empty strings are stored as null values.
This can affect queries with selection criteria that involve empty
strings. For example, select * from table where field = "" does not match
rows in which field is stored as a null value.
Issue 12823 (since 4.2) - ADBC timed auto-commits must be used only with
database drivers that support concurrency
====================================================================
Use the ADBC adapter option for timed auto-commits only with database
drivers that support concurrency. If you use the adapter with database
drivers that do not support concurrency, you may see errors resulting
from multiple database operations occurring in parallel (typically insert
and commit operations).
h.) IAF
Issue 8461 (since 4.0.1) - IAF does not warn if an invalid file is given
to the logging configuration
====================================================================
The IAF aborts startup if it cannot write to the log file you specify on the
command line or in the IAF configuration file. If the IAF is running and you
invoke the iaf_client --reload operation the IAF tries to use the log file
that you specify in the command line or in the updated configuration file.
If the IAF cannot open that file, it continues to use the log file it was
using before the reload operation. If the IAF can no longer use that log
file, the IAF logs to stderr.
i.) Miscellaneous
Issue 9746 (since 4.2) - Java-enabled correlator and IAF sometimes require
explicit reduction of maximum heap size
=====================================================================
This release includes the latest update of Java 6: 1.6.0u18, which
contains a fix for sun bug #6629887
(see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6629887). Due to
this fix, the default maximum heap size is set purely as a function of
available memory. If a Java-enabled correlator or IAF is being run with
more restrictive resource limits than available memory, this may cause it
to fail because the JVM cannot reserve a large enough heap. In this case,
you should explicitly reduce the maximum heap size to below the heap limit
on the process by passing the -Xmx argument to the JVM. In the correlator
this can be specified on the command line with -J (for example, -J -Xmx1g).
In the IAF this is set in the configuration file (for example,
<jvm-option>-Xmx512M</jvm-option>).
--------------------
3. Trademark Notice
--------------------
All Progress Apama brands and product names are trademarks or registered
trademarks of Progress Software Corporation or one of its affiliates or
subsidiaries. Other brands and product names may be trademarks or
registered trademarks of their respective owners. No license is granted
to reproduce or use any such brand, product name or trademark except as
expressly in the applicable license agreement.
-------------------------------------
4. Proprietary Information Statement
-------------------------------------
Progress Software Corporation considers information included in this software
to be Confidential Information. Your access and use of this Confidential
Information is subject to the terms and conditions of the software license
agreement, which has been executed and with which you agree to comply.
Accordingly, you may not disclose or disseminate any such Confidential
Information except as expressly permitted under such license agreement.