| Author |
Message
|
| SreeBindu |
 Posted: Tue Aug 21, 2012 6:08 am Post subject: Migration of Broker Runtime to v8- Issues with it |
 |
|
Novice
Joined: 21 Aug 2012
Posts: 12
|
HI ,
We have migrated the Broker runtime from v7 t0 v8 and deployed the migrated flows of v8 flows. In the pre-production system,the migrated v8 flows worked fine ,but in the production the broker is not able to process the request and send to end system.Its using SOAP Input nodes and its a https flow. Once the broker is restarted only then for few minutes its able to process the records to endsystem again after some time, broker is not able to process the request . The broker is getting hanged at some place and stops processing the requests....again we need to restart the broker only then the messages gets processed.Not sure if the issue is related to code or w.r.t migration environment.
We have migrated
1) Broker Runtime v7 to v8
2)WMB 8.0 and IE02
3) WMQ 7.0.1.8
4)WTX 8.4
5)Oracle 11g Client
The recommended Fix Packs have been applied and verified. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Aug 21, 2012 6:12 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Is this in any way related to your out of memory errors?
Is the EG frequently crashing when it 'stops processing'?
What are the results of the basic troubleshooting you've of course already performed? |
|
| Back to top |
|
|
| SreeBindu |
| Posted: Tue Aug 21, 2012 6:20 am Post subject: |
|
|
Novice
Joined: 21 Aug 2012
Posts: 12
|
1) Actually after migration this out of memory issue is one among other issues.
2) I dint face any strange behavior for EG when it stopped processing.
3) When we were testing the flows in v8 pre-production environment, we dint face any issues as the transaction volume was very less.we just tested E2E,if it reaches end system or not. but in producion as the transactions were heavy, the broker wasnt able to process all....  |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Aug 21, 2012 6:25 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| SreeBindu wrote: |
| When we were testing the flows in v8 pre-production environment, we dint face any issues as the transaction volume was very less.we just tested E2E,if it reaches end system or not. but in producion as the transactions were heavy, the broker wasnt able to process all... |
Points out the need to do performance regression testing with actual production-like loads before you migrate functionality to production.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| SreeBindu |
| Posted: Tue Aug 21, 2012 8:10 am Post subject: |
|
|
Novice
Joined: 21 Aug 2012
Posts: 12
|
| Yes we have tested with the same production -like loads but havent faced any issues w.r.t environment.But we faced minor issues with the code which we were able to solve but not something like this kind of broker issues.... |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Aug 21, 2012 8:12 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It has to be doing *something* when it is not responding.
If it's not abending, then it's stuck somehow.
Take a service trace. If nothing else, it will save you a step when you open your PMR. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Aug 21, 2012 8:22 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| SreeBindu wrote: |
| Yes we have tested with the same production -like loads but havent faced any issues w.r.t environment.But we faced minor issues with the code which we were able to solve but not something like this kind of broker issues.... |
The ability of the WebSphere Message Broker product does not change between TEST environment and PROD environment. The capability to perform is the same in each environment.
Your statement that the ability of the Broker runtime to perform in TEST but not in PROD is confusing.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| SreeBindu |
| Posted: Tue Aug 21, 2012 8:44 am Post subject: |
|
|
Novice
Joined: 21 Aug 2012
Posts: 12
|
@mqjeff : We even raised a pmr for this....its stil on the way
@lancelotlinc : yes i agree with you.Here when we faced the issue with broker.We did a kind of workaround.
Workaround: We had a single flow which contains consumer,entity and producer in it,which was giving us the problems. So we just splited the single EG's to 3 EG's and placed the consumer flows in one EG, Entity flows in other EG and then the Producer flows in other EG. Finally this has worked out(I mean we are not restarting the broker to process the messages).It was going as usual
But here we got a new problem is that a deadlock is occuring in the Producer flows. (Again for this , we implemented another workaround, which is a temporary fix)
Finally i have recreated the scenario in TEST environment ie,spliting of 1 EG to 3 EG's, and checked if deadlock is happenig.But it was not happening in the Test environment but facing the iisue in PROD. That is y i was telling you that the issue was only with the PRod but not witth the Test env. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Aug 21, 2012 8:46 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Seems like you are not using viable troubleshooting techniques.
Shooting a shotgun in the dark is likely to hit something, just not the thing you intend. 
Why not actually find the root cause and fix the root cause than work around some problem that is not well understood?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| SreeBindu |
| Posted: Tue Aug 21, 2012 9:02 am Post subject: |
|
|
Novice
Joined: 21 Aug 2012
Posts: 12
|
yaaaaa but we dint had much time to trouble shoot that time.......
So now trying to dig something if i can get. But these days was confused whether it was code issue or environment issue.But after the workaround it was little clear that its something related to environment..... |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Aug 21, 2012 9:09 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| SreeBindu wrote: |
| yaaaaa but we dint had much time to trouble shoot that time....... |
and now you're paying for it. |
|
| Back to top |
|
|
| SreeBindu |
| Posted: Tue Aug 21, 2012 9:16 am Post subject: |
|
|
Novice
Joined: 21 Aug 2012
Posts: 12
|
kind of..... 
Any idea or any picture y are we facing these issues...... |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 21, 2012 9:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| SreeBindu wrote: |
| Any idea or any picture y are we facing these issues...... |
No. You've given us no information except that it sorta doesn't work kind of 'cause it kinda hangs. You were advised earlier in this thread to take a service trace.
I'd say one possible problem is that you've hacked your solution round so much with these temporary fixes you've introduced another problem (this deadlock) which you didn't have before which is masking the original issue.
As others have said, find the issue then fix the issue. Don't just run round and round changing things in the hope it will help.
If you're doing this because you don't have time to fix it properly for the same reason you didn't have time to troubleshoot the original problem, see how well that's worked out for you.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
