mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ceki Gulcu (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (FTPSERVER-403) FTP would periodically hang in MDC
Date Mon, 31 Oct 2011 22:59:32 GMT

    [ https://issues.apache.org/jira/browse/FTPSERVER-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140608#comment-13140608
] 

Ceki Gulcu edited comment on FTPSERVER-403 at 10/31/11 10:57 PM:
-----------------------------------------------------------------

SLF4J bug 203 was fixed moments ago and is part of SLF4J version 1.6.4.

                
      was (Author: ceki@qos.ch):
    SLF4J bug 203 will be fixed shortly.
                  
> FTP would periodically hang in MDC
> ----------------------------------
>
>                 Key: FTPSERVER-403
>                 URL: https://issues.apache.org/jira/browse/FTPSERVER-403
>             Project: FtpServer
>          Issue Type: Bug
>          Components: Core, Server
>    Affects Versions: 1.0.3, 1.0.4, 1.0.5, 1.0.6
>         Environment: Encountered it both on Linux and FreeBSD, both on Sun JVM 1.6 and
OpenJDK 6.
>            Reporter: ArtemGr
>
> FTP works fine for the most time but once in a while (depended on how often the FTP is
used) it would hang, consuming 100% CPU, in
>         java.util.HashMap.removeEntryForKey (HashMap.java:586)
>         java.util.HashMap.remove (HashMap.java:555)
>         org.slf4j.helpers.BasicMDCAdapter.remove (BasicMDCAdapter.java:91)
>         org.slf4j.MDC.remove (MDC.java:156)
>         org.apache.mina.filter.logging.MdcInjectionFilter.filter (MdcInjectionFilter.java:141)
>         org.apache.mina.filter.util.CommonEventFilter.messageSent (CommonEventFilter.java:75)
>         org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageSent (DefaultIoFilterChain.java:462)
>         org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1300 (DefaultIoFilterChain.java:46)
>         org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageSent
(DefaultIoFilterChain.java:802)
>         org.apache.mina.filter.codec.ProtocolCodecFilter.messageSent (ProtocolCodecFilter.java:287)
>         org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageSent (DefaultIoFilterChain.java:462)
>         org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1300 (DefaultIoFilterChain.java:46)
>         org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageSent
(DefaultIoFilterChain.java:802)
>         org.apache.mina.core.filterchain.IoFilterEvent.fire (IoFilterEvent.java:80)
>         org.apache.mina.core.session.IoEvent.run (IoEvent.java:63)
>         org.apache.mina.filter.executor.OrderedThreadPoolExecutor$Worker.runTask (OrderedThreadPoolExecutor.java:780)
>         org.apache.mina.filter.executor.OrderedThreadPoolExecutor$Worker.runTasks (OrderedThreadPoolExecutor.java:772)
>         org.apache.mina.filter.executor.OrderedThreadPoolExecutor$Worker.run (OrderedThreadPoolExecutor.java:714)
>         java.lang.Thread.run (Thread.java:636)
> Seems like a synchronization issue to me.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message