December 2009 - jboss-remoting-issues

[JBoss JIRA] Created: (JBREM-929) Secure remote classloading

by David Lloyd (JIRA)

Secure remote classloading -------------------------- Key: JBREM-929 URL: http://jira.jboss.com/jira/browse/JBREM-929 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 3.0.0-M3 Remote classloading should be allowed only if either (a) a security manager is installed (and thus the security manager would create the policy) or (b) a specific option is enabled (which would be disabled by default) to allow it. Also, the remote classloader needs to be able to work with the standard security manager policy - which is to say, that classes loaded from a remote service need to have a unique codeBase URL so that administrators can grant permission to remote classes based on the service from whence they came. -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-1171) Integrate remote protocol into R3

by David Lloyd (JIRA)

Integrate remote protocol into R3 --------------------------------- Key: JBREM-1171 URL: https://jira.jboss.org/jira/browse/JBREM-1171 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core Reporter: David Lloyd Assignee: 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: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

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

2
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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues December 2009