September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5542) Upgrade to Remoting JMX 1.0.5.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-5542: ------------------------------------- Summary: Upgrade to Remoting JMX 1.0.5.Final Key: AS7-5542 URL: https://issues.jboss.org/browse/AS7-5542 Project: Application Server 7 Issue Type: Task Components: JMX, Remoting Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.4.Final (EAP) -- 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, 9 months

1
0
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.1.0.CR1 (was: 1.1.0.Beta1) > 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.1.0.CR1 > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-44) Allow a connection to be established where there is an existing Remoting Connection

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-44: -------------------------------------- Summary: Allow a connection to be established where there is an existing Remoting Connection Key: REMJMX-44 URL: https://issues.jboss.org/browse/REMJMX-44 Project: Remoting JMX Issue Type: Task Components: Connection Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 1.1.0.Beta1 This is closely related to REMJMX-43 - one motivation for that task is re-use of existing Remoting connections so Remoting JMX needs to be able to use the connection without interfering with it. -- 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

13 years, 9 months

1
4
0 / 0

[JBoss JIRA] (REMJMX-43) Add support for an MBeanServer / MBeanServerConnection locator

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-43: -------------------------------------- Summary: Add support for an MBeanServer / MBeanServerConnection locator Key: REMJMX-43 URL: https://issues.jboss.org/browse/REMJMX-43 Project: Remoting JMX Issue Type: Task Components: Connection Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta1 The idea of adding a 'locator' is so that we can add a query string to the request URL and this can contain additional information to call out to a locator to find either the referenced MBeanServer or MBeanServerConnection. The Remoting JMX side of the implementation is just to add the locator API and to make use of it including the addition of support for query string. One place to consider using this is within AS7 where a connection will be made to the master domain controller and the query string will identify a process to manage - the locator will then either return the MBeanServer or MBeanServerConnection - the end result will be that the master process becomes a proxy to the other processes providing a shared entry point and shared connections to other processes to be managed. -- 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

13 years, 9 months

1
4
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 resolved REMJMX-12. ------------------------------------ Resolution: Done > 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 > Assignee: Darran Lofthouse > Priority: Blocker > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-50) Client must eliminate unsupported versions from the list.

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-50: -------------------------------------- Summary: Client must eliminate unsupported versions from the list. Key: REMJMX-50 URL: https://issues.jboss.org/browse/REMJMX-50 Project: Remoting JMX Issue Type: Bug Components: Connection Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 1.0.5.CR1 At the moment the client just iterates to find the highest version - however unsupported versions should have been dropped from the list (so should banned versions) This means when we add version 0x02 existing clients break. Need to find a way to add the versions without breaking the existing clients. One option may be to add version 0x00 existing clients will not use this as 0x01 is higher - if a client selects 0x00 then begin negotiating the version again. -- 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

13 years, 9 months

1
3
0 / 0

[JBoss JIRA] (REMJMX-47) Refactor the RemotingConnectorServer / JMXConnectorServer to pull initial comms earlier

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-47: -------------------------------------- Summary: Refactor the RemotingConnectorServer / JMXConnectorServer to pull initial comms earlier Key: REMJMX-47 URL: https://issues.jboss.org/browse/REMJMX-47 Project: Remoting JMX Issue Type: Task Components: Connection Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.4.CR1 The JMXConnectorServer implementation is supposed to associate incoming connections with a single MBean server - with the addition of an MBeanServerLocator in addition to the possibility of proxied requests to a remote MBeanServer there is also the possibility of multiple MBeanServers in the same process. Once a connection is established the connection is associated with the RemotingConnectorServer so the selection of MBeanServer / RemotingConnectorServer needs to happen before this. For version 2 of the protocol this association should happen after begin() is called i.e. the initial message exchange allows for the key/value pairs to be set to select the MBeanServer and then when begin is called the final association occurs. For version 1 we will be assuming only one MBeanServer or the MBeanServerLocator will need to select one with no properties, in this case will will assume begin has been called as soon as the connection is established. Although this change will move some of the initial negotiation of the connection out of the RemotingConnectorServer it is MANDATORY that for the initial version negotiation and for version 1 that there are no alterations to the protocol - version 2 however is a new protocol so AFTER it has been selected the protocol can diverge. -- 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

13 years, 9 months

1
3
0 / 0

[JBoss JIRA] (REMJMX-51) Add a test that tests all protocol versions currently run.

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-51: -------------------------------------- Summary: Add a test that tests all protocol versions currently run. Key: REMJMX-51 URL: https://issues.jboss.org/browse/REMJMX-51 Project: Remoting JMX Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.5.CR1 This is a fairly simple smoke test that will test each version, to achieve this all other versions will be excluded, the server will be started and then the client will make a series of calls. As new versions are added later this test will automatically run the same test for them all. -- 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

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] (JGRP-1513) windows and linux

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1513?page=com.atlassian.jira.plugin.... ] Bela Ban deleted JGRP-1513: --------------------------- > windows and linux > ----------------- > > Key: JGRP-1513 > URL: https://issues.jboss.org/browse/JGRP-1513 > Project: JGroups > Issue Type: Bug > Reporter: Balamurali L > Assignee: Bela Ban > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1499) Configuration error message references "start_port" property that does not exist

by Dennis Reed (JIRA)

Dennis Reed created JGRP-1499: --------------------------------- Summary: Configuration error message references "start_port" property that does not exist Key: JGRP-1499 URL: https://issues.jboss.org/browse/JGRP-1499 Project: JGroups Issue Type: Bug Affects Versions: 3.0.11 Reporter: Dennis Reed Assignee: Dennis Reed Error message refers to the TCP "start_port" property which has been replaced with "bind_port". Error: java.lang.IllegalArgumentException: start_port cannot be set to 0, as no dynamic discovery protocol (e.g. MPING or TCPGOSSIP) has been detected. at org.jgroups.protocols.BasicTCP.init(BasicTCP.java:74) at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:847) at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:469) at org.jgroups.JChannel.init(JChannel.java:795) at org.jgroups.JChannel.<init>(JChannel.java:166) ... -- 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

13 years, 9 months

2
2
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 September 2012