Skip to content

SessionPool logging is using wrong object string to replace #3235

New issue
New issue
Closed
Closed
SessionPool logging is using wrong object string to replace#3235
Assignees
pongad
Labels
priority: p2Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Description

@carlzogh
carlzogh
opened on May 6, 2018

Class: com.google.cloud.spanner.SessionPool
Function: PoolMaintainer.closeIdleSessions(Instant currTime)

logger.log(Level.FINE, "Closing session %s", sess.getName());
Should instead be
logger.log(Level.FINE, "Closing session {0}", sess.getName());
to replace {0} with sess.getName(), otherwise all it's logging is Closing session %s

Activity

  1. pongad commented on May 8, 2018

    @pongad
    pongad
    on May 8, 2018
    Contributor

    Closed by #3224

  2. pongad
    closed this as completedon May 8, 2018

  3. pongad commented on May 8, 2018

    @pongad
    pongad
    on May 8, 2018
    Contributor

    Sorry closed wrong issue 😢

  4. pongad
    reopened this on May 8, 2018
  5. pongad
    self-assigned this
    on May 8, 2018
  6. pongad
    added
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    priority: p2Moderately-important priority. Fix may not be included in next release.
    on May 8, 2018
  7. pongad
    closed this as completedin #3241on May 8, 2018
  8. pongad
    added a commit that references this issue on May 8, 2018

    spanner: fix log syntax (#3241)

    260e93d
  9. theacodes
    unassigned
    pongad
    on Sep 28, 2018
  10. JustinBeckwith
    assigned
    pongad
    on Feb 1, 2021
  11. chingor13
    added 4 commits that reference this issue on Mar 24, 2026

    deps: update dependency net.bytebuddy:byte-buddy to v1.15.2 (#3235)

    1e72ff0

    chore(main): release 2.46.1 (#3238)

    2b85614

    chore: Update generation configuration at Tue Aug 6 02:15:55 UTC 2024 (…

    70f4387

    chore: merge train for nonblocking-appendable/** branches (#3231)

    c7058c7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

priority: p2Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions