Problems with the agent after updating Java 21

Avatar
Victorvf13 Vvf
Created

Hi, I recently had a problem with my TeamCity application. I wanted to update Java 17 to Java 21 because TeamCity required the new version. On my AWS EC2 server, I have a service focused on TeamCity. I connected to the terminal and updated it from there. I restarted TeamCity using commands. The agent had already been updated when I tried to build, but I got an error: the TeamCity connection to my GitLab was lost, and it wouldn't deploy. I decided to create a new token, configured it in the TeamCity build, and the connection was successful. However, the build process wouldn't start when I clicked "Run." Everything I built, although it was successful, on my displayed page it only shows a 500 error. Please help.

Votes

0

Share

1 comment
Avatar
Tom Sun
Created

Hi,

Thanks for reaching out. To investigate this, we need a bit more information about your setup and the errors you are seeing. Could you share the following?

  1. TeamCity version. You can find it on the About page of your TeamCity server, or in the first lines of teamcity-server.log.
  2. A browser Network Trace and screenshots of the issue.
    • Open your browser's Developer Tools (F12) and switch to the Network tab.
    • Enable Preserve log and reproduce the issue (for example, click Run on the build configuration or open the page that returns HTTP 500).
    • Export the captured network activity as a HAR file and send it to us.
    • Please also provide screenshots of any error pages, messages, or unexpected behavior you observe in the browser.
  3. teamcity-server.log excerpts cover two moments:
    • When you click Run on a build configuration and nothing happens.
    • When you open the build result page, that returns HTTP 500.
  4. Details about the Java runtime used by the TeamCity server.
    • Which Java 21 distribution did you switch to (Oracle JDK, OpenJDK, Amazon Corretto, Temurin, etc.)?
    • Please also provide the output of java -version from the machine running the TeamCity server.
  5. Build agent details.
    • Does the build agent run on the same EC2 instance as the TeamCity server, or on a separate host?
    • Which Java version is currently being used by the agent process?

Large files can be uploaded via https://uploads.jetbrains.com/. Please let us know the exact id after the upload.

Looking forward to your reply.

0

Please sign in to leave a comment.