[
https://issues.apache.org/jira/browse/DIRMINA-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395471#comment-13395471
]
Nagesh commented on DIRMINA-895:
--------------------------------
The time being returned is a Unix timestamp; not duration. This timestamp value
would then have to be used to arrival of heartbeat, etc.
I wish, this method returned a duration value; it would have been so much
easier.
> What does getLastReadTime() return ?
> ------------------------------------
>
> Key: DIRMINA-895
> URL: https://issues.apache.org/jira/browse/DIRMINA-895
> Project: MINA
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.4
> Environment: Linux (Ubuntu 12.04) 64-bit, Java 1.7, OpenJDK Runtime
> Environment
> Reporter: Nagesh
> Priority: Minor
> Labels: 2.0.4, connect, core, getLastReadTime(), heartbeat,
> session
> Fix For: 2.0.4
>
> Attachments: LastReadTime.png
>
>
> I started my server (implemented using MINA), the client connects to it and
> within 5 seconds a heartbeat comes in. To handle the heartbeat, I wanted to
> know if the heartbeat came in within 5 seconds since the last read time (in
> this case, connect time). However, the last read time is appearing as a value
> in the order of 10^9 or so ! So, the comparison always fails.
> That is why, I wanted to know, if the last read time was the *time duration*
> since the last read. Or, does it actually represent some time (ddmmyy...
> etc.) ?
> Also, the connect is happening once the client has sent a connect message
> (containing, for example, id and password). This message is handled in a
> handler. Isn't this connect counted as a read after the session is created
> (i.e. the server is bound as acceptor.bind(portNumber)) ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
