You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Dominik Drzewiecki (JIRA)" <ji...@apache.org> on 2011/03/25 15:59:10 UTC

[jira] [Created] (WICKET-3558) Expose active requests via JMX

Expose active requests via JMX
------------------------------

                 Key: WICKET-3558
                 URL: https://issues.apache.org/jira/browse/WICKET-3558
             Project: Wicket
          Issue Type: Improvement
          Components: wicket-jmx
    Affects Versions: 1.4.16
            Reporter: Dominik Drzewiecki
            Priority: Minor


It'd be nice if RequestLogger.active was exposed via JMX in the same manner the RequestLogger.liveSessions.size() is. Moreover it'd be great to track and expose the peak number of concurrent (active) requests.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (WICKET-3558) Expose active requests via JMX

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Drzewiecki updated WICKET-3558:
---------------------------------------

    Attachment: exposeActiveViaJMX-1.5.patch

> Expose active requests via JMX
> ------------------------------
>
>                 Key: WICKET-3558
>                 URL: https://issues.apache.org/jira/browse/WICKET-3558
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-jmx
>    Affects Versions: 1.4.16
>            Reporter: Dominik Drzewiecki
>            Priority: Minor
>         Attachments: exposeActiveViaJMX-1.4.patch, exposeActiveViaJMX-1.5.patch, exposeActiveViaJMX.patch
>
>
> It'd be nice if RequestLogger.active was exposed via JMX in the same manner the RequestLogger.liveSessions.size() is. Moreover it'd be great to track and expose the peak number of concurrent (active) requests.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (WICKET-3558) Expose active requests via JMX

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Drzewiecki updated WICKET-3558:
---------------------------------------

    Attachment: exposeActiveViaJMX-1.4.patch

> Expose active requests via JMX
> ------------------------------
>
>                 Key: WICKET-3558
>                 URL: https://issues.apache.org/jira/browse/WICKET-3558
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-jmx
>    Affects Versions: 1.4.16
>            Reporter: Dominik Drzewiecki
>            Priority: Minor
>         Attachments: exposeActiveViaJMX-1.4.patch, exposeActiveViaJMX-1.5.patch, exposeActiveViaJMX.patch
>
>
> It'd be nice if RequestLogger.active was exposed via JMX in the same manner the RequestLogger.liveSessions.size() is. Moreover it'd be great to track and expose the peak number of concurrent (active) requests.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (WICKET-3558) Expose active requests via JMX

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Drzewiecki updated WICKET-3558:
---------------------------------------

    Affects Version/s: 1.5-RC2

> Expose active requests via JMX
> ------------------------------
>
>                 Key: WICKET-3558
>                 URL: https://issues.apache.org/jira/browse/WICKET-3558
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-jmx
>    Affects Versions: 1.4.16, 1.5-RC2
>            Reporter: Dominik Drzewiecki
>            Priority: Minor
>         Attachments: exposeActiveViaJMX-1.4.patch, exposeActiveViaJMX-1.5.patch
>
>
> It'd be nice if RequestLogger.active was exposed via JMX in the same manner the RequestLogger.liveSessions.size() is. Moreover it'd be great to track and expose the peak number of concurrent (active) requests.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (WICKET-3558) Expose active requests via JMX

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Drzewiecki updated WICKET-3558:
---------------------------------------

    Attachment:     (was: exposeActiveViaJMX-1.4.patch)

> Expose active requests via JMX
> ------------------------------
>
>                 Key: WICKET-3558
>                 URL: https://issues.apache.org/jira/browse/WICKET-3558
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-jmx
>    Affects Versions: 1.4.16
>            Reporter: Dominik Drzewiecki
>            Priority: Minor
>         Attachments: exposeActiveViaJMX-1.4.patch, exposeActiveViaJMX-1.5.patch, exposeActiveViaJMX.patch
>
>
> It'd be nice if RequestLogger.active was exposed via JMX in the same manner the RequestLogger.liveSessions.size() is. Moreover it'd be great to track and expose the peak number of concurrent (active) requests.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (WICKET-3558) Expose active requests via JMX

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Drzewiecki updated WICKET-3558:
---------------------------------------

    Attachment:     (was: exposeActiveViaJMX-1.5.patch)

> Expose active requests via JMX
> ------------------------------
>
>                 Key: WICKET-3558
>                 URL: https://issues.apache.org/jira/browse/WICKET-3558
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-jmx
>    Affects Versions: 1.4.16, 1.5-RC2
>            Reporter: Dominik Drzewiecki
>            Priority: Minor
>         Attachments: exposeActiveViaJMX-1.4.patch, exposeActiveViaJMX-1.5.patch
>
>
> It'd be nice if RequestLogger.active was exposed via JMX in the same manner the RequestLogger.liveSessions.size() is. Moreover it'd be great to track and expose the peak number of concurrent (active) requests.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (WICKET-3558) Expose active requests via JMX

Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011231#comment-13011231 ] 

Martin Grigorov commented on WICKET-3558:
-----------------------------------------

Provide a patch please.
Thanks!

> Expose active requests via JMX
> ------------------------------
>
>                 Key: WICKET-3558
>                 URL: https://issues.apache.org/jira/browse/WICKET-3558
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-jmx
>    Affects Versions: 1.4.16
>            Reporter: Dominik Drzewiecki
>            Priority: Minor
>         Attachments: exposeActiveViaJMX.patch
>
>
> It'd be nice if RequestLogger.active was exposed via JMX in the same manner the RequestLogger.liveSessions.size() is. Moreover it'd be great to track and expose the peak number of concurrent (active) requests.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (WICKET-3558) Expose active requests via JMX

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Drzewiecki updated WICKET-3558:
---------------------------------------

    Attachment:     (was: exposeActiveViaJMX.patch)

> Expose active requests via JMX
> ------------------------------
>
>                 Key: WICKET-3558
>                 URL: https://issues.apache.org/jira/browse/WICKET-3558
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-jmx
>    Affects Versions: 1.4.16, 1.5-RC2
>            Reporter: Dominik Drzewiecki
>            Priority: Minor
>         Attachments: exposeActiveViaJMX-1.4.patch, exposeActiveViaJMX-1.5.patch
>
>
> It'd be nice if RequestLogger.active was exposed via JMX in the same manner the RequestLogger.liveSessions.size() is. Moreover it'd be great to track and expose the peak number of concurrent (active) requests.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (WICKET-3558) Expose active requests via JMX

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Drzewiecki updated WICKET-3558:
---------------------------------------

    Attachment: exposeActiveViaJMX-1.5.patch

> Expose active requests via JMX
> ------------------------------
>
>                 Key: WICKET-3558
>                 URL: https://issues.apache.org/jira/browse/WICKET-3558
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-jmx
>    Affects Versions: 1.4.16, 1.5-RC2
>            Reporter: Dominik Drzewiecki
>            Priority: Minor
>         Attachments: exposeActiveViaJMX-1.4.patch, exposeActiveViaJMX-1.5.patch
>
>
> It'd be nice if RequestLogger.active was exposed via JMX in the same manner the RequestLogger.liveSessions.size() is. Moreover it'd be great to track and expose the peak number of concurrent (active) requests.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (WICKET-3558) Expose active requests via JMX

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Drzewiecki updated WICKET-3558:
---------------------------------------

    Attachment: exposeActiveViaJMX-1.4.patch

This one supersedes exposeActiveViaJMX.patch which appears to miss one class modifcations.

> Expose active requests via JMX
> ------------------------------
>
>                 Key: WICKET-3558
>                 URL: https://issues.apache.org/jira/browse/WICKET-3558
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-jmx
>    Affects Versions: 1.4.16
>            Reporter: Dominik Drzewiecki
>            Priority: Minor
>         Attachments: exposeActiveViaJMX-1.4.patch, exposeActiveViaJMX-1.5.patch, exposeActiveViaJMX.patch
>
>
> It'd be nice if RequestLogger.active was exposed via JMX in the same manner the RequestLogger.liveSessions.size() is. Moreover it'd be great to track and expose the peak number of concurrent (active) requests.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (WICKET-3558) Expose active requests via JMX

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Drzewiecki updated WICKET-3558:
---------------------------------------

    Attachment: exposeActiveViaJMX.patch

> Expose active requests via JMX
> ------------------------------
>
>                 Key: WICKET-3558
>                 URL: https://issues.apache.org/jira/browse/WICKET-3558
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-jmx
>    Affects Versions: 1.4.16
>            Reporter: Dominik Drzewiecki
>            Priority: Minor
>         Attachments: exposeActiveViaJMX.patch
>
>
> It'd be nice if RequestLogger.active was exposed via JMX in the same manner the RequestLogger.liveSessions.size() is. Moreover it'd be great to track and expose the peak number of concurrent (active) requests.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (WICKET-3558) Expose active requests via JMX

Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-3558.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5-RC3
                   1.4.17
         Assignee: Martin Grigorov

Added with r1085992 (trunk) and r1085993 (1.4.x).
Thanks!

> Expose active requests via JMX
> ------------------------------
>
>                 Key: WICKET-3558
>                 URL: https://issues.apache.org/jira/browse/WICKET-3558
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-jmx
>    Affects Versions: 1.4.16, 1.5-RC2
>            Reporter: Dominik Drzewiecki
>            Assignee: Martin Grigorov
>            Priority: Minor
>             Fix For: 1.4.17, 1.5-RC3
>
>         Attachments: exposeActiveViaJMX-1.4.patch, exposeActiveViaJMX-1.5.patch
>
>
> It'd be nice if RequestLogger.active was exposed via JMX in the same manner the RequestLogger.liveSessions.size() is. Moreover it'd be great to track and expose the peak number of concurrent (active) requests.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira