james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Closed: (JAMES-115) Fetching email by fetchPOP logged in wrong file if fetch fails
Date Sun, 06 Jun 2004 18:57:54 GMT
Message:

   The following issue has been closed.

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JAMES-115
    Summary: Fetching email by fetchPOP logged in wrong file if fetch fails
       Type: Bug

     Status: Closed
 Resolution: WON'T FIX

    Project: James
 Components: 
             James Core
   Versions:
             2.1

   Assignee: 
   Reporter: Marco Beelen

    Created: Sun, 13 Jul 2003 10:10 AM
    Updated: Sun, 6 Jun 2004 11:56 AM
Environment: Operating System: Windows NT/2K
Platform: PC

Description:
On my trouble-shooting-search for information about a failing fetchPOP-job I  
started looking in the fetchpop.log.
There was no information in that file

In the scheduler.log I get the follow message:

13/07/03 11:41:51 WARN  scheduler: Error occured executing trigger myFetchName
java.lang.NegativeArraySizeException
	at org.apache.commons.net.pop3.POP3Client.listMessages
(POP3Client.java:418)
	at org.apache.james.fetchpop.FetchPOP.targetTriggered(FetchPOP.java:124)
	at 
org.apache.avalon.cornerstone.blocks.scheduler.DefaultTimeScheduler.doRunEntry
(DefaultTimeScheduler.java:240)
	at 
org.apache.avalon.cornerstone.blocks.scheduler.DefaultTimeScheduler.access$000
(DefaultTimeScheduler.java:36)
	at 
org.apache.avalon.cornerstone.blocks.scheduler.DefaultTimeScheduler$1.run
(DefaultTimeScheduler.java:216)
	at org.apache.avalon.excalibur.thread.impl.ExecutableRunnable.execute
(ExecutableRunnable.java:47)
	at org.apache.avalon.excalibur.thread.impl.WorkerThread.run
(WorkerThread.java:80)

I would expect also an entry in the fetchpop.log stating the job has been run 
but failed and for more information about what went wrong to look in the 
scheduler.log OR move the logging of the failing fetch the fetchpop.log


---------------------------------------------------------------------
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