May 2008 - jboss-remoting-issues - Jboss List Archives

[JBoss JIRA] Closed: (JBREM-816) Add instructions to Remoting Guide for overriding a transport or create a new transport

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-816?page=all ] Ron Sigal closed JBREM-816. --------------------------- Resolution: Done Added Chapter 6. Adding a New Transport. > Add instructions to Remoting Guide for overriding a transport or create a new transport > --------------------------------------------------------------------------------------- > > Key: JBREM-816 > URL: http://jira.jboss.com/jira/browse/JBREM-816 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.SP1 > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.4.0.GA (Pinto) > > > Client and server invokers are created by the org.jboss.remoting.InvokerRegistry class, which will look for classes called TransportClientFactory and TransportServerFactory in the directory org/jboss/remoting/transport/<transport> and use them to create client and server invokers for the <transport> transport. > The current discussion of this facility in the Remoting Guide is rather brief. -- 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-974) CLONE [JBREM-944] - Fix race in ConnectionNotifier

by Ron Sigal (JIRA)

CLONE [JBREM-944] - Fix race in ConnectionNotifier -------------------------------------------------- Key: JBREM-974 URL: http://jira.jboss.com/jira/browse/JBREM-974 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

15 years, 11 months

1
5
0 / 0

[JBoss JIRA] Closed: (JBREM-898) Fix encrypting marshaller/unmarshaller test cases

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-898?page=all ] Ron Sigal closed JBREM-898. --------------------------- Resolution: Won't Fix > Fix encrypting marshaller/unmarshaller test cases > ------------------------------------------------- > > Key: JBREM-898 > URL: http://jira.jboss.com/jira/browse/JBREM-898 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.SP4 > Reporter: Ron Sigal > > The following tests fail consistently: > org.jboss.test.remoting.marshall.encrypt.EncryptingMarshallerTestCase > org.jboss.test.remoting.marshall.encrypt.EncryptionStandaloneTestCase -- 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-898) Fix encrypting marshaller/unmarshaller test cases

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-898?page=all ] Ron Sigal updated JBREM-898: ---------------------------- Fix Version/s: (was: 2.4.0.CR1 (Pinto)) Removed fix version. > Fix encrypting marshaller/unmarshaller test cases > ------------------------------------------------- > > Key: JBREM-898 > URL: http://jira.jboss.com/jira/browse/JBREM-898 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.SP4 > Reporter: Ron Sigal > > The following tests fail consistently: > org.jboss.test.remoting.marshall.encrypt.EncryptingMarshallerTestCase > org.jboss.test.remoting.marshall.encrypt.EncryptionStandaloneTestCase -- 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] Reopened: (JBREM-898) Fix encrypting marshaller/unmarshaller test cases

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-898?page=all ] Ron Sigal reopened JBREM-898: ----------------------------- > Fix encrypting marshaller/unmarshaller test cases > ------------------------------------------------- > > Key: JBREM-898 > URL: http://jira.jboss.com/jira/browse/JBREM-898 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.SP4 > Reporter: Ron Sigal > > The following tests fail consistently: > org.jboss.test.remoting.marshall.encrypt.EncryptingMarshallerTestCase > org.jboss.test.remoting.marshall.encrypt.EncryptionStandaloneTestCase -- 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] Closed: (JBREM-894) Deprecate multiplex transport

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-894?page=all ] Ron Sigal closed JBREM-894. --------------------------- Resolution: Duplicate Issue > Deprecate multiplex transport > ----------------------------- > > Key: JBREM-894 > URL: http://jira.jboss.com/jira/browse/JBREM-894 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ron Sigal > Assigned To: Ron Sigal > > The original impetus for the development of the multiplex transport was to support the JBossMessaging project, but in that regard it was superseded by the bisocket transport. > Moreover, the introduction of Remoting 3 should eliminate any further need for the multiplex transport. > Therefore, the multiplex transport will not be developed any further. If any changes to Remoting break any multiplex unit tests, those tests will be removed. -- 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] Reopened: (JBREM-633) Investigate timeout during org.jboss.test.remoting.transport.multiplex.invoker.MultiplexInvokerTestCase

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-633?page=all ] Ron Sigal reopened JBREM-633: ----------------------------- > Investigate timeout during org.jboss.test.remoting.transport.multiplex.invoker.MultiplexInvokerTestCase > ------------------------------------------------------------------------------------------------------- > > Key: JBREM-633 > URL: http://jira.jboss.com/jira/browse/JBREM-633 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.2.0.Beta1 (Bluto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > > Occurred on 11/4/06 and 11/5/06 for jdk 1.4. -- 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] Reopened: (JBREM-894) Deprecate multiplex transport

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-894?page=all ] Ron Sigal reopened JBREM-894: ----------------------------- > Deprecate multiplex transport > ----------------------------- > > Key: JBREM-894 > URL: http://jira.jboss.com/jira/browse/JBREM-894 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ron Sigal > Assigned To: Ron Sigal > > The original impetus for the development of the multiplex transport was to support the JBossMessaging project, but in that regard it was superseded by the bisocket transport. > Moreover, the introduction of Remoting 3 should eliminate any further need for the multiplex transport. > Therefore, the multiplex transport will not be developed any further. If any changes to Remoting break any multiplex unit tests, those tests will be removed. -- 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-894) Deprecate multiplex transport

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-894?page=all ] Ron Sigal updated JBREM-894: ---------------------------- Fix Version/s: (was: 2.4.0.Beta2 (Pinto)) Removed fix version. > Deprecate multiplex transport > ----------------------------- > > Key: JBREM-894 > URL: http://jira.jboss.com/jira/browse/JBREM-894 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ron Sigal > Assigned To: Ron Sigal > > The original impetus for the development of the multiplex transport was to support the JBossMessaging project, but in that regard it was superseded by the bisocket transport. > Moreover, the introduction of Remoting 3 should eliminate any further need for the multiplex transport. > Therefore, the multiplex transport will not be developed any further. If any changes to Remoting break any multiplex unit tests, those tests will be removed. -- 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-633) Investigate timeout during org.jboss.test.remoting.transport.multiplex.invoker.MultiplexInvokerTestCase

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-633?page=all ] Ron Sigal updated JBREM-633: ---------------------------- Fix Version/s: (was: 2.4.0.Beta2 (Pinto)) Removed fix version. > Investigate timeout during org.jboss.test.remoting.transport.multiplex.invoker.MultiplexInvokerTestCase > ------------------------------------------------------------------------------------------------------- > > Key: JBREM-633 > URL: http://jira.jboss.com/jira/browse/JBREM-633 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.2.0.Beta1 (Bluto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > > Occurred on 11/4/06 and 11/5/06 for jdk 1.4. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues May 2008