BaseChannel.close
25 views
Skip to first unread message
Alejandro Revilla
Jul 30, 2010, 8:23:52 PM7/30/10
to jPOS Users
As a follow-up to http://groups.google.com/group/jpos-users/browse_thread/thread/e04fe631ab49b3a2
Marcel, you may want to try r2955, Dave did some changes en r2954
(added shutdownOutput()) and I changed the SO_LINGER to 5 secs in
r2555, I believe the combination of the two fixes will fix the
connection reset problem, while keeping a cap on the amount of time
that a socket will linger around.
Marcel, you may want to try r2955, Dave did some changes en r2954
(added shutdownOutput()) and I changed the SO_LINGER to 5 secs in
r2555, I believe the combination of the two fixes will fix the
connection reset problem, while keeping a cap on the amount of time
that a socket will linger around.
David Bergert
Jul 30, 2010, 10:53:59 PM7/30/10
to jpos-...@googlegroups.com
I did quite a bit of followup testing on this. Me and Wireshark on a Friday Evening ;)
Pre - r2953 - The TCP disconnect was always a RST on a channel.close()
With both r2956 (adding the shutdownOutput() and the setSoLinger (true, 5)) - The TCP disconnect was a FIN or RST
Thanks Alejandro.
David Bergert, CISSP, CISA, CPISM/A
www.paymentsystemsblog.com
> --
> You received this message because you are subscribed to the "jPOS Users" group.
> Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
> To post to this group, send email to jpos-...@googlegroups.com
> To unsubscribe, send email to jpos-users+...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/jpos-users
Reply all
Reply to author
Forward
0 new messages