Problem communicating with socket application

[Pep]

Spooky. So what exactly connects the client and server?

As Gordon says, I imagine they must be talking via a proxy. I
would be inclined to compare the traces for IP address, MAC
address, IP sequence numbers, to prove there is some entity
playing piggy in the middle and corrupting the data stream. That
kind of change doesn't happen by accident - you have to re-write
checksums, and even change sequence numbering if you're dropping
bytes from the stream.

Steve

I agree, very spooky.

We are about to run the client and server on the same segment as each other
to see if the problem still exists.

Cheers,
Pep.

 

[Pep]

Per the Java API docs:

public String readLine() throws IOException
Read a line of text. A line is considered to be terminated by any
one of a line feed ('\n'), a carriage return ('\r'), or a carriage
return followed immediately by a linefeed.

From some of the conversation, it feels as if there might be a filter
that is converting the stream like dos2unix, etc. Is there a chance
that the socket on the server end is not a true socket, but perhaps a
telnet connections? For example, the telnet protocol requires that 0xFF
be escaped.

Having now run my client on the same network segment as the server, I have
successfully processed in excess of 5,000 records without dropping any. So
it looks like there is something on the network which is responsible for
the conversion or dropping of bytes.

Now to find out what it is

Cheers,
Pep.

 

[Pep]

So Java nothing to do with it.

Write a class that reads one record scanning it byte by byte

You might use http://mindprod.com/jgloss/readblocking.html
as a model. Perhaps it should also convert it to char for you as well
after it has scanned the bytes.

Having now run my client on the same network segment as the server, I have
successfully processed in excess of 5,000 records without dropping any. So
it looks like there is something on the network which is responsible for
the conversion or dropping of bytes.

Now to find out what it is

Cheers,
Pep.

 

[Pep]

Spooky. So what exactly connects the client and server?

As Gordon says, I imagine they must be talking via a proxy. I
would be inclined to compare the traces for IP address, MAC
address, IP sequence numbers, to prove there is some entity
playing piggy in the middle and corrupting the data stream. That
kind of change doesn't happen by accident - you have to re-write
checksums, and even change sequence numbering if you're dropping
bytes from the stream.

Steve

Having now run my client on the same network segment as the server, I have
successfully processed in excess of 5,000 records without dropping any. So
it looks like there is something on the network which is responsible for
the conversion or dropping of bytes.

Now to find out what it is

Cheers,
Pep.

 

[Steve Horsley]

Having now run my client on the same network segment as the server, I have
successfully processed in excess of 5,000 records without dropping any. So
it looks like there is something on the network which is responsible for
the conversion or dropping of bytes.

Now to find out what it is

The thot plickens.

That might prove to be an interesting investigation.

One thing I can guarantee - when you find the kit responsible,
and find whoever is responsible for that kit, they will
categorically deny that their kit could possibly have anything to
do with your problem.

Steve

 

[Pep]

The thot plickens.

That might prove to be an interesting investigation.

One thing I can guarantee - when you find the kit responsible,
and find whoever is responsible for that kit, they will
categorically deny that their kit could possibly have anything to
do with your problem.

Steve

ROFL.

I already had one sysad state "absolutely impossible" when I described the
problem to him and it's not even his problem

Pep.