Jean-Baptiste Onofré wrote: > > Hi Martin, > > Your scenario looks fine for me. The only things is that the timer bean > (that's > read on the JMS queue) need to repost the message in the JMS queue if the > mainframe doesn't answer (else the JMS message will disappear from the > queue). I > have made something like that (not using SMX but using EJB Message Driven > Bean) > and to avoid huge JMS load (due to repost), I have add a timeout property > in the > message attributes. > > Regards > JB >
Hi JB, thanks for your hint. In the meantime I tend to store such cases in a usual DB. Because of I've already an auditlog mechanism which store every request and response in the DB. So it would be an easy thing to enhance this mechanism and store such requests with a "pending" marker. I believe this gives me more freedom for implementation than a JMS approach Regards, Martin -- View this message in context: http://www.nabble.com/Re%3A-Design-question-from-a-SMX-newbie-%28handle-temporarily-unavailabletarget-service%29-tp21436233p21454128.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
