Skip to content

server.xml - StuckThreadDetectionValve introduced in 7.6.12 #339

@mojibake-umd

Description

@mojibake-umd

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions