Issue 9262: Section: 1.2.5.1 (log-service-rtf) Source: (, ) Nature: Clarification Severity: Significant Summary: The specification says that "The write_recordlist() operation is provided ass a convienience operation to allow the output of a query of one log to be written to another log. In this case, only the "info" field (event content) of the RecordData struct is written to the log, the LogRecord id and logging time will be assigned by the log.". This is the only place in the spec that RecordData is used, I believe that LogRecord was intended. Also, it is unclear whether the attr_list field should be copied. While it says "only the info field" is written, attr_list is among the fields listed that will be "assigned by the log". For what it's worth, the Orbix Log Service implementation appears to copy the attr_list. Their Enterprise Messaging Guide for ORBIX 6.2 says "write_recordlist() is functionally identical to write_records(). It writes data directly to the log and raises the same exceptions. The major difference is that the record's data is stored in a LogRecord. This allows you to add a series of name/value pair attributes to assist in querying the log". The TAO log service implementation, which I currently maintain, also copies the value of attr_list. Resolution: Revised Text: Actions taken: Discussion: End of Annotations:===== iler: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Fri, 27 Jan 2006 16:25:38 -0500 To: issues@omg.org, log-service-rtf@omg.org From: Juergen Boldt Subject: issue 9261 -- Telecom Log Service RTF issue From: webmaster@omg.org Date: 24 Jan 2006 18:12:12 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: J.T. Conklin Company: Identity Engines, Inc. mailFrom: jtc@acorntoolworks.com Notification: No Specification: Telecom Log Service Specification Section: 1.4.3 FormalNumber: formal/03-07-xx Version: 1.1.2 RevisionDate: 07/xx/03 Page: 1-11,1-12,1-16 Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/417.9 (KHTML, like Gecko) Safari/417.8 Description I am the current maintainer of the TAO logging service implementation. The specification is unclear what the interactions between set_max_size(), set_log_full_action(), and set_capacity_alarm_thresholds() have on the current processing of capacity alarms. For example, consider a log with DsLogAdmin::halt log full action and 0 (ie. infinate) max size, and a capacity alarm threshold list of [50, 75, 90, 100]. If the log has 80KB of records, and the max size is set to 100KB, are ThresholdAlarms supposed to be sent for crossing 50 and 75%, or should a threshold alarm only be sent once the log grows to 90%? Similar questions arise when the log full action is changed to/from DsLogAdmin::halt from/to DsLogAdmin::wrap, as the capacity alarm threshold processing changes from a percentage to a "gauge". Or when the capacity alarm threshold list is changed from one set of values to another. ================================= Jürgen Boldt Director, Member Services Object Management Group, Inc. 140 Kendrick Street Building A, Suite 300 Needham, MA 02494 Tel. +1 781 444 0404 ext. 132 Fax: +1 781 444 0320 email: juergen@omg.org www www.omg.org ================================