| Author |
Message
|
| extrany |
 Posted: Tue Dec 27, 2011 9:53 am Post subject: Flow droppes on SOAP Request |
 |
|
Novice
Joined: 01 Sep 2011
Posts: 14
|
Hi all.
We have a flow, where one SOAP Request can be used multiple times in cycle. When it used up to 11-12 , flow droppes without any errors in system log or in user trace.
Something with memory? Maybe MQSI_THREAD_STACK_SIZE will help?
WMB 6.1.0.9, platform AIX.
Any ideas? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Dec 27, 2011 10:07 am Post subject: Re: Flow droppes on SOAP Request |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| extrany wrote: |
| We have a flow, where one SOAP Request can be used multiple times in cycle. |
Why are you cycling a single request, and how? Why are you not using aggregation for this kind of thing?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| extrany |
| Posted: Tue Dec 27, 2011 10:12 am Post subject: |
|
|
Novice
Joined: 01 Sep 2011
Posts: 14
|
For x elements we must find some information (the web-service give it to us) and map it to xml.
Cycle is for all of x: prepare request, soap request, work with response, go to next element(if it is nesessary).
I can't modify design of the flow now  I must find some properties, that will help me. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Dec 27, 2011 10:54 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| extrany wrote: |
I can't modify design of the flow now I must find some properties, that will help me. |
Yes you can. If it does not work then you will have to change it.
Besides, what is wrong with changing how your flow works but keeing the interface to the outside world the same?
Think about splitting your flow up as Vitor suggested.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| extrany |
| Posted: Tue Dec 27, 2011 12:03 pm Post subject: |
|
|
Novice
Joined: 01 Sep 2011
Posts: 14
|
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Dec 27, 2011 12:11 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| extrany wrote: |
| If I had more time... |
or training. Seems you do not possess the knowledge required, yet.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 27, 2011 1:05 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| extrany wrote: |
| I must find some properties, that will help me. |
Good luck with that. Without knowing what's failing you're going to be down to randomly changing things to see if it helps. Given that nothing in the system log it does seem to be unlikely anything at the system level is going to have that much effect.
But I could be wrong of course.
It's interesting that "nothing" turns up in the user trace. Typically the user trace contains a lot, even if it contains no error messages saying "your problem is here:"
This information could help you diagnose the issue with your flow and (possibly) identify small changes that will assist you short of a redesign.
If you're lucky.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| extrany |
| Posted: Tue Dec 27, 2011 1:21 pm Post subject: |
|
|
Novice
Joined: 01 Sep 2011
Posts: 14
|
Thank you all for you comments.
Next time I'll use aggregate functional. Now I will try to find solution of the problem without serious redesign. But I think something wrong with memory, stack. Because flow droppes after fixed count of requests.
About user trace... There is some information about message going through the flow, soap requests, and after this some information that meens "message rolled back to input terminal"(Execution group restarts). But i'll see more closely.
Last edited by extrany on Tue Dec 27, 2011 1:30 pm; edited 1 time in total |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 27, 2011 1:26 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| extrany wrote: |
Thank you all for you comments.
Next time I'll use aggregate functional. Now I will try to find solution of the problem without serious redesign. But I think something wrong with memory, stack. Because flow droppes after fixed count of requests. |
No something's wrong with your design, especially if you are looping a node using the graphical interface instead of propagate 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 27, 2011 1:31 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| extrany wrote: |
| But I think something wrong with memory, stack. Because flow droppes after fixed count of requests. |
If you were running out of memory, it's odd that it runs out after a fixed count rather than just because it's expended. It's also odd given that the only thing using memory is your flow...
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Dec 28, 2011 5:34 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Gee Sir Vitor, please go easy on this guy. He's not been to training class yet and his boss said he must make the flow work without changing it.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 28, 2011 6:55 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| Gee Sir Vitor, please go easy on this guy. He's not been to training class yet and his boss said he must make the flow work without changing it. |
And if my boss told me to write a JCN I could easily end up at a point where it was so screwed up I'd have to start again having taken advice from someone who knew what they were doing.
Especially if the task was not a straightforward one, as appears to be the case here. So the OP can either chase snark through his design with a measurable chance he'll find a setting that make his code work (increased heap size if he's looping inside Java for example) or explain to his boss that the current flow won't work, he needs time to redesign it and it would never have come to this if proper training had been provided before work started.
I also simply commented it's odd that it runs out of memory after a fixed number of itterations. This could be a clue & the OP's highest chance of success is finding the cause of the abend. This will be faster than redesigning, and much faster than looking for the "just work will you" button in the broker runtime.
A button I've been looking for lo these many years.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Dec 28, 2011 7:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| I am currently placing odds at 3 to one that extrany has wired the flow in a loop, that there is a node connection that extends from a out terminal of one node into the in terminal of some other node. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 28, 2011 8:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| I am currently placing odds at 3 to one that extrany has wired the flow in a loop, that there is a node connection that extends from a out terminal of one node into the in terminal of some other node. |
A loop, and running out of memory? You think? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| extrany |
| Posted: Thu Dec 29, 2011 12:39 am Post subject: |
|
|
Novice
Joined: 01 Sep 2011
Posts: 14
|
We are very lucky and increasing stack size up to 4Mb for thread helped us with this problem.
But you are right, design could be better. By the way, not me wrote this code and design. I just added some esql functionality and had no time to redesign. But thank you for a lot of words about importance of design. I'll remember it and when it will be needed, read about and use aggregate functional.
By the way, it's odd, but abend file did't generate when EG terminated. And on Windows, when we received this error, in Event log there was a record about stack overflow, on AIX we hadn't. |
|
| Back to top |
|
|
|
|
