Ticket #362 (closed enhancement: fixed)

Opened 1 year ago

Last modified 1 year ago

Using a bitshift for the Appender ID induces severe limitation on usability

Reported by:	volcore	Assigned to:	kris
Priority:	normal	Milestone:	0.97 RC 1
Component:	IO	Version:	trunk
Keywords:	logger	Cc:

Description

The problem is that for the appender ID a mask is used, the mask is defined to be an int and shifted right every time an appender is instantiated. Apparently this causes the ID to overflow quickly (after 30 appenders).

In a rather large project we quickly get out of Appender ID's. Another solution should be found here. Changing the type of Mask to long doubles the limit, but that's still not enough if we have a large number of subsystems, each with its own appender.

Change History

03/26/07 03:15:15 changed by larsivi

type changed from wishlist to enhancement.
milestone set to 0.97 RC 1.

03/26/07 18:41:24 changed by kris

status changed from new to closed.
resolution set to fixed.

what are you doing with more than 30 appenders?

03/27/07 13:25:32 changed by kris

status changed from closed to reopened.
resolution deleted.

(whoops; this ticket was mistakenly closed by me ... not sure how that happened)

04/03/07 21:27:54 changed by kris

status changed from reopened to closed.
resolution set to fixed.

As is, the logging system supports more than 30 distinct appenders. For example, these could be different files, different email urls, or whatever. These are assigned to log-events on a one-to-many basis e.g. multiple events funnel into shared appenders, via the logger hierarchy.

It seems somewhat counter-productive to have that many different places to look for logged output, and there's been no follow-up at this time, so I'm going to close the ticket.

Please reopen if there continues to be a problem?

Ticket Navigation