AttachmentsImpl.removeAttachment() has return of true and false reversed
------------------------------------------------------------------------
Key: JBREM-1243
URL: https://jira.jboss.org/browse/JBREM-1243
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.1.0.Beta2
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 3.1.0.Beta3
In org.jboss.remoting3.AttachmentsImpl.removeAttachment(), the lines returning false and true should be reversed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Update svn properties
---------------------
Key: JBREM-1241
URL: https://jira.jboss.org/browse/JBREM-1241
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 2.2.3.SP2
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.3.SP3
Some of the files are missing the svn:eol-style property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Avoid excessive calls to InetAddress.getLocalHost() [Clone of JBREM-1234]
-------------------------------------------------------------------------
Key: JBREM-1235
URL: https://jira.jboss.org/browse/JBREM-1235
Project: JBoss Remoting
Issue Type: Quality Risk
Security Level: Public (Everyone can see)
Affects Versions: 2.5.3 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.3.SP1
>From JBPAPP-4617 "Possible performance issue in Remoting":
JMS remote connections that are used locally result in a lot of calls to InetAddress.getLocalHost() which for some reason is slow.
Why not:
private static final InetAddress LOCAL_HOST;
static
{
try
{
LOCAL_HOST = InetAddress.getLocalHost();
}
catch (UnknownHostException e)
{
throw new ExceptionInInitializerError(e);
}
}
private static InetAddress getLocalHost() throws UnknownHostException
{
return LOCAL_HOST;
}
Which is roughly 1000x faster.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Assure version compatibility with earlier versions of Remoting
--------------------------------------------------------------
Key: JBREM-1239
URL: https://jira.jboss.org/browse/JBREM-1239
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.3.SP3
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Client hangs when hitting MaxPoolSize with idleTimeout
------------------------------------------------------
Key: JBREM-1230
URL: https://jira.jboss.org/browse/JBREM-1230
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.2.3.SP1, 2.2.2.SP9
Reporter: Takayoshi Kimura
1. In SocketServerInvoker.processInvocation(), clientpool.wait() is called when hitting MaxPoolSize
2. SocketServerInvoker$IdleTimerTask calls ServerThread.shutdown() and remove it from clientpool when it's timed out in idle state
3. ServerThread.shutdown() doesn't call clientpool.notify(), so #1 doesn't resume although there is free slot available
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira