RE: Oracle Connection Pool - Global Naming Resource - HOW TO
Hi!!! i did the same but now i'm facing with this problem 19/11/2002 02:20:21 PM org.apache.jk.common.ChannelSocket processConnection GRAVE: Error, closing connection java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read1(BufferedInputStream.java:222) at java.io.BufferedInputStream.read(BufferedInputStream.java:277) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:471) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:409) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:524) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:638) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:533) at java.lang.Thread.run(Thread.java:536) I usually do this, Context ctx = null; ctx = new InitialContext(); Context envCtx = (Context) ctx.lookup(java:/comp/env/); DataSource ds = (DataSource) envCtx.lookup(/test); Connection conn = ds.getConnection(); Statement s = conn.createStatement(); ResultSet r = s.executeQuery(SELECT * FROM TABLE); while (r.next()) out.println(r.getString(1)); r.close(); s.close(); conn.close(); The problem is that i cannot manage the exception because it happens sometimes and i don´t know why, when it happens Tomcat crashes and i´ve to restrat it. I wonder if you´re doing the same as me, or i´m i doning something wrong? thanks in advance -Mensaje original- De: Roberts, Eric [mailto:[EMAIL PROTECTED]] Enviado el: Jueves, 21 de Noviembre de 2002 10:27 a.m. Para: Tomcat Users List Asunto: Oracle Connection Pool - Global Naming Resource - HOW TO I had problems earlier getting a Global Naming Resource database connection pool to work with my Oracle db. The only reply I got was that someone else had the same problem! I now have it working, so for those interested, here is the HOW TO: When defining the parameters for the db pool (say TESTdb) ensure that the maxActive parameter is not set too high, i.e. that Oracle has enough connections available for the pool (Oracle config parameter max_connections). Mine was set to 100 in server.xml, and when the pool tried to establish itself, it just sat and waited for 100 connections to become available! Every app that wants to use the connection pool should have a Context entry in server.xml containing a ResourceLink to the name of the pool. ResourceLink name=testDb global=jdbc/TESTdb type=javax.sql.DataSource/ The application can then connect using: Context ctx = null; ctx = new InitialContext(); Context envCtx = (Context) ctx.lookup(java:/comp/env/); DataSource ds = (DataSource) envCtx.lookup(/testDb); Connection conn = ds.getConnection(); No entries are required in the application web.xml to reference the resource. Have Fun! -- 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]
java.net.SocketException While closing a Data base Connection
Hi All! Hope you can help me (Tomcat 4.12 running whith jdk 1.4.1) I have a web application that needs to make a conecction with a database so i crated a Data Source. The problem is that sometimes i get this exception 19/11/2002 02:20:21 PM org.apache.jk.common.ChannelSocket processConnection GRAVE: Error, closing connection java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read1(BufferedInputStream.java:222) at java.io.BufferedInputStream.read(BufferedInputStream.java:277) at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:471) at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:409) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:524) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:638) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:533) at java.lang.Thread.run(Thread.java:536) My application is working but sometimes Tomcat crashes and i have to restart it. I've no idea why is that happening so i appreciate any help Thanks in advance -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
tomcat JDNI DB connection pool to Oracle
Anabody could help me, i´ve been trying to do this for days
I've been successfully making JDBC connections directly in my JSP
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
Connection con =
DriverManager.getConnection(jdbc:oracle:oci8:+login+/+passwd+@+databas
e)
Now I'm trying to setup my Tomcat 4.0.9's JDNI DB connection pool, but I
can't get it to work
Here is what I've done so far
1. Move the Oracle Drivers (classes12.zip) into TOMCAT_HOME\common\lib
directory and rename it to classes12.jar
2. Added the following codes to my webapp's web.xml
resource-ref
res-ref-namejdbc/homebank/res-ref-name
res-typejavax.sql.DataSource/res-type
res-authContainer/res-auth
/resource-ref
3. Added the following codes within the GlobalNamingResources
/GlobalNamingResources tag
of TOMCAT_HOME\conf\server.xml
Resource name=jdbc/homebank auth=Container
type=javax.sql.DataSource/
ResourceParams name=jdbc/homebank
parameter
namefactory/name
valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
/parameter
parameter
namedriverClassName/name
valueoracle.jdbc.driver.OracleDriver/value
/parameter
parameter
nameurl/name
valuejdbc:oracle:oci8@homebank/value
/parameter
parameter
nameusername/name
valuescott/value
/parameter
parameter
namepassword/name
valuetiger/value
/parameter
parameter
namemaxActive/name
value20/value
/parameter
parameter
namemaxIdle/name
value10/value
/parameter
parameter
namemaxWait/name
value-1/value
/parameter
/ResourceParams
4. try to make connection within my JSP
%@ page import=java.net.* %
%@ page import=java.io.* %
%@ page import=java.sql.* %
%@ page import=javax.sql.* %
%@ page import=java.util.* %
%@ page import=javax.naming.* %
%
try {
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup(java:comp/env);
DataSource ds = (DataSource) envCtx.lookup(jdbc/homebank);
Connection conn1 = ds.getConnection();
out.println(Oracle Connected!br);
}
catch (SQLException E) {
out.println(brunable to get connection on ora !);
out.println(brSQLException: + E.getMessage());
out.println(brSQLState: + E.getSQLState());
out.println(brVendorError: + E.getErrorCode());
}
%
Results :
unable to get connection on ora !
SQLException: Cannot load JDBC driver class 'null'
SQLState: null
VendorError: 0
Why? I'm able to make connection call JDBC directly in my other JSP,
but not when I try to get the connection via JDNI Context ...??
Thank you in advance
P.S.: i´ve search the archives and found nothing that could help me.
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Data Base Connection
Hi all! I have 2 web applications that runs in my Tomcat 4.1.8 server. Every thing works fine if i run only one of the two applications. If i run one application and then the other i get this exception org.apache.jasper.JasperException: Native Library C:\oracle\ora81\bin\ocijdbc8.dll already loaded in another classloader I´m trying to create a data source to solve this problem, i´ve done all i found in tomcat-docs: 1. Create the data source Resource name=jdbc/myoracle auth=Container type=javax.sql.DataSource/ ResourceParams name=jdbc/myoracle parameter namefactory/name valueorg.apache.commons.dbcp.BasicDataSourceFactory/value /parameter parameter namedriverClassName/name valueoracle.jdbc.driver.OracleDriver/value /parameter parameter nameurl/name valuejdbc:oracle:oci8:[EMAIL PROTECTED]:1521:mysid/value /parameter parameter nameusername/name valuescott/value /parameter parameter namepassword/name valuetiger/value /parameter parameter namemaxActive/name value20/value /parameter parameter namemaxIdle/name value10/value /parameter parameter namemaxWait/name value-1/value /parameter /ResourceParams 2. Configure web.xml (i added this line) resource-ref descriptionOracle Datasource example/description res-ref-namejdbc/myoracle/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref 3. I have a bean that creates a connection like this Context initContext = new InitialContext(); Context envContext = (Context)initContext.lookup(java:/comp/env); DataSource ds = (DataSource)envContext.lookup(jdbc/myoracle); Connection conn = ds.getConnection(); The problem is that the connection whit my oracle data base cannot be creates because i get this execption: java.sql.SQLException: Cannot load JDBC driver class 'null' I don´t know if the problem is with the bean or with the server.xml or with both How can i check if the Data source is working fine since i found nothing in the log files. Thanks in advance -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat 4.1 in production
Thanks for that, could you tell me where to find how to use the CoyoteConnector, because I´ve tried but i don´t know if it works like the AJP13Conecctor .. i wonder if it could be that the isapi_redirect.dll i have doesn´t support that -Mensaje original- De: Bill Barker [mailto:[EMAIL PROTECTED]] Enviado el: Martes, 13 de Agosto de 2002 03:49 p.m. Para: [EMAIL PROTECTED] Asunto: Re: Tomcat 4.1 in production The Ajp13Connector isn't supported for the manager webapp in 4.1.x. You have to use the CoyoteConnector if you want to connect Tomcat to IIS and also use the manager webapp. The entry in server.xml looks like: Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler / - Original Message - From: Isabel Lameda [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Tuesday, August 13, 2002 11:48 AM Subject: RE: Tomcat 4.1 in production I´m having a problem with Tomcat 4.1.8 Beta. I´ve set up all i need to view jsp files in IIS and the problem is that when when i uncomment the line for the ajp 1.3 Connector in the server.xml, which is: Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ I get this exception: INFO: Creating MBeanServer 12/08/2002 04:22:10 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 ServerLifecycleListener: createMBeans: MBeanException java.lang.Exception: ManagedBean is not found with Ajp13Connector at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:225) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:359) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:716) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:690) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:329) at org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLife cycleListener.java:206) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor t.java:166) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2181) 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) Starting service Tomcat-Standalone Apache Tomcat/4.1.8 12/08/2002 11:26:32 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Every thing works fine, except that i cannot use the Administration Tool, when i open it i get this: HTTP Status 503 - Servlet action is currently unavailable type: Status report message: Servlet action is currently unavailable description: The requested service (Servlet action is currently unavailable) is not currently available. If i comment back the line for the ajp connector the administration tool works fine but the thing is that i need to use the connector. I'm also worry about what other problems could involve that exception, because until now i´ve only found that with the administration tool. In the server.xml i also have this lines referencing some listeners: Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ ListenerclassName=org.apache.catalina.mbeans.GlobalResourcesLifecycleListe nerdebug=0/ If i comment the first one, the exception disapeers and every thing works but i cannot either use the administration tool Regards -Mensaje original- De: Wills, Mike N. (TC) [mailto:[EMAIL PROTECTED]] Enviado el: Martes, 13 de Agosto de 2002 02:26 p.m. Para: 'Tomcat Users List' Asunto: Tomcat 4.1 in production I have heard of some people using Tomcat 4.1 in a production environment. I know that running beta software is usually a bad thing. What are people's experiences with it here? Mike Wills -- 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: Tomcat 4.1 in production
-Mensaje original- De: Bill Barker [mailto:[EMAIL PROTECTED]] Enviado el: Martes, 13 de Agosto de 2002 03:49 p.m. Para: [EMAIL PROTECTED] Asunto: Re: Tomcat 4.1 in production The Ajp13Connector isn't supported for the manager webapp in 4.1.x. You have to use the CoyoteConnector if you want to connect Tomcat to IIS and also use the manager webapp. The entry in server.xml looks like: Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler / - Original Message - From: Isabel Lameda [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Tuesday, August 13, 2002 11:48 AM Subject: RE: Tomcat 4.1 in production I´m having a problem with Tomcat 4.1.8 Beta. I´ve set up all i need to view jsp files in IIS and the problem is that when when i uncomment the line for the ajp 1.3 Connector in the server.xml, which is: Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ I get this exception: INFO: Creating MBeanServer 12/08/2002 04:22:10 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 ServerLifecycleListener: createMBeans: MBeanException java.lang.Exception: ManagedBean is not found with Ajp13Connector at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:225) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:359) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:716) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:690) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:329) at org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLife cycleListener.java:206) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor t.java:166) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2181) 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) Starting service Tomcat-Standalone Apache Tomcat/4.1.8 12/08/2002 11:26:32 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Every thing works fine, except that i cannot use the Administration Tool, when i open it i get this: HTTP Status 503 - Servlet action is currently unavailable type: Status report message: Servlet action is currently unavailable description: The requested service (Servlet action is currently unavailable) is not currently available. If i comment back the line for the ajp connector the administration tool works fine but the thing is that i need to use the connector. I'm also worry about what other problems could involve that exception, because until now i´ve only found that with the administration tool. In the server.xml i also have this lines referencing some listeners: Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ ListenerclassName=org.apache.catalina.mbeans.GlobalResourcesLifecycleListe nerdebug=0/ If i comment the first one, the exception disapeers and every thing works but i cannot either use the administration tool Regards -Mensaje original- De: Wills, Mike N. (TC) [mailto:[EMAIL PROTECTED]] Enviado el: Martes, 13 de Agosto de 2002 02:26 p.m. Para: 'Tomcat Users List' Asunto: Tomcat 4.1 in production I have heard of some people using Tomcat 4.1 in a production environment. I know that running beta software is usually a bad thing. What are people's experiences with it here? Mike Wills -- 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]
Coyote Connector
Does anybody knows how to use the Coyote Connector in Tomcat 4.1.8, because i´ve been trying and having this error: INFO: APR not loaded, disabling jni components: java.io.IOException: no jkjni in java.library.path -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Coyote Conecction in Tomcat 4.1.8
Does anybody knows how to use te Coyote Connector in Tomcat 4.1.8? I´ve this line in my server.xml: Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ -- Actually i´m having this error: INFO: APR not loaded, disabling jni components: java.io.IOException: no jkjni in java.library.path I don´t really understand bescause in jakarta home page i found that the CoyoteConnector is already included in Tomcat 4.1.8 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Coyote Conecction in Tomcat 4.1.8
Not really, i´m trying to connect Tomcat to IIS, I've alreary done that with AJP13 Connector but the problem is that i cannot use the administration tool. Somebody told me to use the Coyote Connector instead -Mensaje original- De: Andrew [mailto:[EMAIL PROTECTED]] Enviado el: Miércoles, 14 de Agosto de 2002 02:57 p.m. Para: 'Tomcat Users List' Asunto: RE: Coyote Conecction in Tomcat 4.1.8 Let me clarify. It's not a show stopper for connecting Apache 2.0.39 to Tomcat 4.1.x via mod_jk2. - Andrew -Original Message- From: Andrew [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 14, 2002 2:50 PM To: 'Tomcat Users List' Subject: RE: Coyote Conecction in Tomcat 4.1.8 It's informational in nature. Not really an error. - Andrew -Original Message- From: Isabel Lameda [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 14, 2002 1:45 PM To: '[EMAIL PROTECTED]' Subject: Coyote Conecction in Tomcat 4.1.8 Does anybody knows how to use te Coyote Connector in Tomcat 4.1.8? I´ve this line in my server.xml: Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ -- Actually i´m having this error: INFO: APR not loaded, disabling jni components: java.io.IOException: no jkjni in java.library.path I don´t really understand bescause in jakarta home page i found that the CoyoteConnector is already included in Tomcat 4.1.8 -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-user- [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: Coyote Conecction in Tomcat 4.1.8
Thanks now it works, all the problem was that the channelSocket.port was set on 8019, so i chage it to 8009 as you said and everything is working now. Regards -Mensaje original- De: Bill Barker [mailto:[EMAIL PROTECTED]] Enviado el: Miércoles, 14 de Agosto de 2002 03:26 p.m. Para: [EMAIL PROTECTED] Asunto: Re: Coyote Conecction in Tomcat 4.1.8 The errors are harmless. You can get rid of them by editing $CATALINA_HOME/conf/jk2.properties and commenting out (by putting a '#' in front of) the lines that start shm.file and apr.jniModSo. For good measure, you should probably make certain that the value of channelSocket.port is 8009. The Coyote Connector is supposed to work with any version of isapi_redirector.dll, but I don't use IIS myself. However the jk2 version is supposed to have improvements in it (esp. for IIS-5). You can pick up the jk2 version from http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/nightly/win32 / - Original Message - From: Isabel Lameda [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, August 14, 2002 10:44 AM Subject: Coyote Conecction in Tomcat 4.1.8 Does anybody knows how to use te Coyote Connector in Tomcat 4.1.8? I´ve this line in my server.xml: Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ -- Actually i´m having this error: INFO: APR not loaded, disabling jni components: java.io.IOException: no jkjni in java.library.path I don´t really understand bescause in jakarta home page i found that the CoyoteConnector is already included in Tomcat 4.1.8 -- 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: Quick Question
Try to create a file in your bean and see where Tomcat stores it -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Enviado el: Lunes, 12 de Agosto de 2002 06:00 p.m. Para: Tomcat Users List Asunto: Quick Question Hi all, I wrote a simple java bean that reads a txt file, the problem is where do I need to put the txt file??... What is the default directory in Tomcat?? when I put something like this in my java bean : FileReader(config.txt) Where does tomcat look for that file? thanks Alex -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat 4.0.4 and IIS 5.0
Here you can find out what you need, I did all with Tomcat 4.1.8 and i´m having a problem, but it seems that with Tomcat 4.0.4 are no problems http://members.ozemail.com.au/~lampante/howto/tomcat/iisnt/index.html -Mensaje original- De: Reis, Tom [mailto:[EMAIL PROTECTED]] Enviado el: Martes, 13 de Agosto de 2002 01:29 p.m. Para: Tomcat Users List (E-mail) Asunto: Tomcat 4.0.4 and IIS 5.0 Could someone tell me what I need to download in order to integrate Tomcat 4.0.4 with IIS 5.0. Thanks. -- 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 in production
I´m having a problem with Tomcat 4.1.8 Beta. I´ve set up all i need to view jsp files in IIS and the problem is that when when i uncomment the line for the ajp 1.3 Connector in the server.xml, which is: Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ I get this exception: INFO: Creating MBeanServer 12/08/2002 04:22:10 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 ServerLifecycleListener: createMBeans: MBeanException java.lang.Exception: ManagedBean is not found with Ajp13Connector at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:225) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:359) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:716) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:690) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:329) at org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLife cycleListener.java:206) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor t.java:166) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2181) 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) Starting service Tomcat-Standalone Apache Tomcat/4.1.8 12/08/2002 11:26:32 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Every thing works fine, except that i cannot use the Administration Tool, when i open it i get this: HTTP Status 503 - Servlet action is currently unavailable type: Status report message: Servlet action is currently unavailable description: The requested service (Servlet action is currently unavailable) is not currently available. If i comment back the line for the ajp connector the administration tool works fine but the thing is that i need to use the connector. I'm also worry about what other problems could involve that exception, because until now i´ve only found that with the administration tool. In the server.xml i also have this lines referencing some listeners: Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ ListenerclassName=org.apache.catalina.mbeans.GlobalResourcesLifecycleListe nerdebug=0/ If i comment the first one, the exception disapeers and every thing works but i cannot either use the administration tool Regards -Mensaje original- De: Wills, Mike N. (TC) [mailto:[EMAIL PROTECTED]] Enviado el: Martes, 13 de Agosto de 2002 02:26 p.m. Para: 'Tomcat Users List' Asunto: Tomcat 4.1 in production I have heard of some people using Tomcat 4.1 in a production environment. I know that running beta software is usually a bad thing. What are people's experiences with it here? Mike Wills -- 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]
Ajp 1.3 Connector Fails
I´ve downloaded Tomcat 4.1.8 Beta Released and uncomment the line for the ajp 1.3 Connector, which is: Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ So when i start the Tomcat i get this INFO: Initializing Coyote HTTP/1.1 on port 8080 ServerLifecycleListener: createMBeans: MBeanException java.lang.Exception: ManagedBean is not found with Ajp13Connector at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:225) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:359) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:716) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:690) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:329) at org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLife cycleListener.java:206) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor t.java:166) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2181) 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) Starting service Tomcat-Standalone Apache Tomcat/4.1.8 12/08/2002 11:26:32 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Every thing works fine, i can view my pages using IIS via the ajp Connector. The only problem is that i cannot use the Administration Tool, when i open it i get this: HTTP Status 503 - Servlet action is currently unavailable type: Status report message: Servlet action is currently unavailable description: The requested service (Servlet action is currently unavailable) is not currently available. If i comment back the line for the ajp connector the administration tool works fine but the thing is that i need to use the connector. I'm also worry about what other problems could be due that exception, because until now i´ve only found that with the administration tool. Thanks, I´ll appreciate any help. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Connection IIS Tomcat
I´ve downloaded Tomcat 4.1.8 Beta Released and uncomment the line for the ajp 1.3 Connector in the server.xml, which is: Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ So when i start the Tomcat i get this: INFO: Creating MBeanServer 12/08/2002 04:22:10 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 ServerLifecycleListener: createMBeans: MBeanException java.lang.Exception: ManagedBean is not found with Ajp13Connector at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:225) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:359) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:716) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:690) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:329) at org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLife cycleListener.java:206) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor t.java:166) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2181) 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) Starting service Tomcat-Standalone Apache Tomcat/4.1.8 12/08/2002 11:26:32 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Every thing works fine, i can view my pages using IIS via the ajp Connector. The only problem is that i cannot use the Administration Tool, when i open it i get this: HTTP Status 503 - Servlet action is currently unavailable type: Status report message: Servlet action is currently unavailable description: The requested service (Servlet action is currently unavailable) is not currently available. If i comment back the line for the ajp connector the administration tool works fine but the thing is that i need to use the connector. I'm also worry about what other problems could be due that exception, because until now i´ve only found that with the administration tool. In the server.xml i also have this lines referencing some listeners: Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener debug=0/ If i comment the first one the exception in the Creating MBeanServer disapeers and every thing works but i cannot also use the administration tool Thanks, I´ll appreciate any help. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
