osaf/services/saf/immsv/immloadd/imm_loader.cc | 21 ++---
1 files changed, 14 insertions(+), 7 deletions(-)
The sync retry time was changed from 150msec to the huge value of 2 seconds
in ticket #851 (OpenSAF 4.5). This large value may have been apropriate
for optimizing some
Summary: IMM: Sync-retry reverted back to milliseconds with increase on retries
[#1188]
Review request for Trac Ticket(s): 1188
Peer Reviewer(s): Neel; (Mahesh)
Pull request to:
Affected branch(es): 4.5; default(4.6)
Development branch:
Impacted area
Summary: imm: fix return code in admin operation when return params contain
valid extended name [#1189]
Review request for Trac Ticket(s): 1189
Peer Reviewer(s): Neelakanta
Pull request to: Zoran
Affected branch(es): opensaf-4.5.x, default(4.6)
Development branch: default(4.6)
osaf/libs/agents/saf/imma/imma_om_api.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
The patch solves a bug in admin operation when return parameters contain valid
extended name.
diff --git a/osaf/libs/agents/saf/imma/imma_om_api.c
b/osaf/libs/agents/saf/imma/imma_om_api.c
---
Hi Guys,
I'm chasing an issue with N+M, and before I dig deeper to fix it I
wanted to see if any of you know about it.
Here's what I do:
1. si-swap of OpenSAF-2N controller
2. AMF node lock of now standby controller
This (now OpenSAF standby) controller has an active
Hi Anders Bj,
I changed of 2 second is required to address following issue, as a part
of TIPC multicast following issue was observed to address that i did the
change:
With TIPC multicast enabled, When A node sync is in-progress , the sync
message are being send in very high number/frequency
