February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (REMJMX-19) Optimise server side notifications to eliminate serialization issue re different instances of same filter and hand back server side.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-19?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-19: ----------------------------------- Fix Version/s: 1.1.0.Beta1 (was: 1.0.2.Final) > Optimise server side notifications to eliminate serialization issue re different instances of same filter and hand back server side. > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: REMJMX-19 > URL: https://issues.jboss.org/browse/REMJMX-19 > Project: Remoting JMX > Issue Type: Task > Components: Notifications > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta1 > > > The NotificationMBeanSupport class compares these items by identity so when different copies are received server side it breaks these comparisons. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-12) Allow for protocol versions to be excluded client and server side

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-12?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-12: ----------------------------------- Fix Version/s: 1.1.0.Beta1 (was: 1.0.2.Final) > Allow for protocol versions to be excluded client and server side > ----------------------------------------------------------------- > > Key: REMJMX-12 > URL: https://issues.jboss.org/browse/REMJMX-12 > Project: Remoting JMX > Issue Type: Task > Components: Connection > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta1 > > > Once we start supporting multiple versions of the protocols we should also allow version to be excluded client and server side. > This will mean if a version is identified as being problematic is can be excluded to force the use of a previous version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-4) Allow for long method calls within the protocol.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-4?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated REMJMX-4: ---------------------------------- Fix Version/s: 1.1.0.Beta1 (was: 1.0.2.Final) > Allow for long method calls within the protocol. > ------------------------------------------------ > > Key: REMJMX-4 > URL: https://issues.jboss.org/browse/REMJMX-4 > Project: Remoting JMX > Issue Type: Task > Components: Connection, RPC > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta1 > > > Methods such as invoke could take a long time to return depending on what the MBean is actually doing. > This task is to build support for this into the protocol, 2 initial ideas are: - > 1 - Allow the client to 'ping' the server after a request has timed out and ask the server is this request still running, server side the we can track the correlation IDs of current requests an check it is still in-progress. > 2 - The server could periodically send a message to the client to say the message is still in progress, the client could cache these and on timing out check if one has been received recently and wait again if one has. > 3 - Any other suggestions? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3921) Upgrade to Remoting JMX 1.0.2.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3921: ------------------------------------- Summary: Upgrade to Remoting JMX 1.0.2.Final Key: AS7-3921 URL: https://issues.jboss.org/browse/AS7-3921 Project: Application Server 7 Issue Type: Task Components: JMX Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 7.1.1.Final Need to pick up the other changes needed in Remoting JMX. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3899) Upgrade to Remoting JMX 1.0.1.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3899: ------------------------------------- Summary: Upgrade to Remoting JMX 1.0.1.Final Key: AS7-3899 URL: https://issues.jboss.org/browse/AS7-3899 Project: Application Server 7 Issue Type: Task Components: JMX, Remoting Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 7.1.1.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
4
0 / 0

[JBoss JIRA] (REMJMX-8) Connection state notification suppport

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-8?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated REMJMX-8: ---------------------------------- Fix Version/s: 1.0.2.Final (was: 1.0.1.Final) > Connection state notification suppport > -------------------------------------- > > Key: REMJMX-8 > URL: https://issues.jboss.org/browse/REMJMX-8 > Project: Remoting JMX > Issue Type: Task > Components: Connection, Notifications > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.2.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-4) Allow for long method calls within the protocol.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-4?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated REMJMX-4: ---------------------------------- Fix Version/s: 1.0.2.Final (was: 1.0.1.Final) > Allow for long method calls within the protocol. > ------------------------------------------------ > > Key: REMJMX-4 > URL: https://issues.jboss.org/browse/REMJMX-4 > Project: Remoting JMX > Issue Type: Task > Components: Connection, RPC > Reporter: Darran Lofthouse > Fix For: 1.0.2.Final > > > Methods such as invoke could take a long time to return depending on what the MBean is actually doing. > This task is to build support for this into the protocol, 2 initial ideas are: - > 1 - Allow the client to 'ping' the server after a request has timed out and ask the server is this request still running, server side the we can track the correlation IDs of current requests an check it is still in-progress. > 2 - The server could periodically send a message to the client to say the message is still in progress, the client could cache these and on timing out check if one has been received recently and wait again if one has. > 3 - Any other suggestions? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-19) Optimise server side notifications to eliminate serialization issue re different instances of same filter and hand back server side.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-19?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-19: ----------------------------------- Fix Version/s: 1.0.2.Final (was: 1.0.1.Final) > Optimise server side notifications to eliminate serialization issue re different instances of same filter and hand back server side. > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: REMJMX-19 > URL: https://issues.jboss.org/browse/REMJMX-19 > Project: Remoting JMX > Issue Type: Task > Components: Notifications > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.2.Final > > > The NotificationMBeanSupport class compares these items by identity so when different copies are received server side it breaks these comparisons. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-12) Allow for protocol versions to be excluded client and server side

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-12?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-12: ----------------------------------- Fix Version/s: 1.0.2.Final (was: 1.0.1.Final) > Allow for protocol versions to be excluded client and server side > ----------------------------------------------------------------- > > Key: REMJMX-12 > URL: https://issues.jboss.org/browse/REMJMX-12 > Project: Remoting JMX > Issue Type: Task > Components: Connection > Reporter: Darran Lofthouse > Fix For: 1.0.2.Final > > > Once we start supporting multiple versions of the protocols we should also allow version to be excluded client and server side. > This will mean if a version is identified as being problematic is can be excluded to force the use of a previous version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-10) Internationalisation of log messages

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-10?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-10: ----------------------------------- Fix Version/s: 1.0.2.Final (was: 1.0.1.Final) > Internationalisation of log messages > ------------------------------------ > > Key: REMJMX-10 > URL: https://issues.jboss.org/browse/REMJMX-10 > Project: Remoting JMX > Issue Type: Task > Reporter: Darran Lofthouse > Fix For: 1.0.2.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2012