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

[JBoss JIRA] Closed: (JBREM-871) HTTP Client invoker doesn't throw exceptions when using the sslservlet protocol

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-871?page=all ] Ron Sigal closed JBREM-871. --------------------------- Resolution: Done > HTTP Client invoker doesn't throw exceptions when using the sslservlet protocol > ------------------------------------------------------------------------------- > > Key: JBREM-871 > URL: http://jira.jboss.com/jira/browse/JBREM-871 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: transport > Affects Versions: 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Jay Howell > Assigned To: Ron Sigal > Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP4 > > > In the HTTP Client Invoker, the only server side exceptions that get thrown are for the servlet protocol only... and also have to be servlet exceptions... The code from the client that throws the exception is inside of this if block.... > i// now check for error response and throw exception unless configured to not do so > if(responseCode >= 400 > || ("servlet".equals(getLocator().getProtocol()) > && result instanceof InvocationResponse > && ((InvocationResponse) result).getResult() instanceof ServletThrowable)) > { -- 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

1
0
0 / 0

[JBoss JIRA] Reopened: (JBREM-873) Have ServerInvokerCallbackHandler register as connection listener

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-873?page=all ] Ron Sigal reopened JBREM-873: ----------------------------- > Have ServerInvokerCallbackHandler register as connection listener > ----------------------------------------------------------------- > > Key: JBREM-873 > URL: http://jira.jboss.com/jira/browse/JBREM-873 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP2 > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.2.2.SP4, 2.4.0.Beta1 (Pinto) > > > This feature is implemented in response to JBPAPP-402 :"In certain situations createQueueConnection can hang". > JBossMessaging does not, in general, call org.jboss.remoting.callback.ServerInvokerCallbackHandler.destroy() when a lease indicates that a connection has failed. More generally, the need to call ServerCallbackHandler.destroy() is not documented in the Remoting Guide, so it is possible that JBossMessaging is not alone. -- 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

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ] Ron Sigal closed JBREM-858. --------------------------- Resolution: Done > MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools > ----------------------------------------------------------------------------------- > > Key: JBREM-858 > URL: http://jira.jboss.com/jira/browse/JBREM-858 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP4 > > > If two instances of org.jboss.remoting.Client are created, one with clientMaxPoolSize=1 and one with clientMaxPoolSize=30, they will still share the same connection pool because the key to the connection pools, org.jboss.remoting.transport.socket.ServerAddress, does not include the value of clientMaxPoolSize. ServerAddress.equals() and ServerAddress.hashCode() should be modified to include the value of clientMaxPoolSize. -- 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

1
0
0 / 0

[JBoss JIRA] Reopened: (JBREM-860) Eliminate delay in MicroSocketClientInvoker.getConnection()

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-860?page=all ] Ron Sigal reopened JBREM-860: ----------------------------- > Eliminate delay in MicroSocketClientInvoker.getConnection() > ----------------------------------------------------------- > > Key: JBREM-860 > URL: http://jira.jboss.com/jira/browse/JBREM-860 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.2.2.SP4, 2.4.0.Beta1 (Pinto) > > > org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection() currently calls Thread.sleep(1000) after each unsuccessful attempt to retrieve a connection from the connection pool. This introduced an unnecessary delay in general, and, in particular, makes the use of a connection pool of size one impractical. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-860) Eliminate delay in MicroSocketClientInvoker.getConnection()

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-860?page=all ] Ron Sigal updated JBREM-860: ---------------------------- Fix Version/s: 2.4.0.Beta1 (Pinto) Added fix version 2.4.0.Beta1 - see JBREM-975 "Make sure all fixes on 2.2 branch are applied to 2.x branch". > Eliminate delay in MicroSocketClientInvoker.getConnection() > ----------------------------------------------------------- > > Key: JBREM-860 > URL: http://jira.jboss.com/jira/browse/JBREM-860 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.2.2.SP4, 2.4.0.Beta1 (Pinto) > > > org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection() currently calls Thread.sleep(1000) after each unsuccessful attempt to retrieve a connection from the connection pool. This introduced an unnecessary delay in general, and, in particular, makes the use of a connection pool of size one impractical. -- 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

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-860) Eliminate delay in MicroSocketClientInvoker.getConnection()

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-860?page=all ] Ron Sigal closed JBREM-860. --------------------------- Resolution: Done > Eliminate delay in MicroSocketClientInvoker.getConnection() > ----------------------------------------------------------- > > Key: JBREM-860 > URL: http://jira.jboss.com/jira/browse/JBREM-860 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP4 > > > org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection() currently calls Thread.sleep(1000) after each unsuccessful attempt to retrieve a connection from the connection pool. This introduced an unnecessary delay in general, and, in particular, makes the use of a connection pool of size one impractical. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ] Ron Sigal updated JBREM-858: ---------------------------- Fix Version/s: 2.4.0.Beta1 (Pinto) Added fix version 2.4.0.Beta1 - see JBREM-975 "Make sure all fixes on 2.2 branch are applied to 2.x branch". > MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools > ----------------------------------------------------------------------------------- > > Key: JBREM-858 > URL: http://jira.jboss.com/jira/browse/JBREM-858 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.2.2.SP4, 2.4.0.Beta1 (Pinto) > > > If two instances of org.jboss.remoting.Client are created, one with clientMaxPoolSize=1 and one with clientMaxPoolSize=30, they will still share the same connection pool because the key to the connection pools, org.jboss.remoting.transport.socket.ServerAddress, does not include the value of clientMaxPoolSize. ServerAddress.equals() and ServerAddress.hashCode() should be modified to include the value of clientMaxPoolSize. -- 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

1
0
0 / 0

[JBoss JIRA] Reopened: (JBREM-858) MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-858?page=all ] Ron Sigal reopened JBREM-858: ----------------------------- > MaxPoolSize value should be used in key to MicroSocketClientInvoker.connectionPools > ----------------------------------------------------------------------------------- > > Key: JBREM-858 > URL: http://jira.jboss.com/jira/browse/JBREM-858 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.2.2.SP4, 2.4.0.Beta1 (Pinto) > > > If two instances of org.jboss.remoting.Client are created, one with clientMaxPoolSize=1 and one with clientMaxPoolSize=30, they will still share the same connection pool because the key to the connection pools, org.jboss.remoting.transport.socket.ServerAddress, does not include the value of clientMaxPoolSize. ServerAddress.equals() and ServerAddress.hashCode() should be modified to include the value of clientMaxPoolSize. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-855) Update build.xml to allow jdk 1.5 compiler to target JVM version 1.4

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-855?page=all ] Ron Sigal updated JBREM-855: ---------------------------- Fix Version/s: 2.4.0.Beta1 (Pinto) Added fix version 2.4.0.Beta1 - see JBREM-975 "Make sure all fixes on 2.2 branch are applied to 2.x branch". > Update build.xml to allow jdk 1.5 compiler to target JVM version 1.4 > -------------------------------------------------------------------- > > Key: JBREM-855 > URL: http://jira.jboss.com/jira/browse/JBREM-855 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.2.2.SP4, 2.4.0.Beta1 (Pinto) > > > Fernando has suggested updating build.xml so that the *-brew scripts can use the jdk 1.5 compiler to generate code that is compatible with a 1.4 JVM. This way we have a single version of jboss-remoting.jar in the repository which is (1) appropriate in the current versions of the Application Server, which are compiled with jdk 1.5, and (2) usable in a standalone context by clients built with a jdk 1.4 compiler. > The changes should be applied to the following branches: > - remoting_2_2_0_GA (for community AS) > - remoting_2_2_2_GA_CP (for EAP 4.2 and 4.3) > - remoting_2_x (for Remoting 2.4.0) -- 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

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-855) Update build.xml to allow jdk 1.5 compiler to target JVM version 1.4

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-855?page=all ] Ron Sigal closed JBREM-855. --------------------------- Resolution: Done > Update build.xml to allow jdk 1.5 compiler to target JVM version 1.4 > -------------------------------------------------------------------- > > Key: JBREM-855 > URL: http://jira.jboss.com/jira/browse/JBREM-855 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP4 > > > Fernando has suggested updating build.xml so that the *-brew scripts can use the jdk 1.5 compiler to generate code that is compatible with a 1.4 JVM. This way we have a single version of jboss-remoting.jar in the repository which is (1) appropriate in the current versions of the Application Server, which are compiled with jdk 1.5, and (2) usable in a standalone context by clients built with a jdk 1.4 compiler. > The changes should be applied to the following branches: > - remoting_2_2_0_GA (for community AS) > - remoting_2_2_2_GA_CP (for EAP 4.2 and 4.3) > - remoting_2_x (for Remoting 2.4.0) -- 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

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