You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Lahiru Gunathilake <gl...@gmail.com> on 2009/11/25 15:22:51 UTC

Like to know the Synapse AMQP trasports status

Hi all,

I like to do some work with synapse AMQP trasport and like to know the
status of the trasport in current synapse code base.

Regards
Lahiru

-- 
Apache Qpid, Worlds dominant messaging middleware..!!!

Re: Like to know the Synapse AMQP trasports status

Posted by Rajith Attapattu <ra...@gmail.com>.
One important point to note is that the new address format I talked
about in Qpid JMS client, will only be implemented in the 0-10 code
path.
It may or may not get implemented in the 0-8/0-9 code path as it may
not have much benefit given that AMQP 1.0 is coming out  sometime next
year.
Therefore you would not have the same features/flexibility I talked
about when running against an 0-8/0-9 broker. Ex RabbitMQ.
But I doubt there is much of an impact for most use cases. At least
not the ones I have seen so far for Synapse.

But once AMQP 1.0 comes out, RabbitMQ and all other vendors will
obviously support 1.0, so this is only a temporary issue.

Rajith

On Thu, Nov 26, 2009 at 2:43 PM, Rajith Attapattu <ra...@gmail.com> wrote:
> On Thu, Nov 26, 2009 at 1:38 PM, Asanka Abeysinghe <as...@wso2.com> wrote:
>> Hi Rajith,
>> Thank you for the detailed explanation, so it seems we don't have any
>> functionality limitations by using JMS to bridge AMQP.
>
> For the most part no. 95% of the use cases could be met with using
> pure JMS interfaces.
> So far most of the client use cases we encountered were able to
> satisfy with the JMS client.
> Anytime we found it difficult, it was more due to the design issues in
> the JMS client than anything else.
> Based on those use cases we kept on improving the JMS client.
> The other clients written in python, c++ (and eventually ruby) are
> also moving towards protocol-version agnostic high level API's.
>
> However due to the limitations of the JMS API there will be use cases
> that may not be able to satisfy effectively.
> For example streaming large messages. (there are ways to get around
> this but may not be as efficient though)
> Also the JMS imposes a certain threading model in the client
> implementation when doing message listeners.
> There maybe use cases where you want a single thread to read from
> subscriptions based on several sessions.
> This is not possible with JMS unless we use receive() where the
> semantics mandate it to be synchronous in nature with certain
> guarantees that makes this method slow.
> The motivation for the said use case is where you have a worker thread
> pool and want to read messages as efficiently as possible from a bunch
> of queues (spread across several sessions) where the number of
> sessions is greater than the number of cores available for the
> process. So having a thread per session may result in a lot of context
> switching.
> But these are specialized use cases. I don't know if Synapse has such
> requirements.
>
>
>> What about performance, do you think it will be same with JMS and a native AMQP java
>> client ?
>
> There was also quite a bit of performance work done in the JMS client
> to the extent the difference btw the JMS layer and lower layer is
> negligible for most real business applications especially within the
> context of something like Synapse. In artificial benchmarks the diff
> is about 10k msg/sec.
>
>> And I like to know the motivation behind on writing the previous native AMQP
>> code we had ? Was it due to limited support JMS on QPid ?
>
> Several reasons.
> The JMS client had a few design issues that prevented it from making
> full use of the protocol.
> For example it wasn't possible to do declare/bind arguments or bind
> the same queue with multiple binding keys.
> Setting flow control or reliability guarantees on a per destination
> basis was also not possible even at present.
> This is being addressed now with the new address format.
> So It took us some time to figure out the best way to allow such
> support while using pure JMS interfaces.
>
> Another reason was performance. At the time the delta btw the native
> and JMS layer was quite a bit.
> But now most of those issues are addressed to an extent that it
> doesn't really matter for most real business applications.
>
> Another reason was that I didn't know better at that time and had the
> same questions that you raised.
> I didn't have reasonable answers to those questions and at times had
> the incorrect assumption that it was due to limitations of the JMS
> API.
> Then we found ways of addressing those concerns properly.
> Now with the benefit of hindsight I realize that most of those
> questions can be answered satisfactorily.
>
> Thanks for all these questions as the discussion will make it clear if
> we would need an AMQP client or not.
> I also urge you to think through the use cases for Synapse (as you
> guys know them best) and see if any of my explanations doesn't fit or
> doesn't answer them completely.
> I think it's a worthwhile experiment to do that. We could also
> document those cases so the end users know how best to leverage AMQP
> support via Synapse.
>
>> Thx
>> Asanka
>>
>> On Thu, Nov 26, 2009 at 9:18 PM, Rajith Attapattu <ra...@gmail.com>
>> wrote:
>>>
>>> On Thu, Nov 26, 2009 at 4:31 AM, Asanka Abeysinghe <as...@wso2.com>
>>> wrote:
>>> > +1 for native AMQP transport,
>>> > By bridging from JMS to AMQP is it possible to get the full advantage of
>>> > AMQP specific features like exchanges, exchange types, routing keys,
>>> > dynamic
>>> > creation of queues etc ... ?
>>>
>>> Again Good question and one for the FAQ.
>>> Even now the JMS client is flexible enough to take full advantage of
>>> exchanges, exchange types, rk's and dynamic creation of queues.
>>> The new addressing format is even more flexible as it permits lot more
>>> options like flow control, reliability expectations, declare and bind
>>> arguments, how and when queues should be created by the client (ex
>>> never - centrally administered, producer-created by producer,
>>> consumer-created by consumer)
>>> (As an aside, it's worth noting that exchanges are not going to be
>>> there in 1.0 )
>>>
>>> If you need to create queues as part of business logic, you could
>>> still use the createQueue()/createTopic() methods and pass in an
>>> address string and get the same benefits mentioned above.
>>> As I mentioned in my first email, one important development in AMQP
>>> 1.0 is that management commands such as declare, bind , query queues
>>> etc... are not part of the core protocol, but rather sent as messages
>>> over the transport to a known admin/mgt service. The Qpid project's
>>> QMF framework is aiming to follow that direction even from 0-10 by
>>> allowing to perform management functions using pure message passing
>>> (ex using Map messages)
>>>
>>> Does this sufficiently answer your all your questions?
>>> If not please feel free to dig further and I am happy to answer any
>>> questions you have.
>>>
>>> If you have specific use cases that would also help, as sometimes
>>> discussing in abstract form is a bit difficult.
>>>
>>> Regards,
>>>
>>> Rajith
>>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Re: Like to know the Synapse AMQP trasports status

Posted by Rajith Attapattu <ra...@gmail.com>.
On Thu, Nov 26, 2009 at 1:38 PM, Asanka Abeysinghe <as...@wso2.com> wrote:
> Hi Rajith,
> Thank you for the detailed explanation, so it seems we don't have any
> functionality limitations by using JMS to bridge AMQP.

For the most part no. 95% of the use cases could be met with using
pure JMS interfaces.
So far most of the client use cases we encountered were able to
satisfy with the JMS client.
Anytime we found it difficult, it was more due to the design issues in
the JMS client than anything else.
Based on those use cases we kept on improving the JMS client.
The other clients written in python, c++ (and eventually ruby) are
also moving towards protocol-version agnostic high level API's.

However due to the limitations of the JMS API there will be use cases
that may not be able to satisfy effectively.
For example streaming large messages. (there are ways to get around
this but may not be as efficient though)
Also the JMS imposes a certain threading model in the client
implementation when doing message listeners.
There maybe use cases where you want a single thread to read from
subscriptions based on several sessions.
This is not possible with JMS unless we use receive() where the
semantics mandate it to be synchronous in nature with certain
guarantees that makes this method slow.
The motivation for the said use case is where you have a worker thread
pool and want to read messages as efficiently as possible from a bunch
of queues (spread across several sessions) where the number of
sessions is greater than the number of cores available for the
process. So having a thread per session may result in a lot of context
switching.
But these are specialized use cases. I don't know if Synapse has such
requirements.


> What about performance, do you think it will be same with JMS and a native AMQP java
> client ?

There was also quite a bit of performance work done in the JMS client
to the extent the difference btw the JMS layer and lower layer is
negligible for most real business applications especially within the
context of something like Synapse. In artificial benchmarks the diff
is about 10k msg/sec.

> And I like to know the motivation behind on writing the previous native AMQP
> code we had ? Was it due to limited support JMS on QPid ?

Several reasons.
The JMS client had a few design issues that prevented it from making
full use of the protocol.
For example it wasn't possible to do declare/bind arguments or bind
the same queue with multiple binding keys.
Setting flow control or reliability guarantees on a per destination
basis was also not possible even at present.
This is being addressed now with the new address format.
So It took us some time to figure out the best way to allow such
support while using pure JMS interfaces.

Another reason was performance. At the time the delta btw the native
and JMS layer was quite a bit.
But now most of those issues are addressed to an extent that it
doesn't really matter for most real business applications.

Another reason was that I didn't know better at that time and had the
same questions that you raised.
I didn't have reasonable answers to those questions and at times had
the incorrect assumption that it was due to limitations of the JMS
API.
Then we found ways of addressing those concerns properly.
Now with the benefit of hindsight I realize that most of those
questions can be answered satisfactorily.

Thanks for all these questions as the discussion will make it clear if
we would need an AMQP client or not.
I also urge you to think through the use cases for Synapse (as you
guys know them best) and see if any of my explanations doesn't fit or
doesn't answer them completely.
I think it's a worthwhile experiment to do that. We could also
document those cases so the end users know how best to leverage AMQP
support via Synapse.

> Thx
> Asanka
>
> On Thu, Nov 26, 2009 at 9:18 PM, Rajith Attapattu <ra...@gmail.com>
> wrote:
>>
>> On Thu, Nov 26, 2009 at 4:31 AM, Asanka Abeysinghe <as...@wso2.com>
>> wrote:
>> > +1 for native AMQP transport,
>> > By bridging from JMS to AMQP is it possible to get the full advantage of
>> > AMQP specific features like exchanges, exchange types, routing keys,
>> > dynamic
>> > creation of queues etc ... ?
>>
>> Again Good question and one for the FAQ.
>> Even now the JMS client is flexible enough to take full advantage of
>> exchanges, exchange types, rk's and dynamic creation of queues.
>> The new addressing format is even more flexible as it permits lot more
>> options like flow control, reliability expectations, declare and bind
>> arguments, how and when queues should be created by the client (ex
>> never - centrally administered, producer-created by producer,
>> consumer-created by consumer)
>> (As an aside, it's worth noting that exchanges are not going to be
>> there in 1.0 )
>>
>> If you need to create queues as part of business logic, you could
>> still use the createQueue()/createTopic() methods and pass in an
>> address string and get the same benefits mentioned above.
>> As I mentioned in my first email, one important development in AMQP
>> 1.0 is that management commands such as declare, bind , query queues
>> etc... are not part of the core protocol, but rather sent as messages
>> over the transport to a known admin/mgt service. The Qpid project's
>> QMF framework is aiming to follow that direction even from 0-10 by
>> allowing to perform management functions using pure message passing
>> (ex using Map messages)
>>
>> Does this sufficiently answer your all your questions?
>> If not please feel free to dig further and I am happy to answer any
>> questions you have.
>>
>> If you have specific use cases that would also help, as sometimes
>> discussing in abstract form is a bit difficult.
>>
>> Regards,
>>
>> Rajith
>>
>> > - Asanka
>> >
>> > On Thu, Nov 26, 2009 at 10:34 AM, Ruwan Linton <ru...@gmail.com>
>> > wrote:
>> >>
>> >> +1 for developing a native AMQP transport.
>> >>
>> >> Thanks,
>> >> Ruwan
>> >>
>> >> On Thu, Nov 26, 2009 at 9:52 AM, Hiranya Jayathilaka
>> >> <hi...@gmail.com> wrote:
>> >>>
>> >>> Well personally I like the idea of Synapse having a native AMQP
>> >>> implementation rather than having to access AMQP queues over JMS. Some
>> >>> of
>> >>> the prominent AMQP providers like RabbitMQ does not provide JMS and
>> >>> JNDI
>> >>> support at a satisfactory level. IMHO it is totally worth having this
>> >>> transport - as an optional one of course.
>> >>>
>> >>> Thanks,
>> >>> Hiranya
>> >>>
>> >>> On Wed, Nov 25, 2009 at 11:14 PM, Rajith Attapattu
>> >>> <ra...@gmail.com>
>> >>> wrote:
>> >>>>
>> >>>> Hi Lahiru,
>> >>>>
>> >>>> I am afraid it's in an unusable state atm mainly due to my fault.
>> >>>> I would also like to take this opportunity to discuss the continuity
>> >>>> of the amqp transport.
>> >>>>
>> >>>> The motivation behind creating an AMQP specific transport instead of
>> >>>> using it via the JMS transport was due to the perceived flexibility &
>> >>>> performance achieved via a transport that is close to the protocol.
>> >>>>
>> >>>> However as Qpid gained more experience and myself having the
>> >>>> privilege
>> >>>> of working with customers and end users realized that the JMS
>> >>>> implementation is lacking this flexibility more due to design issues
>> >>>> than any real issue with the API itself. Over the last year or so we
>> >>>> made significant improvements to the JMS client.
>> >>>> The new address format that will be used by all the Qpid clients
>> >>>> including JMS will be rich enough to tune protocol specifics via the
>> >>>> javax.jms.Destination abstraction while allowing applications to use
>> >>>> pure JMS without having to resort to a vendor specific low level API.
>> >>>> Going forward management aspects such as having to create
>> >>>> queues/exchanges dynamically could be done by sending a map message
>> >>>> than invoking a protocol command. Infact in AMQP 1.0 management/admin
>> >>>> work such as declaring queues are not protocol specific commands any
>> >>>> more. They are achieved via sending messages to a known admin/mgt
>> >>>> service within a container.
>> >>>>
>> >>>> There was also quite a bit of performance work done in the JMS client
>> >>>> to the extent the difference btw the JMS layer and lower layer is
>> >>>> negligible for a real business application especially within the
>> >>>> context of Synapse. In artificial benchmarks the diff is about 10k
>> >>>> msg/sec.
>> >>>>
>> >>>> Therefore with the benefit of hindsight I feel that having an AMQP
>> >>>> specific transport doesn't add anything significant over the well
>> >>>> tested JMS transport that Synapse has.
>> >>>> However before coming to a conclusion, it would be worthwhile to
>> >>>> figure out all the use cases around AMQP with Synapse.
>> >>>> Then we could document how they could be achieved via the JMS
>> >>>> transport.
>> >>>> If there are any use cases that cannot be reasonably met, then
>> >>>> perhaps
>> >>>> we could discuss about an AMQP specific transport.
>> >>>>
>> >>>> Regards,
>> >>>>
>> >>>> Rajith
>> >>>>
>> >>>> On Wed, Nov 25, 2009 at 9:22 AM, Lahiru Gunathilake
>> >>>> <gl...@gmail.com>
>> >>>> wrote:
>> >>>> > Hi all,
>> >>>> >
>> >>>> > I like to do some work with synapse AMQP trasport and like to know
>> >>>> > the
>> >>>> > status of the trasport in current synapse code base.
>> >>>> >
>> >>>> > Regards
>> >>>> > Lahiru
>> >>>> >
>> >>>> > --
>> >>>> > Apache Qpid, Worlds dominant messaging middleware..!!!
>> >>>> >
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Regards,
>> >>>>
>> >>>> Rajith Attapattu
>> >>>> Red Hat
>> >>>> http://rajith.2rlabs.com/
>> >>>>
>> >>>> ---------------------------------------------------------------------
>> >>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> >>>> For additional commands, e-mail: dev-help@synapse.apache.org
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Hiranya Jayathilaka
>> >>> Software Engineer;
>> >>> WSO2 Inc.;  http://wso2.org
>> >>> E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
>> >>> Blog: http://techfeast-hiranya.blogspot.com
>> >>
>> >>
>> >>
>> >> --
>> >> Ruwan Linton
>> >> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>> >> WSO2 Inc.; http://wso2.org
>> >> email: ruwan@wso2.com; cell: +94 77 341 3097
>> >> blog: http://ruwansblog.blogspot.com
>> >
>> >
>> >
>> > --
>> > Asanka Abeysinghe
>> > Architect - WSO2, Inc.
>> > m: +94 77 7340064      p: +94 11 2688451/3
>> > e: asankaa@wso2.com w: http://www.wso2.com
>> > b: http://www.asankama.com
>> >
>>
>>
>>
>> --
>> Regards,
>>
>> Rajith Attapattu
>> Red Hat
>> http://rajith.2rlabs.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>
>
>
> --
> Asanka Abeysinghe
> Architect - WSO2, Inc.
> m: +94 77 7340064      p: +94 11 2688451/3
> e: asankaa@wso2.com w: http://www.wso2.com
> b: http://www.asankama.com
>



-- 
Regards,

Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Re: Like to know the Synapse AMQP trasports status

Posted by Asanka Abeysinghe <as...@wso2.com>.
Hi Rajith,
Thank you for the detailed explanation, so it seems we don't have any
functionality limitations by using JMS to bridge AMQP. What about
performance, do you think it will be same with JMS and a native AMQP java
client ?
And I like to know the motivation behind on writing the previous native AMQP
code we had ? Was it due to limited support JMS on QPid ?
Thx
Asanka

On Thu, Nov 26, 2009 at 9:18 PM, Rajith Attapattu <ra...@gmail.com>wrote:

> On Thu, Nov 26, 2009 at 4:31 AM, Asanka Abeysinghe <as...@wso2.com>
> wrote:
> > +1 for native AMQP transport,
> > By bridging from JMS to AMQP is it possible to get the full advantage of
> > AMQP specific features like exchanges, exchange types, routing keys,
> dynamic
> > creation of queues etc ... ?
>
> Again Good question and one for the FAQ.
> Even now the JMS client is flexible enough to take full advantage of
> exchanges, exchange types, rk's and dynamic creation of queues.
> The new addressing format is even more flexible as it permits lot more
> options like flow control, reliability expectations, declare and bind
> arguments, how and when queues should be created by the client (ex
> never - centrally administered, producer-created by producer,
> consumer-created by consumer)
> (As an aside, it's worth noting that exchanges are not going to be
> there in 1.0 )
>
> If you need to create queues as part of business logic, you could
> still use the createQueue()/createTopic() methods and pass in an
> address string and get the same benefits mentioned above.
> As I mentioned in my first email, one important development in AMQP
> 1.0 is that management commands such as declare, bind , query queues
> etc... are not part of the core protocol, but rather sent as messages
> over the transport to a known admin/mgt service. The Qpid project's
> QMF framework is aiming to follow that direction even from 0-10 by
> allowing to perform management functions using pure message passing
> (ex using Map messages)
>
> Does this sufficiently answer your all your questions?
> If not please feel free to dig further and I am happy to answer any
> questions you have.
>
> If you have specific use cases that would also help, as sometimes
> discussing in abstract form is a bit difficult.
>
> Regards,
>
> Rajith
>
> > - Asanka
> >
> > On Thu, Nov 26, 2009 at 10:34 AM, Ruwan Linton <ru...@gmail.com>
> > wrote:
> >>
> >> +1 for developing a native AMQP transport.
> >>
> >> Thanks,
> >> Ruwan
> >>
> >> On Thu, Nov 26, 2009 at 9:52 AM, Hiranya Jayathilaka
> >> <hi...@gmail.com> wrote:
> >>>
> >>> Well personally I like the idea of Synapse having a native AMQP
> >>> implementation rather than having to access AMQP queues over JMS. Some
> of
> >>> the prominent AMQP providers like RabbitMQ does not provide JMS and
> JNDI
> >>> support at a satisfactory level. IMHO it is totally worth having this
> >>> transport - as an optional one of course.
> >>>
> >>> Thanks,
> >>> Hiranya
> >>>
> >>> On Wed, Nov 25, 2009 at 11:14 PM, Rajith Attapattu <rajith77@gmail.com
> >
> >>> wrote:
> >>>>
> >>>> Hi Lahiru,
> >>>>
> >>>> I am afraid it's in an unusable state atm mainly due to my fault.
> >>>> I would also like to take this opportunity to discuss the continuity
> >>>> of the amqp transport.
> >>>>
> >>>> The motivation behind creating an AMQP specific transport instead of
> >>>> using it via the JMS transport was due to the perceived flexibility &
> >>>> performance achieved via a transport that is close to the protocol.
> >>>>
> >>>> However as Qpid gained more experience and myself having the privilege
> >>>> of working with customers and end users realized that the JMS
> >>>> implementation is lacking this flexibility more due to design issues
> >>>> than any real issue with the API itself. Over the last year or so we
> >>>> made significant improvements to the JMS client.
> >>>> The new address format that will be used by all the Qpid clients
> >>>> including JMS will be rich enough to tune protocol specifics via the
> >>>> javax.jms.Destination abstraction while allowing applications to use
> >>>> pure JMS without having to resort to a vendor specific low level API.
> >>>> Going forward management aspects such as having to create
> >>>> queues/exchanges dynamically could be done by sending a map message
> >>>> than invoking a protocol command. Infact in AMQP 1.0 management/admin
> >>>> work such as declaring queues are not protocol specific commands any
> >>>> more. They are achieved via sending messages to a known admin/mgt
> >>>> service within a container.
> >>>>
> >>>> There was also quite a bit of performance work done in the JMS client
> >>>> to the extent the difference btw the JMS layer and lower layer is
> >>>> negligible for a real business application especially within the
> >>>> context of Synapse. In artificial benchmarks the diff is about 10k
> >>>> msg/sec.
> >>>>
> >>>> Therefore with the benefit of hindsight I feel that having an AMQP
> >>>> specific transport doesn't add anything significant over the well
> >>>> tested JMS transport that Synapse has.
> >>>> However before coming to a conclusion, it would be worthwhile to
> >>>> figure out all the use cases around AMQP with Synapse.
> >>>> Then we could document how they could be achieved via the JMS
> transport.
> >>>> If there are any use cases that cannot be reasonably met, then perhaps
> >>>> we could discuss about an AMQP specific transport.
> >>>>
> >>>> Regards,
> >>>>
> >>>> Rajith
> >>>>
> >>>> On Wed, Nov 25, 2009 at 9:22 AM, Lahiru Gunathilake <
> glahiru@gmail.com>
> >>>> wrote:
> >>>> > Hi all,
> >>>> >
> >>>> > I like to do some work with synapse AMQP trasport and like to know
> the
> >>>> > status of the trasport in current synapse code base.
> >>>> >
> >>>> > Regards
> >>>> > Lahiru
> >>>> >
> >>>> > --
> >>>> > Apache Qpid, Worlds dominant messaging middleware..!!!
> >>>> >
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Regards,
> >>>>
> >>>> Rajith Attapattu
> >>>> Red Hat
> >>>> http://rajith.2rlabs.com/
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> >>>> For additional commands, e-mail: dev-help@synapse.apache.org
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Hiranya Jayathilaka
> >>> Software Engineer;
> >>> WSO2 Inc.;  http://wso2.org
> >>> E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
> >>> Blog: http://techfeast-hiranya.blogspot.com
> >>
> >>
> >>
> >> --
> >> Ruwan Linton
> >> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> >> WSO2 Inc.; http://wso2.org
> >> email: ruwan@wso2.com; cell: +94 77 341 3097
> >> blog: http://ruwansblog.blogspot.com
> >
> >
> >
> > --
> > Asanka Abeysinghe
> > Architect - WSO2, Inc.
> > m: +94 77 7340064      p: +94 11 2688451/3
> > e: asankaa@wso2.com w: http://www.wso2.com
> > b: http://www.asankama.com
> >
>
>
>
> --
> Regards,
>
> Rajith Attapattu
> Red Hat
> http://rajith.2rlabs.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>


-- 
Asanka Abeysinghe
Architect - WSO2, Inc.
m: +94 77 7340064      p: +94 11 2688451/3
e: asankaa@wso2.com w: http://www.wso2.com
b: http://www.asankama.com

Re: Like to know the Synapse AMQP trasports status

Posted by Rajith Attapattu <ra...@gmail.com>.
On Thu, Nov 26, 2009 at 4:31 AM, Asanka Abeysinghe <as...@wso2.com> wrote:
> +1 for native AMQP transport,
> By bridging from JMS to AMQP is it possible to get the full advantage of
> AMQP specific features like exchanges, exchange types, routing keys, dynamic
> creation of queues etc ... ?

Again Good question and one for the FAQ.
Even now the JMS client is flexible enough to take full advantage of
exchanges, exchange types, rk's and dynamic creation of queues.
The new addressing format is even more flexible as it permits lot more
options like flow control, reliability expectations, declare and bind
arguments, how and when queues should be created by the client (ex
never - centrally administered, producer-created by producer,
consumer-created by consumer)
(As an aside, it's worth noting that exchanges are not going to be
there in 1.0 )

If you need to create queues as part of business logic, you could
still use the createQueue()/createTopic() methods and pass in an
address string and get the same benefits mentioned above.
As I mentioned in my first email, one important development in AMQP
1.0 is that management commands such as declare, bind , query queues
etc... are not part of the core protocol, but rather sent as messages
over the transport to a known admin/mgt service. The Qpid project's
QMF framework is aiming to follow that direction even from 0-10 by
allowing to perform management functions using pure message passing
(ex using Map messages)

Does this sufficiently answer your all your questions?
If not please feel free to dig further and I am happy to answer any
questions you have.

If you have specific use cases that would also help, as sometimes
discussing in abstract form is a bit difficult.

Regards,

Rajith

> - Asanka
>
> On Thu, Nov 26, 2009 at 10:34 AM, Ruwan Linton <ru...@gmail.com>
> wrote:
>>
>> +1 for developing a native AMQP transport.
>>
>> Thanks,
>> Ruwan
>>
>> On Thu, Nov 26, 2009 at 9:52 AM, Hiranya Jayathilaka
>> <hi...@gmail.com> wrote:
>>>
>>> Well personally I like the idea of Synapse having a native AMQP
>>> implementation rather than having to access AMQP queues over JMS. Some of
>>> the prominent AMQP providers like RabbitMQ does not provide JMS and JNDI
>>> support at a satisfactory level. IMHO it is totally worth having this
>>> transport - as an optional one of course.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>> On Wed, Nov 25, 2009 at 11:14 PM, Rajith Attapattu <ra...@gmail.com>
>>> wrote:
>>>>
>>>> Hi Lahiru,
>>>>
>>>> I am afraid it's in an unusable state atm mainly due to my fault.
>>>> I would also like to take this opportunity to discuss the continuity
>>>> of the amqp transport.
>>>>
>>>> The motivation behind creating an AMQP specific transport instead of
>>>> using it via the JMS transport was due to the perceived flexibility &
>>>> performance achieved via a transport that is close to the protocol.
>>>>
>>>> However as Qpid gained more experience and myself having the privilege
>>>> of working with customers and end users realized that the JMS
>>>> implementation is lacking this flexibility more due to design issues
>>>> than any real issue with the API itself. Over the last year or so we
>>>> made significant improvements to the JMS client.
>>>> The new address format that will be used by all the Qpid clients
>>>> including JMS will be rich enough to tune protocol specifics via the
>>>> javax.jms.Destination abstraction while allowing applications to use
>>>> pure JMS without having to resort to a vendor specific low level API.
>>>> Going forward management aspects such as having to create
>>>> queues/exchanges dynamically could be done by sending a map message
>>>> than invoking a protocol command. Infact in AMQP 1.0 management/admin
>>>> work such as declaring queues are not protocol specific commands any
>>>> more. They are achieved via sending messages to a known admin/mgt
>>>> service within a container.
>>>>
>>>> There was also quite a bit of performance work done in the JMS client
>>>> to the extent the difference btw the JMS layer and lower layer is
>>>> negligible for a real business application especially within the
>>>> context of Synapse. In artificial benchmarks the diff is about 10k
>>>> msg/sec.
>>>>
>>>> Therefore with the benefit of hindsight I feel that having an AMQP
>>>> specific transport doesn't add anything significant over the well
>>>> tested JMS transport that Synapse has.
>>>> However before coming to a conclusion, it would be worthwhile to
>>>> figure out all the use cases around AMQP with Synapse.
>>>> Then we could document how they could be achieved via the JMS transport.
>>>> If there are any use cases that cannot be reasonably met, then perhaps
>>>> we could discuss about an AMQP specific transport.
>>>>
>>>> Regards,
>>>>
>>>> Rajith
>>>>
>>>> On Wed, Nov 25, 2009 at 9:22 AM, Lahiru Gunathilake <gl...@gmail.com>
>>>> wrote:
>>>> > Hi all,
>>>> >
>>>> > I like to do some work with synapse AMQP trasport and like to know the
>>>> > status of the trasport in current synapse code base.
>>>> >
>>>> > Regards
>>>> > Lahiru
>>>> >
>>>> > --
>>>> > Apache Qpid, Worlds dominant messaging middleware..!!!
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>>
>>>> Rajith Attapattu
>>>> Red Hat
>>>> http://rajith.2rlabs.com/
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>>> For additional commands, e-mail: dev-help@synapse.apache.org
>>>>
>>>
>>>
>>>
>>> --
>>> Hiranya Jayathilaka
>>> Software Engineer;
>>> WSO2 Inc.;  http://wso2.org
>>> E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
>>> Blog: http://techfeast-hiranya.blogspot.com
>>
>>
>>
>> --
>> Ruwan Linton
>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>> WSO2 Inc.; http://wso2.org
>> email: ruwan@wso2.com; cell: +94 77 341 3097
>> blog: http://ruwansblog.blogspot.com
>
>
>
> --
> Asanka Abeysinghe
> Architect - WSO2, Inc.
> m: +94 77 7340064      p: +94 11 2688451/3
> e: asankaa@wso2.com w: http://www.wso2.com
> b: http://www.asankama.com
>



-- 
Regards,

Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Re: Like to know the Synapse AMQP trasports status

Posted by Asanka Abeysinghe <as...@wso2.com>.
+1 for native AMQP transport,
By bridging from JMS to AMQP is it possible to get the full advantage of
AMQP specific features like exchanges, exchange types, routing keys, dynamic
creation of queues etc ... ?
- Asanka

On Thu, Nov 26, 2009 at 10:34 AM, Ruwan Linton <ru...@gmail.com>wrote:

> +1 for developing a native AMQP transport.
>
> Thanks,
> Ruwan
>
>
> On Thu, Nov 26, 2009 at 9:52 AM, Hiranya Jayathilaka <hiranya911@gmail.com
> > wrote:
>
>> Well personally I like the idea of Synapse having a native AMQP
>> implementation rather than having to access AMQP queues over JMS. Some of
>> the prominent AMQP providers like RabbitMQ does not provide JMS and JNDI
>> support at a satisfactory level. IMHO it is totally worth having this
>> transport - as an optional one of course.
>>
>> Thanks,
>> Hiranya
>>
>>
>> On Wed, Nov 25, 2009 at 11:14 PM, Rajith Attapattu <ra...@gmail.com>wrote:
>>
>>> Hi Lahiru,
>>>
>>> I am afraid it's in an unusable state atm mainly due to my fault.
>>> I would also like to take this opportunity to discuss the continuity
>>> of the amqp transport.
>>>
>>> The motivation behind creating an AMQP specific transport instead of
>>> using it via the JMS transport was due to the perceived flexibility &
>>> performance achieved via a transport that is close to the protocol.
>>>
>>> However as Qpid gained more experience and myself having the privilege
>>> of working with customers and end users realized that the JMS
>>> implementation is lacking this flexibility more due to design issues
>>> than any real issue with the API itself. Over the last year or so we
>>> made significant improvements to the JMS client.
>>> The new address format that will be used by all the Qpid clients
>>> including JMS will be rich enough to tune protocol specifics via the
>>> javax.jms.Destination abstraction while allowing applications to use
>>> pure JMS without having to resort to a vendor specific low level API.
>>> Going forward management aspects such as having to create
>>> queues/exchanges dynamically could be done by sending a map message
>>> than invoking a protocol command. Infact in AMQP 1.0 management/admin
>>> work such as declaring queues are not protocol specific commands any
>>> more. They are achieved via sending messages to a known admin/mgt
>>> service within a container.
>>>
>>> There was also quite a bit of performance work done in the JMS client
>>> to the extent the difference btw the JMS layer and lower layer is
>>> negligible for a real business application especially within the
>>> context of Synapse. In artificial benchmarks the diff is about 10k
>>> msg/sec.
>>>
>>> Therefore with the benefit of hindsight I feel that having an AMQP
>>> specific transport doesn't add anything significant over the well
>>> tested JMS transport that Synapse has.
>>> However before coming to a conclusion, it would be worthwhile to
>>> figure out all the use cases around AMQP with Synapse.
>>> Then we could document how they could be achieved via the JMS transport.
>>> If there are any use cases that cannot be reasonably met, then perhaps
>>> we could discuss about an AMQP specific transport.
>>>
>>> Regards,
>>>
>>> Rajith
>>>
>>> On Wed, Nov 25, 2009 at 9:22 AM, Lahiru Gunathilake <gl...@gmail.com>
>>> wrote:
>>> > Hi all,
>>> >
>>> > I like to do some work with synapse AMQP trasport and like to know the
>>> > status of the trasport in current synapse code base.
>>> >
>>> > Regards
>>> > Lahiru
>>> >
>>> > --
>>> > Apache Qpid, Worlds dominant messaging middleware..!!!
>>> >
>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>> Rajith Attapattu
>>> Red Hat
>>> http://rajith.2rlabs.com/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>> For additional commands, e-mail: dev-help@synapse.apache.org
>>>
>>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Software Engineer;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>



-- 
Asanka Abeysinghe
Architect - WSO2, Inc.
m: +94 77 7340064      p: +94 11 2688451/3
e: asankaa@wso2.com w: http://www.wso2.com
b: http://www.asankama.com

Re: Like to know the Synapse AMQP trasports status

Posted by Ruwan Linton <ru...@gmail.com>.
+1 for developing a native AMQP transport.

Thanks,
Ruwan

On Thu, Nov 26, 2009 at 9:52 AM, Hiranya Jayathilaka
<hi...@gmail.com>wrote:

> Well personally I like the idea of Synapse having a native AMQP
> implementation rather than having to access AMQP queues over JMS. Some of
> the prominent AMQP providers like RabbitMQ does not provide JMS and JNDI
> support at a satisfactory level. IMHO it is totally worth having this
> transport - as an optional one of course.
>
> Thanks,
> Hiranya
>
>
> On Wed, Nov 25, 2009 at 11:14 PM, Rajith Attapattu <ra...@gmail.com>wrote:
>
>> Hi Lahiru,
>>
>> I am afraid it's in an unusable state atm mainly due to my fault.
>> I would also like to take this opportunity to discuss the continuity
>> of the amqp transport.
>>
>> The motivation behind creating an AMQP specific transport instead of
>> using it via the JMS transport was due to the perceived flexibility &
>> performance achieved via a transport that is close to the protocol.
>>
>> However as Qpid gained more experience and myself having the privilege
>> of working with customers and end users realized that the JMS
>> implementation is lacking this flexibility more due to design issues
>> than any real issue with the API itself. Over the last year or so we
>> made significant improvements to the JMS client.
>> The new address format that will be used by all the Qpid clients
>> including JMS will be rich enough to tune protocol specifics via the
>> javax.jms.Destination abstraction while allowing applications to use
>> pure JMS without having to resort to a vendor specific low level API.
>> Going forward management aspects such as having to create
>> queues/exchanges dynamically could be done by sending a map message
>> than invoking a protocol command. Infact in AMQP 1.0 management/admin
>> work such as declaring queues are not protocol specific commands any
>> more. They are achieved via sending messages to a known admin/mgt
>> service within a container.
>>
>> There was also quite a bit of performance work done in the JMS client
>> to the extent the difference btw the JMS layer and lower layer is
>> negligible for a real business application especially within the
>> context of Synapse. In artificial benchmarks the diff is about 10k
>> msg/sec.
>>
>> Therefore with the benefit of hindsight I feel that having an AMQP
>> specific transport doesn't add anything significant over the well
>> tested JMS transport that Synapse has.
>> However before coming to a conclusion, it would be worthwhile to
>> figure out all the use cases around AMQP with Synapse.
>> Then we could document how they could be achieved via the JMS transport.
>> If there are any use cases that cannot be reasonably met, then perhaps
>> we could discuss about an AMQP specific transport.
>>
>> Regards,
>>
>> Rajith
>>
>> On Wed, Nov 25, 2009 at 9:22 AM, Lahiru Gunathilake <gl...@gmail.com>
>> wrote:
>> > Hi all,
>> >
>> > I like to do some work with synapse AMQP trasport and like to know the
>> > status of the trasport in current synapse code base.
>> >
>> > Regards
>> > Lahiru
>> >
>> > --
>> > Apache Qpid, Worlds dominant messaging middleware..!!!
>> >
>>
>>
>>
>> --
>> Regards,
>>
>> Rajith Attapattu
>> Red Hat
>> http://rajith.2rlabs.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>



-- 
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com

Re: Like to know the Synapse AMQP trasports status

Posted by Rajith Attapattu <ra...@gmail.com>.
On Fri, Nov 27, 2009 at 12:23 AM, Ruwan Linton <ru...@gmail.com> wrote:
> +1, can some one do a PoC on RabitMQ with the JMS transport?

Qpid and RabbitMQ did some work to figure out how well the clients and
brokers worked with each other.
I have contacted a RabbitMQ guy who may have a document that describes
the config on both sides and a list of issues.

An example of how you could use the Qpid JMS client + Synapse/Axis2
JMS transport with Qpid/RabbitMQ brokers is definitely a good idea.
I think Suran already did the Qpid broker part and both him and I have
written a blog entry with the details,
So a similar exercise for RabbitMQ broker is a good addition.

If somebody could provide a list of use cases around Synapse + AMQP I
could write up how we can configure Synapse and Qpid to achieve those.


> and if it is
> successful then submit that as a sample on to synapse, if we fail to do
> that, what ever the theory is, we will have to go for a native AMQP or some
> transport which can work with AMQP providers like RabitMQ.

I have outlined the challenges/cost/benefit for both approaches.
What exactly to do is a decision that you folks need to make as a project.
Sure I am part of the PMC, but the truth is I haven't been active at
all in the last 2 years or so with the exception of an occasional
email.
So I am not going to be part of the decision making process, plus I am
bias too :)

Work out and see how well the JMS transport + Qpid JMS client could
satisfy the Synapse use cases, including the ability to work with
different AMQP providers.
Look at what's happening in the AMQP landscape in the future. Paul is
an excellent source here as he attends AMQP PMC meetings.
Then see what makes sense for the project going forward.

> Lahiru, whould you like to do this? Or may be Rajith :-)
>
> Thanks,
> Ruwan
>
> On Fri, Nov 27, 2009 at 9:41 AM, Hiranya Jayathilaka <hi...@gmail.com>
> wrote:
>>
>>
>> On Thu, Nov 26, 2009 at 8:42 PM, Rajith Attapattu <ra...@gmail.com>
>> wrote:
>>>
>>> On Wed, Nov 25, 2009 at 11:22 PM, Hiranya Jayathilaka
>>> <hi...@gmail.com> wrote:
>>> > Well personally I like the idea of Synapse having a native AMQP
>>> > implementation rather than having to access AMQP queues over JMS. Some
>>> > of
>>> > the prominent AMQP providers like RabbitMQ does not provide JMS and
>>> > JNDI
>>> > support at a satisfactory level. IMHO it is totally worth having this
>>> > transport - as an optional one of course.
>>>
>>> Good question and one for the FAQ.
>>> AMQP servers does not need to be aware of JMS or support JNDI.
>>> The Qpid client (or for that matter any JMS client built on top of
>>> AMQP) will map JMS semantics on to AMQP, and the protocol takes care
>>> of the rest.
>>> The AMQP WG does understand the prominence of JMS very well, hence
>>> have taken that into account when designing the protocol.
>>>
>>> You could use Qpid JNDI to represent pre created AMQP queues (using a
>>> management tool), or you could dynamically create these queues based
>>> on the destination configuration.
>>> The new address syntax for all language clients that Qpid is currently
>>> working on has a lot more flexibility than the older format.
>>> For example It could do things, like specify declare arguments (to
>>> make use of provide specific features like
>>> max-queue-size,max-queue-count, reject-policy ..etc)
>>> Another example is setting destination specific flow control, or
>>> reliability expectations.
>>> Another important point to note is that, this configuration is done
>>> with AMQP 1.0 in mind. So you could just upgrade to an AMQP 1.0 server
>>> __without any code changes__
>>>
>>> Another benefit of the JMS transport is that you could use it to talk
>>> to RabbitMQ or Qpid brokers.
>>
>> Can we use the JMS transport to talk with brokers like RabbitMQ which are
>> not written in Java? Do you mean to say that we can already use the Axis2
>> JMS transport to connect with JMS unaware AMQP brokers? If that can be done
>> then I'm ready to give up the idea of writing a native AMQP transport.
>> However we need to properly document such tasks by providing sufficient
>> samples.
>>
>> Thanks,
>> Hiranya
>>
>>>
>>> If we use a native AMQP transport it will likely be very close to a
>>> particular protocol version and the sensible option is to use 0-10 or
>>> go straight to 1.0
>>> It should be noted there are significant semantic differences between
>>> 0-8/0-9, 0-10 and 1.0 versions of the protocol.
>>> So it will not work with RabbitMQ. If you use 1.0 currently no
>>> production versions exist as the protocol is yet to be ratified.
>>> If that is taken into account you will end up writing a higher level
>>> client that is protocol agnostic, which would quite bit of work for no
>>> real benefit.
>>> So why not use the JMS transport?
>>>
>>> The RabbitMQ sever is at 0-8 (0-9 too ??) version of the protocol,
>>> while the Qpid java broker supports 0-8,0-9,0-10 and the c++ broker
>>> only the 0-10 version.
>>> However the Qpid JMS client supports all (0-8,0-9 and 0-10) versions
>>> of the protocol.
>>> So you should be able to use the JMS transport with RabbitMQ or Qpid.
>>> (The Qpid client and RabbitMQ does have a few quirks, and that is more
>>> due to issues with the 0-8 protocol and to the fact that some features
>>> are not supported by one vendor)
>>>
>>> So in summary I still don't see any tangible benefit of having a
>>> native AMQP transport, unless we have some very compelling use cases.
>>> Infact I think for a project like Synapse using AMQP via JMS seems
>>> like a safe bet.
>>> But if someone is willing to experiment, I wouldn't stand in the way
>>> either :)
>>>
>>> > Thanks,
>>> > Hiranya
>>> >
>>> > On Wed, Nov 25, 2009 at 11:14 PM, Rajith Attapattu <ra...@gmail.com>
>>> > wrote:
>>> >>
>>> >> Hi Lahiru,
>>> >>
>>> >> I am afraid it's in an unusable state atm mainly due to my fault.
>>> >> I would also like to take this opportunity to discuss the continuity
>>> >> of the amqp transport.
>>> >>
>>> >> The motivation behind creating an AMQP specific transport instead of
>>> >> using it via the JMS transport was due to the perceived flexibility &
>>> >> performance achieved via a transport that is close to the protocol.
>>> >>
>>> >> However as Qpid gained more experience and myself having the privilege
>>> >> of working with customers and end users realized that the JMS
>>> >> implementation is lacking this flexibility more due to design issues
>>> >> than any real issue with the API itself. Over the last year or so we
>>> >> made significant improvements to the JMS client.
>>> >> The new address format that will be used by all the Qpid clients
>>> >> including JMS will be rich enough to tune protocol specifics via the
>>> >> javax.jms.Destination abstraction while allowing applications to use
>>> >> pure JMS without having to resort to a vendor specific low level API.
>>> >> Going forward management aspects such as having to create
>>> >> queues/exchanges dynamically could be done by sending a map message
>>> >> than invoking a protocol command. Infact in AMQP 1.0 management/admin
>>> >> work such as declaring queues are not protocol specific commands any
>>> >> more. They are achieved via sending messages to a known admin/mgt
>>> >> service within a container.
>>> >>
>>> >> There was also quite a bit of performance work done in the JMS client
>>> >> to the extent the difference btw the JMS layer and lower layer is
>>> >> negligible for a real business application especially within the
>>> >> context of Synapse. In artificial benchmarks the diff is about 10k
>>> >> msg/sec.
>>> >>
>>> >> Therefore with the benefit of hindsight I feel that having an AMQP
>>> >> specific transport doesn't add anything significant over the well
>>> >> tested JMS transport that Synapse has.
>>> >> However before coming to a conclusion, it would be worthwhile to
>>> >> figure out all the use cases around AMQP with Synapse.
>>> >> Then we could document how they could be achieved via the JMS
>>> >> transport.
>>> >> If there are any use cases that cannot be reasonably met, then perhaps
>>> >> we could discuss about an AMQP specific transport.
>>> >>
>>> >> Regards,
>>> >>
>>> >> Rajith
>>> >>
>>> >> On Wed, Nov 25, 2009 at 9:22 AM, Lahiru Gunathilake
>>> >> <gl...@gmail.com>
>>> >> wrote:
>>> >> > Hi all,
>>> >> >
>>> >> > I like to do some work with synapse AMQP trasport and like to know
>>> >> > the
>>> >> > status of the trasport in current synapse code base.
>>> >> >
>>> >> > Regards
>>> >> > Lahiru
>>> >> >
>>> >> > --
>>> >> > Apache Qpid, Worlds dominant messaging middleware..!!!
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Regards,
>>> >>
>>> >> Rajith Attapattu
>>> >> Red Hat
>>> >> http://rajith.2rlabs.com/
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>> >> For additional commands, e-mail: dev-help@synapse.apache.org
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Hiranya Jayathilaka
>>> > Software Engineer;
>>> > WSO2 Inc.;  http://wso2.org
>>> > E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
>>> > Blog: http://techfeast-hiranya.blogspot.com
>>> >
>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>> Rajith Attapattu
>>> Red Hat
>>> http://rajith.2rlabs.com/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>> For additional commands, e-mail: dev-help@synapse.apache.org
>>>
>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Software Engineer;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>



-- 
Regards,

Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Re: Like to know the Synapse AMQP trasports status

Posted by Lahiru Gunathilake <gl...@gmail.com>.
On Fri, Nov 27, 2009 at 10:53 AM, Ruwan Linton <ru...@gmail.com>wrote:

> +1, can some one do a PoC on RabitMQ with the JMS transport? and if it is
> successful then submit that as a sample on to synapse, if we fail to do
> that, what ever the theory is, we will have to go for a native AMQP or some
> transport which can work with AMQP providers like RabitMQ.
>
> Lahiru, whould you like to do this? Or may be Rajith :-)
>
Sure, I will do talk to Rajith and do it.


Lahiru

>
> Thanks,
> Ruwan
>
>
> On Fri, Nov 27, 2009 at 9:41 AM, Hiranya Jayathilaka <hiranya911@gmail.com
> > wrote:
>
>>
>>
>> On Thu, Nov 26, 2009 at 8:42 PM, Rajith Attapattu <ra...@gmail.com>wrote:
>>
>>> On Wed, Nov 25, 2009 at 11:22 PM, Hiranya Jayathilaka
>>> <hi...@gmail.com> wrote:
>>> > Well personally I like the idea of Synapse having a native AMQP
>>> > implementation rather than having to access AMQP queues over JMS. Some
>>> of
>>> > the prominent AMQP providers like RabbitMQ does not provide JMS and
>>> JNDI
>>> > support at a satisfactory level. IMHO it is totally worth having this
>>> > transport - as an optional one of course.
>>>
>>> Good question and one for the FAQ.
>>> AMQP servers does not need to be aware of JMS or support JNDI.
>>> The Qpid client (or for that matter any JMS client built on top of
>>> AMQP) will map JMS semantics on to AMQP, and the protocol takes care
>>> of the rest.
>>> The AMQP WG does understand the prominence of JMS very well, hence
>>> have taken that into account when designing the protocol.
>>>
>>> You could use Qpid JNDI to represent pre created AMQP queues (using a
>>> management tool), or you could dynamically create these queues based
>>> on the destination configuration.
>>> The new address syntax for all language clients that Qpid is currently
>>> working on has a lot more flexibility than the older format.
>>> For example It could do things, like specify declare arguments (to
>>> make use of provide specific features like
>>> max-queue-size,max-queue-count, reject-policy ..etc)
>>> Another example is setting destination specific flow control, or
>>> reliability expectations.
>>> Another important point to note is that, this configuration is done
>>> with AMQP 1.0 in mind. So you could just upgrade to an AMQP 1.0 server
>>> __without any code changes__
>>>
>>> Another benefit of the JMS transport is that you could use it to talk
>>> to RabbitMQ or Qpid brokers.
>>>
>>
>> Can we use the JMS transport to talk with brokers like RabbitMQ which are
>> not written in Java? Do you mean to say that we can already use the Axis2
>> JMS transport to connect with JMS unaware AMQP brokers? If that can be done
>> then I'm ready to give up the idea of writing a native AMQP transport.
>> However we need to properly document such tasks by providing sufficient
>> samples.
>>
>> Thanks,
>> Hiranya
>>
>>
>>> If we use a native AMQP transport it will likely be very close to a
>>> particular protocol version and the sensible option is to use 0-10 or
>>> go straight to 1.0
>>> It should be noted there are significant semantic differences between
>>> 0-8/0-9, 0-10 and 1.0 versions of the protocol.
>>> So it will not work with RabbitMQ. If you use 1.0 currently no
>>> production versions exist as the protocol is yet to be ratified.
>>> If that is taken into account you will end up writing a higher level
>>> client that is protocol agnostic, which would quite bit of work for no
>>> real benefit.
>>> So why not use the JMS transport?
>>>
>>> The RabbitMQ sever is at 0-8 (0-9 too ??) version of the protocol,
>>> while the Qpid java broker supports 0-8,0-9,0-10 and the c++ broker
>>> only the 0-10 version.
>>> However the Qpid JMS client supports all (0-8,0-9 and 0-10) versions
>>> of the protocol.
>>> So you should be able to use the JMS transport with RabbitMQ or Qpid.
>>> (The Qpid client and RabbitMQ does have a few quirks, and that is more
>>> due to issues with the 0-8 protocol and to the fact that some features
>>> are not supported by one vendor)
>>>
>>> So in summary I still don't see any tangible benefit of having a
>>> native AMQP transport, unless we have some very compelling use cases.
>>> Infact I think for a project like Synapse using AMQP via JMS seems
>>> like a safe bet.
>>> But if someone is willing to experiment, I wouldn't stand in the way
>>> either :)
>>>
>>> > Thanks,
>>> > Hiranya
>>> >
>>> > On Wed, Nov 25, 2009 at 11:14 PM, Rajith Attapattu <rajith77@gmail.com
>>> >
>>> > wrote:
>>> >>
>>> >> Hi Lahiru,
>>> >>
>>> >> I am afraid it's in an unusable state atm mainly due to my fault.
>>> >> I would also like to take this opportunity to discuss the continuity
>>> >> of the amqp transport.
>>> >>
>>> >> The motivation behind creating an AMQP specific transport instead of
>>> >> using it via the JMS transport was due to the perceived flexibility &
>>> >> performance achieved via a transport that is close to the protocol.
>>> >>
>>> >> However as Qpid gained more experience and myself having the privilege
>>> >> of working with customers and end users realized that the JMS
>>> >> implementation is lacking this flexibility more due to design issues
>>> >> than any real issue with the API itself. Over the last year or so we
>>> >> made significant improvements to the JMS client.
>>> >> The new address format that will be used by all the Qpid clients
>>> >> including JMS will be rich enough to tune protocol specifics via the
>>> >> javax.jms.Destination abstraction while allowing applications to use
>>> >> pure JMS without having to resort to a vendor specific low level API.
>>> >> Going forward management aspects such as having to create
>>> >> queues/exchanges dynamically could be done by sending a map message
>>> >> than invoking a protocol command. Infact in AMQP 1.0 management/admin
>>> >> work such as declaring queues are not protocol specific commands any
>>> >> more. They are achieved via sending messages to a known admin/mgt
>>> >> service within a container.
>>> >>
>>> >> There was also quite a bit of performance work done in the JMS client
>>> >> to the extent the difference btw the JMS layer and lower layer is
>>> >> negligible for a real business application especially within the
>>> >> context of Synapse. In artificial benchmarks the diff is about 10k
>>> >> msg/sec.
>>> >>
>>> >> Therefore with the benefit of hindsight I feel that having an AMQP
>>> >> specific transport doesn't add anything significant over the well
>>> >> tested JMS transport that Synapse has.
>>> >> However before coming to a conclusion, it would be worthwhile to
>>> >> figure out all the use cases around AMQP with Synapse.
>>> >> Then we could document how they could be achieved via the JMS
>>> transport.
>>> >> If there are any use cases that cannot be reasonably met, then perhaps
>>> >> we could discuss about an AMQP specific transport.
>>> >>
>>> >> Regards,
>>> >>
>>> >> Rajith
>>> >>
>>> >> On Wed, Nov 25, 2009 at 9:22 AM, Lahiru Gunathilake <
>>> glahiru@gmail.com>
>>> >> wrote:
>>> >> > Hi all,
>>> >> >
>>> >> > I like to do some work with synapse AMQP trasport and like to know
>>> the
>>> >> > status of the trasport in current synapse code base.
>>> >> >
>>> >> > Regards
>>> >> > Lahiru
>>> >> >
>>> >> > --
>>> >> > Apache Qpid, Worlds dominant messaging middleware..!!!
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Regards,
>>> >>
>>> >> Rajith Attapattu
>>> >> Red Hat
>>> >> http://rajith.2rlabs.com/
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>> >> For additional commands, e-mail: dev-help@synapse.apache.org
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Hiranya Jayathilaka
>>> > Software Engineer;
>>> > WSO2 Inc.;  http://wso2.org
>>> > E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
>>> > Blog: http://techfeast-hiranya.blogspot.com
>>> >
>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>> Rajith Attapattu
>>> Red Hat
>>> http://rajith.2rlabs.com/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>> For additional commands, e-mail: dev-help@synapse.apache.org
>>>
>>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Software Engineer;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>



-- 
Apache Qpid, Worlds dominant messaging middleware..!!!

Re: Like to know the Synapse AMQP trasports status

Posted by Ruwan Linton <ru...@gmail.com>.
+1, can some one do a PoC on RabitMQ with the JMS transport? and if it is
successful then submit that as a sample on to synapse, if we fail to do
that, what ever the theory is, we will have to go for a native AMQP or some
transport which can work with AMQP providers like RabitMQ.

Lahiru, whould you like to do this? Or may be Rajith :-)

Thanks,
Ruwan

On Fri, Nov 27, 2009 at 9:41 AM, Hiranya Jayathilaka
<hi...@gmail.com>wrote:

>
>
> On Thu, Nov 26, 2009 at 8:42 PM, Rajith Attapattu <ra...@gmail.com>wrote:
>
>> On Wed, Nov 25, 2009 at 11:22 PM, Hiranya Jayathilaka
>> <hi...@gmail.com> wrote:
>> > Well personally I like the idea of Synapse having a native AMQP
>> > implementation rather than having to access AMQP queues over JMS. Some
>> of
>> > the prominent AMQP providers like RabbitMQ does not provide JMS and JNDI
>> > support at a satisfactory level. IMHO it is totally worth having this
>> > transport - as an optional one of course.
>>
>> Good question and one for the FAQ.
>> AMQP servers does not need to be aware of JMS or support JNDI.
>> The Qpid client (or for that matter any JMS client built on top of
>> AMQP) will map JMS semantics on to AMQP, and the protocol takes care
>> of the rest.
>> The AMQP WG does understand the prominence of JMS very well, hence
>> have taken that into account when designing the protocol.
>>
>> You could use Qpid JNDI to represent pre created AMQP queues (using a
>> management tool), or you could dynamically create these queues based
>> on the destination configuration.
>> The new address syntax for all language clients that Qpid is currently
>> working on has a lot more flexibility than the older format.
>> For example It could do things, like specify declare arguments (to
>> make use of provide specific features like
>> max-queue-size,max-queue-count, reject-policy ..etc)
>> Another example is setting destination specific flow control, or
>> reliability expectations.
>> Another important point to note is that, this configuration is done
>> with AMQP 1.0 in mind. So you could just upgrade to an AMQP 1.0 server
>> __without any code changes__
>>
>> Another benefit of the JMS transport is that you could use it to talk
>> to RabbitMQ or Qpid brokers.
>>
>
> Can we use the JMS transport to talk with brokers like RabbitMQ which are
> not written in Java? Do you mean to say that we can already use the Axis2
> JMS transport to connect with JMS unaware AMQP brokers? If that can be done
> then I'm ready to give up the idea of writing a native AMQP transport.
> However we need to properly document such tasks by providing sufficient
> samples.
>
> Thanks,
> Hiranya
>
>
>> If we use a native AMQP transport it will likely be very close to a
>> particular protocol version and the sensible option is to use 0-10 or
>> go straight to 1.0
>> It should be noted there are significant semantic differences between
>> 0-8/0-9, 0-10 and 1.0 versions of the protocol.
>> So it will not work with RabbitMQ. If you use 1.0 currently no
>> production versions exist as the protocol is yet to be ratified.
>> If that is taken into account you will end up writing a higher level
>> client that is protocol agnostic, which would quite bit of work for no
>> real benefit.
>> So why not use the JMS transport?
>>
>> The RabbitMQ sever is at 0-8 (0-9 too ??) version of the protocol,
>> while the Qpid java broker supports 0-8,0-9,0-10 and the c++ broker
>> only the 0-10 version.
>> However the Qpid JMS client supports all (0-8,0-9 and 0-10) versions
>> of the protocol.
>> So you should be able to use the JMS transport with RabbitMQ or Qpid.
>> (The Qpid client and RabbitMQ does have a few quirks, and that is more
>> due to issues with the 0-8 protocol and to the fact that some features
>> are not supported by one vendor)
>>
>> So in summary I still don't see any tangible benefit of having a
>> native AMQP transport, unless we have some very compelling use cases.
>> Infact I think for a project like Synapse using AMQP via JMS seems
>> like a safe bet.
>> But if someone is willing to experiment, I wouldn't stand in the way
>> either :)
>>
>> > Thanks,
>> > Hiranya
>> >
>> > On Wed, Nov 25, 2009 at 11:14 PM, Rajith Attapattu <ra...@gmail.com>
>> > wrote:
>> >>
>> >> Hi Lahiru,
>> >>
>> >> I am afraid it's in an unusable state atm mainly due to my fault.
>> >> I would also like to take this opportunity to discuss the continuity
>> >> of the amqp transport.
>> >>
>> >> The motivation behind creating an AMQP specific transport instead of
>> >> using it via the JMS transport was due to the perceived flexibility &
>> >> performance achieved via a transport that is close to the protocol.
>> >>
>> >> However as Qpid gained more experience and myself having the privilege
>> >> of working with customers and end users realized that the JMS
>> >> implementation is lacking this flexibility more due to design issues
>> >> than any real issue with the API itself. Over the last year or so we
>> >> made significant improvements to the JMS client.
>> >> The new address format that will be used by all the Qpid clients
>> >> including JMS will be rich enough to tune protocol specifics via the
>> >> javax.jms.Destination abstraction while allowing applications to use
>> >> pure JMS without having to resort to a vendor specific low level API.
>> >> Going forward management aspects such as having to create
>> >> queues/exchanges dynamically could be done by sending a map message
>> >> than invoking a protocol command. Infact in AMQP 1.0 management/admin
>> >> work such as declaring queues are not protocol specific commands any
>> >> more. They are achieved via sending messages to a known admin/mgt
>> >> service within a container.
>> >>
>> >> There was also quite a bit of performance work done in the JMS client
>> >> to the extent the difference btw the JMS layer and lower layer is
>> >> negligible for a real business application especially within the
>> >> context of Synapse. In artificial benchmarks the diff is about 10k
>> >> msg/sec.
>> >>
>> >> Therefore with the benefit of hindsight I feel that having an AMQP
>> >> specific transport doesn't add anything significant over the well
>> >> tested JMS transport that Synapse has.
>> >> However before coming to a conclusion, it would be worthwhile to
>> >> figure out all the use cases around AMQP with Synapse.
>> >> Then we could document how they could be achieved via the JMS
>> transport.
>> >> If there are any use cases that cannot be reasonably met, then perhaps
>> >> we could discuss about an AMQP specific transport.
>> >>
>> >> Regards,
>> >>
>> >> Rajith
>> >>
>> >> On Wed, Nov 25, 2009 at 9:22 AM, Lahiru Gunathilake <glahiru@gmail.com
>> >
>> >> wrote:
>> >> > Hi all,
>> >> >
>> >> > I like to do some work with synapse AMQP trasport and like to know
>> the
>> >> > status of the trasport in current synapse code base.
>> >> >
>> >> > Regards
>> >> > Lahiru
>> >> >
>> >> > --
>> >> > Apache Qpid, Worlds dominant messaging middleware..!!!
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Regards,
>> >>
>> >> Rajith Attapattu
>> >> Red Hat
>> >> http://rajith.2rlabs.com/
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> >> For additional commands, e-mail: dev-help@synapse.apache.org
>> >>
>> >
>> >
>> >
>> > --
>> > Hiranya Jayathilaka
>> > Software Engineer;
>> > WSO2 Inc.;  http://wso2.org
>> > E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
>> > Blog: http://techfeast-hiranya.blogspot.com
>> >
>>
>>
>>
>> --
>> Regards,
>>
>> Rajith Attapattu
>> Red Hat
>> http://rajith.2rlabs.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>



-- 
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com

Re: Like to know the Synapse AMQP trasports status

Posted by Rajith Attapattu <ra...@gmail.com>.
> Can we use the JMS transport to talk with brokers like RabbitMQ which are
> not written in Java?

AMQP protocol is a language and platform independent protocol.
The Qpid JMS client is an AMQP client that implements the JMS interfaces.
The Qpid JMS client works well with the Java and C++ brokers in Qpid.
It will also work reasonably well with the RabbitMQ broker written in
Erlang if the Qpid client has the strict AMQP flag set
The Qpid JMS client could work with the OpenMQBroker, all though the
OpenMQ broker does not support certain protocol features.

The AMQP protocol had significant changes btw 0-8, 0-9. 0-10 and now
1.0 (in progress).
And different vendors implemented different versions of the protocol.
So interop is not all that great.
However the Qpid JMS client implements all 3 versions (0-8/9/10) of
the protocol, but there are still some quirks w.r.t vendor
interoperability.
However the situation is gradually improving.

With the AMQP 1.0 version I expect the vendors to have a much better
story w.r.t interoperability.

> Do you mean to say that we can already use the Axis2
> JMS transport to connect with JMS unaware AMQP brokers?

Yes provided that you use a JMS client (not just Qpid) that speaks AMQP.
None of the brokers in Qpid is JMS aware. They only speak AMQP.
JMS is only a client side API, but does defines some behaviour as well.

Note: You also need to take into account the AMQP versions supported
by clients and brokers as well.

Have I answered your questions clearly?
If not please feel free to continue asking questions until you are satisfied.

Regards,

Rajith

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Re: Like to know the Synapse AMQP trasports status

Posted by Hiranya Jayathilaka <hi...@gmail.com>.
On Thu, Nov 26, 2009 at 8:42 PM, Rajith Attapattu <ra...@gmail.com>wrote:

> On Wed, Nov 25, 2009 at 11:22 PM, Hiranya Jayathilaka
> <hi...@gmail.com> wrote:
> > Well personally I like the idea of Synapse having a native AMQP
> > implementation rather than having to access AMQP queues over JMS. Some of
> > the prominent AMQP providers like RabbitMQ does not provide JMS and JNDI
> > support at a satisfactory level. IMHO it is totally worth having this
> > transport - as an optional one of course.
>
> Good question and one for the FAQ.
> AMQP servers does not need to be aware of JMS or support JNDI.
> The Qpid client (or for that matter any JMS client built on top of
> AMQP) will map JMS semantics on to AMQP, and the protocol takes care
> of the rest.
> The AMQP WG does understand the prominence of JMS very well, hence
> have taken that into account when designing the protocol.
>
> You could use Qpid JNDI to represent pre created AMQP queues (using a
> management tool), or you could dynamically create these queues based
> on the destination configuration.
> The new address syntax for all language clients that Qpid is currently
> working on has a lot more flexibility than the older format.
> For example It could do things, like specify declare arguments (to
> make use of provide specific features like
> max-queue-size,max-queue-count, reject-policy ..etc)
> Another example is setting destination specific flow control, or
> reliability expectations.
> Another important point to note is that, this configuration is done
> with AMQP 1.0 in mind. So you could just upgrade to an AMQP 1.0 server
> __without any code changes__
>
> Another benefit of the JMS transport is that you could use it to talk
> to RabbitMQ or Qpid brokers.
>

Can we use the JMS transport to talk with brokers like RabbitMQ which are
not written in Java? Do you mean to say that we can already use the Axis2
JMS transport to connect with JMS unaware AMQP brokers? If that can be done
then I'm ready to give up the idea of writing a native AMQP transport.
However we need to properly document such tasks by providing sufficient
samples.

Thanks,
Hiranya


> If we use a native AMQP transport it will likely be very close to a
> particular protocol version and the sensible option is to use 0-10 or
> go straight to 1.0
> It should be noted there are significant semantic differences between
> 0-8/0-9, 0-10 and 1.0 versions of the protocol.
> So it will not work with RabbitMQ. If you use 1.0 currently no
> production versions exist as the protocol is yet to be ratified.
> If that is taken into account you will end up writing a higher level
> client that is protocol agnostic, which would quite bit of work for no
> real benefit.
> So why not use the JMS transport?
>
> The RabbitMQ sever is at 0-8 (0-9 too ??) version of the protocol,
> while the Qpid java broker supports 0-8,0-9,0-10 and the c++ broker
> only the 0-10 version.
> However the Qpid JMS client supports all (0-8,0-9 and 0-10) versions
> of the protocol.
> So you should be able to use the JMS transport with RabbitMQ or Qpid.
> (The Qpid client and RabbitMQ does have a few quirks, and that is more
> due to issues with the 0-8 protocol and to the fact that some features
> are not supported by one vendor)
>
> So in summary I still don't see any tangible benefit of having a
> native AMQP transport, unless we have some very compelling use cases.
> Infact I think for a project like Synapse using AMQP via JMS seems
> like a safe bet.
> But if someone is willing to experiment, I wouldn't stand in the way either
> :)
>
> > Thanks,
> > Hiranya
> >
> > On Wed, Nov 25, 2009 at 11:14 PM, Rajith Attapattu <ra...@gmail.com>
> > wrote:
> >>
> >> Hi Lahiru,
> >>
> >> I am afraid it's in an unusable state atm mainly due to my fault.
> >> I would also like to take this opportunity to discuss the continuity
> >> of the amqp transport.
> >>
> >> The motivation behind creating an AMQP specific transport instead of
> >> using it via the JMS transport was due to the perceived flexibility &
> >> performance achieved via a transport that is close to the protocol.
> >>
> >> However as Qpid gained more experience and myself having the privilege
> >> of working with customers and end users realized that the JMS
> >> implementation is lacking this flexibility more due to design issues
> >> than any real issue with the API itself. Over the last year or so we
> >> made significant improvements to the JMS client.
> >> The new address format that will be used by all the Qpid clients
> >> including JMS will be rich enough to tune protocol specifics via the
> >> javax.jms.Destination abstraction while allowing applications to use
> >> pure JMS without having to resort to a vendor specific low level API.
> >> Going forward management aspects such as having to create
> >> queues/exchanges dynamically could be done by sending a map message
> >> than invoking a protocol command. Infact in AMQP 1.0 management/admin
> >> work such as declaring queues are not protocol specific commands any
> >> more. They are achieved via sending messages to a known admin/mgt
> >> service within a container.
> >>
> >> There was also quite a bit of performance work done in the JMS client
> >> to the extent the difference btw the JMS layer and lower layer is
> >> negligible for a real business application especially within the
> >> context of Synapse. In artificial benchmarks the diff is about 10k
> >> msg/sec.
> >>
> >> Therefore with the benefit of hindsight I feel that having an AMQP
> >> specific transport doesn't add anything significant over the well
> >> tested JMS transport that Synapse has.
> >> However before coming to a conclusion, it would be worthwhile to
> >> figure out all the use cases around AMQP with Synapse.
> >> Then we could document how they could be achieved via the JMS transport.
> >> If there are any use cases that cannot be reasonably met, then perhaps
> >> we could discuss about an AMQP specific transport.
> >>
> >> Regards,
> >>
> >> Rajith
> >>
> >> On Wed, Nov 25, 2009 at 9:22 AM, Lahiru Gunathilake <gl...@gmail.com>
> >> wrote:
> >> > Hi all,
> >> >
> >> > I like to do some work with synapse AMQP trasport and like to know the
> >> > status of the trasport in current synapse code base.
> >> >
> >> > Regards
> >> > Lahiru
> >> >
> >> > --
> >> > Apache Qpid, Worlds dominant messaging middleware..!!!
> >> >
> >>
> >>
> >>
> >> --
> >> Regards,
> >>
> >> Rajith Attapattu
> >> Red Hat
> >> http://rajith.2rlabs.com/
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> >> For additional commands, e-mail: dev-help@synapse.apache.org
> >>
> >
> >
> >
> > --
> > Hiranya Jayathilaka
> > Software Engineer;
> > WSO2 Inc.;  http://wso2.org
> > E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
> > Blog: http://techfeast-hiranya.blogspot.com
> >
>
>
>
> --
> Regards,
>
> Rajith Attapattu
> Red Hat
> http://rajith.2rlabs.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>


-- 
Hiranya Jayathilaka
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

Re: Like to know the Synapse AMQP trasports status

Posted by Rajith Attapattu <ra...@gmail.com>.
On Wed, Nov 25, 2009 at 11:22 PM, Hiranya Jayathilaka
<hi...@gmail.com> wrote:
> Well personally I like the idea of Synapse having a native AMQP
> implementation rather than having to access AMQP queues over JMS. Some of
> the prominent AMQP providers like RabbitMQ does not provide JMS and JNDI
> support at a satisfactory level. IMHO it is totally worth having this
> transport - as an optional one of course.

Good question and one for the FAQ.
AMQP servers does not need to be aware of JMS or support JNDI.
The Qpid client (or for that matter any JMS client built on top of
AMQP) will map JMS semantics on to AMQP, and the protocol takes care
of the rest.
The AMQP WG does understand the prominence of JMS very well, hence
have taken that into account when designing the protocol.

You could use Qpid JNDI to represent pre created AMQP queues (using a
management tool), or you could dynamically create these queues based
on the destination configuration.
The new address syntax for all language clients that Qpid is currently
working on has a lot more flexibility than the older format.
For example It could do things, like specify declare arguments (to
make use of provide specific features like
max-queue-size,max-queue-count, reject-policy ..etc)
Another example is setting destination specific flow control, or
reliability expectations.
Another important point to note is that, this configuration is done
with AMQP 1.0 in mind. So you could just upgrade to an AMQP 1.0 server
__without any code changes__

Another benefit of the JMS transport is that you could use it to talk
to RabbitMQ or Qpid brokers.
If we use a native AMQP transport it will likely be very close to a
particular protocol version and the sensible option is to use 0-10 or
go straight to 1.0
It should be noted there are significant semantic differences between
0-8/0-9, 0-10 and 1.0 versions of the protocol.
So it will not work with RabbitMQ. If you use 1.0 currently no
production versions exist as the protocol is yet to be ratified.
If that is taken into account you will end up writing a higher level
client that is protocol agnostic, which would quite bit of work for no
real benefit.
So why not use the JMS transport?

The RabbitMQ sever is at 0-8 (0-9 too ??) version of the protocol,
while the Qpid java broker supports 0-8,0-9,0-10 and the c++ broker
only the 0-10 version.
However the Qpid JMS client supports all (0-8,0-9 and 0-10) versions
of the protocol.
So you should be able to use the JMS transport with RabbitMQ or Qpid.
(The Qpid client and RabbitMQ does have a few quirks, and that is more
due to issues with the 0-8 protocol and to the fact that some features
are not supported by one vendor)

So in summary I still don't see any tangible benefit of having a
native AMQP transport, unless we have some very compelling use cases.
Infact I think for a project like Synapse using AMQP via JMS seems
like a safe bet.
But if someone is willing to experiment, I wouldn't stand in the way either :)

> Thanks,
> Hiranya
>
> On Wed, Nov 25, 2009 at 11:14 PM, Rajith Attapattu <ra...@gmail.com>
> wrote:
>>
>> Hi Lahiru,
>>
>> I am afraid it's in an unusable state atm mainly due to my fault.
>> I would also like to take this opportunity to discuss the continuity
>> of the amqp transport.
>>
>> The motivation behind creating an AMQP specific transport instead of
>> using it via the JMS transport was due to the perceived flexibility &
>> performance achieved via a transport that is close to the protocol.
>>
>> However as Qpid gained more experience and myself having the privilege
>> of working with customers and end users realized that the JMS
>> implementation is lacking this flexibility more due to design issues
>> than any real issue with the API itself. Over the last year or so we
>> made significant improvements to the JMS client.
>> The new address format that will be used by all the Qpid clients
>> including JMS will be rich enough to tune protocol specifics via the
>> javax.jms.Destination abstraction while allowing applications to use
>> pure JMS without having to resort to a vendor specific low level API.
>> Going forward management aspects such as having to create
>> queues/exchanges dynamically could be done by sending a map message
>> than invoking a protocol command. Infact in AMQP 1.0 management/admin
>> work such as declaring queues are not protocol specific commands any
>> more. They are achieved via sending messages to a known admin/mgt
>> service within a container.
>>
>> There was also quite a bit of performance work done in the JMS client
>> to the extent the difference btw the JMS layer and lower layer is
>> negligible for a real business application especially within the
>> context of Synapse. In artificial benchmarks the diff is about 10k
>> msg/sec.
>>
>> Therefore with the benefit of hindsight I feel that having an AMQP
>> specific transport doesn't add anything significant over the well
>> tested JMS transport that Synapse has.
>> However before coming to a conclusion, it would be worthwhile to
>> figure out all the use cases around AMQP with Synapse.
>> Then we could document how they could be achieved via the JMS transport.
>> If there are any use cases that cannot be reasonably met, then perhaps
>> we could discuss about an AMQP specific transport.
>>
>> Regards,
>>
>> Rajith
>>
>> On Wed, Nov 25, 2009 at 9:22 AM, Lahiru Gunathilake <gl...@gmail.com>
>> wrote:
>> > Hi all,
>> >
>> > I like to do some work with synapse AMQP trasport and like to know the
>> > status of the trasport in current synapse code base.
>> >
>> > Regards
>> > Lahiru
>> >
>> > --
>> > Apache Qpid, Worlds dominant messaging middleware..!!!
>> >
>>
>>
>>
>> --
>> Regards,
>>
>> Rajith Attapattu
>> Red Hat
>> http://rajith.2rlabs.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>
>
>
> --
> Hiranya Jayathilaka
> Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>



-- 
Regards,

Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Re: Like to know the Synapse AMQP trasports status

Posted by Hiranya Jayathilaka <hi...@gmail.com>.
Well personally I like the idea of Synapse having a native AMQP
implementation rather than having to access AMQP queues over JMS. Some of
the prominent AMQP providers like RabbitMQ does not provide JMS and JNDI
support at a satisfactory level. IMHO it is totally worth having this
transport - as an optional one of course.

Thanks,
Hiranya

On Wed, Nov 25, 2009 at 11:14 PM, Rajith Attapattu <ra...@gmail.com>wrote:

> Hi Lahiru,
>
> I am afraid it's in an unusable state atm mainly due to my fault.
> I would also like to take this opportunity to discuss the continuity
> of the amqp transport.
>
> The motivation behind creating an AMQP specific transport instead of
> using it via the JMS transport was due to the perceived flexibility &
> performance achieved via a transport that is close to the protocol.
>
> However as Qpid gained more experience and myself having the privilege
> of working with customers and end users realized that the JMS
> implementation is lacking this flexibility more due to design issues
> than any real issue with the API itself. Over the last year or so we
> made significant improvements to the JMS client.
> The new address format that will be used by all the Qpid clients
> including JMS will be rich enough to tune protocol specifics via the
> javax.jms.Destination abstraction while allowing applications to use
> pure JMS without having to resort to a vendor specific low level API.
> Going forward management aspects such as having to create
> queues/exchanges dynamically could be done by sending a map message
> than invoking a protocol command. Infact in AMQP 1.0 management/admin
> work such as declaring queues are not protocol specific commands any
> more. They are achieved via sending messages to a known admin/mgt
> service within a container.
>
> There was also quite a bit of performance work done in the JMS client
> to the extent the difference btw the JMS layer and lower layer is
> negligible for a real business application especially within the
> context of Synapse. In artificial benchmarks the diff is about 10k
> msg/sec.
>
> Therefore with the benefit of hindsight I feel that having an AMQP
> specific transport doesn't add anything significant over the well
> tested JMS transport that Synapse has.
> However before coming to a conclusion, it would be worthwhile to
> figure out all the use cases around AMQP with Synapse.
> Then we could document how they could be achieved via the JMS transport.
> If there are any use cases that cannot be reasonably met, then perhaps
> we could discuss about an AMQP specific transport.
>
> Regards,
>
> Rajith
>
> On Wed, Nov 25, 2009 at 9:22 AM, Lahiru Gunathilake <gl...@gmail.com>
> wrote:
> > Hi all,
> >
> > I like to do some work with synapse AMQP trasport and like to know the
> > status of the trasport in current synapse code base.
> >
> > Regards
> > Lahiru
> >
> > --
> > Apache Qpid, Worlds dominant messaging middleware..!!!
> >
>
>
>
> --
> Regards,
>
> Rajith Attapattu
> Red Hat
> http://rajith.2rlabs.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>


-- 
Hiranya Jayathilaka
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

Re: Like to know the Synapse AMQP trasports status

Posted by Rajith Attapattu <ra...@gmail.com>.
Hi Lahiru,

I am afraid it's in an unusable state atm mainly due to my fault.
I would also like to take this opportunity to discuss the continuity
of the amqp transport.

The motivation behind creating an AMQP specific transport instead of
using it via the JMS transport was due to the perceived flexibility &
performance achieved via a transport that is close to the protocol.

However as Qpid gained more experience and myself having the privilege
of working with customers and end users realized that the JMS
implementation is lacking this flexibility more due to design issues
than any real issue with the API itself. Over the last year or so we
made significant improvements to the JMS client.
The new address format that will be used by all the Qpid clients
including JMS will be rich enough to tune protocol specifics via the
javax.jms.Destination abstraction while allowing applications to use
pure JMS without having to resort to a vendor specific low level API.
Going forward management aspects such as having to create
queues/exchanges dynamically could be done by sending a map message
than invoking a protocol command. Infact in AMQP 1.0 management/admin
work such as declaring queues are not protocol specific commands any
more. They are achieved via sending messages to a known admin/mgt
service within a container.

There was also quite a bit of performance work done in the JMS client
to the extent the difference btw the JMS layer and lower layer is
negligible for a real business application especially within the
context of Synapse. In artificial benchmarks the diff is about 10k
msg/sec.

Therefore with the benefit of hindsight I feel that having an AMQP
specific transport doesn't add anything significant over the well
tested JMS transport that Synapse has.
However before coming to a conclusion, it would be worthwhile to
figure out all the use cases around AMQP with Synapse.
Then we could document how they could be achieved via the JMS transport.
If there are any use cases that cannot be reasonably met, then perhaps
we could discuss about an AMQP specific transport.

Regards,

Rajith

On Wed, Nov 25, 2009 at 9:22 AM, Lahiru Gunathilake <gl...@gmail.com> wrote:
> Hi all,
>
> I like to do some work with synapse AMQP trasport and like to know the
> status of the trasport in current synapse code base.
>
> Regards
> Lahiru
>
> --
> Apache Qpid, Worlds dominant messaging middleware..!!!
>



-- 
Regards,

Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Re: Like to know the Synapse AMQP trasports status

Posted by Andreas Veithen <an...@gmail.com>.
There was a second, more important reason to retire the AMQP
transport: it started as a fork of the JMS transport, but after that
fork was done, we discovered some very serious issues in the JMS
transport. They have been fixed in the JMS transport, but the AMQP
transport probably inherited them, basically making it unsuitable for
production use.

Andreas

On Wed, Nov 25, 2009 at 18:43, Asanka Abeysinghe <as...@wso2.com> wrote:
> Hi Lahiru,
> There was a native AMQP implementation done in the synapse code base
> (org.apache.synapse.transport.amqp) sometime back and removed due to
> dependencies it had with an unreleased QPid version (M3 or M4).
> Currently Synapse do support AMQP using JMS. There is a working sample with
> AMQP and FIX (Sample #260).
> Thx
> Asanka
>
> On Wed, Nov 25, 2009 at 7:52 PM, Lahiru Gunathilake <gl...@gmail.com>
> wrote:
>>
>> Hi all,
>>
>> I like to do some work with synapse AMQP trasport and like to know the
>> status of the trasport in current synapse code base.
>>
>> Regards
>> Lahiru
>>
>> --
>> Apache Qpid, Worlds dominant messaging middleware..!!!
>
>
>
> --
> Asanka Abeysinghe
> Architect - WSO2, Inc.
> m: +94 77 7340064      p: +94 11 2688451/3
> e: asankaa@wso2.com w: http://www.wso2.com
> b: http://www.asankama.com
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Re: Like to know the Synapse AMQP trasports status

Posted by Asanka Abeysinghe <as...@wso2.com>.
Hi Lahiru,
There was a native AMQP implementation done in the synapse code base
(org.apache.synapse.transport.amqp) sometime back and removed due to
dependencies it had with an unreleased QPid version (M3 or M4).
Currently Synapse do support AMQP using JMS. There is a working sample with
AMQP and FIX (Sample #260).
Thx
Asanka

On Wed, Nov 25, 2009 at 7:52 PM, Lahiru Gunathilake <gl...@gmail.com>wrote:

> Hi all,
>
> I like to do some work with synapse AMQP trasport and like to know the
> status of the trasport in current synapse code base.
>
> Regards
> Lahiru
>
> --
> Apache Qpid, Worlds dominant messaging middleware..!!!
>



-- 
Asanka Abeysinghe
Architect - WSO2, Inc.
m: +94 77 7340064      p: +94 11 2688451/3
e: asankaa@wso2.com w: http://www.wso2.com
b: http://www.asankama.com