I've now updated with MINA 2.0.0 M6 but am still getting the exception. Nothing should be sent to the client from MINA as every client that connects will send only its GPS data every x minutes. If the data is incorrect or in the wrong format, the client is not made aware of this (my app will just discard it).
I have although added a LoggingFilter to the FilterChain in each session to log what is sent/received and it appears that nothing is sent to the client prior to the exception occurring. Could this be a memory related issue? Because I've set it up now that say, port 2000 and 2001 use MINA, and port 2002 uses QuickServer. When all were using MINA, port 2002 had the majority of clients connected (~50-90) and the exception would occur there only. But now that 2002 is using QS, I get the same exceptions occurring in both ports 2000 and 2001. The clients connected to these ports also send GPS data but in a different format. I'm not too sure how else I can overcome this exception, if anyone has any ideas I'd greatly appreciate it Thanks Conrad Emmanuel Lecharny wrote: > > On Tue, Jun 2, 2009 at 8:54 AM, conrad_ <[email protected]> wrote: >> >> Thankyou for your reply, but are you sure? > > pretty much. The stack trace is clear about it. "Connection remote by > peer" >> >> My server used the QuickServer framework before using MINA and this >> exception never occurred with QS. >> >> The client(s) have not changed, as they connect and behave the same way >> as >> always (always keeps the connection), but when they connect to the server >> that uses MINA, the IOException occurs, but with QS the exception never >> occured. This is what has lead me to believe that it is a MINA problem. >> >> Could the client had closed the socket because of something happening on >> the >> MINA side (something not enabling the client to continue so forcing to >> close >> the socket)? > > This is an option. Many application will simply close the connection > if they receive something wrong. > > In this case, I would suggest you check what's sent to the client > before the connection is closed. Wireshark could help. > > You would also like to use MINA 1.1.7 version, which is much mature, > unless you are stuck with an old version of JDK. Give a try to MINA > 2.0.0 too. > > -- > Regards, > Cordialement, > Emmanuel Lécharny > www.iktek.com > > -- View this message in context: http://www.nabble.com/java.io.IOException%3A-Connection-reset-by-peer-problem-tp23825854p23846428.html Sent from the Apache MINA User Forum mailing list archive at Nabble.com.
