<HTTP_REQUEST > abort for requests in F5

Ah - OK.

>I am also using certain table lookup and table add commands with hold time for temporary storage. Can any of these cause the mentioned issue?

To make table access CMP compliant, the irule execution is dropped into the pending state during table access/update, because this operation may access other tmm instances.

So if the client aborts the connection with a reset while the irule is in HTTP_REQUEST and is updating the session table, you will get the message that you have been seeing.

Note that this is informative, and that the client has aborted the request.

So yes - the request was aborted, but not by the BigIP.

  Ohh okay. Thanks for the explanation. I understand now. But does it also mean, that usage of table commands can impact the performance of your solutions as the iRule will go into pending state when solutions are under heavy traffic load? Also, will I see the same message in case where the iRule is in pending state and the request gets timed out?

> usage of table commands can impact the performance of your solutions as the iRule will go into pending state when solutions are under heavy traffic load?

iRule use can always impact performance. You should be monitoring iRule CPU use to determine if it is negatively impacting performance.

> Also, will I see the same message in case where the iRule is in pending state and the request gets timed out?

I'm not sure if the message is the same - it may well be. That is only likely to occur if there is an incomplete TCP::collect/HTTP::collect or a timer wait.