Feedback
Did this article resolve your question/issue?

   

Article

Appserver Broker threads are not being released.

« Go Back

Information

 
TitleAppserver Broker threads are not being released.
URL Name000029407
Article Number000166003
EnvironmentOpenEdge-OE Development Server-Windows-Windows 32 bit
OpenEdge 9.x
OpenEdge 10.x
OpenEdge 11.x
All Operating Systems
Question/Problem Description
The AppServer broker thread count increases but does not decrease.
Steps to Reproduce
Clarifying Information
Why do AppServer Broker thread counts never decrease?
Why do AppServer Broker thread counts always increase?
Error Message
Defect/Enhancement Number
Cause
Resolution

The increase in threads is not related to the number of agents running, but rather to the number of clients that have connected to the broker. 

Each time a client connects to the broker, a client thread is dedicated to that connection. The client threads are created on-demand, and are kept in a pool.

Once a client disconnects from the broker, the client thread associated with that client is not terminated, but is returned to the pool, and is re-used by another client.

Consequently, new client threads are spawned only if all the threads in the pool are currently busy at the time a client connects.

The threads in this pool are not trimmed. 

Workaround
Notes
Last Modified Date9/13/2015 11:47 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.