Wish #154

debug info in CMD window

Added by Han Alink about 6 years ago. Updated almost 6 years ago.

Status:Rejected Start date:10/22/2012
Priority:Normal Due date:
Assignee:Manlio Bacco % Done:


Category:all Spent time: -
Target version:-


Is it possible to switch of some of the debug info in the command window?
Since the last update all events (mouse clicks, scrolls etc ) in the tester window are reported in the command window.
I looked at the config file: org.ops4j.pax.logging.properties but don't see how I change this behaviour.


#1 Updated by Stefano Lenzi almost 7 years ago

  • Category set to all
  • Status changed from New to In Progress
  • Assignee changed from Stefano Lenzi to Manlio Bacco

Manlio can you describe the way to configure the logging on the wiki?

#2 Updated by Stefano Lenzi almost 7 years ago

Anyway you can have a look at this log4j properties that will be used for configuring the logging, while the docs on the configuration file is here .

Considering that the logging is mediated by OPS4J Pax Logging you should look at this OPS4J Pax Logging Documentation and Pax ConfMan for letting OSGi read the configuration at runtime.

#3 Updated by Han Alink almost 7 years ago

I still have problems with the logging of data.
Every time I move the mouse or make a mouseclick in the tester window, up to 100 lines of debugging code are generated and displayed in the log window. It makes debugging much more difficult. I don't see how to change this behaviour in the configuration file. Help!!!

#4 Updated by Stefano Lenzi almost 6 years ago

The configuration of the logging system depends on the way you are using for executing the project. If you are using the commands

mvn pax:run
cd runner

from the zigbee.tester folder for executing the ZigBee Suite, then you can update the logging configuration by starting/restarting the OPS4J Pax ConfMan - Properties Loader bundle.
For example on my shell I execute the following commands
-> ps
   ID   State         Level  Name
[   0] [Active     ] [    0] System Bundle (2.0.2)
[   1] [Active     ] [    5] Zigbee Tester (0.4.0.SNAPSHOT)
[   2] [Active     ] [    5] OSGi R4 Core Bundle (4)
[   3] [Active     ] [    5] ZigBee Home Automation Profile Driver (0.7.0.SNAPSHOT)
[   4] [Active     ] [    5] ZigBee Common Cluster Library (0.8.0.SNAPSHOT)
[   5] [Active     ] [    5] ZigBee Base Driver API for OSGi (0.6.0.SNAPSHOT)
[   6] [Active     ] [    5] OSGi and Primitive Types Utility (0.6.0.SNAPSHOT)
[   7] [Resolved   ] [    5] OPS4J Pax ConfMan - Properties Loader (0.2.2)
[   8] [Active     ] [    5] rxtx Bundle Wrapper (2.1.7.SNAPSHOT)
[   9] [Active     ] [    5] net.sf.trove4j Bundle Wrapper (
[  10] [Active     ] [    5] ZigBee Interface Controller API (0.7.0.SNAPSHOT)
[  11] [Active     ] [    5] CC2480 Data Link protocol library (0.8.0.SNAPSHOT)
[  12] [Active     ] [    5] ZigBee Base Driver (0.7.0.SNAPSHOT)
[  13] [Active     ] [    5] OPS4J Pax Logging - API (1.4)
[  14] [Active     ] [    5] OPS4J Pax Logging - Service (1.4)
[  15] [Active     ] [    5] Apache Felix Configuration Admin Service (1.2.4)
[  16] [Installed  ] [    5] ZIC CC2530 dongle (0.2.0.SNAPSHOT)
[  17] [Installed  ] [    5] ZIC for EZ430-RF2480 dongle (0.7.0.SNAPSHOT)
[  18] [Active     ] [    1] Apache Felix Shell Service (1.4.1)
[  19] [Active     ] [    1] Apache Felix Shell TUI (1.4.1)
-> start 7

*NOTE:*The main command here is "start 7" where 7 is the bundle id for the bundle that we need to start.

Finally the actual logging configuration is loaded from the file


from the zigbee.tester folder, so you have to change that file to change the logging policy

I hope it helps...

#5 Updated by Han Alink almost 6 years ago

I did not change a single line in this configuration file; it's the same as I have always used. Nevertheless, since 22/10 every move of the mouse and every click generates multiple lines of debug info. This was never the case, so I think it is introduced by the addition to or change of the Zigbee tester classes. Did you try yourself Stefano?

#6 Updated by Stefano Lenzi almost 6 years ago

I wasn't saying that you changed the configuration (even if you may lost it when you deleted your working copy and you check out the project again)

Nevertheless, the guide that I wrote are the instruction that I do follow on my own, so they should work for you too. The logging system hasn't been changed in last weeks so it should be an issue of the code. You may revert your zigbee.tester to old release and I bet that you will get the same behavior of the logging.

If it is not working please post the sequence of command that you are using for executing the ZigBee Tester

#7 Updated by Han Alink almost 6 years ago

For some reason the logging bundle changed from bundle 6 to 7. I did not notice that and kept starting 6 instead of 7. Sorry for having bothered you with this issue.

#8 Updated by Stefano Lenzi almost 6 years ago

  • Status changed from In Progress to Rejected

Also available in: Atom PDF