Octopus Deploy v6.1.10 teamcity plugin needs restart to run.

[AmerihomeDavidOh]

We're having to restart teamcity daily in order to use this plugin.

Team City support stated the following: This issue boils down to octopus.teamcity.common.OctopusConstants cannot be resolved to a type error. The class in question may not be loaded with the rest of the plugin.

[rain-on]

Hi @AmerihomeDavidOh,

Is this on the server, or client side (I'm assuming server)?
Do you have a log to provide additional context?

cheers,

Trent.

[rain-on]

Hi @AmerihomeDavidOh,
If ok, I'd love to drill deeper into the issue:
When are you seeing this issue? eg. when attempting to execute an OctopusDeploy step, or when configuring a build configuration?

Following the server restart - do OctopusDeploy build steps operate correctly?

Are you able to add new OctopusDeploy steps to a build configuration when it is working correctly?

cheers,

Trent.

[AmerihomeDavidOh]

Hi Trent, 1) Is this server side or client side? *Server side* 2) When are we seeing this issue. Octopus Deploy Step or Configuring a build configuration. *Configuring a build* 3) Following the server restart - Does the OctopusDeploy build steps operate correctly? *Yes* 4) Are we able to add new OctopusDeploy steps to a build configuration when it's working correctly? *Yes, able to build step after restart.* Here are the error logs. ` [2022-02-14 11:51:36,353] ERROR - jetbrains.buildServer.SERVER - Error javax.servlet.jsp.JspException: javax.servlet.jsp.JspException: javax.servlet.jsp.JspException: javax.servlet.ServletException: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: [23] in the jsp file: [/plugins/Octopus.TeamCity/editOctopusPushPackage.jsp] octopus.teamcity.common.OctopusConstants cannot be resolved to a type 20: ~ limitations under the License. 21: --%> 22: 23: <jsp:useBean id="keys" class="octopus.teamcity.common.OctopusConstants" /> 24: <jsp:useBean id="propertiesBean" scope="request" type="jetbrains.buildServer.controllers.BasePropertiesBean"/> 25: 26: <l:settingsGroup title="Octopus Connection"> An error occurred at line: [23] in the jsp file: [/plugins/Octopus.TeamCity/editOctopusPushPackage.jsp] octopus.teamcity.common.OctopusConstants cannot be resolved to a type 20: ~ limitations under the License. 21: --%> 22: 23: <jsp:useBean id="keys" class="octopus.teamcity.common.OctopusConstants" /> 24: <jsp:useBean id="propertiesBean" scope="request" type="jetbrains.buildServer.controllers.BasePropertiesBean"/> 25: 26: <l:settingsGroup title="Octopus Connection"> An error occurred at line: [23] in the jsp file: [/plugins/Octopus.TeamCity/editOctopusPushPackage.jsp] octopus.teamcity.common.OctopusConstants cannot be resolved to a type 20: ~ limitations under the License. 21: --%> 22: 23: <jsp:useBean id="keys" class="octopus.teamcity.common.OctopusConstants" /> 24: <jsp:useBean id="propertiesBean" scope="request" type="jetbrains.buildServer.controllers.BasePropertiesBean"/> 25: 26: <l:settingsGroup title="Octopus Connection"> Stacktrace:; while processing request: GET '/admin/editRunType.html?id=buildType%3ADataServices_JobManager_Build&runnerId=__NEW_RUNNER__&cameFromUrl=%2Fadmin%2FeditBuildRunners.html%3Fid%3DbuildType%253ADataServices_JobManager_Build%26init%3D1&cameFromTitle=', from client 20.20.20.96 (10.50.142.93:51482), authenticated as 'hasan.sachdev' (Hasan Sachdev) {id=5} javax.servlet.jsp.JspException: javax.servlet.jsp.JspException: javax.servlet.jsp.JspException: javax.servlet.ServletException: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: [23] in the jsp file: [/plugins/Octopus.TeamCity/editOctopusPushPackage.jsp] octopus.teamcity.common.OctopusConstants cannot be resolved to a type 20: ~ limitations under the License. 21: --%> 22: 23: <jsp:useBean id="keys" class="octopus.teamcity.common.OctopusConstants" /> 24: <jsp:useBean id="propertiesBean" scope="request" type="jetbrains.buildServer.controllers.BasePropertiesBean"/> 25: 26: <l:settingsGroup title="Octopus Connection"> `

…

On Tue, Feb 22, 2022 at 3:24 PM Trent Mohay ***@***.***> wrote: Hi @AmerihomeDavidOh <https://github.com/AmerihomeDavidOh>, If ok, I'd love to drill deeper into the issue: When are you seeing this issue? eg. when attempting to execute an OctopusDeploy step, or when configuring a build configuration? Following the server restart - do OctopusDeploy build steps operate correctly? Are you able to add new OctopusDeploy steps to a build configuration when it is working correctly? cheers, Trent. — Reply to this email directly, view it on GitHub <#135 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARRTMTR2G3SEV3N2FHYDTOLU4QLJJANCNFSM5PCY2KNQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *David Oh* *Software Developer* AmeriHome Mortgage Company, LLC 1 Baxter Way, Suite 300 Thousand Oaks, CA 91362-3888 NMLS ID 135776 Direct Line: (747) 212-0885 Main Number (747) 800-4220 or Toll Free (888) 469-0810 amerihome.com

[jbristowe]

Hey @AmerihomeDavidOh! 👋 Thanks for this follow up.

After the server restart, the JSP is successfully displayed and you're able to configure a plugin operation (i.e. push package). I'm curious to know if the behaviour you've described happens on subsequent requests. That is, the error is displayed if the JSP is reloaded/refreshed. Or, it only occurs after a significant period of time -- say, later in the day.

Also, what version of TeamCity are you running?

[AmerihomeDavidOh]

Hmm, we use teamcity constantly throughout the day. From my knowledge this error occurs the following day after being unused overnight.

…

On Wed, Feb 23, 2022 at 10:48 AM John Bristowe ***@***.***> wrote: Hey @AmerihomeDavidOh <https://github.com/AmerihomeDavidOh>! 👋 Thanks for this follow up. After the server restart, the JSP is successfully displayed and you're able to configure a plugin operation (i.e. push package). I'm curious to know if the behaviour you've described happens on subsequent requests. That is, the error is displayed you reload the JSP. Or, it only occurs after a significant period of time -- say, later in the day. — Reply to this email directly, view it on GitHub <#135 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARRTMTWZWXMLBFWWD7OVRQDU4UTZHANCNFSM5PCY2KNQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *David Oh* *Software Developer* AmeriHome Mortgage Company, LLC 1 Baxter Way, Suite 300 Thousand Oaks, CA 91362-3888 NMLS ID 135776 Direct Line: (747) 212-0885 Main Number (747) 800-4220 or Toll Free (888) 469-0810 amerihome.com

[jbristowe]

I understand. This information helps. It sounds like this issue relates to class resolution and object lifetime of the bean.

[jbristowe]

What version of the plugin are you using? What version of TeamCity are you running?

[AmerihomeDavidOh]

TeamCity Enterprise <https://www.jetbrains.com/teamcity/?fromServer> 2021.2.2 (build 99660) Plugin version 6.1.10

…

On Wed, Feb 23, 2022 at 11:10 AM John Bristowe ***@***.***> wrote: What version of the plugin are you using? What version of TeamCity are you running? — Reply to this email directly, view it on GitHub <#135 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARRTMTQIXDQC3A4FZXJ6OOTU4UWLBANCNFSM5PCY2KNQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *David Oh* *Software Developer* AmeriHome Mortgage Company, LLC 1 Baxter Way, Suite 300 Thousand Oaks, CA 91362-3888 NMLS ID 135776 Direct Line: (747) 212-0885 Main Number (747) 800-4220 or Toll Free (888) 469-0810 amerihome.com

[jbristowe]

Is it possible there's a cron job running against your server that is modifying its system configuration? Is there a policy that runs on the server overnight?

[AmerihomeDavidOh]

Hi John, Not that I'm aware of, and the only thing we have scheduled is a cleanup, which is a built-in feature of teamcity.

[AmerihomeDavidOh]

Hi John, Just wanted to follow up, and see if there were any updates on this?

…

On Thu, Feb 24, 2022 at 8:31 AM David Oh ***@***.***> wrote: Hi John, Not that I'm aware of, and the only thing we have scheduled is a cleanup, which is a built-in feature of teamcity.

-- *David Oh* *Software Developer* AmeriHome Mortgage Company, LLC 1 Baxter Way, Suite 300 Thousand Oaks, CA 91362-3888 NMLS ID 135776 Direct Line: (747) 212-0885 Main Number (747) 800-4220 or Toll Free (888) 469-0810 amerihome.com

[johnsimons]

Hi @AmerihomeDavidOh,

I am sorry this hasn't been resolved yet.
We are not able to reproduce this issue and are not entirely sure what to do next.
It is my understanding you have contacted TeamCity support and they told you

This issue boils down to octopus.teamcity.common.OctopusConstants cannot be resolved to a type error. The class in question may not be loaded with the rest of the plugin.

Would you be able to go back to TeamCity support and ask them why does it work fine for a whole day and only starts failing after being unused overnight, wouldn't the code that throws octopus.teamcity.common.OctopusConstants cannot be resolved to a type error fail all the time?

[jbristowe]

Hey @AmerihomeDavidOh, thanks for the follow up. As @johnsimons indicates (above), you are observing non-normal behaviour. This behaviour hasn't been reported by customers elsewhere. We're at a loss to explain why this is happening, which is the reason why I asked if any tasks were being performed on your TeamCity machine overnight; it was the only logical conclusion we could deduce.

I would recommend going through your system logs to see if there are any events logged overnight. Some examples include group policy applications, system reboots, memory faults, etc. We suspect something is happening on the server that's causing the TeamCity process/plugin to "recycle" in some form. This results in weird behaviour once you go to use the plugin in the following morning.