But I'd rather not suspect that it could depend on the amount of data transferred. I'm not the ftp expert that much to claim if it is the server or module issue at the moment. At the moment I can't tell you why the data channel would last longer after issuing the close command if it really is the case. It would be important to know how long it takes to close the connection. Is the MIDlet doing any other network connections with pure Java? Please test the service state after closing the ftp connection (For FTP state 5 - closing - can mean that the command connection is already released, 4 - up - both connections are active). So it is the same as the commands would be issued on external interface while the custom MIDlet is running. With the file sizes being transmitted varying considerably from 60 bytes to 112Kbytes, I'll need to check the overall affect on performance since this can be critical on certain applications with other factors limiting the order in which I do things. If opening a new profile won't give an issue - ie potentially having multiple data connections open on different profiles, I'll try that, though my preference would be to just add the data connection check - unless it results in unacceptable delays between FTP transmissions. The nullPointerException only occurred once - though still one time too many !!, the 'Data Connection already Open' being the main problem.
1and1 ftp filezilla code#
This would have been shown in my code if your web site filter hadn't stopped me adding it. Though I already check the service state before I close the connection - I wait until the service returns the ^SISW URC indicating that is ready to accept new data - if I have interpreted this correctly - is this sufficient? - so not relying on just at^SISC. I had not appreciated there are two connection. So I would be surprised if the data connection was still open when trying to transmit so few bytes - this may give issues for later FTP transmissions which are larger files - up to 112Kbytes - which means affecting the overall FTP transmission time The first file is just over 1Kbyte, and the second only 60 byte. Thus there is a delay between each FTP transmission - my response to issuing the script file. The Java application is polling an external Micro-Controller - though for testing a HyperTerminal is substituted for the Micro-Controller with script files being used to provide the data to ASC0 on the EHS6T in response to the poll command. The testing I have carried out is not solely Java. Thank you for your reply which is much appreciated.
^SISI: 1,4,0,0,0,0 … indicating the FTP connection is up and running. URC’s as above until 'DataConnection Open'.
^SIS: 1,0,2100,"S:125 Data connection already open Transfer starting." I would have included more code, but the Spam filter is stopping me.
If I inserted a big delay between the FTP transmissions it will complete ok – presumably after some other timeout delay.Īny thoughts on curing this issue would be appreciated. What can cause the connection not be closed after a at^sisc command? It appears as though even a AT^SISC= 1 ‘Internet Connection Close command’ is issued between the FTP transmissions, and appears to accept the command, and therefore I would have expected the connection to close and allow me to establish a new connection immediatedly. I am having issues between FTP transmissions, mixture of fput, put transmissions.īefore the fault I notice I get a URC ‘Data Connection already open’ message.
0 kommentar(er)
