Re: [Qpid Dispatcher] Runtime behavior on SunOS

[Ted Ross]

On 04/14/2016 01:57 PM, Adel Boutros wrote:

Hello,
We are trying to use qpid-dispatch on SunOS. Before I ask specific questions, I would 
like to know why in the readme, it is mentioned "Dispatch will not build on 
Windows"? Does it imply that the API was built for a pure Linux-oriented OS and thus 
it is expected to have issues on other OSes such as SunOS?


Dispatch, like other Qpid projects, has an abstraction layer over the 
Operating System for locks, conditions, and threads.  It also has an IO 
driver that is OS-specific.  There's no reason why it can't run on 
Windows, SunOS, Solaris, or any other OS.  Nobody has as yet implemented 
the abstractions and IO driver for anything other than Linux.



In our case, after some modifications, we were able to compile it on SunOS but 
the tests are failing.
Actually, we believe to have hit a problem which has to do with the 
multi-threading and locking mechanism in the dispatcher. We are unable to get 
the dispatcher ready to receive connections in the tests.


Have you tried setting the workerThreads to 1 in the configuration? 
This might provide some insight into threading and locking issues.


-Ted


Regards,Adel Boutroswww.murex.com   



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

Re: [VOTE] Release Qpid Proton 0.12.2

[Timothy Bish]

On 04/14/2016 01:28 PM, Robbie Gemmell wrote:

Hi all,

I have put up an RC for 0.12.2, please test it and vote accordingly.

The source release archive and sig/checksums can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.12.2-rc1/

Maven artifacts for the Java bits can be found in a temporary staging repo at:
https://repository.apache.org/content/repositories/orgapacheqpid-1072

Other than version updates, there is only 1 changes since 0.12.1:
https://issues.apache.org/jira/browse/PROTON-1171

It was created from commit a9c41ef19664af2f928324024dab345c5958f85a
on the 0.12.x branch, and is tagged as 0.12.2-rc1.

Regards,
Robbie

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

.


+1

* Checked signatures and checksums
* Built using cmake and ran tests
* Built using maven and ran tests
* Built Qpid JMS using the staged bits and ran the tests
* Built ActiveMQ 5 using the staged bits and ran the AMQP tests.

--
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

Proton C++ API update

[Justin Ross]

Hi, everyone.  Our work on the Proton C++ API has progressed quite a bit,
and it's time to talk about the changes.

First, a confession.  I described the API we delivered in 0.12.0 as
"substantially settled", excepting some of the extension APIs and those API
elements that were hidden in the API docs.

Our work since then has now exceeded what one can reasonably allow inside
the confines of "substantially settled".  I'll try to detail the changes
and their rationales.  After that I'll talk about our plan moving forward.

There have also been many additions that do not affect API compatibility.
I won't list all of those here, but you can explore them on the API spec.

http://home.apache.org/~jross/pumpjack/index.html

Before I enumerate the changes, however, I'd like to say that we really
very much appreciate the use and feedback we've received on the API so
far.  It is absolutely invaluable, we're grateful, and we want more.

## Event handling

http://home.apache.org/~jross/pumpjack/core/handler/index.html

 - Handler callback signatures
   - The handler callbacks now take relevant objects as inputs
   - We removed event (the arg and the API type)
   - In each callback, the first input argument is an entry-point into the
endpoint object tree and can be used for navigation to parent objects such
as container
 - We renamed on-start and on-stop to on-container-start and
on-container-stop; these now take container
 - We removed on-unhandled
 - We renamed on-unhandled-error to simply on-error

You can see the effect on the examples here:

https://github.com/apache/qpid-proton/blob/master/examples/cpp/helloworld.cpp
https://github.com/apache/qpid-proton/tree/master/examples/cpp

## Message

http://home.apache.org/~jross/pumpjack/core/message/index.html

 - We renamed "address" to "to", retaining "address" as an alias; "to"
matches the AMQP spec and better illustrates the relation to "reply-to"
 - We renamed application-properties to properties; "properties" is used in
the sense of application-supplied properties throughout the API

## Sender and receiver instead of link

http://home.apache.org/~jross/pumpjack/core/sender/index.html
http://home.apache.org/~jross/pumpjack/core/receiver/index.html

 - We previously offered properties and methods on link that were useful
only if the link was a receiver or vice versa; instead we now provide only
the relevant members on sender and receiver respectively
 - This is reflected in the event handlers as well: there are now dedicated
handler methods for senders versus receivers
 - Sender and receiver options are split accordingly

## Source and target instead of terminus

http://home.apache.org/~jross/pumpjack/core/source/index.html
http://home.apache.org/~jross/pumpjack/core/target/index.html

 - Same story as sender and receiver; source and target now contain no
context-dependent members
 - Source and target options are split accordingly

## Tracker and delivery^r instead of delivery

http://home.apache.org/~jross/pumpjack/core/tracker/index.html
http://home.apache.org/~jross/pumpjack/core/delivery/index.html

 - Delivery was previously used for both the sending and receiving sides of
a transfer; it is now separated for the same reasons as sender and
receiver, source and target
 - A tracker is associated with sending: it tracks a message transfer from
the sender's perspective
 - A delivery (in the revised sense) is a message transfer being received

## Flow control

http://home.apache.org/~jross/pumpjack/core/receiver/index.html#flow-control

 - We now use API names that speak in terms of credit: receiver.credit,
receiver.add-credit, sender.credit, receiver-options.credit-window

## Endpoint properties and methods

http://home.apache.org/~jross/pumpjack/core/connection/index.html#endpoint-lifecycle

 - We introduced boolean properties for endpoint states instead of the
endpoint.state bit field
 - Endpoint.close takes an optional error-condition

## Endpoint options

http://home.apache.org/~jross/pumpjack/core/connection-options/index.html
http://home.apache.org/~jross/pumpjack/core/session-options/index.html
http://home.apache.org/~jross/pumpjack/core/sender-options/index.html
http://home.apache.org/~jross/pumpjack/core/receiver-options/index.html

 - Connection.virtual-host instead of host, to clarify its purpose versus
the host info supplied in URLs
 - Connection.max-sessions instead of max-channels, in order to speak in
user terms, not AMQP spec terms
 - Added session-options
 - Some 0.12.0 link options will be removed until their status is decided

## Data types

http://home.apache.org/~jross/pumpjack/types/index.html

 - We have dropped the "amqp-" prefixes from type names; if a
language-provided type fits the need, we use that; if the language doesn't
offer one, we can introduce the type without any concern about collisions
 - We will use string, not the URL class, as the first-class representation
of a URL in API signatures; we will continue to use the URL class 

[Qpid Dispatcher] Runtime behavior on SunOS

[Adel Boutros]

Hello,
We are trying to use qpid-dispatch on SunOS. Before I ask specific questions, I 
would like to know why in the readme, it is mentioned "Dispatch will not build 
on Windows"? Does it imply that the API was built for a pure Linux-oriented OS 
and thus it is expected to have issues on other OSes such as SunOS?
In our case, after some modifications, we were able to compile it on SunOS but 
the tests are failing.
Actually, we believe to have hit a problem which has to do with the 
multi-threading and locking mechanism in the dispatcher. We are unable to get 
the dispatcher ready to receive connections in the tests.
Regards,Adel Boutroswww.murex.com 

Re: [VOTE] Release Qpid Proton 0.12.2

[Robbie Gemmell]

On 14 April 2016 at 18:28, Robbie Gemmell  wrote:
> Hi all,
>
> I have put up an RC for 0.12.2, please test it and vote accordingly.
>
> The source release archive and sig/checksums can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.12.2-rc1/
>
> Maven artifacts for the Java bits can be found in a temporary staging repo at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1072
>
> Other than version updates, there is only 1 changes since 0.12.1:
> https://issues.apache.org/jira/browse/PROTON-1171
>
> It was created from commit a9c41ef19664af2f928324024dab345c5958f85a
> on the 0.12.x branch, and is tagged as 0.12.2-rc1.
>
> Regards,
> Robbie

Making my +1 explicit.

I tested as follows:
- Verified the signature+checksums.
- Ran the CMake build+tests.
- Ran the Maven build+tests.
- Ran the Qpid JMS master build against it using the maven staging repo.
- Diffed against the 0.12.1 source release to verify only the expected
  changes + versions updates.

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

[VOTE] Release Qpid Proton 0.12.2

[Robbie Gemmell]

Hi all,

I have put up an RC for 0.12.2, please test it and vote accordingly.

The source release archive and sig/checksums can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton/0.12.2-rc1/

Maven artifacts for the Java bits can be found in a temporary staging repo at:
https://repository.apache.org/content/repositories/orgapacheqpid-1072

Other than version updates, there is only 1 changes since 0.12.1:
https://issues.apache.org/jira/browse/PROTON-1171

It was created from commit a9c41ef19664af2f928324024dab345c5958f85a
on the 0.12.x branch, and is tagged as 0.12.2-rc1.

Regards,
Robbie

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

Apache Qpid Dispatch Router 0.6.0 Beta now available (update 2)

[Ted Ross]

The first beta update release (beta2) of Apache Qpid Dispatch Router 
0.6.0 is available for testing.  You can find the files here:


https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.6.0-beta2/

This update includes the fixes to 12 issues that were discovered during 
testing of the beta1 release.  Please see the wiki page below for a list 
of resolved issues.


https://cwiki.apache.org/confluence/display/qpid/What%27s+New+in+Apache+Qpid+Dispatch+Router+0.6.0

Regards,

-Ted


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

Re: [VOTE] Release Qpid Java 6.0.2 (RC1)

[Robbie Gemmell]

No need for a respin. I'm just proposing deletion of some redundant
artifacts that were presumably just pulled from repository.apache.org
with the others after being auto-generated.

Robbie

On 14 April 2016 at 14:20, Jakub Scholz  wrote:
> I'm not sure whether we need RC2 and new vote to address Robbie's comment.
> But I the tested the new release, especially with focus on the AMQP 0-10
> client and all works well.
>
> +1
>
> On Wed, Apr 13, 2016 at 4:29 PM, Robbie Gemmell 
> wrote:
>
>> On 13 April 2016 at 14:04, Keith W  wrote:
>> > Hi all,
>> >
>> > A release candidate for the next release (6.0.2) of the Qpid Java
>> > Components has been created.
>> >
>> > The list of changes can be found in Jira:
>> >
>> >
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20QPID%20AND%20fixVersion%20%3D%20qpid-java-6.0.2
>> >
>> > Please test and vote accordingly.
>> >
>> > The source and binary archives can be grabbed from here:
>> > https://dist.apache.org/repos/dist/dev/qpid/java/6.0.2-rc1
>> >
>> > Those files and the other maven artifacts are also staged for now at:
>> > https://repository.apache.org/content/repositories/orgapacheqpid-1071
>> >
>> > Kind regards
>> >
>> > 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-1071
>> 
>> > 
>> >   
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> > For additional commands, e-mail: users-h...@qpid.apache.org
>> >
>>
>> As a first quick look comment, can we remove all the *.asc.md5 and
>> *.asc.sha1 files (which Nexus created) from the dist repo? They are
>> rather redundant and really just clutter things up, plus we probably
>> wont ever link to them.
>>
>> Robbie
>>
>> -
>> 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

Re: [VOTE] Release Qpid Java 6.0.2 (RC1)

[Jakub Scholz]

I'm not sure whether we need RC2 and new vote to address Robbie's comment.
But I the tested the new release, especially with focus on the AMQP 0-10
client and all works well.

+1

On Wed, Apr 13, 2016 at 4:29 PM, Robbie Gemmell 
wrote:

> On 13 April 2016 at 14:04, Keith W  wrote:
> > Hi all,
> >
> > A release candidate for the next release (6.0.2) of the Qpid Java
> > Components has been created.
> >
> > The list of changes can be found in Jira:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20QPID%20AND%20fixVersion%20%3D%20qpid-java-6.0.2
> >
> > Please test and vote accordingly.
> >
> > The source and binary archives can be grabbed from here:
> > https://dist.apache.org/repos/dist/dev/qpid/java/6.0.2-rc1
> >
> > Those files and the other maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1071
> >
> > Kind regards
> >
> > 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-1071
> 
> > 
> >   
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
>
> As a first quick look comment, can we remove all the *.asc.md5 and
> *.asc.sha1 files (which Nexus created) from the dist repo? They are
> rather redundant and really just clutter things up, plus we probably
> wont ever link to them.
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>