Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-3168

Reference Manual lacks topics on trace-related connection URL attributes

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.3.1.4
    • 10.4.1.3
    • Documentation
    • None

    Description

      The Admin Guide topic "Network client tracing" describes three connection URL attributes that enable network client tracing:

      http://db.apache.org/derby/docs/dev/adminguide/cadminappsclienttracing.html

      The URL attributes are traceFile, traceDirectory, and traceLevel.

      These three attributes are missing from the Reference Manual section where all the connection URL attributes are listed and described:

      http://db.apache.org/derby/docs/dev/ref/rrefattrib24612.html

      Like the securityMechanism and ssl attributes, these attributes appear to apply only to the client/server mode of Derby, not to the embedded mode.

      I'll add topics to the Reference Manual for each of these attributes, unless there is some reason not to.

      Attachments

        1. DERBY-3168-3.zip
          8 kB
          Camilla Haase
        2. DERBY-3168-3.diff
          14 kB
          Camilla Haase
        3. DERBY-3168-2.zip
          8 kB
          Camilla Haase
        4. DERBY-3168-2.diff
          14 kB
          Camilla Haase
        5. DERBY-3168.zip
          7 kB
          Camilla Haase
        6. DERBY-3168.diff
          12 kB
          Camilla Haase

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            chaase3 Camilla Haase
            chaase3 Camilla Haase
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment