santuario-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 41462] - Xml canonization - UTF-8 encoding issue in Xml security 1.4.0
Date Thu, 22 Feb 2007 20:53:54 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41462>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=41462





------- Additional Comments From jdmarshall@gmail.com  2007-02-22 12:53 -------
This is a pretty awful bug.  This will block me from being able to deploy 1.4.0,
which I need to deal with the race condition in the X509 code.

Has anyone figured out a workaround for this bug yet?

>From looking at the code, I think the submitter has it right here.  This line he
mentions below introduces the bug, and it was added in 1.4. 

A better option perhaps would be to achieve this optimization another way:  let
Hotspot do it for you.

In many cases, such as exactly this scenario here, you have a method that has a
frequently-executed conditional block at the top that uses a cheap, happy path
(or short circuits).  However, Hotspot only inlines very short methods, so the
method call is preserved. (Can JDK 6.0 do partial inlining?  I don't honestly
know).  So what some clever folks figured out is that if you factor out the
'long path' into another method, then Hotspot will frequently inline the
short-circuit logic into the caller.  



-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Mime
View raw message