snip... > > 1) have the consumer spawn new threads to process each request (using the > existing Tuscany thread pool). One problem with that is i don't think we > can't do QOS using the standard JMS APIs as once the consumer returns the > message is considered successfully processed but the spawned thread may > still be processing or have an exception. >
Not sure I understand this para. If the consumer starts processing the message shouldn't we consider that it has been successfully delivered. Processing it may cause errors but these should be application errors that in the @OneWay case presumably get written to a log or when the operation is not one way are put in a return message and sent back to the reply to address. Simon
