Middleware that provides libraries, GUI, and code generator to design multi-node (clustered) applications that are highly available, redundant, and scalable. Provides sub-second node and application fault detection and failover, and useful application libraries including distributed hash tables (checkpoint), event, logging, and communications. Implements SA-Forum APIs where applicable. Used anywhere reliability is a must -- like telecom, wireless, defense and enterprise computing. Download stable release with installer from: ftp.openclovis.com
In the file safplus_run there is a line saying:
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/lib:/usr/local/lib:${ASP_DIR}/lib:${ASP_DIR}/lib/openhpi
The problem is that if one of the libraries reside both in $ASP_DIR/lib and in /usr/lib (for example: libsqlite3).
Then during runtime the library is the one from /usr/lib and during link time it was taken from ASP_LIB.
These libraries may be different.
It happened in our environment and in the log we got the following message:
LOG.DBA.INI.00026 : WARN) SQLite was compiled with version [3006007], but dynamically loaded library is different: version [3007009]. You may have 2 versions of sqlite installed in different directories (for example, /usr/lib, /usr/local/lib), or have different versions installed in the build machine vs. this machine. This issue may cause runtime instability.
In the file safplus_run there is a line saying: export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/lib:/usr/local/lib:${ASP_DIR}/lib:${ASP_DIR}/lib/openhpi
The problem is that if one of the libraries reside both in $ASP_DIR/lib and in /usr/lib (for example: libsqlite3). Then during runtime the library is the one from /usr/lib and during link time it was taken from ASP_LIB. These libraries may be different.
It happened in our environment and in the log we got the following message: LOG.DBA.INI.00026 : WARN) SQLite was compiled with version [3006007], but dynamically loaded library is different: version [3007009]. You may have 2 versions of sqlite installed in different directories (for example, /usr/lib, /usr/local/lib), or have different versions installed in the build machine vs. this machine. This issue may cause runtime instability.