Richfaces + Seam --> CPU100%| JBoss.org Content Archive (Read Only)

This project is read only now. Read more.

1 2 Previous Next 19 Replies Latest reply on Oct 29, 2012 1:02 PM by stephen.bell Go to original post

15. Re: Richfaces + Seam --> CPU100%

pramod_bs Nov 23, 2009 8:22 AM (in response to pramod_bs)

Any hint for us. Our application is in PRODUCTION and when this problem occurs the whole system crawls and other applications are also affected. Any immediate solution or advise will be greatly appreciated.
Actions
16. Re: Richfaces + Seam --> CPU100%

nbelaevski Nov 23, 2009 3:57 PM (in response to pramod_bs)

Try switching on serialization for server state.
Actions
17. Re: Richfaces + Seam --> CPU100%

pramod_bs Nov 23, 2009 6:00 PM (in response to pramod_bs)

Thanks Nick. I am going to try this. I am assuming org.ajax4jsf.SERIALIZE_SERVER_STATE is the parameter.
Do you foresee any performance impact because of this. Our application response is very important.
Actions
18. Richfaces + Seam --> CPU100%

semionk Feb 14, 2011 5:51 AM (in response to pramod_bs)

we are facing same problem with SEAM 2.1.1 and richfaces 3.3.3.Final
we tried to downgrade to 3.3.2.SR1 still facing the same problem.
Does org.ajax4jsf.SERIALIZE_SERVER_STATE=true solved the problem?
Any performance issues due to this change
I will appreciate if you can update me
Actions
19. Re: Richfaces + Seam --> CPU100%

stephen.bell Oct 29, 2012 1:02 PM (in response to nbelaevski)

An impertinent question from a state of profound ignorance.

I can't recreate this at all, but one of our customers seemingly finds it fairly easy to do so. I understand that the same component object has to be accessed in two separate threads--under what circumstances would that happen? Would either the parameter org.ajax4jsf.SERIALIZE_SERVER_STATE or the patch fix the problem? Which is preferable?
Actions

1 2 Previous Next

Go to original post