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

[JBoss JIRA] Commented: (JBREM-813) ServletServerInvoker should return an exception instead of just an error message

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-813?page=comments#action_12414155 ] Ron Sigal commented on JBREM-813: --------------------------------- The default behavior described above applies only to the 2.2 branch. In the 2.x branch (for release 2.4), the default behavior is to throw an exception. The original behavior of returning an error message can be requested by setting the parameter HTTPMetadataConstants.DONT_RETURN_EXCEPTION (actual value "dont-return-exception") to "true". > ServletServerInvoker should return an exception instead of just an error message > -------------------------------------------------------------------------------- > > Key: JBREM-813 > URL: http://jira.jboss.com/jira/browse/JBREM-813 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2.2.GA > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2 > > > The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception. An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 . > Note that for backwards compatibility, this new behavior should be configurable but not the default behavior. -- 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] Created: (JBREM-975) Make sure all fixes on 2.2 branch are applied to 2.x branch

by Ron Sigal (JIRA)

Make sure all fixes on 2.2 branch are applied to 2.x branch ----------------------------------------------------------- Key: JBREM-975 URL: http://jira.jboss.com/jira/browse/JBREM-975 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.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

16 years

1
1
0 / 0

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

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-873?page=all ] Ron Sigal updated JBREM-873: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Removed fix version 2.4.0.Beta1 - it's cloned by JBREM-875. > 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 > > > 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-873) Have ServerInvokerCallbackHandler register as connection listener

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-873?page=all ] Ron Sigal closed JBREM-873. --------------------------- Resolution: Done > 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 > > > 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-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.4.0.Beta1 (Pinto), 2.2.2.GA_CP01 > Reporter: Jay Howell > Assigned To: Ron Sigal > Fix For: 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 > > > 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] Updated: (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 updated JBREM-871: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Removed fix version 2.4.0.Beta1 - it's cloned by JBREM-874. > 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.4.0.Beta1 (Pinto), 2.2.2.GA_CP01 > Reporter: Jay Howell > Assigned To: Ron Sigal > Fix For: 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-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 reopened JBREM-871: ----------------------------- > 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.4.0.Beta1 (Pinto), 2.2.2.GA_CP01 > Reporter: Jay Howell > Assigned To: Ron Sigal > Fix For: 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] 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.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-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: (was: 2.4.0.Beta1 (Pinto)) Removed fix version 2.4.0.Beta1 - it's cloned by JBREM-866. > 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 > > > 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues May 2008