Kenny Smith wrote:
Hi all,Kenny,
I'm having all of my mail backup in the spool tables (using JDBC) with a message_state of 'transport'. I've turned up my logging to DEBUG, but I'm not seeing anything in the logs that looks relevant to slow performance. I sent 230 email 2 hours ago and there are still 190 in the spool/transport waiting to get sent.
I saw the recent conversation about indexes on the spool table causing slow downs after a while, so I stopped James, dumped the table, removed the indicies, put the table back in and started James up. Nothing appears to have changed.
I'm running James 2.1 with jdk1.4 on Solaris.
Any help is appreciated.
Some of the new timeouts going into the more recent James should help with these long delivery/timeout issues.
The remote delivery could use more smarts by grouping messages into the different hostname buckets, so it knows the 3 messages going to yahoo.com accounts, and work through those buckets one by one, rather than the current message-based (so host-agnostic) ordering. That's more work and requires some refactoring to that spool implementation.
--
Serge Knystautas
President
Lokitech >> software . strategy . design >> http://www.lokitech.com/
p. 1.301.656.5501
e. [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
