Qpid
  1. Qpid
  2. QPID-3261

decrease severity and improve clarity of certain log messages

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 0.6, 0.7, 0.8, 0.9, 0.10
    • Fix Version/s: 0.11
    • Component/s: Java Broker, Java Client
    • Labels:
      None

      Description

      Some users have complained on the mailing lists about the following log messages, which do seem like they are being emitted at the wrong level. Based on discussion on the dev list they should be updated to info/debug levels. The second could also be clearer about what it is trying to convey.

      [2011-04-25 13:25:10,177] WARN

      {org.apache.qpid.transport.ClientDelegate}

      - Ignoring the idle
      timeout 120 set by the connection, using the brokers max value 0
      [2011-04-25 13:25:10,178] WARN

      {org.apache.qpid.transport.SessionDelegate}

      - CLOSED:
      [ssn:"10bbf39e-3676-4205-a713-789b3a377cf3"]

      [2011-04-21 21:33:25,038] ERROR

      {org.apache.qpid.server.configuration.ServerConfiguration}

      - Signal HUP not
      supported for OS: Windows Vista

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        1m 40s 1 Robbie Gemmell 16/May/11 21:26
        Resolved Resolved Closed Closed
        1366d 22h 40m 1 Rob Godfrey 11/Feb/15 20:07
        Rob Godfrey made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Robbie Gemmell made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        Robbie Gemmell added a comment -

        Log messages updated.

        Show
        Robbie Gemmell added a comment - Log messages updated.
        Robbie Gemmell created issue -

          People

          • Assignee:
            Robbie Gemmell
            Reporter:
            Robbie Gemmell
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development