Re: [Asterisk-java-devel] ServiceLevelTimer problem

[Brett S. <bs...@no...>]

Not certain about the threads with asteriskjava live but just a note of 
caution. You want to minimise the number of connections to asterisk. 
Generally you should just have a single connection (which actually 
results in two open sockets (reader and a writer)) which you keep open 
(you need to handle disconnects).

Brett



On 11/10/12 16:17, Videanu Adrian wrote:
> Hi all,
> I develop a application using asteriskJava, running on glassfish and i encountered some issues related to the number of threads opened every time i connect to asterisk server.
> So, my setup is as follows:
> 1. i connect to the asterisk server using the live class AsteriskServer asteriskServer = new DefaultAsteriskServer(user,pass....)
> 2. after the connection is done I observed a number of threads equal to the number of my queues (from asterisk) opened, with names like ServiceLevelTimer-QueueName
>
> I thought that when i access asteriskServer.shutdown() these threads will be closed automatically, but this is not happening.
> Is this the expected behavior or this a bug ?
>
> I have to mention that i do not have any class that implements AsteriskQueueListener.
>
> PS. my situation is even more complicated because i perform a lot of connect/disconnect cycles and i end up with a lot of threads with status waiting.
>
> Regards,
> Adrian Videanu
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> Asterisk-java-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/asterisk-java-devel