Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 62 by [email protected]: Number of threads keeps on
increasing during stack start and stop
http://code.google.com/p/jdiameter/issues/detail?id=62
What steps will reproduce the problem?
1. Configure diameter client. Leave the server offline.
2. Start client with method StackImpl.start(Mode mode, long timeOut,
TimeUnit timeUnit)
3. The stack is in state CONFIGURED.
4. Call StackImpl.stop(). Nothing happens.
5. If you do that in a loop, the thread (FSM peer) count goes up and never
comes down.
What is the expected output? What do you see instead?
After stop()the allocated thread pool is still active and is
not released. If the server is started all the stopped and destroyed client
threads connects to the server.
What version of the product are you using? On what operating system?
jdiameter-1.5.10
Linux
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "mobicents-all-issues-changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
