It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884
×6,034
×4,321

question asked: Oct 06 '16, 10:31 a.m.
question was seen: 2,129 times
last updated: Dec 09 '16, 10:27 a.m.

Related questions

How do I suppress repotools from creating "configuration" log ?

0
Kevin Ramer (4.5k●9●186●201) | asked Oct 06 '16, 10:31 a.m.
I use repotools-jts to periodically list issued licenses for server metrics.   I notice that 100000s of log files were written each time repotools-jts is run.  I have removed them, but this is an example of the content, location of one such file.  
current directory is repotools under a CLM 5.0.2 install

cat ./jts/eclipse/configuration/1475763999062.log
!SESSION 2016-10-06 10:26:38.368 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr16-20140626_204542 (JIT enabled, AOT enabled)
J9VM - 20140626_204542
JIT  - r9_20130920_46510ifx7
GC   - GA24_Java6_SR16_20140626_1848_B204542
BootLoader constants: OS=aix, ARCH=ppc64, WS=motif, NL=en_US
Framework arguments:  -application com.ibm.team.repotools.rcp.repotools_application -listIssuedFloatingLicenses repositoryURL=https://imsclm.tivlab.raleigh.ibm.com:9444/jts credentialsFile=/home/ramerk/.credentials.properties logFile=imsclm.log
Command-line arguments:  -application com.ibm.team.repotools.rcp.repotools_application -data /CLM502/rtc3srv1/server/../repotools/jts/workspace -listIssuedFloatingLicenses repositoryURL=https://imsclm.tivlab.raleigh.ibm.com:9444/jts credentialsFile=/home/ramerk/.credentials.properties logFile=imsclm.log

!ENTRY org.eclipse.osgi 4 0 2016-10-06 10:26:39.515
!MESSAGE Bundle org.eclipse.equinox.launcher.win32.win32.x86 not found.


I know I could farm the filesystem and remove those files, but how can they be bit-bucketed ( i.e. never written )

Accepted answer

0
permanent link
Donald Nong (14.5k●6●14) | answered Oct 07 '16, 12:59 a.m.
I believe it is caused by a small bug. The log file is there because Eclipse cannot resolve the bundle mentioned in the log file - "org.eclipse.equinox.launcher.win32.win32.x86". Well, it should not be there anyway, as you are using AIX.

To resolve this, modify the file repotools/jts/eclipse/configuration/config.ini by removing the string "org.eclipse.equinox.launcher.win32.win32.x86,". Or replace it with the actual bundle for the platform (which you can find in the repotools/jts/eclipse/plugins folder. For example, on Red Hat Linux, it is "org.eclipse.equinox.launcher.gtk.linux.x86". I don't find any ill effect with either solution.
Kevin Ramer selected this answer as the correct answer
Comments
Kevin Ramer commented Oct 07 '16, 8:18 a.m.

I will give your suggestion a whirl !

Kevin Ramer commented Oct 07 '16, 8:59 a.m.

Removing the org.eclipse.equinox...win32.win32.x86 made repotools angrier.  There are only the win32 and linux variety of org.eclipse.equinox.launcher plugin under the plugins folder.

Donald Nong commented Oct 09 '16, 7:26 p.m.

Did you remove it and the comma? All plugin names are separated by commas.  It's not my experience that the repotools gets any angrier. :-)

Kevin Ramer commented Dec 09 '16, 10:27 a.m.

I revisited this today making sure I removed the plugin name leaving a single delimiter.  No more logs !

Thanks Donald

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.