[jira] [Created] (QPID-4425) Possible incorrect error reporting "Error locking blob area for persistable item"
Alexey Sviridov created QPID-4425:
-
Summary: Possible incorrect error reporting "Error locking blob
area for persistable item"
Key: QPID-4425
URL: https://issues.apache.org/jira/browse/QPID-4425
Project: Qpid
Issue Type: Improvement
Components: C++ Broker
Affects Versions: 0.18
Environment: Windows
Reporter: Alexey Sviridov
Priority: Trivial
In mssql_store module class BlobEncoder has incorrect error reporting.
In code bellow
{code:title=BlobEncoder.cpp}
blob = SafeArrayCreate(VT_UI1, 1, bound);
if (S_OK != SafeArrayLock(blob)) {
SafeArrayDestroy(blob);
blob = 0;
throw qpid::Exception("Error locking blob area for persistable item");
}
{code}
Exception "Error locking blob area for persistable item" hides possible error
in SafeArrayCreate (which is more likely to be happen, cause SafeArrayCreate
can fail on out of memory)
In module BlobEncoder.cpp three similar methods. (BTW may be it's need some
refactoring to follow DRY principe& :) )
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3027) PHP binding of Qpid Messaging API
[ https://issues.apache.org/jira/browse/QPID-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491939#comment-13491939 ] Paul Colby commented on QPID-3027: -- bq. No, that was a mistake. I must have selected the description by accident while adding my comment yesterday. No problem. I've very nearly done the same thing a few times. I've restored the original description from the history tab (not that I would have been upset if you'd removed it intentionally either). bq. Do you feel this is a work in progress or is the patch close to if not totally working at this point? I'd say "close to if not totally working at this point". Both the cqpid and cqmf2 PHP modules should be fully working, there's just a few areas (particularly in cqmf2) that I've never used, thus never tested. For example, while I have tested the QMF2 client support, I've never tried writing a QMF2 agent in PHP... _should_ work though. > PHP binding of Qpid Messaging API > - > > Key: QPID-3027 > URL: https://issues.apache.org/jira/browse/QPID-3027 > Project: Qpid > Issue Type: New Feature > Components: C++ Client >Affects Versions: 0.8 >Reporter: Paul Colby >Assignee: Darryl L. Pierce > Attachments: cqpid_php.20110220.diff, cqpid_php.20110301.diff, > cqpid_php.20110328.diff, cqpid_php.20110415.diff, cqpid_php.20120406.diff, > cqpid_php.20121105.diff, cqpid_php.20121105-qpid-0.19.diff, > cqpid_php.20121106.diff, cqpid_php.diff, FindPHPDev.cmake, Makefile > > > Working on a PHP binding for the Qpid Messaging API via SWIG. There are > several PHP-specific issues with C++ and SWIG which I've managed to > workaround, so the binding is starting to take shape, but still very much a > work in progress. > The rough plan: > 1. report relevant bugs / feature requests to SWIG (done). > 2. clean-up Qpid php.i SWIG interface file (mostly done - just need to > implement PHP namespaces). > 3. implement qpid::types::Variant <-> PHP typemapping (not started). > 4. implement printinfo pragma (should be easy, just need to choose what info > to include). > 5. create relevant [auto]makefile. > Of course, there's lots of things to discuss / decide along the way... so > I'll post 'em here as they come up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3027) PHP binding of Qpid Messaging API
[ https://issues.apache.org/jira/browse/QPID-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Colby updated QPID-3027: - Description: Working on a PHP binding for the Qpid Messaging API via SWIG. There are several PHP-specific issues with C++ and SWIG which I've managed to workaround, so the binding is starting to take shape, but still very much a work in progress. The rough plan: 1. report relevant bugs / feature requests to SWIG (done). 2. clean-up Qpid php.i SWIG interface file (mostly done - just need to implement PHP namespaces). 3. implement qpid::types::Variant <-> PHP typemapping (not started). 4. implement printinfo pragma (should be easy, just need to choose what info to include). 5. create relevant [auto]makefile. Of course, there's lots of things to discuss / decide along the way... so I'll post 'em here as they come up. was: > PHP binding of Qpid Messaging API > - > > Key: QPID-3027 > URL: https://issues.apache.org/jira/browse/QPID-3027 > Project: Qpid > Issue Type: New Feature > Components: C++ Client >Affects Versions: 0.8 >Reporter: Paul Colby >Assignee: Darryl L. Pierce > Attachments: cqpid_php.20110220.diff, cqpid_php.20110301.diff, > cqpid_php.20110328.diff, cqpid_php.20110415.diff, cqpid_php.20120406.diff, > cqpid_php.20121105.diff, cqpid_php.20121105-qpid-0.19.diff, > cqpid_php.20121106.diff, cqpid_php.diff, FindPHPDev.cmake, Makefile > > > Working on a PHP binding for the Qpid Messaging API via SWIG. There are > several PHP-specific issues with C++ and SWIG which I've managed to > workaround, so the binding is starting to take shape, but still very much a > work in progress. > The rough plan: > 1. report relevant bugs / feature requests to SWIG (done). > 2. clean-up Qpid php.i SWIG interface file (mostly done - just need to > implement PHP namespaces). > 3. implement qpid::types::Variant <-> PHP typemapping (not started). > 4. implement printinfo pragma (should be easy, just need to choose what info > to include). > 5. create relevant [auto]makefile. > Of course, there's lots of things to discuss / decide along the way... so > I'll post 'em here as they come up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4424) C++ Broker on Windows - Assertion Failed: !dispatcher - PollableQueue.h line 136
Chuck Rolke created QPID-4424:
-
Summary: C++ Broker on Windows - Assertion Failed: !dispatcher -
PollableQueue.h line 136
Key: QPID-4424
URL: https://issues.apache.org/jira/browse/QPID-4424
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.18
Environment: Windows Server 2008 R2 64-bit system
Visual Studio 2010 32-bit executable
Reporter: Chuck Rolke
Start broker with 'qpidd --auth no --no-data-dir'.
Sit for 15 or so seconds. No external connections from clients. No cluster.
Assert happens.
Stack at assert time:
msvcr100d.dll!_NMSG_WRITE(int rterrnum=10) Line 217C
msvcr100d.dll!abort() Line 61 + 0x7 bytes C
msvcr100d.dll!_wassert(const wchar_t * expr=0x5ff25504, const wchar_t *
filename=0x5ff25480, unsigned int lineno=136) Line 153 C
>
> qpidbrokerd.dll!qpid::sys::PollableQueue,qpid::broker::Message>
> >::dispatch(qpid::sys::PollableCondition & cond={...}) Line 136 + 0x36
> bytes C++
qpidbrokerd.dll!boost::_mfi::mf1,qpid::broker::Message>
>,qpid::sys::PollableCondition
&>::operator()(qpid::sys::PollableQueue,qpid::broker::Message>
> * p=0x00c72b80, qpid::sys::PollableCondition & a1={...}) Line 165 + 0x10
bytes C++
qpidbrokerd.dll!boost::_bi::list2,qpid::broker::Message>
> *>,boost::arg<1>
>::operator(),qpid::broker::Message>
>,qpid::sys::PollableCondition
&>,boost::_bi::list1 >(boost::_bi::type
__formal={...},
boost::_mfi::mf1,qpid::broker::Message>
>,qpid::sys::PollableCondition &> & f={...},
boost::_bi::list1 & a={...},
boost::_bi::type __formal={...}) Line 314C++
qpidbrokerd.dll!boost::_bi::bind_t,qpid::broker::Message>
>,qpid::sys::PollableCondition
&>,boost::_bi::list2,qpid::broker::Message>
> *>,boost::arg<1> >
>::operator()(qpid::sys::PollableCondition &
a1={...}) Line 33 C++
qpidbrokerd.dll!boost::detail::function::void_function_obj_invoker1,qpid::broker::Message>
>,qpid::sys::PollableCondition
&>,boost::_bi::list2,qpid::broker::Message>
> *>,boost::arg<1> > >,void,qpid::sys::PollableCondition
&>::invoke(boost::detail::function::function_buffer & function_obj_ptr={...},
qpid::sys::PollableCondition & a0={...}) Line 154 C++
qpidcommond.dll!boost::function1::operator()(qpid::sys::PollableCondition & a0={...}) Line 760 + 0x1a bytes
C++
qpidcommond.dll!qpid::sys::PollableConditionPrivate::dispatch(qpid::sys::windows::AsynchIoResult
* result=0x00cad6e0) Line 81 C++
qpidcommond.dll!boost::_mfi::mf1::operator()(qpid::sys::PollableConditionPrivate * p=0x00c72cd0,
qpid::sys::windows::AsynchIoResult * a1=0x00cad6e0) Line 165 + 0x10 bytes
C++
qpidcommond.dll!boost::_bi::list2,boost::arg<1>
>::operator(),boost::_bi::list1
>(boost::_bi::type __formal={...},
boost::_mfi::mf1 & f={...}, boost::_bi::list1 &
a={...}, boost::_bi::type __formal={...}) Line 314 C++
qpidcommond.dll!boost::_bi::bind_t,boost::_bi::list2,boost::arg<1> > >::operator()(qpid::sys::windows::AsynchIoResult * & a1=0x00cad6e0) Line 33 C++
qpidcommond.dll!boost::detail::function::void_function_obj_invoker1,boost::_bi::list2,boost::arg<1> > >,void,qpid::sys::windows::AsynchIoResult
*>::invoke(boost::detail::function::function_buffer & function_obj_ptr={...},
qpid::sys::windows::AsynchIoResult * a0=0x00cad6e0) Line 154C++
qpidcommond.dll!boost::function1::operator()(qpid::sys::windows::AsynchIoResult * a0=0x00cad6e0) Line 760 +
0x1a bytes C++
qpidcommond.dll!qpid::sys::windows::AsynchCallbackRequest::complete()
Line 189 C++
qpidcommond.dll!qpid::sys::windows::AsynchResult::success(unsigned int
bytesTransferred=0) Line 57 + 0xf bytes C++
qpidcommond.dll!qpid::sys::Poller::wait(qpid::sys::Duration
timeout={...}) Line 196 + 0x12 bytes C++
qpidcommond.dll!qpid::sys::Poller::run() Line 118 C++
qpidcommond.dll!qpid::sys::Dispatcher::run() Line 37 + 0x1d bytes
C++
qpidbrokerd.dll!qpid::broker::Broker::run() Line 429 + 0xb bytes
C++
qpidd.exe!qpid::broker::QpiddBroker::execute(qpid::broker::QpiddOptions
* options=0x00c5b818) Line 481 + 0x26 bytesC++
qpidd.exe!qpid::broker::run_broker(int argc=4, char * *
argv=0x00c519f8, bool hidden=false) Line 106 + 0x16 bytes C++
qpidd.exe!main(int argc=4, char * * argv=0x00c519f8) Line 507 + 0xf
bytes C++
qpidd.exe!__tmainCRTStartup() Line 555 + 0x19 bytesC
qpidd.exe!mainCRTStartup() Line 371C
kernel32.dll!75d333aa()
[Frames below may be incorrect and/or missing, no symbols loaded for
kernel32.dll]
ntdll.dll!770c9ef2()
ntdll.dll!770c9ec5()
--
This message is automatically generated by JIRA.
If you think it was sent incor
Re: Review Request: C++ Broker should not declare existing federated queues during bridge creation
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/7901/#review13172 --- Look sensible, but what is the problem that prompted this patch? - Alan Conway On Nov. 6, 2012, 7:20 p.m., Chug Rolke wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/7901/ > --- > > (Updated Nov. 6, 2012, 7:20 p.m.) > > > Review request for qpid and Alan Conway. > > > Description > --- > > This patch conditionalizes the queue declaration during bridge creation. The > queue is declared only if there is no existing queue, which is when the > supplied queue name is blank. > > > This addresses bug QPID-4423. > https://issues.apache.org/jira/browse/QPID-4423 > > > Diffs > - > > trunk/qpid/cpp/src/qpid/broker/Bridge.cpp 1406267 > > Diff: https://reviews.apache.org/r/7901/diff/ > > > Testing > --- > > This passes federation 'make test' testing. > > > Thanks, > > Chug Rolke > >
[jira] [Comment Edited] (QPID-3027) PHP binding of Qpid Messaging API
[ https://issues.apache.org/jira/browse/QPID-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491486#comment-13491486 ] Darryl L. Pierce edited comment on QPID-3027 at 11/6/12 8:50 PM: - No, that was a mistake. I must have selected the description by accident while adding my comment yesterday. My apologies. I'll apply and build the 20121106 patch in my development repo and give it some preliminary testing. Do you feel this is a work in progress or is the patch close to if not totally working at this point? was (Author: mcpierce): No, that was a mistaken. I must have selected the description by accident while adding my comment yesterday. My apologies. I'll apply and build the 20121106 patch in my development repo and give it some preliminary testing. Do you feel this is a work in progress or is the patch close to if not totally working at this point? > PHP binding of Qpid Messaging API > - > > Key: QPID-3027 > URL: https://issues.apache.org/jira/browse/QPID-3027 > Project: Qpid > Issue Type: New Feature > Components: C++ Client >Affects Versions: 0.8 >Reporter: Paul Colby >Assignee: Darryl L. Pierce > Attachments: cqpid_php.20110220.diff, cqpid_php.20110301.diff, > cqpid_php.20110328.diff, cqpid_php.20110415.diff, cqpid_php.20120406.diff, > cqpid_php.20121105.diff, cqpid_php.20121105-qpid-0.19.diff, > cqpid_php.20121106.diff, cqpid_php.diff, FindPHPDev.cmake, Makefile > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-2953) Qpid Cpp Messaging .NET Binding does not include unit tests
[ https://issues.apache.org/jira/browse/QPID-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-2953. --- Resolution: Fixed Fix Version/s: (was: Future) 0.10 jross@nicaea qpid$ svn log -c r1036644 r1036644 | chug | 2010-11-18 16:41:34 -0500 (Thu, 18 Nov 2010) | 4 lines QPID-2953 Qpid Cpp Messaging .NET Binding does not include unit tests. This checkin converts project test\messaging.test from an EXE to a DLL usable by NUnit. Tests for several managed objects are included in new files. > Qpid Cpp Messaging .NET Binding does not include unit tests > --- > > Key: QPID-2953 > URL: https://issues.apache.org/jira/browse/QPID-2953 > Project: Qpid > Issue Type: Improvement > Components: Dot Net Client >Affects Versions: 0.8 > Environment: Windows build >Reporter: Chuck Rolke >Assignee: Chuck Rolke > Fix For: 0.10 > > > The .NET Binding solution includes a project named Test\messaging.test. This > directory is disorganized with respect to a formal test suite. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Review Request: C++ Broker should not declare existing federated queues during bridge creation
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/7901/ --- Review request for qpid and Alan Conway. Description --- This patch conditionalizes the queue declaration during bridge creation. The queue is declared only if there is no existing queue, which is when the supplied queue name is blank. This addresses bug QPID-4423. https://issues.apache.org/jira/browse/QPID-4423 Diffs - trunk/qpid/cpp/src/qpid/broker/Bridge.cpp 1406267 Diff: https://reviews.apache.org/r/7901/diff/ Testing --- This passes federation 'make test' testing. Thanks, Chug Rolke
[jira] [Created] (QPID-4423) C++ Broker Dynamic and static federation should not declare existing queues
Chuck Rolke created QPID-4423: - Summary: C++ Broker Dynamic and static federation should not declare existing queues Key: QPID-4423 URL: https://issues.apache.org/jira/browse/QPID-4423 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.18 Reporter: Chuck Rolke Assignee: Chuck Rolke When configuring either a dynamic or static federated link, it is possible to provide the name of an existing queue to utilize. The issue is that the destination broker of the federated route will attempt to declare the queue regardless of whether or not it should be using an existing queue. This can result in a race condition if the pre-existing queue is not yet available on the source broker. When the destination broker creates a queue it will use default queue settings (i.e. trace/exclude, reject policy, default size limits) and not the desired configured settings that the queue will have when created properly on the source broker. The proposal to fix this issue is if a queue name was provided during a bridge declaration then the broker should not attempt to declare the queue. When no name is provided then the broker may go ahead and declare an exclusive queue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: QPID and eventlet.monkey_patch()
I believe that the 'red lines' are:
import eventlet
eventlet.monkey_patch()
- Original Message -
> From: "Gordon Sim"
> To: dev@qpid.apache.org
> Sent: Tuesday, November 6, 2012 11:53:01 AM
> Subject: Re: QPID and eventlet.monkey_patch()
>
> On 11/06/2012 03:32 PM, Gary Kotton wrote:
> > Hi,
> > Hi,
> > I'm Gary and working on the OpenStack project. I have run into a
> > problem
> > and maybe you can help or can suggest someone who can.
> > The communication between the different modules is done with QPID.
> > We
> > are using python. If the service that I am running starts before
> > qpidd
> > then it hangs and does not recover. Even when the qpidd daemon
> > starts it
> > does not recover.
> >
> > The reason is that we do eventlet.monkey_patch(). The script below
> > easily shows a reproduction of the problem. If the lines below in
> > red
> > are commented out the the script recovers when qpidd starts.
>
> For the benefit of those of us using mail readers that display plain
> text (and thus lose your colouring), could you point out which lines
> these are? Thanks!
>
> > If not then
> > it hangs. Please note that if the sockets are not patched then this
> > works. We need all to be patched.
> >
> > Any clues or direction will be greatly appreciated.
> > Thanks
> > Gary
> >
> > #!/usr/bin/env python
> >
> > import eventlet
> > eventlet.monkey_patch()
> >
> > import os
> > import time
> >
> > from qpid.messaging import endpoints
> >
> > print "QPID Test!"
> >
> > session = None
> > consumers = {}
> > consumer_thread = None
> >
> > default_params = dict(hostname='localhost',
> >port=5672,
> >username='',
> >password='')
> >
> > params = {}
> > for key in default_params.keys():
> > params.setdefault(key, default_params[key])
> >
> > broker = params['hostname'] + ":" + str(params['port'])
> > # Create the connection - this does not open the connection
> > print "==> broker %s" % broker
> > connection = endpoints.Connection(broker)
> >
> > # Check if flags are set and if so set them for the connection
> > # before we call open
> > connection.username = params['username']
> > connection.password = params['password']
> > connection.sasl_mechanisms = ''
> > connection.reconnect = True
> > connection.heartbeat = 60
> > connection.protocol = 'tcp'
> > connection.tcp_nodelay = True
> >
> > while True:
> > try:
> > connection.open()
> > except endpoints.exceptions.ConnectionError, e:
> > print 'Unable to connect to AMQP server: %s' % e
> > time.sleep(1)
> > else:
> > break
> >
> > print 'Connected to AMQP server on %s' % broker
> >
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> For additional commands, e-mail: dev-h...@qpid.apache.org
>
>
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3272) Allow JMS messages originated from another vendor to be sent through Qpid with the Message ID intact.
[ https://issues.apache.org/jira/browse/QPID-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491632#comment-13491632 ] Gordon Sim commented on QPID-3272: -- The AMQP 0-10 protocol unfortunately requires that message-id be a UUID. I suspect that is where this validation originates. > Allow JMS messages originated from another vendor to be sent through Qpid > with the Message ID intact. > - > > Key: QPID-3272 > URL: https://issues.apache.org/jira/browse/QPID-3272 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: 0.6, 0.8, 0.10 >Reporter: Rajith Attapattu >Assignee: Rajith Attapattu >Priority: Minor > Fix For: Future > > > A message bridge it forwards messages between two different messaging > providers. > However when attempting to send a message from another vendor through Qpid, > the send method throws an exception if the message ID is not a UUID. > javax.jms.JMSException: MessageId > 'ID:dhcp209-12.gsslab.pnq.redhat.com-45266-1305237148981-3:0:3:1:1' is not of > the correct format, it must be ID: followed by a UUID > at > org.apache.qpid.client.message.AMQMessageDelegate_0_10.setJMSMessageID(AMQMessageDelegate_0_10.java:165) > at > org.apache.qpid.client.message.AbstractJMSMessage.setJMSMessageID(AbstractJMSMessage.java:92) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: QPID and eventlet.monkey_patch()
On 11/06/2012 03:32 PM, Gary Kotton wrote:
Hi,
Hi,
I'm Gary and working on the OpenStack project. I have run into a problem
and maybe you can help or can suggest someone who can.
The communication between the different modules is done with QPID. We
are using python. If the service that I am running starts before qpidd
then it hangs and does not recover. Even when the qpidd daemon starts it
does not recover.
The reason is that we do eventlet.monkey_patch(). The script below
easily shows a reproduction of the problem. If the lines below in red
are commented out the the script recovers when qpidd starts.
For the benefit of those of us using mail readers that display plain
text (and thus lose your colouring), could you point out which lines
these are? Thanks!
If not then
it hangs. Please note that if the sockets are not patched then this
works. We need all to be patched.
Any clues or direction will be greatly appreciated.
Thanks
Gary
#!/usr/bin/env python
import eventlet
eventlet.monkey_patch()
import os
import time
from qpid.messaging import endpoints
print "QPID Test!"
session = None
consumers = {}
consumer_thread = None
default_params = dict(hostname='localhost',
port=5672,
username='',
password='')
params = {}
for key in default_params.keys():
params.setdefault(key, default_params[key])
broker = params['hostname'] + ":" + str(params['port'])
# Create the connection - this does not open the connection
print "==> broker %s" % broker
connection = endpoints.Connection(broker)
# Check if flags are set and if so set them for the connection
# before we call open
connection.username = params['username']
connection.password = params['password']
connection.sasl_mechanisms = ''
connection.reconnect = True
connection.heartbeat = 60
connection.protocol = 'tcp'
connection.tcp_nodelay = True
while True:
try:
connection.open()
except endpoints.exceptions.ConnectionError, e:
print 'Unable to connect to AMQP server: %s' % e
time.sleep(1)
else:
break
print 'Connected to AMQP server on %s' % broker
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
QPID and eventlet.monkey_patch()
Hi,
Hi,
I'm Gary and working on the OpenStack project. I have run into a problem
and maybe you can help or can suggest someone who can.
The communication between the different modules is done with QPID. We
are using python. If the service that I am running starts before qpidd
then it hangs and does not recover. Even when the qpidd daemon starts it
does not recover.
The reason is that we do eventlet.monkey_patch(). The script below
easily shows a reproduction of the problem. If the lines below in red
are commented out the the script recovers when qpidd starts. If not then
it hangs. Please note that if the sockets are not patched then this
works. We need all to be patched.
Any clues or direction will be greatly appreciated.
Thanks
Gary
#!/usr/bin/env python
import eventlet
eventlet.monkey_patch()
import os
import time
from qpid.messaging import endpoints
print "QPID Test!"
session = None
consumers = {}
consumer_thread = None
default_params = dict(hostname='localhost',
port=5672,
username='',
password='')
params = {}
for key in default_params.keys():
params.setdefault(key, default_params[key])
broker = params['hostname'] + ":" + str(params['port'])
# Create the connection - this does not open the connection
print "==> broker %s" % broker
connection = endpoints.Connection(broker)
# Check if flags are set and if so set them for the connection
# before we call open
connection.username = params['username']
connection.password = params['password']
connection.sasl_mechanisms = ''
connection.reconnect = True
connection.heartbeat = 60
connection.protocol = 'tcp'
connection.tcp_nodelay = True
while True:
try:
connection.open()
except endpoints.exceptions.ConnectionError, e:
print 'Unable to connect to AMQP server: %s' % e
time.sleep(1)
else:
break
print 'Connected to AMQP server on %s' % broker
[jira] [Resolved] (QPID-4417) swig 1.3.29 generated bad perl bindings
[ https://issues.apache.org/jira/browse/QPID-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce resolved QPID-4417. Resolution: Fixed Fix Version/s: 0.19 Changes to both the autotool and cmake build environments added. > swig 1.3.29 generated bad perl bindings > --- > > Key: QPID-4417 > URL: https://issues.apache.org/jira/browse/QPID-4417 > Project: Qpid > Issue Type: Bug >Affects Versions: 0.18 >Reporter: Jimmy Jones >Assignee: Darryl L. Pierce > Fix For: 0.19 > > Attachments: swig.diff > > > swig-1.3.29-2.el5.x86_64.rpm (RHEL5) generates bad bindings for getContent, > which uses sv_setpv rather than sv_setpvn, and also fiddles with NULL at the > end, so fails if the message contains a NULL byte. > Maybe configure should require a later version? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4417) swig 1.3.29 generated bad perl bindings
[ https://issues.apache.org/jira/browse/QPID-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491557#comment-13491557 ] Darryl L. Pierce commented on QPID-4417: Certainly! I've added your change, along with a similar check in the CMake toolchain, to require a minimum of 1.3.32 of Swig if language bindings are built. > swig 1.3.29 generated bad perl bindings > --- > > Key: QPID-4417 > URL: https://issues.apache.org/jira/browse/QPID-4417 > Project: Qpid > Issue Type: Bug >Affects Versions: 0.18 >Reporter: Jimmy Jones >Assignee: Darryl L. Pierce > Attachments: swig.diff > > > swig-1.3.29-2.el5.x86_64.rpm (RHEL5) generates bad bindings for getContent, > which uses sv_setpv rather than sv_setpvn, and also fiddles with NULL at the > end, so fails if the message contains a NULL byte. > Maybe configure should require a later version? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3272) Allow JMS messages originated from another vendor to be sent through Qpid with the Message ID intact.
[ https://issues.apache.org/jira/browse/QPID-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491516#comment-13491516 ] Ted Ross commented on QPID-3272: A message id that is not in the form of a UUID can be unique. And conversely, a message-id that is in the form of a UUID might not be unique. I see from the source code that the message ID is of type UUID. Is this strictly necessary? Is there a reason that it can't be a string? IMO, the "UUID form" validation is too heavy-handed. > Allow JMS messages originated from another vendor to be sent through Qpid > with the Message ID intact. > - > > Key: QPID-3272 > URL: https://issues.apache.org/jira/browse/QPID-3272 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: 0.6, 0.8, 0.10 >Reporter: Rajith Attapattu >Assignee: Rajith Attapattu >Priority: Minor > Fix For: Future > > > A message bridge it forwards messages between two different messaging > providers. > However when attempting to send a message from another vendor through Qpid, > the send method throws an exception if the message ID is not a UUID. > javax.jms.JMSException: MessageId > 'ID:dhcp209-12.gsslab.pnq.redhat.com-45266-1305237148981-3:0:3:1:1' is not of > the correct format, it must be ID: followed by a UUID > at > org.apache.qpid.client.message.AMQMessageDelegate_0_10.setJMSMessageID(AMQMessageDelegate_0_10.java:165) > at > org.apache.qpid.client.message.AbstractJMSMessage.setJMSMessageID(AbstractJMSMessage.java:92) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4422) Python Client (0-8..0-9) should pass "instance" client property to allow re-subscribing to durable subscriptions
Keith Wall created QPID-4422: Summary: Python Client (0-8..0-9) should pass "instance" client property to allow re-subscribing to durable subscriptions Key: QPID-4422 URL: https://issues.apache.org/jira/browse/QPID-4422 Project: Qpid Issue Type: Bug Components: Python Client Affects Versions: 0.18, 0.16, 0.14 Reporter: Keith Wall In order reconnect to an exclusive queue, the client must reconnect with the same clientid. In the Python 0-8 and 0-9 client code, this is currently impossible as it does not allow the "instance" client property to be passed to the broker when performing the connection.start, and so the Broker assigns a random one. This makes it impossible for the Python client users to use exclusive queues, which are integral to using durable subscriptions properly. The 0-10 code does not have this problem. The Python client should be changed to allow the user to pass the client_properties, thus allowing them to specify the instance. We should also take this opportunity to pass the client version number. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3027) PHP binding of Qpid Messaging API
[ https://issues.apache.org/jira/browse/QPID-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491486#comment-13491486 ] Darryl L. Pierce commented on QPID-3027: No, that was a mistaken. I must have selected the description by accident while adding my comment yesterday. My apologies. I'll apply and build the 20121106 patch in my development repo and give it some preliminary testing. Do you feel this is a work in progress or is the patch close to if not totally working at this point? > PHP binding of Qpid Messaging API > - > > Key: QPID-3027 > URL: https://issues.apache.org/jira/browse/QPID-3027 > Project: Qpid > Issue Type: New Feature > Components: C++ Client >Affects Versions: 0.8 >Reporter: Paul Colby >Assignee: Darryl L. Pierce > Attachments: cqpid_php.20110220.diff, cqpid_php.20110301.diff, > cqpid_php.20110328.diff, cqpid_php.20110415.diff, cqpid_php.20120406.diff, > cqpid_php.20121105.diff, cqpid_php.20121105-qpid-0.19.diff, > cqpid_php.20121106.diff, cqpid_php.diff, FindPHPDev.cmake, Makefile > > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
