12:06 p.m.
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
3:45 a.m.
[
https://issues.jboss.org/browse/REMJMX-50?page=com.atlassian.jira.plugin....
]
Darran Lofthouse commented on REMJMX-50:
----------------------------------------
This issue highlights one important point, although the version negotiation is supposed to
be only in terms of protocol versions had the client and server exchanged their own
version then it would have been possible to place a work around in the server side for the
older clients to prevent the error from occurring - on adding support for version 0x00 to
trigger another round of version negotiation I will also exchange client and server
versions.
This information would also be useful server side anyway, should a problem be identified
in the future it may be the easiest way to double check the version of remoting jmx in use
by the remote clients without needing to visit each manually.
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
6:16 a.m.
[
https://issues.jboss.org/browse/REMJMX-50?page=com.atlassian.jira.plugin....
]
Darran Lofthouse updated REMJMX-50:
-----------------------------------
Fix Version/s: 1.1.0.Beta1
(was: 1.0.5.CR1)
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.1.0.Beta1
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:27 a.m.
[
https://issues.jboss.org/browse/REMJMX-50?page=com.atlassian.jira.plugin....
]
Darran Lofthouse resolved REMJMX-50.
------------------------------------
Resolution: Done
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.1.0.Beta1
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
4315
days inactive
4343
days old
3 comments
1 participants
participants (1)
-
Darran Lofthouse (JIRA)