June 2008 - jboss-remoting-issues

[JBoss JIRA] Updated: (JBREM-833) HTTP Transport Implementation

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-833?page=all ] David Lloyd updated JBREM-833: ------------------------------ Fix Version/s: 3.1.0.GA (was: 3.0.0-M3) > HTTP Transport Implementation > ----------------------------- > > Key: JBREM-833 > URL: http://jira.jboss.com/jira/browse/JBREM-833 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: David Lloyd > Assigned To: David Lloyd > Fix For: 3.1.0.GA > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Work stopped: (JBREM-833) HTTP Transport Implementation

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-833?page=all ] Work on JBREM-833 stopped by David Lloyd. > HTTP Transport Implementation > ----------------------------- > > Key: JBREM-833 > URL: http://jira.jboss.com/jira/browse/JBREM-833 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: David Lloyd > Assigned To: David Lloyd > Fix For: 3.1.0.GA > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-904) Remoting 1/2 protocol compatibility

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-904?page=all ] David Lloyd updated JBREM-904: ------------------------------ Summary: Remoting 1/2 protocol compatibility (was: Remoting 1/2 compatibility layer) Compatibility API is out of scope for now; we'll stick with just protocol compatibility. If it comes up later, a new ticket may be opened. > Remoting 1/2 protocol compatibility > ----------------------------------- > > Key: JBREM-904 > URL: http://jira.jboss.com/jira/browse/JBREM-904 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: David Lloyd > Fix For: 3.0.0-M3 > > > A protocol compatibility layer needs to be developed that allows a Remoting 3 server to respond to a Remoting 1/2 request, and also that allows a Remoting 3 client to connect to a Remoting 1/2 server. This will be required before integration with AS5 can be considered. > Another item worth exploration is looking into providing a Remoting 1/2 compatibilty API that allows legacy applications to use the newer transports. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-903) Add an optional JSSE layer to JRPP

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-903?page=all ] David Lloyd updated JBREM-903: ------------------------------ Fix Version/s: 3.1.0.GA (was: 3.0.0-M3) Moving to 3.1.0 to be included with an SSH transport. > Add an optional JSSE layer to JRPP > ---------------------------------- > > Key: JBREM-903 > URL: http://jira.jboss.com/jira/browse/JBREM-903 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: David Lloyd > Fix For: 3.1.0.GA > > > Some organizations are required to use approved technologies such as JSSE for connection encryption. We need to provide an optional JSSE security layer for the JRPP implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-918) Make JRPP resilient against connection failure

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-918?page=all ] David Lloyd updated JBREM-918: ------------------------------ Fix Version/s: 3.1.0.GA (was: 3.0.0-M3) Moving to 3.1.0.GA along with other JRPP issues > Make JRPP resilient against connection failure > ---------------------------------------------- > > Key: JBREM-918 > URL: http://jira.jboss.com/jira/browse/JBREM-918 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: r3 JRPP > Reporter: David Lloyd > Fix For: 3.1.0.GA > > > If a JRPP 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. Note that this looks a lot like a list of features that SCTP already has... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-925) SSLSocketBuilder config attribute names out of sync with v2.2 docs

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-925?page=all ] Ron Sigal updated JBREM-925: ---------------------------- Fix Version/s: 2.4.0.SP1 Assignee: Ron Sigal > SSLSocketBuilder config attribute names out of sync with v2.2 docs > ------------------------------------------------------------------ > > Key: JBREM-925 > URL: http://jira.jboss.com/jira/browse/JBREM-925 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: docs > Reporter: Tom Fennelly > Assigned To: Ron Sigal > Fix For: 2.4.0.SP1 > > > The latest docs available for download are for 2.2.0.GA (http://labs.jboss.org/jbossremoting/docs/index.html). > Table 5.1 (in pdf) outlines the attribute names for configuring the SSLSocketBuilder. They're not consistent with the actual definitions in the SSLSocketBuilder class, so errors result when used as per the docs. > In the ESB, we do a manual mapping of the names in code, so we get around the issue, but other users may be stumped. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-987) Release 2.4.0.GA

by Ron Sigal (JIRA)

Release 2.4.0.GA ---------------- Key: JBREM-987 URL: http://jira.jboss.com/jira/browse/JBREM-987 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.GA (Pinto) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues June 2008