It's all about the answers!

Ask a question

How to change log output level of RTC Eclipse client?


ryosuke oka (17984548) | asked Sep 26 '13, 4:00 a.m.
One of my customer want to trace every transaction of client (Eclipse) and want to know
- what trace level we can change?
- how we can change?

I had check many documents of Eclipse but this dose not seem to be applied to RTC Eclipse client.
If anyone know there is a way to change log output level to be debug or fine, then let me know.



Comments
ryosuke oka commented Sep 26 '13, 4:06 a.m.

Adding more explanation for this.
I mean   .metadata/.log output in RTC client.

Thank you.

One answer



permanent link
Eric Jodet (6.3k5104120) | answered Sep 26 '13, 4:44 a.m.
JAZZ DEVELOPER
 Hello Ryo,
this comes with creating some custom file which contains the debug options.
You then start this Eclipse Client with the debug option pointing to this file:
http://help.eclipse.org/indigo/topic/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html

This said, not sure what you mean by "trace every transaction of client".
If you want to check client / [RTC] server exchanges,
with not use the metronome feature
?

Thanks,
Eric

Comments
ryosuke oka commented Oct 06 '13, 8:21 a.m.

Hi Eric, Thank you for your answer.

1. I had created logging.properties file with these properties and placed it in same directory as eclipse.ini.
.level = INFO
handlers = java.util.logging.FileHandler,
java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.formatter =
java.util.logging.SimpleFormatter
java.util.logging.ConsoleHandler.level = ALL
com.ibm.team.repository.transport.auth.Tracer.level = ALL
com.ibm.team.repository.transport.client.ClientHttpUtil.level = ALL
httpclient.wire.header.level = FINEST
httpclient.wire.content.level = FINEST
httpclient.wire.level = FINEST
httpclient.level = FINEST

2. Then added these in eclipse.ini
-Djavax.net.debug=all
-Djava.util.logging.config.file=<exact path to>logging.properties

but it dose not seems to be working.


ryosuke oka commented Oct 06 '13, 8:22 a.m.


What had happened was one there was a issue of build and the cause was 2 same component name on the same stream. And we found who has accessed the stream around the issued but could not find detailed execution of what had been done.
so, the customer asked us to find a way to trace these normal activites (not error or warning).

Appreciate your comment on log setting and a way to trace.


Eric Jodet commented Oct 06 '13, 12:18 p.m. | edited Oct 06 '13, 12:18 p.m.
JAZZ DEVELOPER

 Hello Ryo,

once you created a file with your debug options,
you create an Eclipse shortcut and point eclipse.exe to use this file

eclipse.exe -debug <some_path>/super_options.file

Hope it helps
Eric


ryosuke oka commented Oct 18 '13, 1:52 a.m.

thank you, Eric.

I was able to get debug output to log file but it dose not include SCM related transaction.
So, It works OK but it did not give me desired output.

I think we do not get scm related log for java output log.


Eric Jodet commented Oct 18 '13, 2:08 a.m.
JAZZ DEVELOPER

Hello Ryo,

did you use SCM tracing settings?
Are you looking for some setting?
You may contact Glenn Bardwel

Eric 


Kevin Ramer commented Oct 18 '13, 4:05 p.m.

RE:

What had happened was one there was a issue of build and the cause was 2 same component name on the same stream.


Finding things about component/streams can also be done by looking at "Recent Events" on a project area.   If you do this within a short period of time after discovery you might find an entry relating to the event.

In eclipse client, right click the project label, choose Show / Recent Events.  There are categories for Source Control Changes, Source Control Components and Source Control Streams.   I've discovered who/when relating to a change in stream component this way in  the past.


Guillermo Hurtado commented Nov 15 '13, 5:22 p.m.

 Hello Ryo, 


The following worked for me...


 1) Created a file named logging.properties and added the following:
 
com.ibm.team.repository.transport.auth.Tracer.level=ALL
com.ibm.team.repository.transport.client.ClientHttpUtil.level=ALL
httpclient.wire.header.level=FINEST
org.apache.commons.httpclient.level=FINEST

2) Edited eclipse.ini and added the following at the end:
-Djava.util.logging.config.file=<path to created logging.properties>

3) Deleted all logs under .metadata folder

4) Restarted eclipse with -clean parameter 


This produced a .log file with entries for the HTTP connections. 

showing 5 of 7 show 2 more comments

Your answer


Register or to post your answer.