January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBREM-154) pluggable server resolver in client

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-154?page=all ] Ron Sigal updated JBREM-154: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Assignee: (was: Tom Elrod) > pluggable server resolver in client > ----------------------------------- > > Key: JBREM-154 > URL: http://jira.jboss.com/jira/browse/JBREM-154 > Project: JBoss Remoting > Issue Type: Feature Request > Components: general > Affects Versions: 1.2.0 final > Reporter: Tom Elrod > Priority: Minor > > Per forum thread http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883462#3883462, need ability for the remoting client to have a pluggable way to resolve a server endpoint. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-142) better configuration for stream server

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-142?page=all ] Ron Sigal updated JBREM-142: ---------------------------- Fix Version/s: 2.4.1.Beta (was: 2.4.0.Beta1 (Pinto)) Assignee: (was: Tom Elrod) > better configuration for stream server > -------------------------------------- > > Key: JBREM-142 > URL: http://jira.jboss.com/jira/browse/JBREM-142 > Project: JBoss Remoting > Issue Type: Feature Request > Components: stream > Affects Versions: 1.2.0 final > Reporter: Tom Elrod > Priority: Minor > Fix For: 2.4.1.Beta > > > The stream server does have basic configuration for transport, host, and port via system properties (see JBREM-125), but needs better alternative for configuration. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-344) support for NTLM authentication

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-344?page=all ] Ron Sigal updated JBREM-344: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Assignee: (was: Tom Elrod) > support for NTLM authentication > ------------------------------- > > Key: JBREM-344 > URL: http://jira.jboss.com/jira/browse/JBREM-344 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 1.4.0 final > Reporter: Tom Elrod > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-385) Need to pull the legacy invokers into remoting

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-385?page=all ] Ron Sigal updated JBREM-385: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Assignee: (was: Tom Elrod) > Need to pull the legacy invokers into remoting > ---------------------------------------------- > > Key: JBREM-385 > URL: http://jira.jboss.com/jira/browse/JBREM-385 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Scott M Stark > > The org.jboss.invocation.* package has dependencies on remoting, and it should just be moved into the remoting project as the legacy remoting impl. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-398) bring AOP Remoting under JBossRemoting project

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-398?page=all ] Ron Sigal updated JBREM-398: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Assignee: (was: Tom Elrod) > bring AOP Remoting under JBossRemoting project > ---------------------------------------------- > > Key: JBREM-398 > URL: http://jira.jboss.com/jira/browse/JBREM-398 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Reporter: Tom Elrod > > Need to bring AOP Remoting under the JBossRemoting project for further development and maintenance. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-505) convert jndi to use remoting for transport

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-505?page=all ] Ron Sigal updated JBREM-505: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Affects Version/s: External_issues Assignee: (was: Tom Elrod) > convert jndi to use remoting for transport > ------------------------------------------ > > Key: JBREM-505 > URL: http://jira.jboss.com/jira/browse/JBREM-505 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: External_issues > Reporter: Tom Elrod > > Need to convert jndi to use remoting as transport. Ties in with JBREM-424. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-800) Adjust timout values to avoid cruisecontrol failures

by Ron Sigal (JIRA)

Adjust timout values to avoid cruisecontrol failures ---------------------------------------------------- Key: JBREM-800 URL: http://jira.jboss.com/jira/browse/JBREM-800 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) It seems that some tests fail on cruisecontrol because a busy machine causes timout deadlines to be missed. For example, http://cruisecontrol.jboss.com/cc/artifacts/jboss-remoting-testsuite-1.4/... This issue will be an umbrella issue to cover adjusting timeout values. If a test continues to fail despite updated timeout values, it will need a JIRA issue of its own. -- 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, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBREM-760) Change port for shutdown tests.

by Ron Sigal (JIRA)

Change port for shutdown tests. ------------------------------- Key: JBREM-760 URL: http://jira.jboss.com/jira/browse/JBREM-760 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.4.0.Beta1 (Pinto) The descendants of org.jboss.test.remoting.shutdown.ShutdownTestParent are failing because the port used by the server is in use. The port number should be changed. -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-786) stale sockets can be gotten from pool even with current rety logic

by james ahlborn (JIRA)

stale sockets can be gotten from pool even with current rety logic ------------------------------------------------------------------ Key: JBREM-786 URL: http://jira.jboss.com/jira/browse/JBREM-786 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 1.4.6.GA Reporter: james ahlborn The retry logic in SocketClientInvoker.transport attempts to ensure that the invoker does not get a stale socket on the last attempt by flushing the pool. however, this only discards any currently unused scokets. a second invoker could return a stale socket after the flush, causing the first invoker to fail again on the last retry (with an EOFException). while this seems like an edge case, we can hit it reliably under load with many connections to the same destination. i've patched this class so that the last call to getConnection will never return a pooled connection. we never got the EOFException after applying this fix. -- 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, 11 months

2
8
0 / 0

[JBoss JIRA] Created: (JBREM-701) add timeout config per client invocation for transports not descended from socket transport

by Ron Sigal (JIRA)

add timeout config per client invocation for transports not descended from socket transport ------------------------------------------------------------------------------------------- Key: JBREM-701 URL: http://jira.jboss.com/jira/browse/JBREM-701 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0.Alpha1 (Otter) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 3.0.0.Alpha1 (Otter) For JBREM-598 per invocation timeouts were implemented for socket, sslsocket, bisocket, and sslbisocket. It's not clear how to implement per invocation timeouts for http and rmi, but it would be good to do, if possible. -- 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, 11 months

1
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008