Index Changes

Difference between version and version     

Back to HTTPBC Throttling, or HTTPBC Throttling Info


At line 6 changed 2 lines.
! Extending Grizzly to Add Throttling
The HTTP/SOAP BC uses the Grizzly/JAX-WS stack. Grizzly handles the HTTP protocol and thus the only way to achieve a viable throttling solution was to extend Grizzly to handle how requests are read off the wire and possibly suspend requests when deemed necessary. Requests that are suspended are re-evaulated at a later time to determine whether the target endpoints are ready to handle the requests; if so, then the requests are resumed for processing as usual. To extend Grizzly, its Pipeline implementation, com.sun.enterprise.web.connector.grizzly.LinkedListPipeline, was extended and the addTask(Task) method was overriden. The extended class is called LinkedListThrottlePipeline, in the package com.sun.jbi.httpsoapbc.embedded. In the overriden addTask(Task) method, the following strategy is taken:
! Extending Grizzly to Handle Request Throttling
The HTTP/SOAP BC uses the Grizzly/JAX-WS stack. [Grizzly|https://grizzly.dev.java.net/] handles the HTTP protocol and thus the only way to achieve a viable throttling solution was to extend Grizzly to handle how requests are read off the wire and possibly suspend requests when deemed necessary. Requests that are suspended are re-evaulated at a later time to determine whether the target endpoints are ready to handle the requests; if so, then the requests are resumed for processing as usual. To extend Grizzly, its Pipeline implementation, com.sun.enterprise.web.connector.grizzly.LinkedListPipeline, was extended and the addTask(Task) method was overriden. The extended class is called LinkedListThrottlePipeline, in the package com.sun.jbi.httpsoapbc.embedded. In the overriden addTask(Task) method, the following strategy is taken:
At line 17 changed 1 line.
Work is underway to incorporate LinkedListThrottlePipeline into Grizzly such that it can be extensible in allowing custom throttling policies to be implemented. The goal is to have this functionality ready in the next Grizzly's release (or hopefully a patch) so that the HTTP/SOAP BC make use of it in the future release.
Work is underway to incorporate LinkedListThrottlePipeline into Grizzly such that it can be extensible in allowing custom throttling policies to be implemented. The goal is to have this functionality ready in the next Grizzly's release (or hopefully a patch) so that the HTTP/SOAP BC make use of it in the future release. Sources for this can be viewed here - [https://grizzly.dev.java.net/source/browse/grizzly/trunk/contribs/grizzly1_0/pipelines/requests-throttling/src/main/java/com/sun/grizzly/pipeline].
At line 63 changed 1 line.
In this example, the ''request URI'' is "/PassThruService/PassThruPort". The HTTP/SOAP BC uses these pieces of information when applying throttling policy on each of the endpoints.
In this example, the ''request URI'' is "/PassThruService/PassThruPort". The HTTP/SOAP BC pieces all these information together and use it when applying throttling policy on each of the endpoints.

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-9) was last changed on 07-Mar-08 14:18 PM, -0800 by jamestran