RE: TOMCAT PROBLEM of disconection
Title: RE: TOMCAT PROBLEM of disconection -Original Message- From: Kitching Simon [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 11, 2001 9:50 AM To: '[EMAIL PROTECTED]' Subject: RE: TOMCAT PROBLEM of disconection The problem is that the java virtual machine you are using has a bug. There really isn't any work-around for this sort of problem - if the jvm is buggy, the best thing is to change jvm. JVM version 1.3 is available for just about every platform now, I suggest you download install it. Isn't 1.3 still 'buggy' on Linux? Regards, Simon -Original Message- From: Khaled Ben Mohamed [SMTP:[EMAIL PROTECTED]] Sent: Thursday, January 11, 2001 5:36 PM To: '[EMAIL PROTECTED]' Subject: TOMCAT PROBLEM of disconection After a undetermined disconection I have this message in a linux system console and tomcat stopped (sometimes the java process take more than 63Mo of memory) What's happen ? I have also a internel servlet error 500 sometimes please help me SIGSEGV 11* segmentation violation si_signo [11]: SIGSEGV 11* segmentation violation si_errno [0]: Succès si_code [0]: SI_USER [pid: 0, uid: 0] stackpointer=0x44699dec Full thread dump Classic VM (1.2.2-L, green threads): Thread-129 (TID:0x40ebf098, sys_thread_t:0x859af18, state:R) prio=5 at java.lang.StringBuffer.init(StringBuffer.java:116) at java.lang.StringBuffer.init(StringBuffer.java:130) at sun.tools.java.ClassDeclaration.getClassDefinition(ClassDeclar ation.java:1 07 ) at sun.tools.java.ClassDefinition.getVariable0(ClassDefinition.java:868) at sun.tools.java.ClassDefinition.getVariable0(ClassDefinition.java:857) at sun.tools.java.ClassDefinition.getVariable0(ClassDefinition.java:857) at sun.tools.java.ClassDefinition.getVariable0(ClassDefinition.java:857) at sun.tools.java.ClassDefinition.getVariable(ClassDefinition.java:817) at sun.tools.tree.Context.getFieldCommon(Context.java:180) at sun.tools.tree.Context.getField(Context.java:274) at sun.tools.tree.IdentifierExpression.bind(IdentifierExpression. java:117) at sun.tools.tree.IdentifierExpression.checkValue(IdentifierExpre ssion.java:2 20 ) at sun.tools.tree.IdentifierExpression.checkAmbigName(IdentifierE xpression.ja va :281) at sun.tools.tree.MethodExpression.checkValue(MethodExpression.java:184) at sun.tools.tree.Expression.checkCondition(Expression.java:278) at sun.tools.tree.Expression.checkCondition(Expression.java:261) at sun.tools.tree.WhileStatement.check(WhileStatement.java:44) at sun.tools.tree.Statement.checkBlockStatement(Statement.java:153) at sun.tools.tree.CompoundStatement.check(CompoundStatement.java:61) at sun.tools.tree.Statement.checkMethod(Statement.java:88) at sun.tools.javac.SourceMember.check(SourceMember.java:535) at sun.tools.javac.SourceClass.checkMembers(SourceClass.java:998) at sun.tools.javac.SourceClass.checkInternal(SourceClass.java:608) at sun.tools.javac.SourceClass.check(SourceClass.java:507) at sun.tools.javac.Main.compile(Main.java:546) at org.apache.jasper.compiler.SunJavaCompiler.compile(SunJavaComp iler.java:13 8) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:238) at org.apache.jasper.runtime.JspServlet.loadJSP(JspServlet.java:413) at org.apache.jasper.runtime.JspServlet$JspServletWrapper.loadIfN ecessary(Jsp Se rvlet.java:14 9) at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service (JspServlet. ja va:161) at org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet .java:261) at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:369) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWra pper.java:50 3) at org.apache.tomcat.core.RequestDispatcherImpl.forward(RequestDi spatcherImpl .j ava:163) at org.apache.jasper.runtime.PageContextImpl.forward(PageContextI mpl.java:357 ) at _0002frecupData_0002ejsprecupData_jsp_15._jspService(_0002frec upData_0002e js precupData_js p_15.java:1402) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:126) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.runtime.JspServlet$JspServletWrapper.service (JspServlet. ja va:174) at org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet .java:261) at org.apache.jasper.runtime.JspServlet.service(JspServlet.java:369) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWra pper.java:50 3) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:559) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.pro cessConnecti on (Ajp12Connect
RE: mod_jserv vs. mod_jk (configuration questions for workers.propert ies)
Title: RE: mod_jserv vs. mod_jk (configuration questions for workers.propert ies) Hey Max, We've (almost) got the same setup: Multiple Apache boxes (LVSed) and multiple Tomcat boxes in a load balanced setup (via mod_jk) All of out Tomcat boxes are identical, so we set the 'home' type attributes of the worker.properties file to where they are on the _Tomcat_ machines. Our Apache boxes just have Apache on them (no jdk etc) It seems to be working fine.. Hope that helped. mk Michael R. Kuz Developer Service Intelligence (403) 261-5000 ext. 363 [EMAIL PROTECTED] -Original Message- From: Max Clark [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 10, 2001 12:50 PM To: '[EMAIL PROTECTED]' Subject: mod_jserv vs. mod_jk (configuration questions for workers.propert ies) I have been browsing through the documentation and have hit a wall. I want to run Apache and Tomcat on separate machines. More than that I want to load balance my Tomcat application servers. I have done this in the past using mod_jserv to talk to jserv servers and it worked pretty well. From what I have gathered I want to use mod_jk with ajp v1.3. I understand everything in the mod_jk.conf-auto and the workers.properties except... the workers.properties file defines tomcat specific variables (i.e. workers.tomcat_home, workers.java_home, classpaths etc...). How can I define tomcat internals from an apache machine that doesn't have tomcat installed? What do I need to define within the workers.properties to have my apache machines connect to the tomcat machines. Do I have to install tomcat on all of the machines? What about a jdk? Has anybody done this? Can somebody help me with this config? Thanks in advance, -Max - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: newbie question
Title: RE: newbie question Yes. mod_jk forwards the requests to 8007 (by default). Just comment out the connector on 8080 that listens for HTTP. -Original Message- From: Henry DU [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 09, 2001 5:55 PM To: [EMAIL PROTECTED] Subject: RE: newbie question If I remove or comment out connector, can Apache send the servlet/jsp requests to tomcat? Thanks From: Michael Kuz [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] Subject: RE: newbie question Date: Tue, 9 Jan 2001 15:54:35 -0700 Actually, Apache (on port 80) is forwarding the servlet requests to Tomcat, AND Tomcat has a stand alone web server running on port 8080. Edit your server.xml file and comment out/remove the connector listening on 8080 Michael R. Kuz Developer Service Intelligence (403) 261-5000 ext. 363 [EMAIL PROTECTED] -Original Message- From: Henry DU [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 09, 2001 3:41 PM To: [EMAIL PROTECTED] Subject: newbie question The servlet URL is the same when I typed http://my.domainame.com/examples/servlet/HelloWorld and http://my.domainame.com:8080/examples/servlet/HelloWorld, they display the same information. Is this due to that Apache port 80 redirects to tomcat 8080 as indicated in server.xml? Thanks _ Get your FREE download of MSN Explorer at http://explorer.msn.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] _ Get your FREE download of MSN Explorer at http://explorer.msn.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: newbie question
Title: RE: newbie question Actually, Apache (on port 80) is forwarding the servlet requests to Tomcat, AND Tomcat has a stand alone web server running on port 8080. Edit your server.xml file and comment out/remove the connector listening on 8080 Michael R. Kuz Developer Service Intelligence (403) 261-5000 ext. 363 [EMAIL PROTECTED] -Original Message- From: Henry DU [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 09, 2001 3:41 PM To: [EMAIL PROTECTED] Subject: newbie question The servlet URL is the same when I typed http://my.domainame.com/examples/servlet/HelloWorld and http://my.domainame.com:8080/examples/servlet/HelloWorld, they display the same information. Is this due to that Apache port 80 redirects to tomcat 8080 as indicated in server.xml? Thanks _ Get your FREE download of MSN Explorer at http://explorer.msn.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: [PATCH PROPOSAL] for mod_jk (was: RE: gracefull shutdown/removalof worker from load balance...)
Title: RE: [PATCH PROPOSAL] for mod_jk (was: RE: gracefull shutdown/removalof worker from load balance...) The worker.property file is only read once, at startup. It would require major change to current mod_jk (as I understand it) to add multiple reads. I don't think that it would be a good idea anyway... all those reads to the file would negatively impact performance. Michael R. Kuz Developer Service Intelligence (403) 261-5000 ext. 363 [EMAIL PROTECTED] -Original Message- From: Fritz Thielemann [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 04, 2001 10:31 AM To: [EMAIL PROTECTED] Subject: Re: [PATCH PROPOSAL] for mod_jk (was: RE: gracefull shutdown/removalof worker from load balance...) Hi Michael, sounds good. but is it possible to change workers.prop on the fly while mod_jk is running? as others reading props only at startup, you checking constantly for the value of worker.tc7.active? thanks Fritz Michael Kuz wrote: Part 1.1.1Type: Plain Text (text/plain) Name: activeState.patch activeState.patch Type: unspecified type (application/octet-stream) Encoding: quoted-printable Part 1.3Type: Plain Text (text/plain) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[PATCH PROPOSAL] for mod_jk (was: RE: gracefull shutdown/removal of worker from load balance...)
Title: RE: gracefull shutdown/removal of worker from load balance... Thanks Dave, here you go! WARNINGThis is not an official patch and that it has only been tested on Linux. Use at your own risk :) OVERVIEW The patch allows for a worker.name.active parameter to be added to the workers.property file. eg: worker.tc7.active=0 If the active parameter = 1, worker will accept new connections as per SOP (this is also the default state, so if the parameter is not in the file it still works, or if the value is anything other then 0 it still works...)If the active parameter = 0, the worker will continue to service existing sessions, but will not accept new sessions.I'm still working on a way to determine actives sessions in a worker... Feedback appreciated! Michael R. Kuz Developer Service Intelligence (403) 261-5000 ext. 363 [EMAIL PROTECTED] -Original Message-From: Dave Smith [mailto:[EMAIL PROTECTED]]Sent: Friday, October 20, 2000 9:01 AMTo: [EMAIL PROTECTED]Subject: Re: gracefull shutdown/removal of worker from load balance... Michael, Please post the patch, if you would. Sounds like a very useful piece of code. Regards, Dave - Original Message - From: Michael Kuz To: '[EMAIL PROTECTED]' Sent: Thursday, January 04, 2001 9:51 AM Subject: RE: gracefull shutdown/removal of worker from load balance... We've got the load balancer working just fine, but had to patch mod_jk in order to allow for the removal of TC worker from the pool. I've added a setting called 'active' for each worker. When active is set to 0, the worker will not accept new connections, but continue with the existing sessions. (This allows us to remove the Tomcat box with no loss of users session info...) I submitted the patch, but have heard nothing back. If you (or anyone else) is interested I will post it. Michael R. Kuz Developer Service Intelligence (403) 261-5000 ext. 363 [EMAIL PROTECTED] -Original Message- From: Boaz Shaham [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 03, 2001 3:21 AM To: '[EMAIL PROTECTED]' Subject: RE: gracefull shutdown/removal of worker from load balance... mod_jserv documentation indicates that this should be done. Take a look at http://java.apache.org/jserv/howto.load-balancing.html However, we tried it but could not make it work. I dont know if mod_jk supports this, but I"ll be glad to hear that someone succeeded - Boaz -Original Message- From: Michael Kuz [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 03, 2001 03:51 To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Subject: gracefull shutdown/removal of worker from load balance...Hello all, How do I remove a worker from the load balancer without killing its current sessions? i.e.: I don't want any new sessions created on that worker, and the existing sessions must be allowed to expire 'naturally' (I can't just delete the entry from the balanced_workers property of the load balancer or current/established sessions get killed/ are not redirected to the proper worker) Our setup: We've got multiple Apache web servers behind LVS with multiple TC(3.2) boxes behind the web servers... Thanks in advance Michael R. Kuz Developer Service Intelligence (403) 261-5000 ext. 363 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] activeState.patch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
gracefull shutdown/removal of worker from load balance...
Title: gracefull shutdown/removal of worker from load balance... Hello all, How do I remove a worker from the load balancer without killing its current sessions? i.e.: I don't want any new sessions created on that worker, and the existing sessions must be allowed to expire 'naturally' (I can't just delete the entry from the balanced_workers property of the load balancer or current/established sessions get killed/ are not redirected to the proper worker) Our setup: We've got multiple Apache web servers behind LVS with multiple TC(3.2) boxes behind the web servers... Thanks in advance Michael R. Kuz Developer Service Intelligence (403) 261-5000 ext. 363 [EMAIL PROTECTED]
