> When the time expired I still see the thread in server.
I'm not sure I quite understand you... the timeout tells a cleaning thread how long it should keep script session objects since they were last touched before invalidating them and discarding them. The thread will always exist.
2009/6/16 Jian-zhi
<Jian-zhi.Wang@...>
I try to use DWR 2.0.5 with reverse feature.
But after I set the scriptSessionTimeout parameter it does not work.
When the time expired I still see the thread in server.
My web.xml settings is below:
<servlet>
<servlet-name>dwr-invoker</servlet-name>
<servlet-class>org.directwebremoting.servlet.DwrServlet</servlet-class>
<init-param>
<param-name>scriptSessionTimeout</param-name>
<param-value>30000</param-value>
</init-param>
<init-param>
<param-name>activeReverseAjaxEnabled</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>initApplicationScopeCreatorsAtStartup</param-name>
<param-value>true</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
Any one any comments about it?
--
View this message in context: http://www.nabble.com/Why-does-scriptSessionTimeout-parameter-not-work-in-DWR-2.0.5---tp24051051p24051051.html
Sent from the DWR - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
