And another thing to try would to edit the file
"conf/context/james-server-context.xml" and replace the
"amq:connectionFactory...." entry with the following:
<amq:connectionFactory id="amqConnectionFactory"
brokerURL="vm://james?create=false">
<amq:prefetchPolicy>
<amq:prefetchPolicy queuePrefetch="1" topicPrefetch="1"/>
</amq:prefetchPolicy>
<property name="blobTransferPolicy" ref="blobTransferPolicy"/>
</amq:connectionFactory>
Bye,
Norman
2011/5/3 Norman Maurer <norman.mau...@googlemail.com>:
> Hi there,
>
> first of I never had such a problem. So here are some questions for
> you so we can hopefully track it down..
>
> 1) Did you also try to "flush" the queue and see if that does start
> the spooling ?
> 2) Do you have an special mailets/matchers (self-written) ?
>
> Thanks,
> Norman
>
>
> 2011/5/3 USHAKOV, Sergey <s.usha...@chemitech.ru>:
>> Hi all,
>>
>> sorry if double-posting, as I am not sure whether my mail comes through...
>>
>> Being a newbie with JAMES, I have currently an instance of JAMES running in
>> test/semi-production mode.
>>
>> Knowing for sure that some of the mails get occasionally "stuck" inside the
>> server, I have made an attempt to explore and manage the mail queues using
>> JConsole.
>>
>> Under the branch "org.apache.james/component/queue/spool" I have found an
>> manageable object that showed several items being present in the queue. I
>> was able to browse them. I was also offered several ways to remove them, but
>> that did not fit my intentions :)
>>
>> Having made severals stops and restarts of the server, I eventually managed
>> to reduce the number of the items in the queue from 26 to 2. With every
>> restart the "mailetcontainer.log" reported that some of the mails were
>> successfully delivered or sent out.
>>
>> But it's beyond my understanding what are the remaining mails doing silently
>> in the "root" state in the queue. Why nothing is reflected by the logs? Why
>> some of them get delivered upon restart, while others stay there? Is there
>> any facility for not removing a mail item, but rather for re-activating its
>> processing by the spool manager, in case the mail is in some suspended
>> state? It is evident by the way, that the mails remaining are preventing new
>> mails from being processed, as having sent in one more mail, I see now 3
>> items in the queue...
>>
>> Any ideas, as well as pointing to an appropriate manual, woulld be most
>> appreciated.
>>
>> Regards,
>> Sergey
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
>> For additional commands, e-mail: server-user-h...@james.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
