November 2009 - jboss-remoting-issues

[JBoss JIRA] Created: (JBREM-1016) Increase Basic Protocol Version

by David Lloyd (JIRA)

Increase Basic Protocol Version ------------------------------- Key: JBREM-1016 URL: https://jira.jboss.org/jira/browse/JBREM-1016 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 3.1.0.GA Increase the protocol version by one. Clone this issue for every minor release. -- 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

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-994) Modify JRPP to run over SSH

by David Lloyd (JIRA)

Modify JRPP to run over SSH --------------------------- Key: JBREM-994 URL: http://jira.jboss.com/jira/browse/JBREM-994 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 3.1.0.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

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-1161) Evaluate FindBugs reports

by Ron Sigal (JIRA)

Evaluate FindBugs reports ------------------------- Key: JBREM-1161 URL: https://jira.jboss.org/jira/browse/JBREM-1161 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.3.SP2 http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-findbug... and http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-5.x-findbugs/... -- 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

14 years, 9 months

1
6
0 / 0

[JBoss JIRA] Created: (JBREM-1170) System.gc() should not call in ServerInvokerCallbackHandler

by ryu ken (JIRA)

System.gc() should not call in ServerInvokerCallbackHandler ----------------------------------------------------------- Key: JBREM-1170 URL: https://jira.jboss.org/jira/browse/JBREM-1170 Project: JBoss Remoting Issue Type: Quality Risk Security Level: Public (Everyone can see) Components: callbacks Affects Versions: 2.2.2.SP11 Reporter: ryu ken It seems System.gc() will be call when Memory Low has been detected. In fact, calling System.gc() may cause performance problems. handleCallback(): // need to check if should persist callback instead of keeping in memory if(shouldPersist()) { try { persistCallback(callback); synchronized (callbacks) { callbacks.notify(); } callback = null; // try to help out with the amount of memory usuage new Thread() { public void run() { System.gc(); } }.start(); } catch(IOException e) { log.error("Unable to persist callback", e); throw new HandleCallbackException("Unable to persist callback and will not " + "be able to deliver.", e); } } getPersistedCallbacks(): if(isMemLow()) { new Thread() { public void run() { System.gc(); } }.start(); break; } isMemLow(): Runtime runtime = Runtime.getRuntime(); long max = runtime.maxMemory(); long total = runtime.totalMemory(); long free = runtime.freeMemory(); float percentage = 100 * free / total; if(max == total && memPercentCeiling >= percentage) { return true; } else { return false; } -- 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

14 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-1168) CoyoteInvoker.normalize() should handle empty URLs

by Ron Sigal (JIRA)

CoyoteInvoker.normalize() should handle empty URLs -------------------------------------------------- Key: JBREM-1168 URL: https://jira.jboss.org/jira/browse/JBREM-1168 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.5.2 (Flounder), 2.2.3.SP1 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.3.SP2, 2.5.2.SP1 (Flounder) When, for some reason, tomcat passes an empty URL to org.jboss.remoting.transport.coyote.CoyoteInvoker, the normalize() method throws an ArrayIndexOutOfBoundsException. The problem should be handled more gracefully. -- 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

14 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (JBREM-1165) Reduce log level of ""received new control socket for unrecognized listenerId" message

by Ron Sigal (JIRA)

Reduce log level of ""received new control socket for unrecognized listenerId" message -------------------------------------------------------------------------------------- Key: JBREM-1165 URL: https://jira.jboss.org/jira/browse/JBREM-1165 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.5.2 (Flounder), 2.2.3.SP1 Reporter: Ron Sigal Assignee: Ron Sigal Priority: Minor Fix For: 2.2.3.SP2, 2.5.2.SP1 (Flounder) This message indicates that, in the process of shutting removing a bisocket callback connection, the server side has been removed before the client side. Just before it gets shut down, the org.jboss.remoting.transport.bisocket.BisocketServerInvoker.ControlMonitorTimerTask has missed a control connection ping and tries to recreate the control connection. It's just a timing issue and the log message should be reduced from ERROR to INFO. -- 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

14 years, 10 months

1
6
0 / 0

[JBoss JIRA] Created: (JBREM-1164) Remoting shouldn't require IPv6 addresses to be surrounded by brackets

by Ron Sigal (JIRA)

Remoting shouldn't require IPv6 addresses to be surrounded by brackets ---------------------------------------------------------------------- Key: JBREM-1164 URL: https://jira.jboss.org/jira/browse/JBREM-1164 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.5.2 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2.SP1 (Flounder) Although IPv6 addresses are surrounded by brackets in URLs, the addresses themselves don't have brackets. Thus, it should be possible to start the Application Server with run.sh -b ::1 instead of requiring run.sh -b [::1] -- 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

14 years, 10 months

3
17
0 / 0

[JBoss JIRA] Created: (JBREM-1166) Possible race condition in ConnectionValidator

by Takayoshi Kimura (JIRA)

Possible race condition in ConnectionValidator ---------------------------------------------- Key: JBREM-1166 URL: https://jira.jboss.org/jira/browse/JBREM-1166 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.3.SP1, 2.2.3 Reporter: Takayoshi Kimura Fix For: 2.2.3.SP2 The 2.2.3 has a minor regression. The ConnectionValidator#start() has been moved outside of synchronized block in this release, this leads a race condition problem. ConnectionValidator#start(): TimerUtil.schedule(this, pingPeriod); // will call ConnectionValidator.run() timer = new Timer(true); // is used in ConnectionValidator.run() These 2 lines looks odd, because it initializes the timer for new thread after spawn the thread. In 2.2.2-SP11 the timer variable is protected by synchronized blocks, so it's not the case. -- 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

14 years, 10 months

2
8
0 / 0

[JBoss JIRA] Created: (JBREM-1162) Release 2.5.2.SP1

by Ron Sigal (JIRA)

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

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-1096) Remoting 2 entity metadata

by David Lloyd (JIRA)

Remoting 2 entity metadata -------------------------- Key: JBREM-1096 URL: https://jira.jboss.org/jira/browse/JBREM-1096 Project: JBoss Remoting Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd -- 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

14 years, 11 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues November 2009