[jira] [Resolved] (QPID-4873) Optimizations in Java client to reduce queue memory footprint
[ https://issues.apache.org/jira/browse/QPID-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-4873. Resolution: Fixed Committed the patch from Helen with modifications to accommodate the suggestions made in the comments. http://svn.apache.org/r1485878 > Optimizations in Java client to reduce queue memory footprint > - > > Key: QPID-4873 > URL: https://issues.apache.org/jira/browse/QPID-4873 > Project: Qpid > Issue Type: Improvement > Components: Java Client, Java Common >Affects Versions: 0.23 >Reporter: Helen Kwong >Assignee: Rajith Attapattu >Priority: Minor > Fix For: 0.23 > > Attachments: ClientQueueMemoryOptimizations.patch > > > My team is using the Java broker and Java client, version 0.16, and looking > to lower the client's memory footprint on our servers. We did some heap > analysis and found that the consumption is coming mostly from > AMQAnyDestination instances, each having a retained size close to ~3KB, and > since we have 6000 queues on each of our 2 brokers, this amounts to about > ~33MB, which is valuable real estate for us. In our analysis we found a few > possible optimizations in the Qpid code that would reduce the per-queue heap > consumption and which don't seem high risk, and would like to propose the > following changes (will attach a patch file). > (I had originally emailed the users list 2 weeks ago, and Rob Godfrey asked > me to raise a JIRA with the changes in a patch file -- > http://mail-archives.apache.org/mod_mbox/qpid-users/201305.mbox/%3CCACsaS94F0MQeyAKTN3yoU=j-MPc6oFWZgtCtj68GAwOcN=5...@mail.gmail.com%3E) > The changes I attach here are with the trunk code and I've redone the numbers > / analysis running with the latest client. > 1. In Address / AddressParser, cacheing / reusing the options Maps for queues > created with the same options string. (This optimization gives us the most > significant savings.) > All our queues are created with the same options string, which means each > corresponding AMQDestination has an Address that has an _options Map that is > the same for all queues, i.e., 12K copies of the same map. As far as we can > tell, the _options map is effectively immutable, i.e., there is no code path > by which an Address’s _options map can be modified. (Is this correct?) So a > possible improvement is that in org.apache.qpid.messaging.util.AddressParser, > we cache the options map for each options string that we've already > encountered, and if the options string passed in has already been seen, we > use the stored options map for that Address. This way, for queues having the > same options, their Address options will reference the same Map. (For our > queues, each Address _options Map currently takes up 1416 B.) > 2. AMQDestination's _link field -- > org.apache.qpid.client.messaging.address.Link > Optimization A: org.apache.qpid.client.messaging.address.Link$Subscription's > args field is by default a new HashMap with default capacity 16. In our use > case it remains empty for all queues. A possible optimization is to set the > default value as Collections.emptyMap() instead. As far was we can tell, > Subscription.getArgs() is not used to get the map and then modify it. For us > this saves 128B per queue. > Optimization B: Similarly, Link has a _bindings List that is by default a new > ArrayList with a default capacity of 10. In our use case it remains empty for > all queues, and as far as we can tell this list is not modified after it is > set. If we make the default value Collections.emptyList() instead, it will > save us 80B per queue. > 3. AMQDestination's _node field -- > org.apache.qpid.client.messaging.address.Node > Node has a _bindings List that is by default a new ArrayList with the default > capacity. In our use case _bindings remains empty for all queues, and I don't > see getBindings() being used to get the list and then modify it. I also don't > see addBindings() being called anywhere in the client. So a possible > optimization is to set the default value as Collections.emptyList() instead. > For us this saves 80B per queue. > The changes in AddressHelper.getBindings() are for the case when there are > node or link properties defined, but no bindings. > Overall: Originally, each queue took up about 2760B for us; with these > optimizations, that goes down to 1024B, saving 63% per queue for us. > We'd appreciate feedback on these changes and whether we are making any > incorrect assumptions. I've also added relevant tests to AMQDestinationTest > but am not sure if that's the best place. Thanks a lot! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please conta
Re: [VOTE] Release 0.22
Justin, I hope it is still not too late to request the inclusion into 0.22 of a minor fix for Windows batch script to start Java Broker ( http://svn.apache.org/r1485859 QPID-4881). We introduced new command line arguments requiring to pass an equal character as part of the argument but the batch script splits the command line argument with 'equal' into two arguments and removes equal character. Such arguments have to be quoted but processing of quoted arguments resulted in the errors. The changes fixed the processing of quoted arguments. It is a minor issue and there are some workarounds but I would like to request the inclusion of the fix as it is quite trivial. Kind Regards, Alex On 23 May 2013 22:40, Ken Giusti wrote: > Justin, > > A new RC, you say? > > Well, I'll just leave this little tidbit here, ya know, just in case: > > https://issues.apache.org/jira/browse/QPID-4883 > > /backs slowly away from my keyboard > > > > - Original Message - > > From: "Justin Ross" > > To: dev@qpid.apache.org > > Sent: Thursday, May 23, 2013 10:34:58 AM > > Subject: Re: [VOTE] Release 0.22 > > > > This vote is withdrawn. We'll have a new RC later today. The only > > new change will be the cmake build fix. Once that's available, I'll > > start a new vote thread. > > > > Justin > > > > On Wed, May 22, 2013 at 5:14 PM, Justin Ross wrote: > > > Okay, we'll fix it tomorrow. > > > > > > On May 22, 2013 4:09 PM, "Darryl L. Pierce" > wrote: > > >> > > >> On Wed, May 22, 2013 at 01:54:50PM -0400, Justin Ross wrote: > > >> > RC5 contains the proposed final bits for Qpid 0.22. > > >> > > > >> > If you favor making the RC5 bits into our official release, vote +1. > > >> > If you have reason to believe RC5 is not ready for release, vote -1. > > >> > > > >> > I will close this vote on Monday, 22 May. I know that's a little > > >> > brief, but I have some vacation time coming up soon, and I'm hoping > to > > >> > finish the release before I leave. > > >> > > >> The patches for 4344 were applied in reverse on this branch and, with > > >> the last cherry-pick, the bindings/CMakeLists.txt broke the CMake > > >> changes. The conditional check for Swig < 1.3.32 is still in the file > > >> and needs to be deleted to fix CMake. > > >> > > >> This is totally my fault. > > >> > > >> -- > > >> Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. > > >> Delivering value year after year. > > >> Red Hat ranks #1 in value among software vendors. > > >> http://www.redhat.com/promo/vendor/ > > >> > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > > For additional commands, e-mail: dev-h...@qpid.apache.org > > > > > > -- > -K > > - > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > For additional commands, e-mail: dev-h...@qpid.apache.org > >
Re: Proton-based AMQP 1.0 JMS client
+1 for a different JIRA system. I believe that is the only way we can support an independent release cycle. Rajith On Thu, May 23, 2013 at 2:36 PM, Rob Godfrey wrote: > On 23 May 2013 20:24, Justin Ross wrote: > > > This is great news! > > > > On Thu, May 23, 2013 at 11:07 AM, Robbie Gemmell > > wrote: > > > Hi all, > > [snip] > > > In keeping with prior discussion of making the project structure more > > > component-based, a couple of things we would like to do: > > > > > > - Create an area in svn, located alongside the proton directory, e.g: > > > http://svn.apache.org/repos/asf/qpid/jms > > > > Perfect, IMO. > > > > > - Request creation of a JIRA project, e.g QPIDJMS, inititally for use > > > relating to the new client but perhaps eventually serving for all QPID > > JMS > > > related components. > > > > Out of curiosity, why do you suggest a distinct jira instance (versus > > using a jira component)? I don't have a strong preference either way. > > > > So for me there's a couple of reasons. Most importantly the existing JIRA > system is full of JIRAs for the existing client(s) which will make it very > difficult to distinguish JIRAs for the new component from JIRAs relating to > the older client libraries. Within the context of a "QPID" JIRA system > trying define components for "JMS client for AMQP 0-8/9/10", "JMS client > for AMQP 1-0 not build on proton", and "JMS AMQP 1-0 client based on > proton" such that people don't get confused may be difficult. Secondly > we'll definitely be using a different release schedule / version numbering > from the existing components. Once we sort out the components better I'd > be fine with moving the older clients into the QPIDJMS jira/directory and > we can tailor the component names to reduce any likelihood of confusion. > > -- Rob > > > > > > Justin > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > > For additional commands, e-mail: dev-h...@qpid.apache.org > > > > >
Re: [VOTE] Release 0.22
Justin, A new RC, you say? Well, I'll just leave this little tidbit here, ya know, just in case: https://issues.apache.org/jira/browse/QPID-4883 /backs slowly away from my keyboard - Original Message - > From: "Justin Ross" > To: dev@qpid.apache.org > Sent: Thursday, May 23, 2013 10:34:58 AM > Subject: Re: [VOTE] Release 0.22 > > This vote is withdrawn. We'll have a new RC later today. The only > new change will be the cmake build fix. Once that's available, I'll > start a new vote thread. > > Justin > > On Wed, May 22, 2013 at 5:14 PM, Justin Ross wrote: > > Okay, we'll fix it tomorrow. > > > > On May 22, 2013 4:09 PM, "Darryl L. Pierce" wrote: > >> > >> On Wed, May 22, 2013 at 01:54:50PM -0400, Justin Ross wrote: > >> > RC5 contains the proposed final bits for Qpid 0.22. > >> > > >> > If you favor making the RC5 bits into our official release, vote +1. > >> > If you have reason to believe RC5 is not ready for release, vote -1. > >> > > >> > I will close this vote on Monday, 22 May. I know that's a little > >> > brief, but I have some vacation time coming up soon, and I'm hoping to > >> > finish the release before I leave. > >> > >> The patches for 4344 were applied in reverse on this branch and, with > >> the last cherry-pick, the bindings/CMakeLists.txt broke the CMake > >> changes. The conditional check for Swig < 1.3.32 is still in the file > >> and needs to be deleted to fix CMake. > >> > >> This is totally my fault. > >> > >> -- > >> Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. > >> Delivering value year after year. > >> Red Hat ranks #1 in value among software vendors. > >> http://www.redhat.com/promo/vendor/ > >> > > > > - > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > For additional commands, e-mail: dev-h...@qpid.apache.org > > -- -K - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-4881) New --config-property argument cannot be used with qpid-server.bat (windows)
[ https://issues.apache.org/jira/browse/QPID-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-4881: Assignee: Alex Rudyy > New --config-property argument cannot be used with qpid-server.bat (windows) > > > Key: QPID-4881 > URL: https://issues.apache.org/jira/browse/QPID-4881 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.22, 0.23 >Reporter: Keith Wall >Assignee: Alex Rudyy >Priority: Minor > Attachments: broket-batch-script-fixes.diff > > > Trying to use a command such using the new argument fails in the following > manner. > Y:\src\qpid\qpid\java\build>.\bin\qpid-server.bat --initial-config-path > Y:\ha_test\config.json --config-property nodenum=5 > Warning: Qpid classpath not set. CLASSPATH set to > Y:\src\qpid\qpid\java\build\li > b\qpid-all.jar;Y:\src\qpid\qpid\java\build\lib\plugins\*;Y:\src\qpid\qpid\java\build\lib\opt\* > Info: QPID_JAVA_GC not set. Defaulting to JAVA_GC -XX:+UseConcMarkSweepGC > -XX:+HeapDumpOnOutOfMemoryError > Info: QPID_JAVA_MEM not set. Defaulting to JAVA_MEM -Xmx1024m > Exception during startup: java.lang.IllegalArgumentException: Configuration > property argument is not of the format name=value: nodenum > java.lang.IllegalArgumentException: Configuration property argument is not of > the format name=value: nodenum > at org.apache.qpid.server.Main.execute(Main.java:226) > at org.apache.qpid.server.Main.(Main.java:134) > at org.apache.qpid.server.Main.main(Main.java:125) > Y:\src\qpid\qpid\java\build> > It appears to be related to the processing of the argument list by the > qpid-server.bat file. It is choking on arguments containing =. > User can workaround by providing the property values as system properties > (e.g via QPID_OPTS: set QPID_OPTS="-Dname=value"), or by invoking the Main > class directly without the qpid-server.bat script. -- 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-4881) New --config-property argument cannot be used with qpid-server.bat (windows)
[ https://issues.apache.org/jira/browse/QPID-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665704#comment-13665704 ] Alex Rudyy commented on QPID-4881: -- Committed a fix allowing to pass quoted command line arguments in order to pass equal characters as part of arguments: http://svn.apache.org/r1485859 > New --config-property argument cannot be used with qpid-server.bat (windows) > > > Key: QPID-4881 > URL: https://issues.apache.org/jira/browse/QPID-4881 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.22, 0.23 >Reporter: Keith Wall >Priority: Minor > Attachments: broket-batch-script-fixes.diff > > > Trying to use a command such using the new argument fails in the following > manner. > Y:\src\qpid\qpid\java\build>.\bin\qpid-server.bat --initial-config-path > Y:\ha_test\config.json --config-property nodenum=5 > Warning: Qpid classpath not set. CLASSPATH set to > Y:\src\qpid\qpid\java\build\li > b\qpid-all.jar;Y:\src\qpid\qpid\java\build\lib\plugins\*;Y:\src\qpid\qpid\java\build\lib\opt\* > Info: QPID_JAVA_GC not set. Defaulting to JAVA_GC -XX:+UseConcMarkSweepGC > -XX:+HeapDumpOnOutOfMemoryError > Info: QPID_JAVA_MEM not set. Defaulting to JAVA_MEM -Xmx1024m > Exception during startup: java.lang.IllegalArgumentException: Configuration > property argument is not of the format name=value: nodenum > java.lang.IllegalArgumentException: Configuration property argument is not of > the format name=value: nodenum > at org.apache.qpid.server.Main.execute(Main.java:226) > at org.apache.qpid.server.Main.(Main.java:134) > at org.apache.qpid.server.Main.main(Main.java:125) > Y:\src\qpid\qpid\java\build> > It appears to be related to the processing of the argument list by the > qpid-server.bat file. It is choking on arguments containing =. > User can workaround by providing the property values as system properties > (e.g via QPID_OPTS: set QPID_OPTS="-Dname=value"), or by invoking the Main > class directly without the qpid-server.bat script. -- 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-4883) C++ Broker may crash if client provides SSL certificate without CommonName entry.
[ https://issues.apache.org/jira/browse/QPID-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved QPID-4883. -- Resolution: Fixed Fix: http://svn.apache.org/viewvc?view=revision&revision=1485860 > C++ Broker may crash if client provides SSL certificate without CommonName > entry. > - > > Key: QPID-4883 > URL: https://issues.apache.org/jira/browse/QPID-4883 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.23 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Blocker > Fix For: 0.23 > > > Broker does not check for a null pointer return value from the Certificate > parsing routines. -- 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-4883) C++ Broker may crash if client provides SSL certificate without CommonName entry.
[ https://issues.apache.org/jira/browse/QPID-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665694#comment-13665694 ] Ken Giusti commented on QPID-4883: -- For testing purposes, I created such a certificate using the following commands: + certutil -R -d /home/kgiusti/work/qpid/build/trunk/TMP/server_db -s O=MyCo,ST=California,C=US -o client.req -f /home/kgiusti/work/qpid/build/trunk/TMP/cert.password -z /bin/sh Generating key. This may take a few moments... + certutil -C -d /home/kgiusti/work/qpid/build/trunk/TMP/CA_db -c Test-CA -i client.req -o client.crt -f /home/kgiusti/work/qpid/build/trunk/TMP/cert.password -m 13949 + certutil -A -d /home/kgiusti/work/qpid/build/trunk/TMP/server_db -n Test-Client -i client.crt -t Pu,, + pk12util -o client_pk12.out -d /home/kgiusti/work/qpid/build/trunk/TMP/server_db -n Test-Client -v -w /home/kgiusti/work/qpid/build/trunk/TMP/cert.password -k /home/kgiusti/work/qpid/build/trunk/TMP/cert.password pk12util: PKCS12 EXPORT SUCCESSFUL + openssl pkcs12 -in ./client_pk12.out -out client_cert_key.pem -passin file:/home/kgiusti/work/qpid/build/trunk/TMP/cert.password MAC verified OK Note the "-s" parameter to the first command gives a subject field that does not contain a CN= entry. > C++ Broker may crash if client provides SSL certificate without CommonName > entry. > - > > Key: QPID-4883 > URL: https://issues.apache.org/jira/browse/QPID-4883 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.23 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Blocker > Fix For: 0.23 > > > Broker does not check for a null pointer return value from the Certificate > parsing routines. -- 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-4883) C++ Broker may crash if client provides SSL certificate without CommonName entry.
[ https://issues.apache.org/jira/browse/QPID-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665685#comment-13665685 ] Ken Giusti commented on QPID-4883: -- Reviewboard entry that contains a proposed patch: https://reviews.apache.org/r/11354/ > C++ Broker may crash if client provides SSL certificate without CommonName > entry. > - > > Key: QPID-4883 > URL: https://issues.apache.org/jira/browse/QPID-4883 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.23 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Blocker > Fix For: 0.23 > > > Broker does not check for a null pointer return value from the Certificate > parsing routines. -- 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: Review Request: Check for null pointer returned from SSL certificate parsing function.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/11354/#review20953
---
Ship it!
Ship It!
- Gordon Sim
On May 23, 2013, 9:24 p.m., Kenneth Giusti wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/11354/
> ---
>
> (Updated May 23, 2013, 9:24 p.m.)
>
>
> Review request for qpid and Gordon Sim.
>
>
> Description
> ---
>
> When a client provides an identifying certificate that does not contain a
> CommonName entry in the subject, the CERT_GetCommonName() method returns a
> NULL pointer.
>
> This fix checks for that null pointer, and returns an empty ("") client auth
> id in that case. From a security/functionality point of view, I think
> setting the auth-id to an empty string when CN is not present can be
> considered valid.
>
>
> This addresses bug qpid-4883.
> https://issues.apache.org/jira/browse/qpid-4883
>
>
> Diffs
> -
>
> /trunk/qpid/cpp/src/qpid/sys/ssl/SslSocket.cpp 1485741
>
> Diff: https://reviews.apache.org/r/11354/diff/
>
>
> Testing
> ---
>
> crash reproducer + unit tests.
>
>
> Thanks,
>
> Kenneth Giusti
>
>
Review Request: Check for null pointer returned from SSL certificate parsing function.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/11354/
---
Review request for qpid and Gordon Sim.
Description
---
When a client provides an identifying certificate that does not contain a
CommonName entry in the subject, the CERT_GetCommonName() method returns a NULL
pointer.
This fix checks for that null pointer, and returns an empty ("") client auth id
in that case. From a security/functionality point of view, I think setting
the auth-id to an empty string when CN is not present can be considered valid.
This addresses bug qpid-4883.
https://issues.apache.org/jira/browse/qpid-4883
Diffs
-
/trunk/qpid/cpp/src/qpid/sys/ssl/SslSocket.cpp 1485741
Diff: https://reviews.apache.org/r/11354/diff/
Testing
---
crash reproducer + unit tests.
Thanks,
Kenneth Giusti
[jira] [Created] (QPID-4883) C++ Broker may crash if client provides SSL certificate without CommonName entry.
Ken Giusti created QPID-4883: Summary: C++ Broker may crash if client provides SSL certificate without CommonName entry. Key: QPID-4883 URL: https://issues.apache.org/jira/browse/QPID-4883 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.23 Reporter: Ken Giusti Assignee: Ken Giusti Priority: Blocker Fix For: 0.23 Broker does not check for a null pointer return value from the Certificate parsing routines. -- 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-4826) Fix memory leak in Perl bindings when building with Swig < 1.3.32
[ https://issues.apache.org/jira/browse/QPID-4826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665546#comment-13665546 ] Jimmy Jones commented on QPID-4826: --- Doesn't QPID-4417 still stand which requires SWIG 1.3.32+? While it may not leak memory it corrupts messages containing \0. > Fix memory leak in Perl bindings when building with Swig < 1.3.32 > - > > Key: QPID-4826 > URL: https://issues.apache.org/jira/browse/QPID-4826 > Project: Qpid > Issue Type: Bug > Components: Perl Client >Affects Versions: 0.18 >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > Fix For: Future > > > There is a memory leak that occurs when building the Perl language bindings > generated with version of Swig earlier than 1.3.32. -- 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-4719) Problem building perl bindings from qpid 0.22 RC1 tarball
[ https://issues.apache.org/jira/browse/QPID-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Jones resolved QPID-4719. --- Resolution: Fixed > Problem building perl bindings from qpid 0.22 RC1 tarball > - > > Key: QPID-4719 > URL: https://issues.apache.org/jira/browse/QPID-4719 > Project: Qpid > Issue Type: Bug > Components: Perl Client >Affects Versions: 0.22 >Reporter: Jimmy Jones >Assignee: Darryl L. Pierce > Fix For: 0.22 > > > Tarball > http://people.apache.org/~jross/qpid-0.22-rc1/qpid-cpp-0.22-rc1.tar.gz is > missing: > bindings/qpid/perl/Makefile.PL > bindings/qpid/perl/Makefile.PL.in > bindings/qpid/perl/qpid.pm > bindings/qpid/perl/lib > which prevents the perl bindings from being built from this tarball. I > presume perl-qpid-0.22-rc1.tar.gz is the new home for the perl bindings, but > this doesn't build either: > Running perl Makefile.PL from perl-qpid-0.22-rc1.tar.gz, after installing > qpid-cpp-0.22-rc1.tar.gz (with automake): > Note (probably harmless): No library found for -lqpidmessaging > Note (probably harmless): No library found for -lqpidtypes > Writing Makefile for cqpid_perl > Weird... libqpidmessaging/types seems to be in /usr/lib rather than lib64 on > my 64-bit system, and its linked against other libs in lib64. > Anyway, if then run make: > cp lib/qpid/messaging/Address.pm blib/lib/qpid/messaging/Address.pm > cp lib/qpid/messaging/Duration.pm blib/lib/qpid/messaging/Duration.pm > cp qpid.pm blib/lib/qpid.pm > cp lib/qpid/messaging/codec.pm blib/lib/qpid/messaging/codec.pm > cp lib/qpid/messaging/Message.pm blib/lib/qpid/messaging/Message.pm > cp lib/qpid/messaging/Connection.pm blib/lib/qpid/messaging/Connection.pm > cp lib/qpid/messaging/Sender.pm blib/lib/qpid/messaging/Sender.pm > cp lib/qpid_messaging.pm blib/lib/qpid_messaging.pm > cp lib/qpid/messaging/Receiver.pm blib/lib/qpid/messaging/Receiver.pm > cp lib/qpid/messaging/Session.pm blib/lib/qpid/messaging/Session.pm > Running Mkbootstrap for cqpid_perl () > chmod 644 cqpid_perl.bs > rm -f blib/arch/auto/cqpid_perl/cqpid_perl.so > gcc -shared -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions > -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic cqpid_perl.o > -o blib/arch/auto/cqpid_perl/cqpid_perl.so \ > \ > gcc: cqpid_perl.o: No such file or directory > gcc: no input files > make: *** [blib/arch/auto/cqpid_perl/cqpid_perl.so] Error 1 -- 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-4650) C++ Broker could use a rebind strategy to steer messages from one queue to other queue(s)
[ https://issues.apache.org/jira/browse/QPID-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke resolved QPID-4650. --- Resolution: Fixed Fix Version/s: 0.23 Fixed at Committed revision 1485836. > C++ Broker could use a rebind strategy to steer messages from one queue to > other queue(s) > - > > Key: QPID-4650 > URL: https://issues.apache.org/jira/browse/QPID-4650 > Project: Qpid > Issue Type: Improvement > Components: C++ Broker >Affects Versions: 0.20 >Reporter: Chuck Rolke >Assignee: Chuck Rolke > Fix For: 0.23 > > Attachments: SlowConsumerRebind_v0.3.pdf, > SlowConsumerRedirect_v1.0.pdf > > > Use case: > A C++ broker is providing a service to many customers. In some cases the > broker is delivering high volumes of near real-time traffic to many clients. > Occasionally a client stops accepting traffic and his delivery queue backs > up. This puts the broker into a low memory situation and all users are > affected. > Solution: > The organization that owns the broker could provide an "overflow backup > service" that does several things: > 1. Provides a local-to-the-broker, high-horsepower backup engine that sits > waiting for consumers' queues to fill up. > 2. When a consumer queue fills to some threshhold value then the backup > engine inserts itself in the consumer's data path with a "rebind" command. > 3. The consumer's traffic is now directed to a queue dedicated to the backup > engine. The backup engine buffers the consumer data and plays it back into > the original consumer queue as space becomes available. > This feature could be approximated with no support from inside the broker but > it could not be done without dropping or duplicating messages during the > rebinding phase. > With internal broker support the rebind operation could be cleanly executed > and the producers and consumers would be unaware of any backup engine > activity. > A detailed use case is available in attached SlowConsumerRebind_v0.3.pdf -- 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: Proton-based AMQP 1.0 JMS client
On 23 May 2013 20:24, Justin Ross wrote: > This is great news! > > On Thu, May 23, 2013 at 11:07 AM, Robbie Gemmell > wrote: > > Hi all, > [snip] > > In keeping with prior discussion of making the project structure more > > component-based, a couple of things we would like to do: > > > > - Create an area in svn, located alongside the proton directory, e.g: > > http://svn.apache.org/repos/asf/qpid/jms > > Perfect, IMO. > > > - Request creation of a JIRA project, e.g QPIDJMS, inititally for use > > relating to the new client but perhaps eventually serving for all QPID > JMS > > related components. > > Out of curiosity, why do you suggest a distinct jira instance (versus > using a jira component)? I don't have a strong preference either way. > So for me there's a couple of reasons. Most importantly the existing JIRA system is full of JIRAs for the existing client(s) which will make it very difficult to distinguish JIRAs for the new component from JIRAs relating to the older client libraries. Within the context of a "QPID" JIRA system trying define components for "JMS client for AMQP 0-8/9/10", "JMS client for AMQP 1-0 not build on proton", and "JMS AMQP 1-0 client based on proton" such that people don't get confused may be difficult. Secondly we'll definitely be using a different release schedule / version numbering from the existing components. Once we sort out the components better I'd be fine with moving the older clients into the QPIDJMS jira/directory and we can tailor the component names to reduce any likelihood of confusion. -- Rob > > Justin > > - > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > For additional commands, e-mail: dev-h...@qpid.apache.org > >
Re: Proton-based AMQP 1.0 JMS client
This is great news! On Thu, May 23, 2013 at 11:07 AM, Robbie Gemmell wrote: > Hi all, [snip] > In keeping with prior discussion of making the project structure more > component-based, a couple of things we would like to do: > > - Create an area in svn, located alongside the proton directory, e.g: > http://svn.apache.org/repos/asf/qpid/jms Perfect, IMO. > - Request creation of a JIRA project, e.g QPIDJMS, inititally for use > relating to the new client but perhaps eventually serving for all QPID JMS > related components. Out of curiosity, why do you suggest a distinct jira instance (versus using a jira component)? I don't have a strong preference either way. Justin - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Error- while Building with qpid
--Kim van der Riet Sorry for the delay. I fixed that one. Missing some header files. Thank you for your immediate response :) -- View this message in context: http://qpid.2158936.n2.nabble.com/Error-while-Building-with-qpid-tp7590349p7593221.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4881) New --config-property argument cannot be used with qpid-server.bat (windows)
[ https://issues.apache.org/jira/browse/QPID-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4881: - Attachment: broket-batch-script-fixes.diff Attached a diff fixing the issue > New --config-property argument cannot be used with qpid-server.bat (windows) > > > Key: QPID-4881 > URL: https://issues.apache.org/jira/browse/QPID-4881 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.22, 0.23 >Reporter: Keith Wall >Priority: Minor > Attachments: broket-batch-script-fixes.diff > > > Trying to use a command such using the new argument fails in the following > manner. > Y:\src\qpid\qpid\java\build>.\bin\qpid-server.bat --initial-config-path > Y:\ha_test\config.json --config-property nodenum=5 > Warning: Qpid classpath not set. CLASSPATH set to > Y:\src\qpid\qpid\java\build\li > b\qpid-all.jar;Y:\src\qpid\qpid\java\build\lib\plugins\*;Y:\src\qpid\qpid\java\build\lib\opt\* > Info: QPID_JAVA_GC not set. Defaulting to JAVA_GC -XX:+UseConcMarkSweepGC > -XX:+HeapDumpOnOutOfMemoryError > Info: QPID_JAVA_MEM not set. Defaulting to JAVA_MEM -Xmx1024m > Exception during startup: java.lang.IllegalArgumentException: Configuration > property argument is not of the format name=value: nodenum > java.lang.IllegalArgumentException: Configuration property argument is not of > the format name=value: nodenum > at org.apache.qpid.server.Main.execute(Main.java:226) > at org.apache.qpid.server.Main.(Main.java:134) > at org.apache.qpid.server.Main.main(Main.java:125) > Y:\src\qpid\qpid\java\build> > It appears to be related to the processing of the argument list by the > qpid-server.bat file. It is choking on arguments containing =. > User can workaround by providing the property values as system properties > (e.g via QPID_OPTS: set QPID_OPTS="-Dname=value"), or by invoking the Main > class directly without the qpid-server.bat script. -- 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-4881) New --config-property argument cannot be used with qpid-server.bat (windows)
[ https://issues.apache.org/jira/browse/QPID-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4881: - Description: Trying to use a command such using the new argument fails in the following manner. Y:\src\qpid\qpid\java\build>.\bin\qpid-server.bat --initial-config-path Y:\ha_test\config.json --config-property nodenum=5 Warning: Qpid classpath not set. CLASSPATH set to Y:\src\qpid\qpid\java\build\li b\qpid-all.jar;Y:\src\qpid\qpid\java\build\lib\plugins\*;Y:\src\qpid\qpid\java\build\lib\opt\* Info: QPID_JAVA_GC not set. Defaulting to JAVA_GC -XX:+UseConcMarkSweepGC -XX:+HeapDumpOnOutOfMemoryError Info: QPID_JAVA_MEM not set. Defaulting to JAVA_MEM -Xmx1024m Exception during startup: java.lang.IllegalArgumentException: Configuration property argument is not of the format name=value: nodenum java.lang.IllegalArgumentException: Configuration property argument is not of the format name=value: nodenum at org.apache.qpid.server.Main.execute(Main.java:226) at org.apache.qpid.server.Main.(Main.java:134) at org.apache.qpid.server.Main.main(Main.java:125) Y:\src\qpid\qpid\java\build> It appears to be related to the processing of the argument list by the qpid-server.bat file. It is choking on arguments containing =. User can workaround by providing the property values as system properties (e.g via QPID_OPTS: set QPID_OPTS="-Dname=value"), or by invoking the Main class directly without the qpid-server.bat script. was: Trying to use a command such using the new argument fails in the following manner. Y:\src\qpid\qpid\java\build>.\bin\qpid-server.bat --initial-config-path Y:\ha_test\config.json --config-property nodenum=5 Warning: Qpid classpath not set. CLASSPATH set to Y:\src\qpid\qpid\java\build\li b\qpid-all.jar;Y:\src\qpid\qpid\java\build\lib\plugins\*;Y:\src\qpid\qpid\java\build\lib\opt\* Info: QPID_JAVA_GC not set. Defaulting to JAVA_GC -XX:+UseConcMarkSweepGC -XX:+HeapDumpOnOutOfMemoryError Info: QPID_JAVA_MEM not set. Defaulting to JAVA_MEM -Xmx1024m Exception during startup: java.lang.IllegalArgumentException: Configuration property argument is not of the format name=value: nodenum java.lang.IllegalArgumentException: Configuration property argument is not of the format name=value: nodenum at org.apache.qpid.server.Main.execute(Main.java:226) at org.apache.qpid.server.Main.(Main.java:134) at org.apache.qpid.server.Main.main(Main.java:125) Y:\src\qpid\qpid\java\build> It appears to be related to the processing of the argument list by the qpid-server.bat file. It is choking on arguments containing =. User could workaround by invoking the Main class directly. > New --config-property argument cannot be used with qpid-server.bat (windows) > > > Key: QPID-4881 > URL: https://issues.apache.org/jira/browse/QPID-4881 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.22, 0.23 >Reporter: Keith Wall >Priority: Minor > > Trying to use a command such using the new argument fails in the following > manner. > Y:\src\qpid\qpid\java\build>.\bin\qpid-server.bat --initial-config-path > Y:\ha_test\config.json --config-property nodenum=5 > Warning: Qpid classpath not set. CLASSPATH set to > Y:\src\qpid\qpid\java\build\li > b\qpid-all.jar;Y:\src\qpid\qpid\java\build\lib\plugins\*;Y:\src\qpid\qpid\java\build\lib\opt\* > Info: QPID_JAVA_GC not set. Defaulting to JAVA_GC -XX:+UseConcMarkSweepGC > -XX:+HeapDumpOnOutOfMemoryError > Info: QPID_JAVA_MEM not set. Defaulting to JAVA_MEM -Xmx1024m > Exception during startup: java.lang.IllegalArgumentException: Configuration > property argument is not of the format name=value: nodenum > java.lang.IllegalArgumentException: Configuration property argument is not of > the format name=value: nodenum > at org.apache.qpid.server.Main.execute(Main.java:226) > at org.apache.qpid.server.Main.(Main.java:134) > at org.apache.qpid.server.Main.main(Main.java:125) > Y:\src\qpid\qpid\java\build> > It appears to be related to the processing of the argument list by the > qpid-server.bat file. It is choking on arguments containing =. > User can workaround by providing the property values as system properties > (e.g via QPID_OPTS: set QPID_OPTS="-Dname=value"), or by invoking the Main > class directly without the qpid-server.bat script. -- 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
[jira] [Updated] (QPID-4348) HA Use independent sequence numbers for identifying messages.
[ https://issues.apache.org/jira/browse/QPID-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated QPID-4348: -- Description: Currently HA code uses queue sequence numbers to identify messasges. This assumes that message sequence is identical on primary and backup. Implementing new features (for example transactions) requires that we tolerate ordering differences between primary and backups. We introduces a new, queue-scoped HA sequence number managed by the HA plugin. This is used to identify messages independently of queue sequence numbers. Needs careful implementation to avoid bad performance effects. - Avoid adding headers, use the same mechansim as we have now for sending HA seq. nos. - Use an efficient index struct (e.g. dequeue) to map HA seq. to queue seq. The benefits: - required to support TX - required for re-use of stored messages for catchup - more robust - aovidb was: Currently HA code uses queue sequence numbers to identify messasges. This assumes that message sequence is identical on primary and backup. Implementing new features (for example transactions) requires that we tolerate ordering differences between primary and backups. We introduces a new, queue-scoped HA sequence number managed by the HA plugin. This is used to identify messages independently of queue sequence numbers. Needs careful implementation to avoid bad performance effects. - Avoid adding headers, use the same mechansim as we have now for sending HA seq. nos. - Use an efficient index struct (e.g. dequeue) to map HA seq. to queue seq. The benefits: - required to support TX - required for re-use of stored messages for catchup - more robust - aovids implicit assumption of synchronization > HA Use independent sequence numbers for identifying messages. > - > > Key: QPID-4348 > URL: https://issues.apache.org/jira/browse/QPID-4348 > Project: Qpid > Issue Type: Improvement > Components: C++ Clustering >Affects Versions: 0.18 >Reporter: Alan Conway >Assignee: Alan Conway > > Currently HA code uses queue sequence numbers to identify messasges. > This assumes that message sequence is identical on primary and backup. > Implementing new features (for example transactions) requires that we tolerate > ordering differences between primary and backups. > We introduces a new, queue-scoped HA sequence number managed by the HA plugin. > This is used to identify messages independently of queue sequence numbers. > Needs careful implementation to avoid bad performance effects. > - Avoid adding headers, use the same mechansim as we have now for sending HA > seq. nos. > - Use an efficient index struct (e.g. dequeue) to map HA seq. to queue seq. > The benefits: > - required to support TX > - required for re-use of stored messages for catchup > - more robust - aovidb -- 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
Proton-based AMQP 1.0 JMS client
Hi all, As most of you will be aware, we currently have a JMS client that supports AMQP 0-8 / 0-9 / 0-9-1 / 0-10 and a separate JMS client supporting AMQP 1.0, the latter of which was partly the result of prototyping work relating to implementing AMQP 1.0. Since then Proton has been created, in part to offer a means for ourselves and others integrate AMQP 1.0 into products. We are already using Proton-c as basis for the AMQP 1.0 support for the C++ client and broker, but are not as yet using Proton-J within a Qpid client or broker (though it is being used by the ActiveMQ project). The time has come where we would like to begin working on a Proton-based JMS[2.0] client. I have recently spent some time with Rob Godfrey working through how we could approach this, putting together a very simple client proof of concept using Proton-J. We are now reaching the point where we would like to actually set up some infrastructure for use going forward, e.g an area to commit code etc and an issue tracker to raise items. In keeping with prior discussion of making the project structure more component-based, a couple of things we would like to do: - Create an area in svn, located alongside the proton directory, e.g: http://svn.apache.org/repos/asf/qpid/jms - Request creation of a JIRA project, e.g QPIDJMS, inititally for use relating to the new client but perhaps eventually serving for all QPID JMS related components. The latter one will require a vote for infra, which I will look to start in the near future. Regards, Robbie
[jira] [Resolved] (QPID-4879) Merged patch removed endif(), breaking CMake build on 0.22
[ https://issues.apache.org/jira/browse/QPID-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce resolved QPID-4879. Resolution: Fixed Fix Version/s: 0.22 > Merged patch removed endif(), breaking CMake build on 0.22 > -- > > Key: QPID-4879 > URL: https://issues.apache.org/jira/browse/QPID-4879 > Project: Qpid > Issue Type: Bug > Components: Build Tools >Affects Versions: 0.22 >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce >Priority: Blocker > Fix For: 0.22 > > Attachments: > 0001-QPID-4879-Re-add-line-accidentally-removed-from-merg.patch > > > QPID-4344 patches were applied out of order and caused a conditional to be > added to the bindings Cmake file. This didn't show up until the last patch > pulled in removed the end() directive for it. -- 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-4882) Syntax (NameError) thrown by python client when using older versions of python (<2.6)
[
https://issues.apache.org/jira/browse/QPID-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved QPID-4882.
--
Resolution: Fixed
Fixed:
http://svn.apache.org/viewvc?view=revision&revision=1485741
> Syntax (NameError) thrown by python client when using older versions of
> python (<2.6)
> -
>
> Key: QPID-4882
> URL: https://issues.apache.org/jira/browse/QPID-4882
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
>Affects Versions: 0.20
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Trivial
> Fix For: 0.23
>
>
> Bug discovered by Petr Matousek.
> Attempting to validate the broker using the 'ssl_trustfile' parameter results
> in the following crash:
> # ~/qc2_drain.py -b amqps://$(hostname):5671 "amq.direct/test"
> --connection-options "{ssl_certfile:/var/lib/qpidd/qpid_nss_db/client.pem,
> ssl_trustfile:/var/lib/qpidd/qpid_nss_db/rootca.crt}"
> Traceback (most recent call last):
> File "/root/qc2_drain.py", line 171, in ?
> conn.open()
> File "", line 6, in open
> File "/usr/lib/python2.4/site-packages/qpid/messaging/endpoints.py", line
> 261, in open
> self.attach()
> File "", line 6, in attach
> File "/usr/lib/python2.4/site-packages/qpid/messaging/endpoints.py", line
> 279, in attach
> self._ewait(lambda: self._transport_connected and not self._unlinked())
> File "/usr/lib/python2.4/site-packages/qpid/messaging/endpoints.py", line
> 214, in _ewait
> self.check_error()
> File "/usr/lib/python2.4/site-packages/qpid/messaging/endpoints.py", line
> 207, in check_error
> raise self.error
> qpid.messaging.exceptions.InternalError: Traceback (most recent call last):
> File "/usr/lib/python2.4/site-packages/qpid/messaging/driver.py", line 509,
> in dispatch
> self.connect()
> File "/usr/lib/python2.4/site-packages/qpid/messaging/driver.py", line 533,
> in connect
> self._transport = trans(self.connection, host, port)
> File "/usr/lib/python2.4/site-packages/qpid/messaging/transports.py", line
> 79, in __init__
> raise SSLError("This version of Python does not support verification of
> the peer's certificate.")
> NameError: global name 'SSLError' is not defined
> This is due to the fact that older python releases do not define the SSLError
> exception.
--
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-4882) Syntax (NameError) thrown by python client when using older versions of python (<2.6)
Ken Giusti created QPID-4882:
Summary: Syntax (NameError) thrown by python client when using
older versions of python (<2.6)
Key: QPID-4882
URL: https://issues.apache.org/jira/browse/QPID-4882
Project: Qpid
Issue Type: Bug
Components: Python Client
Affects Versions: 0.20
Reporter: Ken Giusti
Assignee: Ken Giusti
Priority: Trivial
Fix For: 0.23
Bug discovered by Petr Matousek.
Attempting to validate the broker using the 'ssl_trustfile' parameter results
in the following crash:
# ~/qc2_drain.py -b amqps://$(hostname):5671 "amq.direct/test"
--connection-options "{ssl_certfile:/var/lib/qpidd/qpid_nss_db/client.pem,
ssl_trustfile:/var/lib/qpidd/qpid_nss_db/rootca.crt}"
Traceback (most recent call last):
File "/root/qc2_drain.py", line 171, in ?
conn.open()
File "", line 6, in open
File "/usr/lib/python2.4/site-packages/qpid/messaging/endpoints.py", line
261, in open
self.attach()
File "", line 6, in attach
File "/usr/lib/python2.4/site-packages/qpid/messaging/endpoints.py", line
279, in attach
self._ewait(lambda: self._transport_connected and not self._unlinked())
File "/usr/lib/python2.4/site-packages/qpid/messaging/endpoints.py", line
214, in _ewait
self.check_error()
File "/usr/lib/python2.4/site-packages/qpid/messaging/endpoints.py", line
207, in check_error
raise self.error
qpid.messaging.exceptions.InternalError: Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/qpid/messaging/driver.py", line 509,
in dispatch
self.connect()
File "/usr/lib/python2.4/site-packages/qpid/messaging/driver.py", line 533,
in connect
self._transport = trans(self.connection, host, port)
File "/usr/lib/python2.4/site-packages/qpid/messaging/transports.py", line
79, in __init__
raise SSLError("This version of Python does not support verification of the
peer's certificate.")
NameError: global name 'SSLError' is not defined
This is due to the fact that older python releases do not define the SSLError
exception.
--
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: [VOTE] Release 0.22
This vote is withdrawn. We'll have a new RC later today. The only new change will be the cmake build fix. Once that's available, I'll start a new vote thread. Justin On Wed, May 22, 2013 at 5:14 PM, Justin Ross wrote: > Okay, we'll fix it tomorrow. > > On May 22, 2013 4:09 PM, "Darryl L. Pierce" wrote: >> >> On Wed, May 22, 2013 at 01:54:50PM -0400, Justin Ross wrote: >> > RC5 contains the proposed final bits for Qpid 0.22. >> > >> > If you favor making the RC5 bits into our official release, vote +1. >> > If you have reason to believe RC5 is not ready for release, vote -1. >> > >> > I will close this vote on Monday, 22 May. I know that's a little >> > brief, but I have some vacation time coming up soon, and I'm hoping to >> > finish the release before I leave. >> >> The patches for 4344 were applied in reverse on this branch and, with >> the last cherry-pick, the bindings/CMakeLists.txt broke the CMake >> changes. The conditional check for Swig < 1.3.32 is still in the file >> and needs to be deleted to fix CMake. >> >> This is totally my fault. >> >> -- >> Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. >> Delivering value year after year. >> Red Hat ranks #1 in value among software vendors. >> http://www.redhat.com/promo/vendor/ >> > - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4879) Patches applied out of order breaks CMake
[ https://issues.apache.org/jira/browse/QPID-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce updated QPID-4879: --- Affects Version/s: 0.22 > Patches applied out of order breaks CMake > - > > Key: QPID-4879 > URL: https://issues.apache.org/jira/browse/QPID-4879 > Project: Qpid > Issue Type: Bug > Components: Build Tools >Affects Versions: 0.22 >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce >Priority: Blocker > Attachments: > 0001-QPID-4879-Re-add-line-accidentally-removed-from-merg.patch > > > QPID-4344 patches were applied out of order and caused a conditional to be > added to the bindings Cmake file. This didn't show up until the last patch > pulled in removed the end() directive for it. -- 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-4879) Merged patch removed endif(), breaking CMake build on 0.22
[ https://issues.apache.org/jira/browse/QPID-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce updated QPID-4879: --- Summary: Merged patch removed endif(), breaking CMake build on 0.22 (was: Patches applied out of order breaks CMake) > Merged patch removed endif(), breaking CMake build on 0.22 > -- > > Key: QPID-4879 > URL: https://issues.apache.org/jira/browse/QPID-4879 > Project: Qpid > Issue Type: Bug > Components: Build Tools >Affects Versions: 0.22 >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce >Priority: Blocker > Attachments: > 0001-QPID-4879-Re-add-line-accidentally-removed-from-merg.patch > > > QPID-4344 patches were applied out of order and caused a conditional to be > added to the bindings Cmake file. This didn't show up until the last patch > pulled in removed the end() directive for it. -- 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-4879) Patches applied out of order breaks CMake
[ https://issues.apache.org/jira/browse/QPID-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce updated QPID-4879: --- Attachment: 0001-QPID-4879-Re-add-line-accidentally-removed-from-merg.patch The problem was caused by the deletion of an endif() statement in the bindings directory. This patch re-adds that line, undoing the deletion. > Patches applied out of order breaks CMake > - > > Key: QPID-4879 > URL: https://issues.apache.org/jira/browse/QPID-4879 > Project: Qpid > Issue Type: Bug > Components: Build Tools >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce >Priority: Blocker > Attachments: > 0001-QPID-4879-Re-add-line-accidentally-removed-from-merg.patch > > > QPID-4344 patches were applied out of order and caused a conditional to be > added to the bindings Cmake file. This didn't show up until the last patch > pulled in removed the end() directive for it. -- 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-4879) Patches applied out of order breaks CMake
[ https://issues.apache.org/jira/browse/QPID-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce updated QPID-4879: --- Attachment: (was: 0001-QPID-4879-Remove-the-swig-minimum-version-check.patch) > Patches applied out of order breaks CMake > - > > Key: QPID-4879 > URL: https://issues.apache.org/jira/browse/QPID-4879 > Project: Qpid > Issue Type: Bug > Components: Build Tools >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce >Priority: Blocker > > QPID-4344 patches were applied out of order and caused a conditional to be > added to the bindings Cmake file. This didn't show up until the last patch > pulled in removed the end() directive for it. -- 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] [Issue Comment Deleted] (QPID-4879) Patches applied out of order breaks CMake
[ https://issues.apache.org/jira/browse/QPID-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce updated QPID-4879: --- Comment: was deleted (was: The attached patch fixes the issue on the 0.22 branch.) > Patches applied out of order breaks CMake > - > > Key: QPID-4879 > URL: https://issues.apache.org/jira/browse/QPID-4879 > Project: Qpid > Issue Type: Bug > Components: Build Tools >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce >Priority: Blocker > > QPID-4344 patches were applied out of order and caused a conditional to be > added to the bindings Cmake file. This didn't show up until the last patch > pulled in removed the end() directive for it. -- 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-4881) New --config-property argument cannot be used with qpid-server.bat (windows)
Keith Wall created QPID-4881: Summary: New --config-property argument cannot be used with qpid-server.bat (windows) Key: QPID-4881 URL: https://issues.apache.org/jira/browse/QPID-4881 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.22, 0.23 Reporter: Keith Wall Priority: Minor Trying to use a command such using the new argument fails in the following manner. Y:\src\qpid\qpid\java\build>.\bin\qpid-server.bat --initial-config-path Y:\ha_test\config.json --config-property nodenum=5 Warning: Qpid classpath not set. CLASSPATH set to Y:\src\qpid\qpid\java\build\li b\qpid-all.jar;Y:\src\qpid\qpid\java\build\lib\plugins\*;Y:\src\qpid\qpid\java\build\lib\opt\* Info: QPID_JAVA_GC not set. Defaulting to JAVA_GC -XX:+UseConcMarkSweepGC -XX:+HeapDumpOnOutOfMemoryError Info: QPID_JAVA_MEM not set. Defaulting to JAVA_MEM -Xmx1024m Exception during startup: java.lang.IllegalArgumentException: Configuration property argument is not of the format name=value: nodenum java.lang.IllegalArgumentException: Configuration property argument is not of the format name=value: nodenum at org.apache.qpid.server.Main.execute(Main.java:226) at org.apache.qpid.server.Main.(Main.java:134) at org.apache.qpid.server.Main.main(Main.java:125) Y:\src\qpid\qpid\java\build> It appears to be related to the processing of the argument list by the qpid-server.bat file. It is choking on arguments containing =. User could workaround by invoking the Main class directly. -- 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
libqpidcommon.so.6 crashes while loading
We developed a program using qpid. It runs on a development machine but crashes on the target while loading libqpidcommon.so.6. Looks like it tries to create a string which is large then existing memory. I compared environment on both machines and could not see any difference. Here what we have on the target: uname -a Linux lnxe40747 2.6.32-220.el6.x86_64 #1 SMP Wed Nov 9 08:03:13 EST 2011 x86_64 x86_64 x86_64 GNU/Linux $ free -m total used free sharedbuffers cached Mem: 5851 1145 4706 0 17740 -/+ buffers/cache:387 5464 Swap: 2047 0 2047 ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 46662 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 10240 cpu time (seconds, -t) unlimited max user processes (-u) 1024 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited rpm -qa |grep qpid qpid-cpp-client-0.14-16.el6.x86_64 The gdb bt: (gdb) BT #0 0x003498832885 in raise () from /lib64/libc.so.6 #1 0x003498834065 in abort () from /lib64/libc.so.6 #2 0x00349bcbea7d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6 #3 0x00349bcbcc06 in ?? () from /usr/lib64/libstdc++.so.6 #4 0x00349bcbcc33 in std::terminate() () from /usr/lib64/libstdc++.so.6 #5 0x00349bcbcd2e in __cxa_throw () from /usr/lib64/libstdc++.so.6 #6 0x00349bcbd11d in operator new(unsigned long) () from /usr/lib64/libstdc++.so.6 #7 0x00349bc9c3c9 in std::basic_string, std::allocator >::_Rep::_S_create(unsigned long, unsigned long, std::allocator const&) () from /usr/lib64/libstdc++.so.6 #8 0x00349bc9ddaa in std::basic_string, std::allocator >::_M_mutate(unsigned long, unsigned long, unsigned long) () from /usr/lib64/libstdc++.so.6 #9 0x7fdd8b059f7d in qpid::log::Options::Options(std::basic_string, std::allocator > const&, std::basic_string, std::allocator > const&) () from /usr/lib64/libqpidcommon.so.6 #10 0x7fdd8b057a86 in qpid::log::Logger::Logger() () from /usr/lib64/libqpidcommon.so.6 #11 0x7fdd8b058413 in ?? () from /usr/lib64/libqpidcommon.so.6 #12 0x7fdd8b079416 in ?? () from /usr/lib64/libqpidcommon.so.6 #13 0x001d in ?? () #14 0x0001 in ?? () #15 0x7fff10351fc8 in ?? () #16 0x7fdd8af88713 in _init () from /usr/lib64/libqpidcommon.so.6 #17 0x7fdd8c21a4c8 in ?? () #18 0x00349800e4a5 in _dl_init_internal () from /lib64/ld-linux-x86-64.so.2 #19 0x003498000b3a in _dl_start_user () from /lib64/ld-linux-x86-64.so.2 #20 0x0001 in ?? () #21 0x7fff1035368b in ?? () #22 0x in ?? () and valgrind output: ==1643== Memcheck, a memory error detector ==1643== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==1643== Using Valgrind-3.6.0 and LibVEX; rerun with -h for copyright info ==1643== Command: ./PTC_PRO_MSG ==1643== **1643** new/new[] failed and should throw an exception, but Valgrind **1643**cannot throw exceptions and so is aborting instead. Sorry. ==1643==at 0x4A063B3: VALGRIND_PRINTF_BACKTRACE (valgrind.h:5028) ==1643==by 0x4A06CF6: operator new(unsigned long) (vg_replace_malloc.c:261) ==1643==by 0x349BC9C3C8: std::string::_Rep::_S_create(unsigned long, unsigned long, std::allocator const&) (in /usr/lib64/libstdc++.so.6.0.13) ==1643==by 0x349BC9D19A: std::string::_Rep::_M_clone(std::allocator const&, unsigned long) (in /usr/lib64/libstdc++.so.6.0.13) ==1643==by 0x349BC9D5EB: std::string::reserve(unsigned long) (in /usr/lib64/libstdc++.so.6.0.13) ==1643==by 0x349BC978F0: std::basic_stringbuf, std::allocator >::overflow(int) (in /usr/lib64/libstdc++.so.6.0.13) ==1643==by 0x349BC9BAB4: std::basic_streambuf >::xsputn(char const*, long) (in /usr/lib64/libstdc++.so.6.0.13) ==1643==by 0x349BC92934: std::basic_ostream >& std::__ostream_insert >(std::basic_ostream >&, char const*, long) (in /usr/lib64/libstdc++.so.6.0.13) ==1643==by 0x6E97F0A: qpid::log::Options::Options(std::string const&, std::string const&) (in /usr/lib64/libqpidcommon.so.6.0.0) ==1643==by 0x6E95A85: qpid::log::Logger::Logger() (in /usr/lib64/libqpidcommon.so.6.0.0) ==1643==by 0x6E96412: ??? (in /usr/lib64/libqpidcommon.so.6.0.0) ==1643==by 0x6EB7415: ??? (in /usr/lib64/libqpidcommon.so.6.0.0) ==1643== ==1643== HEAP SUMMARY: ==1643== in use at exit: 12,911 bytes in 209 blocks ==1643== total heap usage: 607 allocs, 397 frees, 30,102 bytes allocated ==16
[jira] [Resolved] (QPID-4880) [AMQP 1.0] allow temp queues to be qualified by brokers domain
[ https://issues.apache.org/jira/browse/QPID-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-4880. -- Resolution: Fixed Fixed by http://svn.apache.org/viewvc?view=revision&revision=1485658 > [AMQP 1.0] allow temp queues to be qualified by brokers domain > -- > > Key: QPID-4880 > URL: https://issues.apache.org/jira/browse/QPID-4880 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.23 >Reporter: Gordon Sim >Assignee: Gordon Sim > Fix For: 0.23 > > > i.e. when creating a temp queue, which with 1,0 has a broker assigned name, > have the broker qualify the local name with its configured domain to assist > in routing in a federation. -- 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-4880) [AMQP 1.0] allow temp queues to be qualified by brokers domain
Gordon Sim created QPID-4880: Summary: [AMQP 1.0] allow temp queues to be qualified by brokers domain Key: QPID-4880 URL: https://issues.apache.org/jira/browse/QPID-4880 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.23 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.23 i.e. when creating a temp queue, which with 1,0 has a broker assigned name, have the broker qualify the local name with its configured domain to assist in routing in a federation. -- 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
