Bill de hÓra
Posts: 1137
Nickname: dehora
Registered: May, 2003
|
Bill de hÓra is a technical architect with Propylon
|
|
|
|
503 Service Unavailable
|
Posted: Jun 7, 2004 3:00 AM
|
|
|
This post originated from an RSS feed registered with Java Buzz
by Bill de hÓra.
|
Original Post: 503 Service Unavailable
Feed Title: Bill de hÓra
Feed URL: http://www.dehora.net/journal/atom.xml
Feed Description: FD85 1117 1888 1681 7689 B5DF E696 885C 20D8 21F8
|
Latest Java Buzz Posts
Latest Java Buzz Posts by Bill de hÓra
Latest Posts From Bill de hÓra
|
|
Simon Brown enters the hell that is J2EE fineprint: The reason that we discovered this is because we were trying to figure out the best way to implement logic like, "sorry, not quite ready to process this message yet". - Simon Brown That would be 503 Service unavailable in HTTP. I love HTTP. I came across this problem recently in a different context to Simons' transaction case - mine was MDB throwing an exception to the container and the container continously resending the message. The simplest answer seemed to be to have retry/dead-letter queues - otherwise you end up tied into someone's JMS provider via configuration lock-in. Sometimes you don't want to have a message retried after a number of efforts; sometimes it has to run within a certain time; sometimes there's no point in resending (like invalid XML in a text message). Having retry and dead-letter queues is more work, but it is somewhat portable. Sometimes what JMS provides is too low-level to represent the application problem - there's a world of difference between a transaction and an order fulfilment. And that's why I love HTTP (and Internet protocols in general) over APIs - quite often they have exactly the semantics your application needs....
Read: 503 Service Unavailable
|
|
Previous Topic
