Re: Favicon for resources when using multiple webapps

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Rebecca, On 11/3/16 4:16 PM, Maxfield, Rebecca A wrote: > Hi there, > > I have a Tomcat installation running a few different web apps > (different instances of XTF, if it matters), and each of these has > some resources (PDFs, raw XML, etc.)

Re: Apache tomcat concurrency issue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Miguel Angel, On 11/3/16 12:52 PM, Roldan, Miguel Angel [Global Data & Content] wrote: (Moving this up to the top:) > Httpd apache server on the front-end v. 2.2 connected to apache > tomcat using AJP connector 1.3 > > Apache tomcat 7.0.56

Re: JNDI look up with tomcat 8.5.6

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ajay, On 11/3/16 12:41 AM, Ajay Bilotia wrote: > *Below code is for JNDI look up which is working fine in tomcat 7 > and 8 .* > > InitialContext initContext = new InitialContext(); DataSource ds = >

Tomcat 8.5.5 (8.5+) Default Cookie Processor breaks persistent cookies for all IE versions

Sorry if this has been already asked. I searched the archives and didn't find what I was looking for. Has anyone else run into an issue with persistent cookies in Tomcat 8.5+ and IE not working? We are seeing an issue where the new default cookie processor,

Re: MaxInactiveInterval

On 04/11/2016 15:53, Caldarale, Charles R wrote: >> From: Mark Thomas [mailto:ma...@apache.org] Subject: Re: >> MaxInactiveInterval > >> On 04/11/2016 15:07, André Warnier (tomcat) wrote: >>> A log message in an application running under Tomcat 8 mentions >>> the "MaxInactiveInterval" setting,

Re: jasper

Hi, 2016-11-04 19:40 GMT+02:00 Jason Hall : > > Possible issue with generated source from jsp(s). > > I current installed Tomcat 8.5.6 and use it with netbeans. > > On one of my JSP files, it is creating a source file with a try/catch block that is MUCH greater than the

jasper

Possible issue with generated source from jsp(s). I current installed Tomcat 8.5.6 and use it with netbeans. On one of my JSP files, it is creating a source file with a try/catch block that is MUCH greater than the 64K limit set by the JVM. On glassfish and websphere, this does not

RE: MaxInactiveInterval

> From: Mark Thomas [mailto:ma...@apache.org] > Subject: Re: MaxInactiveInterval > On 04/11/2016 15:07, André Warnier (tomcat) wrote: > > A log message in an application running under Tomcat 8 mentions the > > "MaxInactiveInterval" setting, saying that it is a bit short.. > > > > I think that I

Re: MaxInactiveInterval

On 04/11/2016 15:07, André Warnier (tomcat) wrote: > Hi. > > A log message in an application running under Tomcat 8 mentions the > "MaxInactiveInterval" setting, saying that it is a bit short.. > > The only place in the Tomcat 8 documentation where I find this setting, > is in >

MaxInactiveInterval

Hi. A log message in an application running under Tomcat 8 mentions the "MaxInactiveInterval" setting, saying that it is a bit short.. The only place in the Tomcat 8 documentation where I find this setting, is in https://tomcat.apache.org/tomcat-8.0-doc/config/manager.html where it says that

Re: JNDI lookup failure with tomcat 8.5.6

Hi, Is there a way to add our application's contextclassloader to the list of tomcat's " Bindings class loader list " so that "ContextBindings.isClassLoaderBound()" returns true? Please correct me if i'm wrong in understanding the problem!! Thanks, Padma On Fri, Nov 4, 2016 at 4:16 PM, Mark

Re: JNDI lookup failure with tomcat 8.5.6

Hi Mark, Thanks for your quick reply . Sorry to bug you , I didn't get you. Will you please explain a bit on how to make the custom loader as parent (any configuration changes )? Thanks & Regards, Padma On Fri, Nov 4, 2016 at 4:16 PM, Mark Thomas wrote: > On 04/11/2016

Re: JNDI lookup failure with tomcat 8.5.6

On 04/11/2016 10:45, padma T wrote: > Hi, > > Getting ,JNDI lookup failed exception while starting tomcat 8. > > While debugging it was found that getInitialContext() > of org.apache.naming.java.javaURLContextFactory class returns NamingContext > context instead of the custom ContextClassLoader

JNDI lookup failure with tomcat 8.5.6

Hi, Getting ,JNDI lookup failed exception while starting tomcat 8. While debugging it was found that getInitialContext() of org.apache.naming.java.javaURLContextFactory class returns NamingContext context instead of the custom ContextClassLoader set by our application and the reason is