Re: Disable Caching for JNDI Object Factories?

Andreas Schildbach wrote: currently, if I locate a resource (EJB Home) from Tomcat's JNDI Context, and I have configured an Object Factory for that location, the factory is only exactly queried once. For the records: I finally filed a bug about this one. http://issues.apache.org/bug

Disable Caching for JNDI Object Factories?

Hello everyone, currently, if I locate a resource (EJB Home) from Tomcat's JNDI Context, and I have configured an Object Factory for that location, the factory is only exactly queried once. This is very problematic if the connection to the server has been broken (for example by an EJB server

Basic Auth without modification to web.xml?

Hi everyone, Is it possible with Tomcat to "hide" an application behind a Basic Authentication (or something similar), without modifying the web application itself (also not modifying web.xml)? I am thinking about adding a Valve or something to the context.xml. The content to be protected would j

Re: What happened to MailSessionFactory?

Russ Bonsall wrote: We just moved from Tomcat 5.5.17 to 5.5.20. Our application uses the JavaMail Session as a resource configured in the server.xml. When sending an email in our application I was getting the following exception: > =20 javax.naming.NamingException: Could not create resource

JMX remote with JMXMP

Hello everyone, I'd like to remotely access my MBeans by using the JMXMP protocol. JMXMP is an alternative to the default RMI protocol and aims to be much more firewall friendly. I already have downloaded the JMX remote reference implementation and thus have got hold of jmxremote_optional.ja

Re: JMX via SSH tunnel does not work?

Hello Mikolaj, I have set up the JMX server of JDK 1.5.0_06/Tomcat 5.5.15. It works fine locally, I'm testing with "jconsole". However, if I tunnel the JMX port over SSH, it does not work. I can connect to the port, but there is no flow of data. "jconsole" is hanging around for a minute, and

JMX via SSH tunnel does not work?

Hello everyone, I have set up the JMX server of JDK 1.5.0_06/Tomcat 5.5.15. It works fine locally, I'm testing with "jconsole". However, if I tunnel the JMX port over SSH, it does not work. I can connect to the port, but there is no flow of data. "jconsole" is hanging around for a minute, an

Re: per-webapp logging problem with Tomcat 5.5

Hi Boris, I have now switched my server to "one-properties-per-webabb" (inside webapp dir). It's not nice, but it works. Thanks a lot for your help. Regards, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For addition

Re: per-webapp logging problem with Tomcat 5.5

Remy Maucherat wrote: Very funny. Funny what? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: per-webapp logging problem with Tomcat 5.5

Boris Unckel wrote: I have a workaround: You provide a logging.properties in your webapp. All relevant parameters are controlled per system -D properties. A workaround for what? Providing a logging.properties in my webapp is exactly what I'm trying to avoid. What's the relevant parameters, an

Re: per-webapp logging problem with Tomcat 5.5

Boris Unckel wrote: You want to have a _one_ central place for your log configuration _and_ the correct logging just for that application - currently impossible. I would not necessarely say that logging has to be configured in one central place/file, but I think putting logging config _into_

Re: per-webapp logging problem with Tomcat 5.5

Boris Unckel wrote: Could it be that all libraries I use go to the wrong log? This depends on the common and shared classloader. Please put any JAR which is not delivered by Tomcat and already there in a default installation in your WEB-INF/lib folder. Test again. I don't understand. The

Re: per-webapp logging problem with Tomcat 5.5

Remy Maucherat 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 (".handlers"). org.apache.catalina.core.Co

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

per-webapp logging problem with Tomcat 5.5

Hello everyone, I despair of configuring per-webapp logging for Tomcat 5.5, something that was easily possible with swallowOutput on pre-5.5 Tomcats. I've got 2 hosts (app1.de, app2.de), containing one context each. In addition, there is also the localhost context from the example server.xml.