Alfresco installation problem
Hi, I'm trying to install Alfresco *Enterprise Content Management , on windows server 2003. After deploying the alfresco.war file in tomcat, when I open the alfresco at the following path , it is showing the exception ' *error *retrieving*attribute reloadablehttp://www.google.co.in/search?hl=ensa=Xoi=spellresnum=0ct=resultcd=1q=error+retrieving+attribute+reloadablespell=1 *' Please suggest me the correct procedure to deploy Alfresco on tomcat and make it work.. need help on this. Thanks in advance. Regards, Persistence *
Re: Alfresco installation problem
I can think of two suggestions: 1. Check with the Alfresco folks whether this is a known issue and how to fix it. Seems like an enterprise CMS should be able to provide support to their customers. 2. Check your logs for better error information Just out of curiosity, did the message you received in your browser really have that link or is that just a stray paste? --David persistence k wrote: Hi, I'm trying to install Alfresco *Enterprise Content Management , on windows server 2003. After deploying the alfresco.war file in tomcat, when I open the alfresco at the following path , it is showing the exception ' *error *retrieving*attribute reloadablehttp://www.google.co.in/search?hl=ensa=Xoi=spellresnum=0ct=resultcd=1q=error+retrieving+attribute+reloadablespell=1 *' Please suggest me the correct procedure to deploy Alfresco on tomcat and make it work.. need help on this. Thanks in advance. Regards, Persistence * - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
running servlet from java
Hi!
I would like to run a servlet(/FunPacmanServlet) from java.This servlet
would then show a jsp page in web browser. The problem is that the
contents of jsp page is shown in eclipse console, but the browser does
not show the page. Any idea what i'm doing wrong? I am using eclipse
3.2, tomcat 5.5,firefox. Does tomcat maybe need some setting up?
Best regards, Goran
***My main servlet
code:
import java.io.IOException;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.RequestDispatcher;
import org.umb.portal.app.unimod.*;
import com.evelopers.unimod.*;
import java.util.Enumeration;
/**
* Servlet implementation class for Servlet: LoadPortalServlet
*
*/
public class LoadPortalServlet extends javax.servlet.http.HttpServlet
implements javax.servlet.Servlet {
BqPortalEngine fsmEngine = new BqPortalEngine();
public static LoadPortalServlet startServlet = null;
private HttpServletRequest request = null;
private String jspName = main/portal.jsp;
private String userAgent = Mozilla 5.0;
private String contentType = application/x-www-form-urlencoded;
private String accept =
application/x-shockwave-flash,text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5;
private String keepAlive = 300;
private String host = localhost:8080;
private String contentLength = -1;
private String acceptLanguage= sl,en-gb;q=0.7,en;q=0.3;
private String acceptEncoding= gzip,deflate;
private String acceptCharset = ISO-8859-2,utf-8;q=0.7,*;q=0.7;
public HttpServletRequest getRequest() { return request; }
public String getUserAgent() { return userAgent; }
public String getContentType() { return contentType; }
public String getAccept() { return accept; }
public String getKeepAlive() { return keepAlive; }
public String getHost() { return host; }
public String getContentLength() { return contentLength; }
public String getAcceptLanguage() { return acceptLanguage;}
public String getAcceptEncoding() { return acceptEncoding;}
public String getAcceptCharset() { return acceptCharset; }
public LoadPortalServlet() {
super();
}
public void init(){
System.out.println(START);
System.out.println(STOP);
}
public void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException
{
// System.out.println(GLEJ:+fsmEngine.getCounter());
// fsmEngine.fireEvent();
RequestDispatcher dispatcher = request.getRequestDispatcher(jspName);
System.out.println( Request MAIN portal servlet #\n
+ request.getRequestURI() + \n
+ request.getServletPath() + \n
+ request.getServerPort() + \n
+ request.getRemoteHost() + \n
+ request.getAuthType() + \n
+ request.getCharacterEncoding() + \n
+ request.getContentLength() + \n
+ request.getContentType() + \n
+ request.getContextPath() + \n
+ request.getLocalAddr() + \n
+ request.getLocalName()+ \n
+ request.getLocalPort()+ \n
+ request.getMethod()+ \n
+ request.getPathInfo()+ \n
+ request.getPathTranslated()+ \n
+ request.getProtocol()+ \n
+ request.getQueryString()+ \n
+ request.getUserPrincipal()+ \n
+ request.getSession()+ \n
+ request.getRequestURL()+ \n
+ request.getParameter(url) +\n );
for (Enumeration t=request.getHeaderNames(); t.hasMoreElements();)
{
String headerName = (String) t.nextElement();
System.out.println ( # + headerName + # + request.getHeader(
headerName ) +#\n );
}
System.out.println( \n END \n );
this.request = request;
this.startServlet = this;
userAgent = request.getHeader(User-Agent);
accept = request.getHeader(accept);
keepAlive = request.getHeader(keep-alive);
host = request.getHeader(host);
contentLength = request.getHeader(content-length);
acceptLanguage = request.getHeader(accept-language);
acceptEncoding = request.getHeader(accept-encoding);
acceptCharset = request.getHeader(accept-charset);
contentType =
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5;
if (dispatcher != null)
{
dispatcher.forward(request, response);
}
}
protected void doPost(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
doGet(request, response);
}
}
***My java code (only the function
imports):*
import java.io.IOException;
import com.evelopers.common.exception.SystemException;
import com.evelopers.unimod.runtime.context.StateMachineContext;
import com.evelopers.unimod.runtime.ControlledObject;
import com.evelopers.unimod.core.stateworks.Event;
import com.evelopers.unimod.runtime.*;
import com.evelopers.unimod.runtime.context.*;
import com.evelopers.common.exception.CommonException;
import com.evelopers.unimod.transform.xml.*;
import org.umb.portal.app.config.*;
import org.umb.portal.web.LoadPortalServlet;
import javax.servlet.http.HttpServletRequest;
import org.apache.commons.logging.LogFactory;
Re: Tomcat Locking Up?
Hi, I think you need to make sure this is Tomcat's fault first. The best way to do this is to set up JMX console and keep monitoring it so you can see how much memory is allocated/used, same for CPU, threads, sockets, etc. Maybe you're running out of resources? We run 5.5 Tomcat on websites having high load and the uptime is at least a few months. If nothing helps, profiling is your best friend...not sure if you can do this by yourself, but I'd go this direction. Anyway, I tend to doubt that such a trivial and critical bug as yours would not be noticed. m. On Wed, Feb 20, 2008 at 11:51 AM, Peter Sparkes [EMAIL PROTECTED] wrote: Hi, I am running Tomcat 5.5 I have a website running in a cocoon application under Tomcat5.5, every few days the pages will not load and eventually the browser times out. - 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 Locking Up?
OOPS sorry previous email sent before I finished writing it. Hi, I am running Tomcat 5.5 I have a website running in a cocoon application under Tomcat5.5, every few days the pages will not load and eventually the browser times out. If I then stop tomcat and then start it everything then works fine. I have other instances of Tomcat running other websites on the same server which are not having this problem. Am I right in assuming that all the Tomcat instances share the same memory and that if so it can't be a Tomcat memory problem? If its not a Tomcat memory problem what could it be? Thanks Peter - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Locking Up?
Thanks Mindaugas, Will follow your advice Peter Hi, I think you need to make sure this is Tomcat's fault first. The best way to do this is to set up JMX console and keep monitoring it so you can see how much memory is allocated/used, same for CPU, threads, sockets, etc. Maybe you're running out of resources? We run 5.5 Tomcat on websites having high load and the uptime is at least a few months. If nothing helps, profiling is your best friend...not sure if you can do this by yourself, but I'd go this direction. Anyway, I tend to doubt that such a trivial and critical bug as yours would not be noticed. m. On Wed, Feb 20, 2008 at 11:51 AM, Peter Sparkes [EMAIL PROTECTED] wrote: Hi, I am running Tomcat 5.5 I have a website running in a cocoon application under Tomcat5.5, every few days the pages will not load and eventually the browser times out. - 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 ldap authentication problem
Hi, we have setup Tomcat (6.0.10) to authenticate using form authentication against openldap (2.3.27) with the jndirealm and everything works alright except one little bit of a problem. if the user name has national characters in it (åæø for norwegian) or the password does, the user cannot authenticate .-( for example if our user has a password of hælge the user cannot log in, but if we change the password to helge he can log in. all our html pages uses the utf-8 encoding, using slapcat and looking at the content the data inside openldap seems to be using utf-8 (the output from slapcat is at least utf-8,but I don't know if slapcat converts anything) We are also administrating the users from within our application (using the standard javax.naming package) and from there we can search AND find users with user names that have øæå in them so we know that ldap and javax.naming can communicate and use national characters correctly.. looking at the logfile for ldap (when turning up the debug level) it almost looks like jndirealm is using iso-8859-1 as encoding since in the logfile all natinal characters comes out as garbage. and as I said ALL pages in the system uses UTF-8 as encoding (including the login page) can anyone give me a hint on where to look next, I've searched for an answer using google and in the mailinglist but either I'm nort searching for the right thing, or I just cannot find it.. /Christian Andersson - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Trying to know why tomcat shuts down
Hello, our tomcat, in a test environment, is shutting down unexpectedly. There is no messages about stopping webapp, or even receiving SHUTDOWN message from management port. It's just normal webapp behaviour in logs and that's all. We notice this when someone comes in and says reserver does not respond, whe check processes (a linux 32bits box), and no track of the jvm. No specific operation seems to trigger it. The jvm is not dying, cause that would have led to the presence of a pid.log file and messages in catalina.out. It's not the webapp calling System.exit, because tomcat runs with a security manager that forbids system.exit from webapps. We have no clue on how to get reason of this shutdown. I have attached now a shutdown hook that will call an external script that itself will ask jvm for a dumpstack (kill -3), in the hope we get some information. But our tries with regular shutdown seems to point that jvm ignore such request when it's processing the shutdown hooks. Any suggestion on tracking this greatly appreciated. -- http://www.devlog.be (a belgian developer's logs) - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Trying to know why tomcat shuts down
From: David Delbecq [mailto:[EMAIL PROTECTED] our tomcat, in a test environment, is shutting down unexpectedly. [...] (a linux 32bits box) Which Linux, and have you disabled the kernel option that nukes the largest process if the kernel can't allocate itself some memory? Can't remember its name, but I know it's been mentioned previously on this list. Just a thought, and probably completely off the mark! - Peter - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trying to know why tomcat shuts down
Is Tomcat getting killed by the OOM Killer? http://linux-mm.org/OOM_Killer On Feb 20, 2008 8:12 AM, David Delbecq [EMAIL PROTECTED] wrote: Hello, our tomcat, in a test environment, is shutting down unexpectedly. There is no messages about stopping webapp, or even receiving SHUTDOWN message from management port. It's just normal webapp behaviour in logs and that's all. We notice this when someone comes in and says reserver does not respond, whe check processes (a linux 32bits box), and no track of the jvm. No specific operation seems to trigger it. The jvm is not dying, cause that would have led to the presence of a pid.log file and messages in catalina.out. It's not the webapp calling System.exit, because tomcat runs with a security manager that forbids system.exit from webapps. We have no clue on how to get reason of this shutdown. I have attached now a shutdown hook that will call an external script that itself will ask jvm for a dumpstack (kill -3), in the hope we get some information. But our tries with regular shutdown seems to point that jvm ignore such request when it's processing the shutdown hooks. Any suggestion on tracking this greatly appreciated. -- http://www.devlog.be (a belgian developer's logs) - 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]
Re: Trying to know why tomcat shuts down
Everyday, learning something new, today is check linux system logs if your tomcat disappear [30575826.592000] Out of Memory: Killed process 734 (java) Thanks for your help, you got it right. That server might need a bit of additional memory ^^ En l'instant précis du 20/02/08 14:29, Peter Crowther s'exprimait en ces termes: From: David Delbecq [mailto:[EMAIL PROTECTED] our tomcat, in a test environment, is shutting down unexpectedly. [...] (a linux 32bits box) Which Linux, and have you disabled the kernel option that nukes the largest process if the kernel can't allocate itself some memory? Can't remember its name, but I know it's been mentioned previously on this list. Just a thought, and probably completely off the mark! - Peter - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.devlog.be (a belgian developer's logs) - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mod_jk Problems - worker went to error state and dont recover
Hallo to all, After long unsuccessful research i hope someone can give me a hint to the following problems. Our Apache-mod_jk-Tomcat Infrastructur was running without Problems for about one year-than since two month mod_jk errors occurs. We upgraded the mod_jk Version, made improvements in the worker.properties - the problems changed and get less but sometimes they appear further on. It seems that the mod_jk worker loose the connection to their Tomcat-Backendserver - there are messages in the mod_jk log Files which points in this direction. Normally this seems not to be a big problem - but under certain conditions (which ?) the worker goes to an error state and cannot recover itself- must be done manually. Problem 1: The Tomcats are reachable - unknown why the workers think the server is dead ? Problem 2: I have no idea why the worker goes to an error state and cannot recover. Problem3: I miss explanations of logged messages - i read the messages - but cannot match them to the situation - when does a worker post this messages [Wed Feb 20 10:04:01.889 2008] [19237:3086010048] [info] jk_handler::mod_jk.c (2270): Aborting connection for worker=ajp_ggi [Wed Feb 20 10:04:39.799 2008] [19294:3086010048] [error] ajp_get_reply::jk_ajp_common.c (1623): (INETP1011) Timeout with waiting reply from tomca t. Tomcat is down, stopped or network problems (errno=110) [Wed Feb 20 10:04:39.799 2008] [19294:3086010048] [error] ajp_service::jk_ajp_common.c (2034): (INETP1011) receiving reply from tomcat failed with out recovery in send loop attempt=0 [Wed Feb 20 10:04:41.799 2008] [19294:3086010048] [error] service::jk_lb_worker.c (1105): unrecoverable error 504, request failed. Tomcat failed i n the middle of request, we can't recover to another instance. - Which Timeout - how does mod_jk think Tomcat is down ? Where can i found details to errno=110 ?... - receiving reply from tomcat failed with out recovery in send loop attempt=0 - ? with out recovery in send loop - means? - unrecoverable error 504 - details to this error ? Ok - i turn the logging level to debug - the course of events get more clear - but also more questions appear - there are socket numbers - which sockets - what are these numbers e.g will be shutting down socket 35 for worker INETP1021 - The sockets are good for ? - how many are there/per worker ? can i configure them ? = Generally -How can i solve such problems - i tried to look into the mod_jk code - searching for error codes, error messages - but cannot find some relevant informations, - i am studying the log Files - but don't find out what really happens. So - maybe someone has an idea why the worker think that the corresponding Tomcat is dead, and why he will not recover by itself. ! And i am also searching for tips how i can help myself - and where to find something about the error codes, messages,..in mod_jk thanks for your attention Best ahmed musa (writing from vienna) Current Infrastructur We have 3 Apache Webserver (2.2.6) -based on CentOS release 4.3 / Kernelversion 2.6.9-34 In front of the Webserver there are two (two Locations) HW-Loadbalancer (but they have no role in this story) The Webservers are hosted at our ISP. The Webserver balance the requests via mod_jk (Version 1.2.25) for approx. 10 Webapps to 18 Backend-Tomcatserver (Bladeserver - because of underlying Application-Parts the OS ist Windows 2003 Server - a long story not worth to explain :-) ). The Tomcatserver gain Data via Requests against DB2 Server/DB2-Databases on the Mainframe. The Tomcatserver are Inhouse - and were rebooted nightly because of automated Deployment processes. Between the Webserver and the Tomcatserver is a Checkpoint Firewall. All webapps are deployed on all Tomcats - only mod_jk manages the requests to certain Tomcat- instances. (on one Bladeserver there are two identically Tomcat Instances running). Versions: Tomcat - 5.5.17_11, JDK 1.5.0_11-b03. The requests against the public Website(s) are normal short living requests - not many - The most Webapps (Portals) need a login, have a strong focus on business logic - so the instances are big (many MBs in RAM), the sessions are sticky and the session timeout is 20 minutes. But there are also less requests. To the User requests - Monitoring requests from our ISP are added. The Problems appears at Servers/Portals which very less Userrequests. worker.properties worker.list=ajp_bam,ajp_ggi,ajp_ad,ajp_svp,...,jkstatus worker.template.type=ajp13 worker.template.lbfactor=5 worker.template.socket_keepalive=1 worker.template.connect_timeout=7000 worker.template.prepost_timeout=5000 worker.template.reply_timeout=12 worker.template.retries=6 worker.template.activation=Active worker.template.recovery_options=7 worker.lbtemplate.type=lb worker.lbtemplate.max_reply_timeouts=6 worker.lbtemplate.method=Session #Produktions Worker # AS-INETP101 - 106 - 6/6 GGI worker.INETP1011.host=AS-INETP101.AEAT.ALLIANZ.AT worker.INETP1011.port=65001
RE: Tomcat Locking Up?
From: Peter Sparkes [mailto:[EMAIL PROTECTED] Subject: Tomcat Locking Up? Am I right in assuming that all the Tomcat instances share the same memory and that if so it can't be a Tomcat memory problem? No, your are not right. Each Tomcat process is almost completely independent of the others. If you are running a 1.5 or later HotSpot client JVM, some half-processed class files are shared in order to reduce startup time, but that's it. (But you shouldn't be running Tomcat in client mode.) - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mod_jk Problems - - worker went to error state and dont recover
See Thread at: http://www.techienuggets.com/Detail?tx=25608 Posted on behalf of a User Hallo to all, After long unsuccessful research i hope someone can give me a hint to the following problems. Our Apache-mod_jk-Tomcat Infrastructur was running without Problems for about one year-than since two month mod_jk errors occurs. We upgraded the mod_jk Version, made improvements in the worker.properties - the problems changed and get less but sometimes they appear further on. It seems that the mod_jk worker loose the connection to their Tomcat-Backendserver - there are messages in the mod_jk log Files which points in this direction. Normally this seems not to be a big problem - but under certain conditions (which ?) the worker goes to an error state and cannot recover itself- must be done manually. Problem 1: The Tomcats are reachable - unknown why the workers think the server is dead ? Problem 2: I have no idea why the worker goes to an error state and cannot recover. Problem3: I miss explanations of logged messages - i read the messages - but cannot match them to the situation - when does a worker post this messages [Wed Feb 20 10:04:01.889 2008] [19237:3086010048] [info] jk_handler::mod_jk.c (2270): Aborting connection for worker=ajp_ggi [Wed Feb 20 10:04:39.799 2008] [19294:3086010048] [error] ajp_get_reply::jk_ajp_common.c (1623): (INETP1011) Timeout with waiting reply from tomcat. Tomcat is down, stopped or network problems (errno=110) [Wed Feb 20 10:04:39.799 2008] [19294:3086010048] [error] ajp_service::jk_ajp_common.c (2034): (INETP1011) receiving reply from tomcat failed with out recovery in send loop attempt=0 [Wed Feb 20 10:04:41.799 2008] [19294:3086010048] [error] service::jk_lb_worker.c (1105): unrecoverable error 504, request failed. Tomcat failed in the middle of request, we can't recover to another instance. - Which Timeout - how does mod_jk think Tomcat is down ? Where can i found details to errno=110 ?... - receiving reply from tomcat failed with out recovery in send loop attempt=0 - ? with out recovery in send loop - means? - unrecoverable error 504 - details to this error ? Ok - i turn the logging level to debug - the course of events get more clear - but also more questions appear - there are socket numbers - which sockets - what are these numbers e.g will be shutting down socket 35 for worker INETP1021 - The sockets are good for ? - how many are there/per worker ? can i configure them ? = Generally -How can i solve such problems - i tried to look into the mod_jk code - searching for error codes, error messages - but cannot find some relevant informations, - i am studying the log Files - but don't find out what really happens. So - maybe someone has an idea why the worker think that the corresponding Tomcat is dead, and why he will not recover by itself. ! And i am also searching for tips how i can help myself - and where to find something about the error codes, messages,..in mod_jk thanks for your attention Best ahmed musa (writing from vienna) Current Infrastructur We have 3 Apache Webserver (2.2.6) -based on CentOS release 4.3 /Kernelversion 2.6.9-34 In front of the Webserver there are two (two Locations) HW-Loadbalancer (but they have no role in this story) The Webservers are hosted at our ISP. The Webserver balance the requests via mod_jk (Version 1.2.25) for approx. 10 Webapps to 18 Backend-Tomcatserver (Bladeserver - because of underlying Application-Parts the OS is Windows 2003 Server - a long story not worth to explain :-) ). The Tomcatserver gain Data via Requests against DB2 Server/DB2-Databases on the Mainframe. The Tomcatserver are Inhouse -and were rebooted nightly because of automated Deployment processes. Between the Webserver and the Tomcatserver is a Checkpoint Firewall. All webapps are deployed on all Tomcats - only mod_jk manages the requests to certain Tomcat- instances. (on one Bladeserver there are two identically Tomcat Instances running). Versions: Tomcat - 5.5.17_11, JDK 1.5.0_11-b03. The requests against the public Website(s) are normal short living requests - not many - The most Webapps (Portals) need a login, have a strong focus on business logic - so the instances are big (many MBs in RAM), the sessions are sticky and the session timeout is 20 minutes. But there are also less requests. To the User requests - Monitoring requests from our ISP are added. The Problems appears at Servers/Portals which very less Userrequests. worker.properties worker.list=ajp_bam,ajp_ggi,ajp_ad,ajp_svp,...,jkstatus worker.template.type=ajp13 worker.template.lbfactor=5 worker.template.socket_keepalive=1 worker.template.connect_timeout=7000 worker.template.prepost_timeout=5000 worker.template.reply_timeout=12 worker.template.retries=6 worker.template.activation=Active worker.template.recovery_options=7 worker.lbtemplate.type=lb worker.lbtemplate.max_reply_timeouts=6 worker.lbtemplate.method=Session
Re: mod_jk Problems - - worker went to error state and dont recover
[EMAIL PROTECTED] wrote: See Thread at: http://www.techienuggets.com/Detail?tx=25608 Posted on behalf of a User Hallo to all, After long unsuccessful research i hope someone can give me a hint to the following problems. Our Apache-mod_jk-Tomcat Infrastructur was running without Problems for about one year-than since two month mod_jk errors occurs. We upgraded the mod_jk Version, made improvements in the worker.properties - the problems changed and get less but sometimes they appear further on. It seems that the mod_jk worker loose the connection to their Tomcat-Backendserver - there are messages in the mod_jk log Files which points in this direction. Normally this seems not to be a big problem - but under certain conditions (which ?) the worker goes to an error state and cannot recover itself- must be done manually. Problem 1: The Tomcats are reachable - unknown why the workers think the server is dead ? Problem 2: I have no idea why the worker goes to an error state and cannot recover. 2 is a consequence of 1 Problem3: I miss explanations of logged messages - i read the messages - but cannot match them to the situation - when does a worker post this messages 1 is a consequence of these messages [Wed Feb 20 10:04:01.889 2008] [19237:3086010048] [info] jk_handler::mod_jk.c (2270): Aborting connection for worker=ajp_ggi [Wed Feb 20 10:04:39.799 2008] [19294:3086010048] [error] ajp_get_reply::jk_ajp_common.c (1623): (INETP1011) Timeout with waiting reply from tomcat. Tomcat is down, stopped or network problems (errno=110) [Wed Feb 20 10:04:39.799 2008] [19294:3086010048] [error] ajp_service::jk_ajp_common.c (2034): (INETP1011) receiving reply from tomcat failed with out recovery in send loop attempt=0 [Wed Feb 20 10:04:41.799 2008] [19294:3086010048] [error] service::jk_lb_worker.c (1105): unrecoverable error 504, request failed. Tomcat failed in the middle of request, we can't recover to another instance. The second line tells us, that your configured reply_timeout fired. You set it to 12 (2 minutes), so there are requests taking longer than 2 minutes on the backend, before the first response packet comes back from the backend. With your configuration mod_jk then doesn't wait any longer on the reply *and puts the backend into error mode*. Up until version 1.2.25, if you use a reply-timeout, you need to set it to a high number which justifies the resoning if it takes that long, that something is wrong with the backend. Reality shows: there is no such number. Often there are few requests that take unaccetably long on the backend *although* the backend is still working. So in 1.2.25 we added max_reply_timeouts. With this set in addition to reply_timeout, mod_jk will abort waiting for a reply after reply_timeout, but allow some timeouts before actually deciding to put the backend into error. Unfortunately the implementation of max_reply_timeouts in 1.2.25 was wrong, so you need to go to 1.2.26 to get it working right. See: http://issues.apache.org/bugzilla/show_bug.cgi?id=43229 Caution: this does *not* explain, why the backends are not automatically recovered after a minute of error condition. Maybe you have times, where you getr to many of those reply_timeouts (see log file), and although we recover after a minute the backend almost immediately goes back into error status. - Which Timeout - how does mod_jk think Tomcat is down ? Where can i found details to errno=110 ?... reply_timeout, see above and also http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html errno: a standard unix feature. The numbers are platform dependent. I would assume in your case ETIMEDOUT 110 /* Connection timed out */ so no wonder, that's exactly what we expect (and doesn't tell us the reason, i.e. what's wrong on the *backend* taking that long for a response). - receiving reply from tomcat failed with out recovery in send loop attempt=0 - ? with out recovery in send loop - means? That your configuration doesn't allow us to send the request to another backend. recovery_options 7 include: if mod_jk was able to send the request to a backend, do not try to send it to another backend in case of an error during the response handling. Even if you would allow sending to another backend, it would not help with *not* putting the worker into error state. More likely would be, that you would put all workers into error state, because all of them might run into the same timeout, one after the other. - unrecoverable error 504 - details to this error ? That's simply how we return the situation back to the client (browser). Ok - i turn the logging level to debug - the course of events get more clear - but also more questions appear - there are socket numbers - which sockets - what are these numbers e.g will be shutting down socket 35 for worker INETP1021 - The sockets are good for ? - how many are there/per worker ? can i configure them
OT: a java question - static initialization
class Foo {
private static int;
static {
a = 100;
}
Foo() {
}
}
Class.forName(package.Foo).newInstance();
The static init block of Foo is not called.
I am using Java 1.5 update14. It is a bug?
Thanks
Dave
-
Never miss a thing. Make Yahoo your homepage.
Re: Accessing standalone Tomcat from an external IP address
Hi Chuck, Thank you for your reply, it is helpful to know that no further configuration is required in server.xml to make Tomcat accessible through an external IP. As you mentioned I may need to configure the firewall as described here: https://help.ubuntu.com/6.06/ubuntu/serverguide/C/firewall-configuration.html The netstat tool shows that the connection was received from the external IP. Since the request is not reaching Tomcat , I guess the request is not being frowarded from the external to the internal ip. I checked Tomcat's access log valve outputs, and it shows that no connection was received. This is not related to Tomcat. I'll try to figure this out. -Rashmi On Tue, Feb 19, 2008 at 10:36 PM, Caldarale, Charles R [EMAIL PROTECTED] wrote: From: Rashmi [mailto:[EMAIL PROTECTED] Subject: Accessing standalone Tomcat from an external IP address I'm trying to configure Tomcat so that it can be accessed externally. There's nothing to configure within Tomcat for that. http://xxx.xxx.xxx.xxx:7070 , I can't access the app, I get a The server at external ip is taking too long to respond. You likely have a firewall blocking remote access. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - 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]
Apache2 and tomcat5.5
I'm running FedoraCore8.x86_64 on a machine placed in a LAN with router address 195.168.0.135. The Internet static IP address is 87.227.4.194. So, by hitting http://87.227.4.194 you'll come to the Apache2 welcome page because there is nothing in /var/www/html. My question: Is my tomcat5.5 to be regarded as a COMBINED web server and application server? If yes, what shall I do in order to see the tomcat instead of the the Apache2 welcome page by hitting http://87.227.4.194? /dan - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OT: a java question - static initialization
On Feb 20, 2008 10:47 AM, Dave [EMAIL PROTECTED] wrote:
class Foo {
private static int;
static {
a = 100;
}
Foo() {
}
}
Class.forName(package.Foo).newInstance();
The static init block of Foo is not called.
I am using Java 1.5 update14. It is a bug?
FWIW, appears to work here under 1.6 (Linux) and 1.4.2 (Solaris):
[EMAIL PROTECTED]:~/tmp/jstatic$ java -version
java version 1.6.0
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
[EMAIL PROTECTED]:~/tmp/jstatic$ cat test.java
public class test {
public static void main(String [] args)
throws Exception {
Object o = Class.forName(foo).newInstance() ;
}
}
[EMAIL PROTECTED]:~/tmp/jstatic$ cat foo.java
public class foo {
private static int a ;
static {
a = 100 ;
System.out.println(a set to + a) ;
}
foo() {
}
}
[EMAIL PROTECTED]:~/tmp/jstatic$ javac test.java
[EMAIL PROTECTED]:~/tmp/jstatic$ javac foo.java
[EMAIL PROTECTED]:~/tmp/jstatic$ java -classpath . test
a set to 100
And under 1.4.2:
[EMAIL PROTECTED]:~/tmp/jstatic$ java -version
java version 1.4.2
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
[EMAIL PROTECTED]:~/tmp/jstatic$ javac test.java
[EMAIL PROTECTED]:~/tmp/jstatic$ javac foo.java
[EMAIL PROTECTED]:~/tmp/jstatic$ java -classpath . test
a set to 100
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache2 and tomcat5.5
Yes, Tomcat is a regular web server as well as an application server. To use Tomcat as your web server, 1. Don't run the Apache2 web server. 2. Configure Tomcat to listen on the correct HTTP port. In conf/server.xml where it says Connector port=8080 change it to Connector port=80 (or whatever port Apache 2 was using - could be different depending on how your gateway router is set up) -- Len On Feb 20, 2008 10:52 AM, elvberg [EMAIL PROTECTED] wrote: I'm running FedoraCore8.x86_64 on a machine placed in a LAN with router address 195.168.0.135. The Internet static IP address is 87.227.4.194. So, by hitting http://87.227.4.194 you'll come to the Apache2 welcome page because there is nothing in /var/www/html. My question: Is my tomcat5.5 to be regarded as a COMBINED web server and application server? If yes, what shall I do in order to see the tomcat instead of the the Apache2 welcome page by hitting http://87.227.4.194? /dan - 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]
RE: a java question - static initialization
From: Dave [mailto:[EMAIL PROTECTED]
Subject: OT: a java question - static initialization
class Foo {
private static int;
static {
a = 100;
}
Foo() {
}
}
Class.forName(package.Foo).newInstance();
The static init block of Foo is not called.
Works fine for me under 1.5.0_14 (and other levels). Since your example
code is chock full of syntactic and semantic errors, you might want to
correct those first and publish actual code.
Here's what ran for me:
package myPackage;
class Foo {
private static int a;
static { a = 100; }
Foo() { }
public String toString() { return Integer.toString(a); }
}
package myPackage;
public class FooMain {
static public void main(String[] args) throws Exception {
System.out.println(Class.forName(myPackage.Foo).newInstance());
}
}
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk Problems - - worker went to error state and dont recover
Hello, Wow -thank you very much Rainer for your very quick and informative answer. I will go to 1.2.26 and think about some smoother Values for reply_timeout and max_reply_timeouts. I will search for the requests which causes the Problems - becasue i still log the response time in your mentioned way - but I am not sure that the Userrequests are responsible for the Situation. So one further question - does mod_jk itself checks if the Backend is reachable - without userrequests? When there are connections to the Backend - are they closed after the respone or are the hold open for further requests. Is it possible that the Checkpoint Firewall in Between can be responsible for the connectivity problem? Another point is the not recovering of the worker. Yes, you are right - in this situation i have many reply_timeouts - but these happens in a period of time - for example 30 minutes - but the worker is still dead even then when there are no more reply_timeouts. It remains dead. It was necessary to restart it manually via jkstatus. Another point is the learning - i read the dics - the infos on the apache Website i dont't find other ones - are there other ones ? - and they are not going in depth - if you read the spec and watch the logs it is - for me - very hard to match the things. Also the many possibilities that mod_jk has to prove if there is a connection to the Backend,... - i understand them but check the reality in an error situation is very hard. Under matching i mean Which Part of the Communication sequence failed - why - and causes which error message. But i will try - and study also the mailing list.. Thank you for your time - tomorrow we will have the new version and will see what happens. best ahmed Original-Nachricht Datum: Wed, 20 Feb 2008 15:56:42 +0100 Von: Rainer Jung [EMAIL PROTECTED] An: Tomcat Users List users@tomcat.apache.org Betreff: Re: mod_jk Problems - - worker went to error state and dont recover [EMAIL PROTECTED] wrote: See Thread at: http://www.techienuggets.com/Detail?tx=25608 Posted on behalf of a User Hallo to all, After long unsuccessful research i hope someone can give me a hint to the following problems. Our Apache-mod_jk-Tomcat Infrastructur was running without Problems for about one year-than since two month mod_jk errors occurs. We upgraded the mod_jk Version, made improvements in the worker.properties - the problems changed and get less but sometimes they appear further on. It seems that the mod_jk worker loose the connection to their Tomcat-Backendserver - there are messages in the mod_jk log Files which points in this direction. Normally this seems not to be a big problem - but under certain conditions (which ?) the worker goes to an error state and cannot recover itself- must be done manually. Problem 1: The Tomcats are reachable - unknown why the workers think the server is dead ? Problem 2: I have no idea why the worker goes to an error state and cannot recover. 2 is a consequence of 1 Problem3: I miss explanations of logged messages - i read the messages - but cannot match them to the situation - when does a worker post this messages 1 is a consequence of these messages [Wed Feb 20 10:04:01.889 2008] [19237:3086010048] [info] jk_handler::mod_jk.c (2270): Aborting connection for worker=ajp_ggi [Wed Feb 20 10:04:39.799 2008] [19294:3086010048] [error] ajp_get_reply::jk_ajp_common.c (1623): (INETP1011) Timeout with waiting reply from tomcat. Tomcat is down, stopped or network problems (errno=110) [Wed Feb 20 10:04:39.799 2008] [19294:3086010048] [error] ajp_service::jk_ajp_common.c (2034): (INETP1011) receiving reply from tomcat failed with out recovery in send loop attempt=0 [Wed Feb 20 10:04:41.799 2008] [19294:3086010048] [error] service::jk_lb_worker.c (1105): unrecoverable error 504, request failed. Tomcat failed in the middle of request, we can't recover to another instance. The second line tells us, that your configured reply_timeout fired. You set it to 12 (2 minutes), so there are requests taking longer than 2 minutes on the backend, before the first response packet comes back from the backend. With your configuration mod_jk then doesn't wait any longer on the reply *and puts the backend into error mode*. Up until version 1.2.25, if you use a reply-timeout, you need to set it to a high number which justifies the resoning if it takes that long, that something is wrong with the backend. Reality shows: there is no such number. Often there are few requests that take unaccetably long on the backend *although* the backend is still working. So in 1.2.25 we added max_reply_timeouts. With this set in addition to reply_timeout, mod_jk will abort waiting for a reply after reply_timeout, but allow some timeouts before actually deciding to put the backend into error. Unfortunately the implementation of
RE: different context on different ports, but one tomcat
From: Szabolcs Márton [mailto:[EMAIL PROTECTED] Subject: different context on different ports, but one tomcat I have ONE instance of Tomcat with 3 different webapps (context) instance#1: accept connection only on port 80 from anywhere instance#2: accept connections only on https port from anywhere instance#3 accept connections on port 7080 but only from localhost You didn't bother to tell us what level of Tomcat you're using, but this should be a starting point for the current version: http://tomcat.apache.org/tomcat-6.0-doc/config/valve.html#Remote%20Address%20Filter You will probably have to extend the above filter to add checks for port numbers and secure connections. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: different context on different ports, but one tomcat
From: Caldarale, Charles R Subject: RE: different context on different ports, but one tomcat From: Szabolcs Márton [mailto:[EMAIL PROTECTED] Subject: different context on different ports, but one tomcat I have ONE instance of Tomcat with 3 different webapps (context) instance#1: accept connection only on port 80 from anywhere instance#2: accept connections only on https port from anywhere instance#3 accept connections on port 7080 but only from localhost You didn't bother to tell us what level of Tomcat you're using, but this should be a starting point for the current version: http://tomcat.apache.org/tomcat-6.0-doc/config/valve.html#Remo te%20Address%20Filter You will probably have to extend the above filter to add checks for port numbers and secure connections. Forgot to mention that #2 should be handled by configuring a transport-guarantee of CONFIDENTIAL in its web.xml descriptor. Why do you think it's necesary to prohibit https access to application #1? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: different context on different ports, but one tomcat
If the webapps shall be completely isolated and shall not share connectors it could be an option to define three separate services in server.xml. Then the transport guarantee for webapp2 is given by the server configuration. You should be aware that you must assign separate thread pools to each connector and thus need more resources than if your webapps can share a connector. -- Matthias Server port=8005 shutdown=SHUTDOWN !-- listener and resource definitions skipped -- Service name=Catalina1 Connector port=80 protocol=HTTP/1.1 connectionTimeout=2 / Engine name=Catalina1 defaultHost=localhost !-- Valve, realm etc. skipped -- Host name=localhost appBase=webapps1 unpackWARs=true autoDeploy=true xmlValidation=false xmlNamespaceAware=false /Host /Engine /Service Service name=Catalina2 Connector port=8443 protocol=HTTP/1.1 SSLEnabled=true scheme=https secure=true clientAuth=false sslProtocol=TLS / Engine name=Catalina2 defaultHost=localhost !-- Valve, realm etc. skipped -- Host name=localhost appBase=webapps2 unpackWARs=true autoDeploy=true xmlValidation=false xmlNamespaceAware=false /Host /Engine /Service Service name=Catalina3 Connector port=7080 address=127.0.0.1 protocol=HTTP/1.1 / Engine name=Catalina3 defaultHost=localhost !-- Valve, realm etc. skipped -- Host name=localhost appBase=webapps3 unpackWARs=true autoDeploy=true xmlValidation=false xmlNamespaceAware=false /Host /Engine /Service /Server -Original Message- From: Szabolcs Márton [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 20, 2008 5:54 PM To: users@tomcat.apache.org Subject: different context on different ports, but one tomcat Hi! anybody has idea what should i do, when i would like the following to happen: I have ONE instance of Tomcat with 3 different webapps (context) instance#1: accept connection only on port 80 from anywhere instance#2: accept connections only on https port from anywhere instance#3 accept connections on port 7080 but only from localhost this is possible in tomcat? firstly only with tomcat, no firewall or apache! if it is not possible, that any tricks appropiated :) thx Saby - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk Problems - - worker went to error state and dont recover
Ahmed Musa wrote:
Hello,
Wow -thank you very much Rainer for your very quick and informative answer.
I will go to 1.2.26 and think about some smoother Values for reply_timeout
and max_reply_timeouts.
I will search for the requests which causes the Problems - becasue i still log the response time in your mentioned way - but I am not sure that the Userrequests are responsible for the Situation.
One note: for Apache httpd 2.x %d is microseconds (there is no format
for milliseconds), for Tomcat %D is milliseconds. As long as you are
searching for the root cause, it might make sense to have both access
logs active to check about duration differences.
So one further question - does mod_jk itself checks if the Backend is reachable - without userrequests?
No. Everything only works on top of user requests.
When there are connections to the Backend - are they closed after the respone
or are the hold open for further requests.
In general hold open. There are parameters on how long they are held
open without more requests before they get shut down, and also how many
might be kept open even when no requests are coming in. Those are the
connection pool parameters, which you will find on
http://tomcat.apache.org/connectors-doc/reference/workers.html
Tomcat also has a connectionTimeout on the connector, which will shut
down a connection from the Tomcat side if it is idle for to long.
If you don't want to reuse connections at all, there's also a setting (a
JkOption in Apache).
Is it possible that the Checkpoint Firewall in Between can be responsible for
the connectivity problem?
It can cut a connection that's idle for too long. Since you have
cping/cpong active via connect_timeout and prepost_timeout, you should
get a cping error message, if the connection was dropped by the firewall
during idle times and mod_jk tries to use it again. The reply timeout in
the error log indicates, that the backend isn't answering. Of course if
it takes *very* long to answer, it might be that the firewall dropped
the connection in between, but then the root cause would still be the
long response time of the backend.
Another point is the not recovering of the worker. Yes, you are right - in
this situation i have many reply_timeouts - but these happens in a period of time - for
example 30 minutes - but the worker is still dead even then when there are no more
reply_timeouts. It remains dead.
It was necessary to restart it manually via jkstatus.
I assume you are using stickyness, so when a session started on a node,
it will stay there. So when a worker is in error for a long time, all
new sessions will start on other nodes. If the worker is ready for
recovery, it needs a request, that doesn't carry a session to get probed
with this request.
In jkstatus, the status of an error worker should switch to REC, when
mod_jk decides that it could send a non-sticky request there (to probe)
and to PRB, during the time this request is on the node, and finally
either to OK or back to ERR depending on the result of the request.
You can log the number of errors (and accesses) that happened on the
node in the httpd access log. If you think that the node simply stays in
error for a long time, then the error count (and access count) should
stay constant. I would expect, that they do not.
Have a look at how LogFormat in Apache httpd works, and then add some of
those documented in
http://tomcat.apache.org/connectors-doc/reference/apache.html
like:
JK_LB_LAST_NAME
JK_LB_LAST_ACCESSED
JK_LB_LAST_ERRORS
JK_LB_LAST_BUSY
JK_LB_LAST_STATE
using the syntax %{JK_LB_LAST_STATE}n etc.
Another point is the learning - i read the dics - the infos on the apache Website i
dont't find other ones - are there other ones ? - and they are not going in depth - if
you read the spec and watch the logs it is - for me - very hard to match the things. Also
the many possibilities that mod_jk has to prove if there is a connection to the
Backend,... - i understand them but check the reality in an error situation is very hard.
Under matching i mean Which Part of the Communication sequence failed - why - and
causes which error message.
But i will try - and study also the mailing list..
It's hard for us too (sometimes).
Thank you for your time - tomorrow we will have the new version and will see
what happens.
best
ahmed
Regards,
Rainer
Original-Nachricht
Datum: Wed, 20 Feb 2008 15:56:42 +0100
Von: Rainer Jung [EMAIL PROTECTED]
An: Tomcat Users List users@tomcat.apache.org
Betreff: Re: mod_jk Problems - - worker went to error state and dont recover
[EMAIL PROTECTED] wrote:
See Thread at: http://www.techienuggets.com/Detail?tx=25608 Posted on
behalf of a User
Hallo to all, After long unsuccessful research i hope someone can
give me a hint to the following problems.
Our Apache-mod_jk-Tomcat Infrastructur was running without Problems
for about one year-than since two month mod_jk
Configuring Default ROOT Context
I am trying to configure Tomcat v6.0. I have a book that is about 4 years old and using it to install. I am having problems setting up for: 1) Servlet reloading (it shows you how to do it for versions 4.xx, but this doesn't seem to work (it tells you to key on a sentence to find where to add some code 'DefaultContext reloadable=true/'. But I could never find the sentence when doing a search in server.xml. 2) I would like to enable the ROOT context. It says to uncomment the line 'context path=' docBase=ROOT debug=0/', but again, I can't find this line in server.xml. Any help would be great! osubb -- View this message in context: http://www.nabble.com/Configuring-Default-ROOT-Context-tp15595290p15595290.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OT: a java question - static initialization
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kenneth,
Kenneth Westelinck wrote:
| Did a quick test on 1.6.0 update 2 and the static block does get called. I
| guess this is a bug.
Er, this code doesn't look like it should compile:
| class Foo {
|
| private static int;
|
Isn't there an expected identifier?
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAke8fUQACgkQ9CaO5/Lv0PBEGQCgrUzyijqDv/5+AnDX6H/h9Xsa
KMAAoJC6KSnAsy4g3x4zNu67J48HzPRV
=eBYe
-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]
Re: Apache2 and tomcat5.5
I have changed in server.xml (as root) to Connector port=80 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 / !-- A Connector using the shared thread pool-- !-- Connector executor=tomcatThreadPool port=80 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 / I've stopped the httd service I've added to D-Link router Virtual Server List Name Private IP Protocol Schedule 87.227.4.194 192.168.0.135 TCP 80/80 always 87.227.4.194 192.168.0.135 TCP 8084/8084 always and the result of running http://87.227.4.194 is Unable to connect Firefox can't establish a connection to the server at 87.227.4.194. On Wed, 2008-02-20 at 11:06 -0500, Len Popp wrote: Yes, Tomcat is a regular web server as well as an application server. To use Tomcat as your web server, 1. Don't run the Apache2 web server. 2. Configure Tomcat to listen on the correct HTTP port. In conf/server.xml where it says Connector port=8080 change it to Connector port=80 (or whatever port Apache 2 was using - could be different depending on how your gateway router is set up) - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache2 and tomcat5.5
Does Tomcat work locally on the server? i.e. on the server computer itself, if you browse to http://localhost/ do you see Tomcat's welcome page? -- Len On Feb 20, 2008 3:57 PM, elvberg [EMAIL PROTECTED] wrote: I have changed in server.xml (as root) to Connector port=80 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 / !-- A Connector using the shared thread pool-- !-- Connector executor=tomcatThreadPool port=80 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 / I've stopped the httd service I've added to D-Link router Virtual Server List Name Private IP Protocol Schedule 87.227.4.194 192.168.0.135 TCP 80/80 always 87.227.4.194 192.168.0.135 TCP 8084/8084 always and the result of running http://87.227.4.194 is Unable to connect Firefox can't establish a connection to the server at 87.227.4.194. On Wed, 2008-02-20 at 11:06 -0500, Len Popp wrote: Yes, Tomcat is a regular web server as well as an application server. To use Tomcat as your web server, 1. Don't run the Apache2 web server. 2. Configure Tomcat to listen on the correct HTTP port. In conf/server.xml where it says Connector port=8080 change it to Connector port=80 (or whatever port Apache 2 was using - could be different depending on how your gateway router is set up) - 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]
Re: Apache2 and tomcat5.5
I see Tomcat's welcome page if I browse http://localhost:8084/ or http://192.168.0.135:8084 /dan On Wed, 2008-02-20 at 16:12 -0500, Len Popp wrote: Does Tomcat work locally on the server? i.e. on the server computer itself, if you browse to http://localhost/ do you see Tomcat's welcome page? - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache2 and tomcat5.5
The Tomcat server is not running as a service, it's running as an integrated part of the NetBeans IDE 6.0.1. 8084 is the port HTTP/1.1 I need tomcat as an application server (as well as a web server). /dan On Wed, 2008-02-20 at 13:19 -0800, Hassan Schroeder wrote: On Wed, Feb 20, 2008 at 12:57 PM, elvberg [EMAIL PROTECTED] wrote: I've added to D-Link router Virtual Server List Name Private IP Protocol Schedule 87.227.4.194 192.168.0.135 TCP 80/80 always 87.227.4.194 192.168.0.135 TCP 8084/8084 always Why did you feel the need to change this, if you were able to connect to the instance of httpd before? And what's the 8084 for? But as already suggested, make sure that Tomcat's actually running and can be accessed locally; if not, check your startup logs. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache2 and tomcat5.5
On Wed, Feb 20, 2008 at 1:27 PM, elvberg [EMAIL PROTECTED] wrote: The Tomcat server is not running as a service, it's running as an integrated part of the NetBeans IDE 6.0.1. Personally, I'd just install Tomcat standalone outside the IDE and make life a whole lot easier :-) But in any case, if your server.xml file really has a Connector defined for port 80, you should look in your startup log to see if it's running, and if not, why not. -- Hassan Schroeder [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]
Re: Apache2 and tomcat5.5
So Tomcat is running on port 8084 but the Connector config you posted earlier says it's on port 80... Something's wrong but I can't think what. Sorry. -- Len On Feb 20, 2008 4:16 PM, elvberg [EMAIL PROTECTED] wrote: I see Tomcat's welcome page if I browse http://localhost:8084/ or http://192.168.0.135:8084 /dan On Wed, 2008-02-20 at 16:12 -0500, Len Popp wrote: Does Tomcat work locally on the server? i.e. on the server computer itself, if you browse to http://localhost/ do you see Tomcat's welcome page? - 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]
Re: Apache2 and tomcat5.5
If you are running on Linux you may have problems using a 'plain' tomcat installation pointing at port 80. This is a system port and reserved for privileged access. You must 1. use some kind of redirection such as iptables and leave the tomcat mapping at 8080 OR 2 you must run tomcat as root THIS IS VERY BAD DON'T DO THIS OR 3. use something like jsvc and set the 'user' to tomcat after starting up as root. jsvc will start as root and bind to the port and then switch to the non-privileged tomcat user for normal operation. Regards Alan Chaney Hassan Schroeder wrote: On Wed, Feb 20, 2008 at 12:57 PM, elvberg [EMAIL PROTECTED] wrote: I've added to D-Link router Virtual Server List Name Private IP Protocol Schedule 87.227.4.194 192.168.0.135 TCP 80/80 always 87.227.4.194 192.168.0.135 TCP 8084/8084 always Why did you feel the need to change this, if you were able to connect to the instance of httpd before? And what's the 8084 for? But as already suggested, make sure that Tomcat's actually running and can be accessed locally; if not, check your startup logs. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Form data refresh?
I would add a one time token to the request. Do you mean on the client side using javascript or something?
RE: not reading my /etc/tomcat5/tomcat5.conf file
I concur that that's the easiest way to do this. However, if you MUST work with 3rd party repackaged tomcat (or 3rd party repackaged distro versions of anything for that matter), the Cent OS forums would probably be the best place to ask. On Tue, 2008-02-19 at 21:46 -0600, Caldarale, Charles R wrote: From: Kimberly Begley [mailto:[EMAIL PROTECTED] Subject: not reading my /etc/tomcat5/tomcat5.conf file I'm running CentOS 5 with Tomcat5 (5.5.2.0) that came with the install. I'd strongly recommend you throw that away and download and install a real Tomcat from http://tomcat.apache.org. The 3rd-party repackaged versions give no end of headaches. You may also need to install a real JVM; some of the Linux distributions come with GNU Java, and that is not suitable for any real work. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - 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]
Re: not reading my /etc/tomcat5/tomcat5.conf file
Thanks - I did as you suggested and have a new Tomcat5 and JVM running - without any problems so far! Thanks so much, Kimberly On Thu, Feb 21, 2008 at 10:57 AM, Philip Cote [EMAIL PROTECTED] wrote: I concur that that's the easiest way to do this. However, if you MUST work with 3rd party repackaged tomcat (or 3rd party repackaged distro versions of anything for that matter), the Cent OS forums would probably be the best place to ask. On Tue, 2008-02-19 at 21:46 -0600, Caldarale, Charles R wrote: From: Kimberly Begley [mailto:[EMAIL PROTECTED] Subject: not reading my /etc/tomcat5/tomcat5.conf file I'm running CentOS 5 with Tomcat5 (5.5.2.0) that came with the install. I'd strongly recommend you throw that away and download and install a real Tomcat from http://tomcat.apache.org. The 3rd-party repackaged versions give no end of headaches. You may also need to install a real JVM; some of the Linux distributions come with GNU Java, and that is not suitable for any real work. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - 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] -- Kimberly Begley
Re: Form data refresh?
Alaska Winter wrote: I would add a one time token to the request. Do you mean on the client side using javascript or something? Nope... just either a hidden field in the form or if you are building URLs w/ parameters, just add it in. Very simple stuff. 1. tomcat receive's request 2. if it's an action request like adding an item to a cart, check for the presence of the token and compare to the one on the session. 3. On match, change the token in the session so the response can make sure it get's in the response hidden field or urls. Failing a match, create a new one anyway and store it in the session for the response and forward to a safe non-action page like a browse page 4. Build response w/ either the hidden field pre-loaded with the new token or urls built w/ the new token. Nothing so complex as javascript involved. Just straight server-side management. --David - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JASPER libraries incompatibilities
From: Hitesh Raghav [mailto:[EMAIL PROTECTED] Subject: RE: JASPER libraries incompatibilities Is there any URLs about these backward incompatibilities (i.e. Servlet/JSP specs backward incompatibilities)? The specs themselves usually document incompatibilities. Servlet spec: http://jcp.org/aboutJava/communityprocess/mrel/jsr154/index2.html JSP spec: http://jcp.org/aboutJava/communityprocess/final/jsr245/index.html - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Form data refresh?
i think I understand: -- generate unique token=xyz123 and store in the session -- generated catalogue content so that addToCart url's look like this in the html source: http://my.domain.com/addToCart.do?itemId=HB0019?token=xyz123 -- when users adds an item to the cart, check form data token against session token. -- if match, add to cart, generate new token and store in session. -- user clicks 'continue shopping' and new cataloge content is generate with urls containing new session token: http://my.domain.com/addToCart.do?itemId=HB0019?token=bgh456 what happens if user hits the back button to catalogue. Perfectly valid thing to do.
Re: different context on different ports, but one tomcat
Caldarale, Charles R wrote: From: Szabolcs Márton [mailto:[EMAIL PROTECTED] Subject: different context on different ports, but one tomcat I have ONE instance of Tomcat with 3 different webapps (context) instance#1: accept connection only on port 80 from anywhere instance#2: accept connections only on https port from anywhere instance#3 accept connections on port 7080 but only from localhost You didn't bother to tell us what level of Tomcat you're using, but this should be a starting point for the current version: http://tomcat.apache.org/tomcat-6.0-doc/config/valve.html#Remote%20Address%20Filter this would be incorrect, since you've already accepted the connection and parsed the HTTP request. Matthias Reich posted the correct solution, just use multiple Service containers Filip You will probably have to extend the above filter to add checks for port numbers and secure connections. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - 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]
Re: running servlet from java
Hi,
You can change your eclipse setting to invoke a web browser instead of the
default internal one.
start from eclipse menu.
Window - Preference - Internet - Web Browser
Thanks Regards
David
Goran Jambrović [EMAIL PROTECTED]
02/20/2008 08:15 PM
Mail Size: 12872
Please respond to
Tomcat Users List users@tomcat.apache.org
To
users@tomcat.apache.org
cc
Subject
running servlet from java
Our Ref
Your Ref
Hi!
I would like to run a servlet(/FunPacmanServlet) from java.This servlet
would then show a jsp page in web browser. The problem is that the
contents of jsp page is shown in eclipse console, but the browser does
not show the page. Any idea what i'm doing wrong? I am using eclipse
3.2, tomcat 5.5,firefox. Does tomcat maybe need some setting up?
Best regards, Goran
***My main servlet
code:
import java.io.IOException;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.RequestDispatcher;
import org.umb.portal.app.unimod.*;
import com.evelopers.unimod.*;
import java.util.Enumeration;
/**
* Servlet implementation class for Servlet: LoadPortalServlet
*
*/
public class LoadPortalServlet extends javax.servlet.http.HttpServlet
implements javax.servlet.Servlet {
BqPortalEngine fsmEngine = new BqPortalEngine();
public static LoadPortalServlet startServlet = null;
private HttpServletRequest request = null;
private String jspName = main/portal.jsp;
private String userAgent = Mozilla 5.0;
private String contentType = application/x-www-form-urlencoded;
private String accept =
application/x-shockwave-flash,text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5;
private String keepAlive = 300;
private String host = localhost:8080;
private String contentLength = -1;
private String acceptLanguage= sl,en-gb;q=0.7,en;q=0.3;
private String acceptEncoding= gzip,deflate;
private String acceptCharset = ISO-8859-2,utf-8;q=0.7,*;q=0.7;
public HttpServletRequest getRequest() { return request; }
public String getUserAgent() { return userAgent; }
public String getContentType() { return contentType; }
public String getAccept() { return accept; }
public String getKeepAlive() { return keepAlive; }
public String getHost() { return host; }
public String getContentLength() { return contentLength; }
public String getAcceptLanguage() { return acceptLanguage;}
public String getAcceptEncoding() { return acceptEncoding;}
public String getAcceptCharset() { return acceptCharset; }
public LoadPortalServlet() {
super();
}
public void init(){
System.out.println(START);
System.out.println(STOP);
}
public void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException
{
// System.out.println(GLEJ:+fsmEngine.getCounter());
// fsmEngine.fireEvent();
RequestDispatcher dispatcher = request.getRequestDispatcher(jspName);
System.out.println( Request MAIN portal servlet #\n
+ request.getRequestURI() + \n
+ request.getServletPath() + \n
+ request.getServerPort() + \n
+ request.getRemoteHost() + \n
+ request.getAuthType() + \n
+ request.getCharacterEncoding() + \n
+ request.getContentLength() + \n
+ request.getContentType() + \n
+ request.getContextPath() + \n
+ request.getLocalAddr() + \n
+ request.getLocalName()+ \n
+ request.getLocalPort()+ \n
+ request.getMethod()+ \n
+ request.getPathInfo()+ \n
+ request.getPathTranslated()+ \n
+ request.getProtocol()+ \n
+ request.getQueryString()+ \n
+ request.getUserPrincipal()+ \n
+ request.getSession()+ \n
+ request.getRequestURL()+ \n
+ request.getParameter(url) +\n );
for (Enumeration t=request.getHeaderNames(); t.hasMoreElements();)
{
String headerName = (String) t.nextElement();
System.out.println ( # + headerName + # + request.getHeader(
headerName ) +#\n );
}
System.out.println( \n END \n );
this.request = request;
this.startServlet = this;
userAgent = request.getHeader(User-Agent);
accept = request.getHeader(accept);
keepAlive = request.getHeader(keep-alive);
host = request.getHeader(host);
contentLength = request.getHeader(content-length);
acceptLanguage = request.getHeader(accept-language);
acceptEncoding = request.getHeader(accept-encoding);
acceptCharset = request.getHeader(accept-charset);
contentType =
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5;
if (dispatcher != null)
{
dispatcher.forward(request, response);
}
}
protected void doPost(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
doGet(request, response);
}
}
***My java code (only the function
imports):*
import java.io.IOException;
import com.evelopers.common.exception.SystemException;
import com.evelopers.unimod.runtime.context.StateMachineContext;
import
setting up SSL
I'm having a real problem getting SSL working with Tomcat. Back when I was using Apache and mod_jk2, I had SSL working with Tomcat. But now that I've switched to just using Tomcat, I can't seem to get it to work. I'm using Linux (Fedora Core 5) and Tomcat 5.5.26. I've reverted to a clean version of Tomcat. I create a keystore using the following command: % keytool -genkey -alias tomcat -keyalg RSA -keystore temp.kdb (password = changeit) % cp temp.kdb /usr/local/tomcat/conf I then edit server.xml, uncommenting the extra controller, and changing the ports to 80 and 443. Finally, I add the following lines to the https connector: keystoreFile=/usr/local/tomcat/conf/temp.kdb keystorePass=changeit After restarting Tomcat, I am able to connect to http://localhost and http://localhost:443, but any attempt to get to https://localhost just hangs until the browser times out. Catalina.out doesn't list any errors, and in fact says that: Feb 21, 2008 2:24:31 AM org.apache.coyote.http11.Http11AprProtocol start INFO: Starting Coyote HTTP/1.1 on http-80 Feb 21, 2008 2:24:31 AM org.apache.coyote.http11.Http11AprProtocol start INFO: Starting Coyote HTTP/1.1 on http-443 Any ideas? Is it possible that Tomcat isn't able to find the openssl libraries (or something?). I'm really tearing my hair out here - any help would be greatly appreciated. Thanks! Daniel - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
