If you are using the unusual convention of type.method(...) to call a method, you will be passing an instance of type as the first parameter name. We have corrected an issue with the any.getActionParameterNames() method so that it now correctly returns self as the first parameter where there is no closure. This matches the behavior of the new any.getActionParameterTypes() method (see also EPL enhancements in 10.3.1).

Correlator and IAF processes using the --pidfile option now take an exclusive lock on the pidfile. This means that multiple components using the same pidfile will be prevented from starting up. See also Starting the correlator and IAF command-line options.

As of this version, the .NET Event Parser plug-in correctly interprets floating point separators on hosts that use a separator other than the period. Prior to Apama 10.3.1, the .NET Event Parser plug-in did not interpret Location events correctly. The issue occurred only with hosts set up to use a character other than the period (.) as the floating point separator. For example, if the local host was set up to use a comma as the floating point separator, then a Location([4.4,3.3,2.2,1.1]) was interpreted as Location([44,33,22,11]). Now this is correctly interpreted as Location([4.4,3.3,2.2,1.1]).