August 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Transaction Services] - Re: Metadata Support for Transactional Web Services

by mark.little＠jboss.com

Thanks Bill. Much appreciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074019#4074019 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074019

18 years, 7 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Failover MessageRedelivery

by mark.little＠jboss.com

"kurt.stam(a)jboss.com" wrote : This redelivery mechanism only kicks in for async delivery. For synchronous message delivery I simply let the delivery fail, so the client can deal with the delivery failure. | | I hope this makes sense to everyone. I will be adding docs tomorrow, but please let me know if you have any feedback/suggestions. | Nice work Kurt. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074013#4074013 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074013

18 years, 7 months

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: Metadata Support for Transactional Web Services

by bill.burke＠jboss.com

FYI, created some noise for you: http://www.theserverside.com/news/thread.tss?thread_id=46557 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074007#4074007 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074007

18 years, 7 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Failover MessageRedelivery

by kurt.stam＠jboss.com

Well this should not happen between actions in the pipeline, but only when routing between services. The code base is now refactored (well almost) to always use the ServiceInvoker for sending messages between services. Now look at the code in asyncDelivery: | message.getProperties().setProperty(MessageStore.CLASSIFICATION, MessageStore.CLASSIFICATION_RDLVR); | message.getProperties().setProperty(DELIVER_TO, service); | deliverToDeadLetterService(message); | If delivery fails it sets the TO service in a property as well as telling it to store it in the MessageStore under classification RDLVR. Now the Redeliver Service periodically wakes up and tries to redeliver all the messages in the RDLVR classification. It uses the setting for the TO service to figure out where to send it. Note that this is bound to the service address and not the EPR. For each retry it will pull the latest EPR information for that service. Going to work on making the maxRedeliveries configurable now :). Does that help? --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074005#4074005 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074005

18 years, 7 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Failover MessageRedelivery

by beve

Hi Kurt, this looks nice! :) We are going to use this but I'm a little bit confused about how the messages that we want redelivered should be added to the MessageStore. We have actions pipelines and when an error occurs and it makes sense to attempt to redeliver, do we simply add the message to the store using a classification name for the pipeline in question. And then configure a redelivery service like this: | <service category="JBossESB-Internal" name="RedeliverService" description="Scheduled Service to Redeliver Messages"> | <listeners> | <scheduled-listener name="redeliver-scheduled-listener" scheduleidref="5-min-trigger" composer="org.jboss.soa.esb.schedule.RedeliverEventMessageComposer" /> | </listeners> | <actions> | <action name="RedeliverMessagesAction" class="org.jboss.soa.esb.actions.MessageRedeliverer"> | <property name="classification" value="process1"/> | </action> | </actions> | </service> | Is this the way we should be doing this? Thanks, Daniel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073993#4073993 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073993

18 years, 7 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Failover MessageRedelivery

by kurt.stam＠jboss.com

I redelivery accounts for the situation where: 1- the jms queue you are trying to use has gone AWAL. So the ServiceInvoker will still find the EPR in the Registry, but at that point it is a 'dead' EPR. When the JMS provider comes back online your message should get redelivered. 2. The destination service is on a different box and the service EPR (or even the service) has not yet registered with the registry. Delivery will be retried until either successful or the max number of retries are reached, after which it is stored in the MessageStore with classification DLQ. --K View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073990#4073990 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073990

18 years, 7 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Starting the detachment of portal common

by chris.laprun＠jboss.com

"julien(a)jboss.com" wrote : I have started to detach the jboss portal common module and I have imported in the SVN under /repos/portal/modules/common/trunk. I have built the binary and put it in the library repository under jboss-portal/modules/common/1.0.0-SNAPSHOT. | | Now I am going to include it in 2.6 branch and trunk (it was taken from 2.6 branch). It should be completed this week. | Several questions: why do this? what are the benefits? why start on the 2.6 branch and not on trunk? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073944#4073944 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073944

18 years, 7 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Failover MessageRedelivery

by burrsutter

How might this situtation arise? "if your delivery fails" Static-Router, CBR, MessageFilter, the wiretap actions? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073937#4073937 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073937

18 years, 7 months

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: Metadata Support for Transactional Web Services

by maciej.machulak

A new version (0.2.0) of the Transactional Web Services Programmer's API has been also released (also available at http://labs.jboss.com/jbosstm/baframework). Cheers, Maciej View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073927#4073927 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073927

18 years, 7 months

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: Metadata Support for Transactional Web Services

by maciej.machulak

Hi, There's a new version of the framework available on the web site (http://labs.jboss.com/jbosstm/baframework). It now supports both agreement protocols - Business Agreement With Participant Completion and Business Agreement With Coordinator Completion (more information about those protocols can be found in the WS-BusinessActivity specification). The API actually slightly changed (in terms of annotation names). I have also extended the demo application. Cheers, Maciej View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073925#4073925 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073925

18 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums August 2007