January 2010 - jboss-jira - Jboss List Archives

[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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-1178) Release 2.5.2.SP2

by Ron Sigal (JIRA)

Release 2.5.2.SP2 ----------------- Key: JBREM-1178 URL: https://jira.jboss.org/jira/browse/JBREM-1178 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-1174) Update jars to match EAP 5.0.1

by Ron Sigal (JIRA)

Update jars to match EAP 5.0.1 ------------------------------ Key: JBREM-1174 URL: https://jira.jboss.org/jira/browse/JBREM-1174 Project: JBoss Remoting Issue Type: Task 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, 4 months

1
5
0 / 0

[JBoss JIRA] Created: (JBREM-1172) SSLSocketBuilder should allow keystore and truststore URLs to be "NONE"

by Ron Sigal (JIRA)

SSLSocketBuilder should allow keystore and truststore URLs to be "NONE" ----------------------------------------------------------------------- Key: JBREM-1172 URL: https://jira.jboss.org/jira/browse/JBREM-1172 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) Some Java Cryptography Extension (JCE) providers support hardware based key and truststores, such as PKCS#12 Smartcards. Rather than specify URLs for keystores and truststores, the Java Secure Socket Extension (JSSE) Reference Guide (http://java.sun.com/j2se/1.5.0/docs/guide/security/jsse/JSSERefGuide.html) specifies that string "NONE" should be used. org.jboss.remoting.security.SSLSocketBuilder is unable to handler "NONE", and it throws a NullStoreURLException if no keystore or truststore (in the case that a truststore is necessary) is configured. -- 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, 4 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, 4 months

1
6
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, 4 months

1
5
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, 4 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, 4 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAS-6886) Upgrade to Remoting 2.5.2

by Ron Sigal (JIRA)

Upgrade to Remoting 2.5.2 ------------------------- Key: JBAS-6886 URL: https://jira.jboss.org/jira/browse/JBAS-6886 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: Ron Sigal Will have some important changes to support JBossMessaging. -- 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, 4 months

3
14
0 / 0

[JBoss JIRA] Created: (JBREM-1176) Fix classloader leak caused by client invoker destruction delay facility

by Ron Sigal (JIRA)

Fix classloader leak caused by client invoker destruction delay facility ------------------------------------------------------------------------ Key: JBREM-1176 URL: https://jira.jboss.org/jira/browse/JBREM-1176 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.5.2.SP1 (Flounder), 2.2.3.SP1 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.3.SP2, 2.5.2.SP2 (Flounder) This issue was turned up by https://jira.jboss.org/jira/browse/JBPAPP-3193 "Regression in EAP 4.x testsuite in Ejb3ClassloaderLeakUnitTestCase". The problem is that org.jboss.remoting.Client creates a static java.util.Timer which is never deleted. -- 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, 4 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2010