| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Exception occuring with TimeOut nodes |
« View previous topic :: View next topic » |
| Author |
Message
|
| psandip |
 Posted: Tue Oct 13, 2009 11:02 pm Post subject: Exception occuring with TimeOut nodes |
 |
|
Novice
Joined: 11 Aug 2006
Posts: 17
|
Hi,
I am developing a message flow in MB 6.1 where I need to capture the request via SOAPInput node and send a timeout request to timeout control node. The corresponding TimeOut notification flow is present in the same mesage flow. Before the Timeout control node, I am preparing the MQMD header as specified in the documents.
CREATE NEXTSIBLING OF OutputRoot.Properties DOMAIN 'MQMD';
SET OutputRoot.MQMD.Version = MQMD_CURRENT_VERSION;
SET OutputRoot.MQMD.Format = 'XMLNSC';
But the massage comes out from the failure terminal of the timeout notification node. However if I do put an MQGet node before the Timeout control node, then this MQMD header seems to be correct in the respect that now message comes from the out terminal of the timeout notification node.
I also tried MQFMT_STRING for OutputRoot.MQMD.Format field but still same problem.
_________________
With Best Regards,
Sandeep |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Tue Oct 13, 2009 11:55 pm Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
What clues did the user trace give you as to why this was happening?
What differences are there between the message that is gotten using an MQGet and the message that you have formed? What have you done to check this? |
|
| Back to top |
|
|
| psandip |
| Posted: Wed Oct 14, 2009 12:31 am Post subject: |
|
|
Novice
Joined: 11 Aug 2006
Posts: 17
|
the trace says:
UserTrace BIP4624I: Exception condition detected on input node: 'ProvisionServiceFlow.TimeoutNotification'.
Node 'ProvisionServiceFlow.TimeoutNotification' has detected a failure during message processing. The message broker is propagating the message to the failure terminal.
Examine further messages to determine why the message is not being received as expected. Correct this situation if possible. Perform any local error recovery processing required.
2009-10-14 13:59:10.695299 924 RecoverableException BIP4619E: The TimeoutNotification node 'ProvisionServiceFlow.TimeoutNotification' received a bad timeout request.
The node received a corrupt timeout request message. This error can occur if the message stored by the corresponding TimeoutControl node cannot be de-serialized. It can also occur if messages that are not generated by a TimeoutControl node have been put on the message store.
Correct the incoming data.
_________________
With Best Regards,
Sandeep |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Oct 14, 2009 1:42 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| I suggest that you do what the message says. Examine the other error messages in the user trace, and quote them here. If you can't find them, increase the log file size when you enable user trace. |
|
| Back to top |
|
|
| psandip |
| Posted: Wed Oct 14, 2009 2:43 am Post subject: |
|
|
Novice
Joined: 11 Aug 2006
Posts: 17
|
Let me say the requirement first.
When a request comes through SOAPInput node, a file needs to be generated with some message transformation logic. If a request does not come for , say 5 minutes, we need to go ahead and close the file. Thus if a request comes the next instant, a new file will be used otherwise it is the same old file where records are to be written. The file can hold say 100 records. So whether or not to create a file is driven by two parameters, one whether the record limit for the file has exceeded which has been already implemented through logic in compute node and the other parameter is whether a specified time limit has exceeded which I am implementing using Timer nodes. Also there needs to be some kind of synchronization so that once I send the timeout request for say 5 minutes and then a request has arrived , I should be able to cancel the timeout request.
Can this be done through Timer nodes?. I am quite confident that it can be done but not totally confident.
_________________
With Best Regards,
Sandeep |
|
| Back to top |
|
|
| mqseries0209 |
| Posted: Wed Oct 14, 2009 6:21 am Post subject: |
|
|
Voyager
Joined: 30 Mar 2006
Posts: 90
|
| Quote: |
| When a request comes through SOAPInput node, a file needs to be generated with some message transformation logic. If a request does not come for , say 5 minutes, we need to go ahead and close the file. Thus if a request comes the next instant, a new file will be used otherwise it is the same old file where records are to be written. The file can hold say 100 records. So whether or not to create a file is driven by two parameters, one whether the record limit for the file has exceeded which has been already implemented through logic in compute node and the other parameter is whether a specified time limit has exceeded which I am implementing using Timer nodes. Also there needs to be some kind of synchronization so that once I send the timeout request for say 5 minutes and then a request has arrived , I should be able to cancel the timeout request. |
Although your requirement is little tricky, I would suggest u to examine using collection node (u would have more control) and timeout notification node for this purpose (ofcourse with SOAPInput node )
_________________
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Integration Developer V6.0 |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
