mina 心跳机制 ieRequest isResponse毕竟什么时候调用

mina 心跳机制 ieRequest isResponse毕竟什么时候调用,第1张

mina 心跳机制 ieRequest isResponse到底什么时候调用

上下文设置:

服务器端基于Mina开发,心跳包25秒发一次0D+0A,客户端收到后,回0D-0A

因为客户端设置了60秒一次心跳包,所以心跳包有服务器端先发起。

客户端心跳过滤器代码:(服务器端代码就不贴了,差不多的)

package com.mina.client

import java.text.SimpleDateFormat

import java.util.Date

import org.apache.mina.core.buffer.IoBuffer

import org.apache.mina.core.session.IdleStatus

import org.apache.mina.core.session.IoSession

import org.apache.mina.filter.keepalive.KeepAliveFilter

import org.apache.mina.filter.keepalive.KeepAliveMessageFactory

import org.apache.mina.filter.keepalive.KeepAliveRequestTimeoutHandler

public class MyKeepAliveFilter extends KeepAliveFilter {

public MyKeepAliveFilter() {

super(new KeepAliveMessageFactoryImpl(), IdleStatus.BOTH_IDLE, new ExceptionHandler(), 60, 70)

this.setForwardEvent(false)//此消息不会继续传递,不会被业务层看见

}

}

class ExceptionHandler implements KeepAliveRequestTimeoutHandler {

public void keepAliveRequestTimedOut(KeepAliveFilter filter, IoSession session) throws Exception {

System.out.println("心跳超时")

session.close(true)

}

}

class KeepAliveMessageFactoryImpl implements KeepAliveMessageFactory {

private static final byte int_req = '+'// 2B

private static final byte int_rep = '-'// 2D

private static final IoBuffer KAMSG_REQ = IoBuffer.wrap(new byte[]{0x0D, '+', 0x0A})

private static final IoBuffer KAMSG_REP = IoBuffer.wrap(new byte[]{0x0D, '-', 0x0A})

/**

* 此方法为发心跳包,发+

*/

@Override

public Object getRequest(IoSession arg0) {

System.out.println()

System.out.println(new SimpleDateFormat("yyyyMMdd-HH:mm:ss-SSS").format(new Date()) + " 发心跳包+:" + KAMSG_REQ.duplicate())

return KAMSG_REQ.duplicate()

}

/**

* 收到对方的心跳包后,此方法回心跳包,回-

*/

@Override

public Object getResponse(IoSession arg0, Object arg1) {

System.out.println()

System.out.println(new SimpleDateFormat("yyyyMMdd-HH:mm:ss-SSS").format(new Date()) + " 回心跳包-:" + KAMSG_REP.duplicate())

return KAMSG_REP.duplicate()

}

/**

* 是否是心跳请求包,不管是对方的还是自己的

*/

@Override

public boolean isRequest(IoSession session, Object message) {

if(!(message instanceof IoBuffer)) {

return false

}

IoBuffer realMessage = (IoBuffer)message

System.out.println()

if(realMessage.limit() != 3) {

System.out.println(new SimpleDateFormat("yyyyMMdd-HH:mm:ss-SSS").format(new Date()) + " isRequest limit不等于3,RETURN FALSE: message长度:" + realMessage.limit() + " : " + realMessage)

return false

} else {

System.out.println(new SimpleDateFormat("yyyyMMdd-HH:mm:ss-SSS").format(new Date()) + " isRequest limit等于3, message长度:" + realMessage.limit() + " : " + realMessage)

}

if (realMessage.remaining() != 3) {

return false

}

byte[] b = new byte[3]

realMessage.get(b)

boolean result = (b[1] == int_req)

System.out.println(new SimpleDateFormat("yyyyMMdd-HH:mm:ss-SSS").format(new Date()) + " isRequest 判断是否为+:" + result)

realMessage.rewind()// 把pos重新设为0

return result

}

/**

* 判断是否是心跳响应包,不管是对方的,还是自己的

*/

@Override

public boolean isResponse(IoSession session, Object message) {

if(!(message instanceof IoBuffer)) {

return false

}

IoBuffer realMessage = (IoBuffer)message

System.out.println()

if(realMessage.limit() != 3) {

System.out.println(new SimpleDateFormat("yyyyMMdd-HH:mm:ss-SSS").format(new Date()) + " isResponse limit不等于3,RETURN FALSE: message长度:" + realMessage.limit() + " : " + realMessage)

return false

} else {

System.out.println(new SimpleDateFormat("yyyyMMdd-HH:mm:ss-SSS").format(new Date()) + " isResponse limit等于3, message长度:" + realMessage.limit() + " : " + realMessage)

}

if (realMessage.remaining() != 3) {

return false

}

byte[] b = new byte[3]

realMessage.get(b)

boolean result = (b[1] == int_rep)

System.out.println(new SimpleDateFormat("yyyyMMdd-HH:mm:ss-SSS").format(new Date()) + " isResponse 判断是否为-:" + result)

realMessage.rewind()// 把pos重新设为0

return result

}

}

输出的日志:

20141113-15:49:00-778 isRequest limit等于3, message长度:3 : HeapBuffer[pos=0 lim=3 cap=2048: 0D 2B 0A]

20141113-15:49:00-779 isRequest 判断是否为+:true

20141113-15:49:00-779 回心跳包-:HeapBuffer[pos=0 lim=3 cap=3: 0D 2D 0A]

20141113-15:49:00-780 isResponse limit等于3, message长度:3 : HeapBuffer[pos=0 lim=3 cap=2048: 0D 2B 0A]

20141113-15:49:00-780 isResponse 判断是否为-:false

20141113-15:49:00-781 isRequest limit等于3, message长度:3 : HeapBuffer[pos=0 lim=3 cap=2048: 0D 2B 0A]

20141113-15:49:00-781 isRequest 判断是否为+:true

20141113-15:49:00-782 isRequest limit等于3, message长度:3 : HeapBuffer[pos=0 lim=3 cap=3: 0D 2D 0A]

20141113-15:49:00-783 isRequest 判断是否为+:false

20141113-15:49:00-783 isResponse limit等于3, message长度:3 : HeapBuffer[pos=0 lim=3 cap=3: 0D 2D 0A]

20141113-15:49:00-783 isResponse 判断是否为-:true

20141113-15:49:25-794 isRequest limit等于3, message长度:3 : HeapBuffer[pos=0 lim=3 cap=1024: 0D 2B 0A]

20141113-15:49:25-795 isRequest 判断是否为+:true

20141113-15:49:25-795 回心跳包-:HeapBuffer[pos=0 lim=3 cap=3: 0D 2D 0A]

20141113-15:49:25-796 isResponse limit等于3, message长度:3 : HeapBuffer[pos=0 lim=3 cap=1024: 0D 2B 0A]

20141113-15:49:25-796 isResponse 判断是否为-:false

20141113-15:49:25-797 isRequest limit等于3, message长度:3 : HeapBuffer[pos=0 lim=3 cap=1024: 0D 2B 0A]

20141113-15:49:25-797 isRequest 判断是否为+:true

20141113-15:49:25-798 isRequest limit等于3, message长度:3 : HeapBuffer[pos=0 lim=3 cap=3: 0D 2D 0A]

20141113-15:49:25-798 isRequest 判断是否为+:false

20141113-15:49:25-799 isResponse limit等于3, message长度:3 : HeapBuffer[pos=0 lim=3 cap=3: 0D 2D 0A]

20141113-15:49:25-799 isResponse 判断是否为-:true

有此得出

以上可得出:

对方是25秒一次心跳包,发+

如果对方先发心跳包,我方回心跳-后,如果心跳一直维持,就不会再主动发出+,除非超过设定的60秒的时候。

本地收到消息后

1、走isRequest,发现传递进来的数据为+,则return true,getResponse()回-

2、走isResponse,发现传递进来的数据为+,则return false

3、走isRequest,发现传递进来的数据为+,则return true,但没有回-

4、走isRequest,发现传递进来的数据为-,则return faslse

5、走isResponse,发现传递进来的数据位-,则 return true,但没有回+

如果本地先发心跳包

发+

isRequest 传进来+,对方收到+后,回-

isRequest 传进来-

isResopnse 传进来-

isResponse 传进来-

isResponse 传进来-

心跳的实现是在底层完成的,不会触发业务处理器中的messageReceived事件。。。你这情况可能是由于传输过来的数据编码格式不正确,导致服务端的messageReceived事件不会被触发,也就接收不到任何消息

建议可以看下通信时客户端和服务端的传输编码格式是否统一,如果统一,会不会是客户端请求时候协议格式不正确呢

祝你好运


欢迎分享,转载请注明来源:内存溢出

原文地址:https://54852.com/tougao/11293108.html

(0)
打赏 微信扫一扫微信扫一扫 支付宝扫一扫支付宝扫一扫
上一篇 2023-05-15
下一篇2023-05-15

发表评论

登录后才能评论

评论列表(0条)

    保存