Telecom Log Service Avatar
  1. OMG Specification

Telecom Log Service — Open Issues

  • Acronym: TLOG
  • Issues Count: 42
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Summary

Key Issue Reported Fixed Disposition Status
TLOG-41 Chapter 2.2.4.4, page 2-11 TLOG 1.0 open
TLOG-40 3. Appendix 1, page A-5 has missing definition of write_recordlist method TLOG 1.0 open
TLOG-46 Chapter 2.2.7.1, page 2-24 copy and copy_with_id operations TLOG 1.0 open
TLOG-45 Definition of DAG topology TLOG 1.0 open
TLOG-44 Chapter 2.2.5.5, page 2-22. set_record_attribute operation TLOG 1.0 open
TLOG-39 Page 2-19. Description of write_recordlist TLOG 1.0 open
TLOG-38 missing LogOffDuty exceptions TLOG 1.0 open
TLOG-43 Chapter 2.2.5.4, page 2-21 TLOG 1.0 open
TLOG-42 Chapter 2.2.5.1, page 2-19 TLOG 1.0 open
TLOG-59 Section: 1.2.5.1 TLOG 1.1.2 open
TLOG-58 Section: 1.2.5.1 TLOG 1.1.2 open
TLOG-55 Section: 1.2.4.11 TLOG 1.1.2 open
TLOG-54 Section: 1.2.5.1 TLOG 1.1.2 open
TLOG-52 AttributeValueChange event section 1.4.4 TLOG 1.1.2 open
TLOG-51 Chapter 2.5, page 2-33 TLOG 1.0 open
TLOG-57 Section: 1.4.3 TLOG 1.1.2 open
TLOG-53 support QoS properties TLOG 1.1.2 open
TLOG-48 Chapter 2.3.1, page 2-26 TLOG 1.0 open
TLOG-47 Chapter 2.2.7.2, page 2-25. destroy operation TLOG 1.0 open
TLOG-50 Chapter 2.4.1, page 2-29 TLOG 1.0 open
TLOG-56 Section: 1.4.3 TLOG 1.1.2 open
TLOG-49 Chapter 2.4 TLOG 1.0 open
TLOG-1 The text for the copy() and copy_with_id() operations TLOG 1.0b1 open
TLOG-13 $issue.summary TLOG 1.0b1 open
TLOG-12 $issue.summary TLOG 1.0b1 open
TLOG-4 $issue.summary TLOG 1.0b1 open
TLOG-3 $issue.summary TLOG 1.0b1 open
TLOG-9 $issue.summary TLOG 1.0b1 open
TLOG-8 $issue.summary TLOG 1.0b1 open
TLOG-6 $issue.summary TLOG 1.0b1 open
TLOG-5 $issue.summary TLOG 1.0b1 open
TLOG-11 $issue.summary TLOG 1.0b1 open
TLOG-10 $issue.summary TLOG 1.0b1 open
TLOG-7 $issue.summary TLOG 1.0b1 open
TLOG-2 $issue.summary TLOG 1.0b1 open
TLOG-20 OMG Document formal/01-04-08 --IDL issue TLOG 1.0 open
TLOG-19 TelecomLogService/2000-01-04 -- typo TLOG 1.0 open
TLOG-15 Telecom logging -- illegal IDL TLOG 1.0 open
TLOG-14 $issue.summary TLOG 1.0b1 open
TLOG-18 Viewing old logs TLOG 1.0 open
TLOG-17 Initial references? TLOG 1.0 open
TLOG-16 Telecom Log Service issue TLOG 1.0 open

Issues Descriptions

Chapter 2.2.4.4, page 2-11

  • Key: TLOG-41
  • Legacy Issue Number: 5627
  • Status: open  
  • Source: nokia.com ( Ivan Bodunov)
  • Summary:

    · Chapter 2.2.4.4, page 2-11. To have one style in the document and make it more readable I propose to change ulong to unsigned long.

  • Reported: TLOG 1.0 — Tue, 3 Sep 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

3. Appendix 1, page A-5 has missing definition of write_recordlist method

  • Key: TLOG-40
  • Legacy Issue Number: 5618
  • Status: open  
  • Source: nokia.com ( Ivan Bodunov)
  • Summary:

    3. Appendix 1, page A-5 has missing definition of write_recordlist method in the Log interface and has doubled definition of write_records method.

    All these issues are applied to version 1.0 as well (formal/2000-01-04).

  • Reported: TLOG 1.0 — Fri, 30 Aug 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Chapter 2.2.7.1, page 2-24 copy and copy_with_id operations

  • Key: TLOG-46
  • Legacy Issue Number: 5632
  • Status: open  
  • Source: nokia.com ( Ivan Bodunov)
  • Summary:

    · Chapter 2.2.7.1, page 2-24. What is so resource consuming in the copy and copy_with_id operations? Why it can raise NoResources exception and any factory cannot? Factories also create logs and the log server also can have not enough resources to do it, but according to the specification factories do not raise NoResources exception. If NoResources should leave there then appendix 1 should be corrected since definitions of these copy operations do not contain NoResources exception in the list of raised exceptions and appendix 1 does not have definition of NoResources exception at all (should be put in DsLogAdmin module). Or if NoResources can be omitted then description of those copy operations should be modified

  • Reported: TLOG 1.0 — Tue, 3 Sep 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Definition of DAG topology

  • Key: TLOG-45
  • Legacy Issue Number: 5631
  • Status: open  
  • Source: nokia.com ( Ivan Bodunov)
  • Summary:

    · Chapter 2.2.6, page 2-24. It is not clear for reader what is DAG topology. I propose to explain this. At least write what it stands for, like "DAG (directed acyclic graph)".

  • Reported: TLOG 1.0 — Tue, 3 Sep 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Chapter 2.2.5.5, page 2-22. set_record_attribute operation

  • Key: TLOG-44
  • Legacy Issue Number: 5630
  • Status: open  
  • Source: nokia.com ( Ivan Bodunov)
  • Summary:

    · Chapter 2.2.5.5, page 2-22. set_record_attribute operation does not raise InvalidGrammar and InvalidConstraint exceptions. These exceptions should be deleted from the description of the operation

  • Reported: TLOG 1.0 — Tue, 3 Sep 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Page 2-19. Description of write_recordlist

  • Key: TLOG-39
  • Legacy Issue Number: 5617
  • Status: open  
  • Source: nokia.com ( Ivan Bodunov)
  • Summary:

    2. Page 2-19. Description of write_recordlist says "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." Why doesn't it say anything about attr_list field of RecordData struct? Seems to me that this field (list of name/value pairs) can also be modified and written to the log.

  • Reported: TLOG 1.0 — Fri, 30 Aug 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

missing LogOffDuty exceptions

  • Key: TLOG-38
  • Legacy Issue Number: 5616
  • Status: open  
  • Source: nokia.com ( Ivan Bodunov)
  • Summary:

    1. Page 2-19 has missing LogOffDuty exception in the signatures of write_records and write_recordlist methods.

    Currently there is:
    void write_records(in Anys records)
    raises(LogFull, LogLocked, LogDisabled);
    void write_recordlist(in RecordList list)
    raises(LogFull, LogLocked, LogDisabled);

    Should be:
    void write_records(in Anys records)
    raises(LogFull, LogOffDuty, LogLocked, LogDisabled);
    void write_recordlist(in RecordList list)
    raises(LogFull, LogOffDuty, LogLocked, LogDisabled);

  • Reported: TLOG 1.0 — Fri, 30 Aug 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Chapter 2.2.5.4, page 2-21

  • Key: TLOG-43
  • Legacy Issue Number: 5629
  • Status: open  
  • Source: nokia.com ( Ivan Bodunov)
  • Summary:

    · Chapter 2.2.5.4, page 2-21. delete_records operation does not raise InvalidAttribute exception. This exception should be deleted from the description of the operation.

  • Reported: TLOG 1.0 — Tue, 3 Sep 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Chapter 2.2.5.1, page 2-19

  • Key: TLOG-42
  • Legacy Issue Number: 5628
  • Status: open  
  • Source: nokia.com ( Ivan Bodunov)
  • Summary:

    · Chapter 2.2.5.1, page 2-19. What are the values for minor codes: LOGFULL, LOGOFFDUTY, LOGLOCKED, and LOGDISABLED? Should those be defined in IDL?

  • Reported: TLOG 1.0 — Tue, 3 Sep 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Section: 1.2.5.1

  • Key: TLOG-59
  • Legacy Issue Number: 9262
  • Status: open  
  • Source: Identity Engines, Inc. ( J.T. Conklin)
  • 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.

  • Reported: TLOG 1.1.2 — Tue, 24 Jan 2006 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Section: 1.2.5.1

  • Key: TLOG-58
  • Legacy Issue Number: 9311
  • Status: open  
  • Source: Identity Engines, Inc. ( J.T. Conklin)
  • 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.

  • Reported: TLOG 1.1.2 — Wed, 25 Jan 2006 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Section: 1.2.4.11

  • Key: TLOG-55
  • Legacy Issue Number: 9259
  • Status: open  
  • Source: Identity Engines, Inc. ( J.T. Conklin)
  • Summary:

    The specification states "If the capacity of a log exeeds that of one of its log capacity alarm thresholds, ..." This wording is confusing: The log capacity (as set by set_max_size()) is not compared with the capacity alarm thresholds; it does not state that the ThresholdAlarm is sent once when the threshold has been met, which may lead some to believe the alarm events will be sent continuously; and the word "Exceed" means that a alarm would never be sent for a threshold of 100%. I think that something like "If after a log record has been written, the current size of a log, as expressed as a percentage of max log size, is greater or equal to the next log capacity threshold, then a ThresholdAlarm event is generated ..." might be clearer.

  • Reported: TLOG 1.1.2 — Tue, 24 Jan 2006 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Section: 1.2.5.1

  • Key: TLOG-54
  • Legacy Issue Number: 8829
  • Status: open  
  • Source: Identity Engines ( J.T. Conklin)
  • Summary:

    I am in the process of updating TAO's Logging Service implementation. Section 1.2.5.1 stats "The Telecom Log Service proposes to define the following OMG Standard exception codes for use with the CosEvent and CosNotification push operations..." and goes on to mention a LOGFULL and LOGOFFDUTY minor code for the NO_RESOURCE [sic] SystemException, a LOGLOCKED minor code for the NO_PERMISSIONS SystemException, and a LOGDISABLED minor code for the TRANSIENT SystemException. TAO does not define these minor codes, so I checked the latest CORBA spec (3.0.3 / formal/04-03-12) and they are not in Appendix A either. What exactly does the spec mean "proposes to define" and what should an implementer do to handle these errors in the here and now.

  • Reported: TLOG 1.1.2 — Tue, 31 May 2005 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

AttributeValueChange event section 1.4.4

  • Key: TLOG-52
  • Legacy Issue Number: 8827
  • Status: open  
  • Source: Identity Engines ( J.T. Conklin)
  • Summary:

    Section 1.4.4 states that the "AttributeValueChange event is generated by a log factor when one of its log changes one of changes one of the following attributes..." The description of the set_* methods state "An AttributeValueChange is generated whenever the * is set". The former implies that the event will be sent if the value is changed, the latter imples the event will be sent even if the value is the same.

  • Reported: TLOG 1.1.2 — Fri, 27 May 2005 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Chapter 2.5, page 2-33

  • Key: TLOG-51
  • Legacy Issue Number: 5637
  • Status: open  
  • Source: nokia.com ( Ivan Bodunov)
  • Summary:

    · Chapter 2.5, page 2-33. The paragraph of the second bullet point can also contain the TypedRecordIterator.

  • Reported: TLOG 1.0 — Tue, 3 Sep 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Section: 1.4.3

  • Key: TLOG-57
  • Legacy Issue Number: 9261
  • Status: open  
  • Source: Identity Engines, Inc. ( J.T. Conklin)
  • Summary:

    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.

  • Reported: TLOG 1.1.2 — Tue, 24 Jan 2006 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

support QoS properties

  • Key: TLOG-53
  • Legacy Issue Number: 8828
  • Status: open  
  • Source: Identity Engines ( J.T. Conklin)
  • Summary:

    I'm working on TAO's Log Service implementation, and I'm not sure how I'm supposed to support QoS properties. The spec for get_log_qos() method states it "returns a list of the quality of service properties supported by the log." This is different from the other get_* methods, which return the current value of the settings. If this is the intent, it should be emphasized, and perhaps a new method introduced to fetch the current QoS settings. The three defined QoS settings QoSNone, QoSFlush, and QoSReliability are mutually exclusive. But unlike the Notification Service Spec's section on QoS settings, there is no guideance wrt. semantics of a property list with multiple properties or what should be returned in the denied list in the UnsupportedQoS exception.

  • Reported: TLOG 1.1.2 — Fri, 27 May 2005 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Chapter 2.3.1, page 2-26

  • Key: TLOG-48
  • Legacy Issue Number: 5634
  • Status: open  
  • Source: nokia.com ( Ivan Bodunov)
  • Summary:

    · Chapter 2.3.1, page 2-26. It is more correct if it is said that BasicLogFactory creates BasicLog but not Log (similar to that EventLogFactory creates EventLog).

  • Reported: TLOG 1.0 — Tue, 3 Sep 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Chapter 2.2.7.2, page 2-25. destroy operation

  • Key: TLOG-47
  • Legacy Issue Number: 5633
  • Status: open  
  • Source: nokia.com ( Ivan Bodunov)
  • Summary:

    · Chapter 2.2.7.2, page 2-25. destroy operation is not only inherited from CosEventChannelAdmin::EventChannel but also defined in BasicLog interface. It is worth to mention it, since destroy operation can also be invoked on BasicLog objects.

  • Reported: TLOG 1.0 — Tue, 3 Sep 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Chapter 2.4.1, page 2-29

  • Key: TLOG-50
  • Legacy Issue Number: 5636
  • Status: open  
  • Source: nokia.com ( Ivan Bodunov)
  • Summary:

    · Chapter 2.4.1, page 2-29. Definition of the ObjectCreation struct contains logref field. This is different from the same definition in appendix 1 on page A-7. I think the correct version is on page 2-29. Then ObjectDeletion struct (page 2-30) does not have logref field. Is it OK? If yes, then "NOTE" in appendix 1 on page A-7 is wrong and not needed at all. If not, then the definition of that struct both on page 2-30 and in the appendix 1 should be modified.

  • Reported: TLOG 1.0 — Tue, 3 Sep 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Section: 1.4.3

  • Key: TLOG-56
  • Legacy Issue Number: 9260
  • Status: open  
  • Source: Identity Engines, Inc. ( J.T. Conklin)
  • Summary:

    The IDL for the ThresholdAlarm event defines three constants for the percieved_severity field: critical, minor, and cleared. The text says the "percieved_severity is minor if log is not full, and critical otherwise". If these are the only valid values, why is there a definition for cleared?

  • Reported: TLOG 1.1.2 — Tue, 24 Jan 2006 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Chapter 2.4

  • Key: TLOG-49
  • Legacy Issue Number: 5635
  • Status: open  
  • Source: nokia.com ( Ivan Bodunov)
  • Summary:

    · Chapter 2.4. Within the whole chapter in the description of every generated event "the log field" is used instead of "the logref field". Should be changed in every occurrence.

  • Reported: TLOG 1.0 — Tue, 3 Sep 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

The text for the copy() and copy_with_id() operations

  • Key: TLOG-1
  • Legacy Issue Number: 2726
  • Status: open  
  • Source: Anonymous
  • Summary:

    The text for the copy() and copy_with_id() operations defined on the DsLogAdmin::Log
    interface should specify that a DsLogNotification::ObjectCreation notification will
    be generated as a result of the copy operation.

  • Reported: TLOG 1.0b1 — Sun, 13 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

${issue.summary}

  • Key: TLOG-13
  • Legacy Issue Number: 2774
  • Status: open  
  • Source: Anonymous
  • Summary:
  • Reported: TLOG 1.0b1 — Tue, 29 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

${issue.summary}

  • Key: TLOG-12
  • Legacy Issue Number: 2773
  • Status: open  
  • Source: Anonymous
  • Summary:
  • Reported: TLOG 1.0b1 — Mon, 28 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

${issue.summary}

  • Key: TLOG-4
  • Legacy Issue Number: 2757
  • Status: open  
  • Source: Anonymous
  • Summary:
  • Reported: TLOG 1.0b1 — Fri, 18 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

${issue.summary}

  • Key: TLOG-3
  • Legacy Issue Number: 2756
  • Status: open  
  • Source: Anonymous
  • Summary:
  • Reported: TLOG 1.0b1 — Thu, 17 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

${issue.summary}

  • Key: TLOG-9
  • Legacy Issue Number: 2764
  • Status: open  
  • Source: Anonymous
  • Summary:
  • Reported: TLOG 1.0b1 — Tue, 22 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

${issue.summary}

  • Key: TLOG-8
  • Legacy Issue Number: 2763
  • Status: open  
  • Source: Anonymous
  • Summary:
  • Reported: TLOG 1.0b1 — Tue, 22 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

${issue.summary}

  • Key: TLOG-6
  • Legacy Issue Number: 2759
  • Status: open  
  • Source: Anonymous
  • Summary:
  • Reported: TLOG 1.0b1 — Fri, 18 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

${issue.summary}

  • Key: TLOG-5
  • Legacy Issue Number: 2758
  • Status: open  
  • Source: Anonymous
  • Summary:
  • Reported: TLOG 1.0b1 — Fri, 18 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

${issue.summary}

  • Key: TLOG-11
  • Legacy Issue Number: 2771
  • Status: open  
  • Source: Anonymous
  • Summary:
  • Reported: TLOG 1.0b1 — Mon, 28 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

${issue.summary}

  • Key: TLOG-10
  • Legacy Issue Number: 2768
  • Status: open  
  • Source: Anonymous
  • Summary:
  • Reported: TLOG 1.0b1 — Fri, 25 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

${issue.summary}

  • Key: TLOG-7
  • Legacy Issue Number: 2762
  • Status: open  
  • Source: Anonymous
  • Summary:
  • Reported: TLOG 1.0b1 — Tue, 22 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

${issue.summary}

  • Key: TLOG-2
  • Legacy Issue Number: 2755
  • Status: open  
  • Source: Anonymous
  • Summary:
  • Reported: TLOG 1.0b1 — Thu, 17 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

OMG Document formal/01-04-08 --IDL issue

  • Key: TLOG-20
  • Legacy Issue Number: 4799
  • Status: open  
  • Source: Anonymous
  • Summary:

    I think the OMG Telecom Log Service IDL (DsLogAdmin and DsNotifyLogAdmin
    modules) isn't in accordance with the CORBA 2.6 "OMG IDL Syntax and
    Semantics" specification.

    Indeed the DsNotifyLogAdmin::NotifyLog interface inherits from both
    DsLogAdmin::Log.get_qos and CosNotification::QoSAdmin.get_qos
    operations, this is illegal according to section 3.7.5 (page 3-20) of
    the CORBA 2.6 specification.

    I've tried to compile the OMG Telecom Log Service with 2 differents ORBs
    (ORBacus 4.0.5 and JacORB 1.4beta2) without success.

  • Reported: TLOG 1.0 — Wed, 2 Jan 2002 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

TelecomLogService/2000-01-04 -- typo

  • Key: TLOG-19
  • Legacy Issue Number: 4279
  • Status: open  
  • Source: Anonymous
  • Summary:

    There is a typo on the first sentence on page 2-13. The words "enabled lock" should be "enabled log" in the following sentence : The stop field indicates the date and time at which an unlocked and enabled lock stops functioning.

  • Reported: TLOG 1.0 — Fri, 20 Apr 2001 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Telecom logging -- illegal IDL

  • Key: TLOG-15
  • Legacy Issue Number: 2920
  • Status: open  
  • Source: Triodia Technologies Pty Ltd ( Michi Henning)
  • Summary:

    The Notification Service defines:

    module CosNotification {
    // ...
    interface QoSAdmin

    { QoSProperties get_qos(); void set_qos(in QoSProperties qos) raises(UnsupportedQoS); // ... }

    ;
    // ...
    };

    module CosNotifyChannelAdmin {
    // ...
    interface EventChannel :
    CosNotification::QoSAdmin,
    CosNotification::AdminPropertiesAdmin,
    CosEventChannelAdmin::EventChannel

    { // ... };
    // ...
    };

    The Logging Service defines:

    module DSLogAdmin {
    // ...
    interface Log { // ... QoSList get_qos(); void set_qos(in QoSList qos) raises(UnsupportedQoS); // ... };
    };

    module DsEventLogAdmin {
    interface EventLog :
    DsLogAdmin::Log,
    CosEventChannelAdmin::EventChannel {};
    // ...
    };

    module DsNotifyLogAdmin {
    interface NotifyLog :
    DsEventLogAdmin::EventLog,
    CosNotifyChannelAdmin::EventChannel { // ... }

    ;
    };

    The net result is that DsNotifyLogAdmin::NotifyLog inherits get_qos()
    and set_qos() twice, once from QoSNotification::QoSAdmin, and once from
    DSLogAdmin::Log, which is illegal. This makes the Logging Service
    unimplementable right now.

    Looks like the operations in DSLogAdmin::Log will have to be renamed or
    the inheritance structure will have to change.

  • Reported: TLOG 1.0 — Fri, 1 Oct 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

${issue.summary}

  • Key: TLOG-14
  • Legacy Issue Number: 2777
  • Status: open  
  • Source: Anonymous
  • Summary:
  • Reported: TLOG 1.0b1 — Wed, 30 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Viewing old logs

  • Key: TLOG-18
  • Legacy Issue Number: 3695
  • Status: open  
  • Source: Scientific Research Corporation ( Rob Ruff)
  • Summary:

    Assuming a log is persistent, how does one access the logged data after the system has been shut down? It seems important to be able to view this data after the system shuts down to determine if there were any glitches while the system ran or to troubleshoot any problems that occured.

  • Reported: TLOG 1.0 — Mon, 12 Jun 2000 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Initial references?

  • Key: TLOG-17
  • Legacy Issue Number: 3458
  • Status: open  
  • Source: Triodia Technologies Pty Ltd ( Michi Henning)
  • Summary:

    The Log Service spec doesn't state how a client gets access to the
    intial references for the service (namely, the various factories).

  • Reported: TLOG 1.0 — Fri, 24 Mar 2000 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Telecom Log Service issue

  • Key: TLOG-16
  • Legacy Issue Number: 3120
  • Status: open  
  • Source: Anonymous
  • Summary:

    This issue concerns the Telecom Log Service as described in
    the dtc/99-07-02 document.

    I think the following statements in the spec are not compatible
    together:

    "Log forwarding is determined solely by forwarding state, it is not
    affected by the log's administrative state, availability state, log
    duration, scheduling, or log full action."

    "A log may be not be able to create any new log records because it is
    full, locked, or disabled. If a log cannot create new log records when
    a push operation is invoked, then the push operation should fail and a
    SystemException should be raised."

    If the log records are forwarded, then throwing system exceptions to
    the supplier doesn't make sense.

  • Reported: TLOG 1.0 — Wed, 15 Dec 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT