QPID Threading model?

Hi, how does it works behind scenes in QPID? I got some idea, that each connection has own thread or thread from pool, to handle incoming/outgoing messages. But is it only one for transmission and reception as well? Where the threads are created? I got through code in C++, and have to admit, that

[jira] [Commented] (QPID-7159) [Java Client] Disabling user ids in AMQP messages

[ https://issues.apache.org/jira/browse/QPID-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235574#comment-15235574 ] ASF subversion and git services commented on QPID-7159: --- Commit 17386

[jira] [Created] (DISPATCH-273) The entity view is missing information for some entities

Ernest Allen created DISPATCH-273: - Summary: The entity view is missing information for some entities Key: DISPATCH-273 URL: https://issues.apache.org/jira/browse/DISPATCH-273 Project: Qpid Dispatch

[jira] [Created] (DISPATCH-272) Re-enable the connection cross-section popup

Ernest Allen created DISPATCH-272: - Summary: Re-enable the connection cross-section popup Key: DISPATCH-272 URL: https://issues.apache.org/jira/browse/DISPATCH-272 Project: Qpid Dispatch Issu

[jira] [Created] (DISPATCH-271) Handle single router

Ernest Allen created DISPATCH-271: - Summary: Handle single router Key: DISPATCH-271 URL: https://issues.apache.org/jira/browse/DISPATCH-271 Project: Qpid Dispatch Issue Type: Bug Co

[jira] [Commented] (QPID-7159) [Java Client] Disabling user ids in AMQP messages

[ https://issues.apache.org/jira/browse/QPID-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235560#comment-15235560 ] ASF subversion and git services commented on QPID-7159: --- Commit 17386

[jira] [Updated] (QPID-7189) [Java Client 0-8..0-10] Client fails to create delegate for AMQP 0.9.1 in response to broker supported protocol received during protocol negotiation

[ https://issues.apache.org/jira/browse/QPID-7189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7189: - Summary: [Java Client 0-8..0-10] Client fails to create delegate for AMQP 0.9.1 in response to broker suppo

[jira] [Resolved] (QPID-7136) [Java Broker] [BDB HA] [AMQP 1.0] Connection to a replica throws an uncaught exception which closes the broker

[ https://issues.apache.org/jira/browse/QPID-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7136. -- Resolution: Fixed > [Java Broker] [BDB HA] [AMQP 1.0] Connection to a replica throws an uncaught > excep

[jira] [Commented] (QPID-7136) [Java Broker] [BDB HA] [AMQP 1.0] Connection to a replica throws an uncaught exception which closes the broker

[ https://issues.apache.org/jira/browse/QPID-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235551#comment-15235551 ] Keith Wall commented on QPID-7136: -- Changes look reasonable to me. > [Java Broker] [BDB H

[jira] [Updated] (QPID-7132) qpid-server does not properly quote dirname $0 argument

[ https://issues.apache.org/jira/browse/QPID-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7132: - Status: Reviewable (was: In Progress) > qpid-server does not properly quote dirname $0 argument >

[jira] [Commented] (DISPATCH-263) Router crash when requesting log

[ https://issues.apache.org/jira/browse/DISPATCH-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235537#comment-15235537 ] Ernest Allen commented on DISPATCH-263: --- Additional Info: In the above crashes, I

[jira] [Updated] (QPID-7132) qpid-server does not properly quote dirname $0 argument

[ https://issues.apache.org/jira/browse/QPID-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7132: - Assignee: Alex Rudyy (was: Keith Wall) > qpid-server does not properly quote dirname $0 argument > ---

[jira] [Updated] (QPID-7132) qpid-server does not properly quote dirname $0 argument

[ https://issues.apache.org/jira/browse/QPID-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7132: - Assignee: Alex Rudyy > qpid-server does not properly quote dirname $0 argument > --

[jira] [Assigned] (QPID-7132) qpid-server does not properly quote dirname $0 argument

[ https://issues.apache.org/jira/browse/QPID-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7132: Assignee: Keith Wall (was: Alex Rudyy) > qpid-server does not properly quote dirname $0 argument >

[jira] [Commented] (QPID-7181) [AMQP 1.0] Selector parsing error causes Java Broker to shutdown

[ https://issues.apache.org/jira/browse/QPID-7181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235527#comment-15235527 ] ASF subversion and git services commented on QPID-7181: --- Commit 17386

[jira] [Resolved] (QPID-7181) [AMQP 1.0] Selector parsing error causes Java Broker to shutdown

[ https://issues.apache.org/jira/browse/QPID-7181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7181. -- Resolution: Fixed > [AMQP 1.0] Selector parsing error causes Java Broker to shutdown > --

[jira] [Commented] (QPID-7181) [AMQP 1.0] Selector parsing error causes Java Broker to shutdown

[ https://issues.apache.org/jira/browse/QPID-7181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235521#comment-15235521 ] Keith Wall commented on QPID-7181: -- I don't see a way to configure JavaCC to avoid the ugl

[jira] [Updated] (QPID-7155) [Java Broker] Idle timeout ticker times out connection before heartbeating is negotiated

[ https://issues.apache.org/jira/browse/QPID-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7155: - Priority: Minor (was: Major) > [Java Broker] Idle timeout ticker times out connection before heartbeating

[jira] [Updated] (QPID-7155) [Java Broker] Idle timeout ticker times out connection before heartbeating is negotiated

[ https://issues.apache.org/jira/browse/QPID-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7155: - Assignee: Alex Rudyy (was: Keith Wall) > [Java Broker] Idle timeout ticker times out connection before hea

[jira] [Updated] (QPID-7155) [Java Broker] Idle timeout ticker times out connection before heartbeating is negotiated

[ https://issues.apache.org/jira/browse/QPID-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7155: - Status: Reviewable (was: In Progress) > [Java Broker] Idle timeout ticker times out connection before hear

[jira] [Assigned] (QPID-7155) [Java Broker] Idle timeout ticker times out connection before heartbeating is negotiated

[ https://issues.apache.org/jira/browse/QPID-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7155: Assignee: Keith Wall > [Java Broker] Idle timeout ticker times out connection before heartbeating is

[jira] [Commented] (QPID-7155) [Java Broker] Idle timeout ticker times out connection before heartbeating is negotiated

[ https://issues.apache.org/jira/browse/QPID-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235475#comment-15235475 ] ASF subversion and git services commented on QPID-7155: --- Commit 17386

[jira] [Commented] (QPID-7159) [Java Client] Disabling user ids in AMQP messages

[ https://issues.apache.org/jira/browse/QPID-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235408#comment-15235408 ] Keith Wall commented on QPID-7159: -- Changes look reasonable to me. > [Java Client] Disabl

[jira] [Commented] (DISPATCH-263) Router crash when requesting log

[ https://issues.apache.org/jira/browse/DISPATCH-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235362#comment-15235362 ] Ernest Allen commented on DISPATCH-263: --- Yes, I'm still seeing a crash after updat

[jira] [Closed] (DISPATCH-270) Specifying a maxSessions limit of 1 allows unlimited sessions

[ https://issues.apache.org/jira/browse/DISPATCH-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke closed DISPATCH-270. Resolution: Won't Fix Fix Version/s: 0.6 Dispatch is doing the right thing. However, based

[jira] [Resolved] (QPID-7154) Dead lettering of a message may timeout at store level, causing unexpected Broker shutdown

[ https://issues.apache.org/jira/browse/QPID-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7154. -- Resolution: Fixed > Dead lettering of a message may timeout at store level, causing unexpected > Broker

[jira] [Updated] (QPID-7154) Dead lettering of a message may timeout at store level, causing unexpected Broker shutdown

[ https://issues.apache.org/jira/browse/QPID-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7154: - Fix Version/s: qpid-java-6.1 > Dead lettering of a message may timeout at store level, causing unexpected

[jira] [Commented] (QPID-7154) Dead lettering of a message may timeout at store level, causing unexpected Broker shutdown

[ https://issues.apache.org/jira/browse/QPID-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234985#comment-15234985 ] ASF subversion and git services commented on QPID-7154: --- Commit 17385

[jira] [Updated] (QPID-7194) Give client an ordered preferences to drive AMQP protocol selection

[ https://issues.apache.org/jira/browse/QPID-7194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-7194: -- Summary: Give client an ordered preferences to drive AMQP protocol selection (was: Given client an order

[jira] [Updated] (QPID-7192) [Java Broker] BDB HA Virtual Host Node does not restart successfully if JE environment has locally committed transactions requiring rollback

[ https://issues.apache.org/jira/browse/QPID-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7192: - Attachment: QPID-7192-wip.diff > [Java Broker] BDB HA Virtual Host Node does not restart successfully if JE

[jira] [Updated] (QPID-7192) [Java Broker] BDB HA Virtual Host Node does not restart successfully if JE environment has locally committed transactions requiring rollback

[ https://issues.apache.org/jira/browse/QPID-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7192: - Attachment: (was: QPID-7192-wip.diff) > [Java Broker] BDB HA Virtual Host Node does not restart success

[jira] [Updated] (QPID-7192) [Java Broker] BDB HA Virtual Host Node does not restart successfully if JE environment has locally committed transactions requiring rollback

[ https://issues.apache.org/jira/browse/QPID-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7192: - Description: Start-up of BDB HA VHN fails in the following scenario: 1) When Transaction on Master node is

[jira] [Created] (QPID-7194) Given client an ordered preferences to drive AMQP protocol selection

Keith Wall created QPID-7194: Summary: Given client an ordered preferences to drive AMQP protocol selection Key: QPID-7194 URL: https://issues.apache.org/jira/browse/QPID-7194 Project: Qpid Issu

[jira] [Commented] (QPID-7193) Make legacy client fail in clear manner when connecting to a peer that replies AMQP 1.0

[ https://issues.apache.org/jira/browse/QPID-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234835#comment-15234835 ] Keith Wall commented on QPID-7193: -- The currently problem is that the protocol specific pa

[jira] [Updated] (QPID-7193) Make legacy client fail in clear manner when connecting to a peer that replies AMQP 1.0

[ https://issues.apache.org/jira/browse/QPID-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7193: - Fix Version/s: qpid-java-6.1 > Make legacy client fail in clear manner when connecting to a peer that > re

[jira] [Updated] (QPID-7188) [Java Broker] [AMQP1.0] Define a target capability to define how a target will respond when receiving a message it cannot route

[ https://issues.apache.org/jira/browse/QPID-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7188: - Fix Version/s: qpid-java-6.1 > [Java Broker] [AMQP1.0] Define a target capability to define how a target >

[jira] [Commented] (QPIDJMS-169) SASL Plain Mechanism should be enforcing UTF-8 encoding

[ https://issues.apache.org/jira/browse/QPIDJMS-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234677#comment-15234677 ] Keith Wall commented on QPIDJMS-169: Robbie/Tim, Thanks for the replies, I withdraw