[jira] Commented: (FTPSERVER-331) FTP Client Not able to Sign in Caused by FTP Server's Unable to Open Connection

2009-09-16 Thread Yajun Dong (JIRA)

[ 
https://issues.apache.org/jira/browse/FTPSERVER-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12756339#action_12756339
 ] 

Yajun Dong commented on FTPSERVER-331:
--


Hi, Niklas:

The server cann't support FXP transfer mode for one server to our 
FtpSrver when the iptables service started, because the server does not enter 
PASV mode, and open a active port for transfer. So I have given a specified 
value to the port(the active port FtpServer opens) by PASV ports.

Now, I have given a other specified value to the port for FXP transfer 
mode. and the issue does not happened.

 FTP Client Not able to Sign in Caused by FTP Server's Unable to Open 
 Connection
 ---

 Key: FTPSERVER-331
 URL: https://issues.apache.org/jira/browse/FTPSERVER-331
 Project: FtpServer
  Issue Type: Bug
  Components: Server
Affects Versions: 1.0.2
 Environment: linux
Reporter: Yajun Dong
 Attachments: FTPSERVER-331-log.txt


 hi, I was using FTP SERVER-1.0.2 as my FTP server. Now, I found that the 
 server received command for CREATED, but it does not OPEN the connection to 
 client. Additionally, I have given a specified value to the control port, and 
 the range of data transfer ports. But I don't think it is the root of the 
 problem, because Server does not throw any exception of Address already in 
 use: JVM_Bind.
 partial log in attachement.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Closed: (FTPSERVER-331) FTP Client Not able to Sign in Caused by FTP Server's Unable to Open Connection

2009-09-16 Thread Yajun Dong (JIRA)

 [ 
https://issues.apache.org/jira/browse/FTPSERVER-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yajun Dong closed FTPSERVER-331.


Resolution: Fixed

 FTP Client Not able to Sign in Caused by FTP Server's Unable to Open 
 Connection
 ---

 Key: FTPSERVER-331
 URL: https://issues.apache.org/jira/browse/FTPSERVER-331
 Project: FtpServer
  Issue Type: Bug
  Components: Server
Affects Versions: 1.0.2
 Environment: linux
Reporter: Yajun Dong
 Attachments: FTPSERVER-331-log.txt


 hi, I was using FTP SERVER-1.0.2 as my FTP server. Now, I found that the 
 server received command for CREATED, but it does not OPEN the connection to 
 client. Additionally, I have given a specified value to the control port, and 
 the range of data transfer ports. But I don't think it is the root of the 
 problem, because Server does not throw any exception of Address already in 
 use: JVM_Bind.
 partial log in attachement.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (FTPSERVER-331) FTP Client Not able to Sign in Caused by FTP Server's Unable to Open Connection

2009-09-14 Thread Yajun Dong (JIRA)
FTP Client Not able to Sign in Caused by FTP Server's Unable to Open Connection
---

 Key: FTPSERVER-331
 URL: https://issues.apache.org/jira/browse/FTPSERVER-331
 Project: FtpServer
  Issue Type: Bug
  Components: Server
Affects Versions: 1.0.2
 Environment: linux
Reporter: Yajun Dong


hi, I was using FTP SERVER-1.0.2 as my FTP server. Now, I found that the server 
received command for CREATED, but it does not OPEN the connection to client. 
Additionally, I have given a specified value to the control port, and the range 
of data transfer ports. But I don't think it is the root of the problem, 
because Server does not throw any exception of Address already in use: 
JVM_Bind.

partial log in attachement.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (FTPSERVER-331) FTP Client Not able to Sign in Caused by FTP Server's Unable to Open Connection

2009-09-14 Thread Yajun Dong (JIRA)

 [ 
https://issues.apache.org/jira/browse/FTPSERVER-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yajun Dong updated FTPSERVER-331:
-

Attachment: FTPSERVER-331-log.txt

 FTP Client Not able to Sign in Caused by FTP Server's Unable to Open 
 Connection
 ---

 Key: FTPSERVER-331
 URL: https://issues.apache.org/jira/browse/FTPSERVER-331
 Project: FtpServer
  Issue Type: Bug
  Components: Server
Affects Versions: 1.0.2
 Environment: linux
Reporter: Yajun Dong
 Attachments: FTPSERVER-331-log.txt


 hi, I was using FTP SERVER-1.0.2 as my FTP server. Now, I found that the 
 server received command for CREATED, but it does not OPEN the connection to 
 client. Additionally, I have given a specified value to the control port, and 
 the range of data transfer ports. But I don't think it is the root of the 
 problem, because Server does not throw any exception of Address already in 
 use: JVM_Bind.
 partial log in attachement.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (FTPSERVER-331) FTP Client Not able to Sign in Caused by FTP Server's Unable to Open Connection

2009-09-14 Thread Yajun Dong (JIRA)

[ 
https://issues.apache.org/jira/browse/FTPSERVER-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12755331#action_12755331
 ] 

Yajun Dong commented on FTPSERVER-331:
--

It seems that the Session unable to opened. 

 FTP Client Not able to Sign in Caused by FTP Server's Unable to Open 
 Connection
 ---

 Key: FTPSERVER-331
 URL: https://issues.apache.org/jira/browse/FTPSERVER-331
 Project: FtpServer
  Issue Type: Bug
  Components: Server
Affects Versions: 1.0.2
 Environment: linux
Reporter: Yajun Dong
 Attachments: FTPSERVER-331-log.txt


 hi, I was using FTP SERVER-1.0.2 as my FTP server. Now, I found that the 
 server received command for CREATED, but it does not OPEN the connection to 
 client. Additionally, I have given a specified value to the control port, and 
 the range of data transfer ports. But I don't think it is the root of the 
 problem, because Server does not throw any exception of Address already in 
 use: JVM_Bind.
 partial log in attachement.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Issue Comment Edited: (FTPSERVER-331) FTP Client Not able to Sign in Caused by FTP Server's Unable to Open Connection

2009-09-14 Thread Yajun Dong (JIRA)

[ 
https://issues.apache.org/jira/browse/FTPSERVER-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12755331#action_12755331
 ] 

Yajun Dong edited comment on FTPSERVER-331 at 9/14/09 9:26 PM:
---

It seems that the Session is unable to open.

  was (Author: dongt...@gmail.com):
It seems that the Session unable to opened. 
  
 FTP Client Not able to Sign in Caused by FTP Server's Unable to Open 
 Connection
 ---

 Key: FTPSERVER-331
 URL: https://issues.apache.org/jira/browse/FTPSERVER-331
 Project: FtpServer
  Issue Type: Bug
  Components: Server
Affects Versions: 1.0.2
 Environment: linux
Reporter: Yajun Dong
 Attachments: FTPSERVER-331-log.txt


 hi, I was using FTP SERVER-1.0.2 as my FTP server. Now, I found that the 
 server received command for CREATED, but it does not OPEN the connection to 
 client. Additionally, I have given a specified value to the control port, and 
 the range of data transfer ports. But I don't think it is the root of the 
 problem, because Server does not throw any exception of Address already in 
 use: JVM_Bind.
 partial log in attachement.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (FTPSERVER-316) FTP-1.0.0 some exceptions were cast ,when trying to upload file via the public network.

2009-06-16 Thread Yajun Dong (JIRA)
FTP-1.0.0 some exceptions were cast ,when trying to upload file via the public 
network. 


 Key: FTPSERVER-316
 URL: https://issues.apache.org/jira/browse/FTPSERVER-316
 Project: FtpServer
  Issue Type: Bug
  Components: Core
Affects Versions: 1.0.0
 Environment: linux 
Reporter: Yajun Dong


client log/ flush fxp : 

[02:23:52] [右] STOR 
[52wy][Dragon_Ball_Kai][008][x264_aac][Chs_Cht_Jpn][720P][1BB41708].mkv 
[02:23:52] [右] 150 File status okay; about to open data connection. 
[02:23:59] (轻度中止) 
[02:23:59] [右] ABOR 
[02:24:00] (强行中止) 
[02:24:00] [右] 551 
/longzhugai/[52wy][Dragon_Ball_Kai][008][x264_aac][Chs_Cht_Jpn][720P][1BB41708].mkv:
 Error on output file. 
[02:24:00] [右] 传送失败! 
[02:24:00] [右] 连接丢失: 61.153.153.3 

=== 

ftp server log: 

[ INFO] 2009-06-15 02:25:33,893 [ikustih] [220.189.250.117] IOException during 
data transfer 
java.io.EOFException: Unexpected end of ZLIB input stream 
at java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:223) 
at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:141) 
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) 
at java.io.BufferedInputStream.read1(BufferedInputStream.java:258) 
at java.io.BufferedInputStream.read(BufferedInputStream.java:317) 
at java.io.FilterInputStream.read(FilterInputStream.java:90) 
at 
org.apache.ftpserver.impl.IODataConnection.transfer(IODataConnection.java:254) 
at 
org.apache.ftpserver.impl.IODataConnection.transferFromClient(IODataConnection.java:137)
 
at org.apache.ftpserver.command.impl.STOR.execute(STOR.java:163) 
at 
org.apache.ftpserver.impl.DefaultFtpHandler.messageReceived(DefaultFtpHandler.java:169)
 
at 
org.apache.ftpserver.listener.nio.FtpHandlerAdapter.messageReceived(FtpHandlerAdapter.java:65)
 
at 
org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:722)
 
at 
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
 
at 
org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:48)
 
at 
org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:802)
 
at 
org.apache.ftpserver.listener.nio.FtpLoggingFilter.messageReceived(FtpLoggingFilter.java:114)
 
at 
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
 
at 
org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:48)
 
at 
org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:802)
 
at 
org.apache.mina.core.filterchain.IoFilterEvent.fire(IoFilterEvent.java:59) 
at 
org.apache.mina.filter.logging.MdcInjectionFilter.filter(MdcInjectionFilter.java:137)
 
at 
org.apache.mina.filter.util.CommonEventFilter.messageReceived(CommonEventFilter.java:70)
 
at 
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
 
at 
org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:48)
 
at 
org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:802)
 
at 
org.apache.mina.filter.codec.ProtocolCodecFilter$ProtocolDecoderOutputImpl.flush(ProtocolCodecFilter.java:392)
 
at 
org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:228)
 
at 
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
 
at 
org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:48)
 
at 
org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:802)
 
at 
org.apache.mina.core.filterchain.IoFilterEvent.fire(IoFilterEvent.java:59) 
at org.apache.mina.core.session.IoEvent.run(IoEvent.java:64) 
at 
org.apache.mina.filter.executor.OrderedThreadPoolExecutor$Worker.runTask(OrderedThreadPoolExecutor.java:552)
 
at 
org.apache.mina.filter.executor.OrderedThreadPoolExecutor$Worker.runTasks(OrderedThreadPoolExecutor.java:544)
 
at 
org.apache.mina.filter.executor.OrderedThreadPoolExecutor$Worker.run(OrderedThreadPoolExecutor.java:488)
 
at java.lang.Thread.run(Thread.java:619) 
[ WARN] 2009-06-15 02:25:34,256 [ikustih] [220.189.250.117] SENT: 150 File 
status okay; about to open data connection. 

[ERROR] 2009-06-15 02:25:34,257 [ikustih] [220.189.250.117] 

[jira] Closed: (FTPSERVER-316) FTP-1.0.0 some exceptions were cast ,when trying to upload file via the public network.

2009-06-16 Thread Yajun Dong (JIRA)

 [ 
https://issues.apache.org/jira/browse/FTPSERVER-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yajun Dong closed FTPSERVER-316.


   Resolution: Later
Fix Version/s: 1.0.0

No problem. I've already realized the API for ftp-1.0 according to my 
requirements. Therefore I don't think there will be any issue if it upgrades to 
FTP-1.0.2. Thanks for you reply. 

 FTP-1.0.0 some exceptions were cast ,when trying to upload file via the 
 public network. 
 

 Key: FTPSERVER-316
 URL: https://issues.apache.org/jira/browse/FTPSERVER-316
 Project: FtpServer
  Issue Type: Bug
  Components: Core
Affects Versions: 1.0.0
 Environment: linux 
Reporter: Yajun Dong
 Fix For: 1.0.0


 client log/ flush fxp : 
 [02:23:52] [右] STOR 
 [52wy][Dragon_Ball_Kai][008][x264_aac][Chs_Cht_Jpn][720P][1BB41708].mkv 
 [02:23:52] [右] 150 File status okay; about to open data connection. 
 [02:23:59] (轻度中止) 
 [02:23:59] [右] ABOR 
 [02:24:00] (强行中止) 
 [02:24:00] [右] 551 
 /longzhugai/[52wy][Dragon_Ball_Kai][008][x264_aac][Chs_Cht_Jpn][720P][1BB41708].mkv:
  Error on output file. 
 [02:24:00] [右] 传送失败! 
 [02:24:00] [右] 连接丢失: 61.153.153.3 
 === 
 ftp server log: 
 [ INFO] 2009-06-15 02:25:33,893 [ikustih] [220.189.250.117] IOException 
 during data transfer 
 java.io.EOFException: Unexpected end of ZLIB input stream 
 at 
 java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:223) 
 at 
 java.util.zip.InflaterInputStream.read(InflaterInputStream.java:141) 
 at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) 
 at java.io.BufferedInputStream.read1(BufferedInputStream.java:258) 
 at java.io.BufferedInputStream.read(BufferedInputStream.java:317) 
 at java.io.FilterInputStream.read(FilterInputStream.java:90) 
 at 
 org.apache.ftpserver.impl.IODataConnection.transfer(IODataConnection.java:254)
  
 at 
 org.apache.ftpserver.impl.IODataConnection.transferFromClient(IODataConnection.java:137)
  
 at org.apache.ftpserver.command.impl.STOR.execute(STOR.java:163) 
 at 
 org.apache.ftpserver.impl.DefaultFtpHandler.messageReceived(DefaultFtpHandler.java:169)
  
 at 
 org.apache.ftpserver.listener.nio.FtpHandlerAdapter.messageReceived(FtpHandlerAdapter.java:65)
  
 at 
 org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:722)
  
 at 
 org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
  
 at 
 org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:48)
  
 at 
 org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:802)
  
 at 
 org.apache.ftpserver.listener.nio.FtpLoggingFilter.messageReceived(FtpLoggingFilter.java:114)
  
 at 
 org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
  
 at 
 org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:48)
  
 at 
 org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:802)
  
 at 
 org.apache.mina.core.filterchain.IoFilterEvent.fire(IoFilterEvent.java:59) 
 at 
 org.apache.mina.filter.logging.MdcInjectionFilter.filter(MdcInjectionFilter.java:137)
  
 at 
 org.apache.mina.filter.util.CommonEventFilter.messageReceived(CommonEventFilter.java:70)
  
 at 
 org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
  
 at 
 org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:48)
  
 at 
 org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:802)
  
 at 
 org.apache.mina.filter.codec.ProtocolCodecFilter$ProtocolDecoderOutputImpl.flush(ProtocolCodecFilter.java:392)
  
 at 
 org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:228)
  
 at 
 org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
  
 at 
 org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:48)
  
 at 
 org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:802)
  
 at 
 org.apache.mina.core.filterchain.IoFilterEvent.fire(IoFilterEvent.java:59) 
 at org.apache.mina.core.session.IoEvent.run(IoEvent.java:64) 
 at 
 

[jira] Created: (FTPSERVER-296) FTP-1.0.0 some exceptions were cast when trying to upload the huge file via the public network.

2009-04-28 Thread Yajun Dong (JIRA)
FTP-1.0.0 some exceptions were cast when trying to upload the huge file via the 
public network.
---

 Key: FTPSERVER-296
 URL: https://issues.apache.org/jira/browse/FTPSERVER-296
 Project: FtpServer
  Issue Type: New Feature
Affects Versions: 1.0.0
 Environment: ftp-1.0.0 on linux .
Reporter: Yajun Dong


hey. 

 The FTP-1.0.0 deployed over my linux, However, some exception were cast when 
trying to upload the huge file (500M) via the public network. 

===

[ INFO] 2009-04-29 00:48:51,659 [admin] [61.171.184.170] RECEIVED: PASV
[ WARN] 2009-04-29 00:48:51,659 [admin] [61.171.184.170] SENT: 227 Entering 
Passive Mode (222,73,163,169,229,37)


[ INFO] 2009-04-29 00:48:51,679 [admin] [61.171.184.170] RECEIVED: LIST
[ WARN] 2009-04-29 00:48:51,756 [admin] [61.171.184.170] SENT: 150 File status 
okay; about to open data connection.


[ WARN] 2009-04-29 00:48:51,756 [admin] [61.171.184.170] SENT: 226 Closing data 
connection.


[ INFO] 2009-04-29 00:48:52,104 [admin] [61.171.184.170] RECEIVED: PASV
[ WARN] 2009-04-29 00:48:52,104 [admin] [61.171.184.170] SENT: 227 Entering 
Passive Mode (222,73,163,169,148,232)


[ INFO] 2009-04-29 00:48:52,124 [admin] [61.171.184.170] RECEIVED: LIST
[ WARN] 2009-04-29 00:48:52,196 [admin] [61.171.184.170] SENT: 150 File status 
okay; about to open data connection.


[ WARN] 2009-04-29 00:48:52,197 [admin] [61.171.184.170] SENT: 226 Closing data 
connection.


[ WARN] 2009-04-29 00:49:47,712 [admin] [61.171.184.170] CLOSED
[ WARN] 2009-04-29 00:52:36,945 [admin] [61.171.184.170] SENT: 150 File status 
okay; about to open data connection.


[ WARN] 2009-04-29 00:52:36,945 [admin] [61.171.184.170] SENT: 551 
/oracle/NTSrv_disk1.ISO: Error on output file.


[ERROR] 2009-04-29 01:10:29,764 [admin] [61.171.184.170] EXCEPTION :
java.io.IOException: Connection timed out
at sun.nio.ch.FileDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233)
at sun.nio.ch.IOUtil.read(IOUtil.java:206)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:236)
at 
org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:180)
at 
org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:42)
at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:568)
at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:547)
at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:539)
at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.access$400(AbstractPollingIoProcessor.java:57)
at 
org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:867)
at 
org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:65)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
[ERROR] 2009-04-29 01:10:29,764 [admin] [61.171.184.170] Exception caught, 
closing session
java.io.IOException: Connection timed out
at sun.nio.ch.FileDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233)
at sun.nio.ch.IOUtil.read(IOUtil.java:206)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:236)
at 
org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:180)
at 
org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:42)
at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:568)
at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:547)
at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:539)
at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.access$400(AbstractPollingIoProcessor.java:57)
at 
org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:867)
at 
org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:65)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
[ WARN] 

[jira] Created: (FTPSERVER-295) Connection reset by peer, help

2009-04-27 Thread Yajun Dong (JIRA)
Connection reset by peer, help 
---

 Key: FTPSERVER-295
 URL: https://issues.apache.org/jira/browse/FTPSERVER-295
 Project: FtpServer
  Issue Type: Bug
  Components: Core
 Environment: linux  ftpserver-0.1-RC 
Reporter: Yajun Dong


when I upload a larger file, while the file would upload finished, throw the 
exception below :

09/04/27 22:20:03 WARN nio.FtpLoggingFilter: SENT: 150 File status okay; about 
to open data connection.

09/04/27 22:20:03 WARN nio.FtpLoggingFilter: SENT: 226 Transfer complete.

09/04/27 22:20:03 ERROR nio.FtpLoggingFilter: EXCEPTION :
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233)
at sun.nio.ch.IOUtil.read(IOUtil.java:206)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:207)
at 
org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:180)
at 
org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:42)
at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:568)
at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:547)
at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:539)
at 
org.apache.mina.core.polling.AbstractPollingIoProcessor.access$400(AbstractPollingIoProcessor.java:57)
at 
org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:867)
at 
org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:65)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
09/04/27 22:20:03 ERROR impl.DefaultFtpHandler: Exception caught, closing 
session

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (FTPSERVER-294) how to get the file-length from ftp server ?

2009-04-24 Thread Yajun Dong (JIRA)
how to get the file-length from ftp server ?


 Key: FTPSERVER-294
 URL: https://issues.apache.org/jira/browse/FTPSERVER-294
 Project: FtpServer
  Issue Type: Bug
  Components: Core
Affects Versions: 1.0.0
Reporter: Yajun Dong


Hi:
Excuse me, How can i get the file-length of uploading file from client in ftp 
server? i check it whether the file is intergrated, so that i will translate it 
to my system.
 
from China.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.