October 2008 - jboss-remoting-issues

[JBoss JIRA] Created: (JBREM-992) Can't restart a Connector that uses SocketServerInvoker

by Brian Stansberry (JIRA)

Can't restart a Connector that uses SocketServerInvoker ------------------------------------------------------- Key: JBREM-992 URL: http://jira.jboss.com/jira/browse/JBREM-992 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4.0.GA (Pinto) Reporter: Brian Stansberry Priority: Minor You can't take a Connector that uses SocketServerInvoker through a restart, i.e. these lifecycle steps: create/start/stop/start. You have to do a full transition to destroy and back through create. This is because SocketServerInvoker sets its maxPoolSize field to 0 as part of its cleanup work in stop(). If you then call start() you get a failure due to 0 being an invalid value for maxPoolSize: 2008-06-04 12:33:00,382 DEBUG [org.jboss.invocation.unified.server.UnifiedInvokerHA] (RMI TCP Connec tion(31)-127.0.0.1) Starting failed jboss:service=invoker,type=unifiedha,partitionName=RestartPartit ion java.lang.IllegalArgumentException: Illegal cache capacities at org.jboss.util.LRUCachePolicy.<init>(LRUCachePolicy.java:77) at org.jboss.remoting.transport.socket.LRUPool.<init>(LRUPool.java:44) at org.jboss.remoting.transport.socket.SocketServerInvoker.start(SocketServerInvoker.java:231) at org.jboss.invocation.unified.server.UnifiedInvoker.startService(UnifiedInvoker.java:140) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322) at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) -- 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

15 years, 11 months

4
7
0 / 0

[JBoss JIRA] Created: (JBREM-1042) CLONE [JBREM-1019] - RemotingClassLoader needs option to delegate to user class loader before parent

by Ron Sigal (JIRA)

CLONE [JBREM-1019] - RemotingClassLoader needs option to delegate to user class loader before parent ---------------------------------------------------------------------------------------------------- Key: JBREM-1042 URL: https://jira.jboss.org/jira/browse/JBREM-1042 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4.0.GA (Pinto) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.4.0.SP1 (Pinto) For the jbossas5 app client container, a class loader policy that loads from the child first is used to pickup the client jar manifest references. If such a class loader is registered as the user class loader with the RemotingClassLoader, its not going be delegated to first. This results in duplicate and conflicting classes being loaded. -- 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

15 years, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (JBREM-1052) CLONE [JBREM-1046] - HTTPClientInvoker throws NullPointerException when HttpURLConnection.getInputStream() returns null

by Ron Sigal (JIRA)

CLONE [JBREM-1046] - HTTPClientInvoker throws NullPointerException when HttpURLConnection.getInputStream() returns null ----------------------------------------------------------------------------------------------------------------------- Key: JBREM-1052 URL: https://jira.jboss.org/jira/browse/JBREM-1052 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.5.0.GA (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.0.SP1 (Flounder) When an HTTP server returns an error code and no content, it is possible for java.net.HttpUrlConnection.getInputStream() to retun null, which causes a NullPointerException in org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(). -- 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

15 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBREM-1053) Release 2.5.0.SP2

by Ron Sigal (JIRA)

Release 2.5.0.SP2 ----------------- Key: JBREM-1053 URL: https://jira.jboss.org/jira/browse/JBREM-1053 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.0.SP2 (Flounder) -- 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

15 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1040) Sometimes ClientSocketWrapper.checkConnection() doesn't detect closed connection in JBoss Remoting 1.4.3.GA

by Takayoshi Kimura (JIRA)

Sometimes ClientSocketWrapper.checkConnection() doesn't detect closed connection in JBoss Remoting 1.4.3.GA ----------------------------------------------------------------------------------------------------------- Key: JBREM-1040 URL: https://jira.jboss.org/jira/browse/JBREM-1040 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Takayoshi Kimura Assignee: Takayoshi Kimura In a same test described in JBREM-1017, the client sometimes doesn't detect closed connection. After read a CLOSED byte (254), the client gets IOException: Broken pipe when try to write an invocation. This issue is environment specific or timing issue, so doesn't always happen. -- 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

15 years, 11 months

2
4
0 / 0

[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
4
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
2
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
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
1
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
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues October 2008