Memory leak in Avaya JTAPI

Hi,

we are facing a memory leak problem with the Avaya JTAPI 3.1.0 and would
like to know if anybody else already had such problems, too.

We wrote a test application which proves the memory leak (in our
opinion). The application gets a Provider, gets all ACDAddresses from
the provider and adds an Observer to each of them, gets all terminals
from the provider and adds a CallObserver to each of them, and then just
listens for the events (which are simply logged) until memory runs out.

By profiling and decompiling the hidden implementation of Avaya we found
  out that the backing Provider implementation has some Hashtables which
are increasing but never decrease to the same degree. We think this is
the cause for the memory leak.

We are using the same basic functions (observers on ACDAddress and
Terminal) in a production environment and have to restart the
application every night.

Any feedback concerning this issue is welcome.

Best regards
Achim

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JTAPI-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".