| Author |
Message
|
| mqjeff |
 Posted: Sun Jan 10, 2010 8:34 am Post subject: |
 |
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| fjb_saper wrote: |
You could just ask your Unix admin to give read access to the trace file and read + execute access to the directory to all.  |
or sudo access to the mqsireadlog, mqsiformatlog programs.
Or the admin's mobile and home number so that any time you need a trace run, you can just call them and get them to run it.
I mean, really, whichever is more convenient for the admin, it's not a bother for you right? |
|
| Back to top |
|
 |
| SANTYP |
| Posted: Wed Jan 13, 2010 6:17 pm Post subject: Re: Debugger making me to frustrate |
|
|
Centurion
Joined: 27 Mar 2007
Posts: 142
|
| mqmatt wrote: |
| SANTYP wrote: |
I started by debugger.. but it took 20 min for launch the debugger..
I put the break points to my flow it takes morethan 2 mins,..
after posting req msg it is talking 1-2 min to move from one break point to another... |
This sounds like a PMR.
And you might also want to try restarting the toolkit with the -clean option. |
Yes, I tried but no use..  |
|
| Back to top |
|
|
| francoisvdm |
| Posted: Wed Jan 13, 2010 11:35 pm Post subject: |
|
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
I'm old...but I use the debugger almost "exclusively"... very VERY rarely need to use trace nodes.
_________________
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 |
|
|
| Mercator |
| Posted: Thu Jan 14, 2010 8:20 am Post subject: |
|
|
Apprentice
Joined: 21 Jul 2009
Posts: 34
|
How many flow projects do you have linked with your debugger (edit source lookup)? I know that the more I have, the slower the debugger gets.
I discovered this by noticing that my debugger was screaming fast whenever I created a new workspace and then gradually slowed over time.
FYI - As someone who came from a product that never really had a debugger, I will say that I love broker's debugger and use it all the time. It can quickly point me in the right direction for problems, where I can then use user trace / trace nodes to pin point it. |
|
| Back to top |
|
|
| SANTYP |
| Posted: Thu Jan 14, 2010 7:05 pm Post subject: |
|
|
Centurion
Joined: 27 Mar 2007
Posts: 142
|
| Mercator wrote: |
How many flow projects do you have linked with your debugger (edit source lookup)? I know that the more I have, the slower the debugger gets.
I discovered this by noticing that my debugger was screaming fast whenever I created a new workspace and then gradually slowed over time.
FYI - As someone who came from a product that never really had a debugger, I will say that I love broker's debugger and use it all the time. It can quickly point me in the right direction for problems, where I can then use user trace / trace nodes to pin point it. |
fortunalty I have only one project added in the debugger...
even though it is responding very slow...
is there any other way to improve my debugger perfomance  |
|
| Back to top |
|
|
| SOLOHERO |
| Posted: Thu Jan 14, 2010 9:01 pm Post subject: |
|
|
Centurion
Joined: 01 Feb 2007
Posts: 107
|
Check if the system process when you start the debugger,
what version of agent controller are you running.
Agent controller is your debugger. so compare it see the performance, of your system.
Create a new workspace and add your projects , and try to run the debugger again.If required change the debugger port number.
Hope this helps.
_________________
Thanks |
|
| Back to top |
|
|
|
|
