Thanks for the reply, Chris.
I did more of analysis today and I find that if I am trying to connect to
the database then only I get this error. Servlets which are not interacting
with the database do not give any problem. I saw the sql jar file and it's
permissions. I changed the mode to 0777, it still doesn't work.
But that's for sure that the problem here relates to database connectivity.
But then the log message doesn't seem to be like that.
-----Original Message-----
From: Brevsville Administrator [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 22, 2000 10:04 PM
To: [EMAIL PROTECTED]
Subject: Re: cannot scan servlet headers
Hi Anshul
it means the servlet is not visible to JServ. Two usual causes are :
1) read permissions on the jar/class file
2) class/jar no in the correct place
hth
Chris
On Thu, 22 Jun 2000 16:14:18 +0530, Anshul Dutta wrote:
>Does anyone have any clue for this type of error that appears in
>mod_jserv.log ???
>
>___________________________________________________________________________
>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
