[jira] Assigned: (QPID-2045) crash when destroying a federation link with a dynamic bridge
[
https://issues.apache.org/jira/browse/QPID-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned QPID-2045:
--
Assignee: Ted Ross
> crash when destroying a federation link with a dynamic bridge
> -
>
> Key: QPID-2045
> URL: https://issues.apache.org/jira/browse/QPID-2045
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Environment: fedora core 11
>Reporter: Ken Giusti
>Assignee: Ted Ross
> Attachments: federation.patch
>
>
> While experimenting with the Federation tests, I managed to cause a crash in
> the broker. My modified test creates two bridges, but only calls
> "bridge.close()" on one of the bridges. This results in a broker crash. I
> will attach my test shortly. I am running the latest trunk as of today
> (8/11/2009). Thanks,
> -K
>
> pure virtual method called
> terminate called without an active exception
> Program received signal SIGABRT, Aborted.
> [Switching to Thread 0x75001910 (LWP 8354)]
> 0x765032f5 in raise () from /lib64/libc.so.6
> Missing separate debuginfos, use: debuginfo-install
> boost-1.37.0-6.fc11.x86_64 cyrus-sasl-lib-2.1.22-22.fc11.x86_64
> e2fsprogs-libs-1.41.4-12.fc11.x86_64 glibc-2.10.1-4.x86_64
> libgcc-4.4.0-4.x86_64 libstdc++-4.4.0-4.x86_64
> nss-softokn-freebl-3.12.3.99.3-2.11.3.fc11.x86_64
> (gdb) where
> warning: (Internal error: pc 0x776e55de in read in psymtab, but not in
> symtab.)
> warning: (Internal error: pc 0x776e55de in read in psymtab, but not in
> symtab.)
> warning: (Internal error: pc 0x776e5590 in read in psymtab, but not in
> symtab.)
> #0 0x765032f5 in raise () from /lib64/libc.so.6
> #1 0x76504b20 in abort () from /lib64/libc.so.6
> #2 0x003d972c3e15 in __gnu_cxx::__verbose_terminate_handler() () from
> /usr/lib64/libstdc++.so.6
> #3 0x003d972c2236 in ?? () from /usr/lib64/libstdc++.so.6
> #4 0x003d972c2263 in std::terminate() () from /usr/lib64/libstdc++.so.6
> #5 0x003d972c2b3f in __cxa_pure_virtual () from /usr/lib64/libstdc++.so.6
> #6 0x77abd565 in qpid::broker::Exchange::propagateFedOp
> (this=0x70034620, routingKey="ft-key.one.#", tags="", op="U", origin="")
> at qpid/broker/Exchange.cpp:237
> #7 0x77b34975 in qpid::broker::TopicExchange::unbind (this= optimized out>, queue=, constRoutingKey= out>) at qpid/broker/TopicExchange.cpp:267
> #8 0x77af6911 in qpid::broker::QueueBindings::unbind
> (this=0x70040058, exchanges=, queue={px =
> 0x7003fe10, pn = {pi_ = 0x7003b370}}) at
> qpid/broker/QueueBindings.cpp:39
> #9 0x77aed1be in qpid::broker::Queue::unbind (this= out>, exchang...@0x20a2, shared_ref=) at
> qpid/broker/Queue.cpp:849
> #10 0x77aed390 in qpid::broker::Queue::tryAutoDelete
> (brok...@0x629bb0, queue={px = 0x7003fe10, pn = {pi_ = 0x7003b370}})
> at qpid/broker/Queue.cpp:927
> #11 0x77b0e728 in qpid::broker::SemanticState::cancel (this= optimized out>, c=) at qpid/broker/SemanticState.cpp:342
> #12 0x77b12726 in qpid::broker::SemanticState::~SemanticState
> (this=0x700340c8, __in_chrg=) at
> qpid/broker/SemanticState.cpp:73
> #13 0x77b2f858 in qpid::broker::SessionState::~SessionState
> (this=0x70033ef0, __in_chrg=) at
> qpid/broker/SessionState.cpp:96
> #14 0x77b2825a in ~auto_ptr (this=,
> __in_chrg=) at
> /usr/lib/gcc/x86_64-redhat-linux/4.4.0/../../../../include/c++/4.4.0/backward/auto_ptr.h:168
> #15 qpid::broker::SessionHandler::handleDetach (this=,
> __in_chrg=) at qpid/broker/SessionHandler.cpp:70
> #16 0x776e478a in qpid::amqp_0_10::SessionHandler::detach
> (this=0x7b40, name="test-session") at
> qpid/amqp_0_10/SessionHandler.cpp:176
> #17 0x776a5e33 in
> qpid::framing::SessionDetachBody::invoke
> (invocable=, this=) at
> ../include/qpid/framing/SessionDetachBody.h:63
> #18 qpid::framing::AMQP_AllOperations::SessionHandler::Invoker::visit
> (invocable=, this=) at
> qpid/framing/AllInvoker.cpp:744
> #19 0x776e55df in
> qpid::framing::invoke (target= optimized out>, bo...@0x6) at ./qpid/framing/Invoker.h:67
> #20 0x776e1765 in qpid::amqp_0_10::SessionHandler::invoke (this=0x0,
> m...@0x6) at qpid/amqp_0_10/SessionHandler.cpp:72
> #21 0x776e2c00 in qpid::amqp_0_10::SessionHandler::handleIn
> (this=0x7b40, f...@0x750004d0) at
> qpid/amqp_0_10/SessionHandler.cpp:82
> #22 0x77a9ab23 in
> qpid::framing::Handler::operator() (t= optimized out>, this=) at ./qpid/framing/Handler.h:42
> #23 qpid::broker::Connection::received (t=, this= optimized out>) at qpid/broker/Connection.cpp:136
> #24 0x77a7e8e8 in qpid::amqp_0_10::Connection::decode
> (this=0x700012a0, buffer=, size= out>) at qpid/amqp
[jira] Updated: (QPID-2045) crash when destroying a federation link with a dynamic bridge
[
https://issues.apache.org/jira/browse/QPID-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated QPID-2045:
-
Attachment: federation.patch
diff against qpid/cpp/src/tests/federation.py test script - includes my test
which causes the crash.
> crash when destroying a federation link with a dynamic bridge
> -
>
> Key: QPID-2045
> URL: https://issues.apache.org/jira/browse/QPID-2045
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Environment: fedora core 11
>Reporter: Ken Giusti
> Attachments: federation.patch
>
>
> While experimenting with the Federation tests, I managed to cause a crash in
> the broker. My modified test creates two bridges, but only calls
> "bridge.close()" on one of the bridges. This results in a broker crash. I
> will attach my test shortly. I am running the latest trunk as of today
> (8/11/2009). Thanks,
> -K
>
> pure virtual method called
> terminate called without an active exception
> Program received signal SIGABRT, Aborted.
> [Switching to Thread 0x75001910 (LWP 8354)]
> 0x765032f5 in raise () from /lib64/libc.so.6
> Missing separate debuginfos, use: debuginfo-install
> boost-1.37.0-6.fc11.x86_64 cyrus-sasl-lib-2.1.22-22.fc11.x86_64
> e2fsprogs-libs-1.41.4-12.fc11.x86_64 glibc-2.10.1-4.x86_64
> libgcc-4.4.0-4.x86_64 libstdc++-4.4.0-4.x86_64
> nss-softokn-freebl-3.12.3.99.3-2.11.3.fc11.x86_64
> (gdb) where
> warning: (Internal error: pc 0x776e55de in read in psymtab, but not in
> symtab.)
> warning: (Internal error: pc 0x776e55de in read in psymtab, but not in
> symtab.)
> warning: (Internal error: pc 0x776e5590 in read in psymtab, but not in
> symtab.)
> #0 0x765032f5 in raise () from /lib64/libc.so.6
> #1 0x76504b20 in abort () from /lib64/libc.so.6
> #2 0x003d972c3e15 in __gnu_cxx::__verbose_terminate_handler() () from
> /usr/lib64/libstdc++.so.6
> #3 0x003d972c2236 in ?? () from /usr/lib64/libstdc++.so.6
> #4 0x003d972c2263 in std::terminate() () from /usr/lib64/libstdc++.so.6
> #5 0x003d972c2b3f in __cxa_pure_virtual () from /usr/lib64/libstdc++.so.6
> #6 0x77abd565 in qpid::broker::Exchange::propagateFedOp
> (this=0x70034620, routingKey="ft-key.one.#", tags="", op="U", origin="")
> at qpid/broker/Exchange.cpp:237
> #7 0x77b34975 in qpid::broker::TopicExchange::unbind (this= optimized out>, queue=, constRoutingKey= out>) at qpid/broker/TopicExchange.cpp:267
> #8 0x77af6911 in qpid::broker::QueueBindings::unbind
> (this=0x70040058, exchanges=, queue={px =
> 0x7003fe10, pn = {pi_ = 0x7003b370}}) at
> qpid/broker/QueueBindings.cpp:39
> #9 0x77aed1be in qpid::broker::Queue::unbind (this= out>, exchang...@0x20a2, shared_ref=) at
> qpid/broker/Queue.cpp:849
> #10 0x77aed390 in qpid::broker::Queue::tryAutoDelete
> (brok...@0x629bb0, queue={px = 0x7003fe10, pn = {pi_ = 0x7003b370}})
> at qpid/broker/Queue.cpp:927
> #11 0x77b0e728 in qpid::broker::SemanticState::cancel (this= optimized out>, c=) at qpid/broker/SemanticState.cpp:342
> #12 0x77b12726 in qpid::broker::SemanticState::~SemanticState
> (this=0x700340c8, __in_chrg=) at
> qpid/broker/SemanticState.cpp:73
> #13 0x77b2f858 in qpid::broker::SessionState::~SessionState
> (this=0x70033ef0, __in_chrg=) at
> qpid/broker/SessionState.cpp:96
> #14 0x77b2825a in ~auto_ptr (this=,
> __in_chrg=) at
> /usr/lib/gcc/x86_64-redhat-linux/4.4.0/../../../../include/c++/4.4.0/backward/auto_ptr.h:168
> #15 qpid::broker::SessionHandler::handleDetach (this=,
> __in_chrg=) at qpid/broker/SessionHandler.cpp:70
> #16 0x776e478a in qpid::amqp_0_10::SessionHandler::detach
> (this=0x7b40, name="test-session") at
> qpid/amqp_0_10/SessionHandler.cpp:176
> #17 0x776a5e33 in
> qpid::framing::SessionDetachBody::invoke
> (invocable=, this=) at
> ../include/qpid/framing/SessionDetachBody.h:63
> #18 qpid::framing::AMQP_AllOperations::SessionHandler::Invoker::visit
> (invocable=, this=) at
> qpid/framing/AllInvoker.cpp:744
> #19 0x776e55df in
> qpid::framing::invoke (target= optimized out>, bo...@0x6) at ./qpid/framing/Invoker.h:67
> #20 0x776e1765 in qpid::amqp_0_10::SessionHandler::invoke (this=0x0,
> m...@0x6) at qpid/amqp_0_10/SessionHandler.cpp:72
> #21 0x776e2c00 in qpid::amqp_0_10::SessionHandler::handleIn
> (this=0x7b40, f...@0x750004d0) at
> qpid/amqp_0_10/SessionHandler.cpp:82
> #22 0x77a9ab23 in
> qpid::framing::Handler::operator() (t= optimized out>, this=) at ./qpid/framing/Handler.h:42
> #23 qpid::broker::Connection::received (t=, this= optimized out>) at qpid/broker/Connection.cpp:136
> #24 0x77a7e8e8 in qpid::amqp_0_10
[jira] Created: (QPID-2045) crash when destroying a federation link with a dynamic bridge
crash when destroying a federation link with a dynamic bridge
-
Key: QPID-2045
URL: https://issues.apache.org/jira/browse/QPID-2045
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Environment: fedora core 11
Reporter: Ken Giusti
While experimenting with the Federation tests, I managed to cause a crash in
the broker. My modified test creates two bridges, but only calls
"bridge.close()" on one of the bridges. This results in a broker crash. I
will attach my test shortly. I am running the latest trunk as of today
(8/11/2009). Thanks,
-K
pure virtual method called
terminate called without an active exception
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x75001910 (LWP 8354)]
0x765032f5 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install boost-1.37.0-6.fc11.x86_64
cyrus-sasl-lib-2.1.22-22.fc11.x86_64 e2fsprogs-libs-1.41.4-12.fc11.x86_64
glibc-2.10.1-4.x86_64 libgcc-4.4.0-4.x86_64 libstdc++-4.4.0-4.x86_64
nss-softokn-freebl-3.12.3.99.3-2.11.3.fc11.x86_64
(gdb) where
warning: (Internal error: pc 0x776e55de in read in psymtab, but not in
symtab.)
warning: (Internal error: pc 0x776e55de in read in psymtab, but not in
symtab.)
warning: (Internal error: pc 0x776e5590 in read in psymtab, but not in
symtab.)
#0 0x765032f5 in raise () from /lib64/libc.so.6
#1 0x76504b20 in abort () from /lib64/libc.so.6
#2 0x003d972c3e15 in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib64/libstdc++.so.6
#3 0x003d972c2236 in ?? () from /usr/lib64/libstdc++.so.6
#4 0x003d972c2263 in std::terminate() () from /usr/lib64/libstdc++.so.6
#5 0x003d972c2b3f in __cxa_pure_virtual () from /usr/lib64/libstdc++.so.6
#6 0x77abd565 in qpid::broker::Exchange::propagateFedOp
(this=0x70034620, routingKey="ft-key.one.#", tags="", op="U", origin="") at
qpid/broker/Exchange.cpp:237
#7 0x77b34975 in qpid::broker::TopicExchange::unbind (this=, queue=, constRoutingKey=) at qpid/broker/TopicExchange.cpp:267
#8 0x77af6911 in qpid::broker::QueueBindings::unbind
(this=0x70040058, exchanges=, queue={px =
0x7003fe10, pn = {pi_ = 0x7003b370}}) at
qpid/broker/QueueBindings.cpp:39
#9 0x77aed1be in qpid::broker::Queue::unbind (this=, exchang...@0x20a2, shared_ref=) at
qpid/broker/Queue.cpp:849
#10 0x77aed390 in qpid::broker::Queue::tryAutoDelete (brok...@0x629bb0,
queue={px = 0x7003fe10, pn = {pi_ = 0x7003b370}}) at
qpid/broker/Queue.cpp:927
#11 0x77b0e728 in qpid::broker::SemanticState::cancel (this=, c=) at qpid/broker/SemanticState.cpp:342
#12 0x77b12726 in qpid::broker::SemanticState::~SemanticState
(this=0x700340c8, __in_chrg=) at
qpid/broker/SemanticState.cpp:73
#13 0x77b2f858 in qpid::broker::SessionState::~SessionState
(this=0x70033ef0, __in_chrg=) at
qpid/broker/SessionState.cpp:96
#14 0x77b2825a in ~auto_ptr (this=,
__in_chrg=) at
/usr/lib/gcc/x86_64-redhat-linux/4.4.0/../../../../include/c++/4.4.0/backward/auto_ptr.h:168
#15 qpid::broker::SessionHandler::handleDetach (this=,
__in_chrg=) at qpid/broker/SessionHandler.cpp:70
#16 0x776e478a in qpid::amqp_0_10::SessionHandler::detach
(this=0x7b40, name="test-session") at
qpid/amqp_0_10/SessionHandler.cpp:176
#17 0x776a5e33 in
qpid::framing::SessionDetachBody::invoke
(invocable=, this=) at
../include/qpid/framing/SessionDetachBody.h:63
#18 qpid::framing::AMQP_AllOperations::SessionHandler::Invoker::visit
(invocable=, this=) at
qpid/framing/AllInvoker.cpp:744
#19 0x776e55df in
qpid::framing::invoke (target=, bo...@0x6) at ./qpid/framing/Invoker.h:67
#20 0x776e1765 in qpid::amqp_0_10::SessionHandler::invoke (this=0x0,
m...@0x6) at qpid/amqp_0_10/SessionHandler.cpp:72
#21 0x776e2c00 in qpid::amqp_0_10::SessionHandler::handleIn
(this=0x7b40, f...@0x750004d0) at
qpid/amqp_0_10/SessionHandler.cpp:82
#22 0x77a9ab23 in
qpid::framing::Handler::operator() (t=, this=) at ./qpid/framing/Handler.h:42
#23 qpid::broker::Connection::received (t=, this=) at qpid/broker/Connection.cpp:136
#24 0x77a7e8e8 in qpid::amqp_0_10::Connection::decode
(this=0x700012a0, buffer=, size=)
at qpid/amqp_0_10/Connection.cpp:58
#25 0x7770c0b4 in qpid::sys::AsynchIOHandler::readbuff
(this=0x700356d0, buff=0x70043530) at qpid/sys/AsynchIOHandler.cpp:113
#26 0x77657c44 in boost::function2::operator() (this=,
a...@0x20a2, a1=0x6) at /usr/include/boost/function/function_template.hpp:989
#27 0x77655e29 in qpid::sys::posix::AsynchIO::readable
(this=0x70035d60, h=) at
qpid/sys/posix/AsynchIO.cpp:452
#28 0x77712b74 in boost::function1::operator() (this=,
a...@0x20a2) at /usr/include/boost/funct
[jira] Resolved: (QPID-1923) createDurableSubscriber should throw an InvalidDestinationException for temporary topics
[ https://issues.apache.org/jira/browse/QPID-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack resolved QPID-1923. Resolution: Fixed Fix Version/s: 0.6 Reviewed as part of pre-0.6 review task list. Looks ok to me, though dislike use of 'set' prefix on variable names (MR) :-) > createDurableSubscriber should throw an InvalidDestinationException for > temporary topics > > > Key: QPID-1923 > URL: https://issues.apache.org/jira/browse/QPID-1923 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: 0.6 >Reporter: Rafael H. Schloming >Assignee: Rafael H. Schloming > Fix For: 0.6 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1893) java cpp client doesn't generate heartbeats
[ https://issues.apache.org/jira/browse/QPID-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741931#action_12741931 ] Marnie McCormack commented on QPID-1893: Change reviewed as part of 0.6 trunk review tasks. Looks ok to me ! Not resolving JIRA as not sure if this task complete. > java cpp client doesn't generate heartbeats > --- > > Key: QPID-1893 > URL: https://issues.apache.org/jira/browse/QPID-1893 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: 0.5 >Reporter: Rafael H. Schloming >Assignee: Rafael H. Schloming > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1230) Refactor MockProtocolSession and replace with InternalTestProtocolSession
[ https://issues.apache.org/jira/browse/QPID-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack resolved QPID-1230. Resolution: Fixed Fix Version/s: 0.6 Reviewed changes & all ok. > Refactor MockProtocolSession and replace with InternalTestProtocolSession > - > > Key: QPID-1230 > URL: https://issues.apache.org/jira/browse/QPID-1230 > Project: Qpid > Issue Type: Task > Components: Java Tests >Affects Versions: M3 >Reporter: Martin Ritchie >Assignee: Martin Ritchie >Priority: Minor > Fix For: 0.6 > > > Summary: > As a result of QPID-1229 there is a large amount of duplication that we > should resolve in our tests and mock objects. > This JIRA is specific to the removal of MockProtocolSession and replacement > of refs to it with InternalTestProtocolSession instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: [GSoC] progress update (first pencils down date)
HI Robbie, Thanks for the update and all your work on the UI. On the bugs vs docs question, I'd def put the bugs on the list first :-) Thanks, Marnie On Tue, Aug 11, 2009 at 4:36 PM, Robbie Gemmell wrote: > Hi everyone, > > Yesterday marked the first 'pencils down' date in the GSoC timeline, > after which it is suggested we "Take a week to scrub code, write > tests, improve documentation, etc." in the run up to the final > 'pencils down' on August 17th 19:00 UTC. > > I have cataloged my progress in terms of JIRA's here: > http://cwiki.apache.org/confluence/display/qpid/Robbie+Gemmell > > Everything originally intended for the new UI is in place and > considered complete, along with some extra additions and improvements > suggested in the last couple weeks. One remaining suggested feature > (reloading the Log4J logging configuration via JMX on request) is > still being worked on. The actual addition of a JMX reload function is > tiny and straightforward, I am actually really working on the general > robustness of the Log4J configuration process at broker startup, > reload on request, and reload using Log4J's XMLWatchDog to monitor the > XML file for changes. > > I still need to create new documentation for the console to reflect > the updated UI, which has obviously rendered the existing user and > testing guides even more out of date than they were. That is what I > envisaged doing with my time before Monday, however I have also > discovered issues with the way the broker saves the user password and > management rights files. Its probable I wont get all of the above > issues completed fully by the GSoC deadline, but I will be continuing > to polish everything off before the 0.6 release, which allows plenty > of time. Is there a preference whether i should bias my attention > towards the bugs or the documentation at this stage? Given that the UI > is effectively complete and that was the purpose of the GSoC project, > I should perhaps use the remaining GSoC time to do the > documentation...but the bugs uncovered are fairly serious. Thoughts? > > Robbie > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > >
[GSoC] progress update (first pencils down date)
Hi everyone, Yesterday marked the first 'pencils down' date in the GSoC timeline, after which it is suggested we "Take a week to scrub code, write tests, improve documentation, etc." in the run up to the final 'pencils down' on August 17th 19:00 UTC. I have cataloged my progress in terms of JIRA's here: http://cwiki.apache.org/confluence/display/qpid/Robbie+Gemmell Everything originally intended for the new UI is in place and considered complete, along with some extra additions and improvements suggested in the last couple weeks. One remaining suggested feature (reloading the Log4J logging configuration via JMX on request) is still being worked on. The actual addition of a JMX reload function is tiny and straightforward, I am actually really working on the general robustness of the Log4J configuration process at broker startup, reload on request, and reload using Log4J's XMLWatchDog to monitor the XML file for changes. I still need to create new documentation for the console to reflect the updated UI, which has obviously rendered the existing user and testing guides even more out of date than they were. That is what I envisaged doing with my time before Monday, however I have also discovered issues with the way the broker saves the user password and management rights files. Its probable I wont get all of the above issues completed fully by the GSoC deadline, but I will be continuing to polish everything off before the 0.6 release, which allows plenty of time. Is there a preference whether i should bias my attention towards the bugs or the documentation at this stage? Given that the UI is effectively complete and that was the purpose of the GSoC project, I should perhaps use the remaining GSoC time to do the documentation...but the bugs uncovered are fairly serious. Thoughts? Robbie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2041) failed update to the Base64MD5PasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart
[ https://issues.apache.org/jira/browse/QPID-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2041: - Description: failed update to the MD5PasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart Certain use of the File.renameTo() function is not accompanied by a check of the boolean result, meaning a failed rename can leave the file in the wrong location, but the cached nature of the Base64MD5PasswordFilePrincipalDatabase masks the failure until another operation is attempted upon it that needs the output of the previously failed update. This has been observed in a situation where the OS Temp dir is on one file system, and the broker configuration is on another, which caused the rename to fail unnoticed. was: failed update to the MD5PasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart Certain use of the File.renameTo() function is not accompanied by a check of the boolean result, meaning a failed rename can leave the file in the wrong location, but the cached nature of the Base64MD5PasswordFilePrincipalDatabase masks the failure until another operation is attempted upon it that needs the output of the previously failed update. > failed update to the Base64MD5PasswordFilePrincipalDatabase on disk may go > unnoticed, preventing broker restart > --- > > Key: QPID-2041 > URL: https://issues.apache.org/jira/browse/QPID-2041 > Project: Qpid > Issue Type: Bug >Affects Versions: M3, M4, 0.5 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Critical > Fix For: 0.6 > > > failed update to the MD5PasswordFilePrincipalDatabase on disk may go > unnoticed, preventing broker restart > Certain use of the File.renameTo() function is not accompanied by a check of > the boolean result, meaning a failed rename can leave the file in the wrong > location, but the cached nature of the Base64MD5PasswordFilePrincipalDatabase > masks the failure until another operation is attempted upon it that needs the > output of the previously failed update. This has been observed in a situation > where the OS Temp dir is on one file system, and the broker configuration is > on another, which caused the rename to fail unnoticed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2040) failed update to the PlainPasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart
[ https://issues.apache.org/jira/browse/QPID-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2040: - Description: failed update to the PlainPasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart Certain use of the File.renameTo() function is not accompanied by a check of the boolean result, meaning a failed rename can leave the file in the wrong location, but the cached nature of the PlainPasswordFilePrincipalDatabase masks the failure until another operation is attempted upon it that needs the output of the previously failed update. This has been observed in a situation where the OS Temp dir is on one file system, and the broker configuration is on another, which caused the rename to fail unnoticed. was: failed update to the PlainPasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart Certain use of the File.renameTo() function is not accompanied by a check of the boolean result, meaning a failed rename can leave the file in the wrong location, but the cached nature of the PlainPasswordFilePrincipalDatabase masks the failure until another operation is attempted upon it that needs the output of the previously failed update. > failed update to the PlainPasswordFilePrincipalDatabase on disk may go > unnoticed, preventing broker restart > --- > > Key: QPID-2040 > URL: https://issues.apache.org/jira/browse/QPID-2040 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.5 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Critical > Fix For: 0.6 > > > failed update to the PlainPasswordFilePrincipalDatabase on disk may go > unnoticed, preventing broker restart > Certain use of the File.renameTo() function is not accompanied by a check of > the boolean result, meaning a failed rename can leave the file in the wrong > location, but the cached nature of the PlainPasswordFilePrincipalDatabase > masks the failure until another operation is attempted upon it that needs the > output of the previously failed update. This has been observed in a situation > where the OS Temp dir is on one file system, and the broker configuration is > on another, which caused the rename to fail unnoticed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2044) create a new JMX management console user guide
create a new JMX management console user guide -- Key: QPID-2044 URL: https://issues.apache.org/jira/browse/QPID-2044 Project: Qpid Issue Type: Task Components: Java Management : JMX Console Reporter: Robbie Gemmell Fix For: 0.6 The updated UI for the console has rendered the user guide even further out of date, and a new one should be created. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2043) create a new JMX management console testing spec
create a new JMX management console testing spec Key: QPID-2043 URL: https://issues.apache.org/jira/browse/QPID-2043 Project: Qpid Issue Type: Task Components: Java Management : JMX Console Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.6 The updated UI for the console has rendered the testing spec even further out of date, and a new one should be created. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2042) update to the management access rights may not be saved to disk, but still report success
update to the management access rights may not be saved to disk, but still report success - Key: QPID-2042 URL: https://issues.apache.org/jira/browse/QPID-2042 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.5 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Priority: Critical Fix For: 0.6 update to the management access rights may not be saved to disk, but still report success Certain use of the File.renameTo() function is not accompanied by a check of the boolean result, meaning a failed rename can leave the file in the wrong location. As a result, the existing file may not be replace,d though the cached rights will have been updated, meaning the update would simply be temporary. This has been observed in a situation where the OS Temp dir is on one file system, and the broker configuration is on another, which caused the rename to fail unnoticed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2041) failed update to the Base64MD5PasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart
failed update to the Base64MD5PasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart --- Key: QPID-2041 URL: https://issues.apache.org/jira/browse/QPID-2041 Project: Qpid Issue Type: Bug Affects Versions: M4, M3, 0.5 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Priority: Critical Fix For: 0.6 failed update to the MD5PasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart Certain use of the File.renameTo() function is not accompanied by a check of the boolean result, meaning a failed rename can leave the file in the wrong location, but the cached nature of the Base64MD5PasswordFilePrincipalDatabase masks the failure until another operation is attempted upon it that needs the output of the previously failed update. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2040) failed update to the PlainPasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart
failed update to the PlainPasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart --- Key: QPID-2040 URL: https://issues.apache.org/jira/browse/QPID-2040 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.5 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Priority: Critical Fix For: 0.6 failed update to the PlainPasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart Certain use of the File.renameTo() function is not accompanied by a check of the boolean result, meaning a failed rename can leave the file in the wrong location, but the cached nature of the PlainPasswordFilePrincipalDatabase masks the failure until another operation is attempted upon it that needs the output of the previously failed update. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2039) the JMX ConnectorServer is not closed during shutdown of the JMXManagedObjectRegistry
the JMX ConnectorServer is not closed during shutdown of the JMXManagedObjectRegistry - Key: QPID-2039 URL: https://issues.apache.org/jira/browse/QPID-2039 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: M4, M3, M2.1, 0.5 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.6 the JMX ConnectorServer is not closed during shutdown of the JMXManagedObjectRegistry -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1969) per-virtualhost notification areas show all notifications sent by the server
[ https://issues.apache.org/jira/browse/QPID-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1969. - Resolution: Fixed Looks good > per-virtualhost notification areas show all notifications sent by the server > > > Key: QPID-1969 > URL: https://issues.apache.org/jira/browse/QPID-1969 > Project: Qpid > Issue Type: Sub-task > Components: Java Management : JMX Console >Affects Versions: M2.1, M3, M4, 0.5 >Reporter: Robbie Gemmell >Assignee: Aidan Skinner > Fix For: 0.6 > > > The console offers per-virtualhost notification areas, however these show all > notifications sent by the server instead of just those related to the virtual > host being examined -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1967) gather list of available exchange types from broker instead of hardcoding in console
[ https://issues.apache.org/jira/browse/QPID-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1967. - Resolution: Fixed Looks good > gather list of available exchange types from broker instead of hardcoding in > console > > > Key: QPID-1967 > URL: https://issues.apache.org/jira/browse/QPID-1967 > Project: Qpid > Issue Type: Sub-task > Components: Java Management : JMX Console >Reporter: Robbie Gemmell >Assignee: Aidan Skinner > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1966) add status bar for feedback reports
[ https://issues.apache.org/jira/browse/QPID-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1966. - Resolution: Fixed Nice work! :) > add status bar for feedback reports > --- > > Key: QPID-1966 > URL: https://issues.apache.org/jira/browse/QPID-1966 > Project: Qpid > Issue Type: Sub-task > Components: Java Management : JMX Console >Reporter: Robbie Gemmell >Assignee: Aidan Skinner > > add status bar for feedback reports -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1230) Refactor MockProtocolSession and replace with InternalTestProtocolSession
[ https://issues.apache.org/jira/browse/QPID-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1230: --- Description: Summary: As a result of QPID-1229 there is a large amount of duplication that we should resolve in our tests and mock objects. This JIRA is specific to the removal of MockProtocolSession and replacement of refs to it with InternalTestProtocolSession instead. was: Summary: As a result of QPID-1229 there is a large amount of duplication that we should resolve in our tests and mock objects. AckTest and AcknowledgeTest AckTest contains publishMessage as does BrokerBaseCase. The version in AckTest registers a subscriber first but the BrokerBaseCase does not. We have 10 anonymous implementations of MessagePublishInfo, this is a prime candidate for a mock object. Summary: Refactor MockProtocolSession and replace with InternalTestProtocolSession (was: Broker contains duplicated mock object functionality and tests.) Updating JIRA to reflect specific task, and reviewing work > Refactor MockProtocolSession and replace with InternalTestProtocolSession > - > > Key: QPID-1230 > URL: https://issues.apache.org/jira/browse/QPID-1230 > Project: Qpid > Issue Type: Task > Components: Java Tests >Affects Versions: M3 >Reporter: Martin Ritchie >Assignee: Martin Ritchie >Priority: Minor > > Summary: > As a result of QPID-1229 there is a large amount of duplication that we > should resolve in our tests and mock objects. > This JIRA is specific to the removal of MockProtocolSession and replacement > of refs to it with InternalTestProtocolSession instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1887) JMS TTL not working
[ https://issues.apache.org/jira/browse/QPID-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1887. - Resolution: Fixed > JMS TTL not working > --- > > Key: QPID-1887 > URL: https://issues.apache.org/jira/browse/QPID-1887 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: M4 >Reporter: Rajith Attapattu >Assignee: Rajith Attapattu > Fix For: 0.6 > > > Even ff ttl is set in the message producer, it does not get set properly in > the > message properties. Hence the broker is not expiring them. > In the 0-10 codepath, the JMS client was incorrectly setting the expiration > field instead of the ttl field. > This is also related to QPID-1575 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1854) If a SocketTimeoutException is thrown due to an idle conneciton, the IoSender thread does not get closed.
[ https://issues.apache.org/jira/browse/QPID-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1854. - Resolution: Fixed > If a SocketTimeoutException is thrown due to an idle conneciton, the IoSender > thread does not get closed. > - > > Key: QPID-1854 > URL: https://issues.apache.org/jira/browse/QPID-1854 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: M4 >Reporter: Rajith Attapattu >Assignee: Rajith Attapattu >Priority: Critical > Fix For: 0.6 > > > If SocketTimeoutException is thrown due to heartbeats not received then the > java client does not close the IoSender properly. > This can be verified by running the java client with failover and obtaining a > thread dump after each failover attempt. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1853) IoReceiver is not closing the socket if a SocketTimeoutException thrown
[ https://issues.apache.org/jira/browse/QPID-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1853. - Resolution: Fixed > IoReceiver is not closing the socket if a SocketTimeoutException thrown > --- > > Key: QPID-1853 > URL: https://issues.apache.org/jira/browse/QPID-1853 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: M4 >Reporter: Rajith Attapattu >Assignee: Rajith Attapattu >Priority: Critical > Fix For: 0.6 > > > If a SocketTimeoutException is thrown then the IoReceiver does not close the > socket connection. > For that matter if the while loop in the run method of the IoReceiver does > not exit normally due to an exception (that does not result in the socket > being closed) then the socket connection remains open. > This causes tcp connections to remain open. Eventually due to failover > triggered by heartbeats not sent (which results in SocketTimeoutException) > the number of connections keeps growing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1875) Can't create durable queues that use amq.topic due to error in BindingURLParser.
[ https://issues.apache.org/jira/browse/QPID-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1875. - Resolution: Fixed > Can't create durable queues that use amq.topic due to error in > BindingURLParser. > > > Key: QPID-1875 > URL: https://issues.apache.org/jira/browse/QPID-1875 > Project: Qpid > Issue Type: Bug > Components: Java Client >Reporter: Rajith Attapattu >Assignee: Rajith Attapattu >Priority: Minor > Fix For: 0.6 > > > In BindingURLParser, process options method, line 420 has the following error > queueName = _bindingURL.getOption(BindingURL.OPTION_CLIENTID + ":" + > BindingURL.OPTION_SUBSCRIPTION); > This results in the queue name being null and the subsequent queue-declare > failing. It should be corrected to the following > queueName = _bindingURL.getOption(BindingURL.OPTION_CLIENTID + ":" + > BindingURL.OPTION_SUBSCRIPTION); > However I am not sure if forcing a particular pattern for the queue name and > treating it as a durable subscription if the exchange is amq.topic and queue > is durable is correct either. This will create confusion as when they tried > to work with this queue using mgt-tools or connect with other non java > clients, it may not be obvious that the queue name was generated in this > case. > The users should have the freedom to define a queue name of their choice. > There is a clear path to create durable subscriptions in the JMS API. So I > don't think we need to force it in the jndi.properties format. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1859) FailoverSingleServer and FailoverRoundRobinServer does not handle retry properly
[ https://issues.apache.org/jira/browse/QPID-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1859. - Resolution: Fixed > FailoverSingleServer and FailoverRoundRobinServer does not handle retry > properly > > > Key: QPID-1859 > URL: https://issues.apache.org/jira/browse/QPID-1859 > Project: Qpid > Issue Type: Bug > Components: Java Client >Affects Versions: M4 >Reporter: Rajith Attapattu >Assignee: Rajith Attapattu > Fix For: 0.6 > > > The FailoverSingleServer will retry twice than expected. It also retries by > default where as the correct default behavior should be to not to retry. > The FailoverRoundRobinServer also retries one extra time. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-1777) JNDI problem with white spaces
[ https://issues.apache.org/jira/browse/QPID-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1777. - Resolution: Fixed > JNDI problem with white spaces > -- > > Key: QPID-1777 > URL: https://issues.apache.org/jira/browse/QPID-1777 > Project: Qpid > Issue Type: Bug > Components: Java Client > Environment: all >Reporter: Ffrench Mathilde >Assignee: Rajith Attapattu > > Trailing spaces in queue and topic definitions are not discarded. > This leads to other errors as users think the Queue name is myQueue (while > the real queue name is myQueue where are trailing spaces) and tries > to use that name with management tools and fails to delete, purge ..etc > Ex when defining in JNDI properties file if there are trailling spaces as > follows. > queue.myqueue = my_queue > topic.mytopic = my_topic > topic.mytopic2 = my_bk1XX, my_bk2XX, my_bk3XX > where are trailing spaces. > The created queue names are as follows > my_queue instead of my_queue -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Opportunity: 0.6 Release Manager - C++ Volunteers
Taking on the Release Manager role is a great opportunity to get a firm handle on the Apache release process, meet new Qpid-ers and understand the whole Qpid product suite. I'd recommend it, really. Be great to hear from anyone with the desire to take this on ? I don't *think* we've ever had a non-Java committer perform a release from Qpid to date, so it's a great chance to break new ground. Regards, Marnie ps Once you've done it you can also legitimately politely decline all further invitations to take it on :-) On Thu, Aug 6, 2009 at 11:47 AM, Marnie McCormack < marnie.mccorm...@googlemail.com> wrote: > Are there any C++-ers available to act as Release Manager for our 0.6 > offering please ? > > Thought it'd be good to have a non-Java person doing our next one, > especially since some of the complex content is on the C++ side. > > Thanks & Regards, > Marnie >
