NSAPI failure on NT

We were using WebLogic Server version 4.5.1 on our NES proxy server
and everything was
pretty smooth. Now that we have installed version 5.1 of WebLogic we
get the following message:
FAILURE of WEBLOGIC NSAPI plugin
Cannot Connect to Weblogic: timed out after 10 seconds.
Failure at line 465 of file proxy.cpp
The only thing I changed was moving the new proxy36.dll onto the NES
server.
Any ideas are appreciated.
joe

Set the plugin parameter DebugConfigInfo=ON and then send the query param
"__WebLogicBridgeConfig". Make sure that your server/cluster members
are listed.
Example:
<Object name="weblogic" ppath="*/weblogic/*">
Service fn="wl-proxy"
WebLogicCluster="lakeshore1:4736,lakeshore2:4736,lakeshore:4736"\
PathTrim="/weblogic" DebugConfigInfo="ON"
</Object>
Send http://myserver:8000/weblogic/SimpleSession.jsp?__WebLogicBridgeConfig
Also make sure that your can reach your WebLogic servers directly.
--Vinod.
Joe wrote:
We were using WebLogic Server version 4.5.1 on our NES proxy server
and everything was
pretty smooth. Now that we have installed version 5.1 of WebLogic we
get the following message:
FAILURE of WEBLOGIC NSAPI plugin
Cannot Connect to Weblogic: timed out after 10 seconds.
Failure at line 465 of file proxy.cpp
The only thing I changed was moving the new proxy36.dll onto the NES
server.
Any ideas are appreciated.
joe

Similar Messages

NSAPI failure

Using WebLogic Server version 4.5.1 we had little problems.
          We had the server running on one of our NT's and had it setup to go
          through a proxy server(Netscape) and everything was
          pretty smooth.
          Now that we have installed version 5.1 of WebLogic we
          get the following message:
          FAILURE of WEBLOGIC NSAPI plugin
          Cannot Connect to Weblogic: timed out after 10 seconds.
          Failure at line 351 of file proxy.cpp
          Build date/time: Sep. 20, 1999 19:05:10
          Nothing else has changed. Any ideas are appreciated.
          joe


Check out if NSAPI plugin is configured properly.
          Set a plugin paramter: DebugConfigInfo=ON
          and then send a query paramter: __WebLogicBridgeConfig
          with your requests.
          example:
          http://myserver.mydomain.com:8000/foo.jsp?__WebLogicBridgeConfig
          It will display the cluster/host-port infomation.
          --Vinod.
          Joe wrote:
          > Using WebLogic Server version 4.5.1 we had little problems.
          > We had the server running on one of our NT's and had it setup to go
          > through a proxy server(Netscape) and everything was
          > pretty smooth.
          > Now that we have installed version 5.1 of WebLogic we
          > get the following message:
          >
          > FAILURE of WEBLOGIC NSAPI plugin
          >
          > Cannot Connect to Weblogic: timed out after 10 seconds.
          > Failure at line 351 of file proxy.cpp
          >
          > Build date/time: Sep. 20, 1999 19:05:10
          >
          > Nothing else has changed. Any ideas are appreciated.
          > joe

NSAPI failure with NT

We were using WebLogic Server version 4.5.1 on our NES proxy server
and everything was
pretty smooth. Now that we have installed version 5.1 of WebLogic we
get the following message:
FAILURE of WEBLOGIC NSAPI plugin
Cannot Connect to Weblogic: timed out after 10 seconds.
Failure at line 465 of file proxy.cpp
The only thing I changed was moving the new proxy36.dll onto the NES
server.
Any ideas are appreciated.
joe

Set the plugin parameter DebugConfigInfo=ON and then send the query param
"__WebLogicBridgeConfig". Make sure that your server/cluster members
are listed.
Example:
<Object name="weblogic" ppath="*/weblogic/*">
Service fn="wl-proxy"
WebLogicCluster="lakeshore1:4736,lakeshore2:4736,lakeshore:4736"\
PathTrim="/weblogic" DebugConfigInfo="ON"
</Object>
Send http://myserver:8000/weblogic/SimpleSession.jsp?__WebLogicBridgeConfig
Also make sure that your can reach your WebLogic servers directly.
--Vinod.
Joe wrote:
We were using WebLogic Server version 4.5.1 on our NES proxy server
and everything was
pretty smooth. Now that we have installed version 5.1 of WebLogic we
get the following message:
FAILURE of WEBLOGIC NSAPI plugin
Cannot Connect to Weblogic: timed out after 10 seconds.
Failure at line 465 of file proxy.cpp
The only thing I changed was moving the new proxy36.dll onto the NES
server.
Any ideas are appreciated.
joe

ConnectRetrySecs vs ConnectTimeoutSecs vs HungRecoverSecs

Below is a description from one of our developers as to what he
          believes these values mean. Can anyone here clarify what each of these
          values will do and when is a good time to adjust them from the
          defaults? We seem to get bitten by failing weblogic servers and would
          like to be able to failover if one is "hung" a lot sooner than we are.
          We are using NES (Iplanet) 4.1 and WebLogic 4.5.1 SP13..
          It would seem that ConnectTimeoutSecs and ConnectRetrySecs actually
          are internal Weblogic timing things that are in general unrelated to
          our application, but which provide us with the ability to gauge how
          long we should wait before retrying if we can't get any handshake at
          all from the cluster. That is, a request comes in from outside, it
          gets touched by the Weblogic proxy, which then attempts to route the
          request back to the app server cluster. The proxy must then attempt
          to open a socket with the cluster so that someone will respond to the
          request. This first connection to the app server layer requires a
          first "handshake" with the NES proxy, and these paramters gauge how
          long the proxy should wait before it gets that first handshake before
          retrying. It should try to get any app server to respond within
          ConnectRetrySecs, retrying every ConnectRetrySecs until it hits
          ConnectTimeoutSecs, at which time it will stop asking the cluster for
          a connection and return an error status 503 to the end-user (i.e. that
          ugly NSAPI failure page).
          In short, I believe that only one request to get work done will ever
          be sent back to the app server layer even upon retry. Which is good,
          'cause otherwise it'd go into some crazy spin-lock condition.
          This is different from what we thought it should do in the past. We
          incorrectly believed that these parameters should be set for the time
          it takes to get the response for the ENTIRE jsp request (i.e. we made
          a connection to the app server, requested that it should do work, and
          this was how long it was going to wait before retrying the work
          request). It turns out that the HungServerRecoverSecs parameter is
          more for that. Thats the length of time that the proxy will wait
          after a work request before declaring that a particular app server has
          fallen out of the cluster, and therefore should no longer be used to
          do any work. Since this time IS dependant on how long it takes us to
          perform any work request (i.e. whats the longest time it takes any JSP
          to render under our highest load), this number should be set VERY
          high. 300 is probably a little high, but workable for us, so thats
          probably ok. However, 300 seconds is 5 minutes. If a server hasn't
          responded to a work request in that long, we probably have bigger
          problems.
          IF the above are correct, then setting ConnectRetrySecs to 2 MAY give
          us some marginally better load-balancing in the cluster, but I doubt
          that we'll see any appreciable difference under our current load
          anyways.
          We also see "failure" Netscape error messages when the cluster is
          under heavy load which result in "Connect Reset by Peer" and "Resource
          Temorarily Available" each of these referring to an error in
          proxy.cpp...
          Thanks..
          Ruth


          Partly yes, partly no.
          You DO NOT want load-balancing by setting these parameters to be small. No, no,
          no. This will make your httpSessions flip around from one server to the other
          when things get slow - making things even slower.
          The analysis of ConnectRetrySecs, ConnectTimeoutSecs is correct - except - if
          the connect times out against one server in the cluster, WLS will try to connect
          to another server in the cluster. You should probably not touch these. If these
          connections keep failing, wlproxy keeps retrying.
          Given that a connection to WL has been made, the remainder of the transaction
          is governed by HungRecoverSeconds. If a request takes longer than this it fails.
          It is NOT retried unless the request is IDEMPOTENT (i.e. you don't want multiple
          charges on a credit card because the server was slow). 300 seconds is fine unless
          you are using SAP.
          If you set the wlproxy property DEBUG=ON, you will get reams of debug information
          in /tmp/wlproxy.log.
          Your best bet is to fix whatever is making WL slow - there is no such thing as
          graceful failover.
          Mike
          [email protected] (Ruth) wrote:
          >Below is a description from one of our developers as to what he
          >believes these values mean. Can anyone here clarify what each of these
          >values will do and when is a good time to adjust them from the
          >defaults? We seem to get bitten by failing weblogic servers and would
          >like to be able to failover if one is "hung" a lot sooner than we are.
          >We are using NES (Iplanet) 4.1 and WebLogic 4.5.1 SP13..
          >
          >---------------------------------------
          >It would seem that ConnectTimeoutSecs and ConnectRetrySecs actually
          >are internal Weblogic timing things that are in general unrelated to
          >our application, but which provide us with the ability to gauge how
          >long we should wait before retrying if we can't get any handshake at
          >all from the cluster. That is, a request comes in from outside, it
          >gets touched by the Weblogic proxy, which then attempts to route the
          >request back to the app server cluster. The proxy must then attempt
          >to open a socket with the cluster so that someone will respond to the
          >request. This first connection to the app server layer requires a
          >first "handshake" with the NES proxy, and these paramters gauge how
          >long the proxy should wait before it gets that first handshake before
          >retrying. It should try to get any app server to respond within
          >ConnectRetrySecs, retrying every ConnectRetrySecs until it hits
          >ConnectTimeoutSecs, at which time it will stop asking the cluster for
          >a connection and return an error status 503 to the end-user (i.e. that
          >ugly NSAPI failure page).
          >
          >In short, I believe that only one request to get work done will ever
          >be sent back to the app server layer even upon retry. Which is good,
          >'cause otherwise it'd go into some crazy spin-lock condition.
          >
          >This is different from what we thought it should do in the past. We
          >incorrectly believed that these parameters should be set for the time
          >it takes to get the response for the ENTIRE jsp request (i.e. we made
          >a connection to the app server, requested that it should do work, and
          >this was how long it was going to wait before retrying the work
          >request). It turns out that the HungServerRecoverSecs parameter is
          >more for that. Thats the length of time that the proxy will wait
          >after a work request before declaring that a particular app server has
          >fallen out of the cluster, and therefore should no longer be used to
          >do any work. Since this time IS dependant on how long it takes us to
          >perform any work request (i.e. whats the longest time it takes any JSP
          >to render under our highest load), this number should be set VERY
          >high. 300 is probably a little high, but workable for us, so thats
          >probably ok. However, 300 seconds is 5 minutes. If a server hasn't
          >responded to a work request in that long, we probably have bigger
          >problems.
          >
          >IF the above are correct, then setting ConnectRetrySecs to 2 MAY give
          >us some marginally better load-balancing in the cluster, but I doubt
          >that we'll see any appreciable difference under our current load
          >anyways.
          >--------------------------
          >We also see "failure" Netscape error messages when the cluster is
          >under heavy load which result in "Connect Reset by Peer" and "Resource
          >Temorarily Available" each of these referring to an error in
          >proxy.cpp...
          >
          >Thanks..
          >
          > Ruth

Internal Server failure, NSAPI plugin

Problem: I Get the following message after a HTTP POST
Failure of WebLogic NSAPI plugin: Internal Server failure, NSAPI
plugin. Cannot continue. Failure at line 369 of file proxy.cpp
Environment: Weblogic 5.1.0. Service Pack 4 Netscape-Enterprise/3.6
SP3
The above problem appears if there is a post from a browser (only
netscape)or from an application program. If I post using IE5 browswer
then the post is successful.
POSTING FROM A JAVA APPLICATION:
I get the NSAPI plugin problem if I post the following string from
my java application. I can reach the weblogic server directly and
I can post the following string successfully.
"POST /servlets/eol/EolPost HTTP/1.0" + "\n\n" + " Host: testpulpweb0.ecomtest.enron.com:5454
" + "\r\n" + "Content-type: text/html" +"\r\n" + "Content-Length:
" content.length() "\n" +content; *************************************************
POSTING FROM BROWSERS
I turned on both the Debug and DebugConfigInfo parameters. Following
is the debug info I get in wlproxy.log after a successful post
from IE5 ************************************************ Fri Mar
16 10:25:32 2001 Sending header to WLS [referer]=[http://localhost/eolfo
rm.htm] Fri Mar 16 10:25:32 2001 Sending header to WLS [accept-language]=[en-us]
Fri Mar 16 10:25:32 2001 Sending header to WLS [content-type]=[text/plain]
Fri Mar 16 10:25:32 2001 Sending header to WLS [accept-encoding]=[gzip,
deflate] Fri Mar 16 10:25:32 2001 Sending header to WLS [user-agent]=[Mozilla/4.0
(compat ible; MSIE 5.01; Windows NT 5.0)] Fri Mar 16 10:25:32 2001
Sending header to WLS [host]=[testpulpweb0.ecomtest.enr on.com:5454]
Fri Mar 16 10:25:32 2001 Sending header to WLS [content-length]=[7]
Fri Mar 16 10:25:32 2001 Sending header to WLS [cookie]=[SITESERVER=ID=ebee2594a
7d91523d4f83d5301864ed6] Fri Mar 16 10:25:32 2001 Sending header
to WLS [X-WebLogic-Force-Cookie]=[true] Fri Mar 16 10:25:32 2001
Sending header to WLS [Proxy-Client-IP]=[172.16.128.68] Fri Mar
16 10:25:32 2001 Sending header to WLS [Proxy-Path-Translated]=[/opt/dyn
amictrade21/cp_eol/servlets/eol/EolPost/ __WebLogicBridgeConfig]
Fri Mar 16 10:25:32 2001 Sending header to WLS [Proxy-Path-Translated-Base]=[/op
t/dynamictrade21/cp_eol] Fri Mar 16 10:25:32 2001 WLS info before
parseHeaders : 127.0.0.1:8001 Fri Mar 16 10:25:32 2001 Header received
from WLS : [HTTP/1.1 200 OK] = [] Fri Mar 16 10:25:32 2001 Header
received from WLS : [Server] = [WebLogic 5.1.0 Service Pack 4 06/29/2000
18:18:23 #74560] Fri Mar 16 10:25:32 2001 Header received from
WLS : [Content-Type] = [text/html ] Fri Mar 16 10:25:32 2001 Header
received from WLS : [Connection] = [Close] Fri Mar 16 10:25:32
2001 Headers from WLS [Server]=[WebLogic 5.1.0 Service Pack 4 06/29/2000
18:18:23 #74560] Fri Mar 16 10:25:32 2001 Headers from WLS [Content-Type]=[text/html]
Fri Mar 16 10:25:32 2001 Headers from WLS [Connection]=[Close]
Fri Mar 16 10:25:32 2001 request [servlets/eol/EolPost/__WebLogicBridgeConfig]
processed .................. ***********************************************
If I post using netscape then I get the "Internal Server failure,
NSAPI plugin. Cannot continue." message
Following is the message in wlproxy.log.
Fri Mar 16 10:30:12 2001 ==================== New Request [servlets/eol/EolPost/__WebLogicBridgeConfig]
===================== **************************************************
Maybe someone of you has an idea?
Thanks in advance,
Satish

First of all, i would suggest you to try the latest WLS service pack and NSAPI plugin come with the service
pack.
Let us know if the problem re-appears.
Kumar
Satish Jonnavithula wrote:
Problem: I Get the following message after a HTTP POST
Failure of WebLogic NSAPI plugin: Internal Server failure, NSAPI
plugin. Cannot continue. Failure at line 369 of file proxy.cpp
Environment: Weblogic 5.1.0. Service Pack 4 Netscape-Enterprise/3.6
SP3
The above problem appears if there is a post from a browser (only
netscape)or from an application program. If I post using IE5 browswer
then the post is successful.
POSTING FROM A JAVA APPLICATION:
I get the NSAPI plugin problem if I post the following string from
my java application. I can reach the weblogic server directly and
I can post the following string successfully.
"POST /servlets/eol/EolPost HTTP/1.0" + "\n\n" + " Host: testpulpweb0.ecomtest.enron.com:5454
" + "\r\n" + "Content-type: text/html" +"\r\n" + "Content-Length:
" content.length() "\n" +content; *************************************************
POSTING FROM BROWSERS
I turned on both the Debug and DebugConfigInfo parameters. Following
is the debug info I get in wlproxy.log after a successful post
from IE5 ************************************************ Fri Mar
16 10:25:32 2001 Sending header to WLS [referer]=[http://localhost/eolfo
rm.htm] Fri Mar 16 10:25:32 2001 Sending header to WLS [accept-language]=[en-us]
Fri Mar 16 10:25:32 2001 Sending header to WLS [content-type]=[text/plain]
Fri Mar 16 10:25:32 2001 Sending header to WLS [accept-encoding]=[gzip,
deflate] Fri Mar 16 10:25:32 2001 Sending header to WLS [user-agent]=[Mozilla/4.0
(compat ible; MSIE 5.01; Windows NT 5.0)] Fri Mar 16 10:25:32 2001
Sending header to WLS [host]=[testpulpweb0.ecomtest.enr on.com:5454]
Fri Mar 16 10:25:32 2001 Sending header to WLS [content-length]=[7]
Fri Mar 16 10:25:32 2001 Sending header to WLS [cookie]=[SITESERVER=ID=ebee2594a
7d91523d4f83d5301864ed6] Fri Mar 16 10:25:32 2001 Sending header
to WLS [X-WebLogic-Force-Cookie]=[true] Fri Mar 16 10:25:32 2001
Sending header to WLS [Proxy-Client-IP]=[172.16.128.68] Fri Mar
16 10:25:32 2001 Sending header to WLS [Proxy-Path-Translated]=[/opt/dyn
amictrade21/cp_eol/servlets/eol/EolPost/ __WebLogicBridgeConfig]
Fri Mar 16 10:25:32 2001 Sending header to WLS [Proxy-Path-Translated-Base]=[/op
t/dynamictrade21/cp_eol] Fri Mar 16 10:25:32 2001 WLS info before
parseHeaders : 127.0.0.1:8001 Fri Mar 16 10:25:32 2001 Header received
from WLS : [HTTP/1.1 200 OK] = [] Fri Mar 16 10:25:32 2001 Header
received from WLS : [Server] = [WebLogic 5.1.0 Service Pack 4 06/29/2000
18:18:23 #74560] Fri Mar 16 10:25:32 2001 Header received from
WLS : [Content-Type] = [text/html ] Fri Mar 16 10:25:32 2001 Header
received from WLS : [Connection] = [Close] Fri Mar 16 10:25:32
2001 Headers from WLS [Server]=[WebLogic 5.1.0 Service Pack 4 06/29/2000
18:18:23 #74560] Fri Mar 16 10:25:32 2001 Headers from WLS [Content-Type]=[text/html]
Fri Mar 16 10:25:32 2001 Headers from WLS [Connection]=[Close]
Fri Mar 16 10:25:32 2001 request [servlets/eol/EolPost/__WebLogicBridgeConfig]
processed .................. ***********************************************
If I post using netscape then I get the "Internal Server failure,
NSAPI plugin. Cannot continue." message
Following is the message in wlproxy.log.
Fri Mar 16 10:30:12 2001 ==================== New Request [servlets/eol/EolPost/__WebLogicBridgeConfig]
===================== **************************************************
Maybe someone of you has an idea?
Thanks in advance,
Satish

Message from the NSAPI plugin: "Internal Server Failure"

Can someone explain the possible causes of the following message displayed when rendering a page:
Message from the NSAPI plugin:
Internal Server failure, NSAPI plugin. Cannot continue.
Build date/time: Nov 10 2005 15:25:36
Change Number: 673701
Thanks

you are probably using a custom NSAPI plugin from a 3rd party company that is emitting this message. to get more information on this issue, you can look into the NSAPI plugins loaded by <https-hostname>/config/magnus.conf and find out which nsapi plugin is causing this error. nsapi plugins bundled within web server like j2eeplugin or fastcgi does not emit this error
also, you can increase the server log verbosity (by setting <log-level>finest</log-level> in config/server.xml and restarting the server
hth

Application is throwing NSAPI and other errors after the migration

We started seeing NSAPI and other errors after the migration of new codes and recently make some changes
1) During the migration, all the 4 WLS cluster instances were bounced simultaneously. What is the best practice and recommendation from BEA Oracle? Do we need to bounce it one by one for any specific reason?
2) we recently introduced the 4th weblogic cluster instance on Solaris 10 zone. All other WLS instances are running on Solaris 8.
Is it okay to have two different OS versions( Solaris 8 and Solaris 10) and different hardware to host WLS cluster instances? Does BEA Oracle support this kind of configuration?
3) We are consistently seeing below errors in the iplanet web server error logs even though site is working fine
[11/Sep/2009:08:53:50] failure ( 4453): for host XX.XX.XX.XX trying to POST /servlet/FSO, wl-proxy reports: exception occurred for backend host 'YY.YY.YY.YY/23120/0': 'CONNECTION_REFUSED [os error=0, line 1732 of URL.cpp]: Error connecting to host YY.YY.YY.YY.YY:23120'
Do we need to upgrade our WLS proxy plugin? . Current version of WLS proxy plug-in is libproxy_61.so. Our Weblogic version is WLS 92 MP2
I'll really appreciate if some can anwsers those questions

OK booted in to Virtualbox, seems too be working fine this way, maybe it is the ATi drivers
any Help would be appreciated

NSAPI Redirector in SOLARIS 8

Hi:
I'm trying to fordward request from iPlanet 6.0 (Solaris 8) to Tomcat 5.5 using NSAPI Redirector.
When I load the plugin mod_jk-1.2.15-solaris8-sparc-apache-1.3.33.so I obtain this message:
[09/Jan/2006:17:22:09] failure (18615): Configuration initialization failed: Error running init function load-modules: dlopen of /uni2/produccion/iws60sp2/plugins/nsapi/mod_jk-1.2.15-solaris8-sparc-apache-1.3.33.so failed (ld.so.1: ns-httpd: fatal: relocation error: file /uni2/produccion/iws60sp2/plugins/nsapi/mod_jk-1.2.15-solaris8-sparc-apache-1.3.33.so: symbol ap_null_cleanup: referenced symbol not found)
I checked that the requeried libraries are in the Path.
Any idea?

hi
i was reading through your posts but still don't understand why you would need or loose your sleep in getting to work with tomcat when sun java system web server can do the job in house.
also, if you r interested in having different entry point, why not have multiple instances of web server or multiple virtual servers to do the job .
pl. note that sun java system web server derives the better performance and is able to put some good numbers in Spec Web because of its wonderful integration.
just my 2c

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

          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
          >>
          >>
          >
          >


          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
          >>>>
          >>>>
          >>>
          >>>
          >>
          >

Internal Server failure, NSAI Plugin. Cannot Continue

Friends,
I am posting this message hoping for a solution.
We have web application running on Iplanet 6.1 -> weblogic 9.2. The initial request hits the iplanet webserver and then the request is redirected to weblogic 9.2 server with the wlproxy plugin configured on iplanet webserver.
Our system architecture is simple, we don't have any cluster configurations on it.
User gets following error message sporadically, Interesting fact of this issue is that, part of the webpage gets this message (Message from NSAPI plugin) and while on refresh the browser error message doesnt show up:
Message from NSAPI plugin:
Internal Server failure, NSAI Plugin. Cannot Continue. Change Number: 755164.
Please help me with solution/debuging strategies if any for the same.
Thanks in Advance.
-DhilliP

looks like, some issue with 3rd party nsapi plugin. u might want to post this question to web logic plugin forum as well as looks like they possibly have some issues with their plugin.
If u r needs are simple, then can u not use the reverse proxy plugin provided by sun and forward the requests to weblogic.
http://docs.sun.com/app/docs/doc/819-6510/6n8h5jos2?a=view
here is the link on how to get this plugin
http://www.sun.com/download/products.xml?id=3f567f91

Single-point failure of proxy server??

Three questions regarding using the proxy server for WLS clustering:
          1. What happen if the proxy server fails? The entire cluster won't be
          accessible?
          If so, is there a implication of having "meta-configuration" for
          proxy server failover?
          2. Does the term "in-memory persistence" clustering (over JDBC) does
          imply
          the session data is "shared" in memory between the primary &
          secondary
          servers, or they are compleleted replicated in each server??
          3. How bad is it in terms of performance using the JDBC session
          persistence
          and the in-memory replication? Any one has experimented it??
          Any thoughts and comments are helpful and appreciated??
          Frank Wang


Frank,
          If using File/JDBC persistence, it doesn't matter which server gets the request
          because all servers have access to every session's data.
          When you assign a hostname "to the cluster" and map that hostname to the IP
          address of each server in the cluster, this sets up something called DNS
          round-robining. What this does is round-robin which IP address is returned when
          the cluster hostname is resolved. Unfortunately, DNS is not very good at
          detecting failed machines so it may continue to hand out IP addresses of failed
          machines.
          A better way to do this is with a hardware router that is made for this purpose
          (e.g., LocalDirector). The router can detect a failed machine and redirect the
          request to another machine in the cluster. Unlike the in-memory replication
          case, it doesn't matter which server gets each request so no proxy is required.
          Hope this helps,
          Robert
          Frank Wagn wrote:
          > Hi, Robert,
          >
          > Thank you for the answers !!
          >
          > It is still not very clear to me when using the File/JDBC session
          > persistence.
          > Since there is no such a "coordinating" proxy server who knows how to
          > load balancing among the servers in the cluster (based on the specified
          > algorithm in the proxy server properties file), how does the load balancing
          > (and failover) work, when the requests are directed to a "mask" of cluster IP
          >
          > (virtual proxy) which in terms broadcast to all the servers??
          >
          > Frank
          >
          > Robert Patrick wrote:
          >
          > > Hi Frank,
          > >
          > > Frank Wang wrote:
          > >
          > > > Three questions regarding using the proxy server for WLS clustering:
          > > >
          > > > 1. What happen if the proxy server fails? The entire cluster won't be
          > > > accessible?
          > > > If so, is there a implication of having "meta-configuration" for
          > > > proxy server failover?
          > >
          > > If you have a single proxy server, this is correct in that it is a single
          > > point of failure. A common configuration is to use multiple proxy
          > > servers (with something like LocalDirector sitting in front to do routing
          > > and load balancing to the proxy servers) that proxy requests to a cluster
          > > of WLS servers.
          > >
          > > > 2. Does the term "in-memory persistence" clustering (over JDBC) does
          > > > imply
          > > > the session data is "shared" in memory between the primary &
          > > > secondary
          > > > servers, or they are compleleted replicated in each server??
          > >
          > > HttpSession state can be shared across the servers in a cluster in one of
          > > three ways.
          > >
          > > 1.) Using File-based persistence (i.e., serialization) - This requires a
          > > shared file system across all of the servers in the cluster. In this
          > > configuration, all servers are equal and can access the session state.
          > > As you might imagine, this approach is rather expensive since file I/O is
          > > involved.
          > >
          > > 2.) Using JDBC-based persistence - This requires that all servers in the
          > > cluster be configured with the same JDBC connection pool. As with method
          > > 1, all servers are equal and can access the session state. As you might
          > > imagine, this approach is rather expensive since database I/O is
          > > involved.
          > >
          > > 3.) In-memory replication (not really persistence) - This scheme uses a
          > > primary-secondary replication scheme so that each session object is kept
          > > on only two machines in the cluster (which two machines vary depending on
          > > the particular session instance). In this scheme, we need a proxy server
          > > sitting in front of the cluster that can route the requests to the server
          > > with the primary copy of the session for each request (or to the
          > > secondary if the primary has failed). The location information is
          > > encoded in the session id and the proxy knows how to decode this
          > > information and route the requests accordingly (because the proxy is
          > > using code supplied by BEA -- the NSAPI or ISAPI plugins or the
          > > HttpClusterServlet).
          > >
          > > > 3. How bad is it in terms of performance using the JDBC session
          > > > persistence
          > > > and the in-memory replication? Any one has experimented it??
          > >
          > > JDBC session persistence performance is highly dependent on the
          > > underlying DBMS. In my experience in doing benchmarks with WLS,
          > > in-memory replication (of a reasonably small amount of session data) does
          > > not add any measurable overhead. Of course, the key words here are
          > > "reasonably small amount of session data". The more data you stuff into
          > > the HttpSession, the more data that needs to be serialized between
          > > servers, more performance will be impacted.
          > >
          > > Just my two cents,
          > > Robert

Crash occurred in NSAPI SAF admin40_host_ip_check

Hello Sun Forum,
I just recently started problems with trying to startup the 'startconsole' facility of my 'iPlanet-WebServer-Enterprise/6.0SP1 B11/09/2001 15:18'. I can 'start-admin' ok and get the message:
http://ux2.pcb, port 7583 ready to accept requests
[23/Mar/2005:14:48:20] info (73928): A new configuration was successfully installed
It seems to be ok and waiting for a connection. When I 'startconsole', I get the login pop-up message box ok, but when I enter the password I get the following messages (I included the start-admin messages too, beginning to failure):
[23/Mar/2005:14:48:17] info (141826): successful server startup
[23/Mar/2005:14:48:17] info (141826): iPlanet-WebServer-Enterprise/6.0SP1 B11/09/2001 15:18
[23/Mar/2005:14:48:18] info (141826): Access Host filter is: *.pcb
[23/Mar/2005:14:48:18] info (141826): Access Address filter is: *
[23/Mar/2005:14:48:20] info (73928): Installing a new configuration
[23/Mar/2005:14:48:20] info (73928): [LS ls1] http://ux2.pcb, port 7583 ready to accept requests
[23/Mar/2005:14:48:20] info (73928): A new configuration was successfully installed
[23/Mar/2005:14:48:20] warning (73928): Address directive ignored
[23/Mar/2005:14:49:01] catastrophe (73928): Server crash detected (signal SIGSEGV)
[23/Mar/2005:14:49:01] info (73928): Crash occurred in NSAPI SAF admin40_host_ip_check
[23/Mar/2005:14:49:02] failure (141826): Child process admin thread is shutting down
[23/Mar/2005:14:49:07] info (73930): Installing a new configuration
[23/Mar/2005:14:49:07] info (73930): [LS ls1] http://ux2.pcb, port 7583 ready to accept requests
[23/Mar/2005:14:49:07] info (73930): A new configuration was successfully installed
[23/Mar/2005:14:49:07] warning (73930): Address directive ignored
[23/Mar/2005:16:01:28] info (144414): successful server startup
This results in a looping of the pop-up logon message box indicating :
Cannot logon because of an incorrect User ID, Incorrect password or Directory problem.
java.io.EOFException: Connection lost
Originally we thought we simply forgot the password. We confirmed we had the right password by doing ldapsearch and additionally taking the effort to put the 'dse.ldif' file back with the same encrypted password (SSHA).
Are there any patches to address this problem? Our VAR thought that we might be under attack but we ONLY see this message as a result of trying 'startconsole' and logon.
Thanks for reading this!

There is this warning:
[23/Mar/2005:14:48:20] warning (73928): Address directive ignored
Did you try fixing that first? Did it help? Are your hostname and/or IP address settings in your admin server config correct? Are you using DNS? Do they match your DNS settings?
I'm glad I'm migrating off this product to IBM Directory Server.Did you attempt to contact an official Sun DS support person? The ones I know are very knowledgeable and helpful. AFAIK, this forum is not a venue for official support. In fact, I end up answering a fair number of questions, and I'm definitely not affiliated with Sun (although I did work on Netscape/iPlanet DS up until 5.1).

Crash occurred in NSAPI SAF send-cgi

Hi,
We are getting Crash every couple of days. But could not find why this should happen. Here is the error log and the pstack info. If anyone has idea, please let me know.
We have recently upgraded to sun servers6.1sp6 and solaris 10.
thanks,
log;
[20/Mar/2007:12:01:56] catastrophe (11443): CORE3260: Server crash detected (signal SIGSEGV)
[20/Mar/2007:12:01:56] info (11443): CORE3261: Crash occurred in NSAPI SAF send-cgi
[20/Mar/2007:12:01:56] info (11443): CORE3262: Crash occurred in function INTnetbuf_next from module /usr/iplanet/servers6.1s
p6/bin/https/lib/libns-httpd40.so
[20/Mar/2007:12:02:08] failure (11442): CORE3107: Child process closed admin channel
[20/Mar/2007:12:02:08] info (11160): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.2_05] from [Sun Microsystems In
c.]
pstack:
core 'core.icorefep1.webservd.3205.1010.1171723612.2319' of 2319: webservd -r /usr/iplanet/servers6.1sp6 -d /usr/iplanet/servers6.1sp6/h
pstack: warning: librtld_db failed to initialize; symbols from shared libraries will not be available
----------------- lwp# 1 --------------------------------
fe0c0e70 ???????? (0, 0, ffbff6e8, 0, 0, 3e8)
----------------- lwp# 4 --------------------------------
fe0c0e70 ???????? (fd9fadb8, 1, fd9fad38, 0, 0, 1388)
----------------- lwp# 5 --------------------------------
fe0c0f84 ???????? (d, fcffaedd, feb, 0, 2c00, 0)
----------------- lwp# 6 --------------------------------
fe0c0144 ???????? (27c90, 4a970, fcefbcc8, 1, 0, 0)
----------------- lwp# 7 --------------------------------
fe0c0528 ???????? (fcdfbeb8, 0, 0, fd7e0800, 0, 1)
----------------- lwp# 8 --------------------------------
fe0c0144 ???????? (28668, 66ebf0, 0, 0, 0, 0)
----------------- lwp# 9 --------------------------------
fe0c0e70 ???????? (0, 0, fcbfbea8, 0, 0, 0)
----------------- lwp# 11 --------------------------------
fe0c0144 ???????? (286b8, 66ee98, 0, 0, 0, 0)
----------------- lwp# 12 --------------------------------
fe0c0144 ???????? (7c1390, 7af2e8, fc9fbc90, 1, 0, 0)
----------------- lwp# 13 --------------------------------
fe0c1378 ???????? (88490, 88478, fa67fd30, 3b9ac800, 1d8dbc20, 16)
----------------- lwp# 14 --------------------------------
fe0c1378 ???????? (8c150, 8c138, f1430, 0, 0, 0)
----------------- lwp# 15 --------------------------------
fe0c1378 ???????? (8c2b8, 8c2a0, f1638, 0, 0, f9e7f8a4)
----------------- lwp# 16 --------------------------------
fe0c1378 ???????? (87c20, 87c08, ff000000, ff000000, 0, 0)
----------------- lwp# 18 --------------------------------
fe0c1378 ???????? (88a30, 88a18, f1a48, 0, 4b8110, f7a7fd50)
----------------- lwp# 19 --------------------------------
fe0c1378 ???????? (88ac0, 88aa8, f1c50, 0, 4b8110, 0)
fd194078 ???????? (88a60, 0, 8cd50, 4000, 4194, f1c50)
fd2aac7c ???????? (fd5358a9, fd5c1238, f1c50, 12c1d0, 31a08c, fd267ed8)
fd267f00 ???????? (f1c50, 13, 40, 0, 40, 1)
fd2643e0 ???????? (f1c50, e3780000, 0, 0, fd2642ac, 1)
fe0c00a0 ???????? (0, 0, 0, 0, 0, 0)
----------------- lwp# 20 --------------------------------
fe0c1378 ???????? (88ac0, 88aa8, edb50, 0, 4b8110, 0)
fd194078 ???????? (88a60, 0, 8d020, 4000, 4194, edb50)
fd2aac7c ???????? (fd5358a9, fd5c1238, edb50, 12cde8, 31a08c, fd267ed8)
fd267f00 ???????? (edb50, 14, 40, 0, 40, 1)
fd2643e0 ???????? (edb50, e3500000, 0, 0, fd2642ac, 1)
fe0c00a0 ???????? (0, 0, 0, 0, 0, 0)
----------------- lwp# 22 --------------------------------
fe0c0e70 ???????? (e2d7f750, 0, e2d7f7b8, 0, 0, 0)
fe061f24 ???????? (e2d7f750, fe0eba68, fe0eba68, 0, e2d7f7b8, 0)
fe06229c ???????? (0, 0, 0, 0, e2d7f840, e2d7f840)
fd10651c ???????? (0, ea60, 1, f7c160d0, c, 0)
fd10633c ???????? (f2880, 0, ea60, 1, 4, 0)
fd293258 ???????? (f2914, e2d7f9a8, 0, ea60, e8dfbf78, 0)
f7c0b96c ???????? (e2d7fa2c, b8, 0, 3c, 0, 0)
f7c05804 ???????? (e2d7faac, b7, 0, f7c16284, 8, e2d7f9c0)
f7c05804 ???????? (e2d7fb24, f38212b8, 0, f7c160d0, 4, e2d7fa50)
f7c05a8c ???????? (e2d7fb9c, 0, 0, f7c16420, 4, e2d7fac8)
f7c0010c ???????? (e2d7fc28, e2d7fe90, a, f3821ca0, 4, e2d7fb40)
fd15bcf8 ???????? (e2d7fe88, e2d7fcf0, e2d7fda8, f2880, f2880, e2d7fd00)
fd24a3e4 ???????? (fd582000, ab7120, e2d7fd9c, e2d7fd98, e2d7fda8, f2880)
fd25d5a8 ???????? (e2d7fe88, e2d7fe84, e2d7fe7c, e2d7fe74, e2d7fe6c, f2880)
fd26e8f8 ???????? (f2880, f2880, 30298, ab7120, 31a08c, fd267ed8)
fd267f00 ???????? (f2880, 16, 40, 0, 40, 1)
fd2643e0 ???????? (f2880, e2d80000, 0, 0, fd2642ac, 1)
fe0c00a0 ???????? (0, 0, 0, 0, 0, 0)
----------------- lwp# 23 --------------------------------
fe0c0e70 ???????? (e1e7f750, 0, e1e7f7b8, 0, 0, 0)
fe061f24 ???????? (e1e7f750, fe0eba68, fe0eba68, 0, e1e7f7b8, 0)
fe06229c ???????? (0, 0, 0, 0, e1e7f840, e1e7f840)
fd10651c ???????? (0, ea60, 1, f7c160d0, c, 0)
fd10633c ???????? (f2c90, 0, ea60, 1, 4, 0)
fd293258 ???????? (f2d24, e1e7f9a8, 0, ea60, e8e053b0, 0)
f7c0b96c ???????? (e1e7fa2c, b8, 0, 3c, 0, 0)
f7c05804 ???????? (e1e7faac, b7, 0, f7c16284, 8, e1e7f9c0)
f7c05804 ???????? (e1e7fb24, f38212b8, 0, f7c160d0, 4, e1e7fa50)
f7c05a8c ???????? (e1e7fb9c, 0, 0, f7c163d0, 4, e1e7fac8)
f7c0010c ???????? (e1e7fc28, e1e7fe90, a, f3821ca0, 4, e1e7fb40)
fd15bcf8 ???????? (e1e7fe88, e1e7fcf0, e1e7fda8, f2c90, f2c90, e1e7fd00)
fd24a3e4 ???????? (fd582000, 8e3120, e1e7fd9c, e1e7fd98, e1e7fda8, f2c90)
fd25d5a8 ???????? (e1e7fe88, e1e7fe84, e1e7fe7c, e1e7fe74, e1e7fe6c, f2c90)
fd26e8f8 ???????? (f2c90, f2c90, 30608, 8e3120, 31a08c, fd267ed8)
fd267f00 ???????? (f2c90, 17, 40, 0, 40, 1)
fd2643e0 ???????? (f2c90, e1e80000, 0, 0, fd2642ac, 1)
fe0c00a0 ???????? (0, 0, 0, 0, 0, 0)
----------------- lwp# 76 --------------------------------
fe0c1294 ???????? (6, 0, fe0a4ba8, ffffffff, fe0e8284, 6)
fe040038 ???????? (0, 1, fe0b579c, a8350, fe0eb298, 0)
fd499d98 ???????? (1, fd53ad22, e1d7f668, fd56f8a2, fd56f83a, 14)
fd37d35c ???????? (e1d7f678, fd5d8b3c, fd53aaec, fd546bb3, fd53ab90, fd546b70)
fd2f6fa4 ???????? (8f, 5000, 0, ff000000, 0, 48a284)
fd2c0188 ???????? (8f, fd5c364c, 20361e8, e1d7f590, e1d7f568, 1)
fd83e174 ???????? (203627c, e1d7f918, 8f, ffffffff, f7c162e4, 0)
f7c0b96c ???????? (e1d7f994, b8, 0, f7c162a0, 0, e1d7f898)
f7c05804 ???????? (e1d7fa2c, b8, 0, f7c16298, 4, e1d7f930)
f7c05804 ???????? (e1d7faac, f38b3ba0, 0, f7c16298, 4, e1d7f9c8)
f7c05a8c ???????? (e1d7fb24, f38212b8, 0, f7c16420, 8, e1d7fa48)
f7c05a8c ???????? (e1d7fb9c, 0, 0, f7c163d0, 4, e1d7fac8)
f7c0010c ???????? (e1d7fc28, e1d7fe90, a, f3821ca0, 4, e1d7fb40)
fd15bcf8 ???????? (e1d7fe88, e1d7fcf0, e1d7fda8, 20361e8, 20361e8, e1d7fd00)
fd24a3e4 ???????? (fd582000, ab6910, e1d7fd9c, e1d7fd98, e1d7fda8, 20361e8)
fd25d5a8 ???????? (e1d7fe88, e1d7fe84, e1d7fe7c, e1d7fe74, e1d7fe6c, 20361e8)
fd26e8f8 ???????? (20361e8, 20361e8, 309c8, ab6910, 31a08c, fd267ed8)
fd267f00 ???????? (20361e8, 4c, 7f, 0, 7f, 1)
fd2643e0 ???????? (20361e8, e1d80000, 0, 0, fd2642ac, 1)
fe0c00a0 ???????? (0, 0, 0, 0, 0, 0)
----------------- lwp# 25 --------------------------------
fe0c0e70 ???????? (e1cfbc88, 1, e1cfbc08, 0, 0, 1388)
fe05cf48 ???????? (e1cfbc88, 1, 1388, 10624c00, 0, 0)
fedd8534 ???????? (e1cfbcf4, 1, e1cfbd24, e1cfbc88, 20, ffffffff)
fedd9dd8 ???????? (30748, e1cfbe58, ffffffff, 12, 0, ffffffff)
ff22a3ac ???????? (f42e8, e1cfbe58, ffffffff, ff000000, 0, 0)
ff220fc0 ???????? (108de50, 7, 8, 0, 1000, ffffe800)
ff106d68 ???????? (108de50, 78f110, 0, 0, 0, 1)
fedddf2c ???????? (78f110, ff106d44, 400, fedf6a98, 0, fedf87dc)
fe0c00a0 ???????? (0, 0, 0, 0, 0, 0)
----------------- lwp# 26 --------------------------------
fe0c0144 ???????? (262a0, 498f8, e1bfbd28, 1, 0, 0)
fe0ba1d4 ???????? (262a0, 498f8, e1bfbd28, 0, 0, 0)
fe0ba64c ???????? (262a0, 498f8, e1bfbd28, 0, 0, 0)
fe0ba7e4 ???????? (262a0, 498f8, e1bfbeb8, ff000000, 0, 0)
fe0ba8d8 ???????? (262a0, 498f8, e1bfbeb8, 0, 0, c350)
fe0ba918 ???????? (262a0, 498f8, e1bfbeb8, 45d7155d, 0, 3618adb8)
fedd79fc ???????? (26298, 2, 78faa0, 0, 3618adb8, 0)
ff23b82c ???????? (2e58, 0, 0, ff2ef26c, ff2ef274, ff2ef260)
fedddf2c ???????? (78faa0, ff23b498, 400, fedf6a98, 0, fedf87dc)
fe0c00a0 ???????? (0, 0, 0, 0, 0, 0)

Unfortunately, we can't tell much from that pstack output because it doesn't include symbols:pstack: warning: librtld_db failed to initialize; symbols from shared libraries will not be availableI don't know pstack couldn't initialize librtld_db. How big is the core file? Is it possible that it was truncated due to a lack of disk space or ulimit? Did you run pstack on the same system that generated the core file?
While I don't remember seeing a bug like this before, have you tried applying the latest service pack? For Web Server 6.1, that's 6.1SP7. Service packs contain important bug fixes.

Server Failure - StandardSession nullpointer...

Server: SUN ONE Web server 6.1
OS: Solaris 9 with recommended patches
HW: SUN v210 (2 processors)
We have received a server failure on our webserver.
Our application log died, the error log died, the server did not accept requests for ten minutes (the access log recorded nothing).
It did NOT restart itself - it just hung. When I tried to
do a thread dump the jvm exited with a 'catastrophe' message and the it restarted.
Here is the most severe error messages in the error log:
[16/Sep/2004:16:05:45] warning (10135): CORE3283: stderr: [Thu Sep 16 16:05:44 MEST 2004]ERROR internal.ErrorServlet     ANAH005 End: Dumps the request.
[16/Sep/2004:16:05:45] failure (10135): StandardManager[/] WEB3425: processsExpire: Exception during session expiration
java.lang.NullPointerException
        at org.apache.catalina.session.StandardSession.keys(StandardSession.java:1502)
        at org.apache.catalina.session.StandardSession.expire(StandardSession.java:629)
        at org.apache.catalina.session.StandardManager.processExpires(StandardManager.java:782)
        at org.apache.catalina.session.StandardManager.run(StandardManager.java:860)
        at java.lang.Thread.run(Thread.java:534)
[16/Sep/2004:16:05:45] failure (10135): for host 10.120.12.38 trying to POST /Menu, service-j2ee reports: WEB2798: [] ServletCon
text.log(): JspFactoryImpl: Exception initializing page context
java.lang.IllegalStateException: WEB3010: Cannot create a session after the response has been committed
        at org.apache.catalina.connector.HttpRequestBase.doGetSession(HttpRequestBase.java:1372)
        at org.apache.catalina.connector.HttpRequestBase.getSession(HttpRequestBase.java:1332)
        at org.apache.catalina.connector.HttpRequestFacade.getSession(HttpRequestFacade.java:214)
        at org.apache.catalina.connector.HttpRequestFacade.getSession(HttpRequestFacade.java:224)
        at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:268)
        at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:268)
        at org.apache.jasper.runtime.PageContextImpl._initialize(PageContextImpl.java:138)
        at org.apache.jasper.runtime.PageContextImpl.initialize(PageContextImpl.java:114)
        at org.apache.jasper.runtime.JspFactoryImpl.internalGetPageContext(JspFactoryImpl.java:181)
        at org.apache.jasper.runtime.JspFactoryImpl.getPageContext(JspFactoryImpl.java:154)
        at _jsps._jsp._include._top_jsp._jspService(_top_jsp.java:47)
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
        at com.iplanet.ias.web.jsp.JspServlet$JspServletWrapper.service(JspServlet.java:667)
        at com.iplanet.ias.web.jsp.JspServlet.serviceJspFile(JspServlet.java:447)
        at com.iplanet.ias.web.jsp.JspServlet.service(JspServlet.java:363)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
        at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:770)
        at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:626)
        at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:537)
        at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:834)
        at _jsps._jsp._utd._menu_utd_jsp._jspService(_menu_utd_jsp.java:150)
        at internal.AuthorizedJspPage.service(AuthorizedJspPage.java:136)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
        at com.iplanet.ias.web.jsp.JspServlet$JspServletWrapper.service(JspServlet.java:667)
        at com.iplanet.ias.web.jsp.JspServlet.serviceJspFile(JspServlet.java:447)
        at com.iplanet.ias.web.jsp.JspServlet.service(JspServlet.java:363)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
        at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:770)
        at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:471)
        at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:382)
        at internal.ODRServlet.forwardToPage(ODRServlet.java:608)
        at internal.ODRServlet.forwardToPage(ODRServlet.java:568)
        at internal.MenuServlet.doGet(MenuServlet.java:370)
        at internal.ODRServlet.doPost(ODRServlet.java:206)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:807)
        at internal.ODRServlet.service(ODRServlet.java:221)
        at internal.AuthorizedServlet.service(AuthorizedServlet.java:269)
        at internal.MenuServlet.service(MenuServlet.java:159)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
        at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:771)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:322)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:209)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
        at com.iplanet.ias.web.connector.
[16/Sep/2004:16:05:46] failure (10135): for host 10.120.12.38 trying to POST /Menu, service-j2ee reports: ApplicationDispatcher[
/] WEB2649: Servlet.service() for servlet jsp threw exception
java.lang.IllegalStateException: WEB3438: getAttribute: Session already invalidated
        at org.apache.catalina.session.StandardSession.getAttribute(StandardSession.java:964)
        at org.apache.catalina.session.StandardSessionFacade.getAttribute(StandardSessionFacade.java:171)
        at org.apache.catalina.session.StandardSessionFacade.getAttribute(StandardSessionFacade.java:171)
        at internal.AuthorizedJspPage.service(AuthorizedJspPage.java:138)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
        at com.iplanet.ias.web.jsp.JspServlet$JspServletWrapper.service(JspServlet.java:667)
        at com.iplanet.ias.web.jsp.JspServlet.serviceJspFile(JspServlet.java:447)
        at com.iplanet.ias.web.jsp.JspServlet.service(JspServlet.java:363)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
        at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:770)
        at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:471)
        at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:382)
        at internal.ODRServlet.forwardToPage(ODRServlet.java:608)
        at internal.ODRServlet.forwardToPage(ODRServlet.java:568)
        at internal.MenuServlet.doGet(MenuServlet.java:370)
        at internal.ODRServlet.doPost(ODRServlet.java:206)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:807)
        at internal.ODRServlet.service(ODRServlet.java:221)
        at internal.AuthorizedServlet.service(AuthorizedServlet.java:269)
        at internal.MenuServlet.service(MenuServlet.java:159)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
        at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:771)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:322)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:209)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
        at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:161)
        at com.iplanet.ias.web.WebContainer.service(WebContainer.java:586)
[16/Sep/2004:16:19:46] warning (10135): CORE3283: stderr: Full thread dump Java HotSpot(TM) Server VM (1.4.2_04-b05 mixed mode):
[16/Sep/2004:16:19:46] catastrophe (10135): CORE3260: Server crash detected (signal SIGSEGV)
[16/Sep/2004:16:19:47] failure (10001): CORE3107: Child process closed admin channel
We need clarification to what has happened.
/ Peter

WebLogic is not a "recoverable server"; it is a "transaction server". (See
          the OpenGroup documentation for exact definitions.) As such, the enlisted
          resources (assuming that they hadn't reached the preare stage in a 2-phase
          commit) would be expected to roll back when the server goes down.
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com
          +1.617.623.5782
          WebLogic Consulting Available
          "Les Sears" <[email protected]> wrote in message
          news:3a3a7d36$[email protected]..
          >
          > Does anyone know what happens with uncommitted transactions in the case of
          a server failure with regards to both CMT and BMT? Upon restart of the
          Weblogic Server, will the transactions be rolled-back?
          >
          > Thanks.

BEA-NSapi-plugins_Dec06(libproxy.so)

Hi,
we have an issue with the BEA-NSapi-plugins_Dec06
App Server: Weblogic7.0.1 SP7
Webserver: iPlanet Webserver6.0 SP5
The AppServer is not communicating with the Webserver after having the plugin BEA-NSapi-plugins_Dec06(libproxy.so)in Webserver. The Appserver displays a 'page cannot be displayed' message.
Can someone please help.
Thanks
Eturi Kumar

Hi All,
The error has seen in the webserver logs
[29/Mar/2007:22:28:18] info ( 8389): successful server startup
[29/Mar/2007:22:28:18] info ( 8389): iPlanet-WebServer-Enterprise/6.0SP10 B10/12/2005 00:16
[29/Mar/2007:22:28:19] info ( 8394): Installing a new configuration
[29/Mar/2007:22:28:19] info ( 8394): [LS ls1] http://OffShoreSMIServer, port 1432 ready to accept requests
[29/Mar/2007:22:28:19] info ( 8394): A new configuration was successfully installed
[29/Mar/2007:22:28:20] info ( 8394): Using the Solaris VM v1.2.2 from Sun Microsystems Inc.
[29/Mar/2007:22:28:20] info ( 8394): Java VM classpath: /export/home/gmacsmi/iPlanetWS/Servers/plugins/servlets/examples/legacy/beans.10/SDKBeans10.jar:/export/home/gmacsmi/iPlanetWS/Servers/bin/https/tools.jar:/export/home/gmacsmi/iPlanetWS/Servers/bin/https/jre/lib/rt.jar:/export/home/gmacsmi/iPlanetWS/Servers/bin/https/jar/NSServletLayer.jar:/export/home/gmacsmi/iPlanetWS/Servers/bin/https/jar/NSJavaUtil.jar:/export/home/gmacsmi/iPlanetWS/Servers/bin/https/jar/AdminNativeUtil.jar:/export/home/gmacsmi/iPlanetWS/Servers/bin/https/jar/NSJavaMiscUtil.jar:/export/home/gmacsmi/iPlanetWS/Servers/bin/https/jar/servlet.jar:/export/home/gmacsmi/iPlanetWS/Servers/bin/https/jar/servlet-2.3-filters-api.jar:/export/home/gmacsmi/iPlanetWS/Servers/bin/https/jar/jsp092.jar:/export/home/gmacsmi/iPlanetWS/Servers/bin/https/jar/jaxp.jar:/export/home/gmacsmi/iPlanetWS/Servers/bin/https/jar/crimson.jar:/export/home/gmacsmi/iPlanetWS/Servers/bin/https/jar/xalan.jar:/export/home/gmacsmi/iPlanetWS/Servers/bin/https/jar/jspengine.jar:
[29/Mar/2007:22:28:20] info ( 8394): Loading IWSSessionManager by default.
[29/Mar/2007:22:28:20] info ( 8394): IWSSessionManager: Maximum number of sessions is 1000
[29/Mar/2007:22:28:49] info ( 8394): Internal Info: loading servlet /gmacsm/jsp/Login.jsp
[29/Mar/2007:22:28:49] info ( 8394): /gmacsm/jsp/Login.jsp: init
[29/Mar/2007:22:28:49] info ( 8394): Internal Info: loading servlet /common/oblixurl.jsp
[29/Mar/2007:22:28:49] info ( 8394): /common/oblixurl.jsp: init
[29/Mar/2007:22:28:57] config ( 8394): SIGSEGV 11 segmentation violation
[29/Mar/2007:22:28:57] config ( 8394): si_signo [11]: SEGV
[29/Mar/2007:22:28:57] config ( 8394): si_errno [0]:
[29/Mar/2007:22:28:57] config ( 8394): si_code [1]: SEGV_MAPERR [addr: 0x8]
[29/Mar/2007:22:29:01] failure ( 8389): Child process admin thread is shutting down
Thanks

NSAPI failure on NT

Similar Messages

Maybe you are looking for