Re: Error compiling proton C++ binding 0.12 with GCC 3.4
Hi Andrew, Thanks for the pointer! Unfortunately this doesn't work, I'll see if we can include a newer version of GCC in our build chain. Alexandre On jeu., 2016-02-18 at 13:27 -0500, Andrew Stitcher wrote: > On Wed, 2016-02-17 at 10:51 +, TRUFANOW Alexandre wrote: > > Hi, > > > > I am attempting to compile proton and the C++ binding using GCC 3.4 > > This is a very old compiler (from no later than 2006), and we don't > test on it (although we are striving currently to support C++03). > > Going forward it is not too unlikely that we will move to using C++11 > features for our implementation. So if you can use a more recent > version of gcc (or clang) then you will be better off. > > > > and > > get the following error when compiling the C++ bindings. (compiler > > flags > > have been removed in proton-c/CMakeLists.txt: -pedantic-errors > > -Wno-variadic-macros) > > > > > [ 33%] Building CXX object proton-c/bindings/cpp/CMakeFiles/qpid- > > > proton-cpp.dir/src/acceptor.cpp.o > > > In file included from /tmp/qpid-proton-0.12.0/proton- > > > c/bindings/cpp/src/contexts.hpp:28, > > > from /tmp/qpid-proton-0.12.0/proton- > > > c/bindings/cpp/src/acceptor.cpp:26: > > > /tmp/qpid-proton-0.12.0/proton- > > > c/bindings/cpp/include/proton/container.hpp:129: error: declaration > > > of `void proton::container::link_options(const > > > proton::link_options&)' > > > /tmp/qpid-proton-0.12.0/proton- > > > c/bindings/cpp/include/proton/link_options.hpp:60: error: changes > > > meaning of `link_options' from `class proton::link_options' > > > make[2]: *** [proton-c/bindings/cpp/CMakeFiles/qpid-proton- > > > cpp.dir/src/acceptor.cpp.o] Error 1 > > > make[1]: *** [proton-c/bindings/cpp/CMakeFiles/qpid-proton- > > > cpp.dir/all] Error 2 > > > > From what I understand, this is due to a clash between the class > > proton::link_options and the method proton::container::link_options > > which cannot have the same name. > > As far as I can tell (and the compilers we test on seem to agree) there > is no name clash here (it is probably a name lookup bug in the > compiler)! > > You could try explicitly making the declaration: > > void link_options(const proton::link_options&); > > But I doubt this will help, as the compiler seems to know this already > and the name is not ambiguous. > > HTH > > Andrew > > > *** This e-mail contains information for the intended recipient only. It may contain proprietary material or confidential information. If you are not the intended recipient you are not authorised to distribute, copy or use this e-mail or any attachment to it. Murex cannot guarantee that it is virus free and accepts no responsibility for any loss or damage arising from its use. If you have received this e-mail in error please notify immediately the sender and delete the original email received, any attachments and all copies from your system.
Re: Dropping proton-dump; Moving to newer minimum CMake version
Well I left it 3 days, heard no objections so I will remove proton-dump and up the minimum version of cmake to 2.8.7. Andrew
[jira] [Created] (PROTON-1139) tx_recv_interactive.py example doesn't work
Jakub Scholz created PROTON-1139: Summary: tx_recv_interactive.py example doesn't work Key: PROTON-1139 URL: https://issues.apache.org/jira/browse/PROTON-1139 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.12.0 Reporter: Jakub Scholz Priority: Minor It looks like the tx_recv_interactive.py example doesn't work anymore, because the get_event_trigger method no longer exists. $ ./tx_recv_interactive.py Traceback (most recent call last): File "./tx_recv_interactive.py", line 70, in events = reactor.get_event_trigger() File "/usr/lib64/python2.7/site-packages/proton/wrapper.py", line 69, in __getattr__ raise AttributeError(name + " not in _attrs") AttributeError: get_event_trigger not in _attrs It looks like it should be replaced by the selectable method and EventInjector object. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] qpid-proton pull request: PROTON-1139 tx_recv_interactive.py examp...
GitHub user scholzj opened a pull request: https://github.com/apache/qpid-proton/pull/67 PROTON-1139 tx_recv_interactive.py example doesn't work This pull request should fix the tx_recv_interactive.py example. You can merge this pull request into a Git repository by running: $ git pull https://github.com/scholzj/qpid-proton PROTON-1139 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/67.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #67 commit 55d9f82fea5e55ce986d570f50258a0dc41e Author: Jakub Scholz Date: 2016-02-19T15:40:32Z PROTON-1139 using selectable() instead of get_event_trigger() --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (PROTON-1139) tx_recv_interactive.py example doesn't work
[ https://issues.apache.org/jira/browse/PROTON-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154372#comment-15154372 ] ASF GitHub Bot commented on PROTON-1139: GitHub user scholzj opened a pull request: https://github.com/apache/qpid-proton/pull/67 PROTON-1139 tx_recv_interactive.py example doesn't work This pull request should fix the tx_recv_interactive.py example. You can merge this pull request into a Git repository by running: $ git pull https://github.com/scholzj/qpid-proton PROTON-1139 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/67.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #67 commit 55d9f82fea5e55ce986d570f50258a0dc41e Author: Jakub Scholz Date: 2016-02-19T15:40:32Z PROTON-1139 using selectable() instead of get_event_trigger() > tx_recv_interactive.py example doesn't work > --- > > Key: PROTON-1139 > URL: https://issues.apache.org/jira/browse/PROTON-1139 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.12.0 >Reporter: Jakub Scholz >Priority: Minor > > It looks like the tx_recv_interactive.py example doesn't work anymore, > because the get_event_trigger method no longer exists. > $ ./tx_recv_interactive.py > Traceback (most recent call last): > File "./tx_recv_interactive.py", line 70, in > events = reactor.get_event_trigger() > File "/usr/lib64/python2.7/site-packages/proton/wrapper.py", line 69, in > __getattr__ > raise AttributeError(name + " not in _attrs") > AttributeError: get_event_trigger not in _attrs > It looks like it should be replaced by the selectable method and > EventInjector object. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Error compiling proton C++ binding 0.12 with GCC 3.4
On Thu, 2016-02-18 at 13:27 -0500, Andrew Stitcher wrote: > On Wed, 2016-02-17 at 10:51 +, TRUFANOW Alexandre wrote: > > Hi, > > > > I am attempting to compile proton and the C++ binding using GCC > > 3.4 > > This is a very old compiler (from no later than 2006), and we don't > test on it (although we are striving currently to support C++03). > > Going forward it is not too unlikely that we will move to using C++11 > features for our implementation. So if you can use a more recent > version of gcc (or clang) then you will be better off. > > > > and > > get the following error when compiling the C++ bindings. (compiler > > flags > > have been removed in proton-c/CMakeLists.txt: -pedantic-errors > > -Wno-variadic-macros) > > > > > [ 33%] Building CXX object proton-c/bindings/cpp/CMakeFiles/qpid- > > > proton-cpp.dir/src/acceptor.cpp.o > > > In file included from /tmp/qpid-proton-0.12.0/proton- > > > c/bindings/cpp/src/contexts.hpp:28, > > > from /tmp/qpid-proton-0.12.0/proton- > > > c/bindings/cpp/src/acceptor.cpp:26: > > > /tmp/qpid-proton-0.12.0/proton- > > > c/bindings/cpp/include/proton/container.hpp:129: error: > > > declaration > > > of `void proton::container::link_options(const > > > proton::link_options&)' > > > /tmp/qpid-proton-0.12.0/proton- > > > c/bindings/cpp/include/proton/link_options.hpp:60: error: changes > > > meaning of `link_options' from `class proton::link_options' > > > make[2]: *** [proton-c/bindings/cpp/CMakeFiles/qpid-proton- > > > cpp.dir/src/acceptor.cpp.o] Error 1 > > > make[1]: *** [proton-c/bindings/cpp/CMakeFiles/qpid-proton- > > > cpp.dir/all] Error 2 > > > > From what I understand, this is due to a clash between the class > > proton::link_options and the method proton::container::link_options > > which cannot have the same name. > > As far as I can tell (and the compilers we test on seem to agree) > there > is no name clash here (it is probably a name lookup bug in the > compiler)! > We came across this error (changes meaning) a lot when we were re- naming things and it is probably not referring to the different namespaces but to the fact that the unqualified name "link_options" is being used to refer to two different things in the same context: a member function and a class. > You could try explicitly making the declaration: > > void link_options(const proton::link_options&); I would have expected that to work since it makes the second use qualified. You could try adding a "class" qualifier to tell the compiler that you are *intentionally* referring to two different things, that is what we usually do when there is a member function that is also a class name: PN_CPP_EXTERN void link_options(const class link_options &); or maybe even PN_CPP_EXTERN void link_options(const class proton::link_options &); It might not work either but it just might sidestep the name resolution quirks in the older compiler. If it does let us know and we'll include the fix in next release.
Help?!: Qpid JMS 0.6.0 HelloWorld example issue
Trying to get the HelloWorld example that is found with the QPID JMS 0.6.0 Release to work. When I go to run it I am seeing the following. Can some one point me to a resolution? I am running out of hair to pull! Thanks. Paul 2016-02-19 10:32:47,256 [main ] - ERROR ProviderFactory - Failed to create Provider instance for AMQP, due to: java.io.IOException: Provider scheme NOT recognized: [AMQP] 2016-02-19 10:32:47,259 [main ] - ERROR JmsConnectionFactory - Failed to create JMS Provider instance for: AMQP Caught exception, exiting. javax.jms.JMSException: Failed to create connection to: AMQP://localhost:5672 at org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:66) at org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:165) at HelloWorld.main(HelloWorld.java:51) Caused by: java.io.IOException: Provider scheme NOT recognized: [AMQP] at org.apache.qpid.jms.provider.ProviderFactory.findProviderFactory(ProviderFactory.java:104) at org.apache.qpid.jms.provider.ProviderFactory.create(ProviderFactory.java:70) at org.apache.qpid.jms.JmsConnectionFactory.createProvider(JmsConnectionFactory.java:221) at org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:161) ... 1 more Caused by: org.apache.qpid.jms.util.ResourceNotFoundException: Could not find factory resource: META-INF/services/org/apache/qpid/jms/provider/AMQP at org.apache.qpid.jms.util.FactoryFinder$StandaloneObjectFactory.loadProperties(FactoryFinder.java:223) at org.apache.qpid.jms.util.FactoryFinder$StandaloneObjectFactory.create(FactoryFinder.java:164) at org.apache.qpid.jms.util.FactoryFinder.newInstance(FactoryFinder.java:122) at org.apache.qpid.jms.provider.ProviderFactory.findProviderFactory(ProviderFactory.java:102) ... 4 more
[jira] [Commented] (PROTON-1133) Proton C includes port number in AMQP Open hostname
[
https://issues.apache.org/jira/browse/PROTON-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154825#comment-15154825
]
ASF GitHub Bot commented on PROTON-1133:
Github user ganeshmurthy closed the pull request at:
https://github.com/apache/qpid-proton/pull/66
> Proton C includes port number in AMQP Open hostname
> ---
>
> Key: PROTON-1133
> URL: https://issues.apache.org/jira/browse/PROTON-1133
> Project: Qpid Proton
> Issue Type: Bug
>Affects Versions: 0.12.0
>Reporter: Chuck Rolke
>
> A command like:
> {noformat}
> qdmanage -b amqp://u1:password@photoserver:21000 --type policyStats query
> {noformat}
> sends the port number in the hostname field of the AMQP Open:
> {noformat}
> Mon Feb 8 11:37:46 2016 SERVER (trace) [2]:0 <- @open(16)
> [container-id="34e49947-b4df-4a01-9570-0a74e9e57b5b",
> hostname="photoserver:21000", channel-max=32767]
> (/home/chug/git/qpid-dispatch/src/server.c:75)
> {noformat}
> Built in C example code using Proton only does the same thing.
> This bug originally reported at
> https://issues.apache.org/jira/browse/DISPATCH-214
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] qpid-proton pull request: PROTON-1133 - Remove the port from the c...
Github user ganeshmurthy closed the pull request at: https://github.com/apache/qpid-proton/pull/66 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Help?!: Qpid JMS 0.6.0 HelloWorld example issue
On 02/19/2016 12:39 PM, Flores, Paul A. wrote: > Trying to get the HelloWorld example that is found with the QPID JMS 0.6.0 > Release to work. > > > > When I go to run it I am seeing the following. > > > > Can some one point me to a resolution? I am running out of hair to pull! > Try changing you URI in the jndi.properties to 'amqp://localhost:5672' not the 'amqp' is not capitalized. > > Thanks. > > > > Paul > > > > 2016-02-19 10:32:47,256 [main ] - ERROR ProviderFactory >- Failed to create Provider instance for AMQP, due to: > java.io.IOException: Provider scheme NOT recognized: [AMQP] > 2016-02-19 10:32:47,259 [main ] - ERROR JmsConnectionFactory >- Failed to create JMS Provider instance for: AMQP > Caught exception, exiting. > javax.jms.JMSException: Failed to create connection to: AMQP://localhost:5672 > at > org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:66) > at > org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:165) > at HelloWorld.main(HelloWorld.java:51) > Caused by: java.io.IOException: Provider scheme NOT recognized: [AMQP] > at > org.apache.qpid.jms.provider.ProviderFactory.findProviderFactory(ProviderFactory.java:104) > at > org.apache.qpid.jms.provider.ProviderFactory.create(ProviderFactory.java:70) > at > org.apache.qpid.jms.JmsConnectionFactory.createProvider(JmsConnectionFactory.java:221) > at > org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:161) > ... 1 more > Caused by: org.apache.qpid.jms.util.ResourceNotFoundException: Could not find > factory resource: META-INF/services/org/apache/qpid/jms/provider/AMQP > at > org.apache.qpid.jms.util.FactoryFinder$StandaloneObjectFactory.loadProperties(FactoryFinder.java:223) > at > org.apache.qpid.jms.util.FactoryFinder$StandaloneObjectFactory.create(FactoryFinder.java:164) > at > org.apache.qpid.jms.util.FactoryFinder.newInstance(FactoryFinder.java:122) > at > org.apache.qpid.jms.provider.ProviderFactory.findProviderFactory(ProviderFactory.java:102) > ... 4 more > -- Tim Bish twitter: @tabish121 blog: http://timbish.blogspot.com/
[GitHub] qpid-proton pull request: PROTON-1139 tx_recv_interactive.py examp...
Github user scholzj commented on the pull request: https://github.com/apache/qpid-proton/pull/67#issuecomment-186408961 I have to say that I haven't tested it on Windows, but I guess the original example didn't worked there either. Is there some way how to make the example work on Windows as well? If not, this change is probably better than nothing. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (PROTON-1139) tx_recv_interactive.py example doesn't work
[ https://issues.apache.org/jira/browse/PROTON-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154868#comment-15154868 ] ASF GitHub Bot commented on PROTON-1139: Github user scholzj commented on the pull request: https://github.com/apache/qpid-proton/pull/67#issuecomment-186408961 I have to say that I haven't tested it on Windows, but I guess the original example didn't worked there either. Is there some way how to make the example work on Windows as well? If not, this change is probably better than nothing. > tx_recv_interactive.py example doesn't work > --- > > Key: PROTON-1139 > URL: https://issues.apache.org/jira/browse/PROTON-1139 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.12.0 >Reporter: Jakub Scholz >Priority: Minor > > It looks like the tx_recv_interactive.py example doesn't work anymore, > because the get_event_trigger method no longer exists. > $ ./tx_recv_interactive.py > Traceback (most recent call last): > File "./tx_recv_interactive.py", line 70, in > events = reactor.get_event_trigger() > File "/usr/lib64/python2.7/site-packages/proton/wrapper.py", line 69, in > __getattr__ > raise AttributeError(name + " not in _attrs") > AttributeError: get_event_trigger not in _attrs > It looks like it should be replaced by the selectable method and > EventInjector object. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
RE: Help?!: Qpid JMS 0.6.0 HelloWorld example issue
I got that far now I am trying to create a queue. Don't seem to able to find qpid-config. In what release/download is that found? From: Timothy Bish [tabish...@gmail.com] Sent: Friday, February 19, 2016 2:41 PM To: proton@qpid.apache.org Subject: Re: Help?!: Qpid JMS 0.6.0 HelloWorld example issue On 02/19/2016 12:39 PM, Flores, Paul A. wrote: > Trying to get the HelloWorld example that is found with the QPID JMS 0.6.0 > Release to work. > > > > When I go to run it I am seeing the following. > > > > Can some one point me to a resolution? I am running out of hair to pull! > Try changing you URI in the jndi.properties to 'amqp://localhost:5672' not the 'amqp' is not capitalized. > > Thanks. > > > > Paul > > > > 2016-02-19 10:32:47,256 [main ] - ERROR ProviderFactory >- Failed to create Provider instance for AMQP, due to: > java.io.IOException: Provider scheme NOT recognized: [AMQP] > 2016-02-19 10:32:47,259 [main ] - ERROR JmsConnectionFactory >- Failed to create JMS Provider instance for: AMQP > Caught exception, exiting. > javax.jms.JMSException: Failed to create connection to: AMQP://localhost:5672 > at > org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:66) > at > org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:165) > at HelloWorld.main(HelloWorld.java:51) > Caused by: java.io.IOException: Provider scheme NOT recognized: [AMQP] > at > org.apache.qpid.jms.provider.ProviderFactory.findProviderFactory(ProviderFactory.java:104) > at > org.apache.qpid.jms.provider.ProviderFactory.create(ProviderFactory.java:70) > at > org.apache.qpid.jms.JmsConnectionFactory.createProvider(JmsConnectionFactory.java:221) > at > org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:161) > ... 1 more > Caused by: org.apache.qpid.jms.util.ResourceNotFoundException: Could not find > factory resource: META-INF/services/org/apache/qpid/jms/provider/AMQP > at > org.apache.qpid.jms.util.FactoryFinder$StandaloneObjectFactory.loadProperties(FactoryFinder.java:223) > at > org.apache.qpid.jms.util.FactoryFinder$StandaloneObjectFactory.create(FactoryFinder.java:164) > at > org.apache.qpid.jms.util.FactoryFinder.newInstance(FactoryFinder.java:122) > at > org.apache.qpid.jms.provider.ProviderFactory.findProviderFactory(ProviderFactory.java:102) > ... 4 more > -- Tim Bish twitter: @tabish121 blog: http://timbish.blogspot.com/
Re: Help?!: Qpid JMS 0.6.0 HelloWorld example issue
qpid-config is in the qpid-tools package. Go to the download site ( http://qpid.apache.org/download.html) and download the "C++ broker (command-line tools)". It is using the Python version of Qpid Messaging API, so you have to download that as well - it is on the same page. On Fri, Feb 19, 2016 at 10:28 PM, Flores, Paul A. wrote: > I got that far now I am trying to create a queue. Don't seem to able to > find qpid-config. In what release/download is that found? > > > From: Timothy Bish [tabish...@gmail.com] > Sent: Friday, February 19, 2016 2:41 PM > To: proton@qpid.apache.org > Subject: Re: Help?!: Qpid JMS 0.6.0 HelloWorld example issue > > On 02/19/2016 12:39 PM, Flores, Paul A. wrote: > > Trying to get the HelloWorld example that is found with the QPID JMS > 0.6.0 Release to work. > > > > > > > > When I go to run it I am seeing the following. > > > > > > > > Can some one point me to a resolution? I am running out of hair to pull! > > > > Try changing you URI in the jndi.properties to 'amqp://localhost:5672' > not the 'amqp' is not capitalized. > > > > > Thanks. > > > > > > > > Paul > > > > > > > > 2016-02-19 10:32:47,256 [main ] - ERROR ProviderFactory > - Failed to create Provider instance for AMQP, due to: > java.io.IOException: Provider scheme NOT recognized: [AMQP] > > 2016-02-19 10:32:47,259 [main ] - ERROR JmsConnectionFactory > - Failed to create JMS Provider instance for: AMQP > > Caught exception, exiting. > > javax.jms.JMSException: Failed to create connection to: > AMQP://localhost:5672 > > at > org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:66) > > at > org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:165) > > at HelloWorld.main(HelloWorld.java:51) > > Caused by: java.io.IOException: Provider scheme NOT recognized: [AMQP] > > at > org.apache.qpid.jms.provider.ProviderFactory.findProviderFactory(ProviderFactory.java:104) > > at > org.apache.qpid.jms.provider.ProviderFactory.create(ProviderFactory.java:70) > > at > org.apache.qpid.jms.JmsConnectionFactory.createProvider(JmsConnectionFactory.java:221) > > at > org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:161) > > ... 1 more > > Caused by: org.apache.qpid.jms.util.ResourceNotFoundException: Could not > find factory resource: META-INF/services/org/apache/qpid/jms/provider/AMQP > > at > org.apache.qpid.jms.util.FactoryFinder$StandaloneObjectFactory.loadProperties(FactoryFinder.java:223) > > at > org.apache.qpid.jms.util.FactoryFinder$StandaloneObjectFactory.create(FactoryFinder.java:164) > > at > org.apache.qpid.jms.util.FactoryFinder.newInstance(FactoryFinder.java:122) > > at > org.apache.qpid.jms.provider.ProviderFactory.findProviderFactory(ProviderFactory.java:102) > > ... 4 more > > > > > -- > Tim Bish > twitter: @tabish121 > blog: http://timbish.blogspot.com/
Re: Help?!: Qpid JMS 0.6.0 HelloWorld example issue
Glad to hear you got past the issue with your jndi config. Jakub's mail covers your question on qpid-config. Note you can also have the broker auto-create queues as needed using the CLI option I mentioned in your recent thread on the users list. As an aside, the current release of the client has been 0.7.0 for a couple months, and the 0.8.0 release just passed its vote now and will be reflected on the site come Monday. It will sync to maven central in the hours ahead, but is available now via repository.apache.org, or you can find an archive here also: http://apache.org/dist/qpid/jms/0.8.0/ Robbie On 19 February 2016 at 21:28, Flores, Paul A. wrote: > I got that far now I am trying to create a queue. Don't seem to able to find > qpid-config. In what release/download is that found? > > > From: Timothy Bish [tabish...@gmail.com] > Sent: Friday, February 19, 2016 2:41 PM > To: proton@qpid.apache.org > Subject: Re: Help?!: Qpid JMS 0.6.0 HelloWorld example issue > > On 02/19/2016 12:39 PM, Flores, Paul A. wrote: >> Trying to get the HelloWorld example that is found with the QPID JMS 0.6.0 >> Release to work. >> >> >> >> When I go to run it I am seeing the following. >> >> >> >> Can some one point me to a resolution? I am running out of hair to pull! >> > > Try changing you URI in the jndi.properties to 'amqp://localhost:5672' > not the 'amqp' is not capitalized. > >> >> Thanks. >> >> >> >> Paul >> >> >> >> 2016-02-19 10:32:47,256 [main ] - ERROR ProviderFactory >> - Failed to create Provider instance for AMQP, due to: >> java.io.IOException: Provider scheme NOT recognized: [AMQP] >> 2016-02-19 10:32:47,259 [main ] - ERROR JmsConnectionFactory >> - Failed to create JMS Provider instance for: AMQP >> Caught exception, exiting. >> javax.jms.JMSException: Failed to create connection to: AMQP://localhost:5672 >> at >> org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:66) >> at >> org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:165) >> at HelloWorld.main(HelloWorld.java:51) >> Caused by: java.io.IOException: Provider scheme NOT recognized: [AMQP] >> at >> org.apache.qpid.jms.provider.ProviderFactory.findProviderFactory(ProviderFactory.java:104) >> at >> org.apache.qpid.jms.provider.ProviderFactory.create(ProviderFactory.java:70) >> at >> org.apache.qpid.jms.JmsConnectionFactory.createProvider(JmsConnectionFactory.java:221) >> at >> org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:161) >> ... 1 more >> Caused by: org.apache.qpid.jms.util.ResourceNotFoundException: Could not >> find factory resource: META-INF/services/org/apache/qpid/jms/provider/AMQP >> at >> org.apache.qpid.jms.util.FactoryFinder$StandaloneObjectFactory.loadProperties(FactoryFinder.java:223) >> at >> org.apache.qpid.jms.util.FactoryFinder$StandaloneObjectFactory.create(FactoryFinder.java:164) >> at >> org.apache.qpid.jms.util.FactoryFinder.newInstance(FactoryFinder.java:122) >> at >> org.apache.qpid.jms.provider.ProviderFactory.findProviderFactory(ProviderFactory.java:102) >> ... 4 more >> > > > -- > Tim Bish > twitter: @tabish121 > blog: http://timbish.blogspot.com/
RE: Help?!: Qpid JMS 0.6.0 HelloWorld example issue
Thanks for your help. IMHO The examples need a bit more "meat" on them. A new user is going to be frustrated by the amount of implied but not explicit steps that are required to get them compiled and running. A inclusion of a configuration file that could be used with qpidd would be extremely helpful. From: Robbie Gemmell [robbie.gemm...@gmail.com] Sent: Friday, February 19, 2016 3:51 PM To: proton@qpid.apache.org Subject: Re: Help?!: Qpid JMS 0.6.0 HelloWorld example issue Glad to hear you got past the issue with your jndi config. Jakub's mail covers your question on qpid-config. Note you can also have the broker auto-create queues as needed using the CLI option I mentioned in your recent thread on the users list. As an aside, the current release of the client has been 0.7.0 for a couple months, and the 0.8.0 release just passed its vote now and will be reflected on the site come Monday. It will sync to maven central in the hours ahead, but is available now via repository.apache.org, or you can find an archive here also: http://apache.org/dist/qpid/jms/0.8.0/ Robbie On 19 February 2016 at 21:28, Flores, Paul A. wrote: > I got that far now I am trying to create a queue. Don't seem to able to find > qpid-config. In what release/download is that found? > > > From: Timothy Bish [tabish...@gmail.com] > Sent: Friday, February 19, 2016 2:41 PM > To: proton@qpid.apache.org > Subject: Re: Help?!: Qpid JMS 0.6.0 HelloWorld example issue > > On 02/19/2016 12:39 PM, Flores, Paul A. wrote: >> Trying to get the HelloWorld example that is found with the QPID JMS 0.6.0 >> Release to work. >> >> >> >> When I go to run it I am seeing the following. >> >> >> >> Can some one point me to a resolution? I am running out of hair to pull! >> > > Try changing you URI in the jndi.properties to 'amqp://localhost:5672' > not the 'amqp' is not capitalized. > >> >> Thanks. >> >> >> >> Paul >> >> >> >> 2016-02-19 10:32:47,256 [main ] - ERROR ProviderFactory >> - Failed to create Provider instance for AMQP, due to: >> java.io.IOException: Provider scheme NOT recognized: [AMQP] >> 2016-02-19 10:32:47,259 [main ] - ERROR JmsConnectionFactory >> - Failed to create JMS Provider instance for: AMQP >> Caught exception, exiting. >> javax.jms.JMSException: Failed to create connection to: AMQP://localhost:5672 >> at >> org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:66) >> at >> org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:165) >> at HelloWorld.main(HelloWorld.java:51) >> Caused by: java.io.IOException: Provider scheme NOT recognized: [AMQP] >> at >> org.apache.qpid.jms.provider.ProviderFactory.findProviderFactory(ProviderFactory.java:104) >> at >> org.apache.qpid.jms.provider.ProviderFactory.create(ProviderFactory.java:70) >> at >> org.apache.qpid.jms.JmsConnectionFactory.createProvider(JmsConnectionFactory.java:221) >> at >> org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:161) >> ... 1 more >> Caused by: org.apache.qpid.jms.util.ResourceNotFoundException: Could not >> find factory resource: META-INF/services/org/apache/qpid/jms/provider/AMQP >> at >> org.apache.qpid.jms.util.FactoryFinder$StandaloneObjectFactory.loadProperties(FactoryFinder.java:223) >> at >> org.apache.qpid.jms.util.FactoryFinder$StandaloneObjectFactory.create(FactoryFinder.java:164) >> at >> org.apache.qpid.jms.util.FactoryFinder.newInstance(FactoryFinder.java:122) >> at >> org.apache.qpid.jms.provider.ProviderFactory.findProviderFactory(ProviderFactory.java:102) >> ... 4 more >> > > > -- > Tim Bish > twitter: @tabish121 > blog: http://timbish.blogspot.com/
[GitHub] qpid-proton pull request: PROTON-1139 tx_recv_interactive.py examp...
Github user asfgit closed the pull request at: https://github.com/apache/qpid-proton/pull/67 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] qpid-proton pull request: PROTON-1139 tx_recv_interactive.py examp...
Github user grs commented on the pull request: https://github.com/apache/qpid-proton/pull/67#issuecomment-186430276 Thanks Jakub! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (PROTON-1139) tx_recv_interactive.py example doesn't work
[ https://issues.apache.org/jira/browse/PROTON-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154970#comment-15154970 ] ASF subversion and git services commented on PROTON-1139: - Commit 55d9f82fea5e55ce986d570f50258a0dc41e in qpid-proton's branch refs/heads/master from [~scholzj] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=55d9f82 ] PROTON-1139 using selectable() instead of get_event_trigger() > tx_recv_interactive.py example doesn't work > --- > > Key: PROTON-1139 > URL: https://issues.apache.org/jira/browse/PROTON-1139 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.12.0 >Reporter: Jakub Scholz >Priority: Minor > > It looks like the tx_recv_interactive.py example doesn't work anymore, > because the get_event_trigger method no longer exists. > $ ./tx_recv_interactive.py > Traceback (most recent call last): > File "./tx_recv_interactive.py", line 70, in > events = reactor.get_event_trigger() > File "/usr/lib64/python2.7/site-packages/proton/wrapper.py", line 69, in > __getattr__ > raise AttributeError(name + " not in _attrs") > AttributeError: get_event_trigger not in _attrs > It looks like it should be replaced by the selectable method and > EventInjector object. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-1139) tx_recv_interactive.py example doesn't work
[ https://issues.apache.org/jira/browse/PROTON-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154971#comment-15154971 ] ASF GitHub Bot commented on PROTON-1139: Github user asfgit closed the pull request at: https://github.com/apache/qpid-proton/pull/67 > tx_recv_interactive.py example doesn't work > --- > > Key: PROTON-1139 > URL: https://issues.apache.org/jira/browse/PROTON-1139 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.12.0 >Reporter: Jakub Scholz >Priority: Minor > > It looks like the tx_recv_interactive.py example doesn't work anymore, > because the get_event_trigger method no longer exists. > $ ./tx_recv_interactive.py > Traceback (most recent call last): > File "./tx_recv_interactive.py", line 70, in > events = reactor.get_event_trigger() > File "/usr/lib64/python2.7/site-packages/proton/wrapper.py", line 69, in > __getattr__ > raise AttributeError(name + " not in _attrs") > AttributeError: get_event_trigger not in _attrs > It looks like it should be replaced by the selectable method and > EventInjector object. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-1139) tx_recv_interactive.py example doesn't work
[ https://issues.apache.org/jira/browse/PROTON-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154972#comment-15154972 ] ASF GitHub Bot commented on PROTON-1139: Github user grs commented on the pull request: https://github.com/apache/qpid-proton/pull/67#issuecomment-186430276 Thanks Jakub! > tx_recv_interactive.py example doesn't work > --- > > Key: PROTON-1139 > URL: https://issues.apache.org/jira/browse/PROTON-1139 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.12.0 >Reporter: Jakub Scholz >Priority: Minor > > It looks like the tx_recv_interactive.py example doesn't work anymore, > because the get_event_trigger method no longer exists. > $ ./tx_recv_interactive.py > Traceback (most recent call last): > File "./tx_recv_interactive.py", line 70, in > events = reactor.get_event_trigger() > File "/usr/lib64/python2.7/site-packages/proton/wrapper.py", line 69, in > __getattr__ > raise AttributeError(name + " not in _attrs") > AttributeError: get_event_trigger not in _attrs > It looks like it should be replaced by the selectable method and > EventInjector object. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
