March 2010 - jboss-remoting-issues

[JBoss JIRA] Created: (JBREM-1189) Graceful connection close

by David Lloyd (JIRA)

Graceful connection close ------------------------- Key: JBREM-1189 URL: https://jira.jboss.org/jira/browse/JBREM-1189 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: r3 core: api, r3 core: remote Reporter: David Lloyd Fix For: 3.1.0.Beta1 Design a mechanism for graceful connection shutdown. This could work in one of a few ways: 1. Refuse new clients, immediately close all clients, allow outstanding requests to finish 2. Refuse new clients, keep connection up until all clients are closed and all outstanding requests to finish #1 might be better - since requests have a finite lifespan but clients can hang around indifinitely. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (JBREM-1195) Support SASL EXTERNAL mechanism

by David Lloyd (JIRA)

Support SASL EXTERNAL mechanism ------------------------------- Key: JBREM-1195 URL: https://jira.jboss.org/jira/browse/JBREM-1195 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core: remote Reporter: David Lloyd Fix For: 3.1.0.CR1 In order to use any authentication credentials established by the outer security layer (i.e. SSL), SASL provides the EXTERNAL mechanism. We need to make sure we support this mechanism, including documentation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBREM-1204) Change the artifactId

by David Lloyd (JIRA)

Change the artifactId --------------------- Key: JBREM-1204 URL: https://jira.jboss.org/jira/browse/JBREM-1204 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.1.0.Beta2 The AS team wants R2 to coexist with R3 for a while. So they need distinct artifact IDs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-1200) Rescanning for SASL providers on every connection in or out

by David Lloyd (JIRA)

Rescanning for SASL providers on every connection in or out ----------------------------------------------------------- Key: JBREM-1200 URL: https://jira.jboss.org/jira/browse/JBREM-1200 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: r3 core: remote Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.1.0.Beta2 We should only scan for SASL providers when the protocol provider is constructed, and make up a map of mechanism to sasl*factory. This also allows us to add in a server-side EXTERNAL handler, which is necessarily tied to the protocol implementation in order to extract authentication data from the TLS layer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1202) Allow realm specification in connect URI

by David Lloyd (JIRA)

Allow realm specification in connect URI ---------------------------------------- Key: JBREM-1202 URL: https://jira.jboss.org/jira/browse/JBREM-1202 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: r3 core: api Reporter: David Lloyd Assignee: David Lloyd Priority: Minor Fix For: 3.1.0.Beta2 Syntax is: remote://host:123/ - use the user/realm configured in the OptionMap or client callback remote://user@host:123/ - use "user" as the authorization ID, realm is configured in the OptionMap or client callback remote://user;realm@host:123/ - user "user" as the authorization ID and "realm" as the default authentication realm -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1201) RequestListener.handleClose is redundant

by David Lloyd (JIRA)

RequestListener.handleClose is redundant ---------------------------------------- Key: JBREM-1201 URL: https://jira.jboss.org/jira/browse/JBREM-1201 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: r3 core: api Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.1.0.Beta2 If the user wants to take some action when the client closes, they should register a close handler on ClientContext. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1199) Add marshaller version to negotiation phase

by David Lloyd (JIRA)

Add marshaller version to negotiation phase ------------------------------------------- Key: JBREM-1199 URL: https://jira.jboss.org/jira/browse/JBREM-1199 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core: remote Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.1.0.Beta2 Identify the marshaller version so that if one side is using a newer version, it can "downgrade" to the greatest common version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1198) Determining whether to use SSL is clunky

by David Lloyd (JIRA)

Determining whether to use SSL is clunky ---------------------------------------- Key: JBREM-1198 URL: https://jira.jboss.org/jira/browse/JBREM-1198 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: r3 core: remote Affects Versions: 3.1.0.Beta1 Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.1.0.Beta2 There's no way to set up separate connectors to use SSL and non-SSL, nor is it easy to configure separate servers the same way. Split "remote" into "remote" and "remote+ssl" descriptors which differing default configurations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBREM-918) Make "remote:" resilient against connection failure

by Trustin Lee (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-918?page=com.atlassian.jira.plug... ] Trustin Lee commented on JBREM-918: ----------------------------------- Even if the connection was shut down gracefully, the client might want to connect again? We could simply keep the information for about 30 sec for example regardless if it is a graceful shutdown. +1 for dropping the in-flight requests with a distinguishable exception. > Make "remote:" resilient against connection failure > --------------------------------------------------- > > Key: JBREM-918 > URL: https://jira.jboss.org/jira/browse/JBREM-918 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: r3 core: remote > Reporter: David Lloyd > Fix For: 3.1.0.Beta2 > > > If a remote connection is dropped, it should be possible to re-establish the connection and resume the session, without the loss of any in-flight requests/contexts/services/etc. As a corollary, it might be worth exploring having more than one connection in a "bundle" to help parallelize the transit load and avoid head-of-line bottleneck problems. Perhaps it is worth looking into multihoming as well. > SSL contexts might be useful here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-827) Define a management interface for JBoss Remoting

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-827?page=com.atlassian.jira.plug... ] David Lloyd updated JBREM-827: ------------------------------ Component/s: r3 core > Define a management interface for JBoss Remoting > ------------------------------------------------ > > Key: JBREM-827 > URL: https://jira.jboss.org/jira/browse/JBREM-827 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: r3 core > Reporter: David Lloyd > Fix For: 3.1.0.Beta2 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues March 2010