[jboss-jira] [JBoss JIRA] Commented: (JBREM-671) serlvet invoker no longer supports leasing
[ http://jira.jboss.com/jira/browse/JBREM-671?page=comments#action_12351085 ]
Tom Elrod commented on JBREM-671:
----------------------------------
This has been fixed (behavior is basically the same as in coyote invoker) so that will
first check the request to see if is indeed a request for lease info. If it is, package
invocation request as a $PING$ invocation request to be sent onto ServerInvoker where will
get if leasing is turned on, and if so, what the default lease period should be. Will
include this info in the http response.
Although not automated, the test case can be found within
org.jboss.test.remoting.lease.servlet package. The readme.txt will walk through how to
setup the test.
serlvet invoker no longer supports leasing
------------------------------------------
Key: JBREM-671
URL: http://jira.jboss.com/jira/browse/JBREM-671
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 2.0.0.GA (Boon), 2.2.0.Alpha4
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
A while back, the leasing when using an http transport changed to query server via HEAD
http method call instead of making a formal invocation to get the leasing info from the
remoting server (i.e. if leasing was turned on, what the default lease period should be,
etc.). These changes were made to the http client invoker and http/coyote server invoker,
but not to the web server invoker (which is what is used for servlet server invoker).
Therefore, leasing is basically broken when using servlet invoker.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira