james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (JAMES-153) Looping MessageException causes system stall
Date Wed, 14 Apr 2004 05:13:43 GMT
The following comment has been added to this issue:

     Author: Noel J. Bergman
    Created: Tue, 13 Apr 2004 10:12 PM
       Body:
Please test this against the current James test build.  There are several changes that should
have fixed this problem.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/JAMES-153?page=comments#action_35009

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JAMES-153

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JAMES-153
    Summary: Looping MessageException causes system stall
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: James
 Components: 
             MailStore & MailRepository
   Versions:
             2.1

   Assignee: 
   Reporter: Oliver Draese

    Created: Tue, 17 Feb 2004 3:20 AM
    Updated: Tue, 13 Apr 2004 10:12 PM
Environment: James 2.1.3 on RedHat Linux (x86) with Sun Java 1.4.2

Description:
James hangs and creates looping exception stack traces within the log files until the filesystem
runs full and the complete Linux box hangs. The following exception stack trace is added again
and again (several 1000 times) to the phoenix.console log file in the phoenix temp directory,
what causes an increadible big log file in temp, so that no filesystem space remains free:


javax.mail.MessagingException: Unknown encoding: text
        at javax.mail.internet.MimeUtility.encode(MimeUtility.java:309)
        at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1146)
        at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1600)
        at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1576)
        at org.apache.james.core.MailImpl.writeMessageTo(MailImpl.java:427)
        at org.apache.james.mailrepository.AvalonMailRepository.store(AvalonMailRepository.java:325)
        at org.apache.james.James.sendMail(James.java:499)
        at org.apache.james.James.sendMail(James.java:462)
        at org.apache.james.James.sendMail(James.java:444)
        at org.apache.james.James.storeMail(James.java:819)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.apache.avalon.phoenix.components.application.BlockInvocationHandler.invoke(BlockInvocationHandler.java:92)
        at $Proxy9.storeMail(Unknown Source)
        at org.apache.james.transport.mailets.LocalDelivery.service(LocalDelivery.java:111)
        at org.apache.james.transport.LinearProcessor.service(LinearProcessor.java:413)
        at org.apache.james.transport.JamesSpoolManager.process(JamesSpoolManager.java:436)
        at org.apache.james.transport.JamesSpoolManager.run(JamesSpoolManager.java:366)
        at org.apache.avalon.excalibur.thread.impl.ExecutableRunnable.execute(ExecutableRunnable.java:47)
        at org.apache.avalon.excalibur.thread.impl.WorkerThread.run(WorkerThread.java:80)

In the james log, the following line is repeating several 1000 times:
17/02/04 05:17:17 ERROR James: Error forwarding mail to draese@progredy.deattempting local
delivery

In the maillet log, the following exception is repeating several 1000 times:
17/02/04 07:22:37 INFO  James.Mailet: Error while storing mail.
javax.mail.MessagingException: Exception spooling message: Exception caught while storing
Message Container: javax.mail.MessagingException: Unknown encoding: text
;
  nested exception is:
        java.lang.RuntimeException: Exception caught while storing Message Container: javax.mail.MessagingException:
Unknown encoding: text
        at org.apache.james.James.sendMail(James.java:505)
        at org.apache.james.James.sendMail(James.java:462)
        at org.apache.james.James.sendMail(James.java:444)
        at org.apache.james.James.storeMail(James.java:819)
        at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.apache.avalon.phoenix.components.application.BlockInvocationHandler.invoke(BlockInvocationHandler.java:92)
        at $Proxy9.storeMail(Unknown Source)
        at org.apache.james.transport.mailets.LocalDelivery.service(LocalDelivery.java:111)
        at org.apache.james.transport.LinearProcessor.service(LinearProcessor.java:413)
        at org.apache.james.transport.JamesSpoolManager.process(JamesSpoolManager.java:436)
        at org.apache.james.transport.JamesSpoolManager.run(JamesSpoolManager.java:366)
        at org.apache.avalon.excalibur.thread.impl.ExecutableRunnable.execute(ExecutableRunnable.java:47)
        at org.apache.avalon.excalibur.thread.impl.WorkerThread.run(WorkerThread.java:80)

In the mailstore log, the following error sequence is repeating several 1000 times:
17/02/04 06:44:41 ERROR mailstore: Exception storing mail: javax.mail.MessagingException:
Unknown encoding: text
17/02/04 06:44:41 ERROR mailstore: Exception storing mail: javax.mail.MessagingException:
Unknown encoding: text
17/02/04 06:44:41 ERROR mailstore: Exception storing mail: javax.mail.MessagingException:
Unknown encoding: text
17/02/04 06:44:41 ERROR mailstore: Exception storing mail: javax.mail.MessagingException:
Unknown encoding: text
17/02/04 06:44:41 ERROR mailstore: Exception retrieving mail: java.lang.RuntimeException:
Exception caught while retrieving an object, cause: java.io.FileNotFound
Exception: /opt/james-2.1.3/apps/james/var/mail/spool/4D61696C313037363939363638313837372D353239373934.Repository.FileObjectStore
(No such file or directory), so
we're deleting it... good riddance!

The other log files seem to be OK. Wouldn't it be enough to show trace the exception once,
instead of looping it to all logs? This error occurrs on my system at least once per week
what causes me to have an extremely instable mail server environment because the filesystem
is running full all the times and I have to delete all the logs before I can go on.

Please let me know, if you need any further information to solve this problem


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message