• Bug
  • Status: Closed
  • 2 Major
  • Resolution: Cannot Reproduce
  • DSO:L2
  • gkeim
  • Reporter: gkeim
  • March 27, 2008
  • 0
  • Watchers: 0
  • July 27, 2012
  • April 03, 2008


When you run the demo server and a demo client in a shell with both in the background, the following message is emitted to the console every minute:

2008-03-27 15:08:35,884 [DSO Lock Object.wait() timer] INFO com.tc.object.lockmanager.api.ClientLockManager - ChannelID=[0]: Running Lock GC…

It interferes with normal use of the shell and isn’t very useful to the end-user. Whether or not this message should even go in the log is debatable, but no repetitive message should go to the console.


Fiona OShea 2008-03-28

Is this important to have all the time? Or at debug level?

Saravanan Subbiah 2008-03-28

Are you sure it goes to the console ? It goes to the logs alright. It is useful to have it in the logs and even now we figured out an issue because of the logging.

If it goes to the console, we ill remove it. But I am pretty sure it doesnt go to the console.

Saravanan Subbiah 2008-04-01


Can you follow up with Gary on this ?

Raghvendra Singh 2008-04-03

Not reproducible.

Assigning it to

Gary Keim 2008-07-21

This was happening because there was a .tc.dev.log4j.properties in my home directory, which alters the TC logger even if the file has no content.