[JBoss JIRA] Created: (JBREM-671) serlvet invoker no longer supports leasing
by Tom Elrod (JIRA)
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.2.0.Alpha4, 2.0.0.GA (Boon)
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
18 years, 7 months
[JBoss JIRA] Created: (JBREM-655) rename server thread when new socket connection comes in
by Tom Elrod (JIRA)
rename server thread when new socket connection comes in
--------------------------------------------------------
Key: JBREM-655
URL: http://jira.jboss.com/jira/browse/JBREM-655
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: transport
Affects Versions: 2.2.0.Alpha4, 1.4.5.GA, 2.0.0.GA (Boon), 1.4.4.GA, 1.4.3.GA
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
The ServerThread used to process incoming client requests for the socket server invoker will name the thread based on client address associated with socket connection. However, this address is not updated after the initial client request, so if the server thread is woken up and given a different client socket connection, will not re-name to the client address of for the new socket connection.
--
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
18 years, 7 months