[closed] Jazz server hang up "Error fetching the scr document for application"
Hi there,
we had a server hang up some minutes ago. The behaviour was that the browsers kept on "loading" and finished with an internal error after some time.
Full clients (e.g. Eclipse) did through error messages as well (don't know exactly which).
In the jts.log this error message is present once:
2013-07-23 09:09:45,157 [WebContainer : 13 @@ 09:08 <unauthenticated> /jts/service/com.ibm.team.repository.service.internal.license.ILicenseRestService/assertLicense] ERROR license.behavior.SCRBasedCompatibleLicenseBehavior - Error fetching the scr document for application at url: "https://jazz.rsint.net/ccm/scr"
java.net.SocketTimeoutException: Read timed out
After this error message we got plenty of warnings - containing everytime the same:
2013-07-23 09:11:45,613 [WebContainer : 43 @@ 09:08 <unauthenticated> /jts/service/com.ibm.team.repository.service.internal.license.ILicenseRestService/assertLicense] WARN ory.service.internal.license.FloatingLicenseClient - CRJAZ1272I The floating license available from "https://jazz.rsint.net/jts/service/com.ibm.team.repository.service.internal.license.IFloatingLicenseService/licenses/com.ibm.team.rtc.developer.floating-v3_b92a5960-cb65-11df-bd3b-0800200c9a66?includeFullJar=true" could not be downloaded. The floating license at that location will be ignored.
org.apache.http.conn.ConnectionPoolTimeoutException: Timeout waiting for connection
This took some minutes ( I think around 5 ) and everything worked fine again ...
There where no known changes before this. A server restart did not solve this problem - it got solved by time.
Anybody any idea what happened? Maybe there is something hugh which is coming for us?
Greetings,
Simon
we had a server hang up some minutes ago. The behaviour was that the browsers kept on "loading" and finished with an internal error after some time.
Full clients (e.g. Eclipse) did through error messages as well (don't know exactly which).
In the jts.log this error message is present once:
2013-07-23 09:09:45,157 [WebContainer : 13 @@ 09:08 <unauthenticated> /jts/service/com.ibm.team.repository.service.internal.license.ILicenseRestService/assertLicense] ERROR license.behavior.SCRBasedCompatibleLicenseBehavior - Error fetching the scr document for application at url: "https://jazz.rsint.net/ccm/scr"
java.net.SocketTimeoutException: Read timed out
After this error message we got plenty of warnings - containing everytime the same:
2013-07-23 09:11:45,613 [WebContainer : 43 @@ 09:08 <unauthenticated> /jts/service/com.ibm.team.repository.service.internal.license.ILicenseRestService/assertLicense] WARN ory.service.internal.license.FloatingLicenseClient - CRJAZ1272I The floating license available from "https://jazz.rsint.net/jts/service/com.ibm.team.repository.service.internal.license.IFloatingLicenseService/licenses/com.ibm.team.rtc.developer.floating-v3_b92a5960-cb65-11df-bd3b-0800200c9a66?includeFullJar=true" could not be downloaded. The floating license at that location will be ignored.
org.apache.http.conn.ConnectionPoolTimeoutException: Timeout waiting for connection
This took some minutes ( I think around 5 ) and everything worked fine again ...
There where no known changes before this. A server restart did not solve this problem - it got solved by time.
Anybody any idea what happened? Maybe there is something hugh which is coming for us?
Greetings,
Simon
The question has been closed for the following reason: "Problem is not reproducible or outdated" by rschoon Mar 23 '23, 9:43 a.m.
3 answers
Hello Simon,
Have you checked if you can reach https://jazz.rsint.net/ccm/scr manually (opening in web browser)?
This is a first step which you need to perform when the issue happens again.
From my experience, it is really difficult to investigate such issues. Many of them end up the request to check with network admin or without any clue.
Have you checked if you can reach https://jazz.rsint.net/ccm/scr manually (opening in web browser)?
This is a first step which you need to perform when the issue happens again.
From my experience, it is really difficult to investigate such issues. Many of them end up the request to check with network admin or without any clue.
