You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Raster3 <cr...@yahoo.co.in> on 2010/02/01 05:12:59 UTC
Guranteed Delivery
This is regrading this http://camel.apache.org/guaranteed-delivery.html
I would to restrict this discussion to JMS.
I have used webloic JMS. I understand guranteed delivery is part of JMS
specs and what this means is that the message will be stored by the JMS
provider till its delievered to the intended recepient / subscriber.
This is counter to the image shown in the image associated with the url
where it appears that the message is stored on two sides- sender and
reciever. When using JMS would you not wish the message to be stored just by
the JMS provider?
Am I missing something?
--
View this message in context: http://old.nabble.com/Guranteed-Delivery-tp27399518p27399518.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Guranteed Delivery
Posted by Raster3 <cr...@yahoo.co.in>.
This sounds fair.
Is there any official camel stand on this?
Thanks.
Ashwin Karpe wrote:
>
> Hi,
>
> Interesting point. What is probably confusing in the picture is that the
> JMS Broker is not shown and its location is unclear.
>
> If there are 2 networked broker instances on each box with each having its
> own persistent store then the figure is fine. Also if there was DB
> replication involved then it may be good. If not, then the figure may not
> be quite accurate.
>
> The way to read this is to look at the expressed intent in the figure
> rather to delivery mechanics. In that the picture is fine.
>
> This figure come out of the EIP patterns book which simply expresses the
> idea of delivery level guarantees without talking about concrete
> technology implementations (JMS) for which there may be many possible
> implementations styles and techniques employed by different JMS
> implementations.
>
> Cheers,
>
> Ashwin...
>
>
> Raster3 wrote:
>>
>>
>> This is regrading this http://camel.apache.org/guaranteed-delivery.html
>>
>> I would to restrict this discussion to JMS.
>> I have used webloic JMS. I understand guranteed delivery is part of JMS
>> specs and what this means is that the message will be stored by the JMS
>> provider till its delievered to the intended recepient / subscriber.
>>
>> This is counter to the image shown in the image associated with the url
>> where it appears that the message is stored on two sides- sender and
>> reciever. When using JMS would you not wish the message to be stored just
>> by the JMS provider?
>>
>> Am I missing something?
>>
>
>
--
View this message in context: http://old.nabble.com/Guranteed-Delivery-tp27399518p27402491.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Guranteed Delivery
Posted by Ashwin Karpe <as...@progress.com>.
Hi,
Interesting point. What is confusing in the picture is that the JMS Broker
is not shown and its location is unclear.
If there are 2 networked broker instances on each box with each having its
own persistent store then the figure is fine. Also if there was DB
replication involved then it may be good. If not, then the figure may not be
quite accurate.
The way to read this is to look at the expressed intent in the figure rather
to delivery mechanics.
This figure come out of the EIP patterns book which simply expresses the
idea of delivery level guarantees without talking about concrete technology
implementations (JMS) for which there may be many possible implementations
styles and techniques.
Cheers,
Ashwin...
Raster3 wrote:
>
>
> This is regrading this http://camel.apache.org/guaranteed-delivery.html
>
> I would to restrict this discussion to JMS.
> I have used webloic JMS. I understand guranteed delivery is part of JMS
> specs and what this means is that the message will be stored by the JMS
> provider till its delievered to the intended recepient / subscriber.
>
> This is counter to the image shown in the image associated with the url
> where it appears that the message is stored on two sides- sender and
> reciever. When using JMS would you not wish the message to be stored just
> by the JMS provider?
>
> Am I missing something?
>
-----
---
Ashwin Karpe, Principal Consultant, PS - Opensource Center of Competence
Progress Software Corporation
14 Oak Park Drive
Bedford, MA 01730
---
+1-972-304-9084 (Office)
+1-972-971-1700 (Mobile)
----
Blog: http://opensourceknowledge.blogspot.com/
--
View this message in context: http://old.nabble.com/Guranteed-Delivery-tp27399518p27402353.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Guranteed Delivery
Posted by Raster3 <cr...@yahoo.co.in>.
Thanks. I understand that that the pattern says that the message is stored
when sending and also when receiving. I can understand how this can be
useful when the endpoint is a non-jms endpoint.
But guaranteed delivery goes with the JMS specs and is implemented by the
JMS provider using its filestore / database configuration. When we limit
ourselves to JMS endpoints is not the storing of message at sender and
receiver an over kill especially when guranteed delivery is available out of
the box with JMS providers.
Claus Ibsen-2 wrote:
>
> On Mon, Feb 1, 2010 at 5:12 AM, Raster3 <cr...@yahoo.co.in> wrote:
>>
>>
>> This is regrading this http://camel.apache.org/guaranteed-delivery.html
>>
>> I would to restrict this discussion to JMS.
>> I have used webloic JMS. I understand guranteed delivery is part of JMS
>> specs and what this means is that the message will be stored by the JMS
>> provider till its delievered to the intended recepient / subscriber.
>>
>> This is counter to the image shown in the image associated with the url
>> where it appears that the message is stored on two sides- sender and
>> reciever. When using JMS would you not wish the message to be stored just
>> by
>> the JMS provider?
>>
>> Am I missing something?
>
> That is just how the figure is illustrated in the EIP book
> http://www.enterpriseintegrationpatterns.com/
> http://www.enterpriseintegrationpatterns.com/GuaranteedMessaging.html
>
> Whose figures Camel uses as well.
>
>
>> --
>> View this message in context:
>> http://old.nabble.com/Guranteed-Delivery-tp27399518p27399518.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Author of Camel in Action: http://www.manning.com/ibsen/
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
>
--
View this message in context: http://old.nabble.com/Guranteed-Delivery-tp27399518p27402444.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Guranteed Delivery
Posted by Claus Ibsen <cl...@gmail.com>.
On Mon, Feb 1, 2010 at 5:12 AM, Raster3 <cr...@yahoo.co.in> wrote:
>
>
> This is regrading this http://camel.apache.org/guaranteed-delivery.html
>
> I would to restrict this discussion to JMS.
> I have used webloic JMS. I understand guranteed delivery is part of JMS
> specs and what this means is that the message will be stored by the JMS
> provider till its delievered to the intended recepient / subscriber.
>
> This is counter to the image shown in the image associated with the url
> where it appears that the message is stored on two sides- sender and
> reciever. When using JMS would you not wish the message to be stored just by
> the JMS provider?
>
> Am I missing something?
That is just how the figure is illustrated in the EIP book
http://www.enterpriseintegrationpatterns.com/
http://www.enterpriseintegrationpatterns.com/GuaranteedMessaging.html
Whose figures Camel uses as well.
> --
> View this message in context: http://old.nabble.com/Guranteed-Delivery-tp27399518p27399518.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus