You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Igor Drobiazko (JIRA)" <ji...@apache.org> on 2010/05/26 09:08:33 UTC
[jira] Closed: (TAP5-978) Provide remote management of the page
pool settings
[ https://issues.apache.org/jira/browse/TAP5-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Drobiazko closed TAP5-978.
-------------------------------
Assignee: Igor Drobiazko
Fix Version/s: 5.2.0
Resolution: Fixed
> 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
> Assignee: Igor Drobiazko
> Fix For: 5.2.0
>
>
> 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.