i'm in need of a way to troubleshoot an issue. My company uses a 3rd party Gateway application written in JBOSS (sneers, jibes, flaming comments) that is having communications issues. The 3rd party developer has been unable to determine WHY inbound TCP connections
to their gateway application is failing.
So what I wanted to do is either 1) write an app, or 2) utilize an existing app, that can create a generic TCP Listener on a IP:Port on the server, and a client TCP SENDER that can attempt to establish hundreds or thousands of simultaneous connection attemps,
and transfer some meaningless data stream of a few hundred bytes.
The 3rd party vendor is saying it's a server issue. So what I'd like to do is use a tool to verify that this application server (Windows 2003) can indeed sustain NNNN number of short lived inbound TCP connections. This isn't for THROUGHPUT testing of data
transfer, but for the testing of the max number of simultaneous ESTABLISHED TCP Connections from clients. So it's kind of like a socket stress tool.
For just a little more background, the 3rd party developer will not tell us how they've designed their thread pool and socket communications API. We suspect it has significant architectural flaws.
So if we can use a tool to verify that the physical server and O/S can service thousands of TCP Socket communications of short length messages eith
View Complete Post