tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "JS" <sma...@dcs.kcl.ac.uk>
Subject RE: Dodgy web.xml and error in catalina.out
Date Tue, 08 Apr 2003 20:26:16 GMT
Just some info on further developments.
Thank u Andrew 4ur last mail. The solution was the same for me. The frames
in my html page were referencing "servlet/mypackage.myservlet"When it should be the full qualified
name for my web app
i.e. "mydcs/servlet/package.servlet". It worked.

Though two elements of concern still remain.

The web.xml is still looking dodgy.
The java web services log shows ;

2003-04-08 21:08:48 StandardWrapper[/djs:invoker]: Loading container
servlet invoker2003-04-08 21:08:48 invoker: init
2003-04-08 21:08:48 jsp: init
2003-04-08 21:08:48 Exception initializing TldLocationsCache: XML parsing
error on file /WEB-INF/web.xml: (line 1, col 10): Document root element
"web-app", must match DOCTYPE root "null".2003-04-08 21:08:48 HostConfig[localhost]: Deploying
web application
directory mydcs2003-04-08 21:08:48 StandardHost[localhost]: Installing web application at
context path /mydcs from URL file:C:\WINDOWS\jwsdp-1_0_01\webapps\mydcs2003-04-08 21:08:48
WebappLoader[/mydcs]: Deploying class repositories to
work directory C:\WINDOWS\jwsdp-1_0_01\work\Standard
Engine\localhost\mydcs2003-04-08 21:08:48 WebappLoader[/mydcs]: Deploy class files
/WEB-INF/classes to C:\WINDOWS\jwsdp-1_0_01\webapps\mydcs\WEB-INF\classes2003-04-08 21:08:49
StandardManager[/mydcs]: Seeding random number
generator class java.security.SecureRandom2003-04-08 21:08:49 StandardManager[/mydcs]: Seeding
of random number
generator has been completed2003-04-08 21:08:49 LoginServletNoPool: init


Thanks
JS

> Hi Yoav,
> thanks for getting back to me. Just been following up your questions. -
> url patterns dont make sense. In what way do you mean. Is something
> significantly missing from the web.xml file??
> - DTD File. I dont know how to get hold of it, know network problems.
> Any idea how I can turn on the JWSDP debugging?
> - HTML Source. The source is taken from Marty Hall's core servlets
> book. Basically it tests the performance of the connection pool program
> by rendering 25 "semi"-simultaneous requests to the servlet and
> displaying the results in a frame. Here's the source.The access logs
> show the same urls that are in the HTML file. A couple of the frames
> will generate different error codes i.e. 503s instead of 404si.e.
> 127.0.0.1 - - [08/Apr/2003:19.06:17 00] "GET
> /servlet/coreservlets.ConnectionPoolServlet HTTP/1.1" 404 -
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN">
> <HTML>
> <HEAD><TITLE>Servlet Connection Pooling: A Test</TITLE></HEAD>
>
> <!-- Causes 25 near simultaneous requests for same servlet. -->
>
> <FRAMESET ROWS="*,*,*,*,*" BORDER=0 FRAMEBORDER=0 FRAMESPACING=0>
>  <FRAMESET COLS="*,*,*,*,*">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>  </FRAMESET-
>  <FRAMESET COLS="*,*,*,*,*">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>  </FRAMESET>
>  <FRAMESET COLS="*,*,*,*,*">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>  </FRAMESET>
>  <FRAMESET COLS="*,*,*,*,*">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>  </FRAMESET>
>  <FRAMESET COLS="*,*,*,*,*">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>    <FRAME SRC="/servlet/coreservlets.ConnectionPoolServlet">
>  </FRAMESET>
>
> </FRAMESET>
>
> </HTML>
>
> FYI The structure of my webapp is
> TOMCAT_HOME\webappp\mydcs
> ......... all html files, including this one
>
> \webapp\mydcs\WEB-INF
> ...............web.xml
> ...............\classes
> .................. folder called "coreservlets" containing the class
> files for the connection pool program.
> Thanks again.
>
>
>
>
>
>
>
>
>
>>
>> Howdy,
>> A couple of things seem interesting:
>>
>> - Your url-patterns in web.xml don't make any sense.
>> - You should declare packages for your servlets, e.g. your
>> LoginServlet, but this is not absolutely required.
>> - Can you reach the network location where the DTD is?  i.e. are you
>> having any network problems?
>>
>>>Problem is, when I try and access it through a html page, I get the
>>>404
>>
>> Post the HTML source.
>>
>>>error in one frame and the 503 in another frame. Both the frames in
>>>the html document are accessing the same servlet.
>>
>> Verify this using the access log, which shows you exactly what URL
>> your frames are requesting.
>>
>>>Starting service Java Web Services Developer Pack
>>>Java Web Services Developer Pack/1.0_01-fcs
>>>org.xml.sax.SAXParseException: Document root element "web-app", must
>> match
>>>DOCTYPE root "null".	At
>>
>> Can you turn on JWSDP debugging so that it gives the full URL of the
>> web.xml it's trying to parse?
>>
>> Yoav Shapira
>> Millennium ChemInformatics
>>
>>
>>
>> This e-mail, including any attachments, is a confidential business
>> communication, and may contain information that is confidential,
>> proprietary and/or privileged.  This e-mail is intended only for the
>> individual(s) to whom it is addressed, and may not be saved, copied,
>> printed, disclosed or used by anyone else.  If you are not the(an)
>> intended recipient, please immediately delete this e-mail from your
>> computer system and notify the sender.  Thank you.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For
>> additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For
> additional commands, e-mail: tomcat-user-help@jakarta.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message