Because it is not safe to iterate over a list_t or map_t container type while modifying it, these iterators have been modified to assert (or throw an exception) if accessed after the parent container has been modified. These will fail with a message saying that the iterator has been invalidated by modification of either a map or a list. Any code which now throws an exception will have been unsafe previously (even if it did not crash). The new check simply exposes the existing bug in the user's code. See also C++ data types.

If you are compiling either EPL or connectivity plug-ins in C++, and you build libraries that are used by multiple plug-ins and those libraries have an API using Apama's C++ data types, you may need to change how you compile your plug-ins. If you have multiple shared objects with such an API, you must ensure that all of the shared objects are compiled with the same service pack version of the Apama header files. This does not affect you if you are compiling independent plug-ins. For more details, see Compiling C++ plug-ins and Building plug-ins.