#1285 MDS TCP: zero bytes recvd results in application exit

[Girish]

sometimes application using opensaf exits with below message:

Feb 20 15:24:59 fedvm1 RIB[28549]: MDTM:socket_recv() = 0, conn lost with dh server, exiting library err :Success
Feb 20 15:24:59 fedvm1 osafamfnd[28263]: NO 'safSu=SU1,safSg=app-simplex,safApp=appos' component restart probation timer started (timeout: 4000000000 ns)
Feb 20 15:24:59 fedvm1 osafamfnd[28263]: NO Restarting a component of 'safSu=SU1,safSg=app-simplex,safApp=appos' (comp restart count: 1)
Feb 20 15:24:59 fedvm1 osafamfnd[28263]: NO 'safComp=App,safSu=SU1,safSg=app-simplex,safApp=appos' faulted due to 'avaDown' : Recovery is 'componentRestart'

Exits at location osaf/libs/core/mds/mds_dt_trans.c::mdtm_process_poll_recv_data_tcp

recd_bytes = recv(tcp_cb->DBSRsock, tcp_cb->buffer, local_len_buf, 0);
if (recd_bytes < 0) {
return;
} else if (0 == recd_bytes) {
syslog(LOG_ERR, "MDTM:socket_recv() = %d, conn lost with dh server, exiting library err :%d len:%d", recd_bytes, errno,
local_len_buf);
close(tcp_cb->DBSRsock);
exit(0);
} else if (local_len_buf > recd_bytes) {

local_len_buf turns out be 0

[A V Mahesh (AVM)]

This is not newly introduce bug , this is an existing TCP transport bug.

[Anders Bjornerstedt]

Defect can not have milestone set to a future release.
Either change to enhancement or set the proper milestone.

[A V Mahesh (AVM)]

Need to evaluate and targetd for 4.7