The only thing I can think of is to make sure you set persistent="true" in your JBI container, or on your message. I don't think flow="jms" means persistent by default.
Sharon Yin-2 wrote: > > > > If I set the JBI container's flowName=jms, then I connect a external > webservice using HttpEndpoint in XBean, role="provider", after I debug > into > the source code, I found that servicemix is using the class > "ProviderProcessor.java (line 168)" to invoke external service , as below: > > "int response = > getClient().executeMethod(getHostConfiguration(locationURI), > method);" > > If the external service is down, there will be errors return, but I'm > expecting the request message should be stored in the queue of this > endpoint, because I'm using JMS flow, when I start up external service > again, I want it can receive the request again and process. > > > > I found that org.apache.servicemix.http.processors.ProviderProcessor is > different from "HttpInvoker", which implemented MessageExchangeListener. > As > my test, when I use HttpInvoker as BC to connect external service, > flowName=jms, the request will be stored in queue until send it out > successfully to the external service. > > > > Do I make any mistake? Does HttpEndpoint support reliable message routing > and persistence in JMS flow? > > > > Thanks for any comment. > > > > Chris. > > > -- View this message in context: http://www.nabble.com/HttpEndpoint-can%27t-persist-request-message-in-queue-when-external-service-is-down-tf3563175s12049.html#a9978298 Sent from the ServiceMix - User mailing list archive at Nabble.com.
