R
Rob Fitzpatrick
Guest
Given both the (735) and the (290), my first guess would be a network issue of some kind between client and server. I'd run Wireshark or tshark on both the client machine and the database server, each filtering on traffic to/from the other, and wait for the errors to happen again. You can capture to a ring buffer so you don't have to worry about continually-growing capture files if it takes a while. Then stop the captures once the error happens and compare them. You'd be looking for evidence of packet loss, e.g. many duplicate ACKs or fast TCP retransmissions. Also, a packet that appears in one trace but not the other clearly indicates packet loss. It's a bit tedious and time-consuming, and may require someone with networking expertise, but that's the approach I'd take. Another option is to run a client server-side. It isn't an option to resolve the problem of course, but it could help to demonstrate to the non-believers that the issue isn't OpenEdge or the application. If a server-side TCP client runs fine but a remote TCP client fails with errors, that fairly clearly points to either a networking problem on the client or between the client and the server. Also, it looks like you're reading a .pl over the network. Are you running the client with -pls?
Continue reading...
Continue reading...