• 2 replies
  • Latest Post - ‏2013-07-15T22:49:55Z by GarlandJoseph
134 Posts

Pinned topic Recv-Q on connection will increase in size and never empy.

‏2013-01-12T05:04:09Z |
Hello, I have many servers but not all are displaying this same issue I'll describe now. I have one peoplesoft application server H4A4 which connects to an oracle database server H4D1. Both servers are AIX with large amounts of resource. When the application starts and establishes its connections to the database everything appears normal. but it's not, I'm seeing the buffer size gradually increase and will never empty untll the appilcation is shutdown. on some servers the num is in the high 500,000. If the App doesn't get shutdown the entire server will crash due to no memory.

f1000e00107153b8 tcp4 9260 0 ESTABLISHED
f1000e00253c33b8 tcp4 7320 0 ESTABLISHED
f1000e000c6babb8 tcp 4060 0 CLOSE_WAIT

My understanding of how the connections work is; they establish, connect, xreasfer the data , disconnect, start over.

Same behaviour on the dadtbase server but in additional it add in the us of localhost connections.
T also can see the databasse port sentreciev-q and it was empties.

So my question is; what could cause these ports to remain open and grow data while the send from the database is empty.

All server have AIX 6100-07-04-1216 partitioned on P770s. Any help with this would be great. Thanks,Mark
Updated on 2013-03-20T06:09:56Z at 2013-03-20T06:09:56Z by SystemAdmin
  • SystemAdmin
    134 Posts

    Re: Recv-Q on connection will increase in size and never empy.


    We have the same problem

    From IBM, the issue is to upgraded to 61TL08SP2
    Because the bug is also in 61TL7SP6 (with an emergency APAR) ans this version has lot of problem ( site ibm ) with freed socket which crash the server !!!!
    Problems with Java and most requests to Oracle

    No problem with oldest version 5.3 or 61TL06

    Best regards
  • GarlandJoseph
    9 Posts

    Re: Recv-Q on connection will increase in size and never empy.


    You shows tcp connections so it won't close until until the application specifically closes it.  When you see a send or receive queue growing it means there is a problem on one side of the connections.  it helps to track the state of the connection on both sides.  So what port and what application, what are the ip addresses for each end.  tcpdump also helps for issues like this to determine if the handshake is proper.  in this case it also looks like it's the same system using it's lan address back to itself