[ https://issues.apache.org/jira/browse/JAMES-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier closed JAMES-3727. --------------------------------- Resolution: Fixed > RemoteDelivery stops working > ---------------------------- > > Key: JAMES-3727 > URL: https://issues.apache.org/jira/browse/JAMES-3727 > Project: James Server > Issue Type: Bug > Components: James Core > Affects Versions: 3.5.0 > Environment: linux > Reporter: Dijana Vukovic > Priority: Critical > > We have switched production to james 3.5.0 but after 21k emails sent, it does > not work any more. > We have RemoteDelivery at debug level, so for each successful delivery should > see 2 logs "Attempting" and "sent to", but when james stops working we only > see "Attempting", but nothing is sent, stacktrace of one such failure is: > 11-Mar-2022 17:16:30.280 INFO [RemoteDelivery-2] > org.apache.james.transport.mailets.remote.delivery.MailDelivrer.doDeliver:145 > - Unable to parse headers from stream: > james-3.5.0-mo/bin/../var/store/activemq/blob-transfer/3/ID_localhost-53729-1646941913117-5_2_1_1_19595 > (No such file or directory) > 11-Mar-2022 17:16:31.546 INFO [RemoteDelivery-2] > org.apache.james.transport.mailets.remote.delivery.MailDelivrer.doDeliver:145 > - Unable to parse headers from stream: > james-3.5.0-mo/bin/../var/store/activemq/blob-transfer/3/ID_localhost-53729-1646941913117-5_2_1_1_19595 > (No such file or directory) > 11-Mar-2022 17:16:33.079 INFO [RemoteDelivery-2] > org.apache.james.transport.mailets.remote.delivery.MailDelivrer.doDeliver:145 > - Unable to parse headers from stream: > james-3.5.0-mo/bin/../var/store/activemq/blob-transfer/3/ID_localhost-53729-1646941913117-5_2_1_1_19595 > (No such file or directory) > 11-Mar-2022 17:16:34.658 INFO [RemoteDelivery-2] > org.apache.james.transport.mailets.remote.delivery.MailDelivrer.doDeliver:145 > - Unable to parse headers from stream: > james-3.5.0-mo/bin/../var/store/activemq/blob-transfer/3/ID_localhost-53729-1646941913117-5_2_1_1_19595 > (No such file or directory) > 11-Mar-2022 17:16:36.712 INFO [RemoteDelivery-2] > org.apache.james.transport.mailets.remote.delivery.MailDelivrer.doDeliver:145 > - Unable to parse headers from stream: > james-3.5.0-mo/bin/../var/store/activemq/blob-transfer/3/ID_localhost-53729-1646941913117-5_2_1_1_19595 > (No such file or directory) > 11-Mar-2022 17:16:36.739 ERROR [RemoteDelivery-69] > org.apache.james.transport.mailets.remote.delivery.DeliveryRunnable.lambda$start$1:88 > - Exception caught in RemoteDelivery > org.apache.james.queue.api.MailQueue$MailQueueException: Unable to enqueue > mail org.apache.james.server.core.MailImpl@202ac59d > at > org.apache.james.queue.jms.JMSCacheableMailQueue.enQueue(JMSCacheableMailQueue.java:282) > ~[james-server-queue-jms-3.5.0.jar:3.5.0] > at > org.apache.james.transport.mailets.remote.delivery.DeliveryRunnable.reAttemptDelivery(DeliveryRunnable.java:166) > ~[james-server-mailets-3.5.0.jar:3.5.0] > at > org.apache.james.transport.mailets.remote.delivery.DeliveryRunnable.handleTemporaryFailure(DeliveryRunnable.java:148) > ~[james-server-mailets-3.5.0.jar:3.5.0] > at > org.apache.james.transport.mailets.remote.delivery.DeliveryRunnable.attemptDelivery(DeliveryRunnable.java:131) > ~[james-server-mailets-3.5.0.jar:3.5.0] > at > org.apache.james.transport.mailets.remote.delivery.DeliveryRunnable.processMail(DeliveryRunnable.java:108) > ~[james-server-mailets-3.5.0.jar:3.5.0] > > If grep above on logs: > grep "53729-1646941913117-5_2_1_1_19595" * | wc -l > 42 times from 17:16:30.280 until 17:17:18.288 > If check indeed no such file > var/store/activemq/blob-transfer/3/ID_localhost-53729-1646941913117-5_2_1_1_19595 > but what is the problem, why is stuck, why trying 42x, why no any email go > out ever? > Restart does not change anything, so how to make it working again? From where > it reads such file must exist? -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org