Michael Weissenbacher ha scritto:
Hi,
It should work also with DBs and we are not aware of any racing
condition or locking issue in 2.3.0. So you are probably hitting an
unknown bug. I never seen this behaviour on 2.3.0 so I cannot
investigate on it, sorry.
I'll see if I can prepare a simple t
Hi,
It should work also with DBs and we are not aware of any racing
condition or locking issue in 2.3.0. So you are probably hitting an
unknown bug. I never seen this behaviour on 2.3.0 so I cannot
investigate on it, sorry.
I'll see if I can prepare a simple test-case for 2.3.0 and then make a
Michael Weissenbacher ha scritto:
Hi, I got some some news from the front :)
I am using MySQL for spooling, could this be the culprit?
I tried the normal File-Based spooling and everything is working
smoothly now. Is there any change to get it working with MySQL spooling
too?
Michael
It sh
Hi, I got some some news from the front :)
I am using MySQL for spooling, could this be the culprit?
I tried the normal File-Based spooling and everything is working
smoothly now. Is there any change to get it working with MySQL spooling too?
Michael
--
Hi,
What version of James are you using?
James 2.3.0
James 2.2.0 had bugs in spooling timings and often the send was delayed
10-60 seconds.
Sound pretty much like the problem I'm facing with 2.3.0.
The only option you have is to increase the number of spool threads /
delivery threads: this
What version of James are you using?
James 2.2.0 had bugs in spooling timings and often the send was delayed
10-60 seconds.
The only option you have is to increase the number of spool threads /
delivery threads: this way if the system can handle that you will get
faster deliveries.
Stefano
Hi List,
is there any way how i could influence whether a Mail is processed
immediately or spooled first? I have the requirement that a mail is
processed in under 10 seconds which is usually achieved easily. But
sometimes JAMES decides to spool the mail first and process it like 20
seconds lat
