| Author |
Message
|
| akhnukh |
 Posted: Sun Sep 01, 2013 12:04 am Post subject: Execution Group Hangs after X number of Request |
 |
|
Newbie
Joined: 16 Oct 2008
Posts: 9
|
Hi,
Env- Detail :
MQSI 6.1.0.8
Message FLOW :
SOAP Input --> JAVA Computue --> LABEL NODE --> JAVA Compute Calling SOAP Web Service --> SOAP Reply --> JAVA Compute to Dump log message.
Execution Group report properties:
jvmMinHeapSize= 268435456
jvmMaxHeapSize= 536870912
Problem:
Flow is working fine for normal access, But when i try to run same service using SOAP UI client Load testing , execution group get hanged/irresponsive after 50 Runs. I tried increasing heap size etc but didnt get any clue so far.
Please share any direction for further investigation.
Regards, |
|
| Back to top |
|
 |
| msunny |
| Posted: Sun Sep 01, 2013 8:59 pm Post subject: |
|
|
Novice
Joined: 07 Dec 2007
Posts: 18
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Sep 01, 2013 10:32 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Are you calling the external web service from within the second JCN?
Why are you doing this?
Are you sure that it is not this part of your flow that is causing you the problem?
Why did you not use the existing SOAP Nodes to do this for you?
Have you looked at the fix list for 6.1.0.9 & 6.1.0.10 to see if there are and APARS similar to your problem corrected in those releases?
finally,
Are you migrating away from 6.1 now that it is out of service?
_________________
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 |
|
|
| Tibor |
| Posted: Sun Sep 01, 2013 11:46 pm Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| Have you already tried to switch the broker trace on? It would be useful for working out where your problem is emerging. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Sep 02, 2013 12:18 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Tibor wrote: |
| Have you already tried to switch the broker trace on? It would be useful for working out where your problem is emerging. |
Broker trace won't be all that useful if there is some problem deep in the JCN's. If the EG hangs then the output to the user trace file may well not get completed to the point where the hang takes place.
_________________
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 |
|
|
| Tibor |
| Posted: Mon Sep 02, 2013 12:25 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| smdavies99 wrote: |
| Broker trace won't be all that useful if there is some problem deep in the JCN's. If the EG hangs then the output to the user trace file may well not get completed to the point where the hang takes place. |
You are right, but it might be useful. Similarly any broker related entries in syslog / event viewer. |
|
| Back to top |
|
|
| akhnukh |
| Posted: Wed Sep 04, 2013 12:27 am Post subject: |
|
|
Newbie
Joined: 16 Oct 2008
Posts: 9
|
| smdavies99 wrote: |
Are you calling the external web service from within the second JCN?
Why are you doing this?
Are you sure that it is not this part of your flow that is causing you the problem?
Why did you not use the existing SOAP Nodes to do this for you?
Have you looked at the fix list for 6.1.0.9 & 6.1.0.10 to see if there are and APARS similar to your problem corrected in those releases?
finally,
Are you migrating away from 6.1 now that it is out of service? |
Hi,
Thanks for your replies.
We need to use JCN as part of architecture we are doing some pre processing before calling external webservice. For this purpose we have we have webservice client code and pre processing code bundled in java lib which is in broker shared classes. So in my JCN just invoking methods.
Regarding upgrading we are thinking of upgrading it to 8.
| Quote: |
| External web serivce causing the problem |
BTW I have tried external Webserivce by creating a wrapper flow and external WS is responsive and never hanged the Exe Group.
BTW I have done some more research that as long as i increase Execution group JVM MIN and MAX memory. results are improving mean with min 128 MB it hangs after 30 continuous request. similarly increasing min to 256 it hangs after 45 request. while in both cases max memory is 512.
[/quote] |
|
| Back to top |
|
|
| dogorsy |
| Posted: Wed Sep 04, 2013 1:51 am Post subject: |
|
|
Knight
Joined: 13 Mar 2013
Posts: 553
Location: Home Office
|
| Obviously increasing the jvm memory will not solve the problem, only delay it. You need to look at your code. I would replace the web service you are calling with a stub ( the stub would not do much, you return a valid soap message ), so you can eliminate the external WS from you list of suspects and reduce complexity. |
|
| Back to top |
|
|
|
|
