Thread 2 (Thread -1208419440 (LWP 17894)):
#0 0x00a26410 in __kernel_vsyscall ()
#1 0x00604656 in epoll_wait () from /lib/libc.so.6
#2 0x00ecf6a3 in qpid::sys::Poller::wait () from /usr/lib/libqpidcommon.so.0
#3 0x00f1a445 in qpid::sys::Dispatcher::run ()
#4 0x00943e63 in qpid::client::TCPCon
Thread 2 (Thread -1208419440 (LWP 17894)):
#0 0x00a26410 in __kernel_vsyscall ()
#1 0x00604656 in epoll_wait () from /lib/libc.so.6
#2 0x00ecf6a3 in qpid::sys::Poller::wait () from /usr/lib/libqpidcommon.so.0
#3 0x00f1a445 in qpid::sys::Dispatcher::run ()
#4 0x00943e63 in qpid::client::TCPCon
On Wed, 2009-04-15 at 16:39 +0100, Gordon Sim wrote:
> Gordon Sim wrote:
> > I am seeing an automated build hang on the unit tests. It doesn't happen
> > every time or on every machine (running on RHEL5). I _believe_ it was
> > first introduced by the changes to SocketProxy in r758852[1] (can't
Gordon Sim wrote:
James Mansion wrote:
Sure you couldn't have a C API that is closely based on the MQSeries
one, with extra tweaks?
Or a C++ API that is much like the COM API from MSMQ?
Both with extensions as needed.
These are the most widely deployed existing systems. Sure you're not
goi
On Wed, 2009-04-15 at 15:37 +0100, Gordon Sim wrote:
> I don't see view this work as replacing the existing API. I think it is
> simply at a higher level of abstraction.
>
I see a role for a 'mid-level' API that provides full access to what the
protocol can do, without being tied to the protoco
I am looking for feedback on the patches provided as part of QPID-1786
[1]. As a background, these are patches to the python and java code base
which were started by Ted Ross and Rafael Schloming. They add a Java
Agent which has an API similar to the CPP agent. In addition, it
introduces the no
Unable to acknowledge messages after failover
-
Key: QPID-1816
URL: https://issues.apache.org/jira/browse/QPID-1816
Project: Qpid
Issue Type: Bug
Components: Java Client
Repor
[
https://issues.apache.org/jira/browse/QPID-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aidan Skinner updated QPID-1812:
Status: Ready To Review (was: In Progress)
> Firewall config isn't being parsed correctly
> ---
[
https://issues.apache.org/jira/browse/QPID-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aidan Skinner reassigned QPID-1812:
---
Assignee: Martin Ritchie (was: Aidan Skinner)
Hi Martin, simple fix, please review. :)
> Fir
Update Derby store to check if a queue/exchange already exists on recovery
--
Key: QPID-1815
URL: https://issues.apache.org/jira/browse/QPID-1815
Project: Qpid
Issue Typ
[
https://issues.apache.org/jira/browse/QPID-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Ritchie reassigned QPID-1814:
Assignee: Martin Ritchie
> DerbyStore is to strict, throwing constraint errors if a duplicat
DerbyStore is to strict, throwing constraint errors if a duplicate queue or
exchange is registered
--
Key: QPID-1814
URL: https://issues.apache.org/jira/browse/QPID-18
Gordon Sim wrote:
I am seeing an automated build hang on the unit tests. It doesn't happen
every time or on every machine (running on RHEL5). I _believe_ it was
first introduced by the changes to SocketProxy in r758852[1] (can't
reproduce the hang before that revision).
I can only reproduce t
Use of No Local can result in NPE after persistent message recovery
---
Key: QPID-1813
URL: https://issues.apache.org/jira/browse/QPID-1813
Project: Qpid
Issue Type: Bug
[
https://issues.apache.org/jira/browse/QPID-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699222#action_12699222
]
Carl Trieloff commented on QPID-1811:
-
probably find most of what you are needing in the
doublefox1981 wrote:
const char* host = argc>1 ? argv[1] : "127.0.0.1";
int port = argc>2 ? atoi(argv[2]) : 5672;
Connection connection;
try {
connection.open(host, port);
Session session = connection.newSession();
string request_queue = "request";
/
Alan Conway wrote:
My first impression is that there are too many steps and too many
objects involved in sending/receiving messages.
Essentially there are 3 operations:
- send a message (to somewhere)
- pull a message (from somewhere)
- register a listener to have messages pushed (from somewhe
[
https://issues.apache.org/jira/browse/QPID-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Nagy updated QPID-1811:
--
Attachment: qpidfbsdcompile.diff
Silly changes made so far, just to realize that there is no general pol
It leaves the matter of setting the AMQP_SPEC location, but at least it
installs the required library files.
I suspect we can improve on that as well...
I consistently use /usr/share/AMQP/specs for my specs directories. Maybe
the Python installs could use this directory for a 'base' spec di
Firewall config isn't being parsed correctly
Key: QPID-1812
URL: https://issues.apache.org/jira/browse/QPID-1812
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Version
Unable to compile qpid on FreeBSD
-
Key: QPID-1811
URL: https://issues.apache.org/jira/browse/QPID-1811
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.6
Environ
My first impression is that there are too many steps and too many
objects involved in sending/receiving messages.
Essentially there are 3 operations:
- send a message (to somewhere)
- pull a message (from somewhere)
- register a listener to have messages pushed (from somewhere)
We need to define
[
https://issues.apache.org/jira/browse/QPID-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699184#action_12699184
]
Martin Ritchie commented on QPID-1677:
--
Rajith, why is the setPublishMode() code in the
const char* host = argc>1 ? argv[1] : "127.0.0.1";
int port = argc>2 ? atoi(argv[2]) : 5672;
Connection connection;
try {
connection.open(host, port);
Session session = connection.newSession();
string request_queue = "request";
// Use the name of the
I am seeing an automated build hang on the unit tests. It doesn't happen
every time or on every machine (running on RHEL5). I _believe_ it was
first introduced by the changes to SocketProxy in r758852[1] (can't
reproduce the hang before that revision).
I can only reproduce the hang when runnin
doublefox1981 wrote:
i get the latest version from svn, then i build the broker and
example:request-response, after run the sample client and server, the
broker show that "Exchange not found: amq.failover
(qpid/broker/ExchangeRegistry.cpp:87)".
what's wrong with it?
Do you mean there is a debu
i get the latest version from svn, then i build the broker and
example:request-response, after run the sample client and server, the broker
show that "Exchange not found: amq.failover
(qpid/broker/ExchangeRegistry.cpp:87)".
what's wrong with it?
--
View this message in context:
http://n2.nab
i get the latest version from svn, then i build the broker and
example:request-response, after run the sample client and server, the broker
show that "Exchange not found: amq.failover
(qpid/broker/ExchangeRegistry.cpp:87)".
what's wrong with it?
--
View this message in context:
http://n2.nab
[
https://issues.apache.org/jira/browse/QPID-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Ritchie updated QPID-1809:
-
Status: Ready To Review (was: In Progress)
> SimpleACLTest..testServerPublishInvalidQueueSuccess
Provide scripts to help process the performance data
Key: QPID-1810
URL: https://issues.apache.org/jira/browse/QPID-1810
Project: Qpid
Issue Type: Improvement
Components: Java Pe
SimpleACLTest..testServerPublishInvalidQueueSuccess fails due to incorrect
exception
Key: QPID-1809
URL: https://issues.apache.org/jira/browse/QPID-1809
Project: Qpi
Garrett Smith wrote:
The Python installation instructions call for setting PYTHONPATH to the
python directory in the qpid distribution dir. That works fine.
But there's also a setup.py file, which is the standard disutils program
for building and installing Python libraries. However, it's missin
[
https://issues.apache.org/jira/browse/QPID-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved QPID-1808.
--
Resolution: Fixed
Resolved by r765092 on trunk and r765091 on the 0.5 branch.
> setup.py does not inclu
setup.py does not include mllib
---
Key: QPID-1808
URL: https://issues.apache.org/jira/browse/QPID-1808
Project: Qpid
Issue Type: Bug
Components: Python Client
Affects Versions: M4
Report
doublefox1981 wrote:
int main(int argc, char** argv) {
const char* host = argc>1 ? argv[1] : "192.168.1.233";
int port = argc>2 ? atoi(argv[2]) : 5672;
Connection connection;
try {
ConnectionSettings Setting;
Setting.host = host;
Setting.port = port;
Setting.username = "un
35 matches
Mail list logo
