TIBCO Streaming .NET API memory usage explanation
Article ID: KB0075726
Updated On:
| Products | Versions |
|---|---|
| TIBCO Streaming | - |
Description
The TIBCO Streaming .NET API appears to leak memory.
Issue/Introduction
Streaming .NET server status method has a long timeout
Resolution
The API method to get server status opens a dedicated RPC port with a high timeout, and so the memory allocation that appears to be a leak is the accumulation of resources dedicated to RPC.
You can observe this by attempting to detect that the server has disconnected the client while the client is attempting a dequeue, and getting a null return (rather than the call blocking).
For more information see the following documentation: http://docs.streambase.com/latest/index.jsp?topic=/com.streambase.sb.ide.help/data/html/apiguide/creatingdotnetclients.html
You can observe this by attempting to detect that the server has disconnected the client while the client is attempting a dequeue, and getting a null return (rather than the call blocking).
For more information see the following documentation: http://docs.streambase.com/latest/index.jsp?topic=/com.streambase.sb.ide.help/data/html/apiguide/creatingdotnetclients.html
Feedback
Yes
No
Powered by
