| Author |
Message
|
| wbintegrator |
 Posted: Thu May 25, 2006 2:49 am Post subject: "Unable to open flow editor" when debugging. |
 |
|
Voyager
Joined: 08 Feb 2006
Posts: 83
|
HI all,
I have been receiving this strange error ever since we upgraded the MB toolkit to v6.0 but I'm not sure that it has anything to do with the version as my co-workers don't have the error.
I re-installed the toolkit and applied the updates with hope that it would solve the strange problem but unfortunately I only wasted several hours in vain.
Any ideas?
Thanks for help in advance. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu May 25, 2006 4:13 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Add the -clean option to the Toolkit startup command, and run it that way ONCE.
This will tell Eclipse to rebuild it's plugin cache.
It's very slow, so that's why only run it that way once. Remove the -c otherwise.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wbintegrator |
| Posted: Thu May 25, 2006 4:50 am Post subject: |
|
|
Voyager
Joined: 08 Feb 2006
Posts: 83
|
Thanks for your reply jefflowrey, I tried what you suggested but didn't help..
By the way, important to note that, the error I get is not really actual, as the flow editor IS opened in the end, but after every step in the debugger I get the error first and only after that I see the debugger ball advancing. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu May 25, 2006 4:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I've seen more discussion of this same problem... I think it was here. Try the search, and see what comes up.
I'm pretty sure it's either an issue with the plugin cache, or an issue that is fixed in the Toolkit FP or the broker FP - or maybe both.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wbintegrator |
| Posted: Thu May 25, 2006 5:42 am Post subject: |
|
|
Voyager
Joined: 08 Feb 2006
Posts: 83
|
I've searched the forums for "unable to open flow editor", but didn't find any post on the subject, unfortunately.
As for the TFP/BFP, we have the latest fixes installed. |
|
| Back to top |
|
|
| sourdas2 |
| Posted: Thu May 25, 2006 6:29 am Post subject: |
|
|
Voyager
Joined: 21 Apr 2006
Posts: 90
Location: Kolkata,India
|
Please do a thing ...
firstly delete '.metadata' directory for your tool-kit workspace.
Then try to reinstall the fixpacks and agent controller. Then start the tool kit and try.
Looks like a plug-in error.
_________________
Thanks and Warm Regards
Sourav |
|
| Back to top |
|
|
| anand158 |
| Posted: Thu May 25, 2006 10:40 am Post subject: |
|
|
Newbie
Joined: 25 May 2005
Posts: 8
|
Hi,
Install IBM Rational Agent Controller then restart all the services then you can work in debug Mode
Bye,
Anand |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu May 25, 2006 12:01 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Exactly what service have you applied to the toolkit? I would suggest that at a minimum, you use Rational Product Updater to apply FP1. Right now, we are also up to Broker FP1 Interim Fix 004. (I'm not saying that I've done to research to know this will fix your problem, but its a starting point)
_________________
-wayne |
|
| Back to top |
|
|
| wbintegrator |
| Posted: Sat May 27, 2006 9:29 pm Post subject: |
|
|
Voyager
Joined: 08 Feb 2006
Posts: 83
|
As I mentioned above, I re-installed the whole toolkit, assigned a new workspace - didn't copy anything from the old one, and installed all the fix packs.
Thanks for your suggestions anyway, I'll try to do something. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun May 28, 2006 5:45 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
How much RAM do you have on your PC ?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| wbintegrator |
| Posted: Mon May 29, 2006 2:05 am Post subject: |
|
|
Voyager
Joined: 08 Feb 2006
Posts: 83
|
1G.
I deleted the .metadata once again after the re-install and as I expected, it didn't help, just wanted to make sure. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon May 29, 2006 2:48 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You might be running into memory problems. For a full stack (broker + toolkit ) I would recommend at least 2 GB of RAM.
I am only running the toolkit with 512 MB of RAM and I am feeling it page...
This may introduce delays and timeouts into stuff that normally would be fine.... I have asked for a memory upgrade, and should be getting it shortly.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| francoisvdm |
| Posted: Wed Jun 07, 2006 11:32 pm Post subject: |
|
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
I'm seeing th esame on my side..... only from after I upgraded V6 with fixpacks. Did you manage to fix it? btw, I've got 2G in my machine.
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| Back to top |
|
|
| SpitFire |
| Posted: Thu Jun 08, 2006 1:35 am Post subject: |
|
|
Acolyte
Joined: 01 Aug 2005
Posts: 59
Location: India
|
| wbintegrator wrote: |
| By the way, important to note that, the error I get is not really actual, as the flow editor IS opened in the end, but after every step in the debugger I get the error first and only after that I see the debugger ball advancing. |
It might sound silly, but IMHO, if the flow editor is not opening only while debugging, then I think the problem is more to do with the debug configuration than with anything else.
If I'm wrong, somebody please correct me.
_________________
...: 5|71+ph1|23 :... |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Jun 08, 2006 1:41 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
I'm able to reproduce this problem. The issue is with "Project References" in the properties of the project you are debugging. Those referenced projects must be defined in your workspace. They don't need to be "open" projects, but they must exist in your workspace.
_________________
-wayne |
|
| Back to top |
|
|
|
|
