Re: ProtocolEncoder not getting used in the response path

2016-10-24 Thread Murty Devarakonda
And not only that. I am seeing that the filter for my ProtocolCodecFilter also was not hit in the entry.getNextFilter() call. -- View this message in context: http://apache-mina.10907.n7.nabble.com/ProtocolEncoder-not-getting-used-in-the-response-path-tp51558p51605.html Sent from the Apache MI

Re: ProtocolEncoder not getting used in the response path

2016-10-24 Thread Murty Devarakonda
O.K. Some more progress. While going through the debugger in the file DefaultIoFilterChain.java and in the filterWrite method (line 734 and remember I am in MINA version 2.0.5), I tried to inspect the nextFilter argument and I got an exception in my eclipse: com.sun.jdi.InvocationException occur

Give Range of port - when starting sftpserver

2016-10-24 Thread Goyal, Arpit
Is there possibility to give range of ports between which Mina SSHD library always try to establish port-binding else fails? This is to make sure that certain ports are never taken by Apache MINA SSHD? Regards, Arpit.

Re: ProtocolEncoder not getting used in the response path

2016-10-24 Thread Emmanuel Lécharny
Le 24/10/16 à 19:24, Murty Devarakonda a écrit : > I did read that section to see where things may be going wrong and didn't see > anything that's different than what we are doing. > > Now, to explain a bit about our project, so far the MINA server is listening > on one port and protocol encoder

Re: ProtocolEncoder not getting used in the response path

2016-10-24 Thread Emmanuel Lécharny
Le 24/10/16 à 20:59, Murty Devarakonda a écrit : > Thank you for the tip. I looked into the NioSocketSession.filterChain and I > could see my protocolcodecfactory object there. Here is how I am adding the > filters: > > protected static void addFilters(Properties props, NioSocketAcceptor > acce

Re: ProtocolEncoder not getting used in the response path

2016-10-24 Thread Murty Devarakonda
Thank you for the tip. I looked into the NioSocketSession.filterChain and I could see my protocolcodecfactory object there. Here is how I am adding the filters: protected static void addFilters(Properties props, NioSocketAcceptor acceptor, ProtocolCodecFactory factory) { DefaultIoFil

Re: ProtocolEncoder not getting used in the response path

2016-10-24 Thread Murty Devarakonda
I did read that section to see where things may be going wrong and didn't see anything that's different than what we are doing. Now, to explain a bit about our project, so far the MINA server is listening on one port and protocol encoder and decoder seems to be working fine. Recently we changed t

Re: ProtocolEncoder not getting used in the response path

2016-10-24 Thread Emmanuel Lécharny
Le 24/10/16 à 19:12, Murty Devarakonda a écrit : > Thanks for the reply. I set the logging at the debug level for all the code > in org.apache and didn't see any exceptions being thrown or any error > messages. I tried to debug the MINA code, but didn't get much clues from it > in terms of any

Re: ProtocolEncoder not getting used in the response path

2016-10-24 Thread Murty Devarakonda
Thanks for the reply. I set the logging at the debug level for all the code in org.apache and didn't see any exceptions being thrown or any error messages. I tried to debug the MINA code, but didn't get much clues from it in terms of any eye popping error flows. -- View this message in context