| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Stack overflow error in debugger |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vitor |
 Posted: Tue Jan 09, 2007 6:26 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| burman.abhishek wrote: |
Also I am a bit sceptical, as I am in a delicate project and if anything starts malfunctioning after applying the fix-pack, could lead to serious consequences.
|
Fair comment, but it's always wise to keep patched more or less up to date. If only because it helps prevent this sort of error cramping your development!
I think there are enough people in here who have upgraded to offer a degree of confidence once the project has become less critical, i.e. perhaps patch the development environment once the project has moved into test.
My 2 cents. Other opinions are equally valid. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| pathipati |
| Posted: Tue Jan 09, 2007 7:52 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| Quote: |
| Fair comment, but it's always wise to keep patched more or less up to date. |
yes, if it is possible to rollback..(but I guess we can't rollback) |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 09, 2007 8:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pathipati wrote: |
| Quote: |
| Fair comment, but it's always wise to keep patched more or less up to date. |
yes, if it is possible to rollback..(but I guess we can't rollback) |
You shouldn't need to rollback a development environment unless you've got serious issues, and that touches back to the "leading edge v bleeding edge" question. IHMO the point of patching the dev environment is to shake out all the issues that will bite you when you upgrade the test environment and beyond. Otherwise how can you ensure test (or worse production) stability? Only once you've got dev stable (including additional fixes, posts to this board, support calls to the vendor etc) can you risk it further up the chain.
Not patching until you're certain it's stable and won't interfer with development is the thinking that keeps 5.2 out there... 
My experience is that most shops have multiple dev environment and one is selected as the lucky receipient of the new software! A twist on this is to apply the software to a user-free admin area for stability testing, but my experience is that something that the sys progs have been happily using for weeks breaks in minutes once developers get hold of it.
I'm disinclined to speculate on why this is. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| nvenkatesh |
| Posted: Mon Jan 29, 2007 10:29 pm Post subject: |
|
|
Apprentice
Joined: 29 Jan 2007
Posts: 45
|
Hi,
I too had the same problem and I resolved it. What i found in my project was i had recursive project references . That is Project A had a reference to Project B and Project B inturn had a reference to Project A. (Probably because of that the toolkit is not able to resolve the reference correctly and go in loop). When i deleted one of the references and redeployed the flow, i was able to Debug the flow successfully without getting the stack overflow error. Might be you have a similar setting in your message flow projects.
Thanks |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
