Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

OSE/NSAPI errors

3 views
Skip to first unread message

Jerry Brown

unread,
Dec 7, 2001, 3:43:03 PM12/7/01
to
Hello all,

I am trying to track down a vexxing problem, wondering if anyone has any
ideas.

I have an applet that is communicating through port 80 to a servlet on
the app server. It appears that all communication from the applet is
received by the servlet, but when the servlet tries to respond, we get
sporadic java.io.IOException exceptions. Concurrently, we get OSE/NSAPI
errors on the web server logs.

We're using WAS 3.5.4, iPlanet 4.

Here is the web server error log entries in question:
[07/Dec/2001:09:32:35] warning ( 4148): [was warning] reports:
ns_read_cb attempted to read 349 bytes

[07/Dec/2001:09:32:35] warning ( 4148): [was warning] reports:
ns_read_cb actually read 0 bytes

[07/Dec/2001:09:32:35] failure ( 4148): [was error] reports: ERROR: In
do_service_time_request, maybe server_message_flush failed

[07/Dec/2001:09:33:29] failure ( 4148): [was error] reports: OSE
specification violation!!! prepare_for_write() was not called before write()

[07/Dec/2001:09:33:29] failure ( 4148): [was error] reports: Exitting
ns_write_cb with failure

[07/Dec/2001:09:33:29] failure ( 4148): [was error] reports: ERROR: In
do_service_time_request, enter_callback_mode failed


Here's the stderr log on WebSphere:
[01.12.07 09:31:58:234 CST] 1c02006 WebGroup A SRVE0092I: [Servlet
LOG]: "N
PaintServerImpl: run error": java.io.IOException: Error during native
write oper
ation! Status Code: -1
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.io.IOException.<init>(Compiled Code)
at
com.ibm.servlet.engine.oselistener.nativeEntry.NativeServerConnection
.write(Compiled Code)
at com.ibm.servlet.engine.srp.SRPConnection.write(Compiled Code)
at com.ibm.servlet.engine.srt.SRTOutputStream.write(Compiled Code)
at
com.ibm.servlet.engine.srt.BufferedServletOutputStream.writeOut(Compi
led Code)
at
com.ibm.servlet.engine.srt.BufferedServletOutputStream.flushBytes(Com
piled Code)
at
com.ibm.servlet.engine.srt.BufferedServletOutputStream.flush(Compiled
Code)
at java.io.ObjectOutputStream.flush(Compiled Code)
<<snipped the rest for brevity>>

Is there a way to tweak OSE, or is that even the problem?

BTW, looks like we will be migrating over to WAS 4 in the middle of this
project. I understand that it does not use OSE? Would this solve
problems of this type?

Thanks,
Jerry

--
Jerry Brown
Worldwide Information Technologies
http://www.wit-usa.com
Email: jerry...@wit-usa.com
Phone: 214-678-1050, ext. 344

Todd Kaplinger

unread,
Dec 8, 2001, 9:35:50 AM12/8/01
to
The error during native write typically indicates that the client terminated
the response before the response was completed.

"Jerry Brown" <jerry...@wit-usa.com> wrote in message
news:3C1129D7...@wit-usa.com...

Jerry Brown

unread,
Dec 10, 2001, 9:43:53 AM12/10/01
to
Todd, by "client" are you referring to the applet, which is on the
'clients' computer during execution, and is communicating with the
servlet, which is on the server? Or, are you referring to the servlet as
the 'client', which is writing to the server?

This one is making us crazy...

JB

0 new messages