Overview of service and endpoint listeners
We can use the dmgr to control throughput by starting and stopping individual service listeners and endpoint listeners. When we stop a service listener, this causes any associated endpoint listeners to stop listening to any new inbound requests and the application server rejects any new incoming requests for that service. Additionally, resources become free used to service requests that are already being processed for the service or to service new incoming requests for other services.
- Service listener
The service listener can be started or stopped. When a service listener is stopped, all the endpoints for the service are stopped and new inbound requests are no longer processed. The endpoints for the service send out 404 error message response code to indicate that the service listener is currently stopped and cannot service new inbound requests. When the service listener is started, all the endpoints for the service resume processing of new inbound requests.
- Endpoint listener
The endpoint listener can be started or stopped. When a service endpoint listener is stopped, the specific endpoint stops listening to any new inbound request. The requests that are already being processed are not affected. The endpoint sends out a 404 error message response code to indicate that the endpoint is currently stopped and cannot service a new, inbound request. When the endpoint listener is started, the specific endpoint resumes listening on new inbound requests. The state of a particular service endpoint does not impact the listening function of other endpoints for the same service.
Related:
JAX-WS application packaging Web services View service clients at the application level Deploy and administering enterprise applications Artifacts used to develop web services