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 » Orace query hanging the broker

Post new topic  Reply to topic
 Orace query hanging the broker « View previous topic :: View next topic » 
Author Message
narendra68
PostPosted: Thu Feb 02, 2012 9:13 am    Post subject: Orace query hanging the broker Reply with quote

Apprentice

Joined: 17 Nov 2004
Posts: 30

making a SP call to Oracle , that is taking too much time and cranking up the Broker.

Is there a way to set the time on the DB call. time out on the DB call?

Would appreciate any help on this!!!
_________________
Narendra
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Thu Feb 02, 2012 9:28 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Set the timeout value on the Input node of the flow.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
narendra68
PostPosted: Thu Feb 02, 2012 11:06 am    Post subject: Reply with quote

Apprentice

Joined: 17 Nov 2004
Posts: 30

I have the wait time set and the request gets timed out after that period but for some reason the execution group gets hung up.
_________________
Narendra
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Thu Feb 02, 2012 11:09 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Use trace nodes to see what is happening in your flow. Or, take a user trace.

I like the trace node option much better, since once you put them in, you can leave them in for future troubleshooting.

http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fac04840_.htm

You should put a Trace node before and after every functional node in your flow.

Quote:
Include a Trace node to help diagnose errors in your message flow. By tracing the contents of the message at various points in the flow, you can determine the sequence of processing. You can configure the Trace node to record the content of a message, and to check the action of a specific node on the message. For example, you can include a Trace node immediately after a Compute node to check that the output message has the expected format.

You can also use the Trace node to provide information in error handling in your message flows. For example, you can use this node to record failures in processing because of errors in the content or format of a message.

_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
narendra68
PostPosted: Thu Feb 02, 2012 1:01 pm    Post subject: Reply with quote

Apprentice

Joined: 17 Nov 2004
Posts: 30

No trace after the DB call.
_________________
Narendra
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 » Orace query hanging the broker
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.