Hi Jitendra:
Without knowing the exact details of the application you're using, and
the exact method you're using the restart your application, it's not
possible for me to determine whether the problem with the unexpected
name table entry you're seeing is due to a problem with your
application, a problem with TIPC, or a problem with the way you're
testing things. However, it sounds like it should be easy for you to
figure this out.
Step 1:
- Set up your system such that your application on node <1.1.5> has
published {x,655370, 655370}.
- Dump the name table of node <1.1.5> to verify that the entry is
present.
- Dump the name table of node <1.1.1> to verify the entry is present
there, too.
Step 2:
- Do whatever it is you need to do to terminate the application. (I
don't know whether this involves crashing node <1.1.5>, or manually
killing the application, or what.)
- Verify that the name is no longer visible present in the name table on
node <1.1.1>.
- If node <1.1.5> is still running, verify that the name is no longer
visible present in it's name table, too. *** If the name is still
visible, please provide details on what you've done to terminate the
application. ***
Step 3:
- Restart the application.
- Verify that the name is present in the name table on both node <1.1.1>
and node <1.1.5>.
I know from personal experience that you have to be very careful to
ensure things are cleaned up properly when an application terminates,
especially when writing code that involves child processes. It is very
easy to end up with zombie processes that still have open sockets, which
could result in the sort of unexpected name table entries you're
reporting.
Regards,
Al
> -----Original Message-----
> From: jitendra kolhe [mailto:[EMAIL PROTECTED]
> Sent: Saturday, September 22, 2007 12:54 PM
> To: Stephens, Allan; [email protected]
> Subject: Re: [tipc-discussion] TIPC Messages are Sometimes
> beingmis-directed to the wrong TIPC destport
>
> Hi Allan,
>
> we tried to check name table entry for tipc node <1.1.1> for
> name space {x,655370, 655370}, but did not get any entry for
> node 1.1.1.
>
> Apart from looking for TIPC name for <1.1.1> node, we saw
> some issues with name table entries for a application with Type "x"
>
> Before the application was reseted we had following entry for
> TIPC name {x,655370, 655370}
> Type Lower Upper Port Identity
> Publication
> ------------ ----------------- -------------
> -------------------- -----------
> x 655370 655370
> <1.1.5:520257525> 520257526
>
> After resting the application with type id "x", we had two entries.
> Type Lower Upper Port Identity
> Publication
> ------------ ----------------- -------------
> -------------------- -----------
> x 655370 655370
> <1.1.5:2219147253> 2219147254
>
> <1.1.5:520257525> 520257526
>
> it seems that 520257525, port entry still retained in name table.
> Is this the issue with the application that subscribes to
> TIPC or is it the issues with TIPC name table populating Mechanism?
>
> Thanks,
> Jitendra
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
tipc-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tipc-discussion
