Re: 100% CPU Usage and blocking concurrent Threads when using t:saveState

2009-12-10 Thread Jakob Korherr
I agree with Mario. It really seams llike the internal structure of the TreeMap is destroyed, thus ending in some infinite loop and causing 100% CPU. Shouldn't we generally synchronize those Maps or use ConcurrentMaps? Regards, Jakob Korherr 2009/12/10 Mario Ivankovits ma...@ops.co.at For

RE: 100% CPU Usage and blocking concurrent Threads when using t:saveState

2009-12-10 Thread Mario Ivankovits
: Donnerstag, 10. Dezember 2009 10:35 An: MyFaces Discussion Betreff: Re: 100% CPU Usage and blocking concurrent Threads when using t:saveState I agree with Mario. It really seams llike the internal structure of the TreeMap is destroyed, thus ending in some infinite loop and causing 100% CPU

Re: 100% CPU Usage and blocking concurrent Threads when using t:saveState

2009-12-10 Thread Jan Baudisch
Jakob Korherr Gesendet: Donnerstag, 10. Dezember 2009 10:35 An: MyFaces Discussion Betreff: Re: 100% CPU Usage and blocking concurrent Threads when using t:saveState I agree with Mario. It really seams llike the internal structure of the TreeMap is destroyed, thus ending in some infinite loop

RE: 100% CPU Usage and blocking concurrent Threads when using t:saveState

2009-12-10 Thread Mario Ivankovits
: sethfromaust...@gmail.com [mailto:sethfromaust...@gmail.com] Im Auftrag von Jakob Korherr Gesendet: Donnerstag, 10. Dezember 2009 10:35 An: MyFaces Discussion Betreff: Re: 100% CPU Usage and blocking concurrent Threads when using t:saveState I agree with Mario. It really seams llike

RE: 100% CPU Usage and blocking concurrent Threads when using t:saveState

2009-12-09 Thread Mario Ivankovits
For me, this clearly looks like concurrent usage of the request map. All the servlet scopes (session, request, …) are not thread safe and one has to assure that they are not accessed at the same time by multiple threads. This turns out to be hard as e.g. there is no standard how to