topic Any fix for reported problem? in Alfresco Archive

Any fix for reported problem?

hsjawanda — Thu, 05 Jan 2006 02:54:08 GMT

Hi all,I ran into the problem described in http://www.alfresco.org/jira/browse/AR-283 today. When is a fix planned for this problem? The person who reported this problem also provided a file that fixed the problem for him. How good/bad is this fix? If you guys already know the fix (or have a good i

Re: Any fix for reported problem?

derek — Thu, 05 Jan 2006 09:45:50 GMT

Hi,

This issue only occurs when DEBUG is on. The nulls were passed through very deliberately as the arguments are only used during callbacks, which the SpringAwareUserTransaction was handling itself… except when the base class was attempting to generate a DEBUG string (a use-case I didn't test for).

The solution was just to override the method that generated the DEBUG string and return something that was method-independent. After all, the SpringAwareUserTransaction is method-independent.

The bug has been closed today, but the fix went in on Tuesday. As an aside, it is possible to be generating but not outputing all DEBUG statements. In case you were not intentionally leaving DEBUG on: http://www.alfresco.org/mediawiki/index.php/Log4J_Configuration

Regards

Re: Any fix for reported problem?

davidc — Thu, 05 Jan 2006 13:29:20 GMT

FYI, the fix was committed in SVN revision 2064.