March 2010 - jboss-remoting-issues

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

by Trustin Lee (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-827?page=com.atlassian.jira.plug... ] Trustin Lee reassigned JBREM-827: --------------------------------- Assignee: Trustin Lee > 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 > Assignee: Trustin Lee > Fix For: 3.1.0.Beta3 > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-1208) Remote client listener does not receive service open options

by David Lloyd (JIRA)

Remote client listener does not receive service open options ------------------------------------------------------------ Key: JBREM-1208 URL: https://jira.jboss.org/jira/browse/JBREM-1208 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 -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1080) Add support for future tasks to RequestContext

by David Lloyd (JIRA)

Add support for future tasks to RequestContext ---------------------------------------------- Key: JBREM-1080 URL: https://jira.jboss.org/jira/browse/JBREM-1080 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: r3 api Reporter: David Lloyd Fix For: 3.1.0.Beta1 Right now, the RequestContext keeps track of tasks and threads being used to process a request. If all tasks complete and no reply is sent, it makes sure that the requesting party receives an exception indicating that a reply was never sent. However, if the request listener may wish interact with another framework which uses some asynchronous callback mechanism, from which a reply is to be sent. In this case, all tasks terminate but the reply might still be sent. To solve this problem, RequestContext needs a method which can wrap a Runnable (or similar) with some type of cancellable Runnable or task object, which can then be called by other frameworks as needed later on. The RequestContext wouldn't consider a request "dead" until all tasks completed and all such wrapped Runnables have also been completed or GC'd. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBREM-1206) Address asymmetry between local & remote request & reply handlers

by David Lloyd (JIRA)

Address asymmetry between local & remote request & reply handlers ----------------------------------------------------------------- Key: JBREM-1206 URL: https://jira.jboss.org/jira/browse/JBREM-1206 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: r3 core, r3 core: api, r3 core: remote Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.1.0.Beta2 The asymmetry between using a RequestHandler for local vs. remote request handlers has reached a breaking point with call by value and service classloader association. Introduce Local/Remote variants of RequestHandlers and ReplyHandlers which have a class loader as a property. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-1205) Provide a way for the client to specify an unmarshalling classloader for a request

by David Lloyd (JIRA)

Provide a way for the client to specify an unmarshalling classloader for a request ---------------------------------------------------------------------------------- Key: JBREM-1205 URL: https://jira.jboss.org/jira/browse/JBREM-1205 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: r3 core, r3 core: api, r3 core: remote Reporter: David Lloyd Assignee: David Lloyd Priority: Minor Fix For: 3.1.0.Beta2 It should be an optional parameter which defaults to the TCCL, and failing that, perhaps the caller's classloader. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1203) Streams via "remote"

by David Lloyd (JIRA)

Streams via "remote" -------------------- Key: JBREM-1203 URL: https://jira.jboss.org/jira/browse/JBREM-1203 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 The six stream types over "remote"/"remote+ssl". -- 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, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-1207) Pass-by-value on "local:" protocol

by David Lloyd (JIRA)

Pass-by-value on "local:" protocol ---------------------------------- Key: JBREM-1207 URL: https://jira.jboss.org/jira/browse/JBREM-1207 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core, r3 core: api Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.1.0.Beta2 Use the new JBMAR cloner interface. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1167) Add simple socket based protocol to Remoting 3 samples

by Ron Sigal (JIRA)

Add simple socket based protocol to Remoting 3 samples ------------------------------------------------------ Key: JBREM-1167 URL: https://jira.jboss.org/jira/browse/JBREM-1167 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 3.1.0.Beta1 A simple protocol might help to clarify the concepts of Remoting 3. -- 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, 8 months

2
4
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: ------------------------------ Fix Version/s: 3.1.0.Beta3 (was: 3.1.0.Beta2) > 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.Beta3 > > -- 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, 8 months

1
0
0 / 0

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

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-918?page=com.atlassian.jira.plug... ] David Lloyd updated JBREM-918: ------------------------------ Fix Version/s: 3.1.0.Beta3 (was: 3.1.0.Beta2) > 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.Beta3 > > > 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, 8 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