OK right.
Now I see.
However as far as I understand
the trouble is not on the server-side as you
suggest about the function

tsp_request_close_1_svc() in tsp_server.c

in your case the server (i.e. provider) is dead
(or "networkly" unreachable)
and you want the consumer to handle this.

I am currently trying a fix which seems to work.
You will have a patch to try soon.

May be you should try to debug the code inside a debugger
in order to check the return value of
TSP_request_close, nevertheless.

your STRACE_DEBUG call may be OK but you should check
if STRACE_DEBUG  mask value includes 8 (4th bit)

for example STRACE_DEBUG=15 implies

• WARNING --> 1
• INFO    --> 2
• REQUEST --> 4
• DEBUG   --> 8

You could check values in

tsp/src/core/include/tsp_simple_trace.h

Moreover since you get the message:

ERROR||/home/intocv61/VAla/TSP_0.8.3/sources/src/core/rpc/tsp_client.c##TSP_request_close##208: : RPC: Unable to receive; errno = Connection reset by peer

And that message comes from the macro:

#define TSP_STRACE_RPC_ERROR(cl, pResult) if(!pResult)  {  STRACE_ERROR(("%s", clnt_sperror(cl, "")));  }

called in

tsp_client.c:208
TSP_STRACE_RPC_ERROR(server, retcode);

I would say that retcode is NULL
but your STRACE_DEBUG is not displayed because the debug
level is not activated by the STRACE_DEBUG mask value.

Stepping in TSP source code may seems hard, but
as soon as you did somes more steps
you may find it easy ;=)

Thank you for making this first step, you should go on :=)

---

italic
Hello world,
Concerning the bug 19706, i would like to know what's new about it.
Now, with virgine , we work on TSP version 0.8.3. The problem with >request_sample() core dump is solved.(thanks for correction)
italic

---

Good to known :))

---

italic
But, with this new version, i try to test the tsp_request_close() when the provider is unreachable.The status of this request is TSP_status_OK and no TSP_STATUS_ERROR_PROVIDER_UNREACHABLE.

If you have time, is it possible to correct it ?
italic

---

I am currently being tight in time
may be you could try it yourself and I will be pleased
to review your proposed patch?

Would you have time to give it a try?

You may follow the

TSP_consumer_request_close

function call from
src/core/driver/tsp_consumer.c:750

I think we should check the return value
of the effective rpc call:

TSP_request_close(&req_close, otsp->server);

tell me if you want to try.

bold: please use the tracker (instead of the list)
        for this bug follow-up

If we run a provider and a consumer and
the consumer tries to use TSP_request_xxx while the
provider is dead (or unreachable, or terminated etc...)

we get:

a segfault on TSP_consumer_request_sample.
a wrong TSP_STATUS_OK on TSP_consumer_request_close.

all TSP_consumer_request xxx should return:
TSP_STATUS_ERROR_PROVIDER_UNREACHABLE

in this case.


see discussion on ML:
http://lists.nongnu.org/archive/html/tsp-devel/2007-04/msg00053.html
http://lists.nongnu.org/archive/html/tsp-devel/2007-04/msg00052.html