[
https://issues.apache.org/jira/browse/TAP5-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799303#action_12799303
]
Howard M. Lewis Ship commented on TAP5-978:
-------------------------------------------
I've been thinking that we may want to deprecate the hard-limit, as that is
actually implicit in the number of request processing threads configured by the
servlet container.
In addition, I'd like to extend the configuration options such that individual
pages could override the default limits, using the standard MetaDataLocator
approach.
> Provide remote management of the page pool settings
> ---------------------------------------------------
>
> Key: TAP5-978
> URL: https://issues.apache.org/jira/browse/TAP5-978
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core, tapestry-ioc
> Affects Versions: 5.1.0.5
> Reporter: Igor Drobiazko
>
> It would be very useful to expose the Tapestry applications for remote
> management by using the JMX API. This management should be limited to
> symbols:
> - tapestry.page-pool.soft-limit,
> - tapestry.page-pool.soft-wait
> - tapestry.page-pool.hard-limit
> - tapestry.page-pool.active-window
> Tapestry should register a MBean for editing of these page pool settings. A
> management tool such as JConsole can be used to edit these settings soon as
> an application becomes busy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
