|
From: Scott B. <sco...@ru...> - 2006-09-18 16:05:23
|
We've recently encountered an issue with JDK 1.5 and Spring Web Flow 1.0 RC3 in which our threads were having problems obtaining locks.[1]. We've only seen the issue in production and not in test (we're not sure why yet). The application we are having issues with is CAS[2], which has a basic web flow that for the most part merely is a GET/POST.[3] We use Web Flow to prevent the re-submission of credentials by using the back button and re-POST. To get around the locking problem we've encountered, we've temporarily modified the ConversationLockFactory to return NoOp locks (essentially disabling locking like Java 1.4 does) while we continue to investigate. Are there any significant issues with disabling locking? If not, is there another way to configure Spring Web Flow to disable locking so that we do not have to fork the code? Thanks -Scott 1. http://forum.springframework.org/showthread.php?t=29027 2. http://www.ja-sig.org/products/cas/ 3. http://developer.ja-sig.org/source/browse/jasig/cas3/cas-server-webapp/src/main/webapp/WEB-INF/login-webflow.xml?r=1.1 -- Scott Battaglia Application Developer, Architecture & Engineering Team Enterprise Systems and Services, Rutgers University v: 732.445.0097 | f: 732.445.5493 | sco...@ru... |