January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-546) InvokerLocator.equals is broken

by Petr Matejka (JIRA)

InvokerLocator.equals is broken ------------------------------- Key: JBREM-546 URL: http://jira.jboss.com/jira/browse/JBREM-546 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: general Affects Versions: 1.4.4.GA Reporter: Petr Matejka Assigned To: Tom Elrod InvokerLocator.equals compares hash-codes of uris instead of comparing uris . The probability of hash collision is quite low except for cases when you connect to many nodes (which is my case, i'm connecting to >1000 nodes). -- 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

18 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBREM-547) need test case for exposing multiple interfaces for transporter server target pojo

by Tom Elrod (JIRA)

need test case for exposing multiple interfaces for transporter server target pojo ---------------------------------------------------------------------------------- Key: JBREM-547 URL: http://jira.jboss.com/jira/browse/JBREM-547 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: transporter Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) -- 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

18 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-548) Support one way invocations with no response

by Tim Fox (JIRA)

Support one way invocations with no response -------------------------------------------- Key: JBREM-548 URL: http://jira.jboss.com/jira/browse/JBREM-548 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tim Fox Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) The current remoting implementation of a client side one way invocations just performs a standard two way invocation on a different thread and returns without waiting for the result. JBoss Messaging would like to have a one way invocation which just performs a write to the underlying stream (e.g. socket outpustream) and continues without waiting for the result. This would result in less blocking and better performance since redundant writes for the invocation response would be ommitted, -- 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

18 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBREM-540) need to make servlet-invoker.war part of remoting distribution

by Tom Elrod (JIRA)

need to make servlet-invoker.war part of remoting distribution -------------------------------------------------------------- Key: JBREM-540 URL: http://jira.jboss.com/jira/browse/JBREM-540 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) -- 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

18 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBREM-538) update remoting dist build to break out transports into individual jars

by Tom Elrod (JIRA)

update remoting dist build to break out transports into individual jars ----------------------------------------------------------------------- Key: JBREM-538 URL: http://jira.jboss.com/jira/browse/JBREM-538 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) Because of JBREM-496 would like to have several binaries output from the dist build. Need one that includes everything from remoting. Then need ones for the transports (including one just for the client). So might look like: jboss-remoting-all.jar jboss-remoting-core.jar jboss-remoting-socket.jar jboss-remoting-socket-client.jar jboss-remoting-http.jar jboss-remoting-http-client.jar and so forth. -- 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

18 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBREM-539) add sslservlet procotol

by Tom Elrod (JIRA)

add sslservlet procotol ----------------------- Key: JBREM-539 URL: http://jira.jboss.com/jira/browse/JBREM-539 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) Need to add sslservlet as there is no way to currently have a ssl deployed servlet invoker without this distinction. This will require use of HTTPSClientInvoker on the client side. Would also be nice to do a check internally to make sure that servlet is available and log an error if is not (maybe within start() method), since is only way to really know if servlet deployed within web container properly. -- 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

18 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBREM-544) http client invoker (for http, https, servlet, and sslservlet) needs to handle exceptions in same manner as other transport implementations

by Tom Elrod (JIRA)

http client invoker (for http, https, servlet, and sslservlet) needs to handle exceptions in same manner as other transport implementations ------------------------------------------------------------------------------------------------------------------------------------------- Key: JBREM-544 URL: http://jira.jboss.com/jira/browse/JBREM-544 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) All the other transport clients will throw an exception from the Client.invoke() method when an error occurs. However, the http client invoker currently does not. This is a problem in that can not deliver on no api changes when changing transports. However, there is a need (by the web services group) to have the exception NOT thrown. So need to provide option for both behaviors. -- 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

18 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBREM-543) fix servlet invoker error handling to be more like that of the http invoker

by Tom Elrod (JIRA)

fix servlet invoker error handling to be more like that of the http invoker --------------------------------------------------------------------------- Key: JBREM-543 URL: http://jira.jboss.com/jira/browse/JBREM-543 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) Need to change the servlet invoker so on client side will not throw an exception out of the Client's invoke() method call, but just return the error (as text in most cases) and have the response code indicate the error status code (e.g. 500). Although this is not exactly how the http invoker handles exceptions from the http server invoker, is only way to reliably get errors from web containers (like Tomcat). -- 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

18 years, 7 months

3
11
0 / 0

[JBoss JIRA] Created: (JBREM-545) setting of the bind address within MulticastDetector not working

by Tom Elrod (JIRA)

setting of the bind address within MulticastDetector not working ---------------------------------------------------------------- Key: JBREM-545 URL: http://jira.jboss.com/jira/browse/JBREM-545 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: detection Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) If set the bind address within the MultiplexDetector, it does not actually bind the MultiplexSocket to that address. -- 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

18 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-542) change how remoting servlet finds servlet invoker

by Tom Elrod (JIRA)

change how remoting servlet finds servlet invoker ------------------------------------------------- Key: JBREM-542 URL: http://jira.jboss.com/jira/browse/JBREM-542 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) Currently the servlet deployed within servlet-invoker.war uses the servlet server invoker's JMX Object name (provide within the init-param of web.xml) to lookup the servlet server invoker to make calls upon. This is limited in that requires JMX be available within the web container. Althought this will probably be available in most J2EE app servers, might not be in other web container only deployments. Need to remove this restriction. -- 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

18 years, 7 months

3
10
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2007