[jira] [Created] (QPID-3331) 0.12 release tasks
0.12 release tasks -- Key: QPID-3331 URL: https://issues.apache.org/jira/browse/QPID-3331 Project: Qpid Issue Type: Task Components: Packaging Affects Versions: 0.11 Reporter: Justin Ross - Branching for release (http://svn.apache.org/viewvc?rev=1141543view=rev) - Updating version numbers -- 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] [Closed] (QPID-3334) Missing file causes distcheck failure
[ https://issues.apache.org/jira/browse/QPID-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-3334. - Resolution: Fixed Missing file causes distcheck failure - Key: QPID-3334 URL: https://issues.apache.org/jira/browse/QPID-3334 Project: Qpid Issue Type: Bug Components: Packaging Affects Versions: 0.12 Reporter: Justin Ross Assignee: Justin Ross Priority: Blocker Fix For: 0.12 The C++ broker's distribution is missing a file reference. -- 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-3353) Windows-specific file is missing from 0.12 beta cpp source kit
[ https://issues.apache.org/jira/browse/QPID-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13063965#comment-13063965 ] Justin Ross commented on QPID-3353: --- Approved for 0.12. Windows-specific file is missing from 0.12 beta cpp source kit -- Key: QPID-3353 URL: https://issues.apache.org/jira/browse/QPID-3353 Project: Qpid Issue Type: Bug Components: Packaging Affects Versions: 0.11 Environment: Windows Reporter: Chuck Rolke Fix For: 0.12 Changes made in QPID-2905 http://svn.apache.org/viewvc?rev=1104662view=rev add a file that is not packaged in the source kit. Checkin 1143995 http://svn.apache.org/viewvc?view=revisionrevision=1143995 adds the file by name to Makefile.am so that it is packaged in the cpp source kit. -- 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-3338) qpidxarm CMake target is missing in 0-12
[ https://issues.apache.org/jira/browse/QPID-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13064031#comment-13064031 ] Justin Ross commented on QPID-3338: --- Reviewed by Chuck Rolke on the dev list. Approved for 0.12. qpidxarm CMake target is missing in 0-12 Key: QPID-3338 URL: https://issues.apache.org/jira/browse/QPID-3338 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.12 Environment: Windows with Microsoft compilers (as opposed to mingw) Reporter: Cliff Jansen Assignee: Cliff Jansen Priority: Blocker Fix For: 0.12 Attachments: jira-3338.patch cpp/src/CMakeLists.txt was altered for mingw builds in QPID-2905 (r1104662). The qpidxarm target builds the XA distributed transaction resource manager for use with the Microsoft distributed trasanction coordinator. It was targeted for Windows builds only, using the CMake variable WIN32. This variable was changed to _MSC_VER for QPID-2905, presumably to indicate that the build target should only apply to builds using the Microsoft compiler, and not mingw. Unfortunately _MSC_VER is not a recognized CMAKE variable and the qpidxarm target is never generated. The CMake documentation indicates the the variable MSVC should be used to indicate The Microsoft compiler compared to mingw. -- 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-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 updated QPID-3354: -- Fix Version/s: (was: 0.10) 0.13 0.12 Assignee: Justin Ross 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.12, 0.13 The current build instructions assume older versions of Fedora for build C++. INSTALL file states: INSTALL 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. New INSTALL instructions 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] [Commented] (QPID-3256) Application which uses Qpid (in my case Excel) hangs on shutdown
[
https://issues.apache.org/jira/browse/QPID-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13069008#comment-13069008
]
Justin Ross commented on QPID-3256:
---
Cliff, I'd like to produce RC2 today, and if we want to go ahead with this
patch, I'd like to get it in RC2 (RC3 would be too late). How does that strike
you?
Application which uses Qpid (in my case Excel) hangs on shutdown
Key: QPID-3256
URL: https://issues.apache.org/jira/browse/QPID-3256
Project: Qpid
Issue Type: Bug
Components: C++ Client
Affects Versions: 0.8, 0.10
Environment: OS: Windows.
Qpid is assembled as DLL.
Reporter: Eugene
Assignee: Cliff Jansen
Fix For: 0.13
Attachments: qpid-3256-3.patch, qpid-3256.patch
Hi All
I encountered with strange behavior on shutdown when using qpid 0-8 and 0-10.
When I use qpid in standalone console-application everything is ok. But when
I use qpid in DLL which is loaded into Excel (as RTD module), Excel hangs on
shutdown.
I found out that in standalone application on shutdown I have next stack:
qpidclientd.dll!qpid::client::`anonymous
namespace'::IOThread::~IOThread() Line 138C++
qpidclientd.dll!`qpid::client::`anonymous
namespace'::theIO'::`2'::`dynamic atexit destructor for 'io''() + 0xd bytes
C++
qpidclientd.dll!_CRT_INIT(void * hDllHandle=0x6008, unsigned long
dwReason=0, void * lpreserved=0x0001) Line 449 C
qpidclientd.dll!__DllMainCRTStartup(void * hDllHandle=0x6008,
unsigned long dwReason=0, void * lpreserved=0x0001) Line 560 + 0x11
bytesC
qpidclientd.dll!_DllMainCRTStartup(void * hDllHandle=0x6008,
unsigned long dwReason=0, void * lpreserved=0x0001) Line 510 + 0x11
bytes C
ntdll.dll!77b79960()
[Frames below may be incorrect and/or missing, no symbols loaded for
ntdll.dll]
ntdll.dll!77b9a516()
ntdll.dll!77b9a3b8()
kernel32.dll!77657363()
msvcr90d.dll!__crtExitProcess(int status=0) Line 732 C
msvcr90d.dll!doexit(int code=0, int quick=0, int retcaller=0) Line 644
+ 0x9 bytes C
msvcr90d.dll!exit(int code=0) Line 412 + 0xd bytes C
Test.exe!__tmainCRTStartup() Line 599 C
Test.exe!mainCRTStartup() Line 403 C
kernel32.dll!77653677()
ntdll.dll!77b79f02()
ntdll.dll!77b79ed5()
And in this state all threads of application have been already terminated.
The only thread is:
121720 Main Thread Main Thread
qpid::client::`anonymous namespace'::IOThread::~IOThreadNormal 0
so code from file ConnectionImpl.cpp works well:
~IOThread() {
std::vectorThread threads;
{
ScopedLockMutex l(threadLock);
if (poller_)
poller_-shutdown();
t.swap(threads);
}
for (std::vectorThread::iterator i = threads.begin(); i !=
threads.end(); ++i) {
i-join();
}
}
BUT in Excel I get stack:
qpidclientd.dll!qpid::client::`anonymous namespace'::IOThread::~IOThread()
Line 130 C++
qpidclientd.dll!`qpid::client::`anonymous
namespace'::theIO'::`2'::`dynamic atexit destructor for 'io''() + 0xd bytes
C++
qpidclientd.dll!_CRT_INIT(void * hDllHandle=0x0770, unsigned long
dwReason=0, void * lpreserved=0x) Line 449 C
qpidclientd.dll!__DllMainCRTStartup(void * hDllHandle=0x0770,
unsigned long dwReason=0, void * lpreserved=0x) Line 560 + 0x11
bytesC
qpidclientd.dll!_DllMainCRTStartup(void * hDllHandle=0x0770,
unsigned long dwReason=0, void * lpreserved=0x) Line 510 + 0x11
bytes C
ntdll.dll!77b79960()
[Frames below may be incorrect and/or missing, no symbols loaded for
ntdll.dll]
ntdll.dll!77ba1525()
ntdll.dll!77b81231()
KernelBase.dll!77281da7()
ole32.dll!75bb9562()
ole32.dll!75bb9593()
ole32.dll!75bb95a7()
ole32.dll!75bb98bf()
ole32.dll!75bb9805()
ole32.dll!75bb9a8c()
EXCEL.EXE!2f3811e9()
EXCEL.EXE!2f6933e8()
EXCEL.EXE!2f32a5af()
EXCEL.EXE!2f34894a()
EXCEL.EXE!2f670001()
MSO.DLL!65bc6ed5()
MSO.DLL!65c26a34()
MSO.DLL!65c30305()
MSO.DLL!65bc910c()
MSO.DLL!65c4f420()
MSO.DLL!65bbf161()
comctl32.dll!7233463d()
user32.dll!762971be()
user32.dll!76297d31()
user32.dll!76297dfa()
EXCEL.EXE!2f324572()
EXCEL.EXE!2f324534()
EXCEL.EXE!2f324441()
[jira] [Resolved] (QPID-3353) Windows-specific file is missing from 0.12 beta cpp source kit
[ https://issues.apache.org/jira/browse/QPID-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-3353. --- Resolution: Fixed Assignee: Chuck Rolke Windows-specific file is missing from 0.12 beta cpp source kit -- Key: QPID-3353 URL: https://issues.apache.org/jira/browse/QPID-3353 Project: Qpid Issue Type: Bug Components: Packaging Affects Versions: 0.11 Environment: Windows Reporter: Chuck Rolke Assignee: Chuck Rolke Fix For: 0.12 Changes made in QPID-2905 http://svn.apache.org/viewvc?rev=1104662view=rev add a file that is not packaged in the source kit. Checkin 1143995 http://svn.apache.org/viewvc?view=revisionrevision=1143995 adds the file by name to Makefile.am so that it is packaged in the cpp source kit. -- 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-3394) Broker leaks messages that require async completion.
[ https://issues.apache.org/jira/browse/QPID-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3394: -- Affects Version/s: (was: 0.11) 0.13 Fix Version/s: 0.13 Broker leaks messages that require async completion. -- Key: QPID-3394 URL: https://issues.apache.org/jira/browse/QPID-3394 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.12, 0.13 Reporter: Ken Giusti Assignee: Ken Giusti Priority: Blocker Fix For: 0.12, 0.13 Attachments: membloat.patch The fix for QPID-3252 introduced a bug where messages that require async completion (ie. durable, or flow controlled) are incorrectly stored by the broker until the sender sends an explicit flush. This can cause a excessive amount of memory to be consumed by the broker. -- 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-3394) Broker leaks messages that require async completion.
[ https://issues.apache.org/jira/browse/QPID-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3394: -- Fix Version/s: 0.12 Reviewed by Gordon Sim. Approved for inclusion in 0.12. Broker leaks messages that require async completion. -- Key: QPID-3394 URL: https://issues.apache.org/jira/browse/QPID-3394 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.12, 0.13 Reporter: Ken Giusti Assignee: Ken Giusti Priority: Blocker Fix For: 0.12, 0.13 Attachments: membloat.patch The fix for QPID-3252 introduced a bug where messages that require async completion (ie. durable, or flow controlled) are incorrectly stored by the broker until the sender sends an explicit flush. This can cause a excessive amount of memory to be consumed by the broker. -- 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-2057) qpidd --require-encryption forces SASL security layer to be used even if SSL is in use
[ https://issues.apache.org/jira/browse/QPID-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2057: -- Fix Version/s: (was: 0.11) Future qpidd --require-encryption forces SASL security layer to be used even if SSL is in use -- Key: QPID-2057 URL: https://issues.apache.org/jira/browse/QPID-2057 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Reporter: Ted Ross Assignee: michael j. goulish Priority: Minor Fix For: Future If running SSL and using GSSAPI authentication with the --require-encryption option turned on, the SASL layer will force minSsf to be greater than zero, thus causing the SASL security layer to encrypt. This is unnecessary double-encryption since SSL is already providing a cipher channel at a lower layer. -- 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-2316) 0.6RC2 C++ Build fails if ruby-dev and swig installed
[ https://issues.apache.org/jira/browse/QPID-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13083552#comment-13083552 ] Justin Ross commented on QPID-2316: --- Can we declare this issue resolved? 0.6RC2 C++ Build fails if ruby-dev and swig installed - Key: QPID-2316 URL: https://issues.apache.org/jira/browse/QPID-2316 Project: Qpid Issue Type: Bug Components: Build Tools Affects Versions: 0.6, 0.7 Reporter: Rob Godfrey Assignee: Ted Ross Fix For: 0.11 When attempting to build the C++ contained in the artefact at http://qpid.apache.org/dist/qpid-0.6rc2/qpid-0.6rc2.tar.gz I got the following error on my machine: Making all in ruby make[2]: Entering directory `/home/rob/qpidc-0.6/bindings/qmf/ruby' make[2]: *** No rule to make target `ruby.i', needed by `qmfengine.cpp'. Stop. Further investigation showed that the build succeeded on a separate machine, however on this machine the qmfengine.cpp target was commented out in the buildfile. This was as a result of the fact that the second machine did not have ruby development and SWIG packages installed. After installing these packages the second machine failed in the same way as the first -- 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-2993) Federated source-local links crash remotely federated cluster member on local cluster startup
[ https://issues.apache.org/jira/browse/QPID-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2993: -- Fix Version/s: (was: 0.11) Future Federated source-local links crash remotely federated cluster member on local cluster startup - Key: QPID-2993 URL: https://issues.apache.org/jira/browse/QPID-2993 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Clustering Affects Versions: 0.8 Environment: Debian Linux Squeeze, 32-bit, kernel 2.6.36.2, Dell Poweredge 1950s. Corosync==1.3.0, Openais==1.1.4 Reporter: Mark Moseley Assignee: michael j. goulish Fix For: Future Attachments: 2993_bug.sh, cluster-fed-src.sh This is related to JIRA 2992 that I opened, but this is for source-local routes. Given the same setup as in JIRA 2992 but using source-local routes (and obviously with the exchanges switched accordingly in the qpid-route statements), i.e. cluster A and cluster B with the routes between A1-B1, when cluster B shuts down in the order B2-B1 and starts back up, the static routes are not correctly re-bound on cluster A's side. However if cluster B is shut down in the order B1-B2 and started back up, the route is correctly created and works. However in the non-functioning case (B2-B1, or A2-A1), there is an additional side-effect: on node A2, qpidd crashes with the following error (cluster A is called 'walclust', B is bosclust): 2011-01-07 18:57:35 error Channel exception: not-attached: Channel 1 is not attached (qpid/amqp_0_10/SessionHandler.cpp:39) 2011-01-07 18:57:35 critical cluster(102.0.0.0:13650 READY/error) local error 2030 did not occur on member 101.0.0.0:9920: not-attached: Channel 1 is not attached (qpid/amqp_0_10/SessionHandler.cpp:39) 2011-01-07 18:57:35 critical Error delivering frames: local error did not occur on all cluster members : not-attached: Channel 1 is not attached (qpid/amqp_0_10/SessionHandler.cpp:39) (qpid/cluster/ErrorCheck.cpp:89) 2011-01-07 18:57:35 notice cluster(102.0.0.0:13650 LEFT/error) leaving cluster walclust 2011-01-07 18:57:35 notice Shut down This happens on both sides of the cluster, so it's not limited to one or the other. This crash does *not* occur in the A1-A2/B1-B2 test (i.e. the test where the route is re-bound correctly). I can cause this to reoccur pretty much every time. I've been resetting the cluster completely to a new state between each test. Occasionally in the B2-B1 test, A1 will also crash with the same error (and vice versa for A2-A1 for node B1), though most of the time, it's A2/B2 that crashes. I was getting this same behaviour prior to upgrading corosync/openais as well. Previously I was using the stock Squeeze versions of corosync==1.2.1 and openais==1.1.2. The results are the same with corosync=1.3.0 and openais==1.1.4. -- 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-3061) Discrepancies between CMake and Automake
[ https://issues.apache.org/jira/browse/QPID-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3061: -- Fix Version/s: (was: 0.11) Future Discrepancies between CMake and Automake Key: QPID-3061 URL: https://issues.apache.org/jira/browse/QPID-3061 Project: Qpid Issue Type: Bug Components: Build Tools Affects Versions: 0.8 Reporter: Ted Ross Assignee: Ted Ross Priority: Minor Fix For: Future There are some changes that were put into Autoconf/Automake but not Cmake. This issue is for tracking the synchronization of cmake to automake. -- 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-3066) UTF8Test does not run under non VM 0-10 profiles
[ https://issues.apache.org/jira/browse/QPID-3066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13083559#comment-13083559 ] Justin Ross commented on QPID-3066: --- This looks like it may be resolved. True? UTF8Test does not run under non VM 0-10 profiles Key: QPID-3066 URL: https://issues.apache.org/jira/browse/QPID-3066 Project: Qpid Issue Type: Bug Components: Java Tests Affects Versions: 0.9 Reporter: Andrew Kennedy Assignee: Andrew Kennedy Priority: Minor Fix For: 0.11 The UTF8Test uses the 'isBrokerExternal' and 'isBroker010' methods to check whether it should run, rather than relying on the Excludes files. The checks wrongly cause an exception to be thrown on the java.0.10 test profile. -- 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-3111) DynamicQueueExchangeCreateTest should check for 404 error code explicitly
[ https://issues.apache.org/jira/browse/QPID-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13083673#comment-13083673 ] Justin Ross commented on QPID-3111: --- Is this issue fixed? DynamicQueueExchangeCreateTest should check for 404 error code explicitly - Key: QPID-3111 URL: https://issues.apache.org/jira/browse/QPID-3111 Project: Qpid Issue Type: Bug Components: Java Tests Affects Versions: 0.9 Reporter: Andrew Kennedy Assignee: Andrew Kennedy Priority: Minor Fix For: 0.11 DynamicQueueExchangeCreateTest checks for a tect string in the message property of a thrown exception. This is brittle and should be replaced with a check for the AMQConstant#NOT_FOUND (404) error code instead. -- 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: INSTALL 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. New INSTALL instructions 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] [Updated] (QPID-3966) Add missing license headers to project files
[ https://issues.apache.org/jira/browse/QPID-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3966: -- Attachment: 0.16rc2_rat_output.txt Add missing license headers to project files Key: QPID-3966 URL: https://issues.apache.org/jira/browse/QPID-3966 Project: Qpid Issue Type: Improvement Components: Packaging Affects Versions: 0.16 Reporter: Justin Ross Assignee: Justin Ross Fix For: 0.17 Attachments: 0.16rc2_rat_output.txt To make it easier to audit the project for license headers, add at least minimal license headers to many of the project files. See attachment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-3984) HA tests fail in distribution
[ https://issues.apache.org/jira/browse/QPID-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13271720#comment-13271720 ] Justin Ross commented on QPID-3984: --- Reviewed by me. Approved for 0.16. HA tests fail in distribution - Key: QPID-3984 URL: https://issues.apache.org/jira/browse/QPID-3984 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.15 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.16 The HA tests fail on an installed qpid distribution because they rely on scripts in the qpid/tools directory. This patch runs the tests conditionally, skipping them if the tools aren't available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-3902) Add formal message categories to C++ Broker log messages
[
https://issues.apache.org/jira/browse/QPID-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13293021#comment-13293021
]
Justin Ross commented on QPID-3902:
---
I have a slight preference for Network over IO and Protocol over Amqp.
The former because it's slightly more descriptive, and the latter because it
identifies a general role as the other categories do.
Add formal message categories to C++ Broker log messages
Key: QPID-3902
URL: https://issues.apache.org/jira/browse/QPID-3902
Project: Qpid
Issue Type: Improvement
Reporter: Chuck Rolke
Attachments: qpid-log-src-tabbed2.txt
h3. This is a proposal to add log categories to C++ Broker log messages.
h4. Problem Statement
There are difficulties working with C++ Broker logging when appplying a log
filter criterion. What precise FILTERTEXT can a user specify for:
{noformat}
--log-enable debug+:FILTERTEXT
{noformat}
Even after the fix from QPID-3891 it is not intuitive what to specify for a
FILTERTEXT and any useful filter requires detailed knowledge of the source
code.
h4. Proposal
A log category is a high-level classification of the nature of the logged
event that is not tied to a particular source module or code function name.
This log category would become the target for FILTERTEXT log filters.
The following list is the proposed log category definition. Each log category
name is followed by a list of source code directory names that would
generally produce logs using that log category.
||Category||Source code directory||
|Security|acl ssl gssapi sasl cyrus|
|Broker | broker|
|Management| agent console qmf|
|Amqp|amqp_0_10 framing|
|System| log sys types xml thread mutex fork pipe time ...|
|HA| cluster ha replication|
|Messaging| messaging client|
|Store| store|
|IO| tcp rdma AsynchIO socket epoll|
|Test| |
|Unspecified| |
There is no strict rule that a module produce only log entries of a specific
category.
The category would be inserted into each log message after the time of day
but before the message text.
{noformat}
2012-03-06 16:55:38 [Management] SEND PackageInd
package=org.apache.qpid.broker to=schema.package
{noformat}
A user could then filter log messages by using the category names:
{noformat}
--log-enable debug+:Management
{noformat}
This scheme would have a number of benefits:
1. On a per-message basis the filter comparisons would be using enumeration
values and not strings.
2. The feature could be documented sensibly.
3. Log files would be easier to interpret manually or by event management
systems.
The classifications could be phased in gradually. The current
QPID_LOG(LEVEL, MESSAGE) would produce [Unspecfied] events while the new
QPID_LOG_CAT(LEVEL, CATEGORY, MESSAGE) would produce events using an actual
category.
Similar additions are made for the QPID_MSG entries.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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-4111) 0.18 release tasks
Justin Ross created QPID-4111: - Summary: 0.18 release tasks Key: QPID-4111 URL: https://issues.apache.org/jira/browse/QPID-4111 Project: Qpid Issue Type: Task Components: Packaging Affects Versions: 0.17 Reporter: Justin Ross Assignee: Justin Ross A bug to track various release tasks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4126) HA primary times out expected backups.
[ https://issues.apache.org/jira/browse/QPID-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411926#comment-13411926 ] Justin Ross commented on QPID-4126: --- Reviewed by Gordon. Approved for 0.18. HA primary times out expected backups. -- Key: QPID-4126 URL: https://issues.apache.org/jira/browse/QPID-4126 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.17 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.18 After a failure, the newly-promoted primary broker guards messages for each of the backups that were connected at the time of the failure. It waits for them to reconnect to the new primary before becoming active. This patch introduces a time-out so that if an expected backup fails to fail-over within the time limit, the primary will cancel the guards for that backup and carry on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4128) HA should not use amq.failover for replication links
[ https://issues.apache.org/jira/browse/QPID-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411953#comment-13411953 ] Justin Ross commented on QPID-4128: --- Reviewed by Gordon. Approved for 0.18. HA should not use amq.failover for replication links Key: QPID-4128 URL: https://issues.apache.org/jira/browse/QPID-4128 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.17 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.18 HA replication links should not use the amq.failover exchange to get updates reconnect targets. amq.failover provides the client failover list, HA manages a separate failover list for brokers. Replication links should be using the broker list, and not allow it to be overwritten by amq.failover updates. Review requested for 0.18, 2 line fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4036) Failed client connections permanently exhaust broker's max connections limit
[
https://issues.apache.org/jira/browse/QPID-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13416523#comment-13416523
]
Justin Ross commented on QPID-4036:
---
Reviewed by Alan. Approved for 0.18. Corresponding commit is
http://svn.apache.org/viewvc?view=revisionrevision=1360214 .
Failed client connections permanently exhaust broker's max connections limit
Key: QPID-4036
URL: https://issues.apache.org/jira/browse/QPID-4036
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.16
Environment: CentOS release 5.5 (Final)
Linux 2.6.18-194.32.1.el5 #1 SMP Wed Jan 5 17:52:25 EST 2011 x86_64 x86_64
x86_64 GNU/Linux
gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-48)
Reporter: Paul Colby
Priority: Critical
Labels: sasl, ssl
I'm running a set of Qpid 0.16 C++ brokers with configuration like:
{code}
cluster-name=mm-queue-cluster
cluster-cman=yes
cluster-mechanism=PLAIN
cluster-username=broker
cluster-password=abc123
cluster-url=ssl:gateway02:5671
auth=yes
ssl-cert-db=/etc/qpid/certs/broker
ssl-cert-password-file=/etc/qpid/certs/pass.txt
ssl-cert-name=broker.messagemedia.com.au
require-encryption=yes
{code}
ie the broker is requiring both encryption and authentication (configured
SASL mech list is CRAM-MD5 DIGEST-MD5 EXTERNAL PLAIN).
Now, if a client (let's use {{qpid-stat}} for example) connects via SSL
(amqps) and authenticates successfully, then everything is happy.
However, if a client repeatedly fails to use SSL and/or fails to provide
credentials, then the broker loses one of it's configured max connections
every time!
So, for example, if we start the broker using the configuration shown above,
then do this:
{code}for i in `seq 1 550`; do echo $i; qpid-stat -q ; done{code}
The above loop will report ~ 500 {{AuthenticationFailure}} errors, then
switch to {{ConnectionError}} errors. Once the {{ConnectionError}} errors
begin, all further connections to the broker will be rejected - permanently
(until the broker is restarted), with the broker logging:
{code}error Client max connection count limit exceeded: 500 connection
refused{code}
From my testing, the following loops never cause an issue (with this
configuration):
{code:none}
for i in `seq 1 550`; do echo $i; qpid-stat -b amqps://guest/guest@localhost
-q ; done # Works as expected.
for i in `seq 1 550`; do echo $i; qpid-stat -b amqps://guest/wrong@localhost
-q ; done # AuthenticationFailure as expected.
{code}
Whereas any of the following will break the broker:
{code:none}
for i in `seq 1 550`; do echo $i; qpid-stat -b amqp://guest/guest@localhost
-q ; done # AuthenticationFailure, then ConnectionError.
for i in `seq 1 550`; do echo $i; qpid-stat -b amqp://guest/wrong@localhost
-q ; done # AuthenticationFailure, then ConnectionError.
for i in `seq 1 550`; do echo $i; qpid-stat -b amqp://localhost -q ; done
# AuthenticationFailure, then ConnectionError.
for i in `seq 1 550`; do echo $i; qpid-stat -b amqps://localhost -q ; done
# AuthenticationFailure, then ConnectionError.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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-4133) Non-responsive peer in federated link can result in entire cluster shutdown
[
https://issues.apache.org/jira/browse/QPID-4133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13416538#comment-13416538
]
Justin Ross commented on QPID-4133:
---
Reviewed by Alan and Gordon. Approved for 0.18.
Non-responsive peer in federated link can result in entire cluster shutdown
---
Key: QPID-4133
URL: https://issues.apache.org/jira/browse/QPID-4133
Project: Qpid
Issue Type: Bug
Components: C++ Clustering
Affects Versions: 0.12
Reporter: Jason Dillaman
Assignee: Alan Conway
Attachments: jira-4133.patch
If a federated link is established to a source broker that is slow to respond
with the AMQP handshake, the destination broker cluster will shutdown with an
Unknown connection error.
Exception constructed: Unknown connection: Frame[BEbe; channel=0;
{ClusterConnectionDeliverDoOutputBody: limit=2048; }] control
2.0.0.0:22138-14 (qpid/cluster/Cluster.cpp:542)
Steps to Reproduce:
1. Configure a clustered broker
2. Start netcat in listen mode (nc -l 6000)
3. Add a route between the clustered broker and nc (qpid-route queue add
localhost:5672 localhost:6000 amq.fanout foo)
4. Clustered broker shuts down
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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-4136) HA sporadic failures in ha_tests
[ https://issues.apache.org/jira/browse/QPID-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13416549#comment-13416549 ] Justin Ross commented on QPID-4136: --- Trivial change, approved for 0.18. HA sporadic failures in ha_tests Key: QPID-4136 URL: https://issues.apache.org/jira/browse/QPID-4136 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.7 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.18 ha_tests.py fails sporadically. 2 different types of failure have been observed: failure 1 ha_tests.RecoveryTests.test_queue_hold fail Error during test: Traceback (most recent call last): File /home/aconway/qpid/dbg/src/tests/python/commands/qpid-python-test, line 340, in run phase() File /home/aconway/qpid/qpid/cpp/src/tests/ha_tests.py, line 901, in test_queue_hold cluster[1].assert_browse_backup(q1, [str(i) for i in range(100)+range(100,200)]) File /home/aconway/qpid/qpid/cpp/src/tests/ha_tests.py, line 158, in assert_browse_backup assert_browse_retry(bs, queue, expected, **kwargs) File /home/aconway/qpid/qpid/cpp/src/tests/brokertest.py, line 466, in assert_browse_retry assert expect_contents == actual_contents, msg AssertionError: browse failed: ['0', '1', '2', '3', '4', '5', '6', '7', '8', '9', '10', '11', '12', '13', '14', '15', '16', '17', '18', '19', '20', '21', '22', '23', '24', '25', '26', '27', '28', '29', '30', '31', '32', '33', '34', '35', '36', '37', '38', '39', '40', '41', '42', '43', '44', '45', '46', '47', '48', '49', '50', '51', '52', '53', '54', '55', '56', '57', '58', '59', '60', '61', '62', '63', '64', '65', '66', '67', '68', '69', '70', '71', '72', '73', '74', '75', '76', '77', '78', '79', '80', '81', '82', '83', '84', '85', '86', '87', '88', '89', '90', '91', '92', '93', '94', '95', '96', '97', '98', '99', '100', '101', '102', '103', '104', '105', '106', '107', '108', '109', '110', '111', '112', '113', '114', '115', '116', '117', '118', '119', '120', '121', '122', '123', '124', '125', '126', '127', '128', '129', '130', '131', '132', '133', '134', '135', '136', '137', '138', '139', '140', '141', '142', '143', '144', '145', '146', '147', '148', '149', '150', '151', '152', '153', '154', '155', '156', '157', '158', '159', '160', '161', '162', '163', '164', '165', '166', '167', '168', '169', '170', '171', '172', '173', '174', '175', '176', '177', '178', '179', '180', '181', '182', '183', '184', '185', '186', '187', '188', '189', '190', '191', '192', '193', '194', '195', '196', '197', '198', '199'] != [] - failure 2 ha_tests.RecoveryTests.test_queue_hold .. fail Error during test: Traceback (most recent call last): File /var/lib/jenkins/workspace/Qpid-cpp/qpid/cpp/src/tests/python/commands/qpid-python-test, line 340, in run phase() File /var/lib/jenkins/workspace/Qpid-cpp/qpid/cpp/src/tests/ha_tests.py, line 891, in test_queue_hold assertSyncTimeout(s1) File /var/lib/jenkins/workspace/Qpid-cpp/qpid/cpp/src/tests/ha_tests.py, line 875, in assertSyncTimeout self.fail(Expected Timeout exception) File /usr/lib64/python2.6/unittest.py, line 316, in fail raise self.failureException, msg AssertionError: Expected Timeout exception -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4121) ConcurrentModificationException reported by HouseKeepingTask while closing session
[
https://issues.apache.org/jira/browse/QPID-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13416695#comment-13416695
]
Justin Ross commented on QPID-4121:
---
Reviewed by Keith. Approved for 0.18.
ConcurrentModificationException reported by HouseKeepingTask while closing
session
--
Key: QPID-4121
URL: https://issues.apache.org/jira/browse/QPID-4121
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: 0.16, 0.17, 0.18
Reporter: Philip Harvey
Assignee: Keith Wall
Fix For: 0.19
Attachments:
0001-QPID-4121-AMQProtocolEngine-now-uses-lock-to-prevent.patch
A ConcurrentModificationException was reported by a housekeeping thread while
closing a session. It was closing the session because its transaction was
open or idle for longer than the configured maximum time.
Here is the log excerpt:
{noformat}
2012-07-02 19:25:12,210 WARN [notifier:VirtualHostHouseKeepingTask]
server.AMQChannel (AMQChannel.java:1519) - IDLE TRANSACTION ALERT
org.apache.qpid.server
.logging.subjects.ChannelLogSubject@4ca3b645 503084 ms
2012-07-02 23:48:41,979 WARN [notifier:VirtualHostHouseKeepingTask]
server.AMQChannel (AMQChannel.java:1519) - IDLE TRANSACTION ALERT
org.apache.qpid.server
.logging.subjects.ChannelLogSubject@3b1d0a16 584211 ms
2012-07-02 23:48:42,033 ERROR [notifier:VirtualHostHouseKeepingTask]
virtualhost.VirtualHostImpl$VirtualHostHouseKeepingTask
(VirtualHostImpl.java:407) - Exception in housekeeping for connection:
/xxx.xxx.xxx.xx:50639(x)
java.util.ConcurrentModificationException
at
java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
at java.util.AbstractList$Itr.next(AbstractList.java:343)
at
org.apache.qpid.server.txn.LocalTransaction.rollback(LocalTransaction.java:297)
at org.apache.qpid.server.AMQChannel.close(AMQChannel.java:535)
at
org.apache.qpid.server.protocol.AMQProtocolEngine.closeChannel(AMQProtocolEngine.java:727)
at
org.apache.qpid.server.protocol.AMQProtocolEngine.closeSession(AMQProtocolEngine.java:1350)
at
org.apache.qpid.server.AMQChannel.checkTransactionStatus(AMQChannel.java:1530)
at
org.apache.qpid.server.virtualhost.VirtualHostImpl$VirtualHostHouseKeepingTask.execute(VirtualHostImpl.java:400)
at
org.apache.qpid.server.virtualhost.HouseKeepingTask.run(HouseKeepingTask.java:61)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101
(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic
(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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-4131) Broker should close connection on transaction timeout rather than close session for better compatibility with Java clients
[ https://issues.apache.org/jira/browse/QPID-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13416699#comment-13416699 ] Justin Ross commented on QPID-4131: --- Reviewed by Philip. Approved for 0.18. Broker should close connection on transaction timeout rather than close session for better compatibility with Java clients -- Key: QPID-4131 URL: https://issues.apache.org/jira/browse/QPID-4131 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.12, 0.14, 0.16, 0.18 Reporter: Keith Wall Assignee: Philip Harvey Fix For: 0.19 Older versions of the Java Broker (0.5) used to close the connection in the event of transaction time (on detection of open or idle transaction) rather than close the session. When the transaction timeout feature was forward ported to 0.11, the decision was made to close the session for both 0-10 and 0-8...0-9-1. Unfortunately the Java client does not handle the session close correctly and this results in a connection leak. This change will revert the 0-8...0-9-1 code paths within the Java Broker to use connection close rather than session close. This will ensure that the Java Broker remains compatibility with Java Clients that suffer this problem.. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4107) HA does not replicate alternate-exchange
[ https://issues.apache.org/jira/browse/QPID-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13416707#comment-13416707 ] Justin Ross commented on QPID-4107: --- This is a defect, but one I'd characterize more as a functionality gap than an ordinary bug. At any rate, I think it's too big a change leading up to RC1, so I think it should wait for the next release. HA does not replicate alternate-exchange Key: QPID-4107 URL: https://issues.apache.org/jira/browse/QPID-4107 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.17 Reporter: Alan Conway Assignee: Alan Conway In a HA cluster, the alternate-exchange setting on queues and exchanges is not replicated. Note that to replicate it, you need to solve the problem of ensuring you have replicated the required exchange before you try to set it on a newly replicated queue (or exchange). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4138) HA sporadic failure in ha_tests
[ https://issues.apache.org/jira/browse/QPID-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13418460#comment-13418460 ] Justin Ross commented on QPID-4138: --- Reviewed by Gordon. Approved for 0.18. HA sporadic failure in ha_tests --- Key: QPID-4138 URL: https://issues.apache.org/jira/browse/QPID-4138 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.17 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.18 Sporadic failure in ha_tests. 2 types of failure observed: failure 1 ha_tests.LongTests.test_failover_send_receive ... start Traceback (most recent call last): File /home/aconway/qpidha/qpid/cpp/src/tests/ha_tests.py, line 884, in test_failover_send_receive brokers[(i+1)%3].wait_status(ready) File /home/aconway/qpidha/qpid/cpp/src/tests/ha_tests.py, line 117, in wait_status assert retry(try_get_status, timeout=20), %s status != %r%(self, status) AssertionError: Broker003:cluster0-0.log qpidd-23 :58163 status != 'ready' ha_tests.LongTests.test_failover_send_receive ... fail Error during test: Traceback (most recent call last): File /home/aconway/qpidha/opt/src/tests/python/commands/qpid-python-test, line 340, in run phase() File /home/aconway/qpidha/qpid/cpp/src/tests/ha_tests.py, line 884, in test_failover_send_receive brokers[(i+1)%3].wait_status(ready) File /home/aconway/qpidha/qpid/cpp/src/tests/ha_tests.py, line 117, in wait_status assert retry(try_get_status, timeout=20), %s status != %r%(self, status) AssertionError: Broker003:cluster0-0.log qpidd-23 :58163 status != 'ready' failure 2 ha_tests.LongTests.test_failover_send_receive start Traceback (most recent call last): File /home/aconway/qpidha/qpid/cpp/src/tests/ha_tests.py, line 884, in test_failover_send_receive brokers[(i+1)%3].wait_status(ready) File /home/aconway/qpidha/qpid/cpp/src/tests/ha_tests.py, line 117, in wait_status assert retry(try_get_status, timeout=20), %s status != %r%(self, status) AssertionError: Broker003:cluster0-0.log qpidd-23 :47682 status != 'ready' ha_tests.LongTests.test_failover_send_receive fail Error during test: Traceback (most recent call last): File /home/aconway/qpidha/opt/src/tests/python/commands/qpid-python-test, line 340, in run phase() File /home/aconway/qpidha/qpid/cpp/src/tests/ha_tests.py, line 884, in test_failover_send_receive brokers[(i+1)%3].wait_status(ready) File /home/aconway/qpidha/qpid/cpp/src/tests/ha_tests.py, line 117, in wait_status assert retry(try_get_status, timeout=20), %s status != %r%(self, status) AssertionError: Broker003:cluster0-0.log qpidd-23 :47682 status != 'ready' failure 3 ha_tests.ReplicationTests.test_send_receive . fail Error during test: Traceback (most recent call last): File /home/aconway/qpidha/opt/src/tests/python/commands/qpid-python-test, line 340, in run phase() File /home/aconway/qpidha/qpid/cpp/src/tests/ha_tests.py, line 382, in test_send_receive brokers[2].assert_browse_backup(q, expect, transform=sn) File /home/aconway/qpidha/qpid/cpp/src/tests/ha_tests.py, line 158, in assert_browse_backup assert_browse_retry(bs, queue, expected, **kwargs) File /home/aconway/qpidha/qpid/cpp/src/tests/brokertest.py, line 466, in assert_browse_retry assert expect_contents == actual_contents, msg AssertionError: browse failed: [991L, 992L, 993L, 994L, 995L, 996L, 997L, 998L, 999L, 1000L] != [990, 991, 992, 993, 994, 995, 996, 997, 998, 999, 1000] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4148) HA Not setting initial queues for new RemoteBackups
[ https://issues.apache.org/jira/browse/QPID-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13418462#comment-13418462 ] Justin Ross commented on QPID-4148: --- Reviewed by Gordon. Approved for 0.18. HA Not setting initial queues for new RemoteBackups --- Key: QPID-4148 URL: https://issues.apache.org/jira/browse/QPID-4148 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.17 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.18 Fix bug introduced by r1362584: QPID-4144 HA broker deadlocks on broker::QueueRegistry lock and ha::Primary lock Stopped setting initial queues on new (i.e. not expected) RemoteBackups. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4144) HA broker deadlocks on broeker::QueueRegistry lock and ha::Primary lock
[ https://issues.apache.org/jira/browse/QPID-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13418461#comment-13418461 ] Justin Ross commented on QPID-4144: --- Reviewed by Gordon. Approved for 0.18. HA broker deadlocks on broeker::QueueRegistry lock and ha::Primary lock --- Key: QPID-4144 URL: https://issues.apache.org/jira/browse/QPID-4144 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.17 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.18 Attachments: thread-dump.txt Running tests repeatedly, the broker deadlocked with the attached stack trace. The problem call sequences are: 1. QueueRegistry::destroy takes QueuerRegistry lock ConfigurationObserver::queueDestroy ha::Primary::queueDestroy takes Primary lock. 2. ConnectionObserver::opened cals Primary::opened lock RemoteBackupgetQueues().eachQueue This patch breaks the deadlock at both ends: QueueRegistry no longer holds the lock across the observer call and Primary does not hold the lock across eachQueue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4156) HA close window for clients to connect before HA broker is initialized
[ https://issues.apache.org/jira/browse/QPID-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419150#comment-13419150 ] Justin Ross commented on QPID-4156: --- Reviewed by Gordon. Approved for 0.18. HA close window for clients to connect before HA broker is initialized -- Key: QPID-4156 URL: https://issues.apache.org/jira/browse/QPID-4156 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.17 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.18 A HA backup broker in a cluster rejects client connections. This was previously done in a ConnectionObserver registered during Plugin::initialize. However that left a window before the observer was registered when clients could connect. This showed up as a sporadic failure of the failover test. This patch moves the creation of the observer to Plugin::earlyInitialize, which is guaranteed to be called before the broker starts listening for clients. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4158) HA transition to CATCHUP status too early.
[ https://issues.apache.org/jira/browse/QPID-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419151#comment-13419151 ] Justin Ross commented on QPID-4158: --- Reviewed by Gordon. Approved for 0.18. HA transition to CATCHUP status too early. -- Key: QPID-4158 URL: https://issues.apache.org/jira/browse/QPID-4158 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.17 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.18 Previously we set status to CATCHUP when the BrokerReplicators bridge was initialized. This is too early, it's possible for an aborted attempt to connect to another backup to get as far as bridge init. This patch waits till we receive the first actual message from the primary before updating status to CATCHUP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4155) qpid-stat fails while trying to display queue names that have non-ascii characters
[ https://issues.apache.org/jira/browse/QPID-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419198#comment-13419198 ] Justin Ross commented on QPID-4155: --- Reviewed by me. Approved for 0.18. qpid-stat fails while trying to display queue names that have non-ascii characters -- Key: QPID-4155 URL: https://issues.apache.org/jira/browse/QPID-4155 Project: Qpid Issue Type: Bug Components: Python Tools Affects Versions: 0.18 Reporter: Ted Ross Assignee: Ted Ross Priority: Minor Fix For: 0.19 If a queue (or exchange) is created with a name that contains non-ascii characters, qpid-stat will error out while attempting to display the list of queues or exchanges. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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] [Assigned] (QPID-3963) A federated broker may not reconnect to a remote cluster on link failure.
[ https://issues.apache.org/jira/browse/QPID-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reassigned QPID-3963: - Assignee: Justin Ross (was: Ken Giusti) A federated broker may not reconnect to a remote cluster on link failure. - Key: QPID-3963 URL: https://issues.apache.org/jira/browse/QPID-3963 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Clustering Affects Versions: 0.14 Reporter: Ken Giusti Assignee: Justin Ross Fix For: 0.17 When a broker is federated with a cluster, the cluster informs the broker of the failover addresses that are valid for the cluster. Should a cluster member fail, the broker will reconnect to another member of that cluster. However, the federated broker only queries the cluster for these failover addresses when it first connects to the cluster. Should the cluster topology change, the federated broker's list of available failover addresses will become out-of-date. This can prevent the broker from correctly re-connecting on failure of a cluster member. Example: Given cluster with members C1 and C2, and a separate broker B, federate B to connect to C1. On connecting to C1, B learns the addresses of C2 as an alternate failover address. Now shutdown C1. B will reconnect to C2, and learn that C2 is the only member of the cluster (ie. no failover addresses). After B connects, restart C1 and let it join the cluster. Then shutdown C2. Since B does not know that C1 has become available again, B will not attempt to re-connect to it. Instead, it tries to reconnect to C2 indefinately. The expected behavior would be to have B reconnect to C1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4163) Deadlock between LinkRegistry and TimerTask locks
[ https://issues.apache.org/jira/browse/QPID-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420769#comment-13420769 ] Justin Ross commented on QPID-4163: --- Reviewed by Gordon and Andrew. Approved for 0.18. Deadlock between LinkRegistry and TimerTask locks - Key: QPID-4163 URL: https://issues.apache.org/jira/browse/QPID-4163 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.17 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.18 Attachments: ha-timer-hang.pstack Very occasionally (about 2% of runs), when running ha_tests.py in a long loop one of the brokers deadlocks with the attached stack trace. The problem is a call to TimerTask::cancel with the LinkRegsitry lock held, while another thread is in TimerTask::fire and waiting for the LinkRegistry lock. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4159) HA missing messages in failover test.
[ https://issues.apache.org/jira/browse/QPID-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13421333#comment-13421333 ] Justin Ross commented on QPID-4159: --- Reviewed by Gordon. Approved for 0.18. HA missing messages in failover test. - Key: QPID-4159 URL: https://issues.apache.org/jira/browse/QPID-4159 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.17 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.18 Running this test: ha_tests.py *.test_failover_send_receive -DDURATION=2 in a loop eventually fails with something like: AssertionError: test8 missing message 1752917454 The test should run indefinitely with no missing messages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4165) Fix unsused variable warnings when compiling with -DNDEBUG
[ https://issues.apache.org/jira/browse/QPID-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13421700#comment-13421700 ] Justin Ross commented on QPID-4165: --- Reviewed by Darryl. Approved for 0.18. Fix unsused variable warnings when compiling with -DNDEBUG --- Key: QPID-4165 URL: https://issues.apache.org/jira/browse/QPID-4165 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.17 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.18 Attachments: ndebug.diff Trivial fixes, patch attached. request merge to 0.18. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4107) HA does not replicate alternate-exchange
[ https://issues.apache.org/jira/browse/QPID-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13423283#comment-13423283 ] Justin Ross commented on QPID-4107: --- Subsequent discussion with Alan and Gordon has persuaded me to approve this change. It's not a strict bug fix, but without it, some kind of patch is necessary. Given that the change is isolated to the ha component and generally represents a low risk, I approve this for 0.18 (reversing the comment above). Reviewed by Gordon. HA does not replicate alternate-exchange Key: QPID-4107 URL: https://issues.apache.org/jira/browse/QPID-4107 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.17 Reporter: Alan Conway Assignee: Alan Conway In a HA cluster, the alternate-exchange setting on queues and exchanges is not replicated. Note that to replicate it, you need to solve the problem of ensuring you have replicated the required exchange before you try to set it on a newly replicated queue (or exchange). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4159) HA missing messages in failover test.
[ https://issues.apache.org/jira/browse/QPID-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13423285#comment-13423285 ] Justin Ross commented on QPID-4159: --- Further change is approved for 0.18. HA missing messages in failover test. - Key: QPID-4159 URL: https://issues.apache.org/jira/browse/QPID-4159 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.17 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.18 Running this test: ha_tests.py *.test_failover_send_receive -DDURATION=2 in a loop eventually fails with something like: AssertionError: test8 missing message 1752917454 The test should run indefinitely with no missing messages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4164) Management moveMessage/copyMessage functions fail to properly move/copy the message if the message has been loaded from the store at Broker startup
[ https://issues.apache.org/jira/browse/QPID-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13424884#comment-13424884 ] Justin Ross commented on QPID-4164: --- Reviewed by Keith, Philip, and Robbie. Approved for 0.18. Management moveMessage/copyMessage functions fail to properly move/copy the message if the message has been loaded from the store at Broker startup --- Key: QPID-4164 URL: https://issues.apache.org/jira/browse/QPID-4164 Project: Qpid Issue Type: Bug Components: Java Broker, Java Broker BDB Store, Java Management : JMX Console Affects Versions: 0.16, 0.18 Reporter: Keith Wall Assignee: Keith Wall Priority: Critical Fix For: 0.19 Attachments: QPID-4164-MaxDeliveryCountTest-should-restart-broker-after-enqueue.patch The JMX moveMessage/copyMessage functions fail to properly move/copy the message if the message has been recovered from the store at Broker startup. The Broker permanently loses the message's payload. If an operator subsequently tries to view the problematic message with the Management interfaces, a Broker thread will be put into an infinite loop and this will require a Broker restart. This problem does not affect messages sent during the lifetime of the Broker's execution (they can be moved or copied as normal). The existence of messages with lost payload within the Broker does not affect the flight of other messages through the Broker. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4170) JMX threads can spin in the Queue MBean if there is a failure when viewing message content
[ https://issues.apache.org/jira/browse/QPID-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13426542#comment-13426542 ] Justin Ross commented on QPID-4170: --- Reviewed by Keith. Approved for 0.18. JMX threads can spin in the Queue MBean if there is a failure when viewing message content -- Key: QPID-4170 URL: https://issues.apache.org/jira/browse/QPID-4170 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.12, 0.13, 0.14, 0.15, 0.16, 0.17, 0.18 Reporter: Robbie Gemmell Assignee: Keith Wall Priority: Critical Fix For: 0.19 During the work on QPID-4164 it was found that JMX threads can spin in the Queue MBean if they fail when viewing message content, looping down into the message and back store asking for content which will never be returned. These threads will never stop spinning, and will consume CPU resources and introduce additional/unnecessary resource contention within the store layer. The view content method of the Queue MBean should be updated to avoid this possibility. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4167) Queue attributes are ignored on queue creation with web management console
[ https://issues.apache.org/jira/browse/QPID-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13426544#comment-13426544 ] Justin Ross commented on QPID-4167: --- Reviewed by Keith and Robbie. Approved for 0.18. Queue attributes are ignored on queue creation with web management console -- Key: QPID-4167 URL: https://issues.apache.org/jira/browse/QPID-4167 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.18, 0.19 Reporter: Alex Rudyy Assignee: Robbie Gemmell Fix For: 0.19 Attachments: 0001-QPID-4167-Fix-setting-of-queue-attributes-via-web-ma.patch Setting of such attributes like queueFlowControlSizeBytes, queueFlowResumeSizeBytes, alertThresholdMessageAge, alertThresholdMessageSize, alertThresholdQueueDepthMessages, alertRepeatGap on queue creation with web management console does not work. These attributes are ignored on queue creation with web management console. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4183) [Java Broker] AMQP 1.0 implementation broken by management adaptation layer
[ https://issues.apache.org/jira/browse/QPID-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427362#comment-13427362 ] Justin Ross commented on QPID-4183: --- http://svn.apache.org/viewvc?view=revisionrevision=1368414 Reviewed by Robbie. Approved for 0.18. [Java Broker] AMQP 1.0 implementation broken by management adaptation layer --- Key: QPID-4183 URL: https://issues.apache.org/jira/browse/QPID-4183 Project: Qpid Issue Type: Bug Reporter: Rob Godfrey Assignee: Rob Godfrey Fix For: 0.19 The management adapters added to the broker break the AMQP 1.0 implementation as the implementaion of SessionModel and ConnectionModel is now required or else the connection cannot be properly initiated. Add a minimal implementation to restore AMQP 1.0 functionality -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4142) C++ broker connection counting username error when used in ha cluster and auth is EXTERNAL
[ https://issues.apache.org/jira/browse/QPID-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13433504#comment-13433504 ] Justin Ross commented on QPID-4142: --- Reviewed by Andrew (and Alan, as it happens). Approved for 0.18. C++ broker connection counting username error when used in ha cluster and auth is EXTERNAL -- Key: QPID-4142 URL: https://issues.apache.org/jira/browse/QPID-4142 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.18 Reporter: Chuck Rolke In a cluster setup with auth enabled and set to EXTERNAL then the Acl connection counting does not get the correct username associated with a shadowed connection. The cluster member that accepts the connection accounts for the correct user name. Other cluster members that receive shadow connections see user name 'anonymous'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4142) C++ broker connection counting username error when used in ha cluster and auth is EXTERNAL
[ https://issues.apache.org/jira/browse/QPID-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13433545#comment-13433545 ] Justin Ross commented on QPID-4142: --- Chuck merged this to trunk at revision 1372597. C++ broker connection counting username error when used in ha cluster and auth is EXTERNAL -- Key: QPID-4142 URL: https://issues.apache.org/jira/browse/QPID-4142 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.18 Reporter: Chuck Rolke Fix For: 0.18 In a cluster setup with auth enabled and set to EXTERNAL then the Acl connection counting does not get the correct username associated with a shadowed connection. The cluster member that accepts the connection accounts for the correct user name. Other cluster members that receive shadow connections see user name 'anonymous'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4142) C++ broker connection counting username error when used in ha cluster and auth is EXTERNAL
[ https://issues.apache.org/jira/browse/QPID-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-4142. --- Resolution: Fixed Fix Version/s: 0.18 Assignee: Chuck Rolke C++ broker connection counting username error when used in ha cluster and auth is EXTERNAL -- Key: QPID-4142 URL: https://issues.apache.org/jira/browse/QPID-4142 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.18 Reporter: Chuck Rolke Assignee: Chuck Rolke Fix For: 0.18 In a cluster setup with auth enabled and set to EXTERNAL then the Acl connection counting does not get the correct username associated with a shadowed connection. The cluster member that accepts the connection accounts for the correct user name. Other cluster members that receive shadow connections see user name 'anonymous'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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] [Comment Edited] (QPID-4142) C++ broker connection counting username error when used in ha cluster and auth is EXTERNAL
[ https://issues.apache.org/jira/browse/QPID-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13433545#comment-13433545 ] Justin Ross edited comment on QPID-4142 at 8/14/12 8:08 AM: Chuck merged this to the release branch at revision 1372597. was (Author: justi9): Chuck merged this to trunk at revision 1372597. C++ broker connection counting username error when used in ha cluster and auth is EXTERNAL -- Key: QPID-4142 URL: https://issues.apache.org/jira/browse/QPID-4142 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.18 Reporter: Chuck Rolke Assignee: Chuck Rolke Fix For: 0.18 In a cluster setup with auth enabled and set to EXTERNAL then the Acl connection counting does not get the correct username associated with a shadowed connection. The cluster member that accepts the connection accounts for the correct user name. Other cluster members that receive shadow connections see user name 'anonymous'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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-4102) Sender.send(timeout=N) should pass timeout=N to self.sync()
[ https://issues.apache.org/jira/browse/QPID-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-4102. --- Resolution: Fixed Fix Version/s: 0.19 Assignee: Justin Ross Fixed in revision 1399445 by committing Ernie's patch. Sender.send(timeout=N) should pass timeout=N to self.sync() --- Key: QPID-4102 URL: https://issues.apache.org/jira/browse/QPID-4102 Project: Qpid Issue Type: Bug Components: Python Client Affects Versions: 0.16 Reporter: Mike Bonnet Assignee: Justin Ross Priority: Minor Fix For: 0.19 Attachments: endpoints.py_sync-timeout.patch Session.send(timeout=N) calls self.sync() with no timeout. In the case where self.capacity is UNLIMITED (the default) this can result in send() blocking indefinitely, even if called with a timeout. timeout=N should be passed through to the self.sync() call. -- 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-4410) Restore compatibility with pre-0.18 qpid-config command line options
Justin Ross created QPID-4410: - Summary: Restore compatibility with pre-0.18 qpid-config command line options Key: QPID-4410 URL: https://issues.apache.org/jira/browse/QPID-4410 Project: Qpid Issue Type: Bug Components: Tools Affects Versions: 0.18 Reporter: Justin Ross Assignee: Justin Ross Fix For: 0.19 -- 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-4410) Restore compatibility with pre-0.18 qpid-config command line options
[ https://issues.apache.org/jira/browse/QPID-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13489150#comment-13489150 ] Justin Ross commented on QPID-4410: --- As of 0.18, some of the command line arguments to qpid-config changed (for the better). Where possible, where there are no collisions, reintroduce the old command line args in order avoid breaking existing scripts. Restore compatibility with pre-0.18 qpid-config command line options Key: QPID-4410 URL: https://issues.apache.org/jira/browse/QPID-4410 Project: Qpid Issue Type: Bug Components: Tools Affects Versions: 0.18 Reporter: Justin Ross Assignee: Justin Ross Fix For: 0.19 -- 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-4410) Restore compatibility with pre-0.18 qpid-config command line options
[ https://issues.apache.org/jira/browse/QPID-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4410: -- Attachment: patch.txt Patch from Ernie Allen Restore compatibility with pre-0.18 qpid-config command line options Key: QPID-4410 URL: https://issues.apache.org/jira/browse/QPID-4410 Project: Qpid Issue Type: Bug Components: Tools Affects Versions: 0.18 Reporter: Justin Ross Assignee: Justin Ross Fix For: 0.19 Attachments: patch.txt -- 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-4410) Restore compatibility with pre-0.18 qpid-config command line options
[ https://issues.apache.org/jira/browse/QPID-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-4410. --- Resolution: Fixed Patch applied in revision 1404836 on trunk Restore compatibility with pre-0.18 qpid-config command line options Key: QPID-4410 URL: https://issues.apache.org/jira/browse/QPID-4410 Project: Qpid Issue Type: Bug Components: Tools Affects Versions: 0.18 Reporter: Justin Ross Assignee: Justin Ross Fix For: 0.19 Attachments: patch.txt -- 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] [Assigned] (QPID-4403) C++ Broker Timer warnings are still too verbose and frequent
[ https://issues.apache.org/jira/browse/QPID-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reassigned QPID-4403: - Assignee: Chuck Rolke C++ Broker Timer warnings are still too verbose and frequent Key: QPID-4403 URL: https://issues.apache.org/jira/browse/QPID-4403 Project: Qpid Issue Type: Improvement Components: C++ Broker Affects Versions: 0.18 Reporter: Chuck Rolke Assignee: Chuck Rolke Continuing issue QPID-3476. 1) Further reducing the timer warning message log level. Between 0.12 and 0.13 timer warning messages were demoted from warning to informational log levels. In 0.19 the external store produces overrun info messages every time leading to log file bloat. The proposal here is to demote the information statements to debug statements for the same reasons that they were demoted from warnings: Demoting the warnings to debug statements would avoid undue alarm and prevent excess noise in log files. Should there be a need to see the information it is a lot easier to enable it (--log-enable debug+:Timer) than it is to turn it off at present. 2) Increasing the timer warning interval. Another consideration is to change the hard-coded five second warning interval to something longer. I suggest that one minute would be a good choice. The timer warning code already accumulates the number of warnings for the warning interval to prevent a flood of warnings. Increasing the warning interval further reduces the flood. 3) Performance improvement. When Issue 3476 was patched from warning to info there was a corresponding QPID_LOG_TEST in Timer.cpp that was not patched. This causes the late and overrun calculations to run even though the results will never be logged. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-2953) Qpid Cpp Messaging .NET Binding does not include unit tests
[ https://issues.apache.org/jira/browse/QPID-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-2953. --- Resolution: Fixed Fix Version/s: (was: Future) 0.10 jross@nicaea qpid$ svn log -c r1036644 r1036644 | chug | 2010-11-18 16:41:34 -0500 (Thu, 18 Nov 2010) | 4 lines QPID-2953 Qpid Cpp Messaging .NET Binding does not include unit tests. This checkin converts project test\messaging.test from an EXE to a DLL usable by NUnit. Tests for several managed objects are included in new files. Qpid Cpp Messaging .NET Binding does not include unit tests --- Key: QPID-2953 URL: https://issues.apache.org/jira/browse/QPID-2953 Project: Qpid Issue Type: Improvement Components: Dot Net Client Affects Versions: 0.8 Environment: Windows build Reporter: Chuck Rolke Assignee: Chuck Rolke Fix For: 0.10 The .NET Binding solution includes a project named Test\messaging.test. This directory is disorganized with respect to a formal test suite. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3291) Broker incorrectly sets TTL to 0 for messages about to expire
[ https://issues.apache.org/jira/browse/QPID-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3291: -- Fix Version/s: 0.12 Broker incorrectly sets TTL to 0 for messages about to expire - Key: QPID-3291 URL: https://issues.apache.org/jira/browse/QPID-3291 Project: Qpid Issue Type: Bug Components: C++ Broker Reporter: Andy Goldstein Fix For: 0.12 Attachments: QPID-3291.patch When qpid::broker::Message::adjustTtl() is called prior to delivering a message to a peer, it adjusts the TTL down to reflect the time the message spent in the broker. For a message that has expired, it sets the TTL to 1. The current logic calculates the remaining TTL as the difference, in nanoseconds, between the current time and the expiration time. If this value is greater than 0, it converts the remaining TTL to milliseconds and sets it on the message; otherwise, it sets the TTL to 1. This logic could result in a message that is about to expire receiving a TTL of 0. This would occur if the remaining TTL is somewhere between 1 and 1,000,000 ns. When the division occurs to convert to ms, it would result in some number between 0 and 1, which is rounded down to 0. Instead, this value should be 1. To fix this, the remaining TTL should be compared against 1,000,000. If it is = to that number, then the conversion can proceed successfully; otherwise, the TTL should be set to 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] [Updated] (QPID-4379) HA does not properly handle expired messages
[ https://issues.apache.org/jira/browse/QPID-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4379: -- Fix Version/s: 0.19 HA does not properly handle expired messages - Key: QPID-4379 URL: https://issues.apache.org/jira/browse/QPID-4379 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.18 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.19 Description of problem: If a message expires in a queue before the HA replicator is able to browse the message, the message will be skipped and not replicated. This results in the expired message's async completion never being finalized which can stall the original source of the expired message since it will never receive a completion. Oct 18 10:56:02 itcm24 qpidd[48819]: 2012-10-18 10:56:02 [Broker] debug Browser skipping message from 'QueueXyz' Version-Release number of selected component (if applicable): Qpid 0.18 How reproducible: Frequently Steps to Reproduce: 1. It's a race condition between a message expiring in the queue and the HA browsing subscription being able to replicate it. Actual results: The expired message is skipped and its async completion is never finalized. Expected results: While it is not truly necessary for the HA replicating subscription to replicate an expired message, the async completion needs to be finished. Additional info: see also https://bugzilla.redhat.com/show_bug.cgi?id=868360 -- 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-4360) Non-ready HA broker can be incorrectly promoted
[ https://issues.apache.org/jira/browse/QPID-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4360: -- Fix Version/s: 0.19 Non-ready HA broker can be incorrectly promoted Key: QPID-4360 URL: https://issues.apache.org/jira/browse/QPID-4360 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.18 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.19 Description of problem: rgmanager can promote a non-ready backup HA broker to primary when other backup brokers are available in the ready state. This can result in loss of messages and broker configuration. Additionally, this can cause the previously ready backups to throw exceptions when connecting to the new primary: Sep 20 10:17:18 itcm12 qpidd[10871]: 2012-09-20 10:17:18 [HA] critical Backup queue Queue1: Replication failed: Invalid position move, preceeds messages Sep 20 10:17:18 itcm12 qpidd[10871]: 2012-09-20 10:17:18 [Protocol] error Unexpected exception: Invalid position move, preceeds messages Sep 20 10:17:18 itcm12 qpidd[10871]: 2012-09-20 10:17:18 [Broker] error Connection 10.3.100.12:43837-10.3.100.105:9006 closed by error: Invalid position move, preceeds messages(501) Version-Release number of selected component (if applicable): Qpid 0.18 How reproducible: 100% Steps to Reproduce: 1. Start a primary and backup broker 2. Inject messages into the primary and ensure messages replicate to backup 3. Restart the primary broker and manually re-promote to primary Actual results: Restarted broker becomes primary Expected results: Restarted broker refuses to become primary since at least one ready backup was discovered within some timeout -- 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-4448) Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault
[ https://issues.apache.org/jira/browse/QPID-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503869#comment-13503869 ] Justin Ross commented on QPID-4448: --- http://svn.apache.org/viewvc?view=revisionrevision=1412239 Andrew, please review for 0.18 inclusion. Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault -- Key: QPID-4448 URL: https://issues.apache.org/jira/browse/QPID-4448 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.19 Reporter: Gordon Sim Assignee: Andrew Stitcher Fix For: 0.19, 0.20 thus restricting 1.0-0-10 interop -- 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] [Assigned] (QPID-4448) Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault
[ https://issues.apache.org/jira/browse/QPID-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reassigned QPID-4448: - Assignee: Andrew Stitcher (was: Gordon Sim) Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault -- Key: QPID-4448 URL: https://issues.apache.org/jira/browse/QPID-4448 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.19 Reporter: Gordon Sim Assignee: Andrew Stitcher Fix For: 0.19, 0.20 thus restricting 1.0-0-10 interop -- 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-4449) Fix for QPID-4286 changed the standalone qmf-agent API
[ https://issues.apache.org/jira/browse/QPID-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4449: -- Fix Version/s: 0.20 Fix for QPID-4286 changed the standalone qmf-agent API -- Key: QPID-4449 URL: https://issues.apache.org/jira/browse/QPID-4449 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Affects Versions: 0.19 Reporter: Ted Ross Assignee: Ken Giusti Fix For: 0.19, 0.20, 0.21 The changes to qpid/trunk/qpid/cpp/include/qpid/management/Manageable.h cause applications that use the stand-alone qmf agent API to need to adapt. This file needs to be changed to provide backward compatibility for users of the API. -- 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-4448) Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault
[ https://issues.apache.org/jira/browse/QPID-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4448: -- Fix Version/s: 0.20 Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault -- Key: QPID-4448 URL: https://issues.apache.org/jira/browse/QPID-4448 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.19 Reporter: Gordon Sim Assignee: Andrew Stitcher Fix For: 0.19, 0.20 thus restricting 1.0-0-10 interop -- 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-4449) Fix for QPID-4286 changed the standalone qmf-agent API
[ https://issues.apache.org/jira/browse/QPID-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4449: -- Assignee: Ken Giusti (was: Ted Ross) Fix for QPID-4286 changed the standalone qmf-agent API -- Key: QPID-4449 URL: https://issues.apache.org/jira/browse/QPID-4449 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Affects Versions: 0.19 Reporter: Ted Ross Assignee: Ken Giusti Fix For: 0.19, 0.20, 0.21 The changes to qpid/trunk/qpid/cpp/include/qpid/management/Manageable.h cause applications that use the stand-alone qmf agent API to need to adapt. This file needs to be changed to provide backward compatibility for users of the API. -- 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-4449) Fix for QPID-4286 changed the standalone qmf-agent API
[ https://issues.apache.org/jira/browse/QPID-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503870#comment-13503870 ] Justin Ross commented on QPID-4449: --- http://svn.apache.org/viewvc?view=revisionrevision=1411761 Ken, please review for 0.20 inclusion. Fix for QPID-4286 changed the standalone qmf-agent API -- Key: QPID-4449 URL: https://issues.apache.org/jira/browse/QPID-4449 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Affects Versions: 0.19 Reporter: Ted Ross Assignee: Ken Giusti Fix For: 0.19, 0.20, 0.21 The changes to qpid/trunk/qpid/cpp/include/qpid/management/Manageable.h cause applications that use the stand-alone qmf agent API to need to adapt. This file needs to be changed to provide backward compatibility for users of the API. -- 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] [Comment Edited] (QPID-4448) Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault
[ https://issues.apache.org/jira/browse/QPID-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503869#comment-13503869 ] Justin Ross edited comment on QPID-4448 at 11/26/12 4:27 PM: - http://svn.apache.org/viewvc?view=revisionrevision=1412239 Andrew, please review for 0.20 inclusion. was (Author: justi9): http://svn.apache.org/viewvc?view=revisionrevision=1412239 Andrew, please review for 0.18 inclusion. Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault -- Key: QPID-4448 URL: https://issues.apache.org/jira/browse/QPID-4448 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.19 Reporter: Gordon Sim Assignee: Andrew Stitcher Fix For: 0.19, 0.20 thus restricting 1.0-0-10 interop -- 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-4451) Need to wait for outgoing messages to settle when calling Connection::close()
[ https://issues.apache.org/jira/browse/QPID-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503873#comment-13503873 ] Justin Ross commented on QPID-4451: --- This change is confined to the AMQP 1.0 path. Approved for 0.20. Need to wait for outgoing messages to settle when calling Connection::close() - Key: QPID-4451 URL: https://issues.apache.org/jira/browse/QPID-4451 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 -- 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-4452) issuing and handling of producer credit not implemented
[ https://issues.apache.org/jira/browse/QPID-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503874#comment-13503874 ] Justin Ross commented on QPID-4452: --- The change confined to the AMQP 1.0 code. Approved for 0.20. issuing and handling of producer credit not implemented --- Key: QPID-4452 URL: https://issues.apache.org/jira/browse/QPID-4452 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 Prevents proper stress testing. -- 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] [Comment Edited] (QPID-4452) issuing and handling of producer credit not implemented
[ https://issues.apache.org/jira/browse/QPID-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503874#comment-13503874 ] Justin Ross edited comment on QPID-4452 at 11/26/12 4:33 PM: - http://svn.apache.org/viewvc?view=revisionrevision=1412242 The change confined to the AMQP 1.0 code. Approved for 0.20. was (Author: justi9): The change confined to the AMQP 1.0 code. Approved for 0.20. issuing and handling of producer credit not implemented --- Key: QPID-4452 URL: https://issues.apache.org/jira/browse/QPID-4452 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 Prevents proper stress testing. -- 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] [Comment Edited] (QPID-4452) issuing and handling of producer credit not implemented
[ https://issues.apache.org/jira/browse/QPID-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503874#comment-13503874 ] Justin Ross edited comment on QPID-4452 at 11/26/12 4:33 PM: - http://svn.apache.org/viewvc?view=revisionrevision=1412242 The change is confined to the AMQP 1.0 code. Approved for 0.20. was (Author: justi9): http://svn.apache.org/viewvc?view=revisionrevision=1412242 The change confined to the AMQP 1.0 code. Approved for 0.20. issuing and handling of producer credit not implemented --- Key: QPID-4452 URL: https://issues.apache.org/jira/browse/QPID-4452 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 Prevents proper stress testing. -- 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-4453) [AMQP 1.0 JMS Client] ObjectMessage /w no body improperly converted to an AMQP message.
[ https://issues.apache.org/jira/browse/QPID-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4453: -- Fix Version/s: 0.20 [AMQP 1.0 JMS Client] ObjectMessage /w no body improperly converted to an AMQP message. --- Key: QPID-4453 URL: https://issues.apache.org/jira/browse/QPID-4453 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.18 Reporter: Hiram Chirino Assignee: Rob Godfrey Fix For: 0.20, 0.21 Attachments: QPID-4453.patch The following test case fails: ObjectMessage message = senderSession.createObjectMessage(); sender.send(message); Message msg = receiver.receive(TestConfig.TIMEOUT); Assert.assertTrue(The message should be an instance of ObjectMessage.\n, msg instanceof ObjectMessage); -- 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-4453) [AMQP 1.0 JMS Client] ObjectMessage /w no body improperly converted to an AMQP message.
[ https://issues.apache.org/jira/browse/QPID-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503877#comment-13503877 ] Justin Ross commented on QPID-4453: --- http://svn.apache.org/viewvc?view=revisionrevision=1412270 Patch reviewed by Rob. Approved for 0.20. [AMQP 1.0 JMS Client] ObjectMessage /w no body improperly converted to an AMQP message. --- Key: QPID-4453 URL: https://issues.apache.org/jira/browse/QPID-4453 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.18 Reporter: Hiram Chirino Assignee: Rob Godfrey Fix For: 0.20, 0.21 Attachments: QPID-4453.patch The following test case fails: ObjectMessage message = senderSession.createObjectMessage(); sender.send(message); Message msg = receiver.receive(TestConfig.TIMEOUT); Assert.assertTrue(The message should be an instance of ObjectMessage.\n, msg instanceof ObjectMessage); -- 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-4455) [AMQP 1.0 JMS Client] Queue browsers were not returning jms messages
[
https://issues.apache.org/jira/browse/QPID-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503880#comment-13503880
]
Justin Ross commented on QPID-4455:
---
http://svn.apache.org/viewvc?view=revisionrevision=1412280
Patch reviewed by Rob. Approved for 0.20.
[AMQP 1.0 JMS Client] Queue browsers were not returning jms messages
Key: QPID-4455
URL: https://issues.apache.org/jira/browse/QPID-4455
Project: Qpid
Issue Type: Bug
Components: Java Client
Reporter: Hiram Chirino
Assignee: Rob Godfrey
Fix For: 0.20, 0.21
Attachments: QPID-4455.patch
The following test case is failing:
MessageProducer p = session.createProducer(queue);
TextMessage message = session.createTextMessage();
message.setText(hello);
p.send(message);
QueueBrowser browser = session.createBrowser(queue);
Enumeration enumeration = browser.getEnumeration();
while (enumeration.hasMoreElements()) {
Message m = (Message) enumeration.nextElement();
assertTrue(m instanceof TextMessage);
}
--
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-4455) [AMQP 1.0 JMS Client] Queue browsers were not returning jms messages
[
https://issues.apache.org/jira/browse/QPID-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-4455:
--
Fix Version/s: 0.20
[AMQP 1.0 JMS Client] Queue browsers were not returning jms messages
Key: QPID-4455
URL: https://issues.apache.org/jira/browse/QPID-4455
Project: Qpid
Issue Type: Bug
Components: Java Client
Reporter: Hiram Chirino
Assignee: Rob Godfrey
Fix For: 0.20, 0.21
Attachments: QPID-4455.patch
The following test case is failing:
MessageProducer p = session.createProducer(queue);
TextMessage message = session.createTextMessage();
message.setText(hello);
p.send(message);
QueueBrowser browser = session.createBrowser(queue);
Enumeration enumeration = browser.getEnumeration();
while (enumeration.hasMoreElements()) {
Message m = (Message) enumeration.nextElement();
assertTrue(m instanceof TextMessage);
}
--
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-4456) update the Java broker-only release package to account for changes in plugin system
[ https://issues.apache.org/jira/browse/QPID-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503886#comment-13503886 ] Justin Ross commented on QPID-4456: --- The first change, from Robbie's initial comment, is reviewed by Rob and approved for 0.20. update the Java broker-only release package to account for changes in plugin system --- Key: QPID-4456 URL: https://issues.apache.org/jira/browse/QPID-4456 Project: Qpid Issue Type: Task Components: Packaging Affects Versions: 0.19 Reporter: Robbie Gemmell Assignee: Keith Wall Priority: Blocker Fix For: 0.20 Following the simplification of the plugin system in the Java broker via QPID-4335 and the modifications to the tests in QPID-4353, the plugins are not being packaged in the broker-only release binary (as per discussion on QPID- just prior to the 0.20 beta). The build system should be updated to account for the changes and ensure the plugins are again included. -- 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-4415) perl bindings installed in wrong place
[ https://issues.apache.org/jira/browse/QPID-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503895#comment-13503895 ] Justin Ross commented on QPID-4415: --- Hi, Darryl. Please add a comment with a link to the svn change. I didn't see it in the inclusion request mail. perl bindings installed in wrong place -- Key: QPID-4415 URL: https://issues.apache.org/jira/browse/QPID-4415 Project: Qpid Issue Type: Bug Affects Versions: 0.18 Reporter: Jimmy Jones Assignee: Darryl L. Pierce Attachments: 0001-QPID-4415-Fixes-Perl-bindings-install-location.patch, perl-bindings-path.patch On Ubuntu 12.04, if I run configure --prefix=/usr the bindings get installed into /usr/usr/lib/perl5... However if I run make install from bindings/qpid/perl they get correctly installed. On RHEL5 the same issues occurs, but additionally the architecture string is incorrectly put twice into the path /usr/lib/perl/5.14/x86_64-linux-gnu-thread-multi/x86_64-linux-gnu-thread-multi -- 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-4459) Sender doesn't settle messages
[ https://issues.apache.org/jira/browse/QPID-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503897#comment-13503897 ] Justin Ross commented on QPID-4459: --- http://svn.apache.org/viewvc?view=revisionrevision=1412960 Confined to AMQP 1.0 implemenation. Approved for 0.20. Sender doesn't settle messages -- Key: QPID-4459 URL: https://issues.apache.org/jira/browse/QPID-4459 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 -- 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-4460) after drain, full credit is not replenished
[ https://issues.apache.org/jira/browse/QPID-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503898#comment-13503898 ] Justin Ross commented on QPID-4460: --- http://svn.apache.org/viewvc?view=revisionrevision=1412961 Confined to AMQP 1.0 impl. Approved for 0.20. after drain, full credit is not replenished --- Key: QPID-4460 URL: https://issues.apache.org/jira/browse/QPID-4460 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 -- 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-4464) broker does not set container name on AMQP 1.0 connection open
[ https://issues.apache.org/jira/browse/QPID-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503901#comment-13503901 ] Justin Ross commented on QPID-4464: --- http://svn.apache.org/viewvc?view=revisionrevision=1412962 Reviewed by me and approved for 0.20. broker does not set container name on AMQP 1.0 connection open -- Key: QPID-4464 URL: https://issues.apache.org/jira/browse/QPID-4464 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 -- 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-4465) only send subject filter if subject is specified
[ https://issues.apache.org/jira/browse/QPID-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503902#comment-13503902 ] Justin Ross commented on QPID-4465: --- http://svn.apache.org/viewvc?view=revisionrevision=1412963 Confined to AMQP 1.0 impl. Approved for 0.20. only send subject filter if subject is specified Key: QPID-4465 URL: https://issues.apache.org/jira/browse/QPID-4465 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 -- 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-4415) perl bindings installed in wrong place
[ https://issues.apache.org/jira/browse/QPID-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503971#comment-13503971 ] Justin Ross commented on QPID-4415: --- Reviewed by me. Approved for 0.20. perl bindings installed in wrong place -- Key: QPID-4415 URL: https://issues.apache.org/jira/browse/QPID-4415 Project: Qpid Issue Type: Bug Affects Versions: 0.18 Reporter: Jimmy Jones Assignee: Darryl L. Pierce Attachments: 0001-QPID-4415-Fixes-Perl-bindings-install-location.patch, perl-bindings-path.patch On Ubuntu 12.04, if I run configure --prefix=/usr the bindings get installed into /usr/usr/lib/perl5... However if I run make install from bindings/qpid/perl they get correctly installed. On RHEL5 the same issues occurs, but additionally the architecture string is incorrectly put twice into the path /usr/lib/perl/5.14/x86_64-linux-gnu-thread-multi/x86_64-linux-gnu-thread-multi -- 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-4449) Fix for QPID-4286 changed the standalone qmf-agent API
[ https://issues.apache.org/jira/browse/QPID-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504048#comment-13504048 ] Justin Ross commented on QPID-4449: --- Reviewed by Ken. Approved for 0.20. Fix for QPID-4286 changed the standalone qmf-agent API -- Key: QPID-4449 URL: https://issues.apache.org/jira/browse/QPID-4449 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Affects Versions: 0.19 Reporter: Ted Ross Assignee: Ken Giusti Fix For: 0.19, 0.20, 0.21 The changes to qpid/trunk/qpid/cpp/include/qpid/management/Manageable.h cause applications that use the stand-alone qmf agent API to need to adapt. This file needs to be changed to provide backward compatibility for users of the API. -- 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-4424) C++ Broker on Windows - Assertion Failed: !dispatcher - PollableQueue.h line 136
[
https://issues.apache.org/jira/browse/QPID-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504200#comment-13504200
]
Justin Ross commented on QPID-4424:
---
https://reviews.apache.org/r/8147/
Approved for 0.20.
C++ Broker on Windows - Assertion Failed: !dispatcher - PollableQueue.h line
136
Key: QPID-4424
URL: https://issues.apache.org/jira/browse/QPID-4424
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.18
Environment: Windows Server 2008 R2 64-bit system
Visual Studio 2010 32-bit executable
Reporter: Chuck Rolke
Assignee: Steve Huston
Priority: Blocker
Fix For: 0.20, 0.21
Start broker with 'qpidd --auth no --no-data-dir'.
Sit for 15 or so seconds. No external connections from clients. No cluster.
Assert happens.
Stack at assert time:
msvcr100d.dll!_NMSG_WRITE(int rterrnum=10) Line 217C
msvcr100d.dll!abort() Line 61 + 0x7 bytes C
msvcr100d.dll!_wassert(const wchar_t * expr=0x5ff25504, const wchar_t *
filename=0x5ff25480, unsigned int lineno=136) Line 153 C
qpidbrokerd.dll!qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
::dispatch(qpid::sys::PollableCondition cond={...}) Line 136 + 0x36
bytes C++
qpidbrokerd.dll!boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
::operator()(qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
* p=0x00c72b80, qpid::sys::PollableCondition a1={...}) Line 165 + 0x10
bytes C++
qpidbrokerd.dll!boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1
::operator()boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list1qpid::sys::PollableCondition (boost::_bi::typevoid
__formal={...},
boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition f={...},
boost::_bi::list1qpid::sys::PollableCondition a={...},
boost::_bi::typevoid __formal={...}) Line 314C++
qpidbrokerd.dll!boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1
::operator()qpid::sys::PollableCondition(qpid::sys::PollableCondition
a1={...}) Line 33 C++
qpidbrokerd.dll!boost::detail::function::void_function_obj_invoker1boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1 ,void,qpid::sys::PollableCondition
::invoke(boost::detail::function::function_buffer function_obj_ptr={...},
qpid::sys::PollableCondition a0={...}) Line 154 C++
qpidcommond.dll!boost::function1void,qpid::sys::PollableCondition
::operator()(qpid::sys::PollableCondition a0={...}) Line 760 + 0x1a
bytes C++
qpidcommond.dll!qpid::sys::PollableConditionPrivate::dispatch(qpid::sys::windows::AsynchIoResult
* result=0x00cad6e0) Line 81 C++
qpidcommond.dll!boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*::operator()(qpid::sys::PollableConditionPrivate * p=0x00c72cd0,
qpid::sys::windows::AsynchIoResult * a1=0x00cad6e0) Line 165 + 0x10 bytes
C++
qpidcommond.dll!boost::_bi::list2boost::_bi::valueqpid::sys::PollableConditionPrivate
*,boost::arg1
::operator()boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*,boost::_bi::list1qpid::sys::windows::AsynchIoResult *
(boost::_bi::typevoid __formal={...},
boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
* f={...}, boost::_bi::list1qpid::sys::windows::AsynchIoResult *
a={...}, boost::_bi::typevoid __formal={...}) Line 314 C++
qpidcommond.dll!boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
[jira] [Updated] (QPID-4424) C++ Broker on Windows - Assertion Failed: !dispatcher - PollableQueue.h line 136
[
https://issues.apache.org/jira/browse/QPID-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-4424:
--
Fix Version/s: 0.20
C++ Broker on Windows - Assertion Failed: !dispatcher - PollableQueue.h line
136
Key: QPID-4424
URL: https://issues.apache.org/jira/browse/QPID-4424
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.18
Environment: Windows Server 2008 R2 64-bit system
Visual Studio 2010 32-bit executable
Reporter: Chuck Rolke
Assignee: Steve Huston
Priority: Blocker
Fix For: 0.20, 0.21
Start broker with 'qpidd --auth no --no-data-dir'.
Sit for 15 or so seconds. No external connections from clients. No cluster.
Assert happens.
Stack at assert time:
msvcr100d.dll!_NMSG_WRITE(int rterrnum=10) Line 217C
msvcr100d.dll!abort() Line 61 + 0x7 bytes C
msvcr100d.dll!_wassert(const wchar_t * expr=0x5ff25504, const wchar_t *
filename=0x5ff25480, unsigned int lineno=136) Line 153 C
qpidbrokerd.dll!qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
::dispatch(qpid::sys::PollableCondition cond={...}) Line 136 + 0x36
bytes C++
qpidbrokerd.dll!boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
::operator()(qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
* p=0x00c72b80, qpid::sys::PollableCondition a1={...}) Line 165 + 0x10
bytes C++
qpidbrokerd.dll!boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1
::operator()boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list1qpid::sys::PollableCondition (boost::_bi::typevoid
__formal={...},
boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition f={...},
boost::_bi::list1qpid::sys::PollableCondition a={...},
boost::_bi::typevoid __formal={...}) Line 314C++
qpidbrokerd.dll!boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1
::operator()qpid::sys::PollableCondition(qpid::sys::PollableCondition
a1={...}) Line 33 C++
qpidbrokerd.dll!boost::detail::function::void_function_obj_invoker1boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1 ,void,qpid::sys::PollableCondition
::invoke(boost::detail::function::function_buffer function_obj_ptr={...},
qpid::sys::PollableCondition a0={...}) Line 154 C++
qpidcommond.dll!boost::function1void,qpid::sys::PollableCondition
::operator()(qpid::sys::PollableCondition a0={...}) Line 760 + 0x1a
bytes C++
qpidcommond.dll!qpid::sys::PollableConditionPrivate::dispatch(qpid::sys::windows::AsynchIoResult
* result=0x00cad6e0) Line 81 C++
qpidcommond.dll!boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*::operator()(qpid::sys::PollableConditionPrivate * p=0x00c72cd0,
qpid::sys::windows::AsynchIoResult * a1=0x00cad6e0) Line 165 + 0x10 bytes
C++
qpidcommond.dll!boost::_bi::list2boost::_bi::valueqpid::sys::PollableConditionPrivate
*,boost::arg1
::operator()boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*,boost::_bi::list1qpid::sys::windows::AsynchIoResult *
(boost::_bi::typevoid __formal={...},
boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
* f={...}, boost::_bi::list1qpid::sys::windows::AsynchIoResult *
a={...}, boost::_bi::typevoid __formal={...}) Line 314 C++
qpidcommond.dll!boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*,boost::_bi::list2boost::_bi::valueqpid::sys::PollableConditionPrivate
*,boost::arg1 ::operator()qpid::sys::windows::AsynchIoResult
[jira] [Commented] (QPID-4448) Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault
[ https://issues.apache.org/jira/browse/QPID-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504813#comment-13504813 ] Justin Ross commented on QPID-4448: --- Reviewed by Andrew. Approved for 0.20. Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault -- Key: QPID-4448 URL: https://issues.apache.org/jira/browse/QPID-4448 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.19 Reporter: Gordon Sim Assignee: Andrew Stitcher Fix For: 0.19, 0.20 thus restricting 1.0-0-10 interop -- 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-4477) Need to handle case where outcome is issued by peer before init has been sent
[ https://issues.apache.org/jira/browse/QPID-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504818#comment-13504818 ] Justin Ross commented on QPID-4477: --- This change is isolated to the AMQP 1.0 impl. Approved for 0.20. Need to handle case where outcome is issued by peer before init has been sent - Key: QPID-4477 URL: https://issues.apache.org/jira/browse/QPID-4477 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 This is needed when connecting to a messenger listening on a socket as it assumes ANONYMOUS and issues positive outcome automatically. -- 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-4441) [Java broker] queue declare arguments are lost during v6 schema update for the optional bdbstore
[ https://issues.apache.org/jira/browse/QPID-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4441: -- Fix Version/s: 0.20 [Java broker] queue declare arguments are lost during v6 schema update for the optional bdbstore Key: QPID-4441 URL: https://issues.apache.org/jira/browse/QPID-4441 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.18 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Priority: Blocker Fix For: 0.19, 0.20 The queue declare arguments are lost during v5 - v6 store schema update for the optional bdbstore. This will present itself in a variety of ways, such as a DLQ losing the marker argument used to prevent chained DLQ creation, and also in Priority and Sorted queues becoming regular queues. As part of the schema update, the old FieldTable binary encoding for the queue arguments is transitioned to a property within the larger JSON ConfiguredObject encoding. This process makes use of an intermediate FieldTable to which it does an addAll() based copy of the original FieldTable and then potentially adds a new description argument. This addAll() fails to copy the previous properties due to a defect in the method, wherby the source FieldTables lack of use after creation from encoded bytes means they have yet to be decoded and this is in effect mistaken as it being an empty FieldTable. -- 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-4456) update the Java broker-only release package to account for changes in plugin system
[ https://issues.apache.org/jira/browse/QPID-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505393#comment-13505393 ] Justin Ross commented on QPID-4456: --- Second change reviewed by Keith; approved for 0.20. update the Java broker-only release package to account for changes in plugin system --- Key: QPID-4456 URL: https://issues.apache.org/jira/browse/QPID-4456 Project: Qpid Issue Type: Task Components: Packaging Affects Versions: 0.19 Reporter: Robbie Gemmell Assignee: Keith Wall Priority: Blocker Fix For: 0.20 Following the simplification of the plugin system in the Java broker via QPID-4335 and the modifications to the tests in QPID-4353, the plugins are not being packaged in the broker-only release binary (as per discussion on QPID- just prior to the 0.20 beta). The build system should be updated to account for the changes and ensure the plugins are again included. -- 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-4441) [Java broker] queue declare arguments are lost during v6 schema update for the optional bdbstore
[ https://issues.apache.org/jira/browse/QPID-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505392#comment-13505392 ] Justin Ross commented on QPID-4441: --- Reviewed by Alex. Approved for 0.20. [Java broker] queue declare arguments are lost during v6 schema update for the optional bdbstore Key: QPID-4441 URL: https://issues.apache.org/jira/browse/QPID-4441 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.18 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Priority: Blocker Fix For: 0.19, 0.20 The queue declare arguments are lost during v5 - v6 store schema update for the optional bdbstore. This will present itself in a variety of ways, such as a DLQ losing the marker argument used to prevent chained DLQ creation, and also in Priority and Sorted queues becoming regular queues. As part of the schema update, the old FieldTable binary encoding for the queue arguments is transitioned to a property within the larger JSON ConfiguredObject encoding. This process makes use of an intermediate FieldTable to which it does an addAll() based copy of the original FieldTable and then potentially adds a new description argument. This addAll() fails to copy the previous properties due to a defect in the method, wherby the source FieldTables lack of use after creation from encoded bytes means they have yet to be decoded and this is in effect mistaken as it being an empty FieldTable. -- 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-4476) [Java broker] SimpleLDAPAuthenticationManager returns different Principal name formats for sasl vs non-sasl usage
[ https://issues.apache.org/jira/browse/QPID-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505396#comment-13505396 ] Justin Ross commented on QPID-4476: --- Reviewed by Rob. Approved for 0.20. [Java broker] SimpleLDAPAuthenticationManager returns different Principal name formats for sasl vs non-sasl usage - Key: QPID-4476 URL: https://issues.apache.org/jira/browse/QPID-4476 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.18, 0.20 Reporter: Robbie Gemmell Assignee: Rob Godfrey Fix For: 0.20, 0.21 The SimpleLDAPAuthenticationManager returns different Principal name formats for sasl vs non-sasl usage. In the sasl case, the PlainSaslServer returns the basic username that was originally provided, but in the non-sasl case the SimpleLDAPAuthenticationManager returns a Principal based on the search context/filter. This leads to inconsistent behaviour between e.g. AMQP and JMX interface authentication, and in the later case means it is not possible to specify the user be included as part of an group. The non-sasl behaviour should be updated to be consistent with the sasl behaviour. -- 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-4476) [Java broker] SimpleLDAPAuthenticationManager returns different Principal name formats for sasl vs non-sasl usage
[ https://issues.apache.org/jira/browse/QPID-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4476: -- Fix Version/s: 0.20 [Java broker] SimpleLDAPAuthenticationManager returns different Principal name formats for sasl vs non-sasl usage - Key: QPID-4476 URL: https://issues.apache.org/jira/browse/QPID-4476 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.18, 0.20 Reporter: Robbie Gemmell Assignee: Rob Godfrey Fix For: 0.20, 0.21 The SimpleLDAPAuthenticationManager returns different Principal name formats for sasl vs non-sasl usage. In the sasl case, the PlainSaslServer returns the basic username that was originally provided, but in the non-sasl case the SimpleLDAPAuthenticationManager returns a Principal based on the search context/filter. This leads to inconsistent behaviour between e.g. AMQP and JMX interface authentication, and in the later case means it is not possible to specify the user be included as part of an group. The non-sasl behaviour should be updated to be consistent with the sasl behaviour. -- 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-4468) [Java client] restore ability to enable SSL using a connection level option rather than as a sub-option of each brokerlist entry
[ https://issues.apache.org/jira/browse/QPID-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505400#comment-13505400 ] Justin Ross commented on QPID-4468: --- Reviewed by Rob. Approve for 0.20. [Java client] restore ability to enable SSL using a connection level option rather than as a sub-option of each brokerlist entry Key: QPID-4468 URL: https://issues.apache.org/jira/browse/QPID-4468 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: 0.6, 0.8, 0.10, 0.12, 0.14, 0.16, 0.18 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.20, 0.21 On old client versions it was possible to specify that SSL should be used at the connection level options. It is now only possible to specify this as part of the brokerlist sub-options (in addition to much finer-grained control over the keystores/truststores and certificates etc to be used). If you are just using the SSL system properties to define they keystore/truststore etc and have multiple brokers in the brokerlist it is actually more convenient to specify ssl=true at the connection level. Restoring this will maintain compatibility for drop-in replacement of old clients and also help prevent user confiusion resulting from the URL parsers inability to alert them to the previous ssl configuration going unused. It will be restored as an ovveride of ssl option in the brokerlist entries. -- 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-4468) [Java client] restore ability to enable SSL using a connection level option rather than as a sub-option of each brokerlist entry
[ https://issues.apache.org/jira/browse/QPID-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4468: -- Fix Version/s: 0.20 [Java client] restore ability to enable SSL using a connection level option rather than as a sub-option of each brokerlist entry Key: QPID-4468 URL: https://issues.apache.org/jira/browse/QPID-4468 Project: Qpid Issue Type: Improvement Components: Java Client Affects Versions: 0.6, 0.8, 0.10, 0.12, 0.14, 0.16, 0.18 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.20, 0.21 On old client versions it was possible to specify that SSL should be used at the connection level options. It is now only possible to specify this as part of the brokerlist sub-options (in addition to much finer-grained control over the keystores/truststores and certificates etc to be used). If you are just using the SSL system properties to define they keystore/truststore etc and have multiple brokers in the brokerlist it is actually more convenient to specify ssl=true at the connection level. Restoring this will maintain compatibility for drop-in replacement of old clients and also help prevent user confiusion resulting from the URL parsers inability to alert them to the previous ssl configuration going unused. It will be restored as an ovveride of ssl option in the brokerlist entries. -- 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-4469) [Java common] remove unused sslContext parameter from OutgoingNetworkTransport#connect()
[ https://issues.apache.org/jira/browse/QPID-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4469: -- Fix Version/s: 0.20 [Java common] remove unused sslContext parameter from OutgoingNetworkTransport#connect() Key: QPID-4469 URL: https://issues.apache.org/jira/browse/QPID-4469 Project: Qpid Issue Type: Improvement Components: Java Client, Java Common Affects Versions: 0.14, 0.16, 0.18 Reporter: Robbie Gemmell Assignee: Rob Godfrey Fix For: 0.20, 0.21 OutgoingNetworkTransport#connect() takes an sslContext parameter. This is unused by the transport implementations because SSL is implemented in the client as a wrapper over the transport. The 0-10 path of the client supplies null for this arg, but the 08/0-9/0-9-1 patch still creates and supplies one. The parameter should be removed to ensure consistency now and in the future. -- 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-4474) ensure the BDBHAMessageStore JMX MBean name is quoted
[ https://issues.apache.org/jira/browse/QPID-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4474: -- Fix Version/s: 0.20 ensure the BDBHAMessageStore JMX MBean name is quoted - Key: QPID-4474 URL: https://issues.apache.org/jira/browse/QPID-4474 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.18 Reporter: Robbie Gemmell Assignee: Alex Rudyy Fix For: 0.20, 0.21 Ensure the BDBHAMessageStore JMX MBean name is quoted. The name of the other MBeans (Virtualhost, Queue, Exchange) are quoted to allow them to contain names which cant be encoded in an JMX ObjectName without use of quotes. The BDBHAMessageStore should also have its name quoted, for the same reasons and also for consistency with the other MBeans. -- 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-4474) ensure the BDBHAMessageStore JMX MBean name is quoted
[ https://issues.apache.org/jira/browse/QPID-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505407#comment-13505407 ] Justin Ross commented on QPID-4474: --- From the release-goals point of view, approved for 0.20. Alex will review. ensure the BDBHAMessageStore JMX MBean name is quoted - Key: QPID-4474 URL: https://issues.apache.org/jira/browse/QPID-4474 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.18 Reporter: Robbie Gemmell Assignee: Alex Rudyy Fix For: 0.20, 0.21 Ensure the BDBHAMessageStore JMX MBean name is quoted. The name of the other MBeans (Virtualhost, Queue, Exchange) are quoted to allow them to contain names which cant be encoded in an JMX ObjectName without use of quotes. The BDBHAMessageStore should also have its name quoted, for the same reasons and also for consistency with the other MBeans. -- 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-4461) [Java broker] the qpid-server startup scripts logfile naming prefix and suffix configuration does not work
[ https://issues.apache.org/jira/browse/QPID-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505411#comment-13505411 ] Justin Ross commented on QPID-4461: --- Approved for 0.20. This one's trivial and doesn't require further review imo. [Java broker] the qpid-server startup scripts logfile naming prefix and suffix configuration does not work -- Key: QPID-4461 URL: https://issues.apache.org/jira/browse/QPID-4461 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.18 Reporter: Robbie Gemmell Assignee: Alex Rudyy Fix For: 0.21 The qpid-server startup scripts logfile naming prefix and suffix configuration does not work. Setting the QPID_LOG_SUFFIX or QPID_LOG_PREFIX environment variables means the script unable to start the broker. -- 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-4461) [Java broker] the qpid-server startup scripts logfile naming prefix and suffix configuration does not work
[ https://issues.apache.org/jira/browse/QPID-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4461: -- Fix Version/s: 0.20 [Java broker] the qpid-server startup scripts logfile naming prefix and suffix configuration does not work -- Key: QPID-4461 URL: https://issues.apache.org/jira/browse/QPID-4461 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.18 Reporter: Robbie Gemmell Assignee: Alex Rudyy Fix For: 0.20, 0.21 The qpid-server startup scripts logfile naming prefix and suffix configuration does not work. Setting the QPID_LOG_SUFFIX or QPID_LOG_PREFIX environment variables means the script unable to start the broker. -- 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-4479) spout/drain examples fixes and improvements
[
https://issues.apache.org/jira/browse/QPID-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-4479:
--
Fix Version/s: 0.21
spout/drain examples fixes and improvements
---
Key: QPID-4479
URL: https://issues.apache.org/jira/browse/QPID-4479
Project: Qpid
Issue Type: Improvement
Reporter: Darryl L. Pierce
Assignee: Darryl L. Pierce
Priority: Minor
Fix For: 0.20, 0.21
(From BZ#878940)
Description of problem:
It is unable to set message properties with spout.pl, following change needs
to be made to fix this issue:
- $message-getProperties()-{$name} = $value;
+ $message-setProperty($name, $value);
Below are proposed changes to the spout/drain examples to be more conformable
to other clients (c++, python, java), I think it is valuable to have all the
client examples working the same way:
Patch files for both spout.pl/drain.pl can be found in attachment.
* drain.pl *:
Drain do not output the message properties in usable form (properties are
displayed as a hash), ie:
# perl /usr/share/doc/perl-qpid-0.18/examples/drain.pl -c 1 q
Message(properties=HASH(0x8f1ecc8),content='')
It also can be useful to display if the message is redelivered as other
clients do.
Proposing following change to fix these issues:
+sub printProperties {
+ my $h = shift();
+ return qq[{${\(join', ',map'$_': '$h-{$_}',keys%$h)}}]
+}
- print Message(properties= . $message-getProperties() . ,content=';
+ my $redelivered = ($message-getRedelivered) ? redelivered=True, : ;
+ print Message( . $redelivered . properties= .
printProperties($message-getProperties()) . , content=';
Proposing to set default timeout to 0 (to be more conformable to other
clients):
- my $timeout = 60;
+ my $timeout = 0;
Proposing to set default messages count to 0 (to be more conformable to other
clients)
- my $count = 1;
+ my $count = 0;
* both spout.pl/drain.pl *:
It is good practise to output usage with -h/--help options, or if the input
is wrong. It is also in place to stop the program execution after the bad
input/help request.
Proposing following change:
-connection-options=s = \ $connectionOptions,
-);
-
-
-if (! $result) {
-print Usage: perl drain.pl [OPTIONS]\n;
-}
-
+connection-options=s = \ $connectionOptions,
+help|h = \ usage
+) or usage();
+sub usage {
+print Usage: perl drain.pl [OPTIONS]\n;
+exit;
+}
Version-Release number of selected component (if applicable):
perl-qpid-0.18-1.el6
Actual results:
Unable to set message properties with spout.pl, spout/drain behaviour differs
from other clients (c++,py,java)
Expected results:
Message properties can be set using spout.pl, spout/drain behaviour more
concords to other clients
--
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-4479) spout/drain examples fixes and improvements
[
https://issues.apache.org/jira/browse/QPID-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505419#comment-13505419
]
Justin Ross commented on QPID-4479:
---
This change was codeveloped by Petr Matousek and Darryl. Approved for 0.20.
For the discussion, see https://bugzilla.redhat.com/show_bug.cgi?id=878940 .
spout/drain examples fixes and improvements
---
Key: QPID-4479
URL: https://issues.apache.org/jira/browse/QPID-4479
Project: Qpid
Issue Type: Improvement
Reporter: Darryl L. Pierce
Assignee: Darryl L. Pierce
Priority: Minor
Fix For: 0.20, 0.21
(From BZ#878940)
Description of problem:
It is unable to set message properties with spout.pl, following change needs
to be made to fix this issue:
- $message-getProperties()-{$name} = $value;
+ $message-setProperty($name, $value);
Below are proposed changes to the spout/drain examples to be more conformable
to other clients (c++, python, java), I think it is valuable to have all the
client examples working the same way:
Patch files for both spout.pl/drain.pl can be found in attachment.
* drain.pl *:
Drain do not output the message properties in usable form (properties are
displayed as a hash), ie:
# perl /usr/share/doc/perl-qpid-0.18/examples/drain.pl -c 1 q
Message(properties=HASH(0x8f1ecc8),content='')
It also can be useful to display if the message is redelivered as other
clients do.
Proposing following change to fix these issues:
+sub printProperties {
+ my $h = shift();
+ return qq[{${\(join', ',map'$_': '$h-{$_}',keys%$h)}}]
+}
- print Message(properties= . $message-getProperties() . ,content=';
+ my $redelivered = ($message-getRedelivered) ? redelivered=True, : ;
+ print Message( . $redelivered . properties= .
printProperties($message-getProperties()) . , content=';
Proposing to set default timeout to 0 (to be more conformable to other
clients):
- my $timeout = 60;
+ my $timeout = 0;
Proposing to set default messages count to 0 (to be more conformable to other
clients)
- my $count = 1;
+ my $count = 0;
* both spout.pl/drain.pl *:
It is good practise to output usage with -h/--help options, or if the input
is wrong. It is also in place to stop the program execution after the bad
input/help request.
Proposing following change:
-connection-options=s = \ $connectionOptions,
-);
-
-
-if (! $result) {
-print Usage: perl drain.pl [OPTIONS]\n;
-}
-
+connection-options=s = \ $connectionOptions,
+help|h = \ usage
+) or usage();
+sub usage {
+print Usage: perl drain.pl [OPTIONS]\n;
+exit;
+}
Version-Release number of selected component (if applicable):
perl-qpid-0.18-1.el6
Actual results:
Unable to set message properties with spout.pl, spout/drain behaviour differs
from other clients (c++,py,java)
Expected results:
Message properties can be set using spout.pl, spout/drain behaviour more
concords to other clients
--
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-4477) Need to handle case where outcome is issued by peer before init has been sent
[ https://issues.apache.org/jira/browse/QPID-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4477: -- Fix Version/s: 0.21 Need to handle case where outcome is issued by peer before init has been sent - Key: QPID-4477 URL: https://issues.apache.org/jira/browse/QPID-4477 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20, 0.21 This is needed when connecting to a messenger listening on a socket as it assumes ANONYMOUS and issues positive outcome automatically. -- 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
