jsf - ViewExpiredException after upgrade to jsf2 -

-

we upgraded major platform jsf 1.2 2.0. after upgrading we're getting several viewexpiredexception errors each hour. reading on topic seems expected exception when sessions expire, we've reviewed access logs , getting these exceptions when requests 5 minutes apart in cases.

my questions follows:

1) other session expiration, other conditions might cause viewexpiredexception?

2) exception we're logging doesn't contain detail exact condition causing exception (missing session, corrupt session, unable restore particular component). there way introduce additional logging find out specific situation triggering exception in each case?

mojarra 2.0.4-b09 tomcat 6 using memcached session manager session replication

any appreciated. thanks!

other session expiration, other conditions might cause viewexpiredexception?

the enduser has requested/created views within session , submitting old view. default max views per session 15. in other words, if enduser opens 16 browser windows/tabs on page form within same session , submits first one, user can viewexpiredexception.

the max views per session configureable in web.xml 

<context-param>     <param-name>com.sun.faces.numberofviewsinsession</param-name>     <param-value>15</param-value> </context-param>

see mojarra faq other parameters.

is there way introduce additional logging find out specific situation triggering exception in each case?

not through jsf and/or viewexpiredexception. whole exception means view not present in session anymore. can in turn indeed have more underlying causes. logging session creation , destroy using httpsessionlistener , logging session attribute modifications httpsessionattributelistener may helpful.

update per comments, pressing browser button on cached page containing form , submitting form thereafter indeed cause viewexpiredexception when view been expired. can solved in following 2 ways, preferably in combination of them:

  • instruct browser not cache pages.
  • do not use post forms plain page-to-page navigation.

for more detail, see this answer.


Comments

Post a Comment

Popular posts from this blog

php - What is the difference between $_SERVER['PATH_INFO'] and $_SERVER['ORIG_PATH_INFO']? -

-
what’s difference between $_server['path_info'] , $_server['orig_path_info'] ? how use them? when run print_r($_server) , path_info , orig_path_info not present in array. why not? how can enable them? i have read php manual on them, still don’t understand them. the path_info variable present if invoke php script this: http://www.example.com/phpinfo.php/hello_there it's /hello_there part after .php script. if don't invoke url that, there won't $_server["path_info"] environment variable. the porig_ prefix uncommon. path_info standard cgi-environment variable, , should never prefixed. did read that? (there issues around php3/php4 if invoked php interpreter via cgi-bin/ - hardly has such setups today.) for reference: http://www.ietf.org/rfc/rfc3875
Read more

fortran - Function return type mismatch -

-
i'm attempting recode old c++ program in fortran make use of lapack (i'm aware c++ have lapack++, i'm having lot of trouble installing it, gave up). i didn't have problems compilation, when had variables declared real . when started coding section of program required lapack, found parameters passed dsyev need double precision . tried change double precision (including changing hard coded numbers double precision counterparts, i.e. 0.0 -> 0.0d0) when try compile, following error of functions , subroutines i've written: error: return type mismatch of function <function> @ (1) (real(4)/real(8)) i'm not sure coming from, in program has been changed double precision. for example, i've declared following: double precision :: alpha(3),d(3),zeta1,zeta2 double precision :: a1(3),a2(3),d1(3),d2(3) double precision :: pi pi = 3.14159265359d0 alpha = (/0.109818d0, 0.405771d0, 2.22766d0/) d = (/0.444635d0, 0.535328d0, 0.154329d0 /) 10 i=1,3 ...
Read more

queue - mq_receive: message too long -

-
i implementing communication between 2 processes using queue. problem when call function mq_receive, error: message long. i have done following: struct mq_attr attr; long size = attr.mq_msgsize; .... // initializing queue "/gateway" int rc = mq_receive(gateway, buffer, size, &prio); if print size value, size=1, while when print same size program (got same mechanism), not long integer ( -1217186280 )... how can solve error?....so while size = 1, believe it's right "message long" why 1? p.s. have tried put : int rc = mq_receive(gateway, buffer, sizeof(buffer), &prio); but no result. it seems need read docs more carefully. when call mq_receive should pass size of destination buffer. this size must greater mq_msgsize attribute of queue . in addition, seems have error in queue attributes initialisation makes proper mq_receive call impossible. here standard message queue session: fill mq_attr struct ( doc ): struct mq_a...
Read more