[ http://jira.codehaus.org/browse/XFIRE-371?page=comments#action_64336 ]
Dan Diephouse commented on XFIRE-371: ------------------------------------- Sure enough, it only happens when we generate WSDL, but I just fixed this in SVN. > ThreadLocals not cleared in XFireServletController > -------------------------------------------------- > > Key: XFIRE-371 > URL: http://jira.codehaus.org/browse/XFIRE-371 > Project: XFire > Type: Bug > Components: Core > Versions: 1.0 > Environment: Windows XP, Sun Java 5, Tomcat 4 > Reporter: John Kristian > Assignee: Dan Diephouse > Priority: Minor > Fix For: 1.1 > > > XFireServletController.doService can set the ThreadLocal 'requests' and > 'responses' members, but neglect to clear them before returning. This can be > a source of confusion to the affected thread. For example, the thread may be > subsequently assigned (by a frugal servlet container) to process an unrelated > request, at which point the ThreadLocal request and response may have been > (frugally) allocated to other uses unrelated to this thread's current work. > Havoc may ensue. > Please take greater care to clear these ThreadLocal members before exiting > doService. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
