In purepaths I see more time is consumed in socketRead0 can you please help me to understand the issue better?

[vamshikrishna_y]

Here is the session attached

socketrread0.dts

I am running a jee application on Websphere application server.

If you see the transaction flow nothing is shown in red also transaction response time contribution of database is (0.03%)very less.

Execution time of queries is also very very less.

But the socketRead0 alone took all the respone time which is 21921.28ms

What could be the issue?

Does the scoketRead0 here intdicates data being fetched to the application over the network.

Could you pleae analyze the purepaths and help me understand the issue better?

[harald_berger · Accepted solution]

Hi,

The time is consumed by ResultSet.next() calls which are not instrumented by default. That is why the transaction flow shows different numbers.

Best

Harry

[Joe_Hoffman]

Vamshi,

In addition to what Harry said, keep in mind that Socket.read is a low level java function. It's best to look up the stack and search for the context of what's calling socket.read. In this situation (as identified by Harry), it's a JDBC call to ResultSet.next.

This can happen if the result set is excessively large, and/or if the database is slow and/or the network might be slow. Perhaps take a look at the associated JDBC Execute and inspect the number of rows returned.

But either way, you now know where your transaction is spending most of it's time.

hth

joe hoffman