4 Replies Latest reply on May 26, 2008 10:56 AM by 666705

    Under heavy load the server fails to listen on the specified port

    3004

                Hi,
                I am running Weblogic 6.1 SP4 on a solaris. There are 2 machines in the cluster.
                My weblogic server is listening on port 10001.The server started fine and is able
                to service requests. When there are large number of requests
                coming to the server I get this error on the server log file.
                "Failed to listen on port 10001, failure count: 2, failing for 1,046,226,062 seconds,
                java.net.SocketException: Too many open files"
                
                The log here shows ultimately the server has succeded to listen on port 10001
                "After having failed to listen, the server is now listening on port 10001" but
                sometimes it keeps on giving the message
                "Failed to listen on port 10001, failure count: 2, failing for 1,046,226,062 seconds,
                java.net.SocketException: Too many open files"
                and never successfully listens on the specified port.
                The relevant log entry is shown below.
                
                ####<Feb 25, 2003 9:21:03 PM EST> <Critical> <WebLogicServer> <devbea1> <BEA1Ser
                ver> <ListenThread> <system> <> <000204> <Failed to listen on port 10001, failur
                e count: 2, failing for 1,046,226,062 seconds, java.net.SocketException: Too man
                y open files>
                ####<Feb 25, 2003 9:21:05 PM EST> <Critical> <WebLogicServer> <devbea1> <BEA1Ser
                ver> <ListenThread> <system> <> <000204> <Failed to listen on port 10001, failur
                e count: 3, failing for 1,046,226,062 seconds, java.net.SocketException: Too man
                y open files>
                ####<Feb 25, 2003 9:21:08 PM EST> <Notice> <WebLogicServer> <devbea1> <BEA1Serve
                r> <ListenThread> <system> <> <000205> <After having failed to listen, the serve
                r is now listening on port 10001>
                
                Thanks
                Sudipta
                
        • 1. Re: Under heavy load the server fails to listen on the specified port
          3004
          this could be the OS running out of files handles, a files handle is
                    used for each socket as well as files. i am not too familiar with
                    solaris, but on linux you could use ulimit to increase the number in the
                    startweblogic script.
                    you could also limit the load to the server using the properties maximum
                    open sockets, socket readers, etc from the admin console.
                    
                    
                    Sudipta Sarkar wrote:
                    > Hi,
                    > I am running Weblogic 6.1 SP4 on a solaris. There are 2 machines in the cluster.
                    > My weblogic server is listening on port 10001.The server started fine and is able
                    > to service requests. When there are large number of requests
                    > coming to the server I get this error on the server log file.
                    > "Failed to listen on port 10001, failure count: 2, failing for 1,046,226,062 seconds,
                    > java.net.SocketException: Too many open files"
                    >
                    > The log here shows ultimately the server has succeded to listen on port 10001
                    > "After having failed to listen, the server is now listening on port 10001" but
                    > sometimes it keeps on giving the message
                    > "Failed to listen on port 10001, failure count: 2, failing for 1,046,226,062 seconds,
                    > java.net.SocketException: Too many open files"
                    > and never successfully listens on the specified port.
                    > The relevant log entry is shown below.
                    >
                    > ####<Feb 25, 2003 9:21:03 PM EST> <Critical> <WebLogicServer> <devbea1> <BEA1Ser
                    > ver> <ListenThread> <system> <> <000204> <Failed to listen on port 10001, failur
                    > e count: 2, failing for 1,046,226,062 seconds, java.net.SocketException: Too man
                    > y open files>
                    > ####<Feb 25, 2003 9:21:05 PM EST> <Critical> <WebLogicServer> <devbea1> <BEA1Ser
                    > ver> <ListenThread> <system> <> <000204> <Failed to listen on port 10001, failur
                    > e count: 3, failing for 1,046,226,062 seconds, java.net.SocketException: Too man
                    > y open files>
                    > ####<Feb 25, 2003 9:21:08 PM EST> <Notice> <WebLogicServer> <devbea1> <BEA1Serve
                    > r> <ListenThread> <system> <> <000205> <After having failed to listen, the serve
                    > r is now listening on port 10001>
                    >
                    > Thanks
                    > Sudipta
                    
                    
          • 2. Re: Under heavy load the server fails to listen on the specified
            3004

                      Would that be a good idea to rebounce the server as a cron job in a certain of
                      time regularly?
                      
                      Simon Evans <evans_simon@hotmail.com> wrote:
                      >this could be the OS running out of files handles, a files handle is
                      >
                      >used for each socket as well as files. i am not too familiar with
                      >solaris, but on linux you could use ulimit to increase the number in
                      >the
                      >startweblogic script.
                      >you could also limit the load to the server using the properties maximum
                      >
                      >open sockets, socket readers, etc from the admin console.
                      >
                      >
                      >Sudipta Sarkar wrote:
                      >> Hi,
                      >> I am running Weblogic 6.1 SP4 on a solaris. There are 2 machines
                      >in the cluster.
                      >> My weblogic server is listening on port 10001.The server started fine
                      >and is able
                      >> to service requests. When there are large number of requests
                      >> coming to the server I get this error on the server log file.
                      >> "Failed to listen on port 10001, failure count: 2, failing for 1,046,226,062
                      >seconds,
                      >> java.net.SocketException: Too many open files"
                      >>
                      >> The log here shows ultimately the server has succeded to listen on
                      >port 10001
                      >> "After having failed to listen, the server is now listening on port
                      >10001" but
                      >> sometimes it keeps on giving the message
                      >> "Failed to listen on port 10001, failure count: 2, failing for 1,046,226,062
                      >seconds,
                      >> java.net.SocketException: Too many open files"
                      >> and never successfully listens on the specified port.
                      >> The relevant log entry is shown below.
                      >>
                      >> ####<Feb 25, 2003 9:21:03 PM EST> <Critical> <WebLogicServer> <devbea1>
                      ><BEA1Ser
                      >> ver> <ListenThread> <system> <> <000204> <Failed to listen on port
                      >10001, failur
                      >> e count: 2, failing for 1,046,226,062 seconds, java.net.SocketException:
                      >Too man
                      >> y open files>
                      >> ####<Feb 25, 2003 9:21:05 PM EST> <Critical> <WebLogicServer> <devbea1>
                      ><BEA1Ser
                      >> ver> <ListenThread> <system> <> <000204> <Failed to listen on port
                      >10001, failur
                      >> e count: 3, failing for 1,046,226,062 seconds, java.net.SocketException:
                      >Too man
                      >> y open files>
                      >> ####<Feb 25, 2003 9:21:08 PM EST> <Notice> <WebLogicServer> <devbea1>
                      ><BEA1Serve
                      >> r> <ListenThread> <system> <> <000205> <After having failed to listen,
                      >the serve
                      >> r is now listening on port 10001>
                      >>
                      >> Thanks
                      >> Sudipta
                      >
                      
                      
            • 3. Re: Under heavy load the server fails to listen on the specified
              3004

                        In /etc/system, set 'rlim_fd_max' the following property to a high level and reboot
                        box.
                        example: set rlim_fd_max=10240 in /etc/system.
                        
                        After this check the weblogic start up log messages for the number of file descriptors
                        used and also run the solaris 'pfiles' on the weblogic pid to check the fd.
                        
                        -Mallik
                        
                        
                        
                        
                        "Frank Leopold" <frank.leopold@hotmail.com> wrote:
                        >
                        >Would that be a good idea to rebounce the server as a cron job in a certain
                        >of
                        >time regularly?
                        >
                        >Simon Evans <evans_simon@hotmail.com> wrote:
                        >>this could be the OS running out of files handles, a files handle is
                        >>
                        >>used for each socket as well as files. i am not too familiar with
                        >>solaris, but on linux you could use ulimit to increase the number in
                        >>the
                        >>startweblogic script.
                        >>you could also limit the load to the server using the properties maximum
                        >>
                        >>open sockets, socket readers, etc from the admin console.
                        >>
                        >>
                        >>Sudipta Sarkar wrote:
                        >>> Hi,
                        >>> I am running Weblogic 6.1 SP4 on a solaris. There are 2 machines
                        >>in the cluster.
                        >>> My weblogic server is listening on port 10001.The server started fine
                        >>and is able
                        >>> to service requests. When there are large number of requests
                        >>> coming to the server I get this error on the server log file.
                        >>> "Failed to listen on port 10001, failure count: 2, failing for 1,046,226,062
                        >>seconds,
                        >>> java.net.SocketException: Too many open files"
                        >>>
                        >>> The log here shows ultimately the server has succeded to listen on
                        >>port 10001
                        >>> "After having failed to listen, the server is now listening on port
                        >>10001" but
                        >>> sometimes it keeps on giving the message
                        >>> "Failed to listen on port 10001, failure count: 2, failing for 1,046,226,062
                        >>seconds,
                        >>> java.net.SocketException: Too many open files"
                        >>> and never successfully listens on the specified port.
                        >>> The relevant log entry is shown below.
                        >>>
                        >>> ####<Feb 25, 2003 9:21:03 PM EST> <Critical> <WebLogicServer> <devbea1>
                        >><BEA1Ser
                        >>> ver> <ListenThread> <system> <> <000204> <Failed to listen on port
                        >>10001, failur
                        >>> e count: 2, failing for 1,046,226,062 seconds, java.net.SocketException:
                        >>Too man
                        >>> y open files>
                        >>> ####<Feb 25, 2003 9:21:05 PM EST> <Critical> <WebLogicServer> <devbea1>
                        >><BEA1Ser
                        >>> ver> <ListenThread> <system> <> <000204> <Failed to listen on port
                        >>10001, failur
                        >>> e count: 3, failing for 1,046,226,062 seconds, java.net.SocketException:
                        >>Too man
                        >>> y open files>
                        >>> ####<Feb 25, 2003 9:21:08 PM EST> <Notice> <WebLogicServer> <devbea1>
                        >><BEA1Serve
                        >>> r> <ListenThread> <system> <> <000205> <After having failed to listen,
                        >>the serve
                        >>> r is now listening on port 10001>
                        >>>
                        >>> Thanks
                        >>> Sudipta
                        >>
                        >
                        
                        
              • 4. Re: Under heavy load the server fails to listen on the specified port
                666705
                Hi,I am using linux and getting the same exception.
                          I tried to change the limit in /etc/security/limits.conf file.But the change was not reflected and ulimit -n showed the old value only.Any other way to increase it??