We have Jenkins 1.509.2 + Sonar 3.6.1. And receive the below error, We didn't have the same error with Sonar 3.4.1 from which we upgraded. Could you advise how can we fix the issue?
Exception in thread "main" org.sonar.runner.RunnerException: org.sonar.api.utils.SonarException: Unable to request: /batch_bootstrap/properties
at org.sonar.runner.Runner.delegateExecution(Runner.java:288)
at org.sonar.runner.Runner.execute(Runner.java:151)
at org.sonar.runner.Main.execute(Main.java:84)
at org.sonar.runner.Main.main(Main.java:56)
Caused by: org.sonar.api.utils.SonarException: Unable to request: /batch_bootstrap/properties
at org.sonar.batch.bootstrap.ServerClient.request(ServerClient.java:82)
at org.sonar.batch.bootstrap.ServerClient.request(ServerClient.java:72)
at org.sonar.batch.bootstrap.BatchSettings.downloadSettings(BatchSettings.java:96)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
The error is not received every time - more like 90%. After I have upgraded all the Installed plugins, the error disappeared, on the next day - it appeared again.
It appears for ALL the projects, small and big. The Jenkins server is far (network wise) - from the Sonar server on most of the projects, but we also have projects that are in the same location with Sonar - and still receive this issue. Is there a workaround at least to increase the timeout?
We are seeing a similar error after upgrading from 3.4.1 to 3.6. The problem is not as severe as your (maybe 30% rather than 90%). Like your experience it is not limited to one project (errors in 2 out of every 7 builds). Restarting Sonar seems to help but does not always make it go away. Also, call me crazy but adding a -X flag to the maven build command has so far been the most reliable workaround. FYI, our builds are running on the same machine as the Sonar server (and the MySQL server).
Related
I am facing below issue while switch VS2019 to VS2022. I am not able to run my API project its throwing below error. I Search on google and look many articals but not got success. Please suggest to resolve this problem. I checked and found that .netCore upper version not support to old version code.
HTTP Error 500.37 - ANCM Failed to Start Within Startup Time Limit
Common solutions to this issue:
ANCM failed to start after -1 milliseconds
Troubleshooting steps:
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect
I am running apache beam java pipeline and for some reason getting lots of warning logs in GCP.
I tried changing log level of packages java.net,sun.rmi to SEVERE but still no success.
Logs are getting polluted with these warning messages. Any one else facing the same issue ?
jsonPayload: {
exception: "java.net.SocketTimeoutException: Accept timed out
at java.base/java.net.PlainSocketImpl.socketAccept(Native Method)
at java.base/java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:458)
at java.base/java.net.ServerSocket.implAccept(ServerSocket.java:551)
at java.base/java.net.ServerSocket.accept(ServerSocket.java:519)
at java.rmi/sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:394)
at java.rmi/sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:366)
at java.base/java.lang.Thread.run(Thread.java:834)
"
logger: "sun.rmi.transport.tcp"
message: "RMI TCP Accept-5555: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,localport=5555] throws"
Pipeline is simple : Pubsub to Postgres. No additional third party connectivity.
Please refer to public documentation about troubleshooting.
Select the job to view more detailed information on errors and run results. When you select a job, you can view the execution graph as well as some information about the job. Then, click the Logs button to view log messages generated by your pipeline code and the Dataflow service.
Another thing, that you can use is debug option. When running the gcloud command, you can include the option --verbosity=debug to get debugging output.
This might be related to a JVM bug. Please check Java SDK version snd upgrade to a newer (2.17.0 or higher) version.
Additionally, check Encoding errors, IOExceptions, or unexpected behavior in user code error.
I hope you find the above pieces of information useful.
I couldn't figure out the actual issue but in the mean time since it was polluting the logs traces added flag in pipeline options:
--workerLogLevelOverrides={"sun.rmi.transport.tcp":"OFF"}
I/we(the company) have a weird issue with Jenkins and the connection between Master and Slave.
After a while the connection is rejected/timed out for some reason.
We tried to start it as a Windows Service but that didn't go well(also error message). We try it again, maybe we didn't start it properly.
Below is the error Message(3) and the error from the Server(1) and slave(2)
How can we/I resolve this?
I read that this is still a bug in Jenkins but is there really no workaround?
1,2,3
After upgrading to Release Management 2013.4, we tried creating a release in the client that's also on 2013.4. We've repaired the server (looks like it needed to install .NET 4.5.1) but the error still is the same:
An unhandled exception has occurred in the application: The remote server returned an error: (500) Internal Server Error.\n at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at Microsoft.TeamFoundation.Release.Data.WebRequest.PlatformHttpClient.EndGetResponse...
When we look at the logs, we get a ton of errors with system.servicemodel (webhost failed to process a request) and release management (data at the root level is invalid. line 2, position 1).
Any ideas what this is? We tried to enable detailed logging, but can't because we can't create a release.
Turns out that it's an issue with installing the RM server with HTTPS (default) when it needs to be HTTP. So when we uninstalled and reinstalled RM Server 2013.4 and configured it to HTTP, everything worked!
https://social.msdn.microsoft.com/Forums/vstudio/en-US/d0a9d3f1-05d1-4e4c-b44a-93e9bb4b9044/after-upgrading-to-release-management-update-2-i-cannot-deploy-anything?forum=tfsbuild
Sometime i will encounter this error after multiple access of my web application
I am using Sun Application Server Platform Edition 8.2
What is the reason for encountering this error and how to resolve it.
File system permissions issue perhaps. Need more information for a better answer.