ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » HTTPRequest node trouble

Post new topic  Reply to topic
 HTTPRequest node trouble « View previous topic :: View next topic » 
Author Message
harelmoshe1
PostPosted: Thu Feb 16, 2006 4:58 am    Post subject: HTTPRequest node trouble Reply with quote

Apprentice

Joined: 29 Dec 2005
Posts: 41

Hey,

I wrote the following flow:

HttpInput->Compute->HTTPRequest->(...)

with the HTTPRequest node having both Error and Failure terminals connected to error-handling sub-flows.

The problem is as follows:
When i intentionally send an XML to a web-service with the wrong URL, the message is routed to the failure terminal (the XML i tried to send gets out exactly as i intended to send it). When i try to send it for the 2nd time (say i have a queue with 2 exact messages being sent one after another) and on, it's being replaced by a HTTP Error-response message ("Internal server error 500 blabla") which is being routed to the Error terminal.
I unchecked both "Replace input message with web-service response" and "Replace input with error" check-boxes in the node's configuration, still i keep getting the same problem - only from the 2nd time.
An interesting thing is that only the 1st sending-attempt yields a Socket-Exception being thrown and therefore routes the message to the Failure terminal, while the following attemts yeilds no such exception although the URL is the same (still wrong) in both cases.

By the way, i must get the message i send routed to either Error or Failyre terminal because my error-handling flows need a certain XML tag in it in order to log the error to a DB and handle it right.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Feb 16, 2006 5:38 am    Post subject: Re: HTTPRequest node trouble Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

harelmoshe1 wrote:
By the way, i must get the message i send routed to either Error or Failyre terminal because my error-handling flows need a certain XML tag in it in order to log the error to a DB and handle it right.


Why not just stick the XML tag into the Environment tree, and grab it again in your error logic?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
harelmoshe1
PostPosted: Thu Feb 16, 2006 9:56 am    Post subject: Reply with quote

Apprentice

Joined: 29 Dec 2005
Posts: 41

Quote:
Why not just stick the XML tag into the Environment tree, and grab it again in your error logic?


Thanks for your idea, it will surely get around the problem - but i was wishing that maybe someone could tell me a bit more about the difference between these 'error modes'...

For now, i see no other way but using your idea... thank again.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » HTTPRequest node trouble
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.