Re: Tomcat 6.0 Clustering
Thanks Chris, Re-login may be accepted. I will follow your instruction and the URL you provided. Thanks again, --Sam On Mon, Jun 23, 2008 at 12:36 PM, Christopher Schultz <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Sam, > > Shamshad Ansari wrote: > | I have a web application which runs on Tomcat. There will be at any > | given time a maximum of 20 users. So, the traffic is not much. > | However, the application is kind of mission critical and therefore, we > | can not afford any downtime. I am thinking Clustering would be an > | option where if one server goes down, the other picks up. > > Is it acceptable for users to have to re-login in the event of a server > failure? If so, you can just set up simply clustering via mod_jk, which > binds a particular session to a single back-end machine. You don't have > to use distributable sessions or worry about sending data around the > cluster so the data is available everywhere just in case a server goes down. > > | Could any one please suggest what would be the best option. Also, if > | you could point me to a good tutorial to accomplish this. may be a > | step-by-step example. > > You should definitely start here: > http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html > > There is quite a bit of information in there, including background info > and step-by-step instructions. > > - -chris > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkhf0SIACgkQ9CaO5/Lv0PB5nACfaGFZgtF+CX1OMH96jAB5DOh8 > A+wAmwcr/WX6QMn5DqhahKRO0tb9QGMK > =imH8 > -END PGP SIGNATURE- > > - > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 6.0 Clustering
Hi Guys, I have a web application which runs on Tomcat. There will be at any given time a maximum of 20 users. So, the traffic is not much. However, the application is kind of mission critical and therefore, we can not afford any downtime. I am thinking Clustering would be an option where if one server goes down, the other picks up. Could any one please suggest what would be the best option. Also, if you could point me to a good tutorial to accomplish this. may be a step-by-step example. Thank you, --Sam - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JNI and Tomcat problem
Hi, I have a web application deployed in Tomcat. On a click on button on the web browser, it calls a servlet which in turn calls a native function written in C. First time when tomcat is started and I run the application, it works fine. The second clicking the same button causes the server to crash with the following error message. I have placed the .dll file in $Cateline_Home\shared\lib Tomcat version: 6.0 When I restart the server, it works fine the first time and second time, it crashes and stops again. The error log is: - Jun 15, 2008 2:39:13 AM org.apache.catalina.core.StandardServer await SEVERE: StandardServer.await: accept: java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384) at java.net.ServerSocket.implAccept(ServerSocket.java:453) at java.net.ServerSocket.accept(ServerSocket.java:421) at org.apache.catalina.core.StandardServer.await(StandardServer.java:389) at org.apache.catalina.startup.Catalina.await(Catalina.java:642) at org.apache.catalina.startup.Catalina.start(Catalina.java:602) 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:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Jun 15, 2008 2:39:13 AM org.apache.jk.common.ChannelSocket acceptConnections WARNING: Exception executing accept java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384) at java.net.ServerSocket.implAccept(ServerSocket.java:453) at java.net.ServerSocket.accept(ServerSocket.java:421) at org.apache.jk.common.ChannelSocket.accept(ChannelSocket.java:306) at org.apache.jk.common.ChannelSocket.acceptConnections(ChannelSocket.java:660) at org.apache.jk.common.ChannelSocket$SocketAcceptor.runIt(ChannelSocket.java:870) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690) at java.lang.Thread.run(Thread.java:619) Jun 15, 2008 2:39:13 AM org.apache.jk.common.ChannelSocket acceptConnections WARNING: Exception executing accept java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384) at java.net.ServerSocket.implAccept(ServerSocket.java:453) at java.net.ServerSocket.accept(ServerSocket.java:421) at org.apache.jk.common.ChannelSocket.accept(ChannelSocket.java:306) java.util.logging.ErrorManager: 1 at org.apache.jk.common.ChannelSocket.acceptConnections(ChannelSocket.java:660) java.lang.NullPointerException at org.apache.jk.common.ChannelSocket$SocketAcceptor.runIt(ChannelSocket.java:870) at org.apache.juli.FileHandler.publish(FileHandler.java:137) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690) at java.util.logging.Logger.log(Logger.java:472) at java.lang.Thread.run(Thread.java:619) at java.util.logging.Logger.doLog(Logger.java:494) Jun 15, 2008 2:39:13 AM org.apache.tomcat.util.net.JIoEndpoint$Acceptor run at java.util.logging.Logger.logp(Logger.java:694) SEVERE: Socket accept failed at org.apache.juli.logging.DirectJDKLog.log(DirectJDKLog.java:167) java.net.SocketException: socket closed at org.apache.juli.logging.DirectJDKLog.warn(DirectJDKLog.java:127) at java.net.PlainSocketImpl.socketAccept(Native Method) at org.apache.jk.common.ChannelSocket.acceptConnections(ChannelSocket.java:671) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384) at org.apache.jk.common.ChannelSocket$SocketAcceptor.runIt(ChannelSocket.java:870) at java.net.ServerSocket.implAccept(ServerSocket.java:453) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690) at java.net.ServerSocket.accept(ServerSocket.java:421) at java.lang.Thread.run(Thread.java:619) at org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFactory.java:61) at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:310) at java.lang.Thread.run(Thread.java:619) Jun 15, 2008 2:39:13 AM org.apache.jk.common.ChannelSocket acceptConnections WARNING: Exception executing accept java.net.SocketException: socket closed at java.net.PlainSocketImpl.socketAccept(Native
