When creating a new CTI connection in JTAPI, there are several threads that are created. These threads remain, even after the ProviderObserver has been removed from the Provider object and the Provider is set to null. As new cti connections are created, these outstanding threads eventually cause the application to run out of memory and crash. Is there a way to clean up the Provider object such that these threads are released?

The threads in question have the following signatures:

AvayaJTAPIThread(DistributeCSTAEvent)]
AvayaJTAPIThread(GetCstaEventThread)]
AvayaJTAPIThread(AuditThread)]

Russel,

Would you mind opening a trouble ticket with technical support for this problem? There is a "Request Technical Support" link for this in the left-hand frame of this page.

I apologize for having to redirect you, but the above issue will take some more attention to resolve, and this forum is generally not attended by JTAPI / TSAPI experts.


Best regards, and again my regrets for not being able to help out here,

Tim