[ http://jira.codehaus.org/browse/XFIRE-688?page=comments#action_79467 ] Dan Diephouse commented on XFIRE-688: -------------------------------------
I added some synchronization code to allow concurrent use to the hashmap. Things should no longer freeze... > HashMap access in CustomTypeMapping causes Thread-lock issues under high load > ----------------------------------------------------------------------------- > > Key: XFIRE-688 > URL: http://jira.codehaus.org/browse/XFIRE-688 > Project: XFire > Issue Type: Bug > Components: Aegis Module > Environment: Detected under JBoss 4.0.3SP1 on Linux + Sun JRE 1.5.0_06 > Reporter: Brice Ruth > Assigned To: Dan Diephouse > Fix For: 1.2.3 > > > During testing of a web service exposed through XFire 1.1.2, a thread monitor > detected a Thread-lock being caused by unsafe concurrent HashMap access in > CustomTypeMapping.register(Type) (line 83) - class2xml.put( > type.getTypeClass(), type.getSchemaType() ). > If CustomTypeMapping is an object shared between multiple threads in the J2EE > container, then access to HashMaps needs to be synchronized. > Please review this and any other classes that are shared for potential > concurrent access to non-thread safe objects (like HashMap) in a > multi-threaded environment. -- 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 --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
