Is there a command to totally clear a broker (routes & resources)?

2016-02-11 Thread jjw tectec
We can use "qpid-route route flush broker" to delete all routes for a broker. Is there a simple command that can totally clear a broker, deleting all its queues, exchanges, bindings, and routes?

Re: [Proposal] Roadmap for ending Java 7 support for the Java Broker and AMQP 0-x client

2016-02-11 Thread Jakub Scholz
Looks good to me. Even my (rather conservative) employer already started migrating some projects to Java 8. So I guess it should be ok. @Robbie: Are there any similar plans for the Qpid JMS client? Jakub On Thu, Feb 11, 2016 at 4:12 PM, Rob Godfrey wrote: > All, > > about 2 years ago we discus

RE: Help with Dispatch Build "difficulties"

2016-02-11 Thread Flores, Paul A.
Ken, It didn't work and errors out much earlier. Paul From: Ken Giusti [kgiu...@redhat.com] Sent: Thursday, February 11, 2016 3:16 PM To: users@qpid.apache.org Subject: Re: Help with Dispatch Build "difficulties" Hey - it seems like the math library is n

Re: Help with Dispatch Build "difficulties"

2016-02-11 Thread Ken Giusti
Hey - it seems like the math library is not being linked in. Apparently it's required by that version of python, and cmake can't figure that out. A workaround: try adding the library to the cmake file in src/CMakeLists.txt. You'll want to change: target_link_libraries(qpid-dispatch ${Proton_L

RE: Help with Dispatch Build "difficulties"

2016-02-11 Thread Flores, Paul A.
Ken, I installed Python 2.7 in my Centos 5 environment using some nifty instructions that I found on http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/. This reduced the errors to the following. Should I try a Python 3.3 installation? Paul /sbin/Python-2.7.6/libpython2.7.a(f

Re: Help with Dispatch Build "difficulties"

2016-02-11 Thread Ken Giusti
Paul, You can use 'ccmake' to edit the paths used to find your python install. Run ccmake .. from your build directory, it will display all the configuration name and settings. Type 't' to toggle to advance mode. use the up/down arrows to find PYTHON_LIBRARY PYTHON_INCLUDE_DIR PYTHON_EXECUTA

ApacheCon NA 2016 - Important Dates!!!

2016-02-11 Thread Melissa Warnkin
Hello everyone! I hope this email finds you well.  I hope everyone is as excited about ApacheCon as I am! I'd like to remind you all of a couple of important dates, as well as ask for your assistance in spreading the word! Please use your social media platform(s) to get the word out! The more v

RE: Help with Dispatch Build "difficulties"

2016-02-11 Thread Flores, Paul A.
Ted, It appears to compile but the undefined references. I do have python 2.6 installed on the system but from the linker it appears to be finding an earlier version. I'll look but if you have an idea right off the top of your head how I can get cmake to specifically "look for" python 2.6 tha

Re: Help with Dispatch Build "difficulties"

2016-02-11 Thread Ted Ross
Paul, That's odd because that code only has an effect if you are running Python earlier than 2.5. You said you were using 2.6.8. Do you have the right version (2.6.8) of python-devel installed? Aside from that issue, I think everything else was a warning. -Ted On 02/11/2016 12:24 PM, Flore

RE: Help with Dispatch Build "difficulties"

2016-02-11 Thread Flores, Paul A.
Ted, FYI inserting the following into python_embedded.c resolved one issue. Paul #if PY_VERSION_HEX < 0x0205 && !defined(PY_SSIZE_T_MIN) typedef int Py_ssize_t; #define PY_SSIZE_T_MAX INT_MAX #define PY_SSIZE_T_MIN INT_MIN #endif From: Ted Ross [tr.

RE: Help with Dispatch Build "difficulties"

2016-02-11 Thread Flores, Paul A.
Ted, The following is the output with warning as errors suppressed. Paul /shop/qpid-dispatch-0.5/src/lrp.c: In function ‘qd_lrpc_open_handler’: /shop/qpid-dispatch-0.5/src/lrp.c:59: warning: dereferencing type-punned pointer will break strict-aliasing rules /shop/qpid-dispatch-0.5/src/lrp.c: In

Re: [Proposal] Roadmap for ending Java 7 support for the Java Broker and AMQP 0-x client

2016-02-11 Thread Robbie Gemmell
On 11 February 2016 at 15:12, Rob Godfrey wrote: > All, > > about 2 years ago we discussed the roadmap for ending support for Java 6 > [1]. In April it will be one year since Oracle ceased public support for > Java 7. Towards the end of this year (hopefully) Java 9 will be released. > As such I

Re: Help with Dispatch Build "difficulties"

2016-02-11 Thread Ken Giusti
Hi Paul, Since it's just a warning, you can try removing the -Werror flag from the compiler directives. If you edit the CMakeLists.txt in the topmost directory, comment out the line where -Werror is configured, like so: add_compile_options(-pthread) add_compile_options(-Wall) ##add_compile_op

Re: Help with Dispatch Build "difficulties"

2016-02-11 Thread Ted Ross
Paul, Can you run a "make -k" on your Dispatch source to get a more complete list of build failures? I'd like to have a look at them. If you have proton 0.11, then dispatch _should_ build. -Ted On 02/11/2016 10:14 AM, Flores, Paul A. wrote: Hi Ganesh, I have proton 0.11 compiled and examp

RE: Help with Dispatch Build "difficulties"

2016-02-11 Thread Flores, Paul A.
Hi Ganesh, I have proton 0.11 compiled and examples working. I am using gcc version 4.1.2 and I have Python 2.6.8 installed. While moving to Centos 7 is in the works is there any other way to get past this issue? There is considerable interest in demonstrating dispatch prior to a "deeper"

[Proposal] Roadmap for ending Java 7 support for the Java Broker and AMQP 0-x client

2016-02-11 Thread Rob Godfrey
All, about 2 years ago we discussed the roadmap for ending support for Java 6 [1]. In April it will be one year since Oracle ceased public support for Java 7. Towards the end of this year (hopefully) Java 9 will be released. As such I think it is time for us to start discussing how long we will

Re: Hekp with Dispatch Build "difficulties"

2016-02-11 Thread Ganesh Murthy
Hi Paul, I tried to get a Docker environment going with CentOS 5 but ran into several problems. CentOS 5 is pre-2008 and has an old version of Python. Is there a way you can get to a recent version of CentOS (CentOS 7?). If you want to stay on CentOS 5, please try using dispatch 0.4 and prot