[JBoss JIRA] (ISPN-2955) Async marshalling executor retry when queue fills
by Manik Surtani (JIRA)
[ https://issues.jboss.org/browse/ISPN-2955?page=com.atlassian.jira.plugin.... ]
Manik Surtani reassigned ISPN-2955:
-----------------------------------
Assignee: Manik Surtani (was: Galder Zamarreño)
> Async marshalling executor retry when queue fills
> -------------------------------------------------
>
> Key: ISPN-2955
> URL: https://issues.jboss.org/browse/ISPN-2955
> Project: Infinispan
> Issue Type: Enhancement
> Components: Marshalling
> Affects Versions: 5.2.5.Final
> Reporter: Manik Surtani
> Assignee: Manik Surtani
> Fix For: 5.3.0.Alpha1, 5.3.0.Final
>
>
> When using an async transport and async marshalling, an executor is used to process the marshalling task in a separate thread and the caller's thread is allowed to return immediately.
> When the executor's queue fills and the queue cannot accept any more tasks, it throws a {{RejectedExecutionException}}, causing a very bad user/developer experience. A more correct approach to this is to catch the {{RejectedExecutionException}}, block and retry the task submission.
> The end result is that, in the degenerate case (when the executor queue is full) instead of throwing exceptions, those invocations will perform slightly slower.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (ISPN-2953) Alternate statistics MBeans to allow for a Hawt.io Infinispan plugin
by James Strachan (JIRA)
[ https://issues.jboss.org/browse/ISPN-2953?page=com.atlassian.jira.plugin.... ]
James Strachan commented on ISPN-2953:
--------------------------------------
FWIW we're using the canonical ObjectName. As it happens though I've just worked around it by making a custom tree UI in hawtio for infinispan. So from my perspective I'm happy for you to close this issue now. Though I do think it'd be nice for the MBeans to appear a little nicer in all other JMX tools; but personally am less bothered now we've a nice hawtio plugin :)
> Alternate statistics MBeans to allow for a Hawt.io Infinispan plugin
> --------------------------------------------------------------------
>
> Key: ISPN-2953
> URL: https://issues.jboss.org/browse/ISPN-2953
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Affects Versions: 5.2.5.Final
> Reporter: Manik Surtani
> Assignee: Manik Surtani
> Fix For: 5.3.0.Alpha1, 5.3.0.Final
>
> Attachments: hawtio-infinispan.png
>
>
> Hawt.io draws its MBean trees in a manner different from what RHQ does, and the existing statistics MBean is hard to consume from Hawt.io.
> This feature request is to register an alternate set of MBeans if a flag is passed in ({{-Dinfinispan.jmx.alternate_name_order=true}}?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (ISPN-2953) Alternate statistics MBeans to allow for a Hawt.io Infinispan plugin
by James Strachan (JIRA)
[ https://issues.jboss.org/browse/ISPN-2953?page=com.atlassian.jira.plugin.... ]
James Strachan updated ISPN-2953:
---------------------------------
Attachment: hawtio-infinispan.png
Here's the current screen shot in case anyone's interested
> Alternate statistics MBeans to allow for a Hawt.io Infinispan plugin
> --------------------------------------------------------------------
>
> Key: ISPN-2953
> URL: https://issues.jboss.org/browse/ISPN-2953
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Affects Versions: 5.2.5.Final
> Reporter: Manik Surtani
> Assignee: Manik Surtani
> Fix For: 5.3.0.Alpha1, 5.3.0.Final
>
> Attachments: hawtio-infinispan.png
>
>
> Hawt.io draws its MBean trees in a manner different from what RHQ does, and the existing statistics MBean is hard to consume from Hawt.io.
> This feature request is to register an alternate set of MBeans if a flag is passed in ({{-Dinfinispan.jmx.alternate_name_order=true}}?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (ISPN-2953) Alternate statistics MBeans to allow for a Hawt.io Infinispan plugin
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-2953?page=com.atlassian.jira.plugin.... ]
Adrian Nistor commented on ISPN-2953:
-------------------------------------
Let's not 'fix' this in infinispan. Whoever needs those properties ordered should use ObjectName.getCannonicalName().
> Alternate statistics MBeans to allow for a Hawt.io Infinispan plugin
> --------------------------------------------------------------------
>
> Key: ISPN-2953
> URL: https://issues.jboss.org/browse/ISPN-2953
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Affects Versions: 5.2.5.Final
> Reporter: Manik Surtani
> Assignee: Manik Surtani
> Fix For: 5.3.0.Alpha1, 5.3.0.Final
>
>
> Hawt.io draws its MBean trees in a manner different from what RHQ does, and the existing statistics MBean is hard to consume from Hawt.io.
> This feature request is to register an alternate set of MBeans if a flag is passed in ({{-Dinfinispan.jmx.alternate_name_order=true}}?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (ISPN-2953) Alternate statistics MBeans to allow for a Hawt.io Infinispan plugin
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-2953?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant commented on ISPN-2953:
---------------------------------------
There is no harm in ordering the mbean properties in a way that makes it apparently easier for hawt.io to do its thing, i.e. this won't break the RHQ plugin which queries the MBean server using proper queries. So, from a strictly technical point of view there are no drawbacks, as long as clients understand that they depend on ordering just by chance.
And please do not introduce hacky env variables :)
> Alternate statistics MBeans to allow for a Hawt.io Infinispan plugin
> --------------------------------------------------------------------
>
> Key: ISPN-2953
> URL: https://issues.jboss.org/browse/ISPN-2953
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Affects Versions: 5.2.5.Final
> Reporter: Manik Surtani
> Assignee: Manik Surtani
> Fix For: 5.3.0.Alpha1, 5.3.0.Final
>
>
> Hawt.io draws its MBean trees in a manner different from what RHQ does, and the existing statistics MBean is hard to consume from Hawt.io.
> This feature request is to register an alternate set of MBeans if a flag is passed in ({{-Dinfinispan.jmx.alternate_name_order=true}}?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years