Resin slower than Tomcat, fails the AppFuse Test
So now you know! http://raibledesigns.com/page/rd/20041007#resin_slower_than_tomcat_fails - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat command line arguments
At 15:15 14/10/2004, you wrote: Hey I give the following command to start Tomcat version 5 with a CATALINA_BASE different to the default one: ./startup.sh -Dcatalina.base=/some/dir/that/exists But it fails to pass the argument, what am I doing wrong? Set the environment variable CATALINA_OPTS instead. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
MemoryRealm in a Context
Setup is Tomcat 5.0.28, J2SE 1.4.2, Redhat 9. I've been using a MemoryRealm in a Host container and everything works fine. It is ideal for a computer to computer link over HTTPS to authenticate access. I've now decided that I want a different setup on a per Context basis. The docs for the realm component say that a Realm can be inside a Context container so I moved the Realm section from the Host to the Context and restarted Tomcat. Now when I try and authenticate the debug log shows that the realm is being treated as a JAAS realm and consequently fails. Is there something clever going on here that I'm not aware of or do I need to made further config changes? Cheers, Andy. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multiple virtual hosts at root context
I am using Tomcat 4.1.27 under Linux for a project where the machine is embedded into a pumping machine, i.e. limited memory and resources. The 'services' are all identified by sub domains so that you would get a master domain of the pump site, a sub domain for each pump unit and a further subdomain for each reading. For example, http://finham - gives an overview of the site called finham http://top-bearing.finham gives an overview of the pump called top-bearing http://power.top-bearing.finham gives a power reading for the pump etc. Everything was developed with Apache fronting Tomcat and all is well. We've now arrived at the factory tests and I think I've shot myself in the foot. I had always intended to remove the Apache front end as it just will not fit onto the hardware. The problem seems to be that you cannot have a standalone Tomcat supporting many virtual hosts where the context paths are the same. You can in Apache. I appreciate that there are other ways to do this but this 'design' has now been used by other systems so any changes are bad news at this stage. My question is, am I correct that this cannot be done using a standalone Tomcat and, if not, does anyone have any ideas? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: Multiple virtual hosts at root context
Oops. In the panic of thinking it wasn't possible I somehow proved to myself that it wasn't possible |-( I inadvertently loaded all the contexts for all the hosts into all the hosts. I think the previous post is what used to be known as a structured walk through. So thanks for that all the same. Date: Tue, 21 Oct 2003 09:55:24 +0100 To: Tomcat Users List [EMAIL PROTECTED] From: Andy Hutchinson [EMAIL PROTECTED] Subject: Multiple virtual hosts at root context I am using Tomcat 4.1.27 under Linux for a project where the machine is embedded into a pumping machine, i.e. limited memory and resources. The 'services' are all identified by sub domains so that you would get a master domain of the pump site, a sub domain for each pump unit and a further subdomain for each reading. For example, http://finham - gives an overview of the site called finham http://top-bearing.finham gives an overview of the pump called top-bearing http://power.top-bearing.finham gives a power reading for the pump etc. Everything was developed with Apache fronting Tomcat and all is well. We've now arrived at the factory tests and I think I've shot myself in the foot. I had always intended to remove the Apache front end as it just will not fit onto the hardware. The problem seems to be that you cannot have a standalone Tomcat supporting many virtual hosts where the context paths are the same. You can in Apache. I appreciate that there are other ways to do this but this 'design' has now been used by other systems so any changes are bad news at this stage. My question is, am I correct that this cannot be done using a standalone Tomcat and, if not, does anyone have any ideas? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Crashing on Linux
I thought that the new threading stuff in the RH9 kernel caused problems with the JVM and native threads. At 12:25 29/07/2003 -0400, you wrote: Hi, Check to make sure you aren't throwing a lock down somewhere and stacking up threads behind it. -e On Tue, 29 Jul 2003, Rick Roberts wrote: I had not seen this problem before I recently started implementing JDBCRealm on these servers. Anyone else having stability problems when using Oracle JDBCRealm? Rick Roberts wrote: Also, The only way I can clear this error is to reboot the machine. Here is another piece of info I get from catalina_log.2003-07-29.txt when I try the 2nd restart (/etc/init.d/tomcat restart) 2003-07-29 11:06:33 JDBCRealm[Standalone]: Exception closing database connection java.sql.SQLException: Io exception: Broken pipe at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269) at oracle.jdbc.driver.OracleConnection.close(OracleConnection.java:557) at org.apache.catalina.realm.JDBCRealm.close(Unknown Source) at org.apache.catalina.realm.JDBCRealm.stop(Unknown Source) at org.apache.catalina.core.ContainerBase.stop(Unknown Source) at org.apache.catalina.core.StandardService.stop(Unknown Source) at org.apache.catalina.core.StandardServer.stop(Unknown Source) at org.apache.catalina.startup.Catalina.start(Unknown Source) at org.apache.catalina.startup.Catalina.execute(Unknown Source) at org.apache.catalina.startup.Catalina.process(Unknown Source) 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(Unknown Source) Rick Roberts wrote: Tomcat is crashing every 2 - 3 days on 2 different Linux machines. Both machines are running pretty much identical software configurations. Both machines are serving the same web application so, it's almost certainly something in my web app code that causes the problem. However; the logs from my web app do not tell me anything. I am seeing this error on 2 different Linux machines. Tomcat just stops responding to my requests. Also when I restart Tomcat (using: /etc/init.d/tomcat restart), I get this: [EMAIL PROTECTED] root]# /etc/init.d/tomcat4 restart waiting for processes to exit [ OK ] waiting for processes to exit waiting for processes to exit waiting for processes to exit waiting for processes to exit waiting for processes to exit waiting for processes to exit waiting for processes to exit The only info from logs I can find is from catalina.out: Jul 29, 2003 10:54:06 AM org.apache.tomcat.util.net.PoolTcpEndpoint closeServerSocket SEVERE: Caught exception trying to unlock accept. java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) at java.net.Socket.connect(Socket.java:426) at java.net.Socket.connect(Socket.java:376) at java.net.Socket.init(Socket.java:291) at java.net.Socket.init(Socket.java:119) at org.apache.tomcat.util.net.PoolTcpEndpoint.closeServerSocket(PoolTcpEndpoint.java:326) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:397) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:529) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:536) Jul 29, 2003 10:54:07 AM org.apache.tomcat.util.net.PoolTcpEndpoint closeServerSocket SEVERE: Caught exception trying to close socket. java.lang.NullPointerException at org.apache.tomcat.util.net.PoolTcpEndpoint.closeServerSocket(PoolTcpEndpoint.java:338) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:397) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:529) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:536) Jul 29, 2003 10:54:07 AM org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket WARNING: Reinitializing
