Problems with Tomcat 4.1.12 hanging

[Leonard O'Halloran]

Hi all,

I am using currently using Tomcat 4.1.12 for an application I have 
developed. I have a report that displays a large list of records retrieved from 
a database. The report is generated using a JSP. This operation seems to take a 
very long time and I assumed initially the time was spent in the data 
retrieval. However I have generated a number of stack traces while my 
application is "hanging" and the thread creating the report seems to be 
consistently waiting on a condition within the Jasper functionality. The 
generated stack trace from the thread creating the report is as follows:

"Thread-6" daemon prio=5 tid=0x24f92788 nid=0x714 waiting on condition 
[25afe000..25affd88]
at 
org.apache.jasper.runtime.BodyContentImpl.reAllocBuff(BodyContentImpl.java:82)
at 
org.apache.jasper.runtime.BodyContentImpl.write(BodyContentImpl.java:144)
at 
org.apache.jasper.runtime.BodyContentImpl.write(BodyContentImpl.java:155)
at 
org.apache.jasper.runtime.BodyContentImpl.print(BodyContentImpl.java:291)
at 
org.apache.struts.util.ResponseUtils.writePrevious(ResponseUtils.java:184)
at 
org.apache.struts.taglib.logic.IterateTag.doAfterBody(IterateTag.java:412)
at 
org.apache.struts.taglib.nested.logic.NestedIterateTag.doAfterBody(NestedIterateTag.java:160)
at 
org.apache.jsp.ViewInvoiceByProduct_jsp._jspService(ViewInvoiceByProduct_jsp.java:275)
at 
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:92)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:204)
at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289)
at 
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
at 
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:575)
at 
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:498)
at 
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:768)
at 
org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:359)
at 
org.apache.struts.taglib.tiles.InsertTag.doInclude(InsertTag.java:703)
at 
org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsertTag.java:814)
at 
org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:467)
at 
org.apache.jsp.classicLayout_jsp._jspx_meth_tiles_insert_1(classicLayout_jsp.java:145)
at 
org.apache.jsp.classicLayout_jsp._jspService(classicLayout_jsp.java:85)
at 
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:92)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:204)
at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289)
at 
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
at 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:432)
at 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:356)
at 
org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1033)
at 
org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:268)
at 
org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition(TilesRequestProcessor.java:248)
at 
org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.java:302)
at 
org.apache.struts.action.RequestProcessor.processActionForward(RequestProcessor.java:401)
at 
ie.mcps.framework.web.McpsiRequestProcessor.processActionForward(McpsiRequestProcessor.java:83)
at 
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at 
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1339)
at 
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:489)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(

JNDI Data Source in GlobalNamingResources for Tomcat 4.1.12

[Li, Qiang]

Is there anyone know how to set up JNDI datasource in
GlobalNamingResources for Tomcat4.1.12?

Qiang Li
OMNI
Information Technology Unit
Washington State Department of Corrections
(360)570-6921 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ClassNotDefError problems within JAR files under Tomcat 4.1.12

[Christopher Schultz]

Nathan,

I am developing an imaging servlet under Tomcat 4.1.12 using JAI 1.1.2.
Every time I update my code to add new features, it will return with a
NoClassDefFoundError until I restart Tomcat.  At that point, it finds
the 'missing' class and everything works as expected.
I'm no expert on JAI, but I believe that it uses JNI and a native
library to do some of it's dirty work. If that's the case, then you
should make sure that the JAI JAR file and native library are loaded by
a classloader outside ("higher than") your webapp.
There's documentation on the Tomcat site (and probably other servlet
containers, too) that says that native libraries should only be loaded
one time. IF they get loaded multiple times (as would happen if they
were loaded by the webapp), strange behavior can result.
Try putting jai.jar (or whatever) into TOMCAT_HOME/common/lib and jai.so
(or whatever) in a convenient place where it can be found. (Sorry, dunno
where that might be. Anyone else?)
Hope that helps,
-chris


signature.asc
Description: PGP signature


signature.asc
Description: OpenPGP digital signature

Re: ClassNotDefError problems within JAR files under Tomcat 4.1.12

[Nathan Rogers]

I just noticed a slight (but important typo).  Sorry for the reply to my
own message.
It should say "and they are picked up on a reload without having to
restart the entire container." rather than what it actually does say.
Spellcheckers should be smart enough to know what I mean, even if what I
said was legal English. :)
Nathan Rogers wrote:

I am developing an imaging servlet under Tomcat 4.1.12 using JAI 1.1.2.
Every time I update my code to add new features, it will return with a
NoClassDefFoundError until I restart Tomcat.  At that point, it finds
the 'missing' class and everything works as expected.
Only the superficial ImageIO classes are directly invoked (ImageReader,
ImageWriter, ImageIO) - the NoClassDefFoundErrors are always for
implementation specific classes (typically com.sun.media.*).  I've
verified that the files are in JAR files located under /WEB-INF/lib so
they should be picked up by Tomcat on a reload.  Are the JAR files not
scanned for dependencies on a reload?  I've never had this problem with
classes that I create - I simply place them in /WEB-INF/classes// and they are picked up on a reload with having to
restart the entire container.
Here is the last error that I saw - this is typical of what I see when
these errors occur
java.lang.NoClassDefFoundError:
com/sun/media/imageioimpl/plugins/jpeg2000/J2KReadState
at
com.sun.media.imageioimpl.plugins.jpeg2000.J2KImageReader.readHeader(J2KImageReader.java:285) 

at
com.sun.media.imageioimpl.plugins.jpeg2000.J2KImageReader.getWidth(J2KImageReader.java:235) 

at edu.wisc.library.ltg.digitalCollections.JP2Image.(JP2Image.java:93)
at
edu.wisc.library.ltg.digitalCollections.ImageFactory.createImage(ImageFactory.java:73) 

at
edu.wisc.library.ltg.digitalCollections.TestCollectionImpl.getResource(TestCollectionImpl.java:59) 

at
edu.wisc.library.ltg.imageServlet.SimpleImageServlet.doGet(SimpleImageServlet.java:177) 

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) 

at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) 

at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260) 

at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 

at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 

at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 

at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2396)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) 

at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 

at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) 

at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) 

at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) 

at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) 

at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) 

at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 

at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:405)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:380) 

at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:533) 

at java.lang.Thread.run(Thread.java:534)



--
Nathan Rogers
Library Technology Group
312F Memorial Library
728 State Street
261-1409
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit

ClassNotDefError problems within JAR files under Tomcat 4.1.12

[Nathan Rogers]

I am developing an imaging servlet under Tomcat 4.1.12 using JAI 1.1.2.
Every time I update my code to add new features, it will return with a
NoClassDefFoundError until I restart Tomcat.  At that point, it finds
the 'missing' class and everything works as expected.
Only the superficial ImageIO classes are directly invoked (ImageReader,
ImageWriter, ImageIO) - the NoClassDefFoundErrors are always for
implementation specific classes (typically com.sun.media.*).  I've
verified that the files are in JAR files located under /WEB-INF/lib so
they should be picked up by Tomcat on a reload.  Are the JAR files not
scanned for dependencies on a reload?  I've never had this problem with
classes that I create - I simply place them in /WEB-INF/classes// and they are picked up on a reload with having to
restart the entire container.
Here is the last error that I saw - this is typical of what I see when
these errors occur
java.lang.NoClassDefFoundError:
com/sun/media/imageioimpl/plugins/jpeg2000/J2KReadState
at
com.sun.media.imageioimpl.plugins.jpeg2000.J2KImageReader.readHeader(J2KImageReader.java:285)
at
com.sun.media.imageioimpl.plugins.jpeg2000.J2KImageReader.getWidth(J2KImageReader.java:235)
at edu.wisc.library.ltg.digitalCollections.JP2Image.(JP2Image.java:93)
at
edu.wisc.library.ltg.digitalCollections.ImageFactory.createImage(ImageFactory.java:73)
at
edu.wisc.library.ltg.digitalCollections.TestCollectionImpl.getResource(TestCollectionImpl.java:59)
at
edu.wisc.library.ltg.imageServlet.SimpleImageServlet.doGet(SimpleImageServlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2396)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:405)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:380)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:533)
at java.lang.Thread.run(Thread.java:534)

--
Nathan Rogers
Library Technology Group
312F Memorial Library
728 State Street


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Auto Conf file for Apache 2.0.43 with Tomcat 4.1.12

[John Turner]

Yes, I get your point.

It doesn't get generated because you have to modify server.xml.  You have 
to add Listener elements to server.xml.

This is all described step by step in my HOWTO, if you search for 
"Listener" you will find the steps that do the describing.

John

On Wed, 25 Jun 2003 16:37:25 -0300, Martín Mauri <[EMAIL PROTECTED]> 
wrote:

John,

I had just looked at that file, the thing's that it says: Include
/usr/local/tomcat/conf/auto/mod_jk.conf.
Ok, now, this file mod_jk.conf is supposed to be autogenerated by Tomcat 
at
startup...but it didn't happened in my system do you get my point?

thanks,

Martin

- Original Message -
From: "John Turner" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, June 25, 2003 4:05 PM
Subject: Re: Auto Conf file for Apache 2.0.43 with Tomcat 4.1.12

http://www.johnturner.com/howto

Search for "Listener".

John

On Wed, 25 Jun 2003 15:18:09 -0300, Martín Mauri <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> I've read that Tomcat generates an auto-config file for Apache called
> mod_jk.conf for mod_jk when it starts. Somehow it's disabled in my
> tomcat,
> can anybody tell me how to activate it?
>
> thannk you !!
>
> Martin
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Auto Conf file for Apache 2.0.43 with Tomcat 4.1.12

[Martín Mauri]

John,

I had just looked at that file, the thing's that it says: Include
/usr/local/tomcat/conf/auto/mod_jk.conf.
Ok, now, this file mod_jk.conf is supposed to be autogenerated by Tomcat at
startup...but it didn't happened in my system do you get my point?

thanks,

Martin

- Original Message -
From: "John Turner" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, June 25, 2003 4:05 PM
Subject: Re: Auto Conf file for Apache 2.0.43 with Tomcat 4.1.12


>
> http://www.johnturner.com/howto
>
> Search for "Listener".
>
> John
>
> On Wed, 25 Jun 2003 15:18:09 -0300, Martín Mauri <[EMAIL PROTECTED]>
> wrote:
>
> > Hi,
> >
> > I've read that Tomcat generates an auto-config file for Apache called
> > mod_jk.conf for mod_jk when it starts. Somehow it's disabled in my
> > tomcat,
> > can anybody tell me how to activate it?
> >
> > thannk you !!
> >
> > Martin
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
>
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Auto Conf file for Apache 2.0.43 with Tomcat 4.1.12

[John Turner]

http://www.johnturner.com/howto

Search for "Listener".

John

On Wed, 25 Jun 2003 15:18:09 -0300, Martín Mauri <[EMAIL PROTECTED]> 
wrote:

Hi,

I've read that Tomcat generates an auto-config file for Apache called
mod_jk.conf for mod_jk when it starts. Somehow it's disabled in my 
tomcat,
can anybody tell me how to activate it?

thannk you !!

Martin

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Auto Conf file for Apache 2.0.43 with Tomcat 4.1.12

[Martín Mauri]

Hi,

I've read that Tomcat generates an auto-config file for Apache called
mod_jk.conf for mod_jk when it starts. Somehow it's disabled in my tomcat,
can anybody tell me how to activate it?

thannk you !!

Martin


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat 4.1.12/18 Startup Delay

[Lopez David E-r9374c]

Nikolaos

I also have this problem. In my case, apache must only start
if the conf/auto/modjk.conf has been written. From the time
that startup.sh finishes to when it's safe to start apache is
30 or so seconds. The wait time is variable, so a 30 second
sleep in my /etc/init.d reboot script might work today but 
fail in the future.

My vote would be to have startup.sh exit when tomcat processed
all the code it needs.

If you come up with a solution, please let me know.

David

> -Original Message-
> From: Nikolaos Giannopoulos [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 29, 2003 10:01 AM
> To: [EMAIL PROTECTED]
> Subject: Tomcat 4.1.12/18 Startup Delay
> 
> 
> Hi,
> 
> Is there any reason why Tomcat 4.1.12 and 4.1.18 (on Solaris 
> 8, Sun E450
> Dual 400MHz 1GB RAM) requires about 10-15 second delay after 
> the startup.sh
> script is executed before it can process requests.  We have 
> observed the
> same situation on other boxes.
> 
> Essentially startup.sh returns quite quickly after the script 
> is executed
> but if you attempt to invoke servlets on it they fail (until 10 or so
> seconds after the script returns).
> 
> We noticed this with our RC (server reboot) script and had to 
> manually enter
> a "sleep 15" between Tomcat startup and our apps startup 
> OTHERWISE our app
> would not startup properly as it immediately tries to 
> initialize servlets
> and fails.
> 
> Shouldn't startup.sh return *only* when Tomcat is able to 
> service requests?
> 
> --Nikolaos
> 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat 4.1.12/18 Startup Delay

[Shapira, Yoav]

Howdy,

>Is there any reason why Tomcat 4.1.12 and 4.1.18 (on Solaris 8, Sun
E450
>Dual 400MHz 1GB RAM) requires about 10-15 second delay after the
startup.sh
>script is executed before it can process requests.  We have observed
the
>same situation on other boxes.

>Shouldn't startup.sh return *only* when Tomcat is able to service
requests?

No.

How long tomcat takes to start up depends greatly on what the installed
webapps do on startup.  There can be a lot of processing done in various
listener, filter, and servlet init methods.  Tomcat deploys webapps and
launches those startup events in a very efficient and quick way (I've
profiled this myself to make sure).

Try disabling all unneeded webapps and see if startup time improves.
This includes the examples context as well as the manager/admin contexts
if you don't need them.

Yoav Shapira



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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat 4.1.12/18 Startup Delay

[Nikolaos Giannopoulos]

Hi,

Is there any reason why Tomcat 4.1.12 and 4.1.18 (on Solaris 8, Sun E450
Dual 400MHz 1GB RAM) requires about 10-15 second delay after the startup.sh
script is executed before it can process requests.  We have observed the
same situation on other boxes.

Essentially startup.sh returns quite quickly after the script is executed
but if you attempt to invoke servlets on it they fail (until 10 or so
seconds after the script returns).

We noticed this with our RC (server reboot) script and had to manually enter
a "sleep 15" between Tomcat startup and our apps startup OTHERWISE our app
would not startup properly as it immediately tries to initialize servlets
and fails.

Shouldn't startup.sh return *only* when Tomcat is able to service requests?

--Nikolaos





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Apache-2.0.43 + Tomcat-4.1.12 + MOD_JK2 -- Problem while redirecting from one jsp to another

[Sushil Jadhav]

Hi,
(B
(BI have a following scenario.
(B
(BI am using apache tomcat combination with mod_jk2.
(BIt works fine when I access it with IP address and port no. in URL
(B(e.g. .
(B
(BBut when I access the same jsp with host name in URL
(B(e.g. .
(BI get nothing,
(B
(BI analyzed the problem (but no solution yet ),
(B
(Bwhen the request is redirected, port no. is getting appended to domain name.
(B(e.g. .
(B
(Bis somebody share the same problem, and have any suggestions/answers.
(B
(BRegards,
(BSusheel
(B
(B
(B
(B
(B
(B
(B
(B
(B

problem with Tomcat 4.1.12 and Dell optiplex gs260 pc

[Yong Wang]

Hi, I got the following exception when I run tomcat
4.1.12, J2SDK1.4.1.02 (or J2SDK1.4.0.03) on a Dell
optiplex gs 260 PC running W2K sp3. The same
application works fine if I run tomcat 4.0.06 and
J2SDK1.4.1.02 on the same PC. What could be the cause?
(btw, the class it crashes at is compiled with a
earlier JDK and no source code is available). Thanks
for your help.


2003-03-25 17:57:50 StandardWrapperValve[Dispatcher]:
Allocate exception for servlet Dispatcher
javax.servlet.ServletException: Servlet.init() for
servlet Dispatcher threw exception
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:952)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:658)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2396)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:405)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:380)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:533)
at java.lang.Thread.run(Thread.java:536)
- Root Cause -
java.lang.VerifyError: (class:
com/cysive/framework/forms/FormDefinitionRepository,
method: initialize signature: (Ljava/lang/String;)V)
Incompatible object argument for function call
at
com.cysive.framework.forms.FormInitializer.initialize(FormInitializer.java:116)
at
com.cysive.framework.util.config.InitializerSpec.initialize(InitializerSpec.java:88)
at
com.cysive.framework.util.config.ConfigHandler.initialize(ConfigHandler.java:185)
at
com.cysive.framework.util.config.ConfigManager.readConfig(ConfigManager.java:184)
at
com.cysive.framework.util.config.ConfigManager.initialize(ConfigManager.java:141)
at
com.cysive.framework.util.config.ConfigManager.reload(ConfigManager.java:122)
at
com.cysive.framework.util.config.Bootstrap.reload(Bootstrap.java:242)
at
com.cysive.framework.servlet.controller.Dispatcher.initBootstrap(Dispatcher.java:739)
at
com.cysive.framework.servlet.controller.Dispatcher.init(Dispatcher.java:373)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:924)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:658)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at

Re: tomcat 4.1.12

[puneet sachar]

hi ,

r u the same kapil form deshbandhu colleage...

Let me know

Puneet

__
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

tomcat 4.1.12

[Kapil Sharma]

Hi,
If someone is using tomcat 4 in production environment under heavy loads on
solaris , please send me your server.xml file. I am looking for tomcat
parameter to check my server.xml file on production systems.


Thanks
kapil


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Looking for Pointers on Securing Tomcat 4.1.12 for Public use

[David Kramer]

Newbie here, Im looking for Security Pointers on securing Tomcat 4.1.12 in
Standalone mode running on Rh7.3  I have the normal security stuff in place,
Snort and Tripwire.  I have read through the Security Manager How-To already
and Im just looking for some personal insight, any thoughts are welcome? 

Thanks much,

DK

David Kramer
Software Developer
Reflect.com
Direct: 415.369.4856
Cell: 650.302.7889


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

LogConfigurationException on Tomcat 4.1.12

[Jaimes Blunt]

Hi Everyone,

Has anyone seen the following error on Tomcat4.1.12 running with jdk1.3.  Whenever I 
get this message it pretty much stops all requests from accessing the server.  I just 
end up with page cannot be displayed on the client side.

org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging
.LogConfigurationException: org.apache.commons.logging.LogConfigurationException
: Class org.apache.commons.logging.impl.SimpleLog does not implement Log
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
Impl.java:530)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
Impl.java:285)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:401)
at org.apache.tomcat.util.log.CommonLogHandler.log(CommonLogHandler.java
:97)
at org.apache.tomcat.util.log.Log.log(Log.java:198)
at org.apache.tomcat.util.log.Log.log(Log.java:192)
at org.apache.tomcat.util.log.Log.log(Log.java:174)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:536)
at java.lang.Thread.run(Thread.java:484)

Thanks All

Jaimes

Re: help with SSI directives on tomcat 4.1.12

[Becky Phaneuf]

http://jakarta.apache.org/tomcat/tomcat-4.1-doc/ssi-howto.html

-B



>>> [EMAIL PROTECTED] 02/27/03 06:55PM >>>
Hello all
I am using the following SSI directive in a .shtml file in the
ROOT directory:


OutputServlet1 is a servlet class that just prints "helllo."
(some plain text). I have a println in doGet which wud not print.

It shows in the browser as "[an error occurred while processing
this directive]".

Even if I use any other directive I have the same problem.

Please advise
thanks
Mahesh



-
To unsubscribe, e-mail: [EMAIL PROTECTED] 
For additional commands, e-mail: [EMAIL PROTECTED] 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

help with SSI directives on tomcat 4.1.12

[jonnala]

Hello all
I am using the following SSI directive in a .shtml file in the
ROOT directory:


OutputServlet1 is a servlet class that just prints "helllo."
(some plain text). I have a println in doGet which wud not print.

It shows in the browser as "[an error occurred while processing
this directive]".

Even if I use any other directive I have the same problem.

Please advise
thanks
Mahesh



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem with Tomcat 4.1.12, coyote connector connectionTimeout

[Sven Köhler]

you should run apache and use mod_jk. than you can use the webserver's 
support for SSL.

for a heavy loaded site, it's always a good idea, to use apache+mod_jk 
(or some other webserver of course)

i know, that this is only a work-around, but the only sollution i see 
for you at the moment.
i don't believe, that it is a tomcat-bug, because than this should 
happen from the very first start. it must be some kind of weired 
socket-problem perhaps.

Charles Blaxland wrote:
We have configured Tomcat with the Coyote HTTP/1.1 connector.  It runs fine
for several days (or even a week), but then all HTTP/1.1 redirects begin
taking a long time to return - in fact, they take exactly 60 seconds, which
leads me to believe that it has something to do with the connectionTimeout.
HTTP/1.0 requests are fine, however.
 
Does anyone know what is causing this problem?  Has it been previously
identified/fixed?  I realise that there have been many fixes in the coyote
connector in 4.1.18 - unfortunately we can't run 4.1.18 because of the
problems it has with SSL.  Is there something we can do in 4.1.12 to work
around this?
 
Thanks,
Charles
 
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Problem with Tomcat 4.1.12, coyote connector connectionTimeout

[Charles Blaxland]

We have configured Tomcat with the Coyote HTTP/1.1 connector.  It runs fine
for several days (or even a week), but then all HTTP/1.1 redirects begin
taking a long time to return - in fact, they take exactly 60 seconds, which
leads me to believe that it has something to do with the connectionTimeout.
HTTP/1.0 requests are fine, however.
 
Does anyone know what is causing this problem?  Has it been previously
identified/fixed?  I realise that there have been many fixes in the coyote
connector in 4.1.18 - unfortunately we can't run 4.1.18 because of the
problems it has with SSL.  Is there something we can do in 4.1.12 to work
around this?
 
Thanks,
Charles
 
 

RE: Oracle connection pooling + Tomcat 4.1.12

[pqin]

Tomcat's connection pooling utilizes its JNDI implementation plus
commons-dbcp and pooling, so you have to use whatever the JNDI-datasource
documentation tells you to do, that is

1. type="javax.sql.DataSource"
2.
driverClassName
oracle.jdbc.driver.OracleDriver
3. Do not define factory, there is default value by Tomcat.

Behind the scene, Tomcat will use BasicDataSource and PoolableConnection
(whose underlying connection is OracleConnection).

If you do wish to use Oracle's connection pooling, I didn't have luck
either. But I tried its connection caching.


Regards,
 
 
PQ
 
"This Guy Thinks He Knows Everything"
"This Guy Thinks He Knows What He Is Doing"

-Original Message-
From: Alexey Yastremskiy [mailto:[EMAIL PROTECTED]] 
Sent: February 20, 2003 12:04 AM
To: Tomcat Users List
Subject: Oracle connection pooling + Tomcat 4.1.12

Hi.

I've got a problem: I tried to setup oracle connection pooling in my
tomcat configuration, but didn't succeed. I checked Tomcat docs and Oracle
docs to produce this, but nothing helped :(
Does anyone have in production such a configuration, using
Oracle-implemented connection pooling? Please, help me to do the
same...

Here is my configs

[server.xml]




factory
 
oracle.jdbc.pool.OracleDataSourceFactory


dataSourceName
 
oracle.jdbc.pool.OracleConnectionPoolDataSource


url
jdbc:oracle:thin:@dbserver:1521:SID


description
my datasource


user
...


password
...


...
[end server.xml]

[web.xml]
 ...

my db
jdbc/DB
 
javax.sql.ConnectionPoolDataSource

...
[end web.xml]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Oracle connection pooling + Tomcat 4.1.12

[Mike Jackson]

I had problems using oracle connection pooling when I was using
transactions.  So I scrapped that and went back to poolman.  There is/was
something funny in the way it was doing things, I'd commit the transaction,
but it'd still be dirty or something.  As I explicitly set the isolation
mode prior to starting work I'd be getting these "commit prior to changing
transaction mode" exceptions back from oracle (don't remember exactly the
wording or the ora error code, but you get the idea).  I tried putting a
rollback or commit into the connection setup logic, but then I had other
strange results.

Sorry, I can't answer your question about your config, it could be ok, it
might not be.

--mikej
-=-
mike jackson
[EMAIL PROTECTED]

> -Original Message-
> From: Alexey Yastremskiy [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 19, 2003 9:04 PM
> To: Tomcat Users List
> Subject: Oracle connection pooling + Tomcat 4.1.12
>
>
> Hi.
>
> I've got a problem: I tried to setup oracle connection pooling in my
> tomcat configuration, but didn't succeed. I checked Tomcat docs and Oracle
> docs to produce this, but nothing helped :(
> Does anyone have in production such a configuration, using
> Oracle-implemented connection pooling? Please, help me to do the
> same...
>
> Here is my configs
>
> [server.xml]
> 
>  scope="Shareable" type="javax.sql.ConnectionPoolDataSource"/>
> 
> 
> factory
>
> oracle.jdbc.pool.OracleDataSourceFactory
> 
> 
> dataSourceName
>
> oracle.jdbc.pool.OracleConnectionPoolDataSource
> 
> 
> url
> jdbc:oracle:thin:@dbserver:1521:SID
> 
> 
> description
> my datasource
> 
> 
> user
> ...
> 
> 
> password
> ...
> 
> 
> ...
> [end server.xml]
>
> [web.xml]
>  ...
> 
> my db
> jdbc/DB
>
> javax.sql.ConnectionPoolDataSource e-env-ref-type>
> 
> ...
> [end web.xml]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Oracle connection pooling + Tomcat 4.1.12

[Alexey Yastremskiy]

Hi.

I've got a problem: I tried to setup oracle connection pooling in my
tomcat configuration, but didn't succeed. I checked Tomcat docs and Oracle
docs to produce this, but nothing helped :(
Does anyone have in production such a configuration, using
Oracle-implemented connection pooling? Please, help me to do the
same...

Here is my configs

[server.xml]




factory
oracle.jdbc.pool.OracleDataSourceFactory


dataSourceName
oracle.jdbc.pool.OracleConnectionPoolDataSource


url
jdbc:oracle:thin:@dbserver:1521:SID


description
my datasource


user
...


password
...


...
[end server.xml]

[web.xml]
 ...

my db
jdbc/DB

javax.sql.ConnectionPoolDataSource

...
[end web.xml]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

JAR problems with Tomcat 4.1.12 on Redhat 7.1

[Paul Bothma]

Hi,

This is a two part question, although I think the problems are related. I'm
using Tomcat 4.1.12 on Redhat 7.1 and JDK 1.4.1 RPM. Tomcat starts up fine
except for the following errors:

The /admin context doesn't want to load due to the following error:

2003-02-18 09:00:34 WebappLoader[/admin]: Deploying class repositories to
work directory /usr/jakarta-tomcat-4.1.12/work/Standalone/localhost/admin
2003-02-18 09:00:34 WebappLoader[/admin]: Deploy class files
/WEB-INF/classes to
/usr/jakarta-tomcat-4.1.12/webapps/../server/webapps/admin/WEB-INF/classes
2003-02-18 09:00:34 WebappLoader[/admin]: Deploy JAR /WEB-INF/lib/struts.jar
to
/usr/jakarta-tomcat-4.1.12/webapps/../server/webapps/admin/WEB-INF/lib/strut
s.jar
2003-02-18 09:00:34 ContextConfig[/admin] Exception processing JAR at
resource path /WEB-INF/lib/struts.jar
javax.servlet.ServletException: Exception processing JAR at resource path
/WEB-INF/lib/struts.jar
..

- Root Cause -
java.io.IOException: No such file or directory
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.checkAndCreate(File.java:1313)
at java.io.File.createTempFile(File.java:1401)
at java.io.File.createTempFile(File.java:1438)
at sun.net.www.protocol.jar.URLJarFile$1.run(URLJarFile.java:169)

The struts.jar file is located in /server/webapps/admin/WEB-INF/lib, not
sure if the part: /WEB-INF/lib/struts.jar to
/usr/jakarta-tomcat-4.1.12/webapps/../server/webapps/admin/WEB-INF/lib/strut
s.jar, is correct though. I didn't make any changes to /conf/server.xml and
the directory structure has not been altered either, so I can't see why this
shouldn't work.

The rest of Tomcat works, for exaple the /manager context works fine, and
can be accessed via: http://localhost:8080/manager/.

The other problem is that when I try to compile some JAVA classes that I
wrote located in /HP/WEB-INF/classes using  the following command:
$JAVA_HOME/bin/javac -classpath $PATH_TO_LIB/servlets.jar
$PATH_TO_WEB-INF/classes/*.java, I get the following error: Permission
denied  (I'm running all of this as root). Then I did chmod a+x
servlets.jar, and then I get the following: Cannot execute a binary file.
The file location is correct, etc. I think there is something wrong with the
handling of JAR files, becuase I can't connection to a MySQL database using
org.gjt.mm.Driver either. Doesn't give a ClassNotFoundException through.

Anyway, if someone has any ideas, please help.

Attached are the log files for the admin context and localhost.

Thanks,

Paul

2003-02-18 09:00:34 WebappLoader[/admin]: Deploying class repositories to work 
directory /usr/jakarta-tomcat-4.1.12/work/Standalone/localhost/admin
2003-02-18 09:00:34 WebappLoader[/admin]: Deploy class files /WEB-INF/classes to 
/usr/jakarta-tomcat-4.1.12/webapps/../server/webapps/admin/WEB-INF/classes
2003-02-18 09:00:34 WebappLoader[/admin]: Deploy JAR /WEB-INF/lib/struts.jar to 
/usr/jakarta-tomcat-4.1.12/webapps/../server/webapps/admin/WEB-INF/lib/struts.jar
2003-02-18 09:00:34 ContextConfig[/admin] Exception processing JAR at resource path 
/WEB-INF/lib/struts.jar
javax.servlet.ServletException: Exception processing JAR at resource path 
/WEB-INF/lib/struts.jar
at org.apache.catalina.startup.ContextConfig.tldScanJar(ContextConfig.java:930)
at org.apache.catalina.startup.ContextConfig.tldScan(ContextConfig.java:868)
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:647)
at 
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:243)
at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3493)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:821)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:579)
at 
org.apache.catalina.core.StandardHostDeployer.addChild(StandardHostDeployer.java:529)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:228)
at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:260)
at org.apache.commons.digester.Digester.endElement(Digester.java:1036)
at 
org.apache.xerces.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:579)
at 
org.apache.xerces.impl.XMLNamespaceBinder.endElement(XMLNamespaceBinder.java:646)
at 
org.apache.xerces.impl.dtd.XMLDTDValidator.ha

tomcat 4.1.12 root

[Lynn Young]

Hello,

I am new to tomcat 4.  I used to work on tomcat 3.3.

If I want to read a text file under my application_folder\data\ through 
a java bean program which is under my 
application_folder\web-inf\classes\myBean, how can I specify the path in the bean 
program?  In 3.3, the 
root is installation_folder\bin, so I can use relative path, this 
doesn't seem to work under 4.1.12, how to go around this?  

I know this question could have been asked before, but I couldn't find 
the answer in the archive, so thanks for any info.

Lynn




-
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day

RE: Apache 2 and Tomcat 4.1.12 on W2K

[Turner, John]

See my Win2K/WinXP HOWTO:

http://www.johnturner.com/howto

It uses 4.1.18, but the setup is exactly the same.  It details the setup of
the atuo-config option for Apache, though the file is now called
mod_jk.conf, not tomcat-auto.conf.

Also, regarding the AddModule statement...it's required for Apache 1.3, not
used for Apache 2.  Apache 2 only needs the LoadModule directive, Apache 1.3
needs both.

John

> -Original Message-
> From: Paul Bothma [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 17, 2003 2:36 AM
> To: Tomcat Help
> Subject: Apache 2 and Tomcat 4.1.12 on W2K
> 
> 
> Hi,
> 
> Senario:
> 
> I want to use Apache as a front end server to server static 
> content and
> Tomcat listening on port 8009 using mod_jk or perhaps another 
> method to get
> Apache to forward *.jsp and /servlet requests to Tomcat.
> 
> I'm using James 4.1.12 on W2K an would like to use the 
> tomcat.conf-auto
> file. I've looked through the documentation for Tomcat but 
> can't find out
> where I need to add the setting to enable Tomcat to create the file on
> startup. I've tried the Tomcat 3 method of using  confighome="c:/jakarta-tomcat/conf/" /> in /conf/server.xml, 
> but I can't
> still find the config file.
> 
> Any idea what I need to do to create this file.
> 
> FYI. I'm want to use the auto config file, because I'm having 
> troubles using
> a file that I created manually for Apache. The problem is 
> with the AddModule
> mod_jk.c line in /conf/httpd.conf. I've looked through 
> Apache's docs and it
> appears that the AddModule statement has been removed. I 
> guess that the
> mod_jk.dll only works for version 1.3 of  Apache. (I did 
> notice something in
> the Apache docs that there are some changes to how modules 
> are loaded in v.
> 2).
> 
> Any ideas on what can be done to get Tomcat and Apache 2 to 
> work together.
> 
> Thanks,
> 
> Paul
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Apache 2 and Tomcat 4.1.12 on W2K

[Paul Bothma]

Hi,

Senario:

I want to use Apache as a front end server to server static content and
Tomcat listening on port 8009 using mod_jk or perhaps another method to get
Apache to forward *.jsp and /servlet requests to Tomcat.

I'm using James 4.1.12 on W2K an would like to use the tomcat.conf-auto
file. I've looked through the documentation for Tomcat but can't find out
where I need to add the setting to enable Tomcat to create the file on
startup. I've tried the Tomcat 3 method of using  in /conf/server.xml, but I can't
still find the config file.

Any idea what I need to do to create this file.

FYI. I'm want to use the auto config file, because I'm having troubles using
a file that I created manually for Apache. The problem is with the AddModule
mod_jk.c line in /conf/httpd.conf. I've looked through Apache's docs and it
appears that the AddModule statement has been removed. I guess that the
mod_jk.dll only works for version 1.3 of  Apache. (I did notice something in
the Apache docs that there are some changes to how modules are loaded in v.
2).

Any ideas on what can be done to get Tomcat and Apache 2 to work together.

Thanks,

Paul


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: tomcat 4.1.12 hangs on HP-UX

[Tim Funk]

With my past experience with HP jvms- I would be surpised if 1.4.1.00 
was stable on their platform.

Try a 1.3 jvm with all the kernel patches and see if you can replicate 
the problem.

Also add -XdoCloseWithReadPending to your CATALINA_OPTS.


-Tim

Pfingstl Gernot wrote:
My tomcat hangs after around 30 requests to my struts-servlet. Tomcat doesn't write anything to some log (I had also set debug in server.xml) and doesn't shutdown (I had always to use kill -9 xx). I also looked to the garbage collector (JVM option -Xloggc:gc.log), but the heap size were about 64k (-Xmx was set to 300m). The responses are delayed about 5 to 10 seconds, because there must be fetched some data via OJB. If I do a JMeter test with the tomcat ROOT page (which has practically no delay), tomcat hangs after 5 requests.

Does anybody have any suggestions what to do or where the problem can be?

My configuration: tomcat 4.1.12 on HP-UX with jdk 1.4.1.00:
I tried with standard jvm opts, with
CATALINA_OPTS="-client -d64 -Xms30m -Xmx300m -Xincgc"
and
CATALINA_OPTS="-server -d64 -Xms30m -Xmx300m -Xincgc"
and
CATALINA_OPTS="-client -d64 -Xms30m -Xmx300m"

My connector:


Thank you,
Gernot

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat 4.1.12 Form authentication with IIS 5

[Paul Bothma]

Hi,

I've changed the web.xml to the following:


  HP Admin Security Constraint
  
 Protected Area
 /admin/index.jsp
 /admin/products.jsp
 /admin/groups.jsp
  
  
 admin
  



  FORM
  users
  
/admin/login.jsp
/jsp/error.jsp?code=login
  





  admin


, so as you can see the login.jsp page is not in the secured area any more.
At the moment, I do get directed to the login.jsp but when I try to submit
the form to 'j_security_check' I get the following error from IIS:

HTTP 405 - Resource not allowed.

When I modify uriworkermap.properties to include j_security_check, I get
redirected to a '404' error from Tomcat (based on my  settings
in web.xml). When I consult my MySQL logs I can see that Tomcat does not
even reach the stage where it should try to authenticate using MySQL.

Here is the relevant bit from my localhost_hp_log.txt

Log starts---

2003-02-14 10:15:23 Authenticator[/HP]: Security checking request POST
/HP/admin/j_security_check
2003-02-14 10:15:23 Authenticator[/HP]: Already authenticated ''
2003-02-14 10:15:23 Authenticator[/HP]:  Not subject to any constraint
2003-02-14 10:15:23 StandardContext[/HP]: Mapping contextPath='/HP' with
requestURI='/HP/admin/j_security_check' and
relativeURI='/admin/j_security_check'
2003-02-14 10:15:23 StandardContext[/HP]:  Mapped to servlet 'default' with
servlet path '/admin/j_security_check' and path info 'null' and update=true
2003-02-14 10:15:23 StandardContext[/HP]: Mapping contextPath='/HP' with
requestURI='/HP/jsp/error.jsp' and relativeURI='/jsp/error.jsp'
2003-02-14 10:15:23 StandardContext[/HP]:  Mapped to servlet 'jsp' with
servlet path '/jsp/error.jsp' and path info 'null' and update=true

Log ends---

Also, for some reason when I go to /admin it takes quite a long time (about
5 sec) to redirect me to login.jsp, whereas when I go to /admin on port 8080
it goes much quicker and it add the jsessionid= to the URL (which it
doesn't do with IIS)

Thanks,

Paul

-Original Message-
From: Sean Dockery [mailto:[EMAIL PROTECTED]]
Sent: 14 February 2003 04:08
To: Tomcat Users List
Subject: Re: Tomcat 4.1.12 Form authentication with IIS 5


What happens when you move your form-login-page outside of the /admin/
folder?

Sean Dockery
[EMAIL PROTECTED]
Certified Java Web Component Developer
Certified Delphi Programmer
SBD Consultants
http://www.sbdconsultants.com
- Original Message -
From: "Paul Bothma" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 13, 2003 06:11
Subject: Tomcat 4.1.12 Form authentication with IIS 5


> Hi,
>
> I'm using Tomcat 4.1.12 with IIS 5. When I connect directly to
> http://localhost:8080/HP/admin/ the Tomcat FORM authentication works fine,
> but when I try to connect to http://localhost/HP/admin I get the following
> error:
>
> HTTP Status 403 - Access to the requested resource has been denied
>
> --
--
> 
>
> type Status report
>
> message Access to the requested resource has been denied
>
> description Access to the specified resource (Access to the requested
> resource has been denied) has been forbidden.
>
>
> --
--
> 
>
> Apache Tomcat/4.1.12
>
> Here is the relevant extract from my web.xml file:
>
> 
>   HP Administration
>   
>  Protected Area
>  /admin/*
>   
>   
>  HP_admin
>   
> 
>
> 
>   FORM
>   users
>   
> /admin/login.jsp
> /error.html
>   
> 
>
>
> 
> 
>   HP_admin
> 
>
> I'm using the isapi_redirect.dll filter in IIS to redirect any request to
> *.jsp to Tomcat. (Works fine outside of the secure sections)
>
> Any ideas on how to correct this error.
>
> Paul
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

tomcat 4.1.12 hangs on HP-UX

[Pfingstl Gernot]

My tomcat hangs after around 30 requests to my struts-servlet. Tomcat doesn't write 
anything to some log (I had also set debug in server.xml) and doesn't shutdown (I had 
always to use kill -9 xx). I also looked to the garbage collector (JVM option 
-Xloggc:gc.log), but the heap size were about 64k (-Xmx was set to 300m). The 
responses are delayed about 5 to 10 seconds, because there must be fetched some data 
via OJB. If I do a JMeter test with the tomcat ROOT page (which has practically no 
delay), tomcat hangs after 5 requests.

Does anybody have any suggestions what to do or where the problem can be?

My configuration: tomcat 4.1.12 on HP-UX with jdk 1.4.1.00:
I tried with standard jvm opts, with
CATALINA_OPTS="-client -d64 -Xms30m -Xmx300m -Xincgc"
and
CATALINA_OPTS="-server -d64 -Xms30m -Xmx300m -Xincgc"
and
CATALINA_OPTS="-client -d64 -Xms30m -Xmx300m"

My connector:


Thank you,
Gernot

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat 4.1.12 Form authentication with IIS 5

[Sean Dockery]

What happens when you move your form-login-page outside of the /admin/
folder?

Sean Dockery
[EMAIL PROTECTED]
Certified Java Web Component Developer
Certified Delphi Programmer
SBD Consultants
http://www.sbdconsultants.com
- Original Message -
From: "Paul Bothma" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 13, 2003 06:11
Subject: Tomcat 4.1.12 Form authentication with IIS 5


> Hi,
>
> I'm using Tomcat 4.1.12 with IIS 5. When I connect directly to
> http://localhost:8080/HP/admin/ the Tomcat FORM authentication works fine,
> but when I try to connect to http://localhost/HP/admin I get the following
> error:
>
> HTTP Status 403 - Access to the requested resource has been denied
>
> --
--
> 
>
> type Status report
>
> message Access to the requested resource has been denied
>
> description Access to the specified resource (Access to the requested
> resource has been denied) has been forbidden.
>
>
> ----------
--
> 
>
> Apache Tomcat/4.1.12
>
> Here is the relevant extract from my web.xml file:
>
> 
>   HP Administration
>   
>  Protected Area
>  /admin/*
>   
>   
>  HP_admin
>   
> 
>
> 
>   FORM
>   users
>   
> /admin/login.jsp
> /error.html
>   
> 
>
>
> 
> 
>   HP_admin
> 
>
> I'm using the isapi_redirect.dll filter in IIS to redirect any request to
> *.jsp to Tomcat. (Works fine outside of the secure sections)
>
> Any ideas on how to correct this error.
>
> Paul
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF

[Mike Jackson]

I usally put the clean up in the finally block personally, something like
this:

Connection con = null;
PreparedStatement ps  = null;
ResultSet rs = null;

try {
con = getConnection();
PreparedStatement ps = con.prepareStatement( "select systime from 
dual" );
ResultSet rs = ps.executeQuery();
if ( rs.next() ) {
System.out.println( "Now=" + rs.String( 1 );
}
}
catch( SQLException e ) {
// do somethign
}
finally {
if ( rs != null ) {
try { rs.close(); } catch( Exception e ) {}
}
if ( ps != null ) {
try { ps.close(); } catch( Exception e ) {}
}
if ( con != null ) {
try { con.close(); } catch( Exception e ) {}
}
}

But your results may vary, batteries not included, some assembly required...

--mikej
-=-
mike jackson
[EMAIL PROTECTED]

> -Original Message-
> From: Paul French [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 13, 2003 8:47 AM
> To: 'Tomcat Users List'
> Subject: RE: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons
> BDSF
>
>
> The pool manager won't close a connection being used.
>
> I use oracle jdbc and I have found if I do the following I do not get any
> problems
>
> During the doGet or doPost
>
> {
> try {
>
>   Get a connection from the pool
>
>   Prepare a statement
>   Execute and get a result set
>
>   Close the result set when finished (I read somewhere Oracle can't
> guarantee to clean up all cursors if you simply close the
> prepared statement
> although most of the time it does)
>
>   Close the prepared statement
>
>   }
>   catch (SQLExceptions e)
>   {
> Check all result sets and prepared statements are closed (need to put
> try blocks around each in case of further sql exceptions - simply
> ignore the
> exception)
>   }
>   finally {
> // return the connection to the pool
> if (conn!= null) {
>   try
>   {
> conn.close();
>   }
>   catch (SQLException ignore){}
> }
>   }
>
>
> Like your self I would be interested in any documentation on the Commons
> database pool manager.
>
>
> -Original Message-
> From: Chakravarthy, Sundar [mailto:[EMAIL PROTECTED]]
> Sent: 13 February 2003 16:03
> To: Tomcat Users List
> Subject: RE: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF
>
> Could you tell me how to force Tomcat to  close connections sooner ?
>
> Also where can I find the documentation for all the parameters I could
> set in the xml file ?
>
> Another question:
>
> Say I have the following statements,
>
>
> 1 System.out.println("Creating connection.");
> 2 conn = dataSource.getConnection();
> 3 System.out.println("Creating statement.");
> 4 stmt = conn.createStatement();
>
> What prevents the Pool Manager from closing the connection in line 2
> before line 4 is reached ?
>
> Thanks,
> Sundar
>
> -Original Message-
> From: Robert Dana [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 05, 2003 1:16 PM
> To: [EMAIL PROTECTED]
> Subject: Re: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons
> BDSF
>
> Not sure if this is any help, but I do have some related information.  I
> believe the problems you are experiencing relate directly to a known bug
> in the Oracle JDBC drivers.  In my case, I found that using a
> PreparedStatement object in a servlet resulted in 2 or 3 (depending on
> the complexity of the statement) "overhead" cursors being opened by
> Oracle.  These cursors did not close, even when the PreparedStatement
> itself was closed in my code.  The orphan cursors only seemed to close
> if the connection itself was closed -  a major problem if one is trying
> to use any kind of efficient connection pooling.  This problem has been
> acknowledged by Oracle, but they have not, to my knowledge, fixed it.
> For me, the best solution was to "de-tune" my connection pool to force
> connections to be closed sooner than I normally would, in combination
> with setting a very high value for MAXCURSORS in the init.ora file.
> After some experimentation, I found a combination of those 2 factors
> that resulted in no more "maximum open cursors" errors, with only a
> modest degradation in performance.  A compromise solution to be sure,
> but one that worked out OK for me.
>
> I hope 

RE: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF

[Paul French]

The pool manager won't close a connection being used.

I use oracle jdbc and I have found if I do the following I do not get any
problems

During the doGet or doPost

{
try {

  Get a connection from the pool

  Prepare a statement
  Execute and get a result set

  Close the result set when finished (I read somewhere Oracle can't
guarantee to clean up all cursors if you simply close the prepared statement
although most of the time it does)

  Close the prepared statement

  }
  catch (SQLExceptions e)
  {
Check all result sets and prepared statements are closed (need to put
try blocks around each in case of further sql exceptions - simply ignore the
exception)
  }
  finally {
// return the connection to the pool
if (conn!= null) {
  try
  {
conn.close();
  }
  catch (SQLException ignore){}
}
  }


Like your self I would be interested in any documentation on the Commons
database pool manager.


-Original Message-
From: Chakravarthy, Sundar [mailto:[EMAIL PROTECTED]] 
Sent: 13 February 2003 16:03
To: Tomcat Users List
Subject: RE: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF

Could you tell me how to force Tomcat to  close connections sooner ?

Also where can I find the documentation for all the parameters I could
set in the xml file ?

Another question:

Say I have the following statements,


1 System.out.println("Creating connection.");
2 conn = dataSource.getConnection();
3 System.out.println("Creating statement.");
4 stmt = conn.createStatement();

What prevents the Pool Manager from closing the connection in line 2
before line 4 is reached ?

Thanks,
Sundar

-Original Message-
From: Robert Dana [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 05, 2003 1:16 PM
To: [EMAIL PROTECTED]
Subject: Re: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons
BDSF

Not sure if this is any help, but I do have some related information.  I
believe the problems you are experiencing relate directly to a known bug
in the Oracle JDBC drivers.  In my case, I found that using a
PreparedStatement object in a servlet resulted in 2 or 3 (depending on
the complexity of the statement) "overhead" cursors being opened by
Oracle.  These cursors did not close, even when the PreparedStatement
itself was closed in my code.  The orphan cursors only seemed to close
if the connection itself was closed -  a major problem if one is trying
to use any kind of efficient connection pooling.  This problem has been
acknowledged by Oracle, but they have not, to my knowledge, fixed it.
For me, the best solution was to "de-tune" my connection pool to force
connections to be closed sooner than I normally would, in combination
with setting a very high value for MAXCURSORS in the init.ora file.
After some experimentation, I found a combination of those 2 factors
that resulted in no more "maximum open cursors" errors, with only a
modest degradation in performance.  A compromise solution to be sure,
but one that worked out OK for me.

I hope that is useful information.

Robert Dana

-Original Message-
From: "Tam, Michael" <[EMAIL PROTECTED]>
To: 'Tomcat Users List' <[EMAIL PROTECTED]>
Date: Tue, 4 Feb 2003 18:48:16 -0500 
Subject: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF

Maybe you can post a segment of the code or example to illustrate your
problem.

Michael

-Original Message-
From: Andy Meadows [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 2:25 PM
To: Tomcat Users List
Subject: Re: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF


Doing that.

Actually, further testing reveals that the problem occurs with the
statement.  If an exception occurs while the statement is being
prepared,
then an exception is thrown.  However, it would appear that this
exception
is thrown after a cursor is opened (internally) and that cursor is never
closed.  A call to close on the statement in turn throws a NPE because a
value was never assigned to it.  Thus, I'm left with an open cursor on
an
object that I can't reach.

Can anyone else validate this?

Andy



- Original Message -
From: "Tam, Michael" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
Sent: Tuesday, February 04, 2003 4:22 PM
Subject: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF


> Have seen this problem before.
> It is the JDBC code.  The best solution is to explicitly close
RESULTSET,
> STATEMENT (of any kind), and CONNECTION as soon as you finished using
the
> object ( or else close them in the FINALLY block)
>
> Regards,
> Michael
>
> -Original Message-
> From: Sean Dockery [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 04, 2003 1:04 PM
> To: Tomcat Users List
> Subject: Re: Orac

RE: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF

[Chakravarthy, Sundar]

Could you tell me how to force Tomcat to  close connections sooner ?

Also where can I find the documentation for all the parameters I could
set in the xml file ?

Another question:

Say I have the following statements,


1 System.out.println("Creating connection.");
2 conn = dataSource.getConnection();
3 System.out.println("Creating statement.");
4 stmt = conn.createStatement();

What prevents the Pool Manager from closing the connection in line 2
before line 4 is reached ?

Thanks,
Sundar

-Original Message-
From: Robert Dana [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 05, 2003 1:16 PM
To: [EMAIL PROTECTED]
Subject: Re: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons
BDSF

Not sure if this is any help, but I do have some related information.  I
believe the problems you are experiencing relate directly to a known bug
in the Oracle JDBC drivers.  In my case, I found that using a
PreparedStatement object in a servlet resulted in 2 or 3 (depending on
the complexity of the statement) "overhead" cursors being opened by
Oracle.  These cursors did not close, even when the PreparedStatement
itself was closed in my code.  The orphan cursors only seemed to close
if the connection itself was closed -  a major problem if one is trying
to use any kind of efficient connection pooling.  This problem has been
acknowledged by Oracle, but they have not, to my knowledge, fixed it.
For me, the best solution was to "de-tune" my connection pool to force
connections to be closed sooner than I normally would, in combination
with setting a very high value for MAXCURSORS in the init.ora file.
After some experimentation, I found a combination of those 2 factors
that resulted in no more "maximum open cursors" errors, with only a
modest degradation in performance.  A compromise solution to be sure,
but one that worked out OK for me.

I hope that is useful information.

Robert Dana

-Original Message-
From: "Tam, Michael" <[EMAIL PROTECTED]>
To: 'Tomcat Users List' <[EMAIL PROTECTED]>
Date: Tue, 4 Feb 2003 18:48:16 -0500 
Subject: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF

Maybe you can post a segment of the code or example to illustrate your
problem.

Michael

-Original Message-
From: Andy Meadows [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 2:25 PM
To: Tomcat Users List
Subject: Re: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF


Doing that.

Actually, further testing reveals that the problem occurs with the
statement.  If an exception occurs while the statement is being
prepared,
then an exception is thrown.  However, it would appear that this
exception
is thrown after a cursor is opened (internally) and that cursor is never
closed.  A call to close on the statement in turn throws a NPE because a
value was never assigned to it.  Thus, I'm left with an open cursor on
an
object that I can't reach.

Can anyone else validate this?

Andy



- Original Message -
From: "Tam, Michael" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
Sent: Tuesday, February 04, 2003 4:22 PM
Subject: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF


> Have seen this problem before.
> It is the JDBC code.  The best solution is to explicitly close
RESULTSET,
> STATEMENT (of any kind), and CONNECTION as soon as you finished using
the
> object ( or else close them in the FINALLY block)
>
> Regards,
> Michael
>
> -Original Message-----
> From: Sean Dockery [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 04, 2003 1:04 PM
> To: Tomcat Users List
> Subject: Re: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF
>
>
> Try explicitly closing your ResultSet variables as well.  See if the
> problem persists.
>
> At 13:58 2003-02-04, you wrote:
> >Configuring Tomcat to provide a JNDI connection pool was no problem.
Now,
> >however, we are getting error ORA-01000: maximum cursors opened.
Logging
> >shows that any statement and connection that is opened is again
closed
> >which, according to everything I read, release the cursors.  This is
> >obviously not the case.
> >
> >Has anyone else experienced this problem and, if so, what was the
> >resolution -- other than increasing opened cursor counts.
> >
> >Andy Meadows
> >
> >
> >-
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
>
> Sean Dockery
> [EMAIL PROTECTED]
> Certified Java Web Component Developer
> Certified Delphi Programmer
> SBD Consultants
> http://www.sbdconsultants.com
>
>
>
> 

AW: Does addressing JSPs under WEB-INF/jsp work with Tomcat 4.1.12

[Cebron, Yann]

Hello,

> I read a few hints and tricks on how to make a web 
> application a little more
> secure.
> As I am using Struts right now I decided to put all JSPs 
> under WEB-INF/jsp
^^^

> which (AFAIK) should work for JSP/Servlet spec 2.3.
> Now everytime I try to forward from the (Struts) servlet to a 
> jsp somewhere
> under WEB-INF/jsp I get a 404 errorcode telling me that e.g. 
> "The requested
> resource (/psa/WEB-INF/test.jsp) is not available."
 ^^^

Seems like you're missing your subdir "/jsp/" in your forwards

You can also put all your JSP pages e.g. in /webapp/s/ and define a 
security-constraint on "/s/*" in your web.xml with *no* assigned roles, so nobody can 
access your JSP-pages directly.

Snippet:
**



JSP

/s/*









BASIC
No access

**

Greetings,
Yann

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Does addressing JSPs under WEB-INF/jsp work with Tomcat 4.1.12

[Sebastian Schär]

Hi there,

I read a few hints and tricks on how to make a web application a little more
secure.
As I am using Struts right now I decided to put all JSPs under WEB-INF/jsp
which (AFAIK) should work for JSP/Servlet spec 2.3.
Now everytime I try to forward from the (Struts) servlet to a jsp somewhere
under WEB-INF/jsp I get a 404 errorcode telling me that e.g. "The requested
resource (/psa/WEB-INF/test.jsp) is not available."
Is there anything I have to do like e.g. specifically allow forwards to
WEB-INF/jsp or something?

Thanks for any help


Sebastian



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat 4.1.12 Form authentication with IIS 5

[Paul Bothma]

Hi,

I'm using Tomcat 4.1.12 with IIS 5. When I connect directly to
http://localhost:8080/HP/admin/ the Tomcat FORM authentication works fine,
but when I try to connect to http://localhost/HP/admin I get the following
error:

HTTP Status 403 - Access to the requested resource has been denied




type Status report

message Access to the requested resource has been denied

description Access to the specified resource (Access to the requested
resource has been denied) has been forbidden.





Apache Tomcat/4.1.12

Here is the relevant extract from my web.xml file:


  HP Administration
  
 Protected Area
 /admin/*
  
  
 HP_admin
  



  FORM
  users
  
/admin/login.jsp
/error.html
  





  HP_admin


I'm using the isapi_redirect.dll filter in IIS to redirect any request to
*.jsp to Tomcat. (Works fine outside of the secure sections)

Any ideas on how to correct this error.

Paul


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: pager taglib not working after migrating to tomcat 4.1.12 from tomcat 4.0.4

[THG]

i have a similar problem with a custom taglib.
it works under tomcat 3.x but not under tomcat 4.x.
what changed between jsp 1.1 and jsp 1.2?

thanks,
sincerly Thorsten


On Wed, 12 Feb 2003 23:57:52  
 James Klicman wrote:
>Hi Ashish,
>
>You will want to upgrade to version 2.0 of the Pager tag library. It
>is compatible with JSP 1.2 and Tomcat 4.1.12.
>
>-James
>
>On Wed, Feb 12, 2003 at 04:37:42PM -0800, Ashish Kulkarni wrote:
>> Hi,
>> 
>> I have been using the pager tag lib from
>> http://jsptags.com/tags/navigation/pager/index.jsp
>> for controling the number of records to be displayed
>> on each JSP,
>> It was working fine on tomcat4.0.4, but since i
>> migrated to tomcat4.1.12, it is not working
>> I get 10 records on first page, but nothing on next
>> where as there are 45 records in file
>> 
>> hAs any one got this problem??
>> need help
>> Ashish
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>


_
Get 25MB, POP3, Spam Filtering with LYCOS MAIL PLUS for $19.95/year.
http://login.mail.lycos.com/brandPage.shtml?pageId=plus&ref=lmtplus

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: pager taglib not working after migrating to tomcat 4.1.12 from tomcat 4.0.4

[James Klicman]

Hi Ashish,

You will want to upgrade to version 2.0 of the Pager tag library. It
is compatible with JSP 1.2 and Tomcat 4.1.12.

-James

On Wed, Feb 12, 2003 at 04:37:42PM -0800, Ashish Kulkarni wrote:
> Hi,
> 
> I have been using the pager tag lib from
> http://jsptags.com/tags/navigation/pager/index.jsp
> for controling the number of records to be displayed
> on each JSP,
> It was working fine on tomcat4.0.4, but since i
> migrated to tomcat4.1.12, it is not working
> I get 10 records on first page, but nothing on next
> where as there are 45 records in file
> 
> hAs any one got this problem??
> need help
> Ashish

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

pager taglib not working after migrating to tomcat 4.1.12 from tomcat 4.0.4

[Ashish Kulkarni]

Hi,

I have been using the pager tag lib from
http://jsptags.com/tags/navigation/pager/index.jsp
for controling the number of records to be displayed
on each JSP,
It was working fine on tomcat4.0.4, but since i
migrated to tomcat4.1.12, it is not working
I get 10 records on first page, but nothing on next
where as there are 45 records in file

hAs any one got this problem??
need help
Ashish

__
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF

[Robert Dana]

Not sure if this is any help, but I do have some related information.  I believe the 
problems you are experiencing relate directly to a known bug in the Oracle JDBC 
drivers.  In my case, I found that using a PreparedStatement object in a servlet 
resulted in 2 or 3 (depending on the complexity of the statement) "overhead" cursors 
being opened by Oracle.  These cursors did not close, even when the PreparedStatement 
itself was closed in my code.  The orphan cursors only seemed to close if the 
connection itself was closed -  a major problem if one is trying to use any kind of 
efficient connection pooling.  This problem has been acknowledged by Oracle, but they 
have not, to my knowledge, fixed it.  For me, the best solution was to "de-tune" my 
connection pool to force connections to be closed sooner than I normally would, in 
combination with setting a very high value for MAXCURSORS in the init.ora file.  After 
some experimentation, I found a combination of those 2 factors that resulted in no 
more "maximum open cursors" errors, with only a modest degradation in performance.  A 
compromise solution to be sure, but one that worked out OK for me.

I hope that is useful information.

Robert Dana

-Original Message-
From: "Tam, Michael" <[EMAIL PROTECTED]>
To: 'Tomcat Users List' <[EMAIL PROTECTED]>
Date: Tue, 4 Feb 2003 18:48:16 -0500 
Subject: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF

Maybe you can post a segment of the code or example to illustrate your
problem.

Michael

-Original Message-
From: Andy Meadows [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 2:25 PM
To: Tomcat Users List
Subject: Re: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF


Doing that.

Actually, further testing reveals that the problem occurs with the
statement.  If an exception occurs while the statement is being prepared,
then an exception is thrown.  However, it would appear that this exception
is thrown after a cursor is opened (internally) and that cursor is never
closed.  A call to close on the statement in turn throws a NPE because a
value was never assigned to it.  Thus, I'm left with an open cursor on an
object that I can't reach.

Can anyone else validate this?

Andy



- Original Message -
From: "Tam, Michael" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
Sent: Tuesday, February 04, 2003 4:22 PM
Subject: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF


> Have seen this problem before.
> It is the JDBC code.  The best solution is to explicitly close RESULTSET,
> STATEMENT (of any kind), and CONNECTION as soon as you finished using the
> object ( or else close them in the FINALLY block)
>
> Regards,
> Michael
>
> -Original Message-
> From: Sean Dockery [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 04, 2003 1:04 PM
> To: Tomcat Users List
> Subject: Re: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF
>
>
> Try explicitly closing your ResultSet variables as well.  See if the
> problem persists.
>
> At 13:58 2003-02-04, you wrote:
> >Configuring Tomcat to provide a JNDI connection pool was no problem.
Now,
> >however, we are getting error ORA-01000: maximum cursors opened.  Logging
> >shows that any statement and connection that is opened is again closed
> >which, according to everything I read, release the cursors.  This is
> >obviously not the case.
> >
> >Has anyone else experienced this problem and, if so, what was the
> >resolution -- other than increasing opened cursor counts.
> >
> >Andy Meadows
> >
> >
> >-
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
>
> Sean Dockery
> [EMAIL PROTECTED]
> Certified Java Web Component Developer
> Certified Delphi Programmer
> SBD Consultants
> http://www.sbdconsultants.com
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


a>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> --


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat 4.1.12 available on HP-UX

[PELOQUIN,JEFFREY (HP-Boise,ex1)]

For those of you using Tomcat on an HP-UX machine

HP appears to have finally bundled Tomcat 4.1.12 into its Apache/Tomcat
depot file

for more info see
http://www.software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo
.pl?productNumber=HPUXWSSUITE

Jeff

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF

[Tam, Michael]

Maybe you can post a segment of the code or example to illustrate your
problem.

Michael

-Original Message-
From: Andy Meadows [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 2:25 PM
To: Tomcat Users List
Subject: Re: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF


Doing that.

Actually, further testing reveals that the problem occurs with the
statement.  If an exception occurs while the statement is being prepared,
then an exception is thrown.  However, it would appear that this exception
is thrown after a cursor is opened (internally) and that cursor is never
closed.  A call to close on the statement in turn throws a NPE because a
value was never assigned to it.  Thus, I'm left with an open cursor on an
object that I can't reach.

Can anyone else validate this?

Andy



- Original Message -
From: "Tam, Michael" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
Sent: Tuesday, February 04, 2003 4:22 PM
Subject: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF


> Have seen this problem before.
> It is the JDBC code.  The best solution is to explicitly close RESULTSET,
> STATEMENT (of any kind), and CONNECTION as soon as you finished using the
> object ( or else close them in the FINALLY block)
>
> Regards,
> Michael
>
> -Original Message-
> From: Sean Dockery [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 04, 2003 1:04 PM
> To: Tomcat Users List
> Subject: Re: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF
>
>
> Try explicitly closing your ResultSet variables as well.  See if the
> problem persists.
>
> At 13:58 2003-02-04, you wrote:
> >Configuring Tomcat to provide a JNDI connection pool was no problem.
Now,
> >however, we are getting error ORA-01000: maximum cursors opened.  Logging
> >shows that any statement and connection that is opened is again closed
> >which, according to everything I read, release the cursors.  This is
> >obviously not the case.
> >
> >Has anyone else experienced this problem and, if so, what was the
> >resolution -- other than increasing opened cursor counts.
> >
> >Andy Meadows
> >
> >
> >-
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
>
> Sean Dockery
> [EMAIL PROTECTED]
> Certified Java Web Component Developer
> Certified Delphi Programmer
> SBD Consultants
> http://www.sbdconsultants.com
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF

[Andy Meadows]

Doing that.

Actually, further testing reveals that the problem occurs with the
statement.  If an exception occurs while the statement is being prepared,
then an exception is thrown.  However, it would appear that this exception
is thrown after a cursor is opened (internally) and that cursor is never
closed.  A call to close on the statement in turn throws a NPE because a
value was never assigned to it.  Thus, I'm left with an open cursor on an
object that I can't reach.

Can anyone else validate this?

Andy



- Original Message -
From: "Tam, Michael" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
Sent: Tuesday, February 04, 2003 4:22 PM
Subject: RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF


> Have seen this problem before.
> It is the JDBC code.  The best solution is to explicitly close RESULTSET,
> STATEMENT (of any kind), and CONNECTION as soon as you finished using the
> object ( or else close them in the FINALLY block)
>
> Regards,
> Michael
>
> -Original Message-
> From: Sean Dockery [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 04, 2003 1:04 PM
> To: Tomcat Users List
> Subject: Re: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF
>
>
> Try explicitly closing your ResultSet variables as well.  See if the
> problem persists.
>
> At 13:58 2003-02-04, you wrote:
> >Configuring Tomcat to provide a JNDI connection pool was no problem.
Now,
> >however, we are getting error ORA-01000: maximum cursors opened.  Logging
> >shows that any statement and connection that is opened is again closed
> >which, according to everything I read, release the cursors.  This is
> >obviously not the case.
> >
> >Has anyone else experienced this problem and, if so, what was the
> >resolution -- other than increasing opened cursor counts.
> >
> >Andy Meadows
> >
> >
> >-
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
>
> Sean Dockery
> [EMAIL PROTECTED]
> Certified Java Web Component Developer
> Certified Delphi Programmer
> SBD Consultants
> http://www.sbdconsultants.com
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF

[Tam, Michael]

Have seen this problem before.
It is the JDBC code.  The best solution is to explicitly close RESULTSET,
STATEMENT (of any kind), and CONNECTION as soon as you finished using the
object ( or else close them in the FINALLY block)

Regards,
Michael

-Original Message-
From: Sean Dockery [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 1:04 PM
To: Tomcat Users List
Subject: Re: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF


Try explicitly closing your ResultSet variables as well.  See if the 
problem persists.

At 13:58 2003-02-04, you wrote:
>Configuring Tomcat to provide a JNDI connection pool was no problem.  Now,
>however, we are getting error ORA-01000: maximum cursors opened.  Logging
>shows that any statement and connection that is opened is again closed
>which, according to everything I read, release the cursors.  This is
>obviously not the case.
>
>Has anyone else experienced this problem and, if so, what was the
>resolution -- other than increasing opened cursor counts.
>
>Andy Meadows
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]

Sean Dockery
[EMAIL PROTECTED]
Certified Java Web Component Developer
Certified Delphi Programmer
SBD Consultants
http://www.sbdconsultants.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF

[Sean Dockery]

Try explicitly closing your ResultSet variables as well.  See if the 
problem persists.

At 13:58 2003-02-04, you wrote:
Configuring Tomcat to provide a JNDI connection pool was no problem.  Now,
however, we are getting error ORA-01000: maximum cursors opened.  Logging
shows that any statement and connection that is opened is again closed
which, according to everything I read, release the cursors.  This is
obviously not the case.

Has anyone else experienced this problem and, if so, what was the
resolution -- other than increasing opened cursor counts.

Andy Meadows


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Sean Dockery
[EMAIL PROTECTED]
Certified Java Web Component Developer
Certified Delphi Programmer
SBD Consultants
http://www.sbdconsultants.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Oracle cursor problem with Tomcat 4.1.12 and Commons BDSF

[Andy Meadows]

Configuring Tomcat to provide a JNDI connection pool was no problem.  Now,
however, we are getting error ORA-01000: maximum cursors opened.  Logging
shows that any statement and connection that is opened is again closed
which, according to everything I read, release the cursors.  This is
obviously not the case.

Has anyone else experienced this problem and, if so, what was the
resolution -- other than increasing opened cursor counts.

Andy Meadows


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: tomcat 4.1.12 ssl connector stop responding

[Mohamed Nasser]

I know there was a bug with the coyote connector for tomcat 4.1.12 as I configured 
with apache. I upgraded to 4.1.18 and I have had no problems.

-Original Message-
From: ing.Marco Baiguera [mailto:[EMAIL PROTECTED]]
Sent: Tue, February 04, 2003 5:09 AM
To: [EMAIL PROTECTED]
Subject: tomcat 4.1.12 ssl connector stop responding


i'm using tomcat 4.1.12 on jdsk 1.4.0 as a standalone server with coyote http 1.1 
connector 
having http (8080) connector accessible from internal lan only and https (8443) 
accessible from external hosts (natted to port 443)
after two-three days tomcat stops responding on the https connector (runs ok on http) 
without any exception or log trace.
any hint?
follows my connector configuration.
what about "useURIValidationHack" (can't find any documentation on this) ?
thank you

 
  


---
Ing. Marco Baiguera
Web Application Designer

T.C.TELECENTRAL s.r.l.
Via Fura, 10
25122 Brescia - Italy
Tel  +39 030 3510711
Int + 39 030 3510816
NB. Nel rispetto della legge sulla privacy è fatto  divieto di 
includere il presente indirizzo email in  CC, Forwards e Mailing list 
senza previa autorizzazione. In caso di violazione della suddetta 
richiesta sarete perseguiti legalmente.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

tomcat 4.1.12 ssl connector stop responding

[ing.Marco Baiguera]

i'm using tomcat 4.1.12 on jdsk 1.4.0 as a standalone server with coyote http 1.1 
connector 
having http (8080) connector accessible from internal lan only and https (8443) 
accessible from external hosts (natted to port 443)
after two-three days tomcat stops responding on the https connector (runs ok on http) 
without any exception or log trace.
any hint?
follows my connector configuration.
what about "useURIValidationHack" (can't find any documentation on this) ?
thank you

 
  


---
Ing. Marco Baiguera
Web Application Designer

T.C.TELECENTRAL s.r.l.
Via Fura, 10
25122 Brescia - Italy
Tel  +39 030 3510711
Int + 39 030 3510816
NB. Nel rispetto della legge sulla privacy è fatto  divieto di 
includere il presente indirizzo email in  CC, Forwards e Mailing list 
senza previa autorizzazione. In caso di violazione della suddetta 
richiesta sarete perseguiti legalmente.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat 4.1.12 - JK2 2.0.1 - IIS 5.0 & load balancing

[Warner Godfrey]

Hello,

Is load balancing supported by the JK2 ISAPI filter (isapi_redirect2.dll)?

If it is I am running into problems getting load balancing to work with IIS!
I have successfully load balanced a cluster of Tomcat servers using the JK2
module for Apache2, but wen I try and port my configuration over to IIS I
get the following error in the Event Viewer Application Log:


--
Event Type: Warning
Event Source: Apache Jakarta Connector2
Event Category: None
Event ID: 2
Date:  23/01/2003
Time:  2:07:15 PM
User:  N/A
Computer: TOMCAT1
Description:
Error: [jk_isapi_plugin.c (489)]: HttpExtensionProc worker is NULL
--


I am not sure if there are subtle differences between the Apache2 JK2 module
and the JK2 ISAPI filter for IIS 5.0, but it seems as soon as you try and
reference a load balanced group using the 'uri.group' property in the
workers2.properties configuration file, everything goes pear shaped.
However, if I disable load balancing and reference a worker directly from
the 'uri.group' property, everything works fine!


Can anyone explain the reason for this error? I have included my JK2
configuration below:


-- workers2.properties --
[shm:]
info=Shared memory file. Required for reconfiguration and status with
multiprocess servers
file=c:/tomcat/work/jk2.shm
size=100

[logger.file:0]
level=DEBUG
file=c:/tomcat/logs/iis_jk2.log

[lb:lb]
info=Declaration of a load balanced group.
debug=0

[channel.socket:tomcat1:8009]
info=Forwarding over socket connection to tomcat1 instance.
host=tomcat1
port=8009
lbfactor=1
group=lb
tomcatId=tomcat1:8009

[ajp13:tomcat1:8009]
info=Ajp13 worker, connects to tomcat1 instance using AJP 1.3 protocol.
channel=channel.socket:tomcat1:8009
tomcatId=tomcat1:8009

[channel.socket:tomcat2:8009]
info=Forwarding over socket connection to tomcat2 instance.
host=tomcat2
port=8009
lbfactor=1
group=lb
tomcatId=tomcat2:8009

[ajp13:tomcat2:8009]
info=Ajp13 worker, connects to tomcat2 instance using AJP 1.3 protocol.
channel=channel.socket:tomcat2:8009
tomcatId=tomcat2:8009

[uri:/loadbalancing/SessionTest.jsp]
info=Sample JSP to test load balancing.
context=/loadbalancing
group=lb
--


Finally, my configuration is:
- Windows 2000
- Tomcat 4.1.12
- JK2 ISAPI filter 2.0.1 (binary version downloaded from
<http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0
.1/bin/win32/isapi_redirector2.dll>)
- IIS 5.0



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Tomcat 4.1.12 - JK2 2.0.1 - IIS 5.0 & load balancing

[Warner Godfrey]

- Original Message -
From: "Warner Godfrey" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 23, 2003 2:31 PM
Subject: Tomcat 4.1.12 - JK2 2.0.1 - IIS 5.0 & load balancing


Hello,

Is load balancing supported by the JK2 ISAPI filter (isapi_redirect2.dll)?

If it is I am running into problems getting load balancing to work with IIS!
I have successfully load balanced a cluster of Tomcat servers using the JK2
module for Apache2, but wen I try and port my configuration over to IIS I
get the following error in the Event Viewer Application Log:


--
Event Type: Warning
Event Source: Apache Jakarta Connector2
Event Category: None
Event ID: 2
Date:  23/01/2003
Time:  2:07:15 PM
User:  N/A
Computer: TOMCAT1
Description:
Error: [jk_isapi_plugin.c (489)]: HttpExtensionProc worker is NULL
--


I am not sure if there are subtle differences between the Apache2 JK2 module
and the JK2 ISAPI filter for IIS 5.0, but it seems as soon as you try and
reference a load balanced group using the 'uri.group' property in the
workers2.properties configuration file, everything goes pear shaped.
However, if I disable load balancing and reference a worker directly from
the 'uri.group' property, everything works fine!


Can anyone explain the reason for this error? I have included my JK2
configuration below:


-- workers2.properties --
[shm:]
info=Shared memory file. Required for reconfiguration and status with
multiprocess servers
file=c:/tomcat/work/jk2.shm
size=100

[logger.file:0]
level=DEBUG
file=c:/tomcat/logs/iis_jk2.log

[lb:lb]
info=Declaration of a load balanced group.
debug=0

[channel.socket:tomcat1:8009]
info=Forwarding over socket connection to tomcat1 instance.
host=tomcat1
port=8009
lbfactor=1
group=lb
tomcatId=tomcat1:8009

[ajp13:tomcat1:8009]
info=Ajp13 worker, connects to tomcat1 instance using AJP 1.3 protocol.
channel=channel.socket:tomcat1:8009
tomcatId=tomcat1:8009

[channel.socket:tomcat2:8009]
info=Forwarding over socket connection to tomcat2 instance.
host=tomcat2
port=8009
lbfactor=1
group=lb
tomcatId=tomcat2:8009

[ajp13:tomcat2:8009]
info=Ajp13 worker, connects to tomcat2 instance using AJP 1.3 protocol.
channel=channel.socket:tomcat2:8009
tomcatId=tomcat2:8009

[uri:/loadbalancing/SessionTest.jsp]
info=Sample JSP to test load balancing.
context=/loadbalancing
group=lb
--


Finally, my configuration is:
- Windows 2000
- Tomcat 4.1.12
- JK2 ISAPI filter 2.0.1 (binary version downloaded from
<http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0
.1/bin/win32/isapi_redirector2.dll>)
- IIS 5.0




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

WebAppClassLoader / ProxyDirContext.java Problem - Upgrade from Tomcat 4.1.12 to 4.1.17

[Matt Small]

A few weeks back I noticed this problem when I upgraded from 4.1.12 to
4.1.17.  I wanted to track it down a little bit before reporting it, and now
I think I know where the problem is. I have isolated the problem to changes
made between CVS versions 1.12 and 1.14 of
org.apache.naming.resources.ProxyDirContext.java. These changes were made
between releases 4.1.12 and 4.1.14 of Tomcat by Remy.

My app dynamically generates java code (in a work dir), compiles it (to
WEB-INF/classes), and then loads it using Class.forName(). This has been
working smoothly and has been very stable for over a year now, way back from
when we were using early versions of tomcat 4 (possibly even in tomcat 3).

The basic algorithm is 

Class c;

public Class getClass() throws Exception{
  try{
c = Class.forName("generated.ClassName");
  }catch(ClassNotFoundException cnfe1){
try{
  generateJavaCodeAndCompile(); //compiles to WEB-INF/classes
  c = Class.forName("generated.ClassName");
  return c;
}catch(ClassNotFoundException cnfe2){
  ERROR class could not be loaded
  throw cnfe2;
}
  }
}

Note that when a lot of code has to be regenerated, it would take some time,
but it always worked without any trouble. Classes would generate and load in
the order requested by the application.

After upgrading to 4.1.17 I found that when many classes needed to be
generated and loaded, I would get tons of ClassNotFoundExceptions. Even
though my code was being compiled properly and the class was in the webapp
classes dir, the second call to Class.forName was sometimes throwing
ClassNotFoundExceptions.

After trying various combinations of Tomcat jars, I was able to Isolate the
problem to /common/lib/naming-resources.jar. Where the version from 4.1.12
works fine, but 4.1.14 fails. The only file that is different in that
particular jar was ProxyDirContext.java, so I am assuming the problem stems
from those changes.

Anybody have any idea about why this change causes this problem and what a
fix for this would be?

Thanks very much

Matt

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Cannot send cookies between webapps on Tomcat 4.1.12

[joel . dewitt]

I am running two webapps on Apache Tomcat/4.1.12, on Win2000, port 8080.
One is called "partners" the other "buildings."
I can reach partners through URL: "
http://mymachine.ny.mycompany.com:8080/partners";,
buildings through URL: "http://mymachine.ny.mycompany.com:8080/buildings";.

"Partners" creates a cookie:
...
Cookie aCookie = new Cookie( MY_COOKIE_KEY, aToken.toString() );
aCookie.setPath( "/" );  // deliver to all
directories not just issuer.
aCookie.setSecure( false );
aCookie.setMaxAge( -1 );// "per-session" cookie,
not stored on disk
theResponse.addCookie( aCookie );
...

"Buildings" looks for cookie, and cannot get it in Tomcat.  However,
it can in WebSphere 4.0.

Is the cookie set wrong, or is WebSphere not supposed to be delivering it
to the other app?

Thanks,
Joel



This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Cannot send cookies between webapps on Tomcat 4.1.12

[joel . dewitt]

I am running two webapps on Apache Tomcat/4.1.12, on Win2000, port 8080.
One is called "partners" the other "buildings."
I can reach partners through URL:
"http://mymachine.ny.mycompany.com:8080/partners";,
buildings through URL: "http://mymachine.ny.mycompany.com:8080/buildings";.

"Partners" creates a cookie:
...
Cookie aCookie = new Cookie( MY_COOKIE_KEY, aToken.toString() );
aCookie.setPath( "/" );  // deliver to all
directories not just issuer.
aCookie.setSecure( false );
aCookie.setMaxAge( -1 );// "per-session" cookie,
not stored on disk
theResponse.addCookie( aCookie );
...

"Buildings" looks for cookie, and cannot get it in Tomcat.  However,
it can in WebSphere 4.0.

Is the cookie set wrong, or is WebSphere not supposed to be delivering it
to the other app?

Thanks,
Joel




This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Problems using Tomcat 4.1.12-LE-jdk14 HTTPServlet.log(java.lang.String)

[Thomas B. Holdren]

Greetings,

I have scoured the web/mailing lists all day and have had no luck with
this.

I have a singular servlet in a test context that runs fine until I put
in an HTTPServlet.log(java.lang.String) statement in the servlet's
init() method.  I just want to log a string when the servlet init()'s.
Following is the error message from Tomcat and the configuration of the 
context.

Thanks in advance to anyone who can help.

Sincerely,

Thomas B. Holdren, Developer

System:
RedHat Linux 7.3
Tomcat 4.1.12-LE-jdk14
j2sdk1.4.1_01

Error message:
java.lang.NullPointerException
at 
javax.servlet.GenericServlet.getServletContext(GenericServlet.java:204)
at javax.servlet.GenericServlet.log(GenericServlet.java:298)
at Fred.doGet(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.catalina.servlets.InvokerServlet.serveRequest(InvokerServlet.java:458)
at 
org.apache.catalina.servlets.InvokerServlet.doGet(InvokerServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2396)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at 
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:405)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:380)
at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:533)
at java.lang.Thread.run(Thread.java:536)

Relevant server.xml entry:

  
  prefix="localhost_jobb_log." suffix=".txt" timestamp="true" />


web.xml web-app section:
Java Object Bulletin Board

  invoker
  /servlet/*



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Apache 2.0 + Tomcat 4.1.12 + Realms + Java WebStart don't work

[Antonio Vázquez]

Holger,

I think that the problems was in the spanish and special characters "ñó()"
in the descriptions.

Thanks for your help

Antonio Vázquez
[EMAIL PROTECTED]
www.winsoftsystems.com

- Original Message -
From: "Stratmann, Holger" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
Sent: Tuesday, January 14, 2003 6:09 PM
Subject: AW: Apache 2.0 + Tomcat 4.1.12 + Realms + Java WebStart don't work


I was using Tomcat 4.1 with JavaWebStart (JWS) and it worked fine!

Does your realm work ok? IOW: Can you call html/jsp-pages which are access
protected?
Try calling a page that is in the same directory as the JNLP.

Also:
Which version of JavaWebStart are you using?
If you say: "the system" is unable to load the JNLP file, do you mean the
browser or do you mean JavaWebStart?
Do you use BASIC or form-based authentication? I use BASIC and I'm not sure
if (and how!) form-based could work...
(I was happy to see that JavaWebStart supported BASIC :-)

Let us know...
   Holger

Btw: As a hint for everybody who's using authentication w/ JavaWebStart:
I found it quite annoying to enter username/password every time I launch the
application (!!), just because JWS wants to check for updates. When you
press "Cancel" ("No, I don't want to check for updates..."), JWS does not
launch the application.
Then I found out that JWS uses the HEAD-method to check if files were
modified. GREAT!! You can use access-protection for everything but HEAD and
you're prompted for the password only if an update is available on the
server (which is usually a cool method...)

> -Ursprüngliche Nachricht-
> Von: Antonio Vázquez [mailto:[EMAIL PROTECTED]]
> Gesendet: Dienstag, 14. Januar 2003 17:46
> An: Tomcat
> Betreff: Apache 2.0 + Tomcat 4.1.12 + Realms + Java WebStart
> don't work
>
>
> I have a little problem with Apache 2.0 + Tomcat 4.1.2 using
> JDBC Realms and
> Java WebStart.
>
> If i configure the web application a call the JNLP file, all
> works, but when
> I include  a REALM, the system is unable to load de JNLP file.
>
> I made several test and I am sure that the problem is when
> you use realm
> logins.
>
> Any idea?
>
> Thanks
> Antonio Vázquez
> [EMAIL PROTECTED]
> www.winsoftsystems.com
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>





--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

AW: Apache 2.0 + Tomcat 4.1.12 + Realms + Java WebStart don't work

[Stratmann, Holger]

I was using Tomcat 4.1 with JavaWebStart (JWS) and it worked fine!

Does your realm work ok? IOW: Can you call html/jsp-pages which are access
protected?
Try calling a page that is in the same directory as the JNLP.

Also: 
Which version of JavaWebStart are you using?
If you say: "the system" is unable to load the JNLP file, do you mean the
browser or do you mean JavaWebStart?
Do you use BASIC or form-based authentication? I use BASIC and I'm not sure
if (and how!) form-based could work...
(I was happy to see that JavaWebStart supported BASIC :-)

Let us know...
   Holger

Btw: As a hint for everybody who's using authentication w/ JavaWebStart:
I found it quite annoying to enter username/password every time I launch the
application (!!), just because JWS wants to check for updates. When you
press "Cancel" ("No, I don't want to check for updates..."), JWS does not
launch the application.
Then I found out that JWS uses the HEAD-method to check if files were
modified. GREAT!! You can use access-protection for everything but HEAD and
you're prompted for the password only if an update is available on the
server (which is usually a cool method...)

> -Ursprüngliche Nachricht-
> Von: Antonio Vázquez [mailto:[EMAIL PROTECTED]]
> Gesendet: Dienstag, 14. Januar 2003 17:46
> An: Tomcat
> Betreff: Apache 2.0 + Tomcat 4.1.12 + Realms + Java WebStart 
> don't work
> 
> 
> I have a little problem with Apache 2.0 + Tomcat 4.1.2 using 
> JDBC Realms and
> Java WebStart.
> 
> If i configure the web application a call the JNLP file, all 
> works, but when
> I include  a REALM, the system is unable to load de JNLP file.
> 
> I made several test and I am sure that the problem is when 
> you use realm
> logins.
> 
> Any idea?
> 
> Thanks
> Antonio Vázquez
> [EMAIL PROTECTED]
> www.winsoftsystems.com
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: 
> <mailto:[EMAIL PROTECTED]>
> 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Apache 2.0 + Tomcat 4.1.12 + Realms + Java WebStart don't work

[Antonio Vázquez]

I have a little problem with Apache 2.0 + Tomcat 4.1.2 using JDBC Realms and
Java WebStart.

If i configure the web application a call the JNLP file, all works, but when
I include  a REALM, the system is unable to load de JNLP file.

I made several test and I am sure that the problem is when you use realm
logins.

Any idea?

Thanks
Antonio Vázquez
[EMAIL PROTECTED]
www.winsoftsystems.com


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Tomcat 4.1.12 Directory Listing

[Venkateshwar Bommineni]

> I would like to use default tomcat directory listing functionality in
> one of my application. Following is the context added to server.xml
> configuration.
> 
> path="/directory" docBase="C:\application\data" debug="0">
>className="org.apache.naming.resources.FileDirContext"
> allowLinking="true" caseSensitive="false" />
> 
> 
> 1). This works fine on UNIX based systems but on Win2K box its causing
> this error at tomcat startup time:
> "java.lang.reflect.InvocationTargetException:
> java.lang.IllegalArgumentException: Document base
> ..\C:\application\data does not exist or is not a readable directory"
> What could be the reason and is there any magic flag need to be set?
> 
> 2). Is it possible to configure default Tomcat' s directory listing
> functionality to extend like to show our own file timestamps, images
> etc. I noticed that this whole default directory listing
> implementation is hard coded in the
> "org/apache/catalina/servlets/DefaultServlet.java" class. So is it
> advisable to extend this servlet class or some other tomcat source
> code? what's the other options I can look for?
> 
Pl somebody help me. thanks in advance..
> --Venkat
> 

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Tomcat 4.1.12 Directory Listing

[Venkateshwar Bommineni]

I would like to use default tomcat directory listing functionality in
one of my application. Following is the context added to server.xml
configuration.

   



1). This works fine on UNIX based systems but on Win2K box its causing
this error at tomcat startup time:
"java.lang.reflect.InvocationTargetException:
java.lang.IllegalArgumentException: Document base ..\C:\application\data
does not exist or is not a readable directory"
What could be the reason and is there any magic flag need to be set?

2). Is it possible to configure default Tomcats directory listing
functionality to extend like to show our own file timestamps, images
etc. I noticed that this whole default directory listing implementation
is hard coded in the "org/apache/catalina/servlets/DefaultServlet.java"
class. So is it advisable to extend this servlet class or some other
tomcat source code? what's the other options I can look for?

 thanks in advance..
--Venkat


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: tomcat 4.1.12 :: connection refused :: missing

[Craig R. McClanahan]

On Thu, 9 Jan 2003, João Luiz de Brito Macaíba wrote:

> Date: Thu, 9 Jan 2003 17:06:19 -0200 (EDT)
> From: João Luiz de Brito Macaíba <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: tomcat 4.1.12 :: connection refused :: missing  ...
>
> Hi,
>
>   I'm running tomcat 4.1.12 in FreeBSD 4.7. Looking inside
> server.xml I cannot find  neither a explicit bind to 8080.
>

 is a Tomcat 3.3 thing.  Be sure that you're looking at
the docs for integrating Tomcat 4.1 if that's what you're using.

>   Since I installed I am not able to get http://localhost:8080. All
> I get is a "connection refused message".
>

That's what you would get if Tomcat were not started.

>   Does anyone have any idea ?
>
> Thanks in advance,
> Macaíba.
>

Craig


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

tomcat 4.1.12 :: connection refused :: missing

[João Luiz de Brito Macaíba]

Hi,

I'm running tomcat 4.1.12 in FreeBSD 4.7. Looking inside
server.xml I cannot find  neither a explicit bind to 8080.

Since I installed I am not able to get http://localhost:8080. All
I get is a "connection refused message".

Does anyone have any idea ?

Thanks in advance,
Macaíba.


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Question about Tomcat 4.1.12 WebDAV application

[Andreas Probst]

Hi Jim,

it might be that Windows cached your credentials. You could try 
Slide client (jakarta sub project Slide), which requires to type 
in the credentials everytime you start it.
You won't need to start the Slide server or the included Tomcat, 
just the client at pathTo\jakarta-slide-
1.0.16\client\bin\run.bat. (It might be necessary to start 
run.bat by typing bin\run in the client directory.)

Andreas


On 8 Jan 2003 at 10:34, Jim Coble wrote:

> Version: Tomcat 4.1.12 on Solaris 8
> 
> I'm trying to configure the WebDAV application included in the
> Tomcat 4.1.12 distribution so that it requires a login to add or
> remove files but not to view them.
> 
> If I use the web.xml security-constraint contained in the
> distribution --
> 
>   
> 
>   The Entire Web
>   Application
>   /*
> 
> 
>   tomcat
> 
>   
> 
> -- then all attempts to access the content, including a simple
> browser request for <http://localhost:8080/webdav/> require a
> login.
> 
> I thought I could password protect only adding and removing files
> by adding  for PUT and DELETE as shown below --
> 
>   
> 
>   The Entire Web
>   Application
>   /*
>   DELETE
>   PUT
> 
> 
>   tomcat
> 
>   
> 
>   -- but, if I do that, I seem to be able to add and remove files
>   using my
> WebDAV client (Web Folders on Windows XP) without authenticating.
> 
> I can't help but think that I'm missing something obvious.  Can
> anyone help?
> 
> Thanks in advance.
> --Jim
> 
> ==
> Jim Coble
> Senior Technology Specialist
> Center for Instructional Technology
> Email: [EMAIL PROTECTED]
> Voice: 919-660-5974  Fax: 919-660-5923
> Box 90198, Duke University
> Durham, NC 27708-0198
> ==
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:  
> <mailto:[EMAIL PROTECTED]> For
> additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> 



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Question about Tomcat 4.1.12 WebDAV application

[Jim Coble]

Version: Tomcat 4.1.12 on Solaris 8

I'm trying to configure the WebDAV application included in the Tomcat
4.1.12 distribution so that it requires a login to add or remove files but
not to view them.

If I use the web.xml security-constraint contained in the distribution --

  

  The Entire Web Application
  /*


  tomcat

  

-- then all attempts to access the content, including a simple browser
request for <http://localhost:8080/webdav/> require a login.

I thought I could password protect only adding and removing files by adding
 for PUT and DELETE as shown below --

  

  The Entire Web Application
  /*
  DELETE
  PUT


  tomcat

  

  -- but, if I do that, I seem to be able to add and remove files using my
WebDAV client (Web Folders on Windows XP) without authenticating.

I can't help but think that I'm missing something obvious.  Can anyone
help?

Thanks in advance.
--Jim

==
Jim Coble
Senior Technology Specialist
Center for Instructional Technology
Email: [EMAIL PROTECTED]
Voice: 919-660-5974  Fax: 919-660-5923
Box 90198, Duke University
Durham, NC 27708-0198
==




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Archives! (was Re: SV: tomcat 4.1.12 just stopped working, help !)

[Joel Rees]

> Hmm, I just got enlisted on this mailinglist so I don$B%((Bt have yesterdays mail 
(B>from it. Is there an archive from yesterday, or maybe you could mail me the thread ?
(B
(B(Ouch. That's a long line.)
(B
(BArchives:
(B
(Bhttp://jakarta.apache.org/site/mail.html
(B
(BAnd after you read the policies on this page, there's a link at the
(Bbottom of the page that takes you to a page with, among other things,
(Bseveral archive services listed on it. You really should have seen this
(Bpage when you signed up, by the way.
(B
(BI like marc, for no particular reason:
(B
(Bhttp://marc.theaimsgroup.com/(general list)
(Bhttp://marc.theaimsgroup.com/?l=tomcat-user&r=1&w=2   (tomcat-user)
(B
(B-- 
(BJoel Rees <[EMAIL PROTECTED]>
(B
(B
(B--
(BTo unsubscribe, e-mail:   
(BFor additional commands, e-mail: 

FW: Restricting SSL Cipher Suites with Standalone Tomcat 4.1.12?

[Greg Dowd]

I think every post I've seen in the last 5 days has generated a reply except
this one.  Is there anyone who could point me in the right direction?

-Original Message-
From: Greg Dowd [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 03, 2003 3:28 PM
To: '[EMAIL PROTECTED]'
Subject: Restricting SSL Cipher Suites with Standalone Tomcat 4.1.12?


Can I do this?  Is it a stupid ??  Can someone point me in the right
direction?

I have Tomcat 4.1.12 running fine with JDK 1.3.1 but I'd like to restrict
the available cipher suites to the stronger sets.  I see the notes about
Apache httpd.conf and SSLCipherSuite but that doesn't work for Tomcat, does
it?

Greg Dowd
[EMAIL PROTECTED]
Staff Scientist
Symmetricom, Trusted Time Division



--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: tomcat 4.1.12 just stopped working, help !

[Keshava Murthy]

Hi,
This is the copy of the text I mailed yesterday-

"Thanks for the reply. I had same exception thrown even with fresh
installation of tomcat 4.1.18 without my application included in webapps.
Anyway I solved this problem by uninstalling tomcat, removing all classpath
settings from environmental variables and installing tomcat again. Now it is
working fine, any way this will remain puzzle to me as no one has reported
similar bug anywhere else !!"



- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 07, 2003 5:43 PM
Subject: SV: tomcat 4.1.12 just stopped working, help !


The archive only covers "from June 5, 2000 to March 13, 2002" :(( (unless
you know of another archive than: http://mikal.org/interests/java/tomcat/ )
So, can someone tell me how I am supposed to get a hold of the "Parse error
in application web.xml" thread ? ;)

/Dan

-Ursprungligt meddelande-
Från: Keshava Murthy [mailto:[EMAIL PROTECTED]]
Skickat: den 7 januari 2003 12:46
Till: Tomcat Users List
Ämne: Re: tomcat 4.1.12 just stopped working, help !


Hi

Search in archive with text - "Parse error in application web.xml"

regards,
keshav
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 07, 2003 4:52 PM
Subject: SV: tomcat 4.1.12 just stopped working, help !


Hmm, I just got enlisted on this mailinglist so I don´t have yesterdays mail
from it. Is there an archive from yesterday, or maybe you could mail me the
thread ?

/D

-Ursprungligt meddelande-
Från: Keshava Murthy [mailto:[EMAIL PROTECTED]]
Skickat: den 7 januari 2003 12:21
Till: Tomcat Users List
Ämne: Re: tomcat 4.1.12 just stopped working, help !


Hi,

I had similar problem but not exactly the same. Please refer to my
yesterdays mail for a possible solution..
regards,
Keshav
- Original Message -
From: "Manavendra Gupta" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, January 08, 2003 5:32 AM
Subject: Re: tomcat 4.1.12 just stopped working, help !


> You said your tomcat stopped working somewhere around christmas. What were
> the last servlets you deployed and in what contexts? Or is that /examples
is
> the only context that you have?
>
> ~manav.
>
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, January 07, 2003 1:18 AM
> Subject: SV: tomcat 4.1.12 just stopped working, help !
>
>
> > I checked the ".../webapps/examples/WEB-INF/web.xml" and I checked line
> 115 as suggested in the log, I found some servlets that I had added and
> removed these lines just to get Tomcat working again, but it still doesn´t
> work. So now when I run ".../bin/catalina.sh run" I get this:
> >
> > [root@star bin]# ./catalina.sh run
> > Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
> > Using JAVA_HOME:   /usr/java/j2sdk1.4.1
> > Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry
> > INFO: Loading registry information
> > Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry
> > INFO: Creating new Registry instance
> > Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer
> > INFO: Creating MBeanServer
> > Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init
> > INFO: Initializing Coyote HTTP/1.1 on port 8080
> > Starting service Tomcat-Standalone
> > Apache Tomcat/4.1.12
> > Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start
> > INFO: Starting Coyote HTTP/1.1 on port 8080
> > Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init
> > INFO: JK2: ajp13 listening on tcp port 8009
> > Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start
> > INFO: Jk running ID=0 time=6/291
> config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties
> >
> > I still don´t get any answer from port 8080 :((
> >
> > /Dan
> >
> >
> > -Ursprungligt meddelande-
> > Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]]
> > Skickat: den 7 januari 2003 23:42
> > Till: Tomcat Users List
> > Ämne: Re: tomcat 4.1.12 just stopped working, help !
> >
> >
> > As the log suggests, the deployment descriptor of the servlet does not
> > conform to the DTD :
> >
> > >> The content of element type "servlet" must match
> >
>
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
> > t-param*,load-on-startup?,run-as?,security-role-ref*)".
&

SV: tomcat 4.1.12 just stopped working, help !

[Daniel.T.Hellstrand]

The archive only covers "from June 5, 2000 to March 13, 2002" :(( (unless you know of 
another archive than: http://mikal.org/interests/java/tomcat/ )
So, can someone tell me how I am supposed to get a hold of the "Parse error in 
application web.xml" thread ? ;)

/Dan

-Ursprungligt meddelande-
Från: Keshava Murthy [mailto:[EMAIL PROTECTED]]
Skickat: den 7 januari 2003 12:46
Till: Tomcat Users List
Ämne: Re: tomcat 4.1.12 just stopped working, help !


Hi

Search in archive with text - "Parse error in application web.xml"

regards,
keshav
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 07, 2003 4:52 PM
Subject: SV: tomcat 4.1.12 just stopped working, help !


Hmm, I just got enlisted on this mailinglist so I don´t have yesterdays mail
from it. Is there an archive from yesterday, or maybe you could mail me the
thread ?

/D

-Ursprungligt meddelande-
Från: Keshava Murthy [mailto:[EMAIL PROTECTED]]
Skickat: den 7 januari 2003 12:21
Till: Tomcat Users List
Ämne: Re: tomcat 4.1.12 just stopped working, help !


Hi,

I had similar problem but not exactly the same. Please refer to my
yesterdays mail for a possible solution..
regards,
Keshav
- Original Message -
From: "Manavendra Gupta" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, January 08, 2003 5:32 AM
Subject: Re: tomcat 4.1.12 just stopped working, help !


> You said your tomcat stopped working somewhere around christmas. What were
> the last servlets you deployed and in what contexts? Or is that /examples
is
> the only context that you have?
>
> ~manav.
>
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, January 07, 2003 1:18 AM
> Subject: SV: tomcat 4.1.12 just stopped working, help !
>
>
> > I checked the ".../webapps/examples/WEB-INF/web.xml" and I checked line
> 115 as suggested in the log, I found some servlets that I had added and
> removed these lines just to get Tomcat working again, but it still doesn´t
> work. So now when I run ".../bin/catalina.sh run" I get this:
> >
> > [root@star bin]# ./catalina.sh run
> > Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
> > Using JAVA_HOME:   /usr/java/j2sdk1.4.1
> > Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry
> > INFO: Loading registry information
> > Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry
> > INFO: Creating new Registry instance
> > Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer
> > INFO: Creating MBeanServer
> > Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init
> > INFO: Initializing Coyote HTTP/1.1 on port 8080
> > Starting service Tomcat-Standalone
> > Apache Tomcat/4.1.12
> > Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start
> > INFO: Starting Coyote HTTP/1.1 on port 8080
> > Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init
> > INFO: JK2: ajp13 listening on tcp port 8009
> > Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start
> > INFO: Jk running ID=0 time=6/291
> config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties
> >
> > I still don´t get any answer from port 8080 :((
> >
> > /Dan
> >
> >
> > -Ursprungligt meddelande-
> > Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]]
> > Skickat: den 7 januari 2003 23:42
> > Till: Tomcat Users List
> > Ämne: Re: tomcat 4.1.12 just stopped working, help !
> >
> >
> > As the log suggests, the deployment descriptor of the servlet does not
> > conform to the DTD :
> >
> > >> The content of element type "servlet" must match
> >
>
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
> > t-param*,load-on-startup?,run-as?,security-role-ref*)".
> >
> > Check the web.xml file for the last few servlets you deployed. The
> > descriptor elements should occur in the same order as mentioned above.
> >
> > ~Manav.
> >
> > - Original Message -
> > From: <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Tuesday, January 07, 2003 12:44 AM
> > Subject: tomcat 4.1.12 just stopped working, help !
> >
> >
> > > Hi all
> > > Some time during christmas Tomcat 4.1.12 stopped working for me, I
don´t
> > know why, thought anyone here might have a clue.
> > > This is wh

Re: tomcat 4.1.12 just stopped working, help !

[Keshava Murthy]

Hi

Search in archive with text - "Parse error in application web.xml"

regards,
keshav
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 07, 2003 4:52 PM
Subject: SV: tomcat 4.1.12 just stopped working, help !


Hmm, I just got enlisted on this mailinglist so I don´t have yesterdays mail
from it. Is there an archive from yesterday, or maybe you could mail me the
thread ?

/D

-Ursprungligt meddelande-
Från: Keshava Murthy [mailto:[EMAIL PROTECTED]]
Skickat: den 7 januari 2003 12:21
Till: Tomcat Users List
Ämne: Re: tomcat 4.1.12 just stopped working, help !


Hi,

I had similar problem but not exactly the same. Please refer to my
yesterdays mail for a possible solution..
regards,
Keshav
- Original Message -
From: "Manavendra Gupta" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, January 08, 2003 5:32 AM
Subject: Re: tomcat 4.1.12 just stopped working, help !


> You said your tomcat stopped working somewhere around christmas. What were
> the last servlets you deployed and in what contexts? Or is that /examples
is
> the only context that you have?
>
> ~manav.
>
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, January 07, 2003 1:18 AM
> Subject: SV: tomcat 4.1.12 just stopped working, help !
>
>
> > I checked the ".../webapps/examples/WEB-INF/web.xml" and I checked line
> 115 as suggested in the log, I found some servlets that I had added and
> removed these lines just to get Tomcat working again, but it still doesn´t
> work. So now when I run ".../bin/catalina.sh run" I get this:
> >
> > [root@star bin]# ./catalina.sh run
> > Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
> > Using JAVA_HOME:   /usr/java/j2sdk1.4.1
> > Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry
> > INFO: Loading registry information
> > Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry
> > INFO: Creating new Registry instance
> > Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer
> > INFO: Creating MBeanServer
> > Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init
> > INFO: Initializing Coyote HTTP/1.1 on port 8080
> > Starting service Tomcat-Standalone
> > Apache Tomcat/4.1.12
> > Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start
> > INFO: Starting Coyote HTTP/1.1 on port 8080
> > Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init
> > INFO: JK2: ajp13 listening on tcp port 8009
> > Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start
> > INFO: Jk running ID=0 time=6/291
> config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties
> >
> > I still don´t get any answer from port 8080 :((
> >
> > /Dan
> >
> >
> > -Ursprungligt meddelande-
> > Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]]
> > Skickat: den 7 januari 2003 23:42
> > Till: Tomcat Users List
> > Ämne: Re: tomcat 4.1.12 just stopped working, help !
> >
> >
> > As the log suggests, the deployment descriptor of the servlet does not
> > conform to the DTD :
> >
> > >> The content of element type "servlet" must match
> >
>
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
> > t-param*,load-on-startup?,run-as?,security-role-ref*)".
> >
> > Check the web.xml file for the last few servlets you deployed. The
> > descriptor elements should occur in the same order as mentioned above.
> >
> > ~Manav.
> >
> > - Original Message -
> > From: <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Tuesday, January 07, 2003 12:44 AM
> > Subject: tomcat 4.1.12 just stopped working, help !
> >
> >
> > > Hi all
> > > Some time during christmas Tomcat 4.1.12 stopped working for me, I
don´t
> > know why, thought anyone here might have a clue.
> > > This is what I know:
> > > If I start tomcat with ".../bin/startup.sh" and then run a portscan I
> can
> > see:
> > > 8009/tcp   open    ajp13
> > > 8080/tcp   open    http-proxy
> > > So evidently something happens ;)
> > >
> > > But if I try to access http://my.ip:8080/index.wml (or just
> > http://my.ip:8080) I don´t get any answer at all, it seems totally dead.
> > >
> > > If I the

SV: tomcat 4.1.12 just stopped working, help !

[Daniel.T.Hellstrand]

Hmm, I just got enlisted on this mailinglist so I don´t have yesterdays mail from it. 
Is there an archive from yesterday, or maybe you could mail me the thread ?

/D

-Ursprungligt meddelande-
Från: Keshava Murthy [mailto:[EMAIL PROTECTED]]
Skickat: den 7 januari 2003 12:21
Till: Tomcat Users List
Ämne: Re: tomcat 4.1.12 just stopped working, help !


Hi,

I had similar problem but not exactly the same. Please refer to my
yesterdays mail for a possible solution..
regards,
Keshav
- Original Message -
From: "Manavendra Gupta" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, January 08, 2003 5:32 AM
Subject: Re: tomcat 4.1.12 just stopped working, help !


> You said your tomcat stopped working somewhere around christmas. What were
> the last servlets you deployed and in what contexts? Or is that /examples
is
> the only context that you have?
>
> ~manav.
>
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, January 07, 2003 1:18 AM
> Subject: SV: tomcat 4.1.12 just stopped working, help !
>
>
> > I checked the ".../webapps/examples/WEB-INF/web.xml" and I checked line
> 115 as suggested in the log, I found some servlets that I had added and
> removed these lines just to get Tomcat working again, but it still doesn´t
> work. So now when I run ".../bin/catalina.sh run" I get this:
> >
> > [root@star bin]# ./catalina.sh run
> > Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
> > Using JAVA_HOME:   /usr/java/j2sdk1.4.1
> > Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry
> > INFO: Loading registry information
> > Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry
> > INFO: Creating new Registry instance
> > Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer
> > INFO: Creating MBeanServer
> > Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init
> > INFO: Initializing Coyote HTTP/1.1 on port 8080
> > Starting service Tomcat-Standalone
> > Apache Tomcat/4.1.12
> > Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start
> > INFO: Starting Coyote HTTP/1.1 on port 8080
> > Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init
> > INFO: JK2: ajp13 listening on tcp port 8009
> > Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start
> > INFO: Jk running ID=0 time=6/291
> config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties
> >
> > I still don´t get any answer from port 8080 :((
> >
> > /Dan
> >
> >
> > -Ursprungligt meddelande-
> > Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]]
> > Skickat: den 7 januari 2003 23:42
> > Till: Tomcat Users List
> > Ämne: Re: tomcat 4.1.12 just stopped working, help !
> >
> >
> > As the log suggests, the deployment descriptor of the servlet does not
> > conform to the DTD :
> >
> > >> The content of element type "servlet" must match
> >
>
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
> > t-param*,load-on-startup?,run-as?,security-role-ref*)".
> >
> > Check the web.xml file for the last few servlets you deployed. The
> > descriptor elements should occur in the same order as mentioned above.
> >
> > ~Manav.
> >
> > - Original Message -
> > From: <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Tuesday, January 07, 2003 12:44 AM
> > Subject: tomcat 4.1.12 just stopped working, help !
> >
> >
> > > Hi all
> > > Some time during christmas Tomcat 4.1.12 stopped working for me, I
don´t
> > know why, thought anyone here might have a clue.
> > > This is what I know:
> > > If I start tomcat with ".../bin/startup.sh" and then run a portscan I
> can
> > see:
> > > 8009/tcp   openajp13
> > > 8080/tcp   openhttp-proxy
> > > So evidently something happens ;)
> > >
> > > But if I try to access http://my.ip:8080/index.wml (or just
> > http://my.ip:8080) I don´t get any answer at all, it seems totally dead.
> > >
> > > If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the
> > services on ports 8009 and 8080 are gone.
> > >
> > > But if I directly run ".../bin/catalina.sh run" I get this: (if
someone
> > can get any clue from this)
> > >
> > &g

Re: tomcat 4.1.12 just stopped working, help !

[Keshava Murthy]

Hi,

I had similar problem but not exactly the same. Please refer to my
yesterdays mail for a possible solution..
regards,
Keshav
- Original Message -
From: "Manavendra Gupta" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, January 08, 2003 5:32 AM
Subject: Re: tomcat 4.1.12 just stopped working, help !


> You said your tomcat stopped working somewhere around christmas. What were
> the last servlets you deployed and in what contexts? Or is that /examples
is
> the only context that you have?
>
> ~manav.
>
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, January 07, 2003 1:18 AM
> Subject: SV: tomcat 4.1.12 just stopped working, help !
>
>
> > I checked the ".../webapps/examples/WEB-INF/web.xml" and I checked line
> 115 as suggested in the log, I found some servlets that I had added and
> removed these lines just to get Tomcat working again, but it still doesn´t
> work. So now when I run ".../bin/catalina.sh run" I get this:
> >
> > [root@star bin]# ./catalina.sh run
> > Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
> > Using JAVA_HOME:   /usr/java/j2sdk1.4.1
> > Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry
> > INFO: Loading registry information
> > Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry
> > INFO: Creating new Registry instance
> > Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer
> > INFO: Creating MBeanServer
> > Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init
> > INFO: Initializing Coyote HTTP/1.1 on port 8080
> > Starting service Tomcat-Standalone
> > Apache Tomcat/4.1.12
> > Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start
> > INFO: Starting Coyote HTTP/1.1 on port 8080
> > Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init
> > INFO: JK2: ajp13 listening on tcp port 8009
> > Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start
> > INFO: Jk running ID=0 time=6/291
> config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties
> >
> > I still don´t get any answer from port 8080 :((
> >
> > /Dan
> >
> >
> > -Ursprungligt meddelande-
> > Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]]
> > Skickat: den 7 januari 2003 23:42
> > Till: Tomcat Users List
> > Ämne: Re: tomcat 4.1.12 just stopped working, help !
> >
> >
> > As the log suggests, the deployment descriptor of the servlet does not
> > conform to the DTD :
> >
> > >> The content of element type "servlet" must match
> >
>
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
> > t-param*,load-on-startup?,run-as?,security-role-ref*)".
> >
> > Check the web.xml file for the last few servlets you deployed. The
> > descriptor elements should occur in the same order as mentioned above.
> >
> > ~Manav.
> >
> > - Original Message -
> > From: <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Tuesday, January 07, 2003 12:44 AM
> > Subject: tomcat 4.1.12 just stopped working, help !
> >
> >
> > > Hi all
> > > Some time during christmas Tomcat 4.1.12 stopped working for me, I
don´t
> > know why, thought anyone here might have a clue.
> > > This is what I know:
> > > If I start tomcat with ".../bin/startup.sh" and then run a portscan I
> can
> > see:
> > > 8009/tcp   openajp13
> > > 8080/tcp   openhttp-proxy
> > > So evidently something happens ;)
> > >
> > > But if I try to access http://my.ip:8080/index.wml (or just
> > http://my.ip:8080) I don´t get any answer at all, it seems totally dead.
> > >
> > > If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the
> > services on ports 8009 and 8080 are gone.
> > >
> > > But if I directly run ".../bin/catalina.sh run" I get this: (if
someone
> > can get any clue from this)
> > >
> > > [root@star bin]# ./catalina.sh run
> > > Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
> > > Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
> > > Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
> > > Using JAVA_HOME:   /usr/java/j2sdk1.4.1
> > > Jan 7, 2003 9:40:58 AM org.apache.commons.modele

Re: tomcat 4.1.12 just stopped working, help !

[Manavendra Gupta]

You said your tomcat stopped working somewhere around christmas. What were
the last servlets you deployed and in what contexts? Or is that /examples is
the only context that you have?

~manav.

- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 07, 2003 1:18 AM
Subject: SV: tomcat 4.1.12 just stopped working, help !


> I checked the ".../webapps/examples/WEB-INF/web.xml" and I checked line
115 as suggested in the log, I found some servlets that I had added and
removed these lines just to get Tomcat working again, but it still doesn´t
work. So now when I run ".../bin/catalina.sh run" I get this:
>
> [root@star bin]# ./catalina.sh run
> Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
> Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
> Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
> Using JAVA_HOME:   /usr/java/j2sdk1.4.1
> Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry
> INFO: Loading registry information
> Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry
> INFO: Creating new Registry instance
> Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer
> INFO: Creating MBeanServer
> Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on port 8080
> Starting service Tomcat-Standalone
> Apache Tomcat/4.1.12
> Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start
> INFO: Starting Coyote HTTP/1.1 on port 8080
> Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init
> INFO: JK2: ajp13 listening on tcp port 8009
> Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start
> INFO: Jk running ID=0 time=6/291
config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties
>
> I still don´t get any answer from port 8080 :((
>
> /Dan
>
>
> -Ursprungligt meddelande-
> Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]]
> Skickat: den 7 januari 2003 23:42
> Till: Tomcat Users List
> Ämne: Re: tomcat 4.1.12 just stopped working, help !
>
>
> As the log suggests, the deployment descriptor of the servlet does not
> conform to the DTD :
>
> >> The content of element type "servlet" must match
>
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
> t-param*,load-on-startup?,run-as?,security-role-ref*)".
>
> Check the web.xml file for the last few servlets you deployed. The
> descriptor elements should occur in the same order as mentioned above.
>
> ~Manav.
>
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, January 07, 2003 12:44 AM
> Subject: tomcat 4.1.12 just stopped working, help !
>
>
> > Hi all
> > Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t
> know why, thought anyone here might have a clue.
> > This is what I know:
> > If I start tomcat with ".../bin/startup.sh" and then run a portscan I
can
> see:
> > 8009/tcp   openajp13
> > 8080/tcp   openhttp-proxy
> > So evidently something happens ;)
> >
> > But if I try to access http://my.ip:8080/index.wml (or just
> http://my.ip:8080) I don´t get any answer at all, it seems totally dead.
> >
> > If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the
> services on ports 8009 and 8080 are gone.
> >
> > But if I directly run ".../bin/catalina.sh run" I get this: (if someone
> can get any clue from this)
> >
> > [root@star bin]# ./catalina.sh run
> > Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
> > Using JAVA_HOME:   /usr/java/j2sdk1.4.1
> > Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry
> > INFO: Loading registry information
> > Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry
> > INFO: Creating new Registry instance
> > Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer
> > INFO: Creating MBeanServer
> >
> > Starting service Tomcat-Standalone
> > Apache Tomcat/4.1.12
> > Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error
> > SEVERE: Parse Error at line 114 column 15: The content of element type
> "servlet" must match
>
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
> t-param*,load-on-startup?,run-as?,security-role-ref*)".
> > org.xml.sax.SAXParseException: The content of element type "servlet"
must
> match
>
"(icon?,serv

RE: tomcat 4.1.12 just stopped working, help !

[Kevin Passey]

Or use cooktop if you don't have XML Spy

Cheers

Kevin

-Original Message-
From: Holger Brozio [mailto:[EMAIL PROTECTED]]
Sent: 07 January 2003 09:14
To: Tomcat Users List
Subject: Re: tomcat 4.1.12 just stopped working, help !


Whats about using a tool like XML Spy. With this one you can check, if the
web.xml files are well formed and valid.
Valid means, that they match the rules defined in the web-app_2_3.dtd, which
seems to be the problem in that case.

HTH

Holger
- Original Message -
From: "Peng Tuck Kwok" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, January 07, 2003 9:53 AM
Subject: Re: tomcat 4.1.12 just stopped working, help !


> Hmm, it looks like an error in the web.xml of a certain app. Did you by
> any chance change the web.xml of any of your web applications ?
>
> [EMAIL PROTECTED] wrote:
> > Hi all
> > Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t
know why, thought anyone here might have a clue.
> > This is what I know:
> > If I start tomcat with ".../bin/startup.sh" and then run a portscan I
can see:
> > 8009/tcp   openajp13
> > 8080/tcp   openhttp-proxy
> > So evidently something happens ;)
> >
> > But if I try to access http://my.ip:8080/index.wml (or just
http://my.ip:8080) I don´t get any answer at all, it seems totally dead.
> >
> > If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the
services on ports 8009 and 8080 are gone.
> >
> > But if I directly run ".../bin/catalina.sh run" I get this: (if someone
can get any clue from this)
> >
> > [root@star bin]# ./catalina.sh run
> > Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
> > Using JAVA_HOME:   /usr/java/j2sdk1.4.1
> > Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry
> > INFO: Loading registry information
> > Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry
> > INFO: Creating new Registry instance
> > Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer
> > INFO: Creating MBeanServer
> >
> > Starting service Tomcat-Standalone
> > Apache Tomcat/4.1.12
> > Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error
> > SEVERE: Parse Error at line 114 column 15: The content of element type
"servlet" must match
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
t-param*,load-on-startup?,run-as?,security-role-ref*)".
> > org.xml.sax.SAXParseException: The content of element type "servlet"
must match
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
t-param*,load-on-startup?,run-as?,security-role-ref*)".
> > at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHand
lerWrapper.java:232)
> > at
org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:17
3)
> > at
org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:36
2)
> > at
org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:29
6)
> > at
org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.
java:1953)
> > at
org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:8
78)
> > at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDo
cumentFragmentScannerImpl.java:1144)
> > at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocu
mentFragmentScannerImpl.java:987)
> > at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc
her.dispatch(XMLDocumentFragmentScannerImpl.java:1445)
> > at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocume
ntFragmentScannerImpl.java:333)
> > at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:524)
> > at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:580)
> > at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
> > at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:116
9)
> > at
org.apache.commons.digester.Digester.parse(Digester.java:1495)
> > at
org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.ja
va:282)
> > at
org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:639)
> > at
org.apache.catalina.startup.ContextConfig.lifecycleEv

Re: SV: tomcat 4.1.12 just stopped working, help !

[Peng Tuck Kwok]

If you are sure that is the xml in question, can you forward it to the 
list so we can have a look?

[EMAIL PROTECTED] wrote:
I checked the ".../webapps/examples/WEB-INF/web.xml" and I checked line 115 as suggested in the log, I found some servlets that I had added and removed these lines just to get Tomcat working again, but it still doesn´t work. So now when I run ".../bin/catalina.sh run" I get this:

[root@star bin]# ./catalina.sh run
Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
Using JAVA_HOME:   /usr/java/j2sdk1.4.1
Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry
INFO: Loading registry information
Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer
Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Starting service Tomcat-Standalone
Apache Tomcat/4.1.12
Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8080
Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on tcp port 8009
Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=6/291  config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties

I still don´t get any answer from port 8080 :((

/Dan


-Ursprungligt meddelande-
Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]]
Skickat: den 7 januari 2003 23:42
Till: Tomcat Users List
Ämne: Re: tomcat 4.1.12 just stopped working, help !


As the log suggests, the deployment descriptor of the servlet does not
conform to the DTD :



The content of element type "servlet" must match


"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
t-param*,load-on-startup?,run-as?,security-role-ref*)".

Check the web.xml file for the last few servlets you deployed. The
descriptor elements should occur in the same order as mentioned above.

~Manav.

- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 07, 2003 12:44 AM
Subject: tomcat 4.1.12 just stopped working, help !




Hi all
Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t


know why, thought anyone here might have a clue.


This is what I know:
If I start tomcat with ".../bin/startup.sh" and then run a portscan I can


see:


8009/tcp   openajp13
8080/tcp   openhttp-proxy
So evidently something happens ;)

But if I try to access http://my.ip:8080/index.wml (or just


http://my.ip:8080) I don´t get any answer at all, it seems totally dead.


If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the


services on ports 8009 and 8080 are gone.


But if I directly run ".../bin/catalina.sh run" I get this: (if someone


can get any clue from this)


[root@star bin]# ./catalina.sh run
Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
Using JAVA_HOME:   /usr/java/j2sdk1.4.1
Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry
INFO: Loading registry information
Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer

Starting service Tomcat-Standalone
Apache Tomcat/4.1.12
Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error
SEVERE: Parse Error at line 114 column 15: The content of element type


"servlet" must match
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
t-param*,load-on-startup?,run-as?,security-role-ref*)".


org.xml.sax.SAXParseException: The content of element type "servlet" must


match
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
t-param*,load-on-startup?,run-as?,security-role-ref*)".


   at


org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHand
lerWrapper.java:232)


   at


org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:17
3)


   at


org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:36
2)


   at


org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:29
6)


   at


org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.
java:1953)


   at


org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:8
78)


   at


org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDo
cumentFragmentScannerImpl.java:1144)


   at

SV: tomcat 4.1.12 just stopped working, help !

[Daniel.T.Hellstrand]

I checked the ".../webapps/examples/WEB-INF/web.xml" and I checked line 115 as 
suggested in the log, I found some servlets that I had added and removed these lines 
just to get Tomcat working again, but it still doesn´t work. So now when I run 
".../bin/catalina.sh run" I get this:

[root@star bin]# ./catalina.sh run
Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
Using JAVA_HOME:   /usr/java/j2sdk1.4.1
Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry loadRegistry
INFO: Loading registry information
Jan 7, 2003 10:25:49 AM org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
Jan 7, 2003 10:25:53 AM org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer
Jan 7, 2003 10:25:58 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Starting service Tomcat-Standalone
Apache Tomcat/4.1.12
Jan 7, 2003 10:26:29 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8080
Jan 7, 2003 10:26:29 AM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on tcp port 8009
Jan 7, 2003 10:26:29 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=6/291  config=/etc/jakarta-tomcat-4.1.12/conf/jk2.properties

I still don´t get any answer from port 8080 :((

/Dan


-Ursprungligt meddelande-
Från: Manavendra Gupta [mailto:[EMAIL PROTECTED]]
Skickat: den 7 januari 2003 23:42
Till: Tomcat Users List
Ämne: Re: tomcat 4.1.12 just stopped working, help !


As the log suggests, the deployment descriptor of the servlet does not
conform to the DTD :

>> The content of element type "servlet" must match
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
t-param*,load-on-startup?,run-as?,security-role-ref*)".

Check the web.xml file for the last few servlets you deployed. The
descriptor elements should occur in the same order as mentioned above.

~Manav.

- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 07, 2003 12:44 AM
Subject: tomcat 4.1.12 just stopped working, help !


> Hi all
> Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t
know why, thought anyone here might have a clue.
> This is what I know:
> If I start tomcat with ".../bin/startup.sh" and then run a portscan I can
see:
> 8009/tcp   openajp13
> 8080/tcp   openhttp-proxy
> So evidently something happens ;)
>
> But if I try to access http://my.ip:8080/index.wml (or just
http://my.ip:8080) I don´t get any answer at all, it seems totally dead.
>
> If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the
services on ports 8009 and 8080 are gone.
>
> But if I directly run ".../bin/catalina.sh run" I get this: (if someone
can get any clue from this)
>
> [root@star bin]# ./catalina.sh run
> Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
> Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
> Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
> Using JAVA_HOME:   /usr/java/j2sdk1.4.1
> Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry
> INFO: Loading registry information
> Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry
> INFO: Creating new Registry instance
> Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer
> INFO: Creating MBeanServer
>
> Starting service Tomcat-Standalone
> Apache Tomcat/4.1.12
> Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error
> SEVERE: Parse Error at line 114 column 15: The content of element type
"servlet" must match
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
t-param*,load-on-startup?,run-as?,security-role-ref*)".
> org.xml.sax.SAXParseException: The content of element type "servlet" must
match
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
t-param*,load-on-startup?,run-as?,security-role-ref*)".
> at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHand
lerWrapper.java:232)
> at
org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:17
3)
> at
org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:36
2)
> at
org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:29
6)
> at
org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.
java:1953)
> at
org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:8
78)
> at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDo
cumentFragmentScan

Re: tomcat 4.1.12 just stopped working, help !

[Holger Brozio]

Whats about using a tool like XML Spy. With this one you can check, if the
web.xml files are well formed and valid.
Valid means, that they match the rules defined in the web-app_2_3.dtd, which
seems to be the problem in that case.

HTH

Holger
- Original Message -
From: "Peng Tuck Kwok" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, January 07, 2003 9:53 AM
Subject: Re: tomcat 4.1.12 just stopped working, help !


> Hmm, it looks like an error in the web.xml of a certain app. Did you by
> any chance change the web.xml of any of your web applications ?
>
> [EMAIL PROTECTED] wrote:
> > Hi all
> > Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t
know why, thought anyone here might have a clue.
> > This is what I know:
> > If I start tomcat with ".../bin/startup.sh" and then run a portscan I
can see:
> > 8009/tcp   openajp13
> > 8080/tcp   openhttp-proxy
> > So evidently something happens ;)
> >
> > But if I try to access http://my.ip:8080/index.wml (or just
http://my.ip:8080) I don´t get any answer at all, it seems totally dead.
> >
> > If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the
services on ports 8009 and 8080 are gone.
> >
> > But if I directly run ".../bin/catalina.sh run" I get this: (if someone
can get any clue from this)
> >
> > [root@star bin]# ./catalina.sh run
> > Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
> > Using JAVA_HOME:   /usr/java/j2sdk1.4.1
> > Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry
> > INFO: Loading registry information
> > Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry
> > INFO: Creating new Registry instance
> > Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer
> > INFO: Creating MBeanServer
> >
> > Starting service Tomcat-Standalone
> > Apache Tomcat/4.1.12
> > Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error
> > SEVERE: Parse Error at line 114 column 15: The content of element type
"servlet" must match
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
t-param*,load-on-startup?,run-as?,security-role-ref*)".
> > org.xml.sax.SAXParseException: The content of element type "servlet"
must match
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
t-param*,load-on-startup?,run-as?,security-role-ref*)".
> > at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHand
lerWrapper.java:232)
> > at
org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:17
3)
> > at
org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:36
2)
> > at
org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:29
6)
> > at
org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.
java:1953)
> > at
org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:8
78)
> > at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDo
cumentFragmentScannerImpl.java:1144)
> > at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocu
mentFragmentScannerImpl.java:987)
> > at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc
her.dispatch(XMLDocumentFragmentScannerImpl.java:1445)
> > at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocume
ntFragmentScannerImpl.java:333)
> > at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:524)
> > at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:580)
> > at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
> > at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:116
9)
> > at
org.apache.commons.digester.Digester.parse(Digester.java:1495)
> > at
org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.ja
va:282)
> > at
org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:639)
> > at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:
243)
> > at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor
t.java:166)
> > at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3493)
> > at
org.apach

Re: tomcat 4.1.12 just stopped working, help !

[Manavendra Gupta]

As the log suggests, the deployment descriptor of the servlet does not
conform to the DTD :

>> The content of element type "servlet" must match
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
t-param*,load-on-startup?,run-as?,security-role-ref*)".

Check the web.xml file for the last few servlets you deployed. The
descriptor elements should occur in the same order as mentioned above.

~Manav.

- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 07, 2003 12:44 AM
Subject: tomcat 4.1.12 just stopped working, help !


> Hi all
> Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t
know why, thought anyone here might have a clue.
> This is what I know:
> If I start tomcat with ".../bin/startup.sh" and then run a portscan I can
see:
> 8009/tcp   openajp13
> 8080/tcp   openhttp-proxy
> So evidently something happens ;)
>
> But if I try to access http://my.ip:8080/index.wml (or just
http://my.ip:8080) I don´t get any answer at all, it seems totally dead.
>
> If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the
services on ports 8009 and 8080 are gone.
>
> But if I directly run ".../bin/catalina.sh run" I get this: (if someone
can get any clue from this)
>
> [root@star bin]# ./catalina.sh run
> Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
> Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
> Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
> Using JAVA_HOME:   /usr/java/j2sdk1.4.1
> Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry
> INFO: Loading registry information
> Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry
> INFO: Creating new Registry instance
> Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer
> INFO: Creating MBeanServer
>
> Starting service Tomcat-Standalone
> Apache Tomcat/4.1.12
> Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error
> SEVERE: Parse Error at line 114 column 15: The content of element type
"servlet" must match
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
t-param*,load-on-startup?,run-as?,security-role-ref*)".
> org.xml.sax.SAXParseException: The content of element type "servlet" must
match
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
t-param*,load-on-startup?,run-as?,security-role-ref*)".
> at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHand
lerWrapper.java:232)
> at
org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:17
3)
> at
org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:36
2)
> at
org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:29
6)
> at
org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.
java:1953)
> at
org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:8
78)
> at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDo
cumentFragmentScannerImpl.java:1144)
> at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocu
mentFragmentScannerImpl.java:987)
> at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc
her.dispatch(XMLDocumentFragmentScannerImpl.java:1445)
> at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocume
ntFragmentScannerImpl.java:333)
> at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:524)
> at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:580)
> at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
> at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:116
9)
> at org.apache.commons.digester.Digester.parse(Digester.java:1495)
> at
org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.ja
va:282)
> at
org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:639)
> at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:
243)
> at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor
t.java:166)
> at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3493)
> at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
> at
org.apache.catalina.core.StandardHost.start(StandardHost.java:738)
> at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
> at
org.apache.catalina.core.StandardEngine.start(St

SV: tomcat 4.1.12 just stopped working, help !

[Daniel.T.Hellstrand]

Hehe, not that I know of ;))
Well there is a web.xml in .../conf/ and additional web.xml in every catalog in 
".../webapps/" so is there any good way of finding out in which the error occurs ?




-Ursprungligt meddelande-
Från: Peng Tuck Kwok [mailto:[EMAIL PROTECTED]]
Skickat: den 7 januari 2003 09:54
Till: Tomcat Users List
Ämne: Re: tomcat 4.1.12 just stopped working, help !


Hmm, it looks like an error in the web.xml of a certain app. Did you by 
any chance change the web.xml of any of your web applications ?

[EMAIL PROTECTED] wrote:
> Hi all
> Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, 
>thought anyone here might have a clue.
> This is what I know:
> If I start tomcat with ".../bin/startup.sh" and then run a portscan I can see:
> 8009/tcp   openajp13
> 8080/tcp   openhttp-proxy
> So evidently something happens ;)
> 
> But if I try to access http://my.ip:8080/index.wml (or just http://my.ip:8080) I 
>don´t get any answer at all, it seems totally dead.
> 
> If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the services on ports 
>8009 and 8080 are gone.
> 
> But if I directly run ".../bin/catalina.sh run" I get this: (if someone can get any 
>clue from this)
> 
> [root@star bin]# ./catalina.sh run
> Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
> Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
> Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
> Using JAVA_HOME:   /usr/java/j2sdk1.4.1
> Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry
> INFO: Loading registry information
> Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry
> INFO: Creating new Registry instance
> Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer
> INFO: Creating MBeanServer
> 
> Starting service Tomcat-Standalone
> Apache Tomcat/4.1.12
> Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error
> SEVERE: Parse Error at line 114 column 15: The content of element type "servlet" 
>must match 
>"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),init-param*,load-on-startup?,run-as?,security-role-ref*)".
> org.xml.sax.SAXParseException: The content of element type "servlet" must match 
>"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),init-param*,load-on-startup?,run-as?,security-role-ref*)".
> at 
>org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:232)
> at 
>org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:173)
> at 
>org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:362)
> at 
>org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:296)
> at 
>org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.java:1953)
> at 
>org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:878)
> at 
>org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDocumentFragmentScannerImpl.java:1144)
> at 
>org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:987)
> at 
>org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1445)
> at 
>org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:333)
> at 
>org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:524)
> at 
>org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:580)
> at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
> at 
>org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1169)
> at org.apache.commons.digester.Digester.parse(Digester.java:1495)
> at 
>org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.java:282)
> at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:639)
> at 
>org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:243)
> at 
>org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3493)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
> at org.apache.catalina.core.StandardHost.start(StandardHost.java:738)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
> at org.apache.

Re: tomcat 4.1.12 just stopped working, help !

[Peng Tuck Kwok]

Hmm, it looks like an error in the web.xml of a certain app. Did you by 
any chance change the web.xml of any of your web applications ?

[EMAIL PROTECTED] wrote:
Hi all
Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, thought anyone here might have a clue.
This is what I know:
If I start tomcat with ".../bin/startup.sh" and then run a portscan I can see:
8009/tcp   openajp13
8080/tcp   openhttp-proxy
So evidently something happens ;)

But if I try to access http://my.ip:8080/index.wml (or just http://my.ip:8080) I don´t get any answer at all, it seems totally dead.

If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the services on ports 8009 and 8080 are gone.

But if I directly run ".../bin/catalina.sh run" I get this: (if someone can get any clue from this)

[root@star bin]# ./catalina.sh run
Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
Using JAVA_HOME:   /usr/java/j2sdk1.4.1
Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry
INFO: Loading registry information
Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer

Starting service Tomcat-Standalone
Apache Tomcat/4.1.12
Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error
SEVERE: Parse Error at line 114 column 15: The content of element type "servlet" must match "(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),init-param*,load-on-startup?,run-as?,security-role-ref*)".
org.xml.sax.SAXParseException: The content of element type "servlet" must match "(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),init-param*,load-on-startup?,run-as?,security-role-ref*)".
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:232)
at org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:173)
at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:362)
at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:296)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.java:1953)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:878)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDocumentFragmentScannerImpl.java:1144)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:987)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1445)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:333)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:524)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:580)
at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1169)
at org.apache.commons.digester.Digester.parse(Digester.java:1495)
at org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.java:282)
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:639)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:243)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3493)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:738)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347)
at org.apache.catalina.core.StandardService.start(StandardService.java:497)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2189)
at org.apache.catalina.startup.Catalina.start(Catalina.java:510)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina

tomcat 4.1.12 just stopped working, help !

[Daniel.T.Hellstrand]

Hi all
Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t know why, 
thought anyone here might have a clue.
This is what I know:
If I start tomcat with ".../bin/startup.sh" and then run a portscan I can see:
8009/tcp   openajp13
8080/tcp   openhttp-proxy
So evidently something happens ;)

But if I try to access http://my.ip:8080/index.wml (or just http://my.ip:8080) I don´t 
get any answer at all, it seems totally dead.

If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the services on ports 
8009 and 8080 are gone.

But if I directly run ".../bin/catalina.sh run" I get this: (if someone can get any 
clue from this)

[root@star bin]# ./catalina.sh run
Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
Using JAVA_HOME:   /usr/java/j2sdk1.4.1
Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry
INFO: Loading registry information
Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer

Starting service Tomcat-Standalone
Apache Tomcat/4.1.12
Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error
SEVERE: Parse Error at line 114 column 15: The content of element type "servlet" must 
match 
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),init-param*,load-on-startup?,run-as?,security-role-ref*)".
org.xml.sax.SAXParseException: The content of element type "servlet" must match 
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),init-param*,load-on-startup?,run-as?,security-role-ref*)".
at 
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:232)
at 
org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:173)
at 
org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:362)
at 
org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:296)
at 
org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.java:1953)
at 
org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:878)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDocumentFragmentScannerImpl.java:1144)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:987)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1445)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:333)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:524)
at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:580)
at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at 
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1169)
at org.apache.commons.digester.Digester.parse(Digester.java:1495)
at 
org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.java:282)
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:639)
at 
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:243)
at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3493)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:738)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347)
at org.apache.catalina.core.StandardService.start(StandardService.java:497)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2189)
at org.apache.catalina.startup.Catalina.start(Catalina.java:510)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error
SEVERE: Parse Error at line 120 

Restricting SSL Cipher Suites with Standalone Tomcat 4.1.12?

[Greg Dowd]

Can I do this?  Is it a stupid ??  Can someone point me in the right
direction?

I have Tomcat 4.1.12 running fine with JDK 1.3.1 but I'd like to restrict
the available cipher suites to the stronger sets.  I see the notes about
Apache httpd.conf and SSLCipherSuite but that doesn't work for Tomcat, does
it?

Greg Dowd
[EMAIL PROTECTED]
Staff Scientist
Symmetricom, Trusted Time Division



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: Apache 2+Tomcat 4.1.12: how to disable the Coyote HTTP connector?

[Turner, John]

He wants Ajp13Connector to be his only connector.  He wants to disable
CoyoteConnector on port 8080, but is getting an error message when he tries
to do so.

John


> -Original Message-
> From: Jerry Ford [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 02, 2003 11:30 AM
> To: Tomcat Users List
> Subject: Re: Apache 2+Tomcat 4.1.12: how to disable the Coyote HTTP
> connector?
> 
> 
> Looks like you conmmented out the wrong connector.  The one you have 
> removed is identified as the one for port 8009, which is the 
> one Apache 
> uses.  Restore that connector and comment out the one that is 
> identified 
> as for port 8080.
> 
> Jerry
> 
> Manuel González Castro wrote:
> 
> >Hi,
> >
> >I'm running Apache HTTP Server 2.0.43 + Tomcat 4.1.12 + mod_jk and
> >everything is working fine, Apache can talk to Tomcat to 
> serve *.jsp pages.
> >
> >Now I'd like to disable the default "non-SSL Coyote HTTP/1.1 
> Connector on
> >port 8080" because I don't like everybody getting into
> >http://mydomain.com:8080 and seeing the Tomcat congratulations page,
> >manager, admin page, ... I just want Tomcat to serve JSP 
> pages to Apache
> >using mod_jk.
> >
> >I commented the default Coyote HTTP/1.1 Connector and leaved 
> the AJP 1.3 as
> >the only Connector in my server.xml file:
> >
> >
> > >   port="8009" minProcessors="5" maxProcessors="75"
> >   acceptCount="10" debug="0"/>
> >
> >But when I request a JSP file to Apache, Tomcat doesn't 
> answer, I get this
> >error:
> >"Internal Server Error The server encountered an internal error or
> >misconfiguration and was unable to complete your request."
> >
> >Is there any way to prevent people from accesing 
http://mydomain:8080 and
>leave AJP 1.3 as the only Connector ?
>
>Thanks in advance!
>Manuel
>
>
>
>--
>To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>  
>


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Apache 2+Tomcat 4.1.12: how to disable the Coyote HTTP connector?

[Jerry Ford]

Looks like you conmmented out the wrong connector.  The one you have 
removed is identified as the one for port 8009, which is the one Apache 
uses.  Restore that connector and comment out the one that is identified 
as for port 8080.

Jerry

Manuel González Castro wrote:

Hi,

I'm running Apache HTTP Server 2.0.43 + Tomcat 4.1.12 + mod_jk and
everything is working fine, Apache can talk to Tomcat to serve *.jsp pages.

Now I'd like to disable the default "non-SSL Coyote HTTP/1.1 Connector on
port 8080" because I don't like everybody getting into
http://mydomain.com:8080 and seeing the Tomcat congratulations page,
manager, admin page, ... I just want Tomcat to serve JSP pages to Apache
using mod_jk.

I commented the default Coyote HTTP/1.1 Connector and leaved the AJP 1.3 as
the only Connector in my server.xml file:

   
   
  port="8009" minProcessors="5" maxProcessors="75"
  acceptCount="10" debug="0"/>

But when I request a JSP file to Apache, Tomcat doesn't answer, I get this
error:
"Internal Server Error The server encountered an internal error or
misconfiguration and was unable to complete your request."

Is there any way to prevent people from accesing http://mydomain:8080 and
leave AJP 1.3 as the only Connector ?

Thanks in advance!
Manuel



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
 



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: Apache 2+Tomcat 4.1.12: how to disable the Coyote HTTP connector?

[Turner, John]

That is how you disable the connector on 8080.  All you do is comment it
out.  My guess is that you don't have the comment marks in the right place,
breaking your server.xml file.

John


> -Original Message-
> From: Manuel González Castro [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 02, 2003 8:56 AM
> To: [EMAIL PROTECTED]
> Subject: Apache 2+Tomcat 4.1.12: how to disable the Coyote HTTP
> connector?
> 
> 
> Hi,
> 
> I'm running Apache HTTP Server 2.0.43 + Tomcat 4.1.12 + mod_jk and
> everything is working fine, Apache can talk to Tomcat to 
> serve *.jsp pages.
> 
> Now I'd like to disable the default "non-SSL Coyote HTTP/1.1 
> Connector on
> port 8080" because I don't like everybody getting into
> http://mydomain.com:8080 and seeing the Tomcat congratulations page,
> manager, admin page, ... I just want Tomcat to serve JSP 
> pages to Apache
> using mod_jk.
> 
> I commented the default Coyote HTTP/1.1 Connector and leaved 
> the AJP 1.3 as
> the only Connector in my server.xml file:
> 
> 
> port="8009" minProcessors="5" maxProcessors="75"
>acceptCount="10" debug="0"/>
> 
> But when I request a JSP file to Apache, Tomcat doesn't 
> answer, I get this
> error:
> "Internal Server Error The server encountered an internal error or
> misconfiguration and was unable to complete your request."
> 
> Is there any way to prevent people from accesing 
> http://mydomain:8080 and
> leave AJP 1.3 as the only Connector ?
> 
> Thanks in advance!
> Manuel
> 
> 
> 
> --
> To unsubscribe, e-mail:   
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Apache 2+Tomcat 4.1.12: how to disable the Coyote HTTP connector?

[Manuel González Castro]

Hi,

I'm running Apache HTTP Server 2.0.43 + Tomcat 4.1.12 + mod_jk and
everything is working fine, Apache can talk to Tomcat to serve *.jsp pages.

Now I'd like to disable the default "non-SSL Coyote HTTP/1.1 Connector on
port 8080" because I don't like everybody getting into
http://mydomain.com:8080 and seeing the Tomcat congratulations page,
manager, admin page, ... I just want Tomcat to serve JSP pages to Apache
using mod_jk.

I commented the default Coyote HTTP/1.1 Connector and leaved the AJP 1.3 as
the only Connector in my server.xml file:




But when I request a JSP file to Apache, Tomcat doesn't answer, I get this
error:
"Internal Server Error The server encountered an internal error or
misconfiguration and was unable to complete your request."

Is there any way to prevent people from accesing http://mydomain:8080 and
leave AJP 1.3 as the only Connector ?

Thanks in advance!
Manuel



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Problems with starting Tomcat 4.1.12 - PLEASE HELP

[yves lambert]

Ronin Quigley wrote:


John,

I have tried your suggesions but I think the problem is the path to Tomcat.

I am using Windows XP and the command promp automatically defaults to
C:\Documents and Settings\Go For It  Web Design>, it doesn't recognise
C:\ as a valid command. How can I get around this as Tomcat is installed
under C:\Tomcat?.

Thanks for your help

Rocket
p.s. the logs for Tomcat were empty

 

the directory you are un  doesn'r mattet as long as you set path and 
environment variables: PATH CATALINA_HOME JAVA_HOME.
if you just want to be in c:\tomcat\bin strike "cd c:\tomcat\bin" 
CATALINA_HOME will be set @ .. by the startup batch. but you still have 
to set JAVA_HOME correctly, or ot won't work.

--
\/
<>
/\



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Tomcat 4.1.12, session attributes, and hanging-up

[Bogdan Kiszka]

Something strange happens with Tomcat. It ignores session atributes.
When it starts to accept them then it hungs up after a while. It happens
to standalone version, as well as in isapi version. 

i.e. this example:
<% 
  String count = (String)session.getAttribute("numVisits");
  count = increment(count); 
  out.print("I am here  for the " + count + " time.");
  session.setAttribute("numVisits", count); 
%>

<%!
  String increment(String count) {
if (count != null)
  return Integer.toString(Integer.parseInt(count) + 1);
else
  return "1";
  }
%>

Tomcat keeps showing number 1. When it eventually starts incrementing
numVisits, hangs-up.

Session timeout is set in web.xml to 30 minutes.
Strange is, that same apps (I mean from the same physical location)
launched from other JSP container (i.e. ServletExec) work fine. So I
think the problem is not in apps but in Tomcat.

Any ideas why? Thanks in advance. 
Bogdan


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Help needed to run Tomcat 4.1.12

[Turner, John]

Thanks.  I couldn't remember the equivalent of "$CATALINA_HOME" on Windows.
LOL

John


-Original Message-
From: Paul Yunusov [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, December 18, 2002 7:35 PM
To: Tomcat Users List
Subject: Re: Help needed to run Tomcat 4.1.12

On Wednesday 18 December 2002 07:13 pm, Turner, John wrote:
> Agreedavoid spaces in pathnames if you can.
>
> As an aside, there is no reason to switch directories to start Tomcat.
You
> can do so by typing something like c:\tomcat\bin\startup.bat from any
> command prompt in Windows.
>
> John

Or, more generically, you can type %CATALINA_HOME%/bin/startup.bat at the 
prompt for the same result (I am only having a Windows flashback tonight, so

again, if my memory doesn't betray me, the above should be correct. 
Otherwise, it's just a fantasy induced by UNIX).

Paul


>
>
> -Original Message-
> From: Paul Yunusov [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 18, 2002 7:04 PM
> To: Tomcat Users List
> Subject: Re: Help needed to run Tomcat 4.1.12
>
> On Wednesday 18 December 2002 06:27 pm, Ronin Quigley wrote:
> > I am running Windows XP and have done the following:
> >   a.. Installed Jave SDK and set the path variable to
> > stemRoot%\System32\Wbem;C:Java\bin; b.. Downloaded release version 
> > 4.1.12 of Tomcat
> >   c.. Set the variable JAVA HOME=C:\JAVA
> >   d.. Set the variable CATALINA_HOME= C:\TOMCAT\JAKARTA-TOMCAT 4.1.12
> >   e.. Tested  the above by doing the ECHO test and they were fine.
> > The command prompt in Windows XP automatically defaults to C:\Documents
>
> and
>
> > Settings\Go For It Web Design>, how do I get a C:\ prompt? And once I
get
>
> a
>
> > C:\ prompt can I start it by the following?
> >
> > C:\
> > cd tomcat\jakarta-tomcat 4.1.12\bin
> > startup.bat
> >
> > Any help would be much appreciated.
> >
> > Rocket
>
> To change the working directory to C: type C:\ and press enter in the
> command
> prompt (if my memory doesn't betray me - my Windows days are long gone).
> Your
> steps to start tomcat seem be correct but paths and names in the
> description
>
> of environment variables are a mess (JAVA_HOME should have  the "_",
> "SystemRoot" instead of "stemRoot", C: must be followed by a "\" in paths,
> there is a "-" instead of a space between "jakarta-tomcat" and "4.1.12" in
> the standard distribution, at least on Linux). I attribute this chaos to
> fast
> typing but I'd double check if I were you. My Windows experience taught me
> to
> avoid spaces in paths also.
> HTH,
> Paul

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002
 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Help needed to run Tomcat 4.1.12

[Paul Yunusov]

On Wednesday 18 December 2002 07:13 pm, Turner, John wrote:
> Agreedavoid spaces in pathnames if you can.
>
> As an aside, there is no reason to switch directories to start Tomcat.  You
> can do so by typing something like c:\tomcat\bin\startup.bat from any
> command prompt in Windows.
>
> John

Or, more generically, you can type %CATALINA_HOME%/bin/startup.bat at the 
prompt for the same result (I am only having a Windows flashback tonight, so 
again, if my memory doesn't betray me, the above should be correct. 
Otherwise, it's just a fantasy induced by UNIX).

Paul


>
>
> -Original Message-
> From: Paul Yunusov [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 18, 2002 7:04 PM
> To: Tomcat Users List
> Subject: Re: Help needed to run Tomcat 4.1.12
>
> On Wednesday 18 December 2002 06:27 pm, Ronin Quigley wrote:
> > I am running Windows XP and have done the following:
> >   a.. Installed Jave SDK and set the path variable to
> > stemRoot%\System32\Wbem;C:Java\bin; b.. Downloaded release version 
> > 4.1.12 of Tomcat
> >   c.. Set the variable JAVA HOME=C:\JAVA
> >   d.. Set the variable CATALINA_HOME= C:\TOMCAT\JAKARTA-TOMCAT 4.1.12
> >   e.. Tested  the above by doing the ECHO test and they were fine.
> > The command prompt in Windows XP automatically defaults to C:\Documents
>
> and
>
> > Settings\Go For It Web Design>, how do I get a C:\ prompt? And once I get
>
> a
>
> > C:\ prompt can I start it by the following?
> >
> > C:\
> > cd tomcat\jakarta-tomcat 4.1.12\bin
> > startup.bat
> >
> > Any help would be much appreciated.
> >
> > Rocket
>
> To change the working directory to C: type C:\ and press enter in the
> command
> prompt (if my memory doesn't betray me - my Windows days are long gone).
> Your
> steps to start tomcat seem be correct but paths and names in the
> description
>
> of environment variables are a mess (JAVA_HOME should have  the "_",
> "SystemRoot" instead of "stemRoot", C: must be followed by a "\" in paths,
> there is a "-" instead of a space between "jakarta-tomcat" and "4.1.12" in
> the standard distribution, at least on Linux). I attribute this chaos to
> fast
> typing but I'd double check if I were you. My Windows experience taught me
> to
> avoid spaces in paths also.
> HTH,
> Paul

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: Help needed to run Tomcat 4.1.12

[Turner, John]

Agreedavoid spaces in pathnames if you can.

As an aside, there is no reason to switch directories to start Tomcat.  You
can do so by typing something like c:\tomcat\bin\startup.bat from any
command prompt in Windows.

John


-Original Message-
From: Paul Yunusov [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, December 18, 2002 7:04 PM
To: Tomcat Users List
Subject: Re: Help needed to run Tomcat 4.1.12

On Wednesday 18 December 2002 06:27 pm, Ronin Quigley wrote:
> I am running Windows XP and have done the following:
>   a.. Installed Jave SDK and set the path variable to
> stemRoot%\System32\Wbem;C:Java\bin; b.. Downloaded release version  4.1.12
> of Tomcat
>   c.. Set the variable JAVA HOME=C:\JAVA
>   d.. Set the variable CATALINA_HOME= C:\TOMCAT\JAKARTA-TOMCAT 4.1.12
>   e.. Tested  the above by doing the ECHO test and they were fine.
> The command prompt in Windows XP automatically defaults to C:\Documents
and
> Settings\Go For It Web Design>, how do I get a C:\ prompt? And once I get
a
> C:\ prompt can I start it by the following?
>
> C:\
> cd tomcat\jakarta-tomcat 4.1.12\bin
> startup.bat
>
> Any help would be much appreciated.
>
> Rocket

To change the working directory to C: type C:\ and press enter in the
command 
prompt (if my memory doesn't betray me - my Windows days are long gone).
Your 
steps to start tomcat seem be correct but paths and names in the description

of environment variables are a mess (JAVA_HOME should have  the "_", 
"SystemRoot" instead of "stemRoot", C: must be followed by a "\" in paths, 
there is a "-" instead of a space between "jakarta-tomcat" and "4.1.12" in 
the standard distribution, at least on Linux). I attribute this chaos to
fast 
typing but I'd double check if I were you. My Windows experience taught me
to 
avoid spaces in paths also.
HTH,
Paul

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002
 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Help needed to run Tomcat 4.1.12

[Paul Yunusov]

On Wednesday 18 December 2002 06:27 pm, Ronin Quigley wrote:
> I am running Windows XP and have done the following:
>   a.. Installed Jave SDK and set the path variable to
> stemRoot%\System32\Wbem;C:Java\bin; b.. Downloaded release version  4.1.12
> of Tomcat
>   c.. Set the variable JAVA HOME=C:\JAVA
>   d.. Set the variable CATALINA_HOME= C:\TOMCAT\JAKARTA-TOMCAT 4.1.12
>   e.. Tested  the above by doing the ECHO test and they were fine.
> The command prompt in Windows XP automatically defaults to C:\Documents and
> Settings\Go For It Web Design>, how do I get a C:\ prompt? And once I get a
> C:\ prompt can I start it by the following?
>
> C:\
> cd tomcat\jakarta-tomcat 4.1.12\bin
> startup.bat
>
> Any help would be much appreciated.
>
> Rocket

To change the working directory to C: type C:\ and press enter in the command 
prompt (if my memory doesn't betray me - my Windows days are long gone). Your 
steps to start tomcat seem be correct but paths and names in the description 
of environment variables are a mess (JAVA_HOME should have  the "_", 
"SystemRoot" instead of "stemRoot", C: must be followed by a "\" in paths, 
there is a "-" instead of a space between "jakarta-tomcat" and "4.1.12" in 
the standard distribution, at least on Linux). I attribute this chaos to fast 
typing but I'd double check if I were you. My Windows experience taught me to 
avoid spaces in paths also.
HTH,
Paul

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Help needed to run Tomcat 4.1.12

[Ronin Quigley]

I am running Windows XP and have done the following:
  a.. Installed Jave SDK and set the path variable to 
stemRoot%\System32\Wbem;C:Java\bin;
  b.. Downloaded release version  4.1.12 of Tomcat
  c.. Set the variable JAVA HOME=C:\JAVA
  d.. Set the variable CATALINA_HOME= C:\TOMCAT\JAKARTA-TOMCAT 4.1.12
  e.. Tested  the above by doing the ECHO test and they were fine.   
The command prompt in Windows XP automatically defaults to C:\Documents and 
Settings\Go For It Web Design>, how do I get a C:\ prompt?
And once I get a C:\ prompt can I start it by the following?

C:\
cd tomcat\jakarta-tomcat 4.1.12\bin
startup.bat

Any help would be much appreciated.

Rocket

mod_jk2 with Apache2 & JBoss/Tomcat 4.1.12 bundle?

[Andrzej Jan Taramina]

Has anyone managed to get the jk2 connector working with the bundled 
JBoss/Tomcat 4.1.12 release?

Any tricks/hints?  We're having trouble with it...

Thanks!

Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Apache2, mod_jk2, Tomcat-4.1.12 and jni integration

[Anthony Marlowe]

Hi,

On a Unix Installation  with Mac OS X 10.2.2, java 1.3.1, Apache-2.0.43  
and Tomcat-4.1.2 installed I'm have having problems getting jni to  
properly initilize. I have the same problems on Solaris 5.7 system with  
the identical setup using java 1.4.1_01. During the Apache2 startup  
tomcat and apache startup correctly, however the jni worker is not  
initiated correctly see the Apache2 error_log below.

I needed to change the OPT=-Djava.class.path separator from a ";" to a  
":". The mod_jk2.so and the jkjni.so were built from the  
jakarta-tomcat-connectors-jk2-2.0.2-src with dso and jni enabled. Jni  
was also enabled for the build of httpd-2.0.43.

Any ideas would be appreciated. Thank you in advance.

The Apache stderr.log:

TomcatStarter: main()
Try  org.apache.tomcat.startup.Main
Try  org.apache.catalina.startup.BootstrapService
Starting org.apache.catalina.startup.BootstrapService
Created catalinaLoader in:  
/Volumes/Java_Development/jakarta-tomcat-4.1.12/server/lib
[INFO] Registry - -Loading registry information
[INFO] Registry - -Creating new Registry instance
[INFO] Registry - -Creating MBeanServer
[INFO] AprImpl - -JK2: Initialized apr
[INFO] ChannelJni - -JK2: listening on channel.jni:jni
[INFO] JkMain - -Jk running ID=0 time=6/28   
config=/Volumes/Java_Development/jakarta-tomcat-4.1.12/conf/ 
jk2.properties
TomcatStarter: main()
Try  org.apache.tomcat.startup.Main
Try  org.apache.catalina.startup.BootstrapService
Starting org.apache.catalina.startup.BootstrapService

An portion of the stdout.log:

 Resolving to alternate DTD  
'jar:file:/Volumes/Java_Development/jakarta-tomcat-4.1.12/webapps/ 
struts-upload/WEB-INF/lib/struts.jar!/org/apache/struts/resources/web- 
app_2_2.dtd'
Call  
org.apache.struts.action.ActionServlet.addServletMapping(action/ 
java.lang.String,*.do/java.lang.String)
Bootstrap: Service started
TomcatStarter: Done


The Apache2 error log follows the jk2.properties listing.

The jk2.properties file:

jk2.properties:

handler.list=apr,request,container,channelJni
#
# Override the default port for the socketChannel
# channelSocket.port=8009
# Default:
# channelUnix.file=${jkHome}/work/jk2.socket
# Just to check if the the config  is working
shm.file=/Volumes/Java_Development/jakarta-tomcat-4.1.12/work/jk2.shm

# In order to enable jni use any channelJni directive
channelJni.disabled = 0
# And one of the following directives:

# apr.NativeSo=/Library/Apache2/modules/jkjni.so
# apr.jniModeSo=/Library/Apache2/modules/mod_jk2.so

# If set to inprocess the mod_jk2 will Register natives itself
# This will enable the starting of the Tomcat from mod_jk2
apr.jniModeSo=inproces


Here is the output from the Apache2 error_log, it is a bit long, but I  
think necessary to understand what is occurring during the startup  
process.

[Wed Dec 18 12:13:18 2002] [notice] uriEnv.setAttribute() the worker  
directive is deprecated. Use 'group' instead.
[Wed Dec 18 12:13:18 2002] [notice] Digest: generating secret for  
digest authentication ...
[Wed Dec 18 12:13:18 2002] [notice] Digest: done
[Wed Dec 18 12:13:18 2002] [notice] Apache/2.0.43 (Unix)  
mod_perl/1.99_07-dev Perl/v5.8.0 mod_jk2/2.0.2 DAV/2 PHP/4.2.3  
configured -- resuming normal operations
[Wed Dec 18 12:13:18 2002] [notice] jk2_init() Found child 5525 in  
scoreboard slot 2
[Wed Dec 18 12:13:18 2002] [notice] jk2_init() Found child 5526 in  
scoreboard slot 3
[Wed Dec 18 12:13:18 2002] [notice] jk2_init() Found child 5523 in  
scoreboard slot 0
[Wed Dec 18 12:13:18 2002] [notice] vm.init(): Jni lib:  
/System/Library/Frameworks/JavaVM.framework/Versions/Current/JavaVM
[Wed Dec 18 12:13:18 2002] [notice] jk2_init() Found child 5527 in  
scoreboard slot 4
[Wed Dec 18 12:13:18 2002] [notice] vm.init(): Jni lib:  
/System/Library/Frameworks/JavaVM.framework/Versions/Current/JavaVM
[Wed Dec 18 12:13:18 2002] [notice] jk2_init() Found child 5524 in  
scoreboard slot 1
[Wed Dec 18 12:13:18 2002] [notice] vm.init(): Jni lib:  
/System/Library/Frameworks/JavaVM.framework/Versions/Current/JavaVM
[Wed Dec 18 12:13:18 2002] [notice] vm.init(): Jni lib:  
/System/Library/Frameworks/JavaVM.framework/Versions/Current/JavaVM
[Wed Dec 18 12:13:18 2002] [notice] vm.init(): Jni lib:  
/System/Library/Frameworks/JavaVM.framework/Versions/Current/JavaVM
[Wed Dec 18 12:13:19 2002] [notice] vm.open2() done
[Wed Dec 18 12:13:19 2002] [error] workerEnv.initChannel() init failed  
for channel.jni:jni
[Wed Dec 18 12:13:19 2002] [notice] workerJni.Init() Skipping  
initialization for the 2 5525
[Wed Dec 18 12:13:19 2002] [error] workerEnv.initWorkers() init failed  
for worker.jni:onStartup
[Wed Dec 18 12:13:19 2002] [notice] workerJni.Init() Skipping  
initialization for the 2 5525
[Wed Dec 18 12:13:19 2002] [error] workerEnv.initWorkers() init failed  
for worker.jni:onShutdown
[Wed Dec 18 12:13:19 2002] [notice] uriMap.init() adding context / for  
/jkstatus/*
[Wed Dec 18 12:13:19 2002] [notice]

Re: Cannot compile Tomcat 4.1.12 from source

[Bill Barker]

It looks like you are compiling against the JSR-154 (aka 2.4 Spec)
servlet.jar.  You need to use the 2.3 Spec one.  Your 'build.properties'
file should have something like:

# - Jakarta Servlet API Classes (Servlet 2.3 / JSP 1.2) -
servlet.home=${base.path}/jakarta-servletapi-4
servlet.lib=${servlet.home}/lib
servlet.jar=${servlet.lib}/servlet.jar
servlet.loc=jakarta-servletapi-4

in it for the 'ant download' target to get the correct version.

"Paul Downs" <[EMAIL PROTECTED]> wrote in message
20021217171545.GB22574@u4ia">news:20021217171545.GB22574@u4ia...
>
> Hi,
>   I am having trouble compiling Tomcat 4.1.12 from source, I am using Suns
> jsdk 1.4.1.
>
> build-main:
>  [echo] - Java-utils -
>  [echo] -- puretls.present = ${puretls.present}
>  [echo] -- jsse.present = true
>  [echo] -- commons-logging = true
>  [echo] -- jmx = ${jmx.present}
> /usr/local/src/tomcat/mx4j-1.1/lib/mx4j-jmx.jar
>
> build-catalina:
> [javac] Compiling 122 source files to
>
/usr/local/src/tomcat/jakarta-tomcat-4.1.12-src/catalina/build/server/classe
s
> [javac] This version of java does not support the classic compiler;
> upgrading to modern
> [javac]
>
/usr/local/src/tomcat/jakarta-tomcat-4.1.12-src/catalina/src/share/org/apach
e/catalina/session/StandardSessionFacade.java:97:
> org.apache.catalina.session.StandardSessionFacade should be declared
> abstract; it does not define logout() in
> org.apache.catalina.session.StandardSessionFacade
> [javac] public class StandardSessionFacade
> [javac]^
> [javac]
>
/usr/local/src/tomcat/jakarta-tomcat-4.1.12-src/catalina/src/share/org/apach
e/catalina/session/StandardSession.java:121:
> org.apache.catalina.session.StandardSession should be declared abstract;
it
> does not define logout() in org.apache.catalina.session.StandardSession
> [javac] class StandardSession
> [javac] ^
> [javac]
>
/usr/local/src/tomcat/jakarta-tomcat-4.1.12-src/catalina/src/share/org/apach
e/catalina/connector/HttpResponseBase.java:111:
> org.apache.catalina.connector.HttpResponseBase should be declared
abstract;
> it does not define setCharacterEncoding(java.lang.String) in
> org.apache.catalina.connector.ResponseBase
> [javac] public class HttpResponseBase
> [javac]^
> [javac]
>
/usr/local/src/tomcat/jakarta-tomcat-4.1.12-src/catalina/src/share/org/apach
e/catalina/connector/ResponseFacade.java:86:
> org.apache.catalina.connector.ResponseFacade should be declared abstract;
it
> does not define setCharacterEncoding(java.lang.String) in
> org.apache.catalina.connector.ResponseFacade
> [javac] public class ResponseFacade implements ServletResponse {
> [javac]^
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -deprecation for details.
> [javac] 4 errors
>
>   Everything has been smooth sailing.
>
>   Any ideas?
>
> Thanks,
>
> Paul





--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

latest connector for IIS with Tomcat 4.1.12

[Tuan H. Le]

Hi,

Do you know where I can download the latest connector for IIS (5.0) with Tomcat 4.1.12?

Also, we're experiencing a problem that hang Tomcat when the current connection 
reached around 256 connections. Should we upgrade to Tomcat 4.1.17?

Thanks,
Tuan

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: SSL, IIS, and Tomcat 4.1.12

[Michael McLawhorn]

I just wanted to follow up on this.  When I tried installing 4.1.17 over my 
existing 4.1.12, it cleared the problem right up.  I can't say how much of a 
relief this finally is.


From: "Michael McLawhorn" <[EMAIL PROTECTED]>
Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: SSL, IIS, and Tomcat 4.1.12
Date: Tue, 17 Dec 2002 11:16:10 -0600


I have spent the last several hours hacking around in the archives and have 
seen the same question asked several times, but no clear answer given.  I 
have also spent about ten hours with various configuration tweaks.

I am trying to get Tomcat to act as an application server behind IIS.
With http connections, this has been working without difficulty.  I want to 
modify it to work with SSL.  I can get Tomcat to server SSL w/o difficulty, 
I can get IIS to serve SSL without a problem.  However, when I try to use 
https://myserver/mywebapp, the browser hangs indefinitely.  Sometimes it 
returns after several minutes with a page with all links of the form 
http://myserver:443/*.  Viewing the logfiles, it appears that when an 
https:// request is initiated, the web app is running without problems and 
the redirector is running without problems.

So why is the browser hanging, and what can I do to fix the configuration?

Mike McLawhorn



_
The new MSN 8: advanced junk mail protection and 2 months FREE* 
http://join.msn.com/?page=features/junkmail


--
To unsubscribe, e-mail:   
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: 
<mailto:[EMAIL PROTECTED]>


_
Add photos to your messages with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: Virtual Domains with Tomcat 4.1.12 Standalone

[Hari Venkatesan]

Congratulations Norment. R u using IIS?

Hari

-Original Message-
From: J. Norment [mailto:[EMAIL PROTECTED]] 
Sent: Tuesday, December 17, 2002 1:45 PM
To: Tomcat Users List
Subject: RE: Virtual Domains with Tomcat 4.1.12 Standalone

Just wanted to let you know: I got it working.  I ended up uninstalling Tomcat 4.1.12 
and installing Tomcat 4.1.17, and it worked almost from the start.  (I'm guessing that 
I somehow corrupted my server.xml file.)  Thanks for all your help!


On Tue, 17 Dec 2002 11:19:56 -0500, Turner, John wrote:
>
>If you post your server.xml, someone will look at it.  I can't
>promise I
>will, as time is everything, but someone will.  If you could remove
>the
>comments from it and post an uncommented version, that would make it
>smaller
>and easier to scan.
>
>John
>
>
>>-Original Message-
>>From: J. Norment [mailto:[EMAIL PROTECTED]]
>>Sent: Tuesday, December 17, 2002 11:12 AM
>>To: Tomcat Users List
>>Subject: RE: Virtual Domains with Tomcat 4.1.12 Standalone
>>
>>
>>Got it, John.  Thanks for your time. ( not being sarcastic...
>>forgot to thank you earlier. )
>>( For the record, I only posted the small snippet because
>>that was all that I changed from "out of the box" )
>>
>>I'll try to verify the XML tags now.
>>( I've thought about this before, but I'll look at it again. )
>>
>>I thought that maybe I had something screwy going on with
>>part of the request being blocked, but I honestly don't know
>>that part intimately enough to look at it and verify that
>>everything is coming through ok.
>>
>>
>>On Tue, 17 Dec 2002 11:03:06 -0500, Turner, John wrote:
>>>
>>>No, it is not.  Leave defaultHost alone.
>>>
>>>Setup a Host element for host0.com and host1.com.
>>>
>>>If this is not working, either post your entire server.xml or post
>>>log file
>>>snippets with error messages.  XML files are sensitive to properly
>>>closed
>>>tags and elements...including just a small snippet of your
>>>server.xml file
>>>doesn't let anyone verify that you've positioned and closed the
>>>new
>>>tags
>>>correctly because we can't see any of the other tags.
>>>
>>>My apologies, but this is starting to get fairly tedious.  Adding
>>>a
>>>new Host
>>>element is a trivial exercise, all you have to do is make sure you
>>>position
>>>it correctly and close it correctly.  There's really nothing else
>>>to
>>>do.  If
>>>you have to, copy server.xml to server-work.xml, delete all of the
>>>comments
>>>and other extra information, and work with the resulting smaller
>>>file until
>>>you get the new elements closed and positioned correctly.
>>>Server.xml is no
>>>different than and HTML file...position and close everything
>>>properly, and
>>>it works.
>>>
>>>John
>>>
>>>>-Original Message-
>>>>From: J. Norment [mailto:[EMAIL PROTECTED]]
>>>>Sent: Tuesday, December 17, 2002 10:36 AM
>>>>To: Tomcat Users List
>>>>Subject: RE: Virtual Domains with Tomcat 4.1.12 Standalone
>>>>
>>>>
>>>>Hari:
>>>>
>>>>Thanks for the response.
>>>>( For that matter, thanks for everyone's response so far... )
>>>>
>>>>I want the behavior to be:
>>>>
>>>>http://localhost - loads up the default welcome page,
>>>>root/index.jsp
>>>>http://host0.com - loads up host0's index page
>>>>http://host1.com - loads up host1's index page
>>>>
>>>>Is changing the default host part of the solution?
>>>>
>>>>
>>>>
>>>>On Tue, 17 Dec 2002 10:22:20 -0500, Hari Venkatesan wrote:
>>>>>You have two >>>>host. Did you change ">>>>defaultHost="localhost" debug="99">" to reflect "host0.com" in
>>>>>the
>>>>>defaultHost
>>>>>
>>>>>Hari
>>>>>
>>>>>-Original Message-
>>>>>From: J. Norment [mailto:[EMAIL PROTECTED]]
>>>>>Sent: Tuesday, December 17, 2002 10:15 AM
>>>>>To: Tomcat Users List
>>>>>Subject: RE: Virtual Domains with Tomcat 4.1.12 Standalone
>>>>>
>>>>>This is the change that I had made to the server.xml file:
>>>&g