United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6900249 Use StringBuilder instead of StringBuffer to avoid locking
JDK-6900249 : Use StringBuilder instead of StringBuffer to avoid locking

Details
Type:
Enhancement
Submit Date:
2009-11-11
Status:
Closed
Updated Date:
2012-04-25
Project Name:
JDK
Resolved Date:
2010-01-15
Component:
xml
OS:
generic
Sub-Component:
org.w3c.dom
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
1.4.0
Fixed Versions:
1.4.0 (h1186)

Related Reports

Sub Tasks

Description
The following methods can show up as having high lock times which are using StringBuffer in some xml workloads.  These may be able to be migrated to using StringBuilder:
- com.sun.org.apache.xalan.internal.xsltc.dom.NodeCounter.formatNumbers(int[])
- com.sun.org.apache.xerces.internal.dom.DefferredDocumentImpl.getNodeValueString(int, boolean)
- com.sun.org.apache.xerces.internal.parsers.AbstractDOMParser.reset()
- com.sun.org.apache.xalan.xsltc.runtime.StringValueHandler.getValue()

                                    

Comments
EVALUATION

See comments.
                                     
2009-11-30
EVALUATION

ChangeSet=http://hg.openjdk.java.net/jdk6/jdk6/jaxp/rev/5c070921580c,ChangeRequest=6923146,ChangeRequest=6917454,ChangeRequest=6472982,ChangeRequest=6909759,ChangeRequest=6333993,ChangeRequest=6900779,ChangeRequest=6900773,ChangeRequest=6900249,ChangeRequest=6675332,ChangeRequest=6889654,ChangeRequest=6889649,ChangeRequest=6863312
                                     
2010-02-18



Hardware and Software, Engineered to Work Together