Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

server.xml - StuckThreadDetectionValve introduced in 7.6.12 #339

Closed
mojibake-umd opened this issue Feb 4, 2021 · 0 comments · Fixed by #348
Closed

server.xml - StuckThreadDetectionValve introduced in 7.6.12 #339

mojibake-umd opened this issue Feb 4, 2021 · 0 comments · Fixed by #348

Comments

@mojibake-umd
Copy link

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 5.5.12
  • Ruby:
  • Distribution: Redhat
  • Module version: 4.0.1

How to reproduce (e.g Puppet code you use)

puppet-jira

What are you seeing

Atlassian added
below scanManifest in server.cml https://github.com/voxpupuli/puppet-jira/blob/master/templates/server.xml.erb#L139
starting in version 7.6.12.

What behaviour did you expect instead

Expected settings delivered by vendor to be included in server.xml
https://jira.atlassian.com/browse/JRASERVER-60546

Output log

(/Stage[main]/Jira::Config/File[/opt/jira/atlassian-jira-software-8.13.3-standalone/conf/server.xml]/content)

  •                <Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="120" />
    

Any additional information you'd like to impart

Valid values are 0-600.
Setting to 0 will disable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant