- **status**: review --> fixed
- **Comment**:

[staging:132354]
[staging:ed89d1]
[staging:8809f1]
[staging:bb5b50]

changeset:   5914:bb5b506c020a
tag:         tip
parent:      5910:3727a61f9dd3
user:        Neelakanta Reddy <[email protected]>
date:        Mon Sep 22 19:15:38 2014 +0530
summary:     imm:corrected trace log in setImplementer[#1084]

changeset:   5913:8809f1cfd91b
branch:      opensaf-4.5.x
parent:      5909:82930953c202
user:        Neelakanta Reddy <[email protected]>
date:        Mon Sep 22 19:15:38 2014 +0530
summary:     imm:corrected trace log in setImplementer[#1084]

changeset:   5912:ed89d16a0215
branch:      opensaf-4.4.x
parent:      5908:6f48d26a98a0
user:        Neelakanta Reddy <[email protected]>
date:        Mon Sep 22 19:15:38 2014 +0530
summary:     imm:corrected trace log in setImplementer[#1084]

changeset:   5911:13235416cd60
branch:      opensaf-4.3.x
parent:      5907:6c337679a66e
user:        Neelakanta Reddy <[email protected]>
date:        Mon Sep 22 19:15:38 2014 +0530
summary:     imm:corrected trace log in setImplementer[#1084]





---

** [tickets:#1084] imm: wrong trace log in setImplementer**

**Status:** fixed
**Milestone:** 4.3.3
**Created:** Mon Sep 15, 2014 01:41 PM UTC by Zoran Milinkovic
**Last Updated:** Mon Sep 22, 2014 11:36 AM UTC
**Owner:** Neelakanta Reddy

In ImmModel::setImplementer for regular OI, a wrong trace is logged if class 
implementer has already been set to the object.

                    TRACE_7("ERR_EXIST: Object '%s' already has class 
implementer %s "
                            "conflicts with setting object implementer",
                        objectName.c_str(),
                        obj->mImplementer->mImplementerName.c_str());

This code may crash immnd if obj->mImplementer is NULL.


---

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

Reply via email to