You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by André Pfeiler <pf...@e-spirit.de> on 2007/09/26 09:47:52 UTC
How to increase gui debug level
hi,
how can i increase gui debugging level for a custom plugin component?
in the log i see only:
[eter.gui.util.MenuFactory] Could not instantiate XX.XXX.XXX
I added a jsplitpane inside a VerticalPane class and don't know why the gui
component can't be loaded.
i tried:
log_level.<package_name>.className=DEBUG
^^^ same error message as above
thanks, regards
andre
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: How to increase gui debug level
Posted by sebb <se...@gmail.com>.
The component needs its own logging calls. e.g. if the component is called
a.b.c.d then you would need to set
log_level.a.b.c.d=DEBUG
This assumes you are using the same logging manager as the rest of the code,
and "a.b" is not "org.apache"
Probably easiest for something like this to sprinkle print statements in the
code temporarily.
But I doubt it would help in this case; the problem is detected by the Menu
Factory.
You'll need to step through the code, or go back to something that works.
On 26/09/2007, André Pfeiler <pf...@e-spirit.de> wrote:
>
> hi,
> how can i increase gui debugging level for a custom plugin component?
>
> in the log i see only:
> [eter.gui.util.MenuFactory] Could not instantiate XX.XXX.XXX
>
> I added a jsplitpane inside a VerticalPane class and don't know why the
> gui
> component can't be loaded.
>
> i tried:
> log_level.<package_name>.className=DEBUG
> ^^^ same error message as above
>
>
> thanks, regards
> andre
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
>
>