Humm... I analized the config.xml file and I found:
<spool>
<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>
Could it be this parameter the problem? This means, NNTP Spool is processed each minute. Right? I will play with this parameters and post the share the results.
What I did before, was reading this: http://james.apache.org/nntp_configuration_2_1.html documentation page, and it ommits this block.... :-(
Regards,
Chemi.
Chemi wrote:
Hi, some weeks ago, I posted this comment/question about NNTP access to James 2.2.0 but i didn't receive any comment/answer and it is extrange because the delay to get the messages after they are posted is really big (sometimes 20 seconds).
<<
Hi, I am doing more tests with James 2.2.0 using its NNTP feature.
I have both: James and NNTP Client (Mozilla) phisically in the same box.
I send a message from Mozilla and... I have to wait an average of 8 to 20 seconds to see the message posted. Of course, I am refreshing my client all the time.
I have done the smae thing with other NNTP Servers currently in production in Internet and more or less post a message and read it, is automatic (1 second) and they are in different boxes around internet.
Is this a known issue of James? Or perhaps I have to tune it somewhere to improve the performance?
Thanks in advance for any comment,
Chemi.
>>
As I say, sometimes is really fats and sometimes not. It seems to me there is a slept thread which wakes up each x seconds and processes all the received messages. Does it make sense? Does exist this thread? Is there any way to setup it?
Thanks in advance,
Chemi.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
