I havent read your suggestions yet. I will try to comprehend them. Thanks
for your answers again.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-message-queue-oriented-design-help-tp4703776p4703840.html
Sent from the ActiveMQ - User mailing list archive at
messages's point of view, C clusters are not backup of B clusters.
>> >>
>> >> Normally I was planning to use netty and manage the connections as I
>> >> described. Normally i am doing failover over connections. For reliable
>> >> messages I was planning async Acks. For some cases duplicate detection
>> >> requires. Then I have heard hornetq and then artemis which does nearly
>> all
>> >> of my requirements.
>> >> I dont want to reinvent the wheel. But I cannot figure not the queues,
>> the
>> >> bridges, the diverts, the cluster groups required. Especially site B to
>> >> site
>> >> C failover is very likely to the artemis solution. But it is something
>> >> cülike clusters of clusters
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://activemq.2283324.n4.nabble.com/Artemis-message-queue-oriented-design-help-tp4703776p4703798.html
>> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> >>
>>
>>
>>
>> --
>> Clebert Suconic
>>
--
Clebert Suconic
ble
> >> messages I was planning async Acks. For some cases duplicate detection
> >> requires. Then I have heard hornetq and then artemis which does nearly
> all
> >> of my requirements.
> >> I dont want to reinvent the wheel. But I cannot figure not the queues,
> the
> >> bridges, the diverts, the cluster groups required. Especially site B to
> >> site
> >> C failover is very likely to the artemis solution. But it is something
> >> cülike clusters of clusters
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://activemq.2283324.n4.nabble.com/Artemis-message-queue-oriented-design-help-tp4703776p4703798.html
> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >>
>
>
>
> --
> Clebert Suconic
>
ections. For reliable
>> messages I was planning async Acks. For some cases duplicate detection
>> requires. Then I have heard hornetq and then artemis which does nearly all
>> of my requirements.
>> I dont want to reinvent the wheel. But I cannot figure not the queues, the
&g
ething
> cülike clusters of clusters
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Artemis-message-queue-oriented-design-help-tp4703776p4703798.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
roups required. Especially site B to site
C failover is very likely to the artemis solution. But it is something
cülike clusters of clusters
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-message-queue-oriented-design-help-tp4703776p4703798.html
Sent from the Act
t exactly figure out whether it fulfils my above scenario.
>
> Could you help me? Thanks for your answers.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Artemis-message-queue-oriented-design-help-tp4703776.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
Clebert Suconic
fulfils my above scenario.
Could you help me? Thanks for your answers.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-message-queue-oriented-design-help-tp4703776.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.