Does STAF work well with Windows/Linux Server operating systems?
I tried all the suggestions in attached threads. I disabled to windows NetBios
support from network properties advanced settings via WINS settings and
unselected the "Enable LMHOSTS lookup" box. I am on a dedicated network with
STATIC IP addresses (192.168.0.1 kind of). Below is the set of packets I
captured on wireshark when a ping command was issued from Windows system
(Server 2003) to RHEL (5.3, 32 bit) system.
I am seeing TCP checksum error [TCP CHECKSUM INCORRECT] as attached below.
Finally I got the PONG response but after almost 4.5 seconds. I am on 100MBPS
network.
Is there a way out from this? Thanks.
"1","0.000000","192.168.0.6","192.168.0.1","TCP","activesync > boks [SYN] Seq=0
Win=65535 Len=0 MSS=1460"
"2","0.000041","192.168.0.1","192.168.0.6","TCP","boks > activesync [SYN, ACK]
Seq=0 Ack=1 Win=5840 Len=0 MSS=1460"
"3","0.000147","192.168.0.6","192.168.0.1","TCP","activesync > boks [ACK] Seq=1
Ack=1 Win=65535 Len=0"
"4","4.498068","192.168.0.6","192.168.0.1","TCP","activesync > boks [PSH, ACK]
Seq=1 Ack=1 Win=65535 Len=4"
"5","*REF*","192.168.0.1","192.168.0.6","TCP","boks > activesync [ACK] Seq=1
Ack=5 Win=5840 Len=0"
"6","0.000158","192.168.0.6","192.168.0.1","TCP","activesync > boks [PSH, ACK]
Seq=5 Ack=1 Win=65535 Len=4"
"7","0.000229","192.168.0.1","192.168.0.6","TCP","boks > activesync [ACK] Seq=1
Ack=9 Win=5840 Len=0"
"8","0.000297","192.168.0.1","192.168.0.6","TCP","boks > activesync [PSH, ACK]
Seq=1 Ack=9 Win=5840 [TCP CHECKSUM INCORRECT] Len=4"
"9","0.000510","192.168.0.6","192.168.0.1","TCP","activesync > boks [PSH, ACK]
Seq=9 Ack=5 Win=65531 Len=4"
"10","0.040354","192.168.0.1","192.168.0.6","TCP","boks > activesync [ACK]
Seq=5 Ack=13 Win=5840 Len=0"
"11","0.040814","192.168.0.6","192.168.0.1","TCP","activesync > boks [PSH, ACK]
Seq=13 Ack=5 Win=65531 Len=4"
"12","0.040837","192.168.0.1","192.168.0.6","TCP","boks > activesync [ACK]
Seq=5 Ack=17 Win=5840 Len=0"
"13","0.040921","192.168.0.1","192.168.0.6","TCP","boks > activesync [PSH, ACK]
Seq=5 Ack=17 Win=5840 [TCP CHECKSUM INCORRECT] Len=4"
"14","0.041250","192.168.0.6","192.168.0.1","TCP","activesync > boks [PSH, ACK]
Seq=17 Ack=9 Win=65527 Len=4"
"15","0.081244","192.168.0.1","192.168.0.6","TCP","boks > activesync [ACK]
Seq=9 Ack=21 Win=5840 Len=0"
"16","0.081663","192.168.0.6","192.168.0.1","TCP","activesync > boks [PSH, ACK]
Seq=21 Ack=9 Win=65527 Len=116"
"17","0.081758","192.168.0.1","192.168.0.6","TCP","boks > activesync [ACK]
Seq=9 Ack=137 Win=5840 Len=0"
"18","0.081838","192.168.0.1","192.168.0.6","TCP","boks > activesync [PSH, ACK]
Seq=9 Ack=137 Win=5840 [TCP CHECKSUM INCORRECT] Len=4"
"19","0.081862","192.168.0.1","192.168.0.6","TCP","boks > activesync [FIN, PSH,
ACK] Seq=13 Ack=137 Win=5840 [TCP CHECKSUM INCORRECT] Len=8"
"20","0.081977","192.168.0.6","192.168.0.1","TCP","activesync > boks [ACK]
Seq=137 Ack=22 Win=65515 Len=0"
"21","0.082053","192.168.0.6","192.168.0.1","TCP","activesync > boks [FIN, ACK]
Seq=137 Ack=22 Win=65515 Len=0"
"22","0.082066","192.168.0.1","192.168.0.6","TCP","boks > activesync [ACK]
Seq=22 Ack=138 Win=5840 Len=0"
--- On Tue, 11/3/09, Sharon Lucas <luc...@us.ibm.com> wrote:
From: Sharon Lucas <luc...@us.ibm.com>
Subject: Re: [staf-users] STAF takes a long time to respond (windows and linux)
To: "Rajiv Telang" <rajiv_tel...@yahoo.com>
Cc: staf-users@lists.sourceforge.net
Date: Tuesday, November 3, 2009, 10:11 AM
If this happens as soon as you start STAF up, I would suspect network issues
and/or name server (DNS) issues. STAF attempts to resolve the host names using
standard socket APIs.
STAF does not do anything to restrict the response time. You should look into
your network settings. Also, see the suggestions in the STAF forum thread
links that Dave provided in his note.
In our environment with static IP addresses, I can do STAF pings very quickly
from one Windows or Linux machine to another in our lab. For example, using
the STAFLoop executable we provide, I can execute 10 STAF pings to another
machine with each ping taking any average time of 0.145 seconds.
C:\>STAFLoop 10 client1.ibm.com PING PING
Total loops: 10
Total time : 1.453
Avg. time : 0.145
Loops/sec : 6.88231
You can also verify STAF's performance using the local IPC interface (instead
of a network interface) by specifying "local://local" (or "local") for the
endpoint. For example, using the STAFLoop executable, I can execute 10 STAF
pings to the local machine (using the local IPC interface) with each ping
taking an average time of 0.002 seconds.
C:\>STAFLoop 10 local PING PING
Total loops: 10
Total time : 0.020
Avg. time : 0.002
Loops/sec : 500
In the default STAF.cfg file, STAF configures two network interfaces (ssl and
tcp). Are you using the STAF ssl interface (secure TCP/IP) or the STAF tcp
interface (non-secure TCP/IP)? If you're using the ssl interface (the default
if your using the default STAF.cfg file), then you could try using the tcp
interface instead to see if it is any faster (e.g. STAF tcp://hostname PING
PING). Note that if you don't specify which interface to use in your endpoint,
STAF will first try to communicate to a remote machine with the default
interface (the first interface specified if the DEFAULTINTERFACE setting is not
set in the STAF.cfg file). If that fails twice (as the default CONNECTATTEMPTS
is 2, but is configurable), then STAF will attempt to connect using the second
interface (if one is configured), and cache whichever one was used so that it
knows which one to use in the future.
--------------------------------------------------------------
Sharon Lucas
IBM Austin, luc...@us.ibm.com
(512) 286-7313 or Tieline 363-7313
Rajiv Telang <rajiv_tel...@yahoo.com>
11/03/2009 03:36 AM
To
staf-users@lists.sourceforge.net
cc
Subject
[staf-users] STAF takes a long time to respond (windows and linux)
Hi,
I am trying the STAF over a dedicated network with static IP addresses for all
the machine over network. I am seeing a very slow response time from STAF. A
simple staf ping command takes 4-5 seconds to respond back with a pong. A
simple windows/linux ping operation takes less than a second. This slow
response time from STAF hinders the performance. I have installed full STAF
package from the installer available.
I have seen similar behavior with DHCP IP addresses. And this is true for both
windows and linux versions of STAF.
Is there a setting in STAF that restricts the response time? Can I do some
changes in any of the configuration files to improve the time?
I would appreciate a solution on this problem. Thanks in advance.
- Rajiv
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
