[
https://issues.apache.org/jira/browse/JAMES-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563771#comment-13563771
]
Eric Charles commented on JAMES-1472:
-------------------------------------
Hi Markus,
I have analyzed the 3 given thread dumps with IBMC JCA tool.
They all show remote delivery waiting thread, which is the normal state when
the threads are waiting on mails from ActiveMQ queues.
All the other thread seem normal: no deadlock, no huge number of spooling
threads that could indicate something wrong...
If you want to give a try to the FileQueue to see if the issue if related to
ActiveMQ or not (could be something else in your system/env), you can update
the META-INF/org/apache/james/spring-server.xml :
comment out <bean id="mailqueuefactory"
class="org.apache.james.queue.file.FileMailQueueFactory" />
comment in <bean id="mailqueuefactory"
class="org.apache.james.queue.activemq.ActiveMQMailQueueFactory"
depends-on="broker" />
Thx, Eric
> ReferenceStore not valid ... / Mail spooled but not processed
> -------------------------------------------------------------
>
> Key: JAMES-1472
> URL: https://issues.apache.org/jira/browse/JAMES-1472
> Project: James Server
> Issue Type: Bug
> Components: Remote Delivery, SpoolManager & Processors
> Affects Versions: 3.0-beta3
> Environment: Red Hat Enterprise Linux Server release 5.7 (Tikanga),
> Reporter: Markus Moldaschl
> Attachments: dump1.log, dump2.log, dump3.log
>
>
> see
> http://mail-archives.apache.org/mod_mbox/james-server-user/201301.mbox/browser
> for the description of the problem
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]