---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9258/#review16344
---
/trunk/qpid/cpp/src/qpid/broker/SessionAdapter.cpp
Keith Wall created QPID-4571:
Summary: Qpid client should provide a PooledConnectionFactory
rather like that of ActiveMQ
Key: QPID-4571
URL: https://issues.apache.org/jira/browse/QPID-4571
Project: Qpid
[
https://issues.apache.org/jira/browse/QPID-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574453#comment-13574453
]
Philip Harvey commented on QPID-4533:
-
The committed code has broken the ability of
So I have looked and looked...How do I tell Qpid to not listen on port 8080?
I don't see that in any config file.
Thanks
L
Rob Godfrey wrote:
There are two Qpid Brokers, one written in Java, on in C++.
The Qpid Java broker includes a web management console which by
default starts on
Thomas Pauli created QPID-4572:
--
Summary: unresolved external symbol(Duration)
Key: QPID-4572
URL: https://issues.apache.org/jira/browse/QPID-4572
Project: Qpid
Issue Type: Bug
Darryl L. Pierce created QPID-4573:
--
Summary: Provide non-blocking support for the Ruby langauge
bindings
Key: QPID-4573
URL: https://issues.apache.org/jira/browse/QPID-4573
Project: Qpid
Rajith Attapattu created QPID-4574:
--
Summary: [JMS] Deadlock involving _failoverMutex and
_messageDeliveryLock
Key: QPID-4574
URL: https://issues.apache.org/jira/browse/QPID-4574
Project: Qpid
[
https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574608#comment-13574608
]
Rajith Attapattu commented on QPID-4574:
The issue here is that the locks are
[
https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-4574:
---
Labels: deadlock (was: )
[JMS] Deadlock involving _failoverMutex and
[
https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-4574:
---
Attachment: Test_00782235.java
Reproducer supplied by Pavel Moravec.
Run the reproducer in a
[
https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574612#comment-13574612
]
Rajith Attapattu commented on QPID-4574:
{code}
diff --git
[
https://issues.apache.org/jira/browse/QPID-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574613#comment-13574613
]
Rajith Attapattu commented on QPID-4574:
The change here is that the failoverMutex
On Feb. 8, 2013, 9:35 a.m., Gordon Sim wrote:
/trunk/qpid/cpp/src/qpid/broker/SessionAdapter.cpp, line 297
https://reviews.apache.org/r/9258/diff/2/?file=256761#file256761line297
Ok, how about the following change:
settings.isTemporary = exclusive autodelete
[
https://issues.apache.org/jira/browse/QPID-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574773#comment-13574773
]
Alan Conway commented on QPID-4572:
---
Works for me. Those symbols are in libqpidmessaging.
I've been working on a fix for the blocking APIs. I found another way of
approaching the issue than to make the blocking calls non-blocking.
My first attempt is to create a new native extension to Ruby named
Qpid::Messaging::SessionDispatcher. An instance is automatically created
by
Chuck Rolke created QPID-4575:
-
Summary: Support Visual Studio 2012
Key: QPID-4575
URL: https://issues.apache.org/jira/browse/QPID-4575
Project: Qpid
Issue Type: Bug
Components: C++
[
https://issues.apache.org/jira/browse/QPID-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13575098#comment-13575098
]
Philip Harvey commented on QPID-4533:
-
The aforementioned bug is now fixed. Committed
17 matches
Mail list logo
