[jira] [Commented] (QPID-3333) Make Python SWIG bindings a drop-in replacement for pure Python qpid.messaging package
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092125#comment-13092125 ] Anthony Foglia commented on QPID-: -- Also, I've added a subtask/bug report (QPID-3458); the compiled part of the swig libraries is installed in the wrong place. It's really a separate bug, but as this is becoming a place to track the SWIG binding progress, it made sense to make it a subtask for now. > Make Python SWIG bindings a drop-in replacement for pure Python > qpid.messaging package > -- > > Key: QPID- > URL: https://issues.apache.org/jira/browse/QPID- > Project: Qpid > Issue Type: Improvement > Components: C++ Client >Affects Versions: 0.11, Future >Reporter: Anthony Foglia >Assignee: Gordon Sim > Attachments: 0001-Wrap-NoMessageAvailable-as-Empty-exception.patch, > 0002-Change-Connection-interface-to-match-pure-python.patch, > 0003-Change-Session-interface-to-match-pure-python.patch, > 0004-Change-Receiver-interface-to-match-pure-python.patch, > 0005-Change-Sender-interface-to-match-pure-python.patch, > 0006-Change-Message-interface-to-match-pure-python.patch, > 0007-Handle-connection-options.patch, > 0008-Fixes-and-more-improvements-to-Message-objects.patch, > 0009-Wrap-more-exceptions-2011-08-26.patch, > 0009-Wrap-more-exceptions-2011-08-26.patch, > 0009-Wrapping-of-more-exceptions.patch, > 0010-Add-session-property-to-senders-and-receivers.patch, > 0011-Wrap-returned-UUIDs-as-Python-UUIDs.patch, > 0012-Add-connection-property-to-Session-object.patch, > 0012-Add-connection-property-to-Session-object.patch, > 0013-Handle-amqp-list-and-amqp-map-content.patch, > 0013-Handle-amqp-list-and-amqp-map-content.patch, > 9900-Wrap-qpid-framing-NotAttachedException.patch, > 9900-Wrap-qpid-framing-NotAttachedException.patch > > > These patches are make the compile Python SWIG bindings to the C++ client > much closer to a drop-in replacement for the Python qpid.messaging package. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3333) Make Python SWIG bindings a drop-in replacement for pure Python qpid.messaging package
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Foglia updated QPID-: - Attachment: 0013-Handle-amqp-list-and-amqp-map-content.patch 0012-Add-connection-property-to-Session-object.patch 9900-Wrap-qpid-framing-NotAttachedException.patch 0009-Wrap-more-exceptions-2011-08-26.patch Re-adding, with the desired license. > Make Python SWIG bindings a drop-in replacement for pure Python > qpid.messaging package > -- > > Key: QPID- > URL: https://issues.apache.org/jira/browse/QPID- > Project: Qpid > Issue Type: Improvement > Components: C++ Client >Affects Versions: 0.11, Future >Reporter: Anthony Foglia >Assignee: Gordon Sim > Attachments: 0001-Wrap-NoMessageAvailable-as-Empty-exception.patch, > 0002-Change-Connection-interface-to-match-pure-python.patch, > 0003-Change-Session-interface-to-match-pure-python.patch, > 0004-Change-Receiver-interface-to-match-pure-python.patch, > 0005-Change-Sender-interface-to-match-pure-python.patch, > 0006-Change-Message-interface-to-match-pure-python.patch, > 0007-Handle-connection-options.patch, > 0008-Fixes-and-more-improvements-to-Message-objects.patch, > 0009-Wrap-more-exceptions-2011-08-26.patch, > 0009-Wrap-more-exceptions-2011-08-26.patch, > 0009-Wrapping-of-more-exceptions.patch, > 0010-Add-session-property-to-senders-and-receivers.patch, > 0011-Wrap-returned-UUIDs-as-Python-UUIDs.patch, > 0012-Add-connection-property-to-Session-object.patch, > 0012-Add-connection-property-to-Session-object.patch, > 0013-Handle-amqp-list-and-amqp-map-content.patch, > 0013-Handle-amqp-list-and-amqp-map-content.patch, > 9900-Wrap-qpid-framing-NotAttachedException.patch, > 9900-Wrap-qpid-framing-NotAttachedException.patch > > > These patches are make the compile Python SWIG bindings to the C++ client > much closer to a drop-in replacement for the Python qpid.messaging package. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3333) Make Python SWIG bindings a drop-in replacement for pure Python qpid.messaging package
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Foglia updated QPID-: - Attachment: 9900-Wrap-qpid-framing-NotAttachedException.patch 0013-Handle-amqp-list-and-amqp-map-content.patch 0012-Add-connection-property-to-Session-object.patch 0009-Wrap-more-exceptions-2011-08-26.patch Okay, I've split the 0009 patch wrapping the exceptions into two. The new 0009 only wraps the exceptions from qpid::messaging. The wrapping of the qpid::framing::NotAttachedException is now in a patch I numbered 9900. I still think it should be included, but at least now it's separate, so you can include the others without it. In addition I've added two more patches. The first adds a connection property to the Session objects. The second adds the ability to use lists and maps as the content of Messages. > Make Python SWIG bindings a drop-in replacement for pure Python > qpid.messaging package > -- > > Key: QPID- > URL: https://issues.apache.org/jira/browse/QPID- > Project: Qpid > Issue Type: Improvement > Components: C++ Client >Affects Versions: 0.11, Future >Reporter: Anthony Foglia >Assignee: Gordon Sim > Attachments: 0001-Wrap-NoMessageAvailable-as-Empty-exception.patch, > 0002-Change-Connection-interface-to-match-pure-python.patch, > 0003-Change-Session-interface-to-match-pure-python.patch, > 0004-Change-Receiver-interface-to-match-pure-python.patch, > 0005-Change-Sender-interface-to-match-pure-python.patch, > 0006-Change-Message-interface-to-match-pure-python.patch, > 0007-Handle-connection-options.patch, > 0008-Fixes-and-more-improvements-to-Message-objects.patch, > 0009-Wrap-more-exceptions-2011-08-26.patch, > 0009-Wrapping-of-more-exceptions.patch, > 0010-Add-session-property-to-senders-and-receivers.patch, > 0011-Wrap-returned-UUIDs-as-Python-UUIDs.patch, > 0012-Add-connection-property-to-Session-object.patch, > 0013-Handle-amqp-list-and-amqp-map-content.patch, > 9900-Wrap-qpid-framing-NotAttachedException.patch > > > These patches are make the compile Python SWIG bindings to the C++ client > much closer to a drop-in replacement for the Python qpid.messaging package. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
A hot-standby design for a new cluster implementation.
This is a second candidate design for the "new cluster". I'd appreciate any feedback, this is still in early stages. http://svn.apache.org/viewvc/qpid/trunk/qpid/cpp/design_docs/hot-standby-design.txt?view=markup&pathrev=1162272 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Reopened] (QPID-3457) qpid::Msg::str() method not exported
[ https://issues.apache.org/jira/browse/QPID-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston reopened QPID-3457: Still broken... There's a #include "Msg.h" in log/Statement.h, which Variant.cpp includes, so the unresolved symbol reappeared. > qpid::Msg::str() method not exported > > > Key: QPID-3457 > URL: https://issues.apache.org/jira/browse/QPID-3457 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client >Affects Versions: 0.13 >Reporter: Steve Huston >Assignee: Alan Conway > Fix For: 0.11 > > > Trunk r1161742 added a Msg::str() method to cpp/src/qpid/Msg.cpp - this > method is not marked with an extern decorator, so it's not visible outside > qpidcommon (where Msg.cpp is built) on Windows. This causes build errors on > Windows, with unresolved external references to the method. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Resolved] (QPID-3457) qpid::Msg::str() method not exported
[ https://issues.apache.org/jira/browse/QPID-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved QPID-3457. --- Resolution: Fixed Fix Version/s: 0.11 Fixed in r1162233 on trunk > qpid::Msg::str() method not exported > > > Key: QPID-3457 > URL: https://issues.apache.org/jira/browse/QPID-3457 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client >Affects Versions: 0.13 >Reporter: Steve Huston >Assignee: Alan Conway > Fix For: 0.11 > > > Trunk r1161742 added a Msg::str() method to cpp/src/qpid/Msg.cpp - this > method is not marked with an extern decorator, so it's not visible outside > qpidcommon (where Msg.cpp is built) on Windows. This causes build errors on > Windows, with unresolved external references to the method. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Resolved] (QPID-3354) Change default configure/build instructions for UUID headers from e2fsprogs-devel to libuuid-devel
[ https://issues.apache.org/jira/browse/QPID-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-3354. --- Resolution: Fixed Fix Version/s: (was: 0.12) > Change default configure/build instructions for UUID headers from > e2fsprogs-devel to libuuid-devel > -- > > Key: QPID-3354 > URL: https://issues.apache.org/jira/browse/QPID-3354 > Project: Qpid > Issue Type: Improvement > Components: Build Tools >Affects Versions: 0.10 >Reporter: William Henry >Assignee: Justin Ross > Fix For: 0.13 > > > The current build instructions assume older versions of Fedora for build C++. > INSTALL file states: > > UUID problems: > In some later Linux releases (such as Fedora 12), the uuid/uuid.h file has > been > moved from e2fsprogs-devel into libuuid-devel. If you are using a newer Linux > release and run into a problem during configure in which uuid.h cannot be > found, > look for and install the libuuid-devel package. > <\INSTALL> > We should flip this so that the default is to install libuuid-devel and the > the instructions explain that for older releases of linux you need to install > e2fsprogs-devel. > > UUID problems: > In some earlier Linux releases (such as Fedora 11), the uuid/uuid.h file is > loccated > in e2fsprogs-devel instead of libuuid-devel. If you are using an older Linux > release and run into a problem during configure in which uuid.h cannot be > found, > look for and install the e2fsprogs-devel package. > <\New INSTALL instructions> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Created] (QPID-3458) Install compiled _cqpid.so for SWIG python bindings in site-packages directory
Install compiled _cqpid.so for SWIG python bindings in site-packages directory -- Key: QPID-3458 URL: https://issues.apache.org/jira/browse/QPID-3458 Project: Qpid Issue Type: Sub-task Components: C++ Client Affects Versions: 0.10 Reporter: Anthony Foglia When building and installing the swig wrappers for the C++ client, the shared object _cqpid.so is created and installed in PREFIX/lib. This is imported by the pure Python part of the generated python package (cqpid.py), so it should be in the same directory PREFIX/lib/pythonX.Y/site-packages. Otherwise, the python bindings cannot be imported. I would attempt this fix myself, but I have no experience writing autotools scripts, nor cmake scripts. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Created] (QPID-3457) qpid::Msg::str() method not exported
qpid::Msg::str() method not exported Key: QPID-3457 URL: https://issues.apache.org/jira/browse/QPID-3457 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.13 Reporter: Steve Huston Assignee: Alan Conway Trunk r1161742 added a Msg::str() method to cpp/src/qpid/Msg.cpp - this method is not marked with an extern decorator, so it's not visible outside qpidcommon (where Msg.cpp is built) on Windows. This causes build errors on Windows, with unresolved external references to the method. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: public facing CI for the C++ components
It is possible to get packages installed on the Jenkins slave machines, I have seen several people asking for a bunch of packages on the bui...@apache.org list. The questions would be do those packages exist for Ubuntu and if so what are they, then whether or not they are deemed suitable for install on the slaves. Even if we could get results posted to the notifications list from elsewhere (needs to be from an apache.org address), it would still be nice if could have a single dashboard view of the current build state. Daryyl Pierce was kind enough to offer to help, but as I had to tell told him it really needs to be a committer so that they can get them access to Jenkins. Robbie On 26 August 2011 11:32, Andrew Kennedy wrote: > On 23 Aug 2011, at 09:35, Robbie Gemmell wrote: >> Hi all, >> >> I think it would be a good idea if we could get some public facing CI >> set up for the C++ components. There have been various issues which >> have gone unnnoticed in recent weeks at least in part due to the lack >> of CI as a fallback after not spotting the issues otherwise. We have >> some projects set up for the Java tree on the ASF Jenkins instances >> (more to follow, once we get some issues with the framework sorted >> out), it would be good to get something set up for the C++ broker, >> either directly running there or through its remote results reporting >> abilities. >> >> Any volunteers willing to get involved? > > Hi. > > I had managed to get a C++ build working on Jenkins on an EC2 instance where > I had full control of the packages installed, namely Boost and AIS/corosync > and so forth. I'm not sure whether it is possible to install these libraries > as a normal user, in non /usr/lib locations, and still build Qpid? If not, > this would preclude using the ASF infrastructure to run CI. I will give it a > shot, otherwise I can investigate using Amazon EC2 to run the C++ builds. It > should be simple to have all the CI results reported to the notifications > list, regardless of their origin, although we may need help from infra to > accomplish this from an external source. > > Andrew. > -- > -- andrew d kennedy ? +447582293255 : http://grkvlt.blogspot.com/ ; > > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
JIRA clean up for Java components
Hi all, We have an enormous amount of outstanding JIRAs, with around 700 open, and close to 400 of these are for the Java client and broker. Many of these issues will have been fixed and the JIRA just not updated (duplicated?), many will no longer be relevant at all due to years of subsequent change, and many could be valid but will never be fixed. Regardless, having so many outstanding issues makes it hard to actually keep JIRA in check and know what the important issues to look at are, or what work is being done in general. We need to seriously tidy things up and then keep it tidy going forward. To that end, Rob Godfrey and I have both looked through the entire list of outstanding issues for the Java client and broker and picked out some issues we thought should be retained, leaving some 260 issues remaining as things that either appeared to be resolved already or should just be closed because it is probable no one will ever look at them again. You can find the reduced list at: http://people.apache.org/~robbie/qpid/OpenJavaJIRAs.pdf We intend to close these JIRAs out at the end of next week, marking them with a new fix-for or tag that will allow them to be found in future and restored if need be. I would ask that people look at the list and suggest if there is anything you think ought to be retained in its current state instead. Robbie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Commented] (QPID-2720) Qpid broker can not run inside an OSGi container
[ https://issues.apache.org/jira/browse/QPID-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091800#comment-13091800 ] Robbie Gemmell commented on QPID-2720: -- That could happen if the PluginManager wasn't fully initialized when it was shut down (as would probably happen in some of the tests). I have checked in a fix to prevent the NPE by iterating a list of the ServiceTrackers, which would be empty in that case. > Qpid broker can not run inside an OSGi container > > > Key: QPID-2720 > URL: https://issues.apache.org/jira/browse/QPID-2720 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Danushka Menikkumbura >Assignee: Danushka Menikkumbura > Fix For: 0.13 > > Attachments: QPID-2720-V2.patch, QPID-2720-V3.patch, QPID-2720.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3456) Python and C++ clients behave differently
[
https://issues.apache.org/jira/browse/QPID-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim reassigned QPID-3456:
Assignee: Gordon Sim
> Python and C++ clients behave differently
> -
>
> Key: QPID-3456
> URL: https://issues.apache.org/jira/browse/QPID-3456
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client, Python Client
>Affects Versions: 0.13
>Reporter: Tomas Soltys
>Assignee: Gordon Sim
>Priority: Minor
>
> Python and C++ clients sends different commands to the broker.
> Address:
> response/response.QPID_CLIENT.response_queue_1;
> {
> create: receiver,
> link:
> {
> name: 'response.QPID_CLIENT.response_queue_1',
> durable: false,
> x-declare:
> {
> auto-delete: true,
> exclusive: true,
> arguments:
> {
> 'qpid.max_count': 1000,
> 'qpid.max_size': 100,
> 'qpid.policy_type': ring
> }
> }
> }
> }
> I have set the log level to trace+ on my broker and here is what I got from
> the log when I have used the same same addres for python as well as for c++
> client.
> Python:
> 2011-08-26 12:13:08 trace
> QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 0:
> {ExchangeQueryBody: name=response; }
> 2011-08-26 12:13:08 trace
> QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 1:
> {QueueQueryBody: queue=response; }
> 2011-08-26 12:13:08 trace
> QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 2:
> {QueueDeclareBody: queue=response.QPID_CLIENT.response_queue_1; exclusive=1;
> auto-delete=1;
> arguments={qpid.max_count:F8:int64(1000),qpid.max_size:F8:int64(100),qpid.policy_type:V2:4:str16(ring)};
> }
> 2011-08-26 12:13:08 trace
> QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 3:
> {ExchangeBindBody: queue=response.QPID_CLIENT.response_queue_1;
> exchange=response; binding-key=response.QPID_CLIENT.response_queue_1; }
> 2011-08-26 12:13:08 trace
> QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 4:
> {MessageSubscribeBody: queue=response.QPID_CLIENT.response_queue_1;
> destination=0; accept-mode=0; acquire-mode=0; }
> 2011-08-26 12:13:08 trace
> QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 5:
> {MessageSetFlowModeBody: destination=0; flow-mode=0; }
> 2011-08-26 12:13:08 trace
> QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 6:
> {MessageCancelBody: destination=0; }
> 2011-08-26 12:13:08 trace
> QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 7:
> {QueueDeleteBody: queue=response.QPID_CLIENT.response_queue_1; }
> C++:
> 2011-08-26 12:15:48 trace
> QPID_CLIENT@QPID.a167bd61-8aa3-4900-9ee7-a646bf3c1c63: recv cmd 0:
> {ExecutionSyncBody: }
> 2011-08-26 12:15:48 trace
> QPID_CLIENT@QPID.a167bd61-8aa3-4900-9ee7-a646bf3c1c63: recv cmd 1:
> {ExchangeQueryBody: name=response; }
> 2011-08-26 12:15:48 trace
> QPID_CLIENT@QPID.a167bd61-8aa3-4900-9ee7-a646bf3c1c63: recv cmd 2:
> {ExchangeDeclareBody: exchange=response; type=topic; alternate-exchange=;
> arguments={}; }
> C++ client will get 'ACL denied exchange declare request from
> QPID_CLIENT@QPID' from the broker.
> So to make the C++ client to be able to pass through I had to change the
> adress as followed:
> response/response.QPID_CLIENT.response_queue_1;
> {
> assert: never,
> create: never,
> node :
> {
> type: topic
> },
> link:
> {
> name: 'response.QPID_CLIENT.response_queue_1',
> durable: false,
> x-declare:
> {
> auto-delete: true,
> exclusive: true,
> arguments:
> {
> 'qpid.max_count': 1000,
> 'qpid.max_size': 100,
> 'qpid.policy_type': ring
> }
> }
> }
> }
> And I had to add two ACL rules:
> acl allow members create exchange name=response passive=true
> acl allow QPID_CLIENT@QPID create queuename=response.QPID_CLIENT.*
> passive=true
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3454) System test StreamMessageTest would not detect regression in StreamMessage buffer expansion.
[ https://issues.apache.org/jira/browse/QPID-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3454: - Status: Ready To Review (was: In Progress) > System test StreamMessageTest would not detect regression in StreamMessage > buffer expansion. > > > Key: QPID-3454 > URL: https://issues.apache.org/jira/browse/QPID-3454 > Project: Qpid > Issue Type: Bug > Components: Java Tests >Affects Versions: 0.10, 0.11, 0.12 >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: 0.13 > > > A defect in the logic of > StreamMessageTest#testModifyReceivedMessageExpandsBuffer would mean that a > regression could go unnoticed. > The test incorrectly uses a Junit assertion _within_ an onMessage. > Unfortunately if this assertion were to ever fail, the Junit test harness > would not hear the assertion fail as onMessage is executed by a separate > thread. > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Resolved] (QPID-3453) Test PersistentStoreTest fails on java-bdb-spawn.0-10 profile
[ https://issues.apache.org/jira/browse/QPID-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-3453. -- Resolution: Fixed Re-reviewed, no further comments. > Test PersistentStoreTest fails on java-bdb-spawn.0-10 profile > - > > Key: QPID-3453 > URL: https://issues.apache.org/jira/browse/QPID-3453 > Project: Qpid > Issue Type: Bug > Components: Java Client, Java Tests >Affects Versions: 0.10, 0.11, 0.12 >Reporter: Alex Rudyy >Assignee: Keith Wall >Priority: Minor > Attachments: > QPID-3453-Fixes-an-issue-with-closing-of-detached-session.patch > > > The PersistentStoreTest: fails as follows: > connection closed > org.apache.qpid.transport.ConnectionException: connection closed > at org.apache.qpid.transport.Connection.send(Connection.java:358) > at org.apache.qpid.transport.Session.send(Session.java:498) > at org.apache.qpid.transport.Session.invoke(Session.java:707) > at org.apache.qpid.transport.Session.invoke(Session.java:523) > at > org.apache.qpid.transport.SessionInvoker.sessionRequestTimeout(SessionInvoker.java:48) > at org.apache.qpid.transport.Session.close(Session.java:917) > at org.apache.qpid.client.AMQSession_0_10.sendClose(AMQSession_0_10.java:388) > at org.apache.qpid.client.AMQSession.close(AMQSession.java:729) > at org.apache.qpid.client.AMQSession.close(AMQSession.java:695) > at > org.apache.qpid.client.AMQConnection.closeAllSessions(AMQConnection.java:1147) > at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1041) > at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1030) > On stopping broker, the underlining transport connection is closed and > transport session is put into DETACHED state. > Corresponding AMQSession remains in an open state. > On invoking of AMQConnection#close() method all open AMQSessions are put into > closed state and for each AMQSession method sendClose is invoked. > AMQSession_0_10#sendClose(long) calls close() method for underlying DETACHED > transport session which fails because transport connection is already closed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3454) System test StreamMessageTest would not detect regression in StreamMessage buffer expansion.
[ https://issues.apache.org/jira/browse/QPID-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-3454: Assignee: Robbie Gemmell (was: Keith Wall) Hi Robbie, can you review this change please? > System test StreamMessageTest would not detect regression in StreamMessage > buffer expansion. > > > Key: QPID-3454 > URL: https://issues.apache.org/jira/browse/QPID-3454 > Project: Qpid > Issue Type: Bug > Components: Java Tests >Affects Versions: 0.10, 0.11, 0.12 >Reporter: Keith Wall >Assignee: Robbie Gemmell > Fix For: 0.13 > > > A defect in the logic of > StreamMessageTest#testModifyReceivedMessageExpandsBuffer would mean that a > regression could go unnoticed. > The test incorrectly uses a Junit assertion _within_ an onMessage. > Unfortunately if this assertion were to ever fail, the Junit test harness > would not hear the assertion fail as onMessage is executed by a separate > thread. > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Resolved] (QPID-3266) Tidy up housekeeping configuration option for scheduling frequency: expiredMessageCheckPeriod vs checkPeriod
[ https://issues.apache.org/jira/browse/QPID-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-3266. -- Resolution: Fixed Patch applied. > Tidy up housekeeping configuration option for scheduling frequency: > expiredMessageCheckPeriod vs checkPeriod > > > Key: QPID-3266 > URL: https://issues.apache.org/jira/browse/QPID-3266 > Project: Qpid > Issue Type: Task > Components: Java Broker >Affects Versions: 0.10 >Reporter: Keith Wall >Assignee: Keith Wall >Priority: Minor > Attachments: > 0001-QPID-3266-Tidy-up-housekeeping-configuration-option-.patch > > > QPID-430 renamed the configuration option controlling the frequency of the > housekeeping thread from expiredMessageCheckPeriod to checkPeriod to reflect > that fact that the Housekeeping thread had acquired more responsibilities. > Unfortunately it appears that there difficulties during a merge and we are > now left with different configuration names at different levels within the > configuration. > At we have: > > and > (supported as a synonym of checkPeriod) > whereas at we support only: > > The task is to clean up the configuration classes. I suggest that we > standardise on and issue a clear warning if the old option is > encountered. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Created] (QPID-3456) Python and C++ clients behave differently
Python and C++ clients behave differently
-
Key: QPID-3456
URL: https://issues.apache.org/jira/browse/QPID-3456
Project: Qpid
Issue Type: Bug
Components: C++ Client, Python Client
Affects Versions: 0.13
Reporter: Tomas Soltys
Priority: Minor
Python and C++ clients sends different commands to the broker.
Address:
response/response.QPID_CLIENT.response_queue_1;
{
create: receiver,
link:
{
name: 'response.QPID_CLIENT.response_queue_1',
durable: false,
x-declare:
{
auto-delete: true,
exclusive: true,
arguments:
{
'qpid.max_count': 1000,
'qpid.max_size': 100,
'qpid.policy_type': ring
}
}
}
}
I have set the log level to trace+ on my broker and here is what I got from the
log when I have used the same same addres for python as well as for c++ client.
Python:
2011-08-26 12:13:08 trace
QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 0:
{ExchangeQueryBody: name=response; }
2011-08-26 12:13:08 trace
QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 1:
{QueueQueryBody: queue=response; }
2011-08-26 12:13:08 trace
QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 2:
{QueueDeclareBody: queue=response.QPID_CLIENT.response_queue_1; exclusive=1;
auto-delete=1;
arguments={qpid.max_count:F8:int64(1000),qpid.max_size:F8:int64(100),qpid.policy_type:V2:4:str16(ring)};
}
2011-08-26 12:13:08 trace
QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 3:
{ExchangeBindBody: queue=response.QPID_CLIENT.response_queue_1;
exchange=response; binding-key=response.QPID_CLIENT.response_queue_1; }
2011-08-26 12:13:08 trace
QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 4:
{MessageSubscribeBody: queue=response.QPID_CLIENT.response_queue_1;
destination=0; accept-mode=0; acquire-mode=0; }
2011-08-26 12:13:08 trace
QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 5:
{MessageSetFlowModeBody: destination=0; flow-mode=0; }
2011-08-26 12:13:08 trace
QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 6:
{MessageCancelBody: destination=0; }
2011-08-26 12:13:08 trace
QPID_CLIENT@QPID.7ce755ba-f29b-4532-8af9-b52dad8e8450:0: recv cmd 7:
{QueueDeleteBody: queue=response.QPID_CLIENT.response_queue_1; }
C++:
2011-08-26 12:15:48 trace
QPID_CLIENT@QPID.a167bd61-8aa3-4900-9ee7-a646bf3c1c63: recv cmd 0:
{ExecutionSyncBody: }
2011-08-26 12:15:48 trace
QPID_CLIENT@QPID.a167bd61-8aa3-4900-9ee7-a646bf3c1c63: recv cmd 1:
{ExchangeQueryBody: name=response; }
2011-08-26 12:15:48 trace
QPID_CLIENT@QPID.a167bd61-8aa3-4900-9ee7-a646bf3c1c63: recv cmd 2:
{ExchangeDeclareBody: exchange=response; type=topic; alternate-exchange=;
arguments={}; }
C++ client will get 'ACL denied exchange declare request from
QPID_CLIENT@QPID' from the broker.
So to make the C++ client to be able to pass through I had to change the adress
as followed:
response/response.QPID_CLIENT.response_queue_1;
{
assert: never,
create: never,
node :
{
type: topic
},
link:
{
name: 'response.QPID_CLIENT.response_queue_1',
durable: false,
x-declare:
{
auto-delete: true,
exclusive: true,
arguments:
{
'qpid.max_count': 1000,
'qpid.max_size': 100,
'qpid.policy_type': ring
}
}
}
}
And I had to add two ACL rules:
acl allow members create exchange name=response passive=true
acl allow QPID_CLIENT@QPID create queuename=response.QPID_CLIENT.*
passive=true
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-2901) A number of tests sporadically fails with 0.10 profiles on attempt to commit transaction due to exception in org.apache.qpid.transport.Session#sync
[ https://issues.apache.org/jira/browse/QPID-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-2901: - Attachment: QPID-2901-Fixes-racing-conditions-on-closing-session-from-SCDP.patch The attached patch fixes the problem by changing the following: - subscription send locks are acquired before closing the session from SCDP - transport session closing state is checked in Subscription_0_10#isSuspended method > A number of tests sporadically fails with 0.10 profiles on attempt to commit > transaction due to exception in org.apache.qpid.transport.Session#sync > --- > > Key: QPID-2901 > URL: https://issues.apache.org/jira/browse/QPID-2901 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Affects Versions: 0.7, 0.8, 0.9, 0.10, 0.11, 0.12 >Reporter: Robbie Gemmell > Attachments: > QPID-2901-Fixes-racing-conditions-on-closing-session-from-SCDP.patch > > > The following stack trace is printed for failed commit > org.apache.qpid.transport.SessionException: ch=0 id=0 > ExecutionException(errorCode=INTERNAL_ERROR, commandId=13, > description=Exception processing command: java.lang.RuntimeException: Failed > to commit transaction) > at org.apache.qpid.transport.Session.sync(Session.java:807) > at org.apache.qpid.transport.Session.sync(Session.java:772) > at org.apache.qpid.transport.Session.invoke(Session.java:732) > at org.apache.qpid.transport.Session.invoke(Session.java:561) > at > org.apache.qpid.transport.SessionInvoker.txCommit(SessionInvoker.java:148) > at > org.apache.qpid.client.AMQSession_0_10.sendCommit(AMQSession_0_10.java:423) > at > org.apache.qpid.client.AMQSession_0_10.commit(AMQSession_0_10.java:1008) > at > org.apache.qpid.systest.TestingBaseCase$1.run(TestingBaseCase.java:105) > at java.lang.Thread.run(Thread.java:619) > This is the list of failing tests: > org.apache.qpid.systest.SubscriptionTest#testTopicDurableConsumerMessageAge > org.apache.qpid.systest.SubscriptionTest#testTopicDurableConsumerMessageCount > org.apache.qpid.systest.TopicTest#org.apache.qpid.systest.TopicTest > org.apache.qpid.systest.TopicTest#testTopicDurableConsumerMessageAge > org.apache.qpid.systest.GlobalQueuesTest#testTopicDurableConsumerMessageAge > org.apache.qpid.systest.GlobalTopicsTest#testTopicDurableConsumerMessageSize > org.apache.qpid.systest.GlobalTopicsTest#testTopicDurableConsumerMessageAge -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Commented] (QPID-2901) A number of tests sporadically fails with 0.10 profiles on attempt to commit transaction due to exception in org.apache.qpid.transport.Session#sync
[ https://issues.apache.org/jira/browse/QPID-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091765#comment-13091765 ] Alex Rudyy commented on QPID-2901: -- These tests fail due to racing condition on broker side when TopicDelitePolicy closed the consumer session but broker tries to deliver next message to a subscription with this closed session. Because session is closed the exception is thrown on post commit and that exception is propagated back into producer client. The following stack trace demonstrates the problem BROKER: org.apache.qpid.transport.SessionClosedException: session closed BROKER: at org.apache.qpid.transport.Session.invoke(Session.java:629) BROKER: at org.apache.qpid.server.transport.ServerSession.sendMessage(ServerSession.java:203) BROKER: at org.apache.qpid.server.subscription.Subscription_0_10.send(Subscription_0_10.java:602) BROKER: at org.apache.qpid.server.queue.SimpleAMQQueue.deliverMessage(SimpleAMQQueue.java:747) BROKER: at org.apache.qpid.server.queue.SimpleAMQQueue.deliverToSubscription(SimpleAMQQueue.java:688) BROKER: at org.apache.qpid.server.queue.SimpleAMQQueue.enqueue(SimpleAMQQueue.java:588) BROKER: at org.apache.qpid.server.queue.SimpleAMQQueue.enqueue(SimpleAMQQueue.java:566) BROKER: at org.apache.qpid.server.transport.ServerSession$1.postCommit(ServerSession.java:179) BROKER: at org.apache.qpid.server.txn.LocalTransaction.commit(LocalTransaction.java:254) BROKER: at org.apache.qpid.server.transport.ServerSession.commit(ServerSession.java:449) BROKER: at org.apache.qpid.server.transport.ServerSessionDelegate.txCommit(ServerSessionDelegate.java:441) BROKER: at org.apache.qpid.server.transport.ServerSessionDelegate.txCommit(ServerSessionDelegate.java:98) BROKER: at org.apache.qpid.transport.TxCommit.dispatch(TxCommit.java:91) BROKER: at org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50) BROKER: at org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:116) BROKER: at org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:98) BROKER: at org.apache.qpid.transport.Method.delegate(Method.java:159) BROKER: at org.apache.qpid.transport.Session.received(Session.java:530) BROKER: at org.apache.qpid.transport.Connection.dispatch(Connection.java:404) BROKER: at org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64) BROKER: at org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40) BROKER: at org.apache.qpid.transport.MethodDelegate.txCommit(MethodDelegate.java:152) BROKER: at org.apache.qpid.transport.TxCommit.dispatch(TxCommit.java:91) BROKER: at org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54) BROKER: at org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40) BROKER: at org.apache.qpid.transport.Method.delegate(Method.java:159) BROKER: at org.apache.qpid.transport.Connection.received(Connection.java:369) BROKER: at org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:210) BROKER: at org.apache.qpid.server.transport.ServerConnection.received(ServerConnection.java:56) BROKER: at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95) BROKER: at org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:196) BROKER: at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:129) BROKER: at org.apache.qpid.transport.network.Frame.delegate(Frame.java:133) BROKER: at org.apache.qpid.transport.network.Assembler.received(Assembler.java:100) BROKER: at org.apache.qpid.transport.network.Assembler.received(Assembler.java:42) BROKER: at org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:187) BROKER: at org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:103) BROKER: at org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:42) BROKER: at org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:101) BROKER: at org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:36) BROKER: at org.apache.qpid.transport.network.mina.MinaNetworkHandler.messageReceived(MinaNetworkHandler.java:78) BROKER: at org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageReceived(AbstractIoFilterChain.java:570) BROKER: at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299) BROKER: at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53) BROKER: at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648) BROKER: at org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:220) BROKER: at org.apache.mina.f
[jira] [Commented] (QPID-3453) Test PersistentStoreTest fails on java-bdb-spawn.0-10 profile
[ https://issues.apache.org/jira/browse/QPID-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091750#comment-13091750 ] Alex Rudyy commented on QPID-3453: -- Keith, I uploaded a new patch with simplified version of test > Test PersistentStoreTest fails on java-bdb-spawn.0-10 profile > - > > Key: QPID-3453 > URL: https://issues.apache.org/jira/browse/QPID-3453 > Project: Qpid > Issue Type: Bug > Components: Java Client, Java Tests >Affects Versions: 0.10, 0.11, 0.12 >Reporter: Alex Rudyy >Assignee: Keith Wall >Priority: Minor > Attachments: > QPID-3453-Fixes-an-issue-with-closing-of-detached-session.patch > > > The PersistentStoreTest: fails as follows: > connection closed > org.apache.qpid.transport.ConnectionException: connection closed > at org.apache.qpid.transport.Connection.send(Connection.java:358) > at org.apache.qpid.transport.Session.send(Session.java:498) > at org.apache.qpid.transport.Session.invoke(Session.java:707) > at org.apache.qpid.transport.Session.invoke(Session.java:523) > at > org.apache.qpid.transport.SessionInvoker.sessionRequestTimeout(SessionInvoker.java:48) > at org.apache.qpid.transport.Session.close(Session.java:917) > at org.apache.qpid.client.AMQSession_0_10.sendClose(AMQSession_0_10.java:388) > at org.apache.qpid.client.AMQSession.close(AMQSession.java:729) > at org.apache.qpid.client.AMQSession.close(AMQSession.java:695) > at > org.apache.qpid.client.AMQConnection.closeAllSessions(AMQConnection.java:1147) > at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1041) > at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1030) > On stopping broker, the underlining transport connection is closed and > transport session is put into DETACHED state. > Corresponding AMQSession remains in an open state. > On invoking of AMQConnection#close() method all open AMQSessions are put into > closed state and for each AMQSession method sendClose is invoked. > AMQSession_0_10#sendClose(long) calls close() method for underlying DETACHED > transport session which fails because transport connection is already closed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3453) Test PersistentStoreTest fails on java-bdb-spawn.0-10 profile
[ https://issues.apache.org/jira/browse/QPID-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-3453: - Attachment: (was: QPID-3453-Fixes-an-issue-with-closing-of-detached-session.patch) > Test PersistentStoreTest fails on java-bdb-spawn.0-10 profile > - > > Key: QPID-3453 > URL: https://issues.apache.org/jira/browse/QPID-3453 > Project: Qpid > Issue Type: Bug > Components: Java Client, Java Tests >Affects Versions: 0.10, 0.11, 0.12 >Reporter: Alex Rudyy >Assignee: Keith Wall >Priority: Minor > Attachments: > QPID-3453-Fixes-an-issue-with-closing-of-detached-session.patch > > > The PersistentStoreTest: fails as follows: > connection closed > org.apache.qpid.transport.ConnectionException: connection closed > at org.apache.qpid.transport.Connection.send(Connection.java:358) > at org.apache.qpid.transport.Session.send(Session.java:498) > at org.apache.qpid.transport.Session.invoke(Session.java:707) > at org.apache.qpid.transport.Session.invoke(Session.java:523) > at > org.apache.qpid.transport.SessionInvoker.sessionRequestTimeout(SessionInvoker.java:48) > at org.apache.qpid.transport.Session.close(Session.java:917) > at org.apache.qpid.client.AMQSession_0_10.sendClose(AMQSession_0_10.java:388) > at org.apache.qpid.client.AMQSession.close(AMQSession.java:729) > at org.apache.qpid.client.AMQSession.close(AMQSession.java:695) > at > org.apache.qpid.client.AMQConnection.closeAllSessions(AMQConnection.java:1147) > at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1041) > at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1030) > On stopping broker, the underlining transport connection is closed and > transport session is put into DETACHED state. > Corresponding AMQSession remains in an open state. > On invoking of AMQConnection#close() method all open AMQSessions are put into > closed state and for each AMQSession method sendClose is invoked. > AMQSession_0_10#sendClose(long) calls close() method for underlying DETACHED > transport session which fails because transport connection is already closed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3453) Test PersistentStoreTest fails on java-bdb-spawn.0-10 profile
[ https://issues.apache.org/jira/browse/QPID-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-3453: - Attachment: QPID-3453-Fixes-an-issue-with-closing-of-detached-session.patch > Test PersistentStoreTest fails on java-bdb-spawn.0-10 profile > - > > Key: QPID-3453 > URL: https://issues.apache.org/jira/browse/QPID-3453 > Project: Qpid > Issue Type: Bug > Components: Java Client, Java Tests >Affects Versions: 0.10, 0.11, 0.12 >Reporter: Alex Rudyy >Assignee: Keith Wall >Priority: Minor > Attachments: > QPID-3453-Fixes-an-issue-with-closing-of-detached-session.patch > > > The PersistentStoreTest: fails as follows: > connection closed > org.apache.qpid.transport.ConnectionException: connection closed > at org.apache.qpid.transport.Connection.send(Connection.java:358) > at org.apache.qpid.transport.Session.send(Session.java:498) > at org.apache.qpid.transport.Session.invoke(Session.java:707) > at org.apache.qpid.transport.Session.invoke(Session.java:523) > at > org.apache.qpid.transport.SessionInvoker.sessionRequestTimeout(SessionInvoker.java:48) > at org.apache.qpid.transport.Session.close(Session.java:917) > at org.apache.qpid.client.AMQSession_0_10.sendClose(AMQSession_0_10.java:388) > at org.apache.qpid.client.AMQSession.close(AMQSession.java:729) > at org.apache.qpid.client.AMQSession.close(AMQSession.java:695) > at > org.apache.qpid.client.AMQConnection.closeAllSessions(AMQConnection.java:1147) > at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1041) > at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1030) > On stopping broker, the underlining transport connection is closed and > transport session is put into DETACHED state. > Corresponding AMQSession remains in an open state. > On invoking of AMQConnection#close() method all open AMQSessions are put into > closed state and for each AMQSession method sendClose is invoked. > AMQSession_0_10#sendClose(long) calls close() method for underlying DETACHED > transport session which fails because transport connection is already closed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3453) Test PersistentStoreTest fails on java-bdb-spawn.0-10 profile
[ https://issues.apache.org/jira/browse/QPID-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-3453: Assignee: Keith Wall Keith, could you have a look at attached patch again? > Test PersistentStoreTest fails on java-bdb-spawn.0-10 profile > - > > Key: QPID-3453 > URL: https://issues.apache.org/jira/browse/QPID-3453 > Project: Qpid > Issue Type: Bug > Components: Java Client, Java Tests >Affects Versions: 0.10, 0.11, 0.12 >Reporter: Alex Rudyy >Assignee: Keith Wall >Priority: Minor > Attachments: > QPID-3453-Fixes-an-issue-with-closing-of-detached-session.patch > > > The PersistentStoreTest: fails as follows: > connection closed > org.apache.qpid.transport.ConnectionException: connection closed > at org.apache.qpid.transport.Connection.send(Connection.java:358) > at org.apache.qpid.transport.Session.send(Session.java:498) > at org.apache.qpid.transport.Session.invoke(Session.java:707) > at org.apache.qpid.transport.Session.invoke(Session.java:523) > at > org.apache.qpid.transport.SessionInvoker.sessionRequestTimeout(SessionInvoker.java:48) > at org.apache.qpid.transport.Session.close(Session.java:917) > at org.apache.qpid.client.AMQSession_0_10.sendClose(AMQSession_0_10.java:388) > at org.apache.qpid.client.AMQSession.close(AMQSession.java:729) > at org.apache.qpid.client.AMQSession.close(AMQSession.java:695) > at > org.apache.qpid.client.AMQConnection.closeAllSessions(AMQConnection.java:1147) > at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1041) > at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1030) > On stopping broker, the underlining transport connection is closed and > transport session is put into DETACHED state. > Corresponding AMQSession remains in an open state. > On invoking of AMQConnection#close() method all open AMQSessions are put into > closed state and for each AMQSession method sendClose is invoked. > AMQSession_0_10#sendClose(long) calls close() method for underlying DETACHED > transport session which fails because transport connection is already closed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3453) Test PersistentStoreTest fails on java-bdb-spawn.0-10 profile
[ https://issues.apache.org/jira/browse/QPID-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-3453: - Attachment: (was: 0001-Fixes-an-issue-with-closing-of-detached-session.patch) > Test PersistentStoreTest fails on java-bdb-spawn.0-10 profile > - > > Key: QPID-3453 > URL: https://issues.apache.org/jira/browse/QPID-3453 > Project: Qpid > Issue Type: Bug > Components: Java Client, Java Tests >Affects Versions: 0.10, 0.11, 0.12 >Reporter: Alex Rudyy >Priority: Minor > Attachments: > QPID-3453-Fixes-an-issue-with-closing-of-detached-session.patch > > > The PersistentStoreTest: fails as follows: > connection closed > org.apache.qpid.transport.ConnectionException: connection closed > at org.apache.qpid.transport.Connection.send(Connection.java:358) > at org.apache.qpid.transport.Session.send(Session.java:498) > at org.apache.qpid.transport.Session.invoke(Session.java:707) > at org.apache.qpid.transport.Session.invoke(Session.java:523) > at > org.apache.qpid.transport.SessionInvoker.sessionRequestTimeout(SessionInvoker.java:48) > at org.apache.qpid.transport.Session.close(Session.java:917) > at org.apache.qpid.client.AMQSession_0_10.sendClose(AMQSession_0_10.java:388) > at org.apache.qpid.client.AMQSession.close(AMQSession.java:729) > at org.apache.qpid.client.AMQSession.close(AMQSession.java:695) > at > org.apache.qpid.client.AMQConnection.closeAllSessions(AMQConnection.java:1147) > at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1041) > at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1030) > On stopping broker, the underlining transport connection is closed and > transport session is put into DETACHED state. > Corresponding AMQSession remains in an open state. > On invoking of AMQConnection#close() method all open AMQSessions are put into > closed state and for each AMQSession method sendClose is invoked. > AMQSession_0_10#sendClose(long) calls close() method for underlying DETACHED > transport session which fails because transport connection is already closed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3453) Test PersistentStoreTest fails on java-bdb-spawn.0-10 profile
[ https://issues.apache.org/jira/browse/QPID-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-3453: - Attachment: QPID-3453-Fixes-an-issue-with-closing-of-detached-session.patch > Test PersistentStoreTest fails on java-bdb-spawn.0-10 profile > - > > Key: QPID-3453 > URL: https://issues.apache.org/jira/browse/QPID-3453 > Project: Qpid > Issue Type: Bug > Components: Java Client, Java Tests >Affects Versions: 0.10, 0.11, 0.12 >Reporter: Alex Rudyy >Priority: Minor > Attachments: > QPID-3453-Fixes-an-issue-with-closing-of-detached-session.patch > > > The PersistentStoreTest: fails as follows: > connection closed > org.apache.qpid.transport.ConnectionException: connection closed > at org.apache.qpid.transport.Connection.send(Connection.java:358) > at org.apache.qpid.transport.Session.send(Session.java:498) > at org.apache.qpid.transport.Session.invoke(Session.java:707) > at org.apache.qpid.transport.Session.invoke(Session.java:523) > at > org.apache.qpid.transport.SessionInvoker.sessionRequestTimeout(SessionInvoker.java:48) > at org.apache.qpid.transport.Session.close(Session.java:917) > at org.apache.qpid.client.AMQSession_0_10.sendClose(AMQSession_0_10.java:388) > at org.apache.qpid.client.AMQSession.close(AMQSession.java:729) > at org.apache.qpid.client.AMQSession.close(AMQSession.java:695) > at > org.apache.qpid.client.AMQConnection.closeAllSessions(AMQConnection.java:1147) > at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1041) > at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:1030) > On stopping broker, the underlining transport connection is closed and > transport session is put into DETACHED state. > Corresponding AMQSession remains in an open state. > On invoking of AMQConnection#close() method all open AMQSessions are put into > closed state and for each AMQSession method sendClose is invoked. > AMQSession_0_10#sendClose(long) calls close() method for underlying DETACHED > transport session which fails because transport connection is already closed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Resolved] (QPID-3455) Large message sent over sasl_wrapper encryption layer causes infinite loop in broker
[ https://issues.apache.org/jira/browse/QPID-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3455. -- Resolution: Fixed > Large message sent over sasl_wrapper encryption layer causes infinite loop in > broker > > > Key: QPID-3455 > URL: https://issues.apache.org/jira/browse/QPID-3455 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.12 >Reporter: Gordon Sim >Assignee: Gordon Sim > Fix For: 0.13 > > > This is a result of an incorrectly set max-frame-size on the broker. The > buffer used for decoding after decryption is therefore too small and the > frame cannot be decoded. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3266) Tidy up housekeeping configuration option for scheduling frequency: expiredMessageCheckPeriod vs checkPeriod
[ https://issues.apache.org/jira/browse/QPID-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3266: - Attachment: (was: 0001-QPID-3266-Tidy-up-housekeeping-configuration-option-.patch) > Tidy up housekeeping configuration option for scheduling frequency: > expiredMessageCheckPeriod vs checkPeriod > > > Key: QPID-3266 > URL: https://issues.apache.org/jira/browse/QPID-3266 > Project: Qpid > Issue Type: Task > Components: Java Broker >Affects Versions: 0.10 >Reporter: Keith Wall >Assignee: Keith Wall >Priority: Minor > Attachments: > 0001-QPID-3266-Tidy-up-housekeeping-configuration-option-.patch > > > QPID-430 renamed the configuration option controlling the frequency of the > housekeeping thread from expiredMessageCheckPeriod to checkPeriod to reflect > that fact that the Housekeeping thread had acquired more responsibilities. > Unfortunately it appears that there difficulties during a merge and we are > now left with different configuration names at different levels within the > configuration. > At we have: > > and > (supported as a synonym of checkPeriod) > whereas at we support only: > > The task is to clean up the configuration classes. I suggest that we > standardise on and issue a clear warning if the old option is > encountered. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3266) Tidy up housekeeping configuration option for scheduling frequency: expiredMessageCheckPeriod vs checkPeriod
[ https://issues.apache.org/jira/browse/QPID-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3266: - Attachment: 0001-QPID-3266-Tidy-up-housekeeping-configuration-option-.patch > Tidy up housekeeping configuration option for scheduling frequency: > expiredMessageCheckPeriod vs checkPeriod > > > Key: QPID-3266 > URL: https://issues.apache.org/jira/browse/QPID-3266 > Project: Qpid > Issue Type: Task > Components: Java Broker >Affects Versions: 0.10 >Reporter: Keith Wall >Assignee: Keith Wall >Priority: Minor > Attachments: > 0001-QPID-3266-Tidy-up-housekeeping-configuration-option-.patch > > > QPID-430 renamed the configuration option controlling the frequency of the > housekeeping thread from expiredMessageCheckPeriod to checkPeriod to reflect > that fact that the Housekeeping thread had acquired more responsibilities. > Unfortunately it appears that there difficulties during a merge and we are > now left with different configuration names at different levels within the > configuration. > At we have: > > and > (supported as a synonym of checkPeriod) > whereas at we support only: > > The task is to clean up the configuration classes. I suggest that we > standardise on and issue a clear warning if the old option is > encountered. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Created] (QPID-3455) Large message sent over sasl_wrapper encryption layer causes infinite loop in broker
Large message sent over sasl_wrapper encryption layer causes infinite loop in broker Key: QPID-3455 URL: https://issues.apache.org/jira/browse/QPID-3455 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.12 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.13 This is a result of an incorrectly set max-frame-size on the broker. The buffer used for decoding after decryption is therefore too small and the frame cannot be decoded. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3266) Tidy up housekeeping configuration option for scheduling frequency: expiredMessageCheckPeriod vs checkPeriod
[ https://issues.apache.org/jira/browse/QPID-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3266: - Attachment: 0001-QPID-3266-Tidy-up-housekeeping-configuration-option-.patch Proposed patch to resolve this Jira. > Tidy up housekeeping configuration option for scheduling frequency: > expiredMessageCheckPeriod vs checkPeriod > > > Key: QPID-3266 > URL: https://issues.apache.org/jira/browse/QPID-3266 > Project: Qpid > Issue Type: Task > Components: Java Broker >Affects Versions: 0.10 >Reporter: Keith Wall >Assignee: Keith Wall >Priority: Minor > Attachments: > 0001-QPID-3266-Tidy-up-housekeeping-configuration-option-.patch > > > QPID-430 renamed the configuration option controlling the frequency of the > housekeeping thread from expiredMessageCheckPeriod to checkPeriod to reflect > that fact that the Housekeeping thread had acquired more responsibilities. > Unfortunately it appears that there difficulties during a merge and we are > now left with different configuration names at different levels within the > configuration. > At we have: > > and > (supported as a synonym of checkPeriod) > whereas at we support only: > > The task is to clean up the configuration classes. I suggest that we > standardise on and issue a clear warning if the old option is > encountered. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: public facing CI for the C++ components
On 23 Aug 2011, at 09:35, Robbie Gemmell wrote: > Hi all, > > I think it would be a good idea if we could get some public facing CI > set up for the C++ components. There have been various issues which > have gone unnnoticed in recent weeks at least in part due to the lack > of CI as a fallback after not spotting the issues otherwise. We have > some projects set up for the Java tree on the ASF Jenkins instances > (more to follow, once we get some issues with the framework sorted > out), it would be good to get something set up for the C++ broker, > either directly running there or through its remote results reporting > abilities. > > Any volunteers willing to get involved? Hi. I had managed to get a C++ build working on Jenkins on an EC2 instance where I had full control of the packages installed, namely Boost and AIS/corosync and so forth. I'm not sure whether it is possible to install these libraries as a normal user, in non /usr/lib locations, and still build Qpid? If not, this would preclude using the ASF infrastructure to run CI. I will give it a shot, otherwise I can investigate using Amazon EC2 to run the C++ builds. It should be simple to have all the CI results reported to the notifications list, regardless of their origin, although we may need help from infra to accomplish this from an external source. Andrew. -- -- andrew d kennedy ? +447582293255 : http://grkvlt.blogspot.com/ ; - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Commented] (QPID-2720) Qpid broker can not run inside an OSGi container
[
https://issues.apache.org/jira/browse/QPID-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091700#comment-13091700
]
Keith Wall commented on QPID-2720:
--
I think this commit is causing a NPE stack trace to be logged when running some
tests (during tearDown). It is not causing test failure as the exception is
being swallowed. I'm seeing it when running ServerConfigurationTest, but I'm
sure I see it elsewhere too.
{code}
main 2011-08-26 11:12:59,056 ERROR [qpid.server.registry.ApplicationRegistry]
Error thrown whilst closing PluginManager
java.lang.NullPointerException
at
org.apache.qpid.server.plugins.PluginManager.close(PluginManager.java:356)
at
org.apache.qpid.server.registry.ApplicationRegistry.close(ApplicationRegistry.java:443)
at
org.apache.qpid.server.registry.ApplicationRegistry.close(ApplicationRegistry.java:478)
at
org.apache.qpid.server.registry.ApplicationRegistry.remove(ApplicationRegistry.java:203)
at
org.apache.qpid.server.configuration.ServerConfigurationTest.tearDown(ServerConfigurationTest.java:58)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:132)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:518)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1052)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:906)
{code}
> Qpid broker can not run inside an OSGi container
>
>
> Key: QPID-2720
> URL: https://issues.apache.org/jira/browse/QPID-2720
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Reporter: Danushka Menikkumbura
>Assignee: Danushka Menikkumbura
> Fix For: 0.13
>
> Attachments: QPID-2720-V2.patch, QPID-2720-V3.patch, QPID-2720.patch
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-2720) Qpid broker can not run inside an OSGi container
[ https://issues.apache.org/jira/browse/QPID-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-2720: - Status: Open (was: Ready To Review) > Qpid broker can not run inside an OSGi container > > > Key: QPID-2720 > URL: https://issues.apache.org/jira/browse/QPID-2720 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Danushka Menikkumbura >Assignee: Danushka Menikkumbura > Fix For: 0.13 > > Attachments: QPID-2720-V2.patch, QPID-2720-V3.patch, QPID-2720.patch > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
