[DIRMINA-838] Redundant AttributeKey allocation resulting in high garbage collector activity

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.3
• Fix Version/s: 2.0.8
• Component/s: Filter
• Environment: java version "1.6.0_22"; Java(TM) SE Runtime Environment (build 1.6.0_22-b04); Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)
• Assignee: Unassigned
• Reporter: Platon Potapov
• Created: 13/Jun/11 12:59
• Updated: 09/Sep/14 05:44
• Resolved: 09/Sep/14 05:44

Description

The classes CumulativeProtocolDecoder and ProtocolCodecFilter (there are others too, but these two are the important ones for our project) have members of type AttributeKey declared as:
private final AttributeKey ENCODER = new AttributeKey(ProtocolCodecFilter.class, "encoder");

As can be seen, these are not static, so each time ProtocolCodecFilter is created, AttributeKey objects get created as well, which in turn involves creation of a lot of String and char[] objects. jProfiler indicates that AttributeKey is accountable for creation of about 85% of all Strings and char[] in runs of our project, so it makes a significant difference for us.

Is it OK for these attribute key objects to be singletons? If not, what would take to make them singletons?
Some of other MINA filters have AttributeKeys as static members (e.g. MdcInjectionFilter, SslFilter).

To summarize: the improvement being requested is to make the pre-defined AttributeKey objects static within classes such as CumulativeProtocolDecoder and ProtocolCodecFilter.