November 2008 - jboss-remoting-issues

[JBoss JIRA] Created: (JBREM-1018) JBREM-1014 patch for 2.2.2.SP4

by Galder Zamarreno (JIRA)

JBREM-1014 patch for 2.2.2.SP4 ------------------------------ Key: JBREM-1018 URL: https://jira.jboss.org/jira/browse/JBREM-1018 Project: JBoss Remoting Issue Type: Support Patch Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP4 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Port the fix for JBREM-1014 to JBoss Remoting 2.2.2.SP4, which is the Remoting version in EAP 4.3.0.GA and 4.2.0.GA_CP02. -- 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-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-1070) Fix deadlock in ConnectionValidator

by Ron Sigal (JIRA)

Fix deadlock in ConnectionValidator ----------------------------------- Key: JBREM-1070 URL: https://jira.jboss.org/jira/browse/JBREM-1070 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP10, 2.5.0.SP2 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP11, 2.5.0.SP3 (Flounder) org.jboss.remoting.ConnectionValidator.run() synchronizes on the "lock" variable, which is needed by notifyListeners() in the event of a network failure. In general, the calls in run() to either doCheckConnectionWithLease() or doCheckConnectionWithoutLease() should time out so that run() gives up the "lock" variable, but, if run() executes again soon enough, it can grab "lock" again before notifyListeners() can run. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBREM-1069) Make ConnectorValidator configure ping period correctly

by Ron Sigal (JIRA)

Make ConnectorValidator configure ping period correctly ------------------------------------------------------- Key: JBREM-1069 URL: https://jira.jboss.org/jira/browse/JBREM-1069 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP10, 2.5.0.SP2 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP11, 2.5.0.SP3 (Flounder) When the overloaded org.jboss.remoting.Client method public void addConnectionListener(ConnectionListener listener) is called, it puts the default value org.jboss.remoting.ConnectionValidator.DEFAULT_PING_PERIOD (actual value 2000) in the metadata map passed to ConnectionValidator. Since the metadata map overrides the Client's configuration map, the value in the Client's configuration map, which can come from the InvokerLocator or Connector configuration, is ignored. In particular, the JBossMessaging class org.jboss.jms.client.remoting.JMSRemotingConnection calls that version of Client.addListener(). -- 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
2
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-1060) Distro cleanup (parent task)

by David Lloyd (JIRA)

Distro cleanup (parent task) ---------------------------- Key: JBREM-1060 URL: https://jira.jboss.org/jira/browse/JBREM-1060 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 api, r3 core, r3 JRPP Affects Versions: 3.0.0.Beta1 Reporter: David Lloyd Fix For: 3.0.0.Beta2 Parent task for distro cleanup subtasks. -- 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-1065) Include more samples

by David Lloyd (JIRA)

Include more samples -------------------- Key: JBREM-1065 URL: https://jira.jboss.org/jira/browse/JBREM-1065 Project: JBoss Remoting Issue Type: Sub-task Security Level: Public (Everyone can see) Components: r3 api, r3 core, r3 protocol - multiplex, r3 transporter Affects Versions: 3.0.0.Beta1 Reporter: David Lloyd Fix For: 3.0.0.Beta2 We need more samples - showing protocol use, local listeners, transporters, etc. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues November 2008