License job is running for over 10 days.
One answer
DIAGNOSTICS:
Running services in Admin panel for JTS shows the following stack trace:
WOKRAROUND:
Restart the server. After restarting the server it was working correctly
PREVENTIVE TARGET:
Running services in Admin panel for JTS shows the following stack trace:
java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:140) oracle.net.ns.Packet.receive(Packet.java:300) oracle.net.ns.DataPacket.receive(DataPacket.java:106) oracle.net.ns.NetInputStream.getNextPacket(NetInputStream.java:315) oracle.net.ns.NetInputStream.read(NetInputStream.java:260) oracle.net.ns.NetInputStream.read(NetInputStream.java:185) oracle.net.ns.NetInputStream.read(NetInputStream.java:102)JTS log file shows the following error message when the server stopped updating jts-etl.log file with the progress of license job:
<unauthenticated> /jts/query] WARN com.ibm.team.jfs - CRJZS5742W Query _JxLdoHLQEeWb_bM9811_Zw had an execution time of 282127 ms, and produced 0 results [jts: AsynchronousTaskRunner-2 @@ 07:40] ERROR com.ibm.team.repository - CRJAZ2654E The server was unable to connect to the database because the database connection settings are invalid or because database is unreachable (SQLSTATE: 08006, SQLCODE: 17002). Verify the connection settings in your teamserver.properties file. See the Jazz Team Server log for more information. java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:458) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:546) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:236) ... Caused by: java.net.NoRouteToHostException: No route to host at java.net.PlainSocketImpl.socketConnect(Native Method)This indicates that the network was unavailable but due to unknown reason the connection with Oracle database did not drop. Therefore the process hang on on reading from database.
WOKRAROUND:
Restart the server. After restarting the server it was working correctly
PREVENTIVE TARGET:
-
Monitor ETL job status regularly. This is a first step during an investigation if the report displays old data. You should go to jts and ccm reports page to see when the jobs finished successfully last time
-
Upgrade to the latest CLM version. Since version 5.0 there has been introduced DCC component to run ETL jobs. Since 6.0 this is the only way to gather ETL job.