March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-712) HTTPInvokerProxyTestCase failing

by Tom Elrod (JIRA)

HTTPInvokerProxyTestCase failing -------------------------------- Key: JBREM-712 URL: http://jira.jboss.com/jira/browse/JBREM-712 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Alpha7 Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) -- 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-721) Fix memory leaks in bisocket transport and LeasePinger

by Ron Sigal (JIRA)

Fix memory leaks in bisocket transport and LeasePinger ------------------------------------------------------ Key: JBREM-721 URL: http://jira.jboss.com/jira/browse/JBREM-721 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) 1. The bisocket transport is failing to remove unused objects from static maps. Also, it seems that calling cancel() on a TimerTask marks it as cancelled, but it doesn't remove the TimerTask from the Timer's heap until the TImerTask comes to the head of the heap. Therefore, a busy Timer could keep TimerTasks around for a while with references to objects that cannot be garbage collected. To prevent this problem, TImerTasks should be defined as static classes, with all of the objects it needs from the outer class passed in to the constructor. When the TimerTask is cancelled, it should set its instance variables to null. 2. Bisocket uses some TimerTasks. 3. LeasePinger uses some TimerTasks. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBREM-700) NPE in AbstractDetector

by Tom Elrod (JIRA)

NPE in AbstractDetector ----------------------- Key: JBREM-700 URL: http://jira.jboss.com/jira/browse/JBREM-700 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: detection Affects Versions: 2.2.0.Alpha6 Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) Within method: protected boolean isRemoteDetection(Detection detection) will check for String domain = detection.getIdentity().getDomain(); -- 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-671) serlvet invoker no longer supports leasing

by Tom Elrod (JIRA)

serlvet invoker no longer supports leasing ------------------------------------------ Key: JBREM-671 URL: http://jira.jboss.com/jira/browse/JBREM-671 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.0.Alpha4, 2.0.0.GA (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) A while back, the leasing when using an http transport changed to query server via HEAD http method call instead of making a formal invocation to get the leasing info from the remoting server (i.e. if leasing was turned on, what the default lease period should be, etc.). These changes were made to the http client invoker and http/coyote server invoker, but not to the web server invoker (which is what is used for servlet server invoker). Therefore, leasing is basically broken when using servlet invoker. -- 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-683) ByValueInvocationTestCase is broken

by Tom Elrod (JIRA)

ByValueInvocationTestCase is broken ----------------------------------- Key: JBREM-683 URL: http://jira.jboss.com/jira/browse/JBREM-683 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: general Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto), 2.2.0.Alpha6 The ByValueInvocationTestCase has two tests, one for jboss and one for java serialization. In each test, a remoting connector is created, but never destroyed, so on the next test run, that connector still remains (still using the same bound port). -- 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-682) org.jboss.remoting.transport.socket.ServerThread keeps reference to org.jboss.ejb3.StatelessBeanContext

by Carlo de Wolf (JIRA)

org.jboss.remoting.transport.socket.ServerThread keeps reference to org.jboss.ejb3.StatelessBeanContext ------------------------------------------------------------------------------------------------------- Key: JBREM-682 URL: http://jira.jboss.com/jira/browse/JBREM-682 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA (Boon) Environment: AS 4.2 (20070122) Reporter: Carlo de Wolf Assigned To: Tom Elrod Priority: Critical After undeployment, remoting still has a reference to a bean context. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBREM-673) Use of java.util.Timer recently added and not set to daemon, so applications not exiting

by Tom Elrod (JIRA)

Use of java.util.Timer recently added and not set to daemon, so applications not exiting ---------------------------------------------------------------------------------------- Key: JBREM-673 URL: http://jira.jboss.com/jira/browse/JBREM-673 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: general Affects Versions: 2.2.0.Alpha5 Reporter: Tom Elrod Assigned To: Tom Elrod Priority: Critical Fix For: 2.2.0.Alpha6 -- 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-685) A server needs redundant information to detect a one way invocation

by Ovidiu Feodorov (JIRA)

A server needs redundant information to detect a one way invocation ------------------------------------------------------------------- Key: JBREM-685 URL: http://jira.jboss.com/jira/browse/JBREM-685 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 2.2.0.Alpha7 An oneway invocation is correctly processed on the server side only if: 1. It wraps an OnewayInvocation instance 2. It contains Client.ONEWAY_FLAG in its request payload metadata This is redundant. -- 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

4
4
0 / 0

[JBoss JIRA] Created: (JBREM-659) Java 6 and ClassLoader.loadClass()

by Jan Bares (JIRA)

Java 6 and ClassLoader.loadClass() ---------------------------------- Key: JBREM-659 URL: http://jira.jboss.com/jira/browse/JBREM-659 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Environment: Java 1.6.0-b105 Reporter: Jan Bares Assigned To: Tom Elrod The ClassLoader.loadClass() should be used only for plain classes, not for arrays etc. In ObjectInputStreamWithClassLoader.resolveClass() call: return Class.forName(v.getName(), false, cl); The problem is described at: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6434149 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6500212 http://forums.java.net/jive/thread.jspa?threadID=15823&tstart=0 The bug was found in JBoss AS 4.0.5.GA. -- 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

6
13
0 / 0

[JBoss JIRA] Created: (JBREM-655) rename server thread when new socket connection comes in

by Tom Elrod (JIRA)

rename server thread when new socket connection comes in -------------------------------------------------------- Key: JBREM-655 URL: http://jira.jboss.com/jira/browse/JBREM-655 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.0.Alpha4, 1.4.5.GA, 2.0.0.GA (Boon), 1.4.4.GA, 1.4.3.GA Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) The ServerThread used to process incoming client requests for the socket server invoker will name the thread based on client address associated with socket connection. However, this address is not updated after the initial client request, so if the server thread is woken up and given a different client socket connection, will not re-name to the client address of for the new socket connection. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2007