April 2008 - jboss-remoting-issues

[JBoss JIRA] Created: (JBREM-964) Make InvocationFailureException extend java.rmi.MarshalException

by Ron Sigal (JIRA)

Make InvocationFailureException extend java.rmi.MarshalException ---------------------------------------------------------------- Key: JBREM-964 URL: http://jira.jboss.com/jira/browse/JBREM-964 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4.0.CR1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.4.0.GA In earlier versions of Remoting, org.jboss.remoting.transport.socket.SocketClientInvoker.handleException() and MicroSocketClientInvoker.handleException() wrapped many exceptions in a java.rmi.MarshalException, which could be misleading in some cases, so a new exception, org.jboss.remoting.InvocationFailureException, derived from java.io.IOException; was introduced to take its place. But the new exception changes the Remoting API, so a better solution would be to derive InvocationFailureException from MarshalException. -- 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

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBREM-914) Add a keepalive mechanism to JRPP

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-914?page=all ] David Lloyd closed JBREM-914. ----------------------------- Resolution: Done We'll call this done... > Add a keepalive mechanism to JRPP > --------------------------------- > > Key: JBREM-914 > URL: http://jira.jboss.com/jira/browse/JBREM-914 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: r3 JRPP > Reporter: David Lloyd > Assigned To: Trustin Lee > Fix For: 3.0.0-M2 > > Attachments: jbrem-914.diff > > > JRPP should be configurable to send a ping message at a regular interval. -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-896) Associate a ClassLoader on a per-client basis

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-896?page=all ] David Lloyd closed JBREM-896. ----------------------------- Resolution: Done Done. The classloader associated with a client will be the current thread's context classloader by default. ClassLoaders that are forwarded across the wire will be resurrected as RemoteClassLoaders. > Associate a ClassLoader on a per-client basis > --------------------------------------------- > > Key: JBREM-896 > URL: http://jira.jboss.com/jira/browse/JBREM-896 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: r3 core, r3 api > Reporter: David Lloyd > Fix For: 3.0.0-M2 > > > The MessageInput interface needs a way to associate that input with a context/request/stream/etc. (and therefore a classloader). A general classloader policy should be introduced - probably the context classloader of the thread making an invocation should be used as the basis to load any remote classes. Start a forum thread? -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-896) Associate a ClassLoader on a per-client basis

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-896?page=all ] David Lloyd updated JBREM-896: ------------------------------ Summary: Associate a ClassLoader on a per-client basis (was: Associate a ClassLoader on a per-context basis) > Associate a ClassLoader on a per-client basis > --------------------------------------------- > > Key: JBREM-896 > URL: http://jira.jboss.com/jira/browse/JBREM-896 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: r3 core, r3 api > Reporter: David Lloyd > Fix For: 3.0.0-M2 > > > The MessageInput interface needs a way to associate that input with a context/request/stream/etc. (and therefore a classloader). A general classloader policy should be introduced - probably the context classloader of the thread making an invocation should be used as the basis to load any remote classes. Start a forum thread? -- 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

16 years, 3 months

1
0
0 / 0

[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.0.0-M3 (was: 3.0.0-M2) > 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.0.0-M3 > > -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Work started: (JBREM-914) Add a keepalive mechanism to JRPP

by Trustin Lee (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-914?page=all ] Work on JBREM-914 started by Trustin Lee. > Add a keepalive mechanism to JRPP > --------------------------------- > > Key: JBREM-914 > URL: http://jira.jboss.com/jira/browse/JBREM-914 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: r3 JRPP > Reporter: David Lloyd > Assigned To: Trustin Lee > Fix For: 3.0.0-M2 > > Attachments: jbrem-914.diff > > > JRPP should be configurable to send a ping message at a regular interval. -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBREM-914) Add a keepalive mechanism to JRPP

by Trustin Lee (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-914?page=all ] Trustin Lee reassigned JBREM-914: --------------------------------- Assignee: Trustin Lee > Add a keepalive mechanism to JRPP > --------------------------------- > > Key: JBREM-914 > URL: http://jira.jboss.com/jira/browse/JBREM-914 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: r3 JRPP > Reporter: David Lloyd > Assigned To: Trustin Lee > Fix For: 3.0.0-M2 > > Attachments: jbrem-914.diff > > > JRPP should be configurable to send a ping message at a regular interval. -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-914) Add a keepalive mechanism to JRPP

by Trustin Lee (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-914?page=all ] Trustin Lee updated JBREM-914: ------------------------------ Attachment: jbrem-914.diff Here's the patch.. (somewhat dirty due to automatic cleaning in Eclipse) > Add a keepalive mechanism to JRPP > --------------------------------- > > Key: JBREM-914 > URL: http://jira.jboss.com/jira/browse/JBREM-914 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: r3 JRPP > Reporter: David Lloyd > Fix For: 3.0.0-M2 > > Attachments: jbrem-914.diff > > > JRPP should be configurable to send a ping message at a regular interval. -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-952) CLONE [JBREM-944] - Fix race in ConnectionNotifier

by Ron Sigal (JIRA)

CLONE [JBREM-944] - Fix race in ConnectionNotifier -------------------------------------------------- Key: JBREM-952 URL: http://jira.jboss.com/jira/browse/JBREM-952 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP4 Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.2.2.SP7 org.jboss.remoting.ConnectionNotifier.connectionTerminated() throws NullPointerExceptions from the following code: ConnectionListener[] list = (ConnectionListener[])listeners.toArray(new ConnectionListener[listeners.size()]); for(int x = 0; x < list.length; x++) { list[x].handleConnectionException(ex, client); // <<== NPE's thrown here } It seems that listeners got smaller between the call to listeners.size() and the call to listeners.toArray(), which could result in list having one or more null elements. -- 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

16 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-938) CLONE [JBREM-937] - Callback BisocketServerInvoker should reuse available ServerThreads

by Ron Sigal (JIRA)

CLONE [JBREM-937] - Callback BisocketServerInvoker should reuse available ServerThreads --------------------------------------------------------------------------------------- Key: JBREM-938 URL: http://jira.jboss.com/jira/browse/JBREM-938 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP5 Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.2.SP6 When org.jboss.remoting.transport.bisocket.BisocketServerInvoker.ControlConnectionThread.run() creates a new socket, it always creates a new org.jboss.remoting.transport.socket.ServerThread. Instead, it should look in org.jboss.remoting.transport.socket.SocketServerInvoker.threadpool for existing ServerThreads waiting to be reused. -- 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

16 years, 3 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues April 2008