You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by se...@james.apache.org on 2004/09/07 13:15:37 UTC
[jira] Created: (JAMES-321) Comments on configuri
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JAMES-321
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JAMES-321
Summary: Comments on configuri
Type: Improvement
Status: Unassigned
Priority: Minor
Project: James
Components:
Documentation
Versions:
2.2.0
Assignee:
Reporter: Hes Siemelink
Created: Tue, 7 Sep 2004 4:13 AM
Updated: Tue, 7 Sep 2004 4:13 AM
Description:
In the james-config.file in the section Connection Manager Block, there is a comment about configuring the max-connections parameter. It suggests that setting it to 0 means unlimited connections.
In practice however, it turns out that setting the value to 0 effectively creates a maximum of 1 connection.
(Due to the use of the HardResourceLimiting thread pool by the ServerConnection class, which defaults to a size of 1 if a size of 0 is specified.)
I would suggest to remove the comment in question to prevent confusion.
<!-- The Connection Manager block -->
...
<!-- The max-connections parameter specifies the default maximum number of client -->
<!-- connections that this connection manager will allow per managed server socket. -->
<!-- This value can be overridden by each individual service. -->
<!-- If no value is specified, the value defaults to 30. -->
<!-- A value of 0 means that there is no limit imposed by the connection manager, although -->
<!-- resource limitations imposed by other components (i.e. max # of threads) may -->
<!-- serve to limit the number of open connections. -->
<!-- -->
<connections>
<idle-timeout>300000</idle-timeout>
<max-connections>30</max-connections>
</connections>
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Resolved: (JAMES-321) Comments on configuri
Posted by "Vincenzo Gianferrari Pini (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-321?page=all ]
Vincenzo Gianferrari Pini resolved JAMES-321:
---------------------------------------------
Assign To: Vincenzo Gianferrari Pini
Resolution: Fixed
Fix Version: 2.2.1
> Comments on configuri
> ---------------------
>
> Key: JAMES-321
> URL: http://issues.apache.org/jira/browse/JAMES-321
> Project: James
> Type: Improvement
> Components: Documentation
> Versions: 2.2.0
> Reporter: Hes Siemelink
> Assignee: Vincenzo Gianferrari Pini
> Priority: Minor
> Fix For: 2.2.1
>
> In the james-config.file in the section Connection Manager Block, there is a comment about configuring the max-connections parameter. It suggests that setting it to 0 means unlimited connections.
> In practice however, it turns out that setting the value to 0 effectively creates a maximum of 1 connection.
> (Due to the use of the HardResourceLimiting thread pool by the ServerConnection class, which defaults to a size of 1 if a size of 0 is specified.)
> I would suggest to remove the comment in question to prevent confusion.
> <!-- The Connection Manager block -->
> ...
> <!-- The max-connections parameter specifies the default maximum number of client -->
> <!-- connections that this connection manager will allow per managed server socket. -->
> <!-- This value can be overridden by each individual service. -->
> <!-- If no value is specified, the value defaults to 30. -->
> <!-- A value of 0 means that there is no limit imposed by the connection manager, although -->
> <!-- resource limitations imposed by other components (i.e. max # of threads) may -->
> <!-- serve to limit the number of open connections. -->
> <!-- -->
> <connections>
> <idle-timeout>300000</idle-timeout>
> <max-connections>30</max-connections>
> </connections>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Commented: (JAMES-321) Comments on configuri
Posted by "Alan Gerhard (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-321?page=comments#action_62046 ]
Alan Gerhard commented on JAMES-321:
------------------------------------
Would rather explicitly state your findings.
Maybe the following would be better ??
- <!-- A value of 0 means that there is no limit imposed by the connection manager, although -->
+ <!-- A value of 0 creates a maximum of 1 connection due to the use of the HardResourceLimiting -->
+ <!-- thread pool by the ServerConnection class. -->
- <!-- resource limitations imposed by other components (i.e. max # of threads) may -->
+ <!-- Resource limitations imposed by other components (i.e. max # of threads) may -->
> Comments on configuri
> ---------------------
>
> Key: JAMES-321
> URL: http://issues.apache.org/jira/browse/JAMES-321
> Project: James
> Type: Improvement
> Components: Documentation
> Versions: 2.2.0
> Reporter: Hes Siemelink
> Priority: Minor
>
> In the james-config.file in the section Connection Manager Block, there is a comment about configuring the max-connections parameter. It suggests that setting it to 0 means unlimited connections.
> In practice however, it turns out that setting the value to 0 effectively creates a maximum of 1 connection.
> (Due to the use of the HardResourceLimiting thread pool by the ServerConnection class, which defaults to a size of 1 if a size of 0 is specified.)
> I would suggest to remove the comment in question to prevent confusion.
> <!-- The Connection Manager block -->
> ...
> <!-- The max-connections parameter specifies the default maximum number of client -->
> <!-- connections that this connection manager will allow per managed server socket. -->
> <!-- This value can be overridden by each individual service. -->
> <!-- If no value is specified, the value defaults to 30. -->
> <!-- A value of 0 means that there is no limit imposed by the connection manager, although -->
> <!-- resource limitations imposed by other components (i.e. max # of threads) may -->
> <!-- serve to limit the number of open connections. -->
> <!-- -->
> <connections>
> <idle-timeout>300000</idle-timeout>
> <max-connections>30</max-connections>
> </connections>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org