Pushed this fix in the following changesets. The fix ensures that all rtobjects
created by log is deleted.
We also need to discuss(once lennart is back from holiday) whether log should
have strict check for the rdn in the creation flow also.
[staging:39ffb9]
[staging:0b35a9]
[staging:03d9d8]
changeset: 5472:39ffb9cd77e5
branch: opensaf-4.3.x
parent: 5467:416bbfa19298
user: Mathivanan N.P.<[email protected]>
date: Mon Jul 21 14:08:01 2014 -0400
summary: log: delete associated runtime object whenever app stream is
deleted [#917]
changeset: 5473:0b35a99df663
branch: opensaf-4.4.x
parent: 5468:2a56621b7c53
user: Mathivanan N.P.<[email protected]>
date: Mon Jul 21 14:08:01 2014 -0400
summary: log: delete associated runtime object whenever app stream is
deleted [#917]
changeset: 5474:03d9d861d188
tag: tip
parent: 5471:6e81b33f10d6
user: Mathivanan N.P.<[email protected]>
date: Mon Jul 21 14:08:01 2014 -0400
summary: log: delete associated runtime object whenever app stream is
deleted [#917]
---
** [tickets:#917] LOG: App stream with special file name creates runtime object
that is not removed correctly**
**Status:** assigned
**Milestone:** 4.5.FC
**Created:** Tue May 20, 2014 07:57 AM UTC by elunlen
**Last Updated:** Tue Jul 08, 2014 03:15 PM UTC
**Owner:** Mathi Naickan
1. Problem:
====================
The new application log stream with name "safLgStrCfg=Test" (SaLogStreamConfig)
created by saflogger can not be listed or deleted.
Example:
SC-1:~ # saflogger -a safLgStrCfg=Test "Hello world"
SC-1:~ # immfind safLgStrCfg=Test
safLgStrCfg=Test
SC-1:~ # immlist safLgStrCfg=Test
error - saImmOmAccessorGet_2 FAILED: SA_AIS_ERR_NO_RESOURCES (18)
SC-1:~ # immcfg -d safLgStrCfg=Test
error - saImmOmCcbObjectDelete for 'safLgStrCfg=Test' FAILED:
SA_AIS_ERR_BAD_OPERATION (20)
2. Analysis:
====================
The saflogger doesn’t support creating a configuration log stream. It can only
open the existing configuration log stream.
When using saflogger to create a new app log stream with name
"safLgStrCfg=Test", osaflogd will create a runtime object "safLgStrCfg=Test".
Then saflogger closes the stream and tries to delete this object. Because the
prefix name is not "safLgStr=", it cannot be removed from IMM.
So after that, runtime object "safLgStrCfg=Test" cannot be deleted by using OM
immcfg, and cannot be listed by using immlist cause the stream of this object
has already closed.
---
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.
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
