Hi Ajay
Firstly, you are not alone. While I have not experienced an issue with
the outgoing queue I have had issues with the incoming.
In my case the class org.apache.james.queue.jms.JMSMailQueue handles
retrieving mail from the incoming spool, however despite the routine
checking the queue every ten seconds the mail item can remain stuck in
the spool until another email is sent which pushes the stuck item out of
the queue. So far I have not discovered what causes this blockage in the
queue to occur or disappear as sending another email while it pushes the
blockage out results in the new email being stuck in the queue.
What you may find useful is raising the log level on activemq - *without
restarting james*. Connect up jvisualvm/jconsole to dynamically reload
the log4j config for activemq. MBean of interest -
org.apache.activemq.james.Broker, Operation reloadLog4jProperties.
When a blockage is discovered changing the number of spool threads,
delivery threads etc seems to at times help. But this may just be
because you're stopping and restarting the server and not due to the
configuration change.
I am interested to hear how this goes for you as I'm in a similar
situation and the issues may well be related.
Thanks
Phillip
On 2/12/13 6:45 AM, Ajay Navgale wrote:
Hi,
We are using james 3.0 beta4.
We have an issue while sending an email. There is always one outgoing mail
left in spool and is delivered when any new outgoing mail is to be sent.
Now previous mail gets delivered and this recent once sits in the spool.
This is happening for Remote delivery.
Can anyone throw some light on this.
Thanks & Regards,
Ajay
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
