Many opened JMS sessions cause connection timed out

When 30 MDB consumers are deployed with property maxSession set on 60, the server stops to accept connections and the connection timed out exception is thrown. However when 60 MDB consumers are deployed with property maxSession set on 30, the server accepts connection as expected, only "Failed to open a socket" exception is occurred, because maximum of opened sockets is reached.