(more info) Re: going crazy with certain mod_jk requests freezing

We actually are seeing error messages in the mod_jk logs now: [Sun Feb 26 01:02:52 2006] [12249:43360] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (10.0.0.9:8009), err=-113 [Sun Feb 26 01:02:52

Re: per-webapp logging problem with Tomcat 5.5

Hello, Andreas Schildbach wrote: My problem is, there is no logging going to any logfile. What am I doing wrong? Do I need to have unique numbers as a prefix to app1 and app2? (could I use 0app1 and 0app2?) I could not see any error but one: handlers =

Re: (more info) Re: going crazy with certain mod_jk requests freezing

I apologize for all the messages. But I thought this might also be useful info: Normally, when I run: netstat -tn | egrep ^tcp.*:8009 on the web server and the app server, the connections match up. However, after I start getting the errors below, they seem to not. For example, I currently have

Re: per-webapp logging problem with Tomcat 5.5

Hello Boris, thanks for your answer. I could not see any error but one: handlers = 1catalina.org.apache.juli.FileHandler, 2localhost.org.apache.juli.FileHandler, 3app1.org.apache.juli.FileHandler, 4app2.org.apache.juli.FileHandler, java.util.logging.ConsoleHandler as first line (aside from

RE: [HELP] Forcing Context Reload (watched resource) via Java Code

Thanks Glen, A new area for me to investigate. I appreciate this is not a common design but I am writing out the datasource configuration details dynamically (which is working fine) and I need to reload Tomcat for these datasources to be setup as it's too late by the time I have written them

Re: JSP with use beans calls do not work

Also Claudio Make SURE your tld's (TagLibDescriptors) and jsp libraries (jars) are located in your WEB-INF/lib folder Bon Chance, Martin- - Original Message - From: Claudio Veas To: Tomcat Users List Sent: Saturday, February 25, 2006 3:04 PM Subject: Re: JSP with use beans

Re: [HELP] Forcing Context Reload (watched resource) via Java Code

Good Morning Rob- Message Beans, Session Beans and Business Entity Beans need a J2EE container take a look at Oracle App Server .. a good headsup is available at http://www.oracle.com/oramag/oracle/02-jan/o12industry.html The J2ee authors work for Sun and have posted a very well written

Re: REMOTE_USER forwarding

In your connector config in server.xml add tomcatAuthentication=false. This will allow the auth info from Apache through. Karel Sedlacek wrote: Is there something I need to do in order to make sure that Tomcat is passing along REMOTE_USER? I have a Hyperion report server installation that

Re: regarding tomcat port no

Use netstat to see what ports are open for listening. Versions vary, but I use netstat -tlnp . The option definitions for Mandriva Linux are: -t = tcp connections -l = listening ports -n = numeric only (don't lookup domain and service names) -p = show what process is attached to the port

Re: [HELP] Forcing Context Reload (watched resource) via Java Code

Martin Gainty wrote: Good Morning Rob- Message Beans, Session Beans and Business Entity Beans need a J2EE container take a look at Oracle App Server .. a good headsup is available at http://www.oracle.com/oramag/oracle/02-jan/o12industry.html I think the MBeans[1] refer to Managed Beans,

RE: first jdbc tomcat application

From: umesh balasubramaniam [mailto:[EMAIL PROTECTED] Subject: Re: first jdbc tomcat application I had a similar problem and solved it by adding the parameters using resourceparams instead of specifying all the parameters in the resource tag itself. Where the parameters go depends on the

RE: [HELP] Forcing Context Reload (watched resource) via Java Code

I would be looking for a Tomcat only resolution as I don't want to introduce any more dependencies. I'm pretty sure this is possible with just Tomcat as the html manager webapp is already doing the reloads. Thanks anyway Rob -Original Message- From: Martin Gainty [mailto:[EMAIL

RE: [HELP] Forcing Context Reload (watched resource) via Java Code

From: Rob Gregory [mailto:[EMAIL PROTECTED] Subject: RE: [HELP] Forcing Context Reload (watched resource) via Java Code I'm pretty sure this is possible with just Tomcat as the html manager webapp is already doing the reloads. For experimentation purposes, what happens if you ask the

RE: [HELP] Forcing Context Reload (watched resource) via Java Code

Hi Chuck The manager/html application has the options to reload itself disabled (i.e. they are not links). Calling the manager/reload?path=/manager returns the following:- FAIL - The manager can not reload, undeploy, stop or undeploy itself Which is pretty much as expected. Does this indicate

RE: [HELP] Forcing Context Reload (watched resource) via Java Code

From: Rob Gregory [mailto:[EMAIL PROTECTED] Subject: RE: [HELP] Forcing Context Reload (watched resource) via Java Code Does this indicate that contexts are unable to reload (signal a reload) on it's self? I suspect it's an area the Tomcat developers didn't want to get into - it would

RE: [HELP] Forcing Context Reload (watched resource) via Java Code

A bit messy as the code doing the http request to the manager app would be reloaded before getting the response 'OK' or 'FAIL'. Perhaps a look at the manager source code may give me some pointers Thanks Again Rob -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]

Re: first jdbc tomcat application

On 2/26/06, David McMinn [EMAIL PROTECTED] wrote: I had not added an error-page tag to the web.xml - The default behavior would be a stack trace which would be fine w/ me - In my jsp, I have @ page errorPage=errorpg.jsp.. I don't get a stack trace but I get a page w/ this

Re: per-webapp logging problem with Tomcat 5.5

Good Morning Andreas, Andreas Schildbach wrote: Hello Boris, thanks for your answer. I could not see any error but one: handlers = 1catalina.org.apache.juli.FileHandler, 2localhost.org.apache.juli.FileHandler, 3app1.org.apache.juli.FileHandler, 4app2.org.apache.juli.FileHandler,

Re: per-webapp logging problem with Tomcat 5.5

On 2/26/06, Andreas Schildbach [EMAIL PROTECTED] wrote: Could it be that all libraries I use go to the wrong log? All your libraries, like Spring, will use their own logger names. All these loggers are not defined in your configuration, so will all use the handlers for the root logger