Re: Issue building qpid-proton on Fedora

[Gregor Berginc]

Hi Nandan,

I haven’t tried this but a colleague of mine has updated RPM spec for 
qpid-proton 0.19. You should be able to use it to install system package on 
Fedora:

https://copr.fedorainfracloud.org/coprs/tadeboro/qpid-proton/

Note that this is unofficial until RPM gets updated but you can check the RPM 
spec to be sure that it just bumps the version:

https://github.com/xlab-si/rpm-qpid-proton/commit/dc484f9c18a1c78d620e1173c119414c546e18a9

I guess you can then install Python moudule via pip.

I hope this helps,
-Gregor

> On 19 Jan 2018, at 19:47, nandanone  wrote:
> 
> Andrew::
> 
> I downloaded the 0.19.0 distribution of qpid-proton from the apache site.
> The install instructions talk about building the distribution using
> cmake/make. This is why I was trying to build the distribution (with Perl,
> Ruby, PHP turned off). Is there a way to install the proton module and its
> dependencies without a build? Otherwise when I try to run the examples in
> the Python directory I get errors like
> 
> Traceback (most recent call last):
>  File "simple_send.py", line 23, in 
>from proton import Message
> ImportError: No module named proton
> 
> I have set 
> echo $PYTHONPATH 
> /home/njoshi/Development/community/qpid-proton-0.19.0/
> 
> Thanks,
> 
> Nandan
> 
> 
> 
> 
> 
> 
> 
> --
> Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 

Re: [VOTE] Release Apache Qpid JMS 0.29.0

[Gordon Sim]

On 19/01/18 12:30, Robbie Gemmell wrote:

I have put together a spin for a 0.29.0 Qpid JMS client release,
please give it a test out and vote accordingly.


+1, built from source, including tests, installed binary from tarball 
and tested examples against c++ broker and router.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Issue building qpid-proton on Fedora

[nandanone]

Andrew::

I downloaded the 0.19.0 distribution of qpid-proton from the apache site.
The install instructions talk about building the distribution using
cmake/make. This is why I was trying to build the distribution (with Perl,
Ruby, PHP turned off). Is there a way to install the proton module and its
dependencies without a build? Otherwise when I try to run the examples in
the Python directory I get errors like

Traceback (most recent call last):
  File "simple_send.py", line 23, in 
from proton import Message
ImportError: No module named proton

I have set 
echo $PYTHONPATH 
/home/njoshi/Development/community/qpid-proton-0.19.0/

Thanks,

Nandan







--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 0.29.0

[Timothy Bish]

On 01/19/2018 07:30 AM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a 0.29.0 Qpid JMS client release,
please give it a test out and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.29.0-rc1/

The maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1128

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12342310

Regards,
Robbie

P.S. If you want to test it out using maven (e.g with the examples
src, or your own things), you can temporarily add this to your poms to
access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1128
 
   

The dependency for the client itself would then be:

   
 org.apache.qpid
 qpid-jms-client
 0.29.0
   

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org



+1

* Validated signatures and checksums
* Checked for License and Notice files with updated year, ran mvn 
apache-rat:check

* Built from source and ran the tests
* Built Artemis and ActiveMQ 5.x with staged bits and ran the AMQP tests
* Ran the included example against existing Artemis and ActiveMQ 5.x 
installs



--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 0.29.0

[Robbie Gemmell]

On 19 January 2018 at 12:30, Robbie Gemmell  wrote:
> Hi folks,
>
> I have put together a spin for a 0.29.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.29.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1128
>
> The JIRAs currently assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12342310
>
> Regards,
> Robbie
>
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1128
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 0.29.0
>   

+1

I checked things over as follows:
- Verified the signatures and checksums.
- Checked the LICENCE+NOTICE files in source and bin archives.
- Ran mvn apache-rat:check to verify licence headers in the source archive.
- Ran the source build and tests, all good.
- Built Qpid Broker-J master using staging repo, running the MMS
profile tests, all good.
- Used Qpid Broker-J master to run the joram tests using the staging
repo, all good.
- Used the staging repo with the ActiveMQ 5 + Artemis master builds +
AMQP tests, all good.

Robbie

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

[VOTE] Release Apache Qpid JMS 0.29.0

[Robbie Gemmell]

Hi folks,

I have put together a spin for a 0.29.0 Qpid JMS client release,
please give it a test out and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.29.0-rc1/

The maven artifacts are also staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1128

The JIRAs currently assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12342310

Regards,
Robbie

P.S. If you want to test it out using maven (e.g with the examples
src, or your own things), you can temporarily add this to your poms to
access the staging repo:

  

  staging
  
https://repository.apache.org/content/repositories/orgapacheqpid-1128

  

The dependency for the client itself would then be:

  
org.apache.qpid
qpid-jms-client
0.29.0
  

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Max number of queues per user

[Gordon Sim]

On 19/01/18 12:20, Michael Ivanov wrote:

Is it possible to find out where user/password has to be used instead
of user:password? Proton does not accept the syntax with slash.

Can I assume that '/' is to be used on command line for utilities like
qpid-stat, qpid-config etc and in all other cases delimiter is ':'?


I believe it is actually the qpid.messaging python library that is 
responsible, but assuming you don't care about that, then yes the only 
impact would be on the command line utilities for qpidd.


(The qpid::messaging c++ library will handle both forms).

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Max number of queues per user

[Michael Ivanov]

Thanks for your help.

Is it possible to find out where user/password has to be used instead
of user:password? Proton does not accept the syntax with slash.

Can I assume that '/' is to be used on command line for utilities like
qpid-stat, qpid-config etc and in all other cases delimiter is ':'?

Best regards,

18.01.2018 20:34, Gordon Sim пишет:
> On 18/01/18 15:23, Michael Ivanov wrote:
>> Great, it (almost) works! Many thanks!
>>
>> There's still one problem remains. When I turn auth off, then user is
>> considered to be anonymous, even when I specify user explicitly in broker 
>> url.
> 
> You can force the mechanism with the --sasl-mechanism option to qpid-config. 
> I believe anonymous is preferred to plain by default.
> 
>> When I turn auth on somehow the password is not accepted on command line:
>>
>>     qpid-config -b amqps://user:passwd@hostname:5671 add queue U1
>>
>> The following error occurs:
>>
>>     Failed: ValueError: amqps://user:passwd@hostname:5671
>>
>> When :passwd is not specified I'm prompted for password and everything works.
>> But I need to be able to create queues without manual intervention.
>> Is it possible to accept user name without a password?
> 
> Unfortunately the syntax is non-standard and uses a forward slash to separate 
> user and password rather than a colon as expected:
> e.g. amqps://user/password@hostname
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org