- **summary**: saImmOiImplementerSet returned ERR_LIB for campaign object DN
greater than 255. --> SMF: Implementer-names must be re-used.
- **Type**: enhancement --> defect
- **Milestone**: future --> 4.3.3
- **Comment**:
Changing this to a defect.
Implementer names are not discarded by the immsv. This is clearly
documented in both the IMMSV_PR.doc and the immsv README.
Thus using an obviously transient name such as the DN for a campaign
is a design error.
Every new campaign will add a new implementer-name that is only used
during the campaign and thereafter just wastes memory in the imm server.
Implementer-names are cleared at a cluster restart but that is not any
"solution".
The SMF design needs to be changed so that a re-usable implementername
is used, i.e. where the campaign-id is not part of the name.
Something like 'saSmfCampaign'
---
** [tickets:#1126] SMF: Implementer-names must be re-used.**
**Status:** unassigned
**Milestone:** 4.3.3
**Created:** Mon Sep 22, 2014 04:50 PM UTC by Hrishikesh
**Last Updated:** Wed Oct 01, 2014 01:44 PM UTC
**Owner:** nobody
changeset : 5697
Setup : 4 nodes cluster with SLES 64bit.
Problem:
========
Campaign object DN with more than 255 chars is created using immcfg.
Upon executing the campaign, after starting campaign thread,
saImmOiImplementerSet DN=safSmfCampaign=campaignroc..... , returned ERR_LIBRARY
saying Implementer name too long, size: 395 max:255.
With ticket #930, Longer DNs in SMF are supported, and Campaign object name is
of type SaNameT.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
