[
https://issues.apache.org/jira/browse/QPID-6386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316996#comment-14316996
]
Rob Godfrey commented on QPID-6386:
-----------------------------------
Thanks - I'm running your code on my laptop against the trunk broker and not
managed to reproduce yet...
Would it also be possible for you to paste in the thread dump from your broker
showing these orphaned senders?
> IoSender thread leak
> --------------------
>
> Key: QPID-6386
> URL: https://issues.apache.org/jira/browse/QPID-6386
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.30
> Environment: java version "1.7.0_71"
> OpenJDK Runtime Environment (rhel-2.5.3.2.el6_6-x86_64 u71-b14)
> OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
> Reporter: Mark Soderquist
> Attachments: Qpid6386Bug.java
>
>
> We are running a client that opens and closes a connection for every message
> that it sends. It does this as fast as possible. When testing right after the
> server has started there is normally zero or one IoSender thread. After a
> several minutes there is always one IoSender and sometimes two. The count
> continues to increment one at a time roughly every five minutes. I've been
> running the server now for about 30 minutes with the client continually
> sending messages and we now have six "orphaned" threads. Stopping the client
> does not clear the threads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
