> I seem to be having a problem whereby my mailet's DB connection is being
> closed after a period of about 5 minutes. 5 minutes is NOT a long time
> when you are sending an email to 50000 users...
It would help if you posted the error message. Are you getting the
***** connection XXX is way too old Y > L
message?
I'm not entirely sure that the approach being taken to connection pooling is
correct in that code, but that is only because the connection pools I've
written work differently. Regardless, Mordred isn't going to change, at
least right now. What COULD be done in the short term is add configuration
elements to allow the timeout parameters to be re-configured.
> is there any way I can alter the timeouts in James (or Avalon) to
> prevent timeouts from happening
Not yet. A change would be to remove the static final from the time limit
members of the class, and add additional statements to the configure method:
active_conn_time_limit =
configuration.getChild("active-time-limit").getValueAsInteger(60000);
conn_idle_limit =
configuration.getChild("idle-time-limit").getValueAsInteger(600000);
such that we can say:
<active-time-limit>xxxx</active-time-limit>
<idle-time-limit>yyyy</idle-time-limit>
This is pretty straightforward. Do you want to affect the change on your
end, test it, and submit it?
--- Noel
--
To unsubscribe, e-mail: <mailto:james-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@;jakarta.apache.org>
