Thank you so much for accepting my suggestion and hope that helps the future
developers. And thanks for your support over the past few days too!!!
--
View this message in context:
http://apache-mina.10907.n7.nabble.com/ProtocolEncoder-not-getting-used-in-the-response-path-tp51558p51620.html
Le 25/10/16 à 16:54, Murty Devarakonda a écrit :
> We could identify what the problem is at last. While sending the response
> back to the client, we created a IoBuffer and added the bytes to the same
> and did a session.write(). And we identified that if the response is of
> type IoBuffer, Min
tting-used-in-the-response-path-tp51558p51618.html
Sent from the Apache MINA User Forum mailing list archive at Nabble.com.
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
occurred invoking method.
I am looking into where this one popped out from.
--
View this message in context:
http://apache-mina.10907.n7.nabble.com/ProtocolEncoder-not-getting-used-in-the-response-path-tp51558p51604.html
Sent from the Apache MINA User Forum mailing list archive at Nabble.com.
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
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
ll as new port. Do you think the name "protocol" is causing some
conflicts? As the same name "protocol" is being used to add the code filter
factory for both instances of the acceptors?
--
View this message in context:
http://apache-mina.10907.n7.nabble.com/ProtocolEncode
pache-mina.10907.n7.nabble.com/ProtocolEncoder-not-getting-used-in-the-response-path-tp51558p51597.html
Sent from the Apache MINA User Forum mailing list archive at Nabble.com.
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
message in context:
http://apache-mina.10907.n7.nabble.com/ProtocolEncoder-not-getting-used-in-the-response-path-tp51558p51595.html
Sent from the Apache MINA User Forum mailing list archive at Nabble.com.
oject/userguide/ch9-codec-filter/ch9-codec-filter.html
page ?
>
>
>
> --
> View this message in context:
> http://apache-mina.10907.n7.nabble.com/ProtocolEncoder-not-getting-used-in-the-response-path-tp51558.html
> Sent from the Apache MINA User Forum mailing list archive at Nabble.com.
--
Emmanuel Lecharny
Symas.com
directory.apache.org
ast("limiter", filter);
>}
>}
>
> Any help with this would be greatly appreciated. I even tried logging the
> MINA related log lines at the debug level to see if there is an exception
> during response flow within MINA. But there is no exceptions too.
>
NA related log lines at the debug level to see if there is an exception
during response flow within MINA. But there is no exceptions too.
--
View this message in context:
http://apache-mina.10907.n7.nabble.com/ProtocolEncoder-not-getting-used-in-the-response-path-tp51558.html
Sent from the Ap
14 matches
Mail list logo
