|

»

»

»

java.net - Grizzly

»

Grizzly - Users

How ProtocolParser handle a disconnection from the client ?

View: New views

3 Messages — Rating Filter: Alert me

	How ProtocolParser handle a disconnection from the client ? by Survivant 00 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message I have a little bug in my program. The program is stuck in a loop in the first filter when a client close the connection wihtou sending data to the server. If the client had sent data before closing his session, the server will be fine here the usecase. start the server. a client do a telnet close the client telnet the server will loop. here the ouput for a normal connection GrizzlyGateway started listening for incomming TCP Connections on port : 5000 isExpectingMoreData startBuffer hasNextMessage hasNextMessage: feed\|aaa[eoq] index: 8 substr: substr.len: 0 getNextMessage query = feed\|aaa hasMoreBytesToParse isExpectingMoreData releaseBuffer isExpectingMoreData startBuffer hasMoreBytesToParse isExpectingMoreData releaseBuffer the client send a new request isExpectingMoreData startBuffer hasNextMessage hasNextMessage: quit\|a hasMoreBytesToParse isExpectingMoreData releaseBuffer isExpectingMoreData startBuffer hasNextMessage hasNextMessage: quit\|aaa[eoq] index: 8 substr: substr.len: 0 getNextMessage query = quit\|aaa ClientConnection close hasMoreBytesToParse isExpectingMoreData releaseBuffer isExpectingMoreData startBuffer hasMoreBytesToParse isExpectingMoreData releaseBuffer but if the client open the session and close is after that without sending a message.. it will loop GrizzlyGateway started listening for incomming TCP Connections on port : 5000 isExpectingMoreData startBuffer hasMoreBytesToParse isExpectingMoreData releaseBuffer isExpectingMoreData startBuffer hasMoreBytesToParse isExpectingMoreData releaseBuffer isExpectingMoreData startBuffer hasMoreBytesToParse isExpectingMoreData releaseBuffer isExpectingMoreData startBuffer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... QuoteQueryProtocolParser.java (11K) Download Attachment
	Re: How ProtocolParser handle a disconnection from the client ? by Oleksiy Stashok :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message It is fixed in the branch [1] Thank you!!! WBR, Alexey. [1] https://grizzly.dev.java.net/issues/show_bug.cgi?id=212 On Jul 21, 2008, at 22:29 , Survivant 00 wrote: > I have a little bug in my program. The program is stuck in a loop > in the first filter when a client close the connection wihtou > sending data to the server. If the client had sent data before > closing his session, the server will be fine > > here the usecase. > > start the server. > a client do a telnet > close the client telnet > the server will loop. > > here the ouput for a normal connection > > GrizzlyGateway started > listening for incomming TCP Connections on port : 5000 > isExpectingMoreData > startBuffer > hasNextMessage > hasNextMessage: feed\|aaa[eoq] > index: 8 substr: substr.len: 0 > getNextMessage > query = feed\|aaa > hasMoreBytesToParse > isExpectingMoreData > releaseBuffer > isExpectingMoreData > startBuffer > hasMoreBytesToParse > isExpectingMoreData > releaseBuffer > > > the client send a new request > > isExpectingMoreData > startBuffer > hasNextMessage > hasNextMessage: quit\|a > hasMoreBytesToParse > isExpectingMoreData > releaseBuffer > isExpectingMoreData > startBuffer > hasNextMessage > hasNextMessage: quit\|aaa[eoq] > index: 8 substr: substr.len: 0 > getNextMessage > query = quit\|aaa > ClientConnection close > hasMoreBytesToParse > isExpectingMoreData > releaseBuffer > isExpectingMoreData > startBuffer > hasMoreBytesToParse > isExpectingMoreData > releaseBuffer > > but if the client open the session and close is after that without > sending a message.. it will loop > > GrizzlyGateway started > listening for incomming TCP Connections on port : 5000 > isExpectingMoreData > startBuffer > hasMoreBytesToParse > isExpectingMoreData > releaseBuffer > isExpectingMoreData > startBuffer > hasMoreBytesToParse > isExpectingMoreData > releaseBuffer > isExpectingMoreData > startBuffer > hasMoreBytesToParse > isExpectingMoreData > releaseBuffer > isExpectingMoreData > startBuffer > > > < > QuoteQueryProtocolParser > .java > >--------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@...
	Re: How ProtocolParser handle a disconnection from the client ? by Survivant 00 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message cool thanks.. 2008/7/22 Oleksiy Stashok <Oleksiy.Stashok@...>: It is fixed in the branch [1] Thank you!!! WBR, Alexey. [1] https://grizzly.dev.java.net/issues/show_bug.cgi?id=212 On Jul 21, 2008, at 22:29 , Survivant 00 wrote: I have a little bug in my program. The program is stuck in a loop in the first filter when a client close the connection wihtou sending data to the server. If the client had sent data before closing his session, the server will be fine here the usecase. start the server. a client do a telnet close the client telnet the server will loop. here the ouput for a normal connection GrizzlyGateway started listening for incomming TCP Connections on port : 5000 isExpectingMoreData startBuffer hasNextMessage hasNextMessage: feed\|aaa[eoq] index: 8 substr: substr.len: 0 getNextMessage query = feed\|aaa hasMoreBytesToParse isExpectingMoreData releaseBuffer isExpectingMoreData startBuffer hasMoreBytesToParse isExpectingMoreData releaseBuffer the client send a new request isExpectingMoreData startBuffer hasNextMessage hasNextMessage: quit\|a hasMoreBytesToParse isExpectingMoreData releaseBuffer isExpectingMoreData startBuffer hasNextMessage hasNextMessage: quit\|aaa[eoq] index: 8 substr: substr.len: 0 getNextMessage query = quit\|aaa ClientConnection close hasMoreBytesToParse isExpectingMoreData releaseBuffer isExpectingMoreData startBuffer hasMoreBytesToParse isExpectingMoreData releaseBuffer but if the client open the session and close is after that without sending a message.. it will loop GrizzlyGateway started listening for incomming TCP Connections on port : 5000 isExpectingMoreData startBuffer hasMoreBytesToParse isExpectingMoreData releaseBuffer isExpectingMoreData startBuffer hasMoreBytesToParse isExpectingMoreData releaseBuffer isExpectingMoreData startBuffer hasMoreBytesToParse isExpectingMoreData releaseBuffer isExpectingMoreData startBuffer <QuoteQueryProtocolParser.java>--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@...