LtLOG 1.1 NO IDEA Avatar
  1. OMG Issue

LTLOG11 — HALT mode

  • Key: LTLOG11-6
  • Legacy Issue Number: 7208
  • Status: open  
  • Source: ( Dominick Paniscotti)
  • Summary:

    The desired behavior of the log service when the log full action type is set to WRAP needs to be explicitly defined. This comment is based upon experience with the SCA 2.2 JTeL JTAP tests. Open interpretation of this item led to failures characterized by the following questions:

    a. Is a log with a log full action type of WRAP ever considered full? The JTeL JTAP tests expect this, but there is a semantic issue here – writes to a “full log” will be successful. Further, if a log in WRAP mode can become full, then…

    b. When is it considered full? Since log records use variable amounts of storage, a log nearing capacity may have a handful of bytes available, yet not have enough space to store even the smallest of records.

    c. When should the log service detect that the log is full? JTAP expects a log to be set full as soon as storage is exhausted, i.e., at the completion of a write that exactly fills the log. While this does not seem to be what the specification suggests, it illustrates an example of an area left up to interpretation.

    Declaring a log full only in HALT mode and only when a write is attempted would avoid these questions.

  • Reported: LtLOG 1.0 — Thu, 25 Mar 2004 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT