November 2008 - jboss-remoting-issues

[JBoss JIRA] Created: (JBREM-1050) HTTPClientInvoker does not support BASIC authentication for proxies when use of proxy is configured by system properties

by Ron Sigal (JIRA)

HTTPClientInvoker does not support BASIC authentication for proxies when use of proxy is configured by system properties ------------------------------------------------------------------------------------------------------------------------ Key: JBREM-1050 URL: https://jira.jboss.org/jira/browse/JBREM-1050 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP10 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP11 The use of a proxy can be communicated to the HTTP transport in two ways. 1. The parameters "http.proxyHost" and "http.proxyPort" can be configured in the invocation metadata map, or 2. the system properties "http.proxyHost" and "http.proxyPort" can be set. In the former case, org.jboss.remoting.transport.http.HTTPClientInvoker will attempt to call java.net.URL.openConnection(java.net.Proxy) (which exists only in jdk 1.5 and above). If the call succeeds, HTTPClientInvoker will go on to create a "Proxy-Authorization" request header, based on the values associated with ""http.proxy.username" and "http.proxy.password", either in the invocation metadata map or as system properties. In the latter case, the java.net.URL class will configure proxy information based on the system properties. The problem is that, in the latter case, HTTPClientInvoker does not check for the existence of the "http.proxyHost" and "http.proxyPort" system properties, and so never checks to see if it should create a "Proxy-Authorization" request header. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBREM-1056) Fix race condition in InvokerRegistry

by Ron Sigal (JIRA)

Fix race condition in InvokerRegistry ------------------------------------- Key: JBREM-1056 URL: https://jira.jboss.org/jira/browse/JBREM-1056 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP10 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP11 In org.jboss.remoting.InvokerRegistry.createClientInvoker() there is a reference to serverLocators which is in a synchronized(clientLock) block but which is not protected by a synchronized(serverLock) block. Under heavy load, when org.jboss.remoting.Client.addCallbackListener() is creating a connection to the callback Connector (which is necessarily colocated in the same JVM), serverLocators has been seen to return null. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-1026) Add service metadata

by David Lloyd (JIRA)

Add service metadata -------------------- Key: JBREM-1026 URL: https://jira.jboss.org/jira/browse/JBREM-1026 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 api Reporter: David Lloyd Fix For: 3.0.0-M3 A RequestHandlerSource (aka a forwarded service) needs methods to query static metadata, such as: 1) The presence or absence of ordering guarantees across the total path 2) Security information about the total path (encryption strength for example) 3) Path information (like a traceroute, for cost as well as diagnostic information; could include link cost, transport type & version, etc) 4) Possibly authentication information about the total path It should be possible to add new metadata types later on without interfering with backwards compatibility. So lack of a given metadata type must be considered to be possibly indicative of an older version along the path. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
2
0 / 0

[JBoss JIRA] Closed: (JBREM-837) Static Discovery/Route Deployer

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-837?page=com.atlassian.jira.plug... ] David Lloyd closed JBREM-837. ----------------------------- Resolution: Done Assignee: David Lloyd > Static Discovery/Route Deployer > ------------------------------- > > Key: JBREM-837 > URL: https://jira.jboss.org/jira/browse/JBREM-837 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 3.0.0.Beta1 > > > Mechanism to allow static Discoveries to be deployed/undeployed for a given Endpoint. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-1031) Add jboss-classloading.xml descriptors to artifacts

by David Lloyd (JIRA)

Add jboss-classloading.xml descriptors to artifacts --------------------------------------------------- Key: JBREM-1031 URL: https://jira.jboss.org/jira/browse/JBREM-1031 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 3.0.0.Beta1 The jboss-classloading.xml descriptor is necessary for proper AS5 deployment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1036) Integrate new marshalling framework

by David Lloyd (JIRA)

Integrate new marshalling framework ----------------------------------- Key: JBREM-1036 URL: https://jira.jboss.org/jira/browse/JBREM-1036 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.0.Beta1 Use pluggable externalizers for stream replacement, replacing the old marker object code. Work out something for marshaller negotiation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1055) ConnectionValidator.run() should have a sanity test to prevent calls from application code

by Ron Sigal (JIRA)

ConnectionValidator.run() should have a sanity test to prevent calls from application code ------------------------------------------------------------------------------------------ Key: JBREM-1055 URL: https://jira.jboss.org/jira/browse/JBREM-1055 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.5.0.SP1 (Flounder), 2.2.2.SP10 Reporter: Ron Sigal Assignee: Ron Sigal Priority: Minor Fix For: 2.2.2.SP11, 2.5.0.SP2 (Flounder) org.jboss.remoting.ConnectionValidator extends java.util.TimerTask which implements Runnable and has a public run() class. run() needs to be public so it can be called by java.util.Timer, but it also exposes the method to application code, which can lead to a NullPointerException if run() is called directly. There should be a log message to deter a direct call. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBREM-1041) Remote classloading does not work with Isolated EARs, Part 2

by Ron Sigal (JIRA)

Remote classloading does not work with Isolated EARs, Part 2 ------------------------------------------------------------- Key: JBREM-1041 URL: https://jira.jboss.org/jira/browse/JBREM-1041 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP10 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP11 There are two bugs in org.jboss.remoting.marshal.MarshallerLoaderHandler.loadClassBytes(): 1. The while loop needs a break; and 2. the call to org.jboss.mx.loading.LoaderRepository.getCachedClass() should be the more general call LoaderRepository.loadClass(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Closed: (JBREM-386) tomcat libraries not available to remoting when using http transport

by Trustin Lee (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-386?page=com.atlassian.jira.plug... ] Trustin Lee closed JBREM-386. ----------------------------- Resolution: Out of Date Assignee: Trustin Lee (was: Tom Elrod) I think this issue is safe to be closed as 'out of date' according to its age and the status of the linked issues. > tomcat libraries not available to remoting when using http transport > -------------------------------------------------------------------- > > Key: JBREM-386 > URL: https://jira.jboss.org/jira/browse/JBREM-386 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 1.4.0 final > Reporter: Tom Elrod > Assignee: Trustin Lee > Priority: Blocker > Fix For: External_issues > > > This is just a pointer issue back to JBAS-2766 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues November 2008