Re: nsapi problem with WL 4.5.2 no sp with iPlanet 4.0

Question

          We are noticing the same problem with WL5.1, esp.
          I can replicate this by reducing the number of executeThreads
          within WebLogic to a very low number (say 5). It seems to
          me that there is a problem with the WebLogic proxy (NSAPI); it seems to be gettting into a state where it is not able to do handle connection startups/shutdowns in a graceful manner leaving IDLE connections.
          Any pointers would be appreciated.
          Thanks.
          -dev
          "Jaime Chambron" <[email protected]> wrote:
          >here is more details on the probs we are seeing:
          >
          >Besides a number of other issues that I am experiencing with iPlanet 4.0
          >there are two specific issues that I need your help in resolving. These
          >issues are as follows:
          >
          >Idle connection on the web server. Summary: While running load tests on the
          >site I see up to 500 or more idle connection that will not time out or
          >recycle. Has anyone come across this issue? How was it resolved? Any
          >thoughts on what could be causing the idle connections? Below is an example
          >of the idle connection.
          >
          >*.* *.* 0 0 33232 0 IDLE
          > *.* *.* 0 0 33232 0 IDLE
          > *.* *.* 0 0 33232 0 IDLE
          > *.* *.* 0 0 33232 0 IDLE
          > *.* *.* 0 0 33232 0 IDLE
          > *.* *.* 0 0 33232 0 IDLE
          >
          >
          >
          >
          >2. Logging. How do I turn off verbose logging or minimize it?
          >Summary: Our error log files are continuing to fill up causing sluggish
          >performance and web server crashes. Any suggestions? Here are some
          >of the errors being logged.. (Suspect the NSAPI plugin)
          >
          >[25/Jul/2000:12:54:57] failure ( 1324): Error accepting connection -5971,
          >oserr=24 (PR_PROC_DESC_TABLE_FULL_ERROR)
          >[25/Jul/2000:12:54:57] failure ( 1324): Error accepting connection -5971,
          >oserr=24 (PR_PROC_DESC_TABLE_FULL_ERROR)
          >[25/Jul/2000:12:54:57] failure ( 1324): Error accepting connection -5971,
          >oserr=24 (PR_PROC_DESC_TABLE_FULL_ERROR)
          >[25/Jul/2000:12:54:57] failure ( 1324): for host 208.29.209.9 trying to GET
          >/, wl-proxy reports: Cannot connect to WebLogic: timed out after 10 seconds.
          >
          >[25/Jul/2000:13:18:18] warning ( 1324): DaemonProcessor::Run terminating
          >with 404 sessions still in progress
          >[25/Jul/2000:13:18:19] info ( 1437): successful server startup
          >[25/Jul/2000:13:18:19] info ( 1437): Netscape-Enterprise/4.0 SP4
          >BB1-02/07/100 17:53
          >[25/Jul/2000:13:34:49] failure ( 1437): for host 208.29.209.9 trying to GET
          >/, wl-proxy reports: Cannot connect to WebLogic: timed out after 10 seconds.
          >
          >[25/Jul/2000:13:35:43] failure ( 1437): for host 208.29.209.9 trying to GET
          >/, wl-proxy reports: Cannot connect to WebLogic: timed out after 10 seconds.
          >
          >
          >
          >
          >Jaime Chambron wrote in message <[email protected]>...
          >>hi -
          >>
          >>we are having a ton of probs with our error log on our web servers filling
          >>up and degrading performance b/c we are seeing the following error with our
          >>jsps (the web server sees up to a point in runnign,then all of a sudden
          >>starts to get errors after some load testing)
          >>
          >>the prob causes errors in the proxy.cpp file to occur (at different line
          >>numbers, i believe 400 something and 830) and says things like "file not
          >>found" (though it is there) or timeout...
          >>
          >>this is causing our webservers to eventually grind to a hault, and it looks
          >>like is has something to do with the nsapi plug in. do we need a patch? do
          >>we have something configured wrong?
          >>
          >>
          >>please help!!
          >>thanks
          >>j
          >>
          >>
          >
          >
          

Answer 1

          Hi,
          I'm experiencing the same problem with wls 5.1 sp 9 and iPlanet 4.1 sp 5.
          Did you figure this problem out?
          Regards,
          Torleif Galteland
          "Michael Caughey" <[email protected]> wrote:
          >
          >Have you had any luck in figuring out what is the root cause of your
          >problem?
          >We are having a simalar problem using weblogic 5.1 SP6 & iPlanet 4.1
          >SP2.
          >Thanks,
          >
          >"Dev Worah" <[email protected]> wrote:
          >>
          >>We are noticing the same problem with WL5.1, esp.
          >>
          >>I can replicate this by reducing the number of executeThreads
          >>within WebLogic to a very low number (say 5). It seems to
          >>me that there is a problem with the WebLogic proxy (NSAPI); it seems
          >>to be gettting into a state where it is not able to do handle connection
          >>startups/shutdowns in a graceful manner leaving IDLE connections.
          >>
          >>Any pointers would be appreciated.
          >>
          >>Thanks.
          >>-dev
          >>"Jaime Chambron" <[email protected]> wrote:
          >>>here is more details on the probs we are seeing:
          >>>
          >>>Besides a number of other issues that I am experiencing with iPlanet
          >>4.0
          >>>there are two specific issues that I need your help in resolving.
          >These
          >>>issues are as follows:
          >>>
          >>>Idle connection on the web server. Summary: While running load tests
          >>on the
          >>>site I see up to 500 or more idle connection that will not time out
          >>or
          >>>recycle. Has anyone come across this issue? How was it resolved?
          >
          >>Any
          >>>thoughts on what could be causing the idle connections? Below is an
          >>example
          >>>of the idle connection.
          >>>
          >>>*.* *.* 0 0 33232 0 IDLE
          >>> *.* *.* 0 0 33232 0
          >>IDLE
          >>> *.* *.* 0 0 33232 0
          >>IDLE
          >>> *.* *.* 0 0 33232 0
          >>IDLE
          >>> *.* *.* 0 0 33232 0
          >>IDLE
          >>> *.* *.* 0 0 33232 0
          >>IDLE
          >>>
          >>>
          >>>
          >>>
          >>>2. Logging. How do I turn off verbose logging or minimize it?
          >>>Summary: Our error log files are continuing to fill up causing sluggish
          >>>performance and web server crashes. Any suggestions? Here are
          >>some
          >>>of the errors being logged.. (Suspect the NSAPI plugin)
          >>>
          >>>[25/Jul/2000:12:54:57] failure ( 1324): Error accepting connection
          >-5971,
          >>>oserr=24 (PR_PROC_DESC_TABLE_FULL_ERROR)
          >>>[25/Jul/2000:12:54:57] failure ( 1324): Error accepting connection
          >-5971,
          >>>oserr=24 (PR_PROC_DESC_TABLE_FULL_ERROR)
          >>>[25/Jul/2000:12:54:57] failure ( 1324): Error accepting connection
          >-5971,
          >>>oserr=24 (PR_PROC_DESC_TABLE_FULL_ERROR)
          >>>[25/Jul/2000:12:54:57] failure ( 1324): for host 208.29.209.9 trying
          >>to GET
          >>>/, wl-proxy reports: Cannot connect to WebLogic: timed out after 10
          >>seconds.
          >>>
          >>>[25/Jul/2000:13:18:18] warning ( 1324): DaemonProcessor::Run terminating
          >>>with 404 sessions still in progress
          >>>[25/Jul/2000:13:18:19] info ( 1437): successful server startup
          >>>[25/Jul/2000:13:18:19] info ( 1437): Netscape-Enterprise/4.0 SP4
          >>>BB1-02/07/100 17:53
          >>>[25/Jul/2000:13:34:49] failure ( 1437): for host 208.29.209.9 trying
          >>to GET
          >>>/, wl-proxy reports: Cannot connect to WebLogic: timed out after 10
          >>seconds.
          >>>
          >>>[25/Jul/2000:13:35:43] failure ( 1437): for host 208.29.209.9 trying
          >>to GET
          >>>/, wl-proxy reports: Cannot connect to WebLogic: timed out after 10
          >>seconds.
          >>>
          >>>
          >>>
          >>>
          >>>Jaime Chambron wrote in message <[email protected]>...
          >>>>hi -
          >>>>
          >>>>we are having a ton of probs with our error log on our web servers
          >>filling
          >>>>up and degrading performance b/c we are seeing the following error
          >>with our
          >>>>jsps (the web server sees up to a point in runnign,then all of a sudden
          >>>>starts to get errors after some load testing)
          >>>>
          >>>>the prob causes errors in the proxy.cpp file to occur (at different
          >>line
          >>>>numbers, i believe 400 something and 830) and says things like "file
          >>not
          >>>>found" (though it is there) or timeout...
          >>>>
          >>>>this is causing our webservers to eventually grind to a hault, and
          >>it looks
          >>>>like is has something to do with the nsapi plug in. do we need a
          >patch?
          >>do
          >>>>we have something configured wrong?
          >>>>
          >>>>
          >>>>please help!!
          >>>>thanks
          >>>>j
          >>>>
          >>>>
          >>>
          >>>
          >>
          >