How do I fix this warning on a new 4.0.5 install?
I have just finished a fresh/clean install of CLM 4.0.5 (JTS, CCM, RM, QM) on a Windows 2012 Server. I did the startServer running as Administrator and it started and I was able to complete the Setup and create a couple additional users. When looking at my Tomcat window, I see these warnings:
INFO: Server startup in 48097 ms
[com.ibm.team.server.monitoring.service] warning Cannot access resource for -Xlintfile:META-INF/Xlint.properties
[com.ibm.team.server.monitoring.service] warning Cannot access resource for -Xlintfile:META-INF/Xlint.properties
[com.ibm.team.server.monitoring.service] warning Cannot access resource for -Xlintfile:META-INF/Xlint.properties
Does anyone know what those are and how to fix whatever is wrong?
Thanks, Susan
INFO: Server startup in 48097 ms
[com.ibm.team.server.monitoring.service] warning Cannot access resource for -Xlintfile:META-INF/Xlint.properties
[com.ibm.team.server.monitoring.service] warning Cannot access resource for -Xlintfile:META-INF/Xlint.properties
[com.ibm.team.server.monitoring.service] warning Cannot access resource for -Xlintfile:META-INF/Xlint.properties
Does anyone know what those are and how to fix whatever is wrong?
Thanks, Susan
2 answers
Hi Susan
There is a defect logged with this error for 4.0.5 release and I believe you are running into the same error.
https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=282871
If this is hampering the environment or something that needs to be fixed, you might want to raise a PMR with IBM support and continue to work.
Hi Susan,
Defect 282871: [com.ibm.team.server.monitoring.service] warning Cannot access resource for -Xlintfile:META-INF/Xlint.properties
affects CLM Server Monitoring feature.
There is no risk of loss of data or instability issues because of this.
Defect 282871: [com.ibm.team.server.monitoring.service] warning Cannot access resource for -Xlintfile:META-INF/Xlint.properties
affects CLM Server Monitoring feature.
There is no risk of loss of data or instability issues because of this.