Another thing I do is turn off the JIT // FOR TESTING //
Compiler.disable(); //turn off JIT so we can see line numbers when
debugging. Of course there is the un-scientific way of just putting some
System.out.println("Error 1"); etc. in your servlet code to find out the
last point at which it throws an exception. Also check the
weblogic.properties file to make sure your resources are being used
appropriately.
T. Kochanowicz
-----Original Message-----
From: A mailing list for discussion about Sun Microsystem's Java Servlet
API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of Tom
K.
Sent: Friday, September 29, 2000 3:49 PM
To: [EMAIL PROTECTED]
Subject: Re: problem executing servlet in weblogic 5.1
I would suggest you post your question to the weblogic.developer.newsgroup.
T. Kochanowicz
-----Original Message-----
From: A mailing list for discussion about Sun Microsystem's Java Servlet
API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of
Mullayev, Roman
Sent: Friday, September 29, 2000 1:00 PM
To: [EMAIL PROTECTED]
Subject: problem executing servlet in weblogic 5.1
Hi,
I am running Weblogic 5.1 server (for Solaris) on which I am trying to setup
web
application that runs well on JRun 3.0 engine at this time. The web app. is
coded and setup according Servlet 2.2 specs.
I have added weblogic.httpd.webApp.appname property to weblogic.properties
file that points to root directory of web app.
It seems like it works ok when excessing jsp pages.
But whenever I try to excess the only servlet, FrontServet, (request
dispatcher) the server returns 500 error. In the Weblogic log file I am
getting the following exception:
Fri Sep 28 15:39:03 EDT 2000:<I> <WebAppServletContext-uma> FrontServlet:
init
Thu Sep 28 15:39:03 EDT 2000:<E> <Posix Performance Pack> Failure in
processSockets()
java.net.SocketException: Connection reset by peer: Connection reset by peer
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.socketRead(Compiled Code)
at java.net.SocketInputStream.read(Compiled Code)
at weblogic.socket.PosixSocketMuxer.processSockets(Compiled Code)
at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
Also, I have sample servlet running ok that was setup in weblogic default
context.
Does anyone know what the nature of the problem might be?
Thanks in advance...
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
