Author: norman
Date: Sat Jan 23 18:18:28 2010
New Revision: 902453
URL: http://svn.apache.org/viewvc?rev=902453&view=rev
Log:
cleanup config.xml to remove nntpserver and cornerstone services
Modified:
james/server/trunk/spring-deployment/src/main/config/james/james-config.xml
Modified:
james/server/trunk/spring-deployment/src/main/config/james/james-config.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/spring-deployment/src/main/config/james/james-config.xml?rev=902453&r1=902452&r2=902453&view=diff
==============================================================================
--- james/server/trunk/spring-deployment/src/main/config/james/james-config.xml
(original)
+++ james/server/trunk/spring-deployment/src/main/config/james/james-config.xml
Sat Jan 23 18:18:28 2010
@@ -1128,74 +1128,7 @@
</imapserver>
- <!-- The NNTP server is enabled by default -->
- <!-- Disabling blocks will stop them from listening, -->
- <!-- but does not free as many resources as removing them would -->
- <!-- NNTP-specific: if you disable the NNTP Server, you should also set
the nntp-repository's
- threadCount to 0, otherwise there will be threads active and polling
-->
- <nntpserver enabled="true">
- <!-- THE NNTP PROTOCOL IS EXPERIMENTAL AND NOT AS WELL TESTED AS SMTP AND
POP3 IN THIS RELEASE.
- The James project recommends that you check the James web site for
updates to the NNTP
- service. -->
- <!-- port 563 is the well-known/IANA registered port for NNTP over
SSL/TLS -->
- <!-- port 119 is the well-known/IANA registered port for Standard NNTP
-->
- <port>119</port>
-
- <!-- Uncomment this if you want to bind to a specific inetaddress -->
- <!--
- <bind> </bind>
- -->
- <!-- Uncomment this if you want to use TLS (SSL) on this port -->
- <!--
- <useTLS>true</useTLS>
- -->
-
- <handler>
- <!-- This is the name used by the server to identify itself in the
NNTP -->
- <!-- protocol. If autodetect is TRUE, the server will discover its
-->
- <!-- own host name and use that in the protocol. If discovery fails,
-->
- <!-- the value of 'localhost' is used. If autodetect is FALSE, James
-->
- <!-- will use the specified value. -->
- <!--
- <helloName autodetect="true">myMailServer</helloName>
- -->
- <connectiontimeout>120000</connectiontimeout>
- <!-- Set the authRequired value to true to enable authenticated NNTP
-->
- <authRequired>false</authRequired>
- </handler>
- </nntpserver>
-
- <nntp-repository>
- <!-- If this is set to true, posting will be disallowed. -->
- <readOnly>false</readOnly>
-
- <rootPath>file://var/nntp/groups</rootPath>
- <tempPath>file://var/nntp/temp</tempPath>
- <articleIDPath>file://var/nntp/articleid</articleIDPath>
- <articleIDDomainSuffix>news.james.apache.org</articleIDDomainSuffix>
-
- <!-- The news groups hosted in this NNTP repository. -->
- <!-- Groups here will be added to those found in the file system,
- but removing groups from here will NOT remove them from the
- server. Change <newsgroups> to <newsgroups only="true"> to
- restrict newsgroups to ONLY those found in this list. -->
- <newsgroups>
- <newsgroup>org.apache.james.dev</newsgroup>
- <newsgroup>org.apache.james.user</newsgroup>
- <newsgroup>org.apache.avalon.dev</newsgroup>
- <newsgroup>org.apache.avalon.user</newsgroup>
- </newsgroups>
-
- <spool class="org.apache.james.nntpserver.repository.NNTPSpooler">
- <configuration>
- <spoolPath>file://var/nntp/spool</spoolPath>
- <!-- The number of threads that process spooler related tasks. -->
- <threadCount>1</threadCount>
- <!-- The spool thread(s) should idle for some time, if it has
nothing to do -->
- <threadIdleTime>60000</threadIdleTime>
- </configuration>
- </spool>
- </nntp-repository>
+
<!-- Spool repository configuration -->
<!-- The spool repository is the location where incoming mails are
temporarily stored -->
@@ -1533,122 +1466,4 @@
-->
</database-connections>
-
- <!-- Configuration for Cornerstone Services -->
- <!-- -->
- <!-- For a simple configuration, nothing beneath this line should require
-->
- <!-- alteration. -->
- <!-- -->
- <!-- You will need to adjust the Socket Manager service configuration if
you want -->
- <!-- to enable secure sockets (TLS) for any James service.
-->
- <!-- -->
- <!-- Complex or high volume configurations may require changes to the
parameters -->
- <!-- in this section. Please read the James and Avalon documentation
before -->
- <!-- attempting to adjust this section. -->
- <!-- -->
-
- <!-- The Connection Manager block -->
- <!-- -->
- <!-- The idle-timeout is the number of milliseconds that it will take for
idle -->
- <!-- client connections managed by this connection manager to be marked at
timed out. -->
- <!-- If no value is specified, the value defaults to 5 minutes, 300000
milliseconds -->
- <!-- A value of 0 means that client sockets will not timeout. -->
- <!-- -->
- <!-- 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 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 -->
- <!-- serve to limit the number of open connections. -->
- <!-- -->
- <!-- The max-connections-per-ip parameter specifies the default maximum
number of client -->
- <!-- connections per ip 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 0 ( disabled) . -->
- <!-- -->
- <connections>
- <idle-timeout>300000</idle-timeout>
- <max-connections>30</max-connections>
- <!--
- <max-connections-per-ip>0</max-connections-per-ip>
- -->
- </connections>
-
- <!-- The Socket Manager block -->
- <!-- -->
- <!-- The server-sockets element has a number of factory sub-elements. -->
- <!-- Each of the factory elements has a name and class attribute -->
- <!-- The name attribute for each factory element must be unique. -->
- <!-- The class attribute is the name of a class that implements the -->
- <!-- interface org.apache.avalon.cornerstone.services.ServerSocketFactory
-->
- <!-- Specific factory elements may require some sub-elements. This is -->
- <!-- factory class dependent. -->
- <!-- -->
- <!-- The client-sockets element has a number of factory sub-elements. -->
- <!-- Each of the factory elements has a name and class attribute -->
- <!-- The name attribute for each factory element must be unique. -->
- <!-- The class attribute is the name of a class that implements the -->
- <!-- interface org.apache.avalon.cornerstone.services.SocketFactory -->
- <!-- Specific factory elements may require some sub-elements. This is -->
- <!-- factory class dependent. -->
- <!-- -->
- <!-- In order to use the ssl factory under Java 1.5 and support all Clients
-->
- <!-- (particularly Mozilla Thunderbird) you need to install the Sun JCE -->
- <!-- provider in your environment (james/lib) -->
- <!-- e.g: jre/lib/ext/sunjce_provider.jar -->
- <!-- -->
- <sockets>
- <server-sockets>
- <factory name="plain"
class="org.apache.avalon.cornerstone.blocks.sockets.DefaultServerSocketFactory"/>
- <!--
- <factory name="ssl"
class="org.apache.avalon.cornerstone.blocks.sockets.TLSServerSocketFactory">
- <ssl-factory>
- <keystore>
- <file>conf/keystore</file>
- <password>secret</password>
- <key-password>keysecret</key-password>
- <type>JKS</type>
- <protocol>TLS</protocol>
- <algorithm>SunX509</algorithm>
- <authenticate-client>false</authenticate-client>
- </keystore>
- </ssl-factory>
- </factory>
- -->
- </server-sockets>
- <client-sockets>
- <factory name="plain"
class="org.apache.avalon.cornerstone.blocks.sockets.DefaultSocketFactory"/>
- </client-sockets>
- </sockets>
-
- <!-- The Thread Manager block -->
- <!-- -->
- <!-- The thread manager provides thread pools for use throughout the
server. -->
- <!-- -->
- <!-- A thread pool with the name "default" must be defined in this thread
manager -->
- <!-- configuration. -->
- <!-- -->
- <!-- Each thread pool is defined with a "thread-group" element. -->
- <!-- Each of these elements has the following required sub-elements: -->
- <!-- name - the name of the thread pool, used by other components to -->
- <!-- lookup the thread pool -->
- <!-- priority - the thread priority for threads in the pool. This is -->
- <!-- a value between 0 and 10, with 5 being the normal -->
- <!-- priority and 10 being the maximum. -->
- <!-- is-daemon - whether the threads in the pool are daemon threads. -->
- <!-- max-threads - the maximum number of threads allowed in the pool. -->
- <!-- min-threads - the minimum number of threads allowed in the pool.
(not implemented) -->
- <!-- min-spare-threads - (not implemented) -->
- <thread-manager>
- <thread-group>
- <name>default</name>
- <priority>5</priority>
- <is-daemon>false</is-daemon>
- <max-threads>100</max-threads>
- <min-threads>20</min-threads>
- <min-spare-threads>20</min-spare-threads>
- </thread-group>
- </thread-manager>
</config>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
