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
---------- Forwarded message ----------
The following list is a recap of the currently outstanding issues/questions regarding SAFplus 6.1 that have been submitted for support. The list is not in any specific order.
1) Log daemon crash: have seen safplus_logd crash with 2 separate signatures
2) Log assertion seen in the ce node log file: safplus_logd: clLogGms.c:303: clLogGmsInit: Assertion `val' failed.
3) Instantiation issue: instantiation timeouts that are only seen with 6.1 (same component as 5.0). which component it is varies, and how many components have instantiation issues varies ---- although it recovers by trying the instantiation twice, this issue causes major timing issue for us
4) What causes log messages of this type, and is it an issue? seen at least once on a switchover: [CE_Node2_2N_Su_Comp_Pipe] part of SU [CE_Node2_2N_Su] is already assigned active. Skipping reassignment for SU [CE_Node1_2N_Su]
5) Why is startup unloading, loading, and then again unloading TIPC?
Related to SAFplus since TIPC is used:
1) TIPC causing kernel panic disabling an unknown bearer (seen when shutting down ASP)
2) tipc-config –ls gives unknown link error rather than setting the tolerance for future links
---------- Forwarded message ---------- The following list is a recap of the currently outstanding issues/questions regarding SAFplus 6.1 that have been submitted for support. The list is not in any specific order. 1) Log daemon crash: have seen safplus_logd crash with 2 separate signatures
2) Log assertion seen in the ce node log file: safplus_logd: clLogGms.c:303: clLogGmsInit: Assertion `val' failed.
3) Instantiation issue: instantiation timeouts that are only seen with 6.1 (same component as 5.0). which component it is varies, and how many components have instantiation issues varies ---- although it recovers by trying the instantiation twice, this issue causes major timing issue for us
4) What causes log messages of this type, and is it an issue? seen at least once on a switchover: [CE_Node2_2N_Su_Comp_Pipe] part of SU [CE_Node2_2N_Su] is already assigned active. Skipping reassignment for SU [CE_Node1_2N_Su]
5) Why is startup unloading, loading, and then again unloading TIPC?
Related to SAFplus since TIPC is used: 1) TIPC causing kernel panic disabling an unknown bearer (seen when shutting down ASP)
2) tipc-config –ls gives unknown link error rather than setting the tolerance for future links
Thanks, Howard