Project

General

Profile

Actions

Bug #3641

closed

Some debug logs informations about concurrent access were wrong

Added by Vincent MEMBRÉ over 9 years ago. Updated almost 8 years ago.

Status:
Released
Priority:
1
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Regression:

Description

in a debug log from #3517, a debug log appeared because of concurrent access to a lock.

This log should say which method is throwing, but the wrong method is displayed.

11:17:26.685 [qtp760805843-76] DEBUG com.normation.rudder.services.servers.NodeConfigurationServiceImpl - Concurrent acces for method getStackTrace

The concurrent access is not the method getStackTrace.

Actions #1

Updated by Vincent MEMBRÉ over 9 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/227
Actions #2

Updated by Vincent MEMBRÉ over 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #3

Updated by Anonymous over 9 years ago

Actions #4

Updated by Nicolas PERRON over 9 years ago

  • Subject changed from Some debug logs are not targeting the good method to Some debug logs informations about concurrent access were wrong
Actions #5

Updated by Nicolas PERRON over 9 years ago

  • Status changed from Pending release to Released
Actions #6

Updated by Nicolas PERRON over 9 years ago

This bug has been fixed in Rudder 2.4.7, which was released today.
Check out:

Actions #7

Updated by Benoît PECCATTE almost 8 years ago

  • Category changed from 39 to System integration
Actions

Also available in: Atom PDF