You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Peng Tuck Kwok <pe...@makmal.net> on 2002/12/03 05:09:42 UTC
Datasource and Web.xml
If a web application uses a jndi datasource, should the web.xml contain
the definition for the datasource before deployment (that is in the war
file) or after deployment (that is after the war file has been deployed)
? This sounds strange as I was having problems with this in tomcat
4.1.12 , where Tomcat could not start if the there was a resource
definition in the web.xml. Of course I can't create a resource for the
context using the admin interface since the context doesn't exist yet.
I've used Sun one server and all seems ok so what is the correct
sequence for doing things in tomcat?
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: SocketException
Posted by maninder s batth <an...@netscape.net>.
netstat -a -p should do it , if you are from unix world.download nmap
for windows . that will give you process and port information
just use keywords nmap for windows in google and ull get it
Ram Kochhar wrote:
>Hi,
> I just installed the tomcat and have not done anything except to try to
>run start.bat. My operating system is
> windows 98. How do I found out about the port or another process. I also
>installed microsoft network
> protocal so that TCP/IP is installed but it did not help. Tomcat version
>4.1.9. Thanks.
>
>
>Ram Kochhar
>
>----- Original Message -----
>From: "Paul Campbell" <se...@halcyon.com>
>To: "Tomcat Users List" <to...@jakarta.apache.org>
>Sent: Monday, December 02, 2002 10:32 PM
>Subject: Re: SocketException
>
>
>
>
>>I have jdk1.4 and tomcat 4.1 and it runs with out a problem.
>>
>>Did you make some changes to a config file?
>>
>>Did you invoke some servlet, of jsp that led to the exception?
>>
>>Is there another process that might be using the same port?
>>
>>At 08:46 PM 12/2/02 -0800, you wrote:
>>
>>
>>>Hi,
>>> I have installed tomcat 4.1 and I get the following SocketException
>>>
>>>
>error
>
>
>>>when I try to start the server. I will
>>>appreciate any help. I have a stand alone machine with no modem or
>>>
>>>
>network
>
>
>>>card with jdk1.4.Thanks
>>>
>>>
>>>Ram Kochhar
>>>
>>>r.kochhar01@att.net
>>>
>>>D:\Tomcat 4.1\bin>catalina.bat run
>>>Using CATALINA_BASE: d:\tomcat~1.1
>>>Using CATALINA_HOME: d:\tomcat~1.1
>>>Using CATALINA_TMPDIR: d:\tomcat~1.1\temp
>>>Using JAVA_HOME: d:\jdk1.4
>>>Nov 30, 2002 9:43:34 PM org.apache.commons.modeler.Registry loadRegistry
>>>INFO: Loading registry information
>>>Nov 30, 2002 9:43:34 PM org.apache.commons.modeler.Registry getRegistry
>>>INFO: Creating new Registry instance
>>>Nov 30, 2002 9:43:37 PM org.apache.commons.modeler.Registry getServer
>>>INFO: Creating MBeanServer
>>>Nov 30, 2002 9:43:40 PM org.apache.coyote.http11.Http11Protocol init
>>>SEVERE: Error initializing endpoint
>>>java.net.SocketException: Socket type not supported: create
>>> at java.net.ServerSocket.createImpl(ServerSocket.java:244)
>>> at java.net.ServerSocket.getImpl(ServerSocket.java:202)
>>> at java.net.ServerSocket.bind(ServerSocket.java:308)
>>> at java.net.ServerSocket.bind(ServerSocket.java:266)
>>> at java.net.ServerSocket.<init>(ServerSocket.java:182)
>>> at java.net.ServerSocket.<init>(ServerSocket.java:138)
>>> at
>>>org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(De
>>>faultServerSocketFactory.java:96)
>>> at
>>>org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoi
>>>nt.java:263)
>>> at
>>>org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:150)
>>>
>>> at
>>>org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.
>>>java:1002)
>>> at
>>>org.apache.catalina.core.StandardService.initialize(StandardService.j
>>>ava:579)
>>> at
>>>org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
>>>a:2244)
>>> at org.apache.catalina.startup.Catalina.start(Catalina.java:509)
>>> 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(DelegatingMethodAcces
>>>sorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:324)
>>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
>>>
>>>Catalina.start: LifecycleException: Protocol handler initialization
>>>
>>>
>failed:
>
>
>>>jav
>>>a.net.SocketException: Socket type not supported: create
>>>LifecycleException: Protocol handler initialization failed:
>>>java.net.SocketExce
>>>ption: Socket type not supported: create
>>> at
>>>org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.
>>>java:1004)
>>> at
>>>org.apache.catalina.core.StandardService.initialize(StandardService.j
>>>ava:579)
>>> at
>>>org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
>>>a:2244)
>>> at org.apache.catalina.startup.Catalina.start(Catalina.java:509)
>>> 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(DelegatingMethodAcces
>>>sorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:324)
>>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
>>>Catalina.stop: LifecycleException: This server has not yet been started
>>>LifecycleException: This server has not yet been started
>>> at
>>>org.apache.catalina.core.StandardServer.stop(StandardServer.java:2211
>>>)
>>> at org.apache.catalina.startup.Catalina.start(Catalina.java:541)
>>> 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(DelegatingMethodAcces
>>>sorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:324)
>>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
>>>
>>>
>>>
>>>--
>>>To unsubscribe, e-mail:
>>>
>>>
><ma...@jakarta.apache.org>
>
>
>>>For additional commands, e-mail:
>>>
>>>
><ma...@jakarta.apache.org>
>
>
>>--
>>To unsubscribe, e-mail:
>>
>>
><ma...@jakarta.apache.org>
>
>
>>For additional commands, e-mail:
>>
>>
><ma...@jakarta.apache.org>
>
>
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>
--
Your favorite stores, helpful shopping tools and great gift ideas.
Experience the convenience of buying online with Shop@Netscape!
http://shopnow.netscape.com/
Re: SocketException
Posted by Ram Kochhar <r....@worldnet.att.net>.
Hi,
I just installed the tomcat and have not done anything except to try to
run start.bat. My operating system is
windows 98. How do I found out about the port or another process. I also
installed microsoft network
protocal so that TCP/IP is installed but it did not help. Tomcat version
4.1.9. Thanks.
Ram Kochhar
----- Original Message -----
From: "Paul Campbell" <se...@halcyon.com>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Monday, December 02, 2002 10:32 PM
Subject: Re: SocketException
>
> I have jdk1.4 and tomcat 4.1 and it runs with out a problem.
>
> Did you make some changes to a config file?
>
> Did you invoke some servlet, of jsp that led to the exception?
>
> Is there another process that might be using the same port?
>
> At 08:46 PM 12/2/02 -0800, you wrote:
> >Hi,
> > I have installed tomcat 4.1 and I get the following SocketException
error
> >when I try to start the server. I will
> >appreciate any help. I have a stand alone machine with no modem or
network
> >card with jdk1.4.Thanks
> >
> >
> >Ram Kochhar
> >
> >r.kochhar01@att.net
> >
> > D:\Tomcat 4.1\bin>catalina.bat run
> >Using CATALINA_BASE: d:\tomcat~1.1
> >Using CATALINA_HOME: d:\tomcat~1.1
> >Using CATALINA_TMPDIR: d:\tomcat~1.1\temp
> >Using JAVA_HOME: d:\jdk1.4
> >Nov 30, 2002 9:43:34 PM org.apache.commons.modeler.Registry loadRegistry
> >INFO: Loading registry information
> >Nov 30, 2002 9:43:34 PM org.apache.commons.modeler.Registry getRegistry
> >INFO: Creating new Registry instance
> >Nov 30, 2002 9:43:37 PM org.apache.commons.modeler.Registry getServer
> >INFO: Creating MBeanServer
> >Nov 30, 2002 9:43:40 PM org.apache.coyote.http11.Http11Protocol init
> >SEVERE: Error initializing endpoint
> >java.net.SocketException: Socket type not supported: create
> > at java.net.ServerSocket.createImpl(ServerSocket.java:244)
> > at java.net.ServerSocket.getImpl(ServerSocket.java:202)
> > at java.net.ServerSocket.bind(ServerSocket.java:308)
> > at java.net.ServerSocket.bind(ServerSocket.java:266)
> > at java.net.ServerSocket.<init>(ServerSocket.java:182)
> > at java.net.ServerSocket.<init>(ServerSocket.java:138)
> > at
> >org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(De
> >faultServerSocketFactory.java:96)
> > at
> >org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoi
> >nt.java:263)
> > at
> >org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:150)
> >
> > at
> >org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.
> >java:1002)
> > at
> >org.apache.catalina.core.StandardService.initialize(StandardService.j
> >ava:579)
> > at
> >org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
> >a:2244)
> > at org.apache.catalina.startup.Catalina.start(Catalina.java:509)
> > 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(DelegatingMethodAcces
> >sorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:324)
> > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
> >
> >Catalina.start: LifecycleException: Protocol handler initialization
failed:
> >jav
> >a.net.SocketException: Socket type not supported: create
> >LifecycleException: Protocol handler initialization failed:
> >java.net.SocketExce
> >ption: Socket type not supported: create
> > at
> >org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.
> >java:1004)
> > at
> >org.apache.catalina.core.StandardService.initialize(StandardService.j
> >ava:579)
> > at
> >org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
> >a:2244)
> > at org.apache.catalina.startup.Catalina.start(Catalina.java:509)
> > 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(DelegatingMethodAcces
> >sorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:324)
> > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
> >Catalina.stop: LifecycleException: This server has not yet been started
> >LifecycleException: This server has not yet been started
> > at
> >org.apache.catalina.core.StandardServer.stop(StandardServer.java:2211
> >)
> > at org.apache.catalina.startup.Catalina.start(Catalina.java:541)
> > 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(DelegatingMethodAcces
> >sorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:324)
> > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
> >
> >
> >
> >--
> >To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> >For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: SocketException
Posted by Paul Campbell <se...@halcyon.com>.
I have jdk1.4 and tomcat 4.1 and it runs with out a problem.
Did you make some changes to a config file?
Did you invoke some servlet, of jsp that led to the exception?
Is there another process that might be using the same port?
At 08:46 PM 12/2/02 -0800, you wrote:
>Hi,
> I have installed tomcat 4.1 and I get the following SocketException error
>when I try to start the server. I will
>appreciate any help. I have a stand alone machine with no modem or network
>card with jdk1.4.Thanks
>
>
>Ram Kochhar
>
>r.kochhar01@att.net
>
> D:\Tomcat 4.1\bin>catalina.bat run
>Using CATALINA_BASE: d:\tomcat~1.1
>Using CATALINA_HOME: d:\tomcat~1.1
>Using CATALINA_TMPDIR: d:\tomcat~1.1\temp
>Using JAVA_HOME: d:\jdk1.4
>Nov 30, 2002 9:43:34 PM org.apache.commons.modeler.Registry loadRegistry
>INFO: Loading registry information
>Nov 30, 2002 9:43:34 PM org.apache.commons.modeler.Registry getRegistry
>INFO: Creating new Registry instance
>Nov 30, 2002 9:43:37 PM org.apache.commons.modeler.Registry getServer
>INFO: Creating MBeanServer
>Nov 30, 2002 9:43:40 PM org.apache.coyote.http11.Http11Protocol init
>SEVERE: Error initializing endpoint
>java.net.SocketException: Socket type not supported: create
> at java.net.ServerSocket.createImpl(ServerSocket.java:244)
> at java.net.ServerSocket.getImpl(ServerSocket.java:202)
> at java.net.ServerSocket.bind(ServerSocket.java:308)
> at java.net.ServerSocket.bind(ServerSocket.java:266)
> at java.net.ServerSocket.<init>(ServerSocket.java:182)
> at java.net.ServerSocket.<init>(ServerSocket.java:138)
> at
>org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(De
>faultServerSocketFactory.java:96)
> at
>org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoi
>nt.java:263)
> at
>org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:150)
>
> at
>org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.
>java:1002)
> at
>org.apache.catalina.core.StandardService.initialize(StandardService.j
>ava:579)
> at
>org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
>a:2244)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:509)
> 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(DelegatingMethodAcces
>sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
>
>Catalina.start: LifecycleException: Protocol handler initialization failed:
>jav
>a.net.SocketException: Socket type not supported: create
>LifecycleException: Protocol handler initialization failed:
>java.net.SocketExce
>ption: Socket type not supported: create
> at
>org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.
>java:1004)
> at
>org.apache.catalina.core.StandardService.initialize(StandardService.j
>ava:579)
> at
>org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
>a:2244)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:509)
> 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(DelegatingMethodAcces
>sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
>Catalina.stop: LifecycleException: This server has not yet been started
>LifecycleException: This server has not yet been started
> at
>org.apache.catalina.core.StandardServer.stop(StandardServer.java:2211
>)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:541)
> 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(DelegatingMethodAcces
>sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
>
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
SocketException
Posted by Ram Kochhar <r....@worldnet.att.net>.
Hi,
I have installed tomcat 4.1 and I get the following SocketException error
when I try to start the server. I will
appreciate any help. I have a stand alone machine with no modem or network
card with jdk1.4.Thanks
Ram Kochhar
r.kochhar01@att.net
D:\Tomcat 4.1\bin>catalina.bat run
Using CATALINA_BASE: d:\tomcat~1.1
Using CATALINA_HOME: d:\tomcat~1.1
Using CATALINA_TMPDIR: d:\tomcat~1.1\temp
Using JAVA_HOME: d:\jdk1.4
Nov 30, 2002 9:43:34 PM org.apache.commons.modeler.Registry loadRegistry
INFO: Loading registry information
Nov 30, 2002 9:43:34 PM org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
Nov 30, 2002 9:43:37 PM org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer
Nov 30, 2002 9:43:40 PM org.apache.coyote.http11.Http11Protocol init
SEVERE: Error initializing endpoint
java.net.SocketException: Socket type not supported: create
at java.net.ServerSocket.createImpl(ServerSocket.java:244)
at java.net.ServerSocket.getImpl(ServerSocket.java:202)
at java.net.ServerSocket.bind(ServerSocket.java:308)
at java.net.ServerSocket.bind(ServerSocket.java:266)
at java.net.ServerSocket.<init>(ServerSocket.java:182)
at java.net.ServerSocket.<init>(ServerSocket.java:138)
at
org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(De
faultServerSocketFactory.java:96)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoi
nt.java:263)
at
org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:150)
at
org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.
java:1002)
at
org.apache.catalina.core.StandardService.initialize(StandardService.j
ava:579)
at
org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
a:2244)
at org.apache.catalina.startup.Catalina.start(Catalina.java:509)
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(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Catalina.start: LifecycleException: Protocol handler initialization failed:
jav
a.net.SocketException: Socket type not supported: create
LifecycleException: Protocol handler initialization failed:
java.net.SocketExce
ption: Socket type not supported: create
at
org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.
java:1004)
at
org.apache.catalina.core.StandardService.initialize(StandardService.j
ava:579)
at
org.apache.catalina.core.StandardServer.initialize(StandardServer.jav
a:2244)
at org.apache.catalina.startup.Catalina.start(Catalina.java:509)
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(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Catalina.stop: LifecycleException: This server has not yet been started
LifecycleException: This server has not yet been started
at
org.apache.catalina.core.StandardServer.stop(StandardServer.java:2211
)
at org.apache.catalina.startup.Catalina.start(Catalina.java:541)
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(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Datasource and Web.xml
Posted by Peng Tuck Kwok <pe...@makmal.net>.
Thanks craig. I'll look up the ResourceLink element.
Craig R. McClanahan wrote:
>
> On Tue, 3 Dec 2002, Peng Tuck Kwok wrote:
>
>
>>Date: Tue, 03 Dec 2002 12:09:42 +0800
>>From: Peng Tuck Kwok <pe...@makmal.net>
>>Reply-To: Tomcat Users List <to...@jakarta.apache.org>
>>To: Tomcat Users List <to...@jakarta.apache.org>
>>Subject: Datasource and Web.xml
>>
>>If a web application uses a jndi datasource, should the web.xml contain
>>the definition for the datasource before deployment (that is in the war
>>file) or after deployment (that is after the war file has been deployed)
>>? This sounds strange as I was having problems with this in tomcat
>>4.1.12 , where Tomcat could not start if the there was a resource
>>definition in the web.xml. Of course I can't create a resource for the
>>context using the admin interface since the context doesn't exist yet.
>>I've used Sun one server and all seems ok so what is the correct
>>sequence for doing things in tomcat?
>>
>
>
> There is not really a pre-deploy versus post-deploy state of the web.xml
> file in Tomcat stand-alone. The net effect of this is that:
>
> * You MUST declare your JNDI resources in the web.xml file before
> you deploy the app (i.e. in the original web.xml file you provide)
>
> * You MUST configure your JNDI resources in either server.xml
> at Tomcat startup time (nested in the <Context> element) or
> dynamically if you deploy via the manager webapp, in which case
> you must provide a context configuration file that includes the
> resource configurations.
>
> If you're using the admin webapp to create resources, what you're actually
> doing is setting up things in the <GlobalNamingResources> section of
> server.xml -- the resources are not actually configured to a particular
> webapp until you include a <ResourceLink> element in the <Context> element
> for that webapp.
>
> For more info about JNDI resources in general:
>
> http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources-howto.html
>
> For detailed walkthroughs (using the Java Web Services Developer Pack, but
> the instructions for JNDI resources are also generally applicable to
> Tomcat 4.1 standalone use), see the webapp related chapters in the Java
> Web Services Tutorial:
>
> http://java.sun.com/webservices/docs/1.0/tutorial/index.html
>
> Craig
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Reading wanted.
Posted by Triptpal Singh Lamba <tr...@cs.sunysb.edu>.
Hi all.
Can someone direct me to the following two things please...
1. The most exhaustive online, free resource for Tomcat documentation
2. Whats the best newsletter to keep in touch with the J2EE World updates.
Like we have IEEE software for SE, Dr Dobb blah blah, but whats a good one
for j2ee in general. I tried google but there are so many results I dont
know what to do:)
Btw ,bless the soul of the man who suggested Eclipse. It rocks! I used VA fo
Java 3.5 last time I did a project , buthad to make do with Jbuilder till
eclipse came along. I didnt find a fav. feature I like din editors --the
ctrl + bracket key to manually check brackets match or not and till where.
Thanks
Tript Singh
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Datasource and Initial Context
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Mon, 2 Dec 2002, maninder s batth wrote:
> Date: Mon, 02 Dec 2002 20:41:10 -0800
> From: maninder s batth <an...@netscape.net>
> Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> To: Tomcat Users List <to...@jakarta.apache.org>
> Subject: Datasource and Initial Context
>
> hi i am using my own DataSource class which cannot be configuered by xml
> file
> i need to programatically configure it . since tomcat provides read only
> context
> , is there any way i can use tomcat's jndi implementation, as of now i
> am using
> filesystem provider for datasource, is there any other open source
> provider for
> jndi which is more scalable and faster than file system provider?
> thanks
>
Tomcat will let you use any resource factory you want, as long as it (or a
wrapper class around it) implements the standard JNDI object factory
interface (javax.naming.spi.ObjectFactory). If you grab a source distro
of commons-dbcp <http://jakarta.apache.org/commons/dbcp> and look at the
sources for org.apache.commons.dbcp.BasicDataSourceFactory (the default
object factory for data sources in Tomcat) you can see that it's actually
pretty easy to create such a wrapper class around your own data source
implementation. Then, you tell Tomcat to use your factory by using a
"factory" parameter in the <ResourceParams> section of server.xml.
For more info about JNDI resources in Tomcat, including a simple example
of building your own factory, see:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources-howto.html
Craig
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Datasource and Initial Context
Posted by maninder s batth <an...@netscape.net>.
hi i am using my own DataSource class which cannot be configuered by xml
file
i need to programatically configure it . since tomcat provides read only
context
, is there any way i can use tomcat's jndi implementation, as of now i
am using
filesystem provider for datasource, is there any other open source
provider for
jndi which is more scalable and faster than file system provider?
thanks
Craig R. McClanahan wrote:
>On Tue, 3 Dec 2002, Peng Tuck Kwok wrote:
>
>
>
>>Date: Tue, 03 Dec 2002 12:09:42 +0800
>>From: Peng Tuck Kwok <pe...@makmal.net>
>>Reply-To: Tomcat Users List <to...@jakarta.apache.org>
>>To: Tomcat Users List <to...@jakarta.apache.org>
>>Subject: Datasource and Web.xml
>>
>>If a web application uses a jndi datasource, should the web.xml contain
>>the definition for the datasource before deployment (that is in the war
>>file) or after deployment (that is after the war file has been deployed)
>>? This sounds strange as I was having problems with this in tomcat
>>4.1.12 , where Tomcat could not start if the there was a resource
>>definition in the web.xml. Of course I can't create a resource for the
>>context using the admin interface since the context doesn't exist yet.
>>I've used Sun one server and all seems ok so what is the correct
>>sequence for doing things in tomcat?
>>
>>
>>
>
>There is not really a pre-deploy versus post-deploy state of the web.xml
>file in Tomcat stand-alone. The net effect of this is that:
>
>* You MUST declare your JNDI resources in the web.xml file before
> you deploy the app (i.e. in the original web.xml file you provide)
>
>* You MUST configure your JNDI resources in either server.xml
> at Tomcat startup time (nested in the <Context> element) or
> dynamically if you deploy via the manager webapp, in which case
> you must provide a context configuration file that includes the
> resource configurations.
>
>If you're using the admin webapp to create resources, what you're actually
>doing is setting up things in the <GlobalNamingResources> section of
>server.xml -- the resources are not actually configured to a particular
>webapp until you include a <ResourceLink> element in the <Context> element
>for that webapp.
>
>For more info about JNDI resources in general:
>
>http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources-howto.html
>
>For detailed walkthroughs (using the Java Web Services Developer Pack, but
>the instructions for JNDI resources are also generally applicable to
>Tomcat 4.1 standalone use), see the webapp related chapters in the Java
>Web Services Tutorial:
>
>http://java.sun.com/webservices/docs/1.0/tutorial/index.html
>
>Craig
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>
--
Your favorite stores, helpful shopping tools and great gift ideas.
Experience the convenience of buying online with Shop@Netscape!
http://shopnow.netscape.com/
Re: [4.1.16a] A feeedback from an Initial Installation on WinNT
Posted by Pae Choi <pa...@earthlink.net>.
Ok. I admit that I have not check the list before I was posting. And I
can take your comment on MBean part, but not the deploying part. :-)
Thanks for your comments,
Pae
> This is really a tomcat-user question (and, has been covered, ad nausium,
on
> that list :)
>
> The short form is that you can either use the Ajp13Connector without
MBeans,
> or you can use the Jk2 CoyoteConnector with MBeans. If you have a serious
> need for the Ajp13Connector with MBeans, patches are always welcome.
>
> ----- Original Message -----
> From: "Pae Choi" <pa...@earthlink.net>
> To: "Tomcat Users List" <to...@jakarta.apache.org>
> Cc: <to...@jakarta.apache.org>
> Sent: Monday, December 02, 2002 9:42 PM
> Subject: [4.1.16a] A feeedback from an Initial Installation on WinNT
>
>
> > This is a feedback after trying to install v4.1.16a and mod_jk(JK1). And
> > the some parts seem not working as it used be in v4.1.12.
> >
> > The change made in the server.xml as follows:
> >
> > <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
> > <!-- commeted
> > <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
> > port="8009" minProcessors="5" maxProcessors="75"
> > enableLookups="true" redirectPort="8443"
> > acceptCount="10" debug="0" connectionTimeout="0"
> > useURIValidationHack="false"
> >
> > protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
> > -->
> > <!-- Define an AJP 1.3 Connector on port 8009 -->
> > <!-- uncommented -->
> > <Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
> > port="8009" minProcessors="5" maxProcessors="75"
> > acceptCount="10" debug="0"/>
> > <!-- -->
> >
> > And the exception dusring the startup is as follows:
> >
> > ServerLifecycleListener: createMBeans: MBeanException
> > java.lang.Exception: ManagedBean is not found with Ajp13Connector
> > at
> > org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:224)
> > ...
> >
> >
> > But it did not crashed so that I tested the "index.jsp" as follows:
> >
> > http://localhost/index.jsp
> > http://localhost:8080/index.jsp
> > https://<real-domain>/index.jsp
> > https://<real-domain>:8443/index.jsp
> >
> > All above work as it suppose to be. However, a web app, "demowa.war",
> > did not deployed. And the exception is as follows:
> >
> > 2002-12-03 00:21:51 HostConfig[localhost]: Undeploying web application
at
> > context path /demowa
> > 2002-12-03 00:21:51 StandardHost[localhost]: Removing web application at
> > context path /demowa
> > 2002-12-03 00:21:51 StandardHost[localhost]: ContainerBase.removeChild:
> > stop:
> > LifecycleException: Container StandardContext[/demowa] has not been
> started
> > at
> org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643)
> > at
> >
>
org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1036)
> > at
> >
>
org.apache.catalina.core.StandardHostDeployer.remove(StandardHostDeployer.ja
> > va:420)
> > at org.apache.catalina.core.StandardHost.remove(StandardHost.java:852)
> > at
> org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:919)
> > at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:899)
> > at
> >
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:370)
> > at
> >
>
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor
> > t.java:166)
> > at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1221)
> > at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1233)
> > at
> org.apache.catalina.core.StandardService.stop(StandardService.java:554)
> > at
org.apache.catalina.core.StandardServer.stop(StandardServer.java:2224)
> > at org.apache.catalina.startup.Catalina.start(Catalina.java:543)
> > 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)
> >
> > Thanks,
> >
> >
> > Pae
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [4.1.16a] A feeedback from an Initial Installation on WinNT
Posted by Bill Barker <wb...@wilshire.com>.
This is really a tomcat-user question (and, has been covered, ad nausium, on
that list :)
The short form is that you can either use the Ajp13Connector without MBeans,
or you can use the Jk2 CoyoteConnector with MBeans. If you have a serious
need for the Ajp13Connector with MBeans, patches are always welcome.
----- Original Message -----
From: "Pae Choi" <pa...@earthlink.net>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Cc: <to...@jakarta.apache.org>
Sent: Monday, December 02, 2002 9:42 PM
Subject: [4.1.16a] A feeedback from an Initial Installation on WinNT
> This is a feedback after trying to install v4.1.16a and mod_jk(JK1). And
> the some parts seem not working as it used be in v4.1.12.
>
> The change made in the server.xml as follows:
>
> <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
> <!-- commeted
> <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
> port="8009" minProcessors="5" maxProcessors="75"
> enableLookups="true" redirectPort="8443"
> acceptCount="10" debug="0" connectionTimeout="0"
> useURIValidationHack="false"
>
> protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
> -->
> <!-- Define an AJP 1.3 Connector on port 8009 -->
> <!-- uncommented -->
> <Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
> port="8009" minProcessors="5" maxProcessors="75"
> acceptCount="10" debug="0"/>
> <!-- -->
>
> And the exception dusring the startup is as follows:
>
> ServerLifecycleListener: createMBeans: MBeanException
> java.lang.Exception: ManagedBean is not found with Ajp13Connector
> at
> org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:224)
> ...
>
>
> But it did not crashed so that I tested the "index.jsp" as follows:
>
> http://localhost/index.jsp
> http://localhost:8080/index.jsp
> https://<real-domain>/index.jsp
> https://<real-domain>:8443/index.jsp
>
> All above work as it suppose to be. However, a web app, "demowa.war",
> did not deployed. And the exception is as follows:
>
> 2002-12-03 00:21:51 HostConfig[localhost]: Undeploying web application at
> context path /demowa
> 2002-12-03 00:21:51 StandardHost[localhost]: Removing web application at
> context path /demowa
> 2002-12-03 00:21:51 StandardHost[localhost]: ContainerBase.removeChild:
> stop:
> LifecycleException: Container StandardContext[/demowa] has not been
started
> at
org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643)
> at
>
org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1036)
> at
>
org.apache.catalina.core.StandardHostDeployer.remove(StandardHostDeployer.ja
> va:420)
> at org.apache.catalina.core.StandardHost.remove(StandardHost.java:852)
> at
org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:919)
> at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:899)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:370)
> at
>
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor
> t.java:166)
> at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1221)
> at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1233)
> at
org.apache.catalina.core.StandardService.stop(StandardService.java:554)
> at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2224)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:543)
> 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)
>
> Thanks,
>
>
> Pae
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [4.1.16a] A feeedback from an Initial Installation on WinNT
Posted by Pae Choi <pa...@earthlink.net>.
I have not looked the source code yet. And I won't have time for it for a
while.
Wasn't the exception in the previous message enough to trace the cause? I
will provide you a full log if you think that will help.
Pae
> Pae Choi wrote:
> > This is a feedback after trying to install v4.1.16a and mod_jk(JK1). And
> > the some parts seem not working as it used be in v4.1.12.
> >
> > But it did not crashed so that I tested the "index.jsp" as follows:
> >
> > http://localhost/index.jsp
> > http://localhost:8080/index.jsp
> > https://<real-domain>/index.jsp
> > https://<real-domain>:8443/index.jsp
> >
> > All above work as it suppose to be. However, a web app, "demowa.war",
> > did not deployed. And the exception is as follows:
> >
> > 2002-12-03 00:21:51 HostConfig[localhost]: Undeploying web application
at
> > context path /demowa
> > 2002-12-03 00:21:51 StandardHost[localhost]: Removing web application at
> > context path /demowa
> > 2002-12-03 00:21:51 StandardHost[localhost]: ContainerBase.removeChild:
> > stop:
> > LifecycleException: Container StandardContext[/demowa] has not been
started
> > at
org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643)
> > at
> >
org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1036)
>
> Ok, fine. And why wasn't the webapp deployed ?
>
> Remy
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [4.1.16a] A feeedback from an Initial Installation on WinNT
Posted by Remy Maucherat <re...@apache.org>.
Pae Choi wrote:
> This is a feedback after trying to install v4.1.16a and mod_jk(JK1). And
> the some parts seem not working as it used be in v4.1.12.
>
> But it did not crashed so that I tested the "index.jsp" as follows:
>
> http://localhost/index.jsp
> http://localhost:8080/index.jsp
> https://<real-domain>/index.jsp
> https://<real-domain>:8443/index.jsp
>
> All above work as it suppose to be. However, a web app, "demowa.war",
> did not deployed. And the exception is as follows:
>
> 2002-12-03 00:21:51 HostConfig[localhost]: Undeploying web application at
> context path /demowa
> 2002-12-03 00:21:51 StandardHost[localhost]: Removing web application at
> context path /demowa
> 2002-12-03 00:21:51 StandardHost[localhost]: ContainerBase.removeChild:
> stop:
> LifecycleException: Container StandardContext[/demowa] has not been started
> at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643)
> at
> org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1036)
Ok, fine. And why wasn't the webapp deployed ?
Remy
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
[4.1.16a] A feeedback from an Initial Installation on WinNT
Posted by Pae Choi <pa...@earthlink.net>.
This is a feedback after trying to install v4.1.16a and mod_jk(JK1). And
the some parts seem not working as it used be in v4.1.12.
The change made in the server.xml as follows:
<!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
<!-- commeted
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8009" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" connectionTimeout="0"
useURIValidationHack="false"
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
-->
<!-- Define an AJP 1.3 Connector on port 8009 -->
<!-- uncommented -->
<Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
port="8009" minProcessors="5" maxProcessors="75"
acceptCount="10" debug="0"/>
<!-- -->
And the exception dusring the startup is as follows:
ServerLifecycleListener: createMBeans: MBeanException
java.lang.Exception: ManagedBean is not found with Ajp13Connector
at
org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:224)
...
But it did not crashed so that I tested the "index.jsp" as follows:
http://localhost/index.jsp
http://localhost:8080/index.jsp
https://<real-domain>/index.jsp
https://<real-domain>:8443/index.jsp
All above work as it suppose to be. However, a web app, "demowa.war",
did not deployed. And the exception is as follows:
2002-12-03 00:21:51 HostConfig[localhost]: Undeploying web application at
context path /demowa
2002-12-03 00:21:51 StandardHost[localhost]: Removing web application at
context path /demowa
2002-12-03 00:21:51 StandardHost[localhost]: ContainerBase.removeChild:
stop:
LifecycleException: Container StandardContext[/demowa] has not been started
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643)
at
org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1036)
at
org.apache.catalina.core.StandardHostDeployer.remove(StandardHostDeployer.ja
va:420)
at org.apache.catalina.core.StandardHost.remove(StandardHost.java:852)
at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:919)
at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:899)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:370)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor
t.java:166)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1221)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1233)
at org.apache.catalina.core.StandardService.stop(StandardService.java:554)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2224)
at org.apache.catalina.startup.Catalina.start(Catalina.java:543)
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)
Thanks,
Pae
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
[4.1.16a] A feeedback from an Initial Installation on WinNT
Posted by Pae Choi <pa...@earthlink.net>.
This is a feedback after trying to install v4.1.16a and mod_jk(JK1). And
the some parts seem not working as it used be in v4.1.12.
The change made in the server.xml as follows:
<!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
<!-- commeted
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8009" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" connectionTimeout="0"
useURIValidationHack="false"
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
-->
<!-- Define an AJP 1.3 Connector on port 8009 -->
<!-- uncommented -->
<Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
port="8009" minProcessors="5" maxProcessors="75"
acceptCount="10" debug="0"/>
<!-- -->
And the exception dusring the startup is as follows:
ServerLifecycleListener: createMBeans: MBeanException
java.lang.Exception: ManagedBean is not found with Ajp13Connector
at
org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:224)
...
But it did not crashed so that I tested the "index.jsp" as follows:
http://localhost/index.jsp
http://localhost:8080/index.jsp
https://<real-domain>/index.jsp
https://<real-domain>:8443/index.jsp
All above work as it suppose to be. However, a web app, "demowa.war",
did not deployed. And the exception is as follows:
2002-12-03 00:21:51 HostConfig[localhost]: Undeploying web application at
context path /demowa
2002-12-03 00:21:51 StandardHost[localhost]: Removing web application at
context path /demowa
2002-12-03 00:21:51 StandardHost[localhost]: ContainerBase.removeChild:
stop:
LifecycleException: Container StandardContext[/demowa] has not been started
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643)
at
org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1036)
at
org.apache.catalina.core.StandardHostDeployer.remove(StandardHostDeployer.ja
va:420)
at org.apache.catalina.core.StandardHost.remove(StandardHost.java:852)
at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:919)
at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:899)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:370)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor
t.java:166)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1221)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1233)
at org.apache.catalina.core.StandardService.stop(StandardService.java:554)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2224)
at org.apache.catalina.startup.Catalina.start(Catalina.java:543)
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)
Thanks,
Pae
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Datasource and Web.xml
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Tue, 3 Dec 2002, Peng Tuck Kwok wrote:
> Date: Tue, 03 Dec 2002 12:09:42 +0800
> From: Peng Tuck Kwok <pe...@makmal.net>
> Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> To: Tomcat Users List <to...@jakarta.apache.org>
> Subject: Datasource and Web.xml
>
> If a web application uses a jndi datasource, should the web.xml contain
> the definition for the datasource before deployment (that is in the war
> file) or after deployment (that is after the war file has been deployed)
> ? This sounds strange as I was having problems with this in tomcat
> 4.1.12 , where Tomcat could not start if the there was a resource
> definition in the web.xml. Of course I can't create a resource for the
> context using the admin interface since the context doesn't exist yet.
> I've used Sun one server and all seems ok so what is the correct
> sequence for doing things in tomcat?
>
There is not really a pre-deploy versus post-deploy state of the web.xml
file in Tomcat stand-alone. The net effect of this is that:
* You MUST declare your JNDI resources in the web.xml file before
you deploy the app (i.e. in the original web.xml file you provide)
* You MUST configure your JNDI resources in either server.xml
at Tomcat startup time (nested in the <Context> element) or
dynamically if you deploy via the manager webapp, in which case
you must provide a context configuration file that includes the
resource configurations.
If you're using the admin webapp to create resources, what you're actually
doing is setting up things in the <GlobalNamingResources> section of
server.xml -- the resources are not actually configured to a particular
webapp until you include a <ResourceLink> element in the <Context> element
for that webapp.
For more info about JNDI resources in general:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources-howto.html
For detailed walkthroughs (using the Java Web Services Developer Pack, but
the instructions for JNDI resources are also generally applicable to
Tomcat 4.1 standalone use), see the webapp related chapters in the Java
Web Services Tutorial:
http://java.sun.com/webservices/docs/1.0/tutorial/index.html
Craig
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>