[jira] Commented: (QPID-2428) qpid.subject should be set on outgoing messages if the address specifies a suject
[ https://issues.apache.org/jira/browse/QPID-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841046#action_12841046 ] Rajith Attapattu commented on QPID-2428: The python client already contains a fix. rev 918842 in Qpid trunk contains a fix for the JMS client rev 918845 in Qpid trunk contains a fix for the C++ client > qpid.subject should be set on outgoing messages if the address specifies a > suject > - > > Key: QPID-2428 > URL: https://issues.apache.org/jira/browse/QPID-2428 > Project: Qpid > Issue Type: Bug > Components: C++ Client, Java Client, Python Client >Reporter: Rajith Attapattu >Assignee: Rajith Attapattu > > If the address specifies a subject, then the out going message should set the > "qpid.subject" property as an application property in the message properties. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2428) qpid.subject should be set on outgoing messages if the address specifies a suject
qpid.subject should be set on outgoing messages if the address specifies a suject - Key: QPID-2428 URL: https://issues.apache.org/jira/browse/QPID-2428 Project: Qpid Issue Type: Bug Components: C++ Client, Java Client, Python Client Reporter: Rajith Attapattu Assignee: Rajith Attapattu If the address specifies a subject, then the out going message should set the "qpid.subject" property as an application property in the message properties. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
SubscriptionManager.stop() never returns
I have a program that reads messages from "local_queue". It works fine. It
gets messages from local_queue and prints them to the screen. This program
starts a subscriptionManager that should be stopped when receives SIGINT or
SIGTERM, but it never returns from Subscription manager.stop() function. It
is something wrong with the program or it is a bug ?
If i use:
subscriptions->start();
subscriptions->wait()
instead of : subscriptions->run(), the program returns 0 - normal exit.
[but i still get the same output in gdb]
Here is the code for the program that reads messages from queue:
#include
#include
#include
#include
#include
#include
#include
using namespace qpid::client;
using namespace qpid::framing;
using std::stringstream;
using std::string;
class GatherListener : public MessageListener {
private:
AsyncSession asyncSession;
public:
GatherListener(Session& session): asyncSession(session) {}
virtual void received(Message& request) {
stringstream text;
text << request.getData();
std::coutsubscribe(gather_listener, "local_queue");
std::cout<<"Before run()"
QMF and .NET
Options and thoughts on direction for QMF in C#. We have one impl on the native C# client for QMF v1. Question is to port this to the C++ C# wrapped impl or / and do ? First of QMF can be used in two ways, one for modelling object interactions, second doing management. In the Windows world, the most natural binding for QMF would be to have a powershell mapping. For the object mapping it is less clear. Here we could port the work done on the native C# WCF client which provides a service layer inside WCF. Pros - it works, simple. Cons, duplicates QMF logic in C# and does not map directly to the WCF WS stack. We could wrapped QMFv2 API in C#. Pros, no code duplication. Cons, as above ignores the WCF WS stack. Finally we could write a mapping from WSDL to QMF. This would mean all the WCF WS stuff would work with a QMF payload. Pros - fits into WCF service architecture, Cons - we qould be able to map QMF to WSDL, but would not be able to or it would be a large piece of work to map all of WSDL schema to QMF. (Not sure it is worth the effort.) Love to get thoughts, ideas and perspectives. Carl. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Connection.open get stuck with wrong host address
It is implemented for qpidd 0.5? or 0.6? -- View this message in context: http://n2.nabble.com/Connection-open-get-stuck-with-wrong-host-address-tp4661786p4670557.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2402) qpid::messaging.Message::setTTL() unit ambiguity can cause unexpectected behavior
[ https://issues.apache.org/jira/browse/QPID-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-2402. -- Resolution: Fixed > qpid::messaging.Message::setTTL() unit ambiguity can cause unexpectected > behavior > - > > Key: QPID-2402 > URL: https://issues.apache.org/jira/browse/QPID-2402 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client >Reporter: Kerry Bonin >Assignee: Gordon Sim > > qpid::messaging.Message::setTTL( boost::uint64_t ttl ) - does not declare its > units. > The currently exposed time types are AbsTime and Duration, which seems to > imply they should be used for encapsulating time. > When a Duration object is passed to setTTL, the inline operator int64_t() > returns the member variable nanoseconds. > When this value is propagated to the broker, it is interpreted around > /cpp/src/qpid/broker/Message # 353 to be in millisecond units. > I would recommend: > - document Message.setTTL units clearly - pick ms or ns > - if ms, then overload setTTL to take a Duration object so we can use > without error by converting in setTTL > - if ns, then somewhere downstream (OutgoingMessage#351 ?) the ns needs to > get converted to ms -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2406) Consistent approach to durations in qpid::messaging api
[ https://issues.apache.org/jira/browse/QPID-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-2406. -- Resolution: Fixed > Consistent approach to durations in qpid::messaging api > --- > > Key: QPID-2406 > URL: https://issues.apache.org/jira/browse/QPID-2406 > Project: Qpid > Issue Type: Bug > Components: C++ Client >Affects Versions: 0.6 >Reporter: Gordon Sim >Assignee: Gordon Sim > Fix For: 0.7 > > > in particular no direct use of qpid::sys::Time.h -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2427) Modify browse option in-line with path chosen for python client
[ https://issues.apache.org/jira/browse/QPID-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-2427. -- Resolution: Fixed > Modify browse option in-line with path chosen for python client > --- > > Key: QPID-2427 > URL: https://issues.apache.org/jira/browse/QPID-2427 > Project: Qpid > Issue Type: Bug > Components: C++ Client >Reporter: Gordon Sim >Assignee: Gordon Sim > Fix For: 0.7 > > > Change c++ client from boolean value named 'browse' to 'mode' which can be > 'browse' or 'consume'. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2426) Better error message and logging when receving/sending from/to empty address
[ https://issues.apache.org/jira/browse/QPID-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-2426. -- Resolution: Fixed > Better error message and logging when receving/sending from/to empty address > > > Key: QPID-2426 > URL: https://issues.apache.org/jira/browse/QPID-2426 > Project: Qpid > Issue Type: Bug >Reporter: Gordon Sim >Assignee: Gordon Sim > Fix For: 0.7 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2386) Qpid C++ broker: add user ID in "SASL: Authentication failed" log message
[
https://issues.apache.org/jira/browse/QPID-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved QPID-2386.
--
Resolution: Fixed
> Qpid C++ broker: add user ID in "SASL: Authentication failed" log message
> -
>
> Key: QPID-2386
> URL: https://issues.apache.org/jira/browse/QPID-2386
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
> Environment: Red Hat Enterprise MRG 1.2
>Reporter: Armin Noll
>Assignee: Gordon Sim
>Priority: Minor
>
> When the SASL authentication succeeds the broker then logs a message like the
> following:
> 2010-feb-03 15:28:45 info SASL: Authentication succeeded for: u...@qpid
> When the authentication fails it logs e.g.:
> 2010-feb-03 16:09:20 info SASL: Authentication failed: SASL(-13):
> authentication failure: Password verification failed
> It would be helpful if the log message in the latter case would also contain
> the user ID and domain for which the authentication failed. It could look like
> 2010-feb-03 16:09:20 info SASL: Authentication failed for u...@qpid:
> SASL(-13): authentication failure: Password verification failed
> I think this can easily be achieved by applying the following change to the
> module SASLAUTHENTICATOR.CPP:
> OLD:
> } else {
> QPID_LOG(info, "SASL: Authentication failed: " <<
> sasl_errdetail(sasl_conn));
>
> // TODO: Change to more specific exceptions, when they are
> // available
> switch (code) {
> NEW:
> } else {
> QPID_LOG(info, "SASL: Authentication failed for " <<
> const_cast(static_cast(uid)) << ": " <<
> sasl_errdetail(sasl_conn));
>
> // TODO: Change to more specific exceptions, when they are
> // available
> switch (code) {
> This enhancement request has also been reported as Red Hat service request
> #1991714.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Connection.open get stuck with wrong host address
On Wed, 2010-03-03 at 00:41 -0800, _cristian_ wrote: > You are right with the heartbeat options.But this option is not implemented > yet. That's quite funny, as I implemented the feature myself. > This is from apache qpid api docs: [ > http://qpid.apache.org/docs/api/cpp/html/a00226.html ] > uint16_t heartbeat Allows a heartbeat frequency to be specified > (this > feature is not yet implemented). > After a period [ 2-3 minutes ] connection.open return and i get the message: > Connection timed out: 10.10.5.5:5672 (qpid/sys/posix/Socket.cpp:162) > > Thanks for your help guys - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-2386) Qpid C++ broker: add user ID in "SASL: Authentication failed" log message
[
https://issues.apache.org/jira/browse/QPID-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim reassigned QPID-2386:
Assignee: Gordon Sim
> Qpid C++ broker: add user ID in "SASL: Authentication failed" log message
> -
>
> Key: QPID-2386
> URL: https://issues.apache.org/jira/browse/QPID-2386
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
> Environment: Red Hat Enterprise MRG 1.2
>Reporter: Armin Noll
>Assignee: Gordon Sim
>Priority: Minor
>
> When the SASL authentication succeeds the broker then logs a message like the
> following:
> 2010-feb-03 15:28:45 info SASL: Authentication succeeded for: u...@qpid
> When the authentication fails it logs e.g.:
> 2010-feb-03 16:09:20 info SASL: Authentication failed: SASL(-13):
> authentication failure: Password verification failed
> It would be helpful if the log message in the latter case would also contain
> the user ID and domain for which the authentication failed. It could look like
> 2010-feb-03 16:09:20 info SASL: Authentication failed for u...@qpid:
> SASL(-13): authentication failure: Password verification failed
> I think this can easily be achieved by applying the following change to the
> module SASLAUTHENTICATOR.CPP:
> OLD:
> } else {
> QPID_LOG(info, "SASL: Authentication failed: " <<
> sasl_errdetail(sasl_conn));
>
> // TODO: Change to more specific exceptions, when they are
> // available
> switch (code) {
> NEW:
> } else {
> QPID_LOG(info, "SASL: Authentication failed for " <<
> const_cast(static_cast(uid)) << ": " <<
> sasl_errdetail(sasl_conn));
>
> // TODO: Change to more specific exceptions, when they are
> // available
> switch (code) {
> This enhancement request has also been reported as Red Hat service request
> #1991714.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Vote for 0.6 Release (Really)
On Wed, Mar 3, 2010 at 8:34 AM, Steve Huston wrote: >> -Original Message- >> From: Gordon Sim [mailto:g...@redhat.com] >> Sent: Tuesday, March 02, 2010 7:20 AM >> To: dev@qpid.apache.org >> Subject: Re: Vote for 0.6 Release (Really) >> ... >> > On the .csproj files, I would guess that they probably do need a >> > licence, and if most of them already include it then it >> seems sensible >> > to do the rest and finish the job. >> >> Seems sensible. Is someone willing to volunteer to do that? > > Who's working on the .NET client these days? Has it been tested? > >> Following >> Rajiths comments I'm not sure what the right approach is. There are >> certainly other csproj files with the license in at the top >> of the file - do these cause problems for MSVC? > > No, as long as the inserted XML doesn't step on a special marker char > which may be at the very start of the file. I checked a few of the > dotnet csproj files and they didn't have that marker anyway, so there > should be no problem dropping the license into an XML comment. Just make > sure to try a build before committing and things should be fine. I have no issues adding the license header, but I don't have a way of testing it out. Last time I did it, I had stepped on the almigty special marker and Steve had to work it out. So I believe somebody from the .NET project needs to do this and verify that everything is fine. > -Steve > > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Vote for 0.6 Release (Really)
> -Original Message- > From: Gordon Sim [mailto:g...@redhat.com] > Sent: Tuesday, March 02, 2010 7:20 AM > To: dev@qpid.apache.org > Subject: Re: Vote for 0.6 Release (Really) > ... > > On the .csproj files, I would guess that they probably do need a > > licence, and if most of them already include it then it > seems sensible > > to do the rest and finish the job. > > Seems sensible. Is someone willing to volunteer to do that? Who's working on the .NET client these days? Has it been tested? > Following > Rajiths comments I'm not sure what the right approach is. There are > certainly other csproj files with the license in at the top > of the file - do these cause problems for MSVC? No, as long as the inserted XML doesn't step on a special marker char which may be at the very start of the file. I checked a few of the dotnet csproj files and they didn't have that marker anyway, so there should be no problem dropping the license into an XML comment. Just make sure to try a build before committing and things should be fine. -Steve - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Connection.open get stuck with wrong host address
Thank you for your help. i will upgrade when 0.6 will be released -- View this message in context: http://n2.nabble.com/Connection-open-get-stuck-with-wrong-host-address-tp4661786p4666970.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Connection.open get stuck with wrong host address
On 03/03/2010 11:37 AM, _cristian_ wrote: It is 0.5 This is the output for: qpidd -v qpidd (qpidc) version 0.5 Ok, that is fixed on trunk and will be in the 0.6 release. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Connection.open get stuck with wrong host address
It is 0.5 This is the output for: qpidd -v qpidd (qpidc) version 0.5 -- View this message in context: http://n2.nabble.com/Connection-open-get-stuck-with-wrong-host-address-tp4661786p4666929.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Connection.open get stuck with wrong host address
On 03/03/2010 11:26 AM, _cristian_ wrote: Was this when using a non-zero heartbeat? Yes.I have heartbeat=10. open() returns after 3 minutes, even with heartbeat=10. Is this using 0.5? I believe there was a fix made after that to deal with the opening of the connection (prior to the fix heartbeats were only enabled once the connection was opened). - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Connection.open get stuck with wrong host address
Was this when using a non-zero heartbeat? Yes.I have heartbeat=10. open() returns after 3 minutes, even with heartbeat=10. -- View this message in context: http://n2.nabble.com/Connection-open-get-stuck-with-wrong-host-address-tp4661786p4666883.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Connection.open get stuck with wrong host address
On 03/03/2010 08:41 AM, _cristian_ wrote: You are right with the heartbeat options.But this option is not implemented yet. Those docs are out of date. Heartbeats are implemented. This is from apache qpid api docs: [ http://qpid.apache.org/docs/api/cpp/html/a00226.html ] uint16_theartbeat Allows a heartbeat frequency to be specified (this feature is not yet implemented). After a period [ 2-3 minutes ] connection.open return and i get the message: Connection timed out: 10.10.5.5:5672 (qpid/sys/posix/Socket.cpp:162) Was this when using a non-zero heartbeat? - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Connection.open get stuck with wrong host address
You are right with the heartbeat options.But this option is not implemented yet. This is from apache qpid api docs: [ http://qpid.apache.org/docs/api/cpp/html/a00226.html ] uint16_theartbeat Allows a heartbeat frequency to be specified (this feature is not yet implemented). After a period [ 2-3 minutes ] connection.open return and i get the message: Connection timed out: 10.10.5.5:5672 (qpid/sys/posix/Socket.cpp:162) Thanks for your help guys -- View this message in context: http://n2.nabble.com/Connection-open-get-stuck-with-wrong-host-address-tp4661786p4666291.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
