To keep the forums high quality for all users, please take the time to format your posts correctly.
First of all, use Code Tags when you post any code or data samples so others can easily read your code. You can easily do this by highlighting your code and then clicking on the # in the editing menu. (You can also type code tags
```text
and
```
by hand.)
Second, avoid adding color or different fonts and font size to your posts. Selective use of color to highlight a single word or phrase can be useful at times, but using color, in general, makes the forums harder to read, especially bright colors like red.
Third, be careful when you cut-and-paste, edit any odd characters and make sure all links are working property.
Are your AIX and WebSphere up-to-date? Do the application logs show something interessting when the problem shows up? Can you and users still open new connections after those 300 are reached via telnet/ssh?
Will keep in mind regarding the the format while posting a thread.
--------------------------------------
'AIX and WebSphere up-to-date' by any chance is this concerned with the JDK version?
Found the following errors in the application logs while the port is in hanged status:-
Exception in Constructor
sendData:my Data Length is:194
sendData:sending length of:194
length of the string 194
Exception in sendData64
java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
At this point of time when we are trying to connect to the same port it is throwing an error ' Not able to connect to the port'.
Nope, we are not able to create any further connection after the port gets hanged. The output of netstat -an | grep <port no.> shows all the connections in ESTABLISHED status.
Port limit of 300 - Are you sure this isn't a setting in Weblogic, which is perhaps "per applicaiton"?
How to release ports - if they are established, then neither end has closed them. Sounds like the application (client or server end) needs to be modified to close ports when they are no longer needed.
We have confirmed the same from the development team that there is no such setting for the max. no of connections allowed to the ports. Moreover from our analysis point of view the no. 300 may not be hard coded because everytime the no. of established connection varies before the ports get into hanged status, but everytime it is > 300.
Few quick questions for better understanding of the issue:-
1.Is there any other workaround available to analyze from OS point of view before throwing the ball to the application developers court?
2.Please let me know what may be the possible reason or the scenarios where ports remain in ESTABLISHED status.
Is there any system timeout variable/parameter from AIX point of view where we can mention the time after which the established connection will get automatically closed.
Does established connection for a long time mean an IDLE conection?
Is there any possibility that due to some never ending processes these connections are getting created with time?
Being very much new to the platform, asked you all the above questions for better understanding of the issue. Thanks in advance.
From OS view I know no limit how many connections may be opened up to a port. The will be one I think, but we have no problem with applications where more than 300 people connect to a port and there was nothing to be done in the OS to support this.
I did a simple
no -L| grep 300
to see if there is any network option that might have a value of 300 as default and could be taken into relationship with your problem, but I did not find that value.
So I either still think it is an application set parameter or you might have different values on your OS regarding number of connections. Have no better idea, sorry.
There is definitely no limit of connections to any particular port in AIX ... I have loads of boxes with 2500+ connections to the port of the oracle listener.
I assume you are using connection pools to access somehow a database. If this is the case, please have a look here Configuring and Using WebLogic JDBC
When your applications attempt to get a connection from a connection pool in which there are no available connections, the connection pool throws an exception stating that a connection is not available in the connection pool. To avoid this error, make sure your connection pool can expand to the size required to accommodate your peak load of connection requests.
To set the maximum number of connections for a connection pool in the Administration Console, expand the navigation tree in the left pane to show the Services�>JDBC�>Connection Pools nodes and select a connection pool. Then, in the right pane, select the Configuration�>Connections tab and specify a value for Maximum Capacity.