Known Issues for Event Stream Processor Server

Learn about known issues and apply workarounds for the Server.

Server Issues
CR# Description
671971

By default, the RSA login uses the "SHA1withRSA" signature algorithm and the "MD5" digest algorithm. If you change the signature and digester methods in the cluster configuration, make the same changes to the SIGN_ALGORITHM and DIGEST_ALGORITHM environment variables.

For example, values for the SIGN_ALGORITHM environment variable are "SHA1withRSA" (default), "MD5withRSA", and "SHA1withDSA" (Java only). Possible values for the DIGEST_ALGORITHM environment variable are "MD5" (default) and "SHA1".

674280

Avoid using retention with input windows that use a log store. While the compiler does not flag this as an error, the retention policy on input windows that use a log store may not work as expected after recovery.

674786

In the case of the ESP Server crashing, if you have a join-based window using a log store, one source window using a log store, and another source window using a memory store and being derived from a window using a log store, the data in the join window is recovered up to the crash, but new records uploaded to the ESP Server do not get joined. When all the source windows use a log store, the same records that are uploaded to the ESP Server get joined.

744905

The compiler crashes when the for loops iterator is inside of a switch statement. The error is caused by the switch statement being compiled twice. Each compilation adds the for loops iterator and counter twice to the list of local registers. The first compilation is done only to determine characteristics of the compilation without generating bytecode; a copy of the compile state is used to determine characteristics and is then destroyed.