Re: Tomcat 9 throws exception when sending unencoded charecters in QueryString

Hi Christopher Schultz, I did not mean that the browser is throwing an error. My problem is that in 9.0.13 tomcat's error page is shown instead of my error page. I have given error page location in web.xml. error.jsp is located in the root of my webapp. I know that if I add '^' in

tomcat logs

hello. dear tomcat users! My web application is named "Auction". I've been looking for any log info in "auction.log" file in {cataline_base}/logs At some moment my app stopped to logging to that file. I'm just wondering what went wrong. What pushed my app to stop logging. That file is empty now,

Re: [EXTERNAL] Re: tomcat Finding!

You have to add Valve under Server/Service/Engine/Host/ Works for us as expected On Wed, 19 Dec 2018 at 03:17, wrote: > Added following to the Server.xml, still showing in the latest scan. > > showReport=false" showServerInfo="false" /> > > Thank you, > Danyaal > > -Original Message- >

Re: Tomcat 8 runs under Java 7, but not Java 8

On 12/18/18, 2:49 PM, Caldarale, Charles R wrote: The above indicates you have a Tomcat (or something much like it) already running... You would think so, and yet if I switch the JAVA_HOME line in setenv.sh to Java 7, it launches just fine. . . . WAIT A SECOND! Port 443 is open, and the

RE: Tomcat 8 runs under Java 7, but not Java 8

> From: James H. H. Lampert [mailto:jam...@touchtonecorp.com] > Subject: Re: Tomcat 8 runs under Java 7, but not Java 8 > Excerpt from the relevant time period, catalina.2018-12-18.log: > > 18-Dec-2018 20:18:55.419 SEVERE [main] org.apache.catalina.core.StandardServer.await > >

Re: Tomcat 8 runs under Java 7, but not Java 8

On 12/18/18, 12:50 PM, Mark Thomas wrote: They don't appear to be very helpful. They certainly didn't suggest anything to me. What do the Tomcat logs show? catalina.-mm-dd.log is likely to be the most useful but check them all. Dear Mr. Thomas, et al: Excerpt from the relevant time

Re: Tomcat 8 runs under Java 7, but not Java 8

Hi James, Le 18/12/2018 à 21:40, James H. H. Lampert a écrit : > I just installed Java 8 (not as the default JRE) on a Google Compute > Debian 8 instance that has been running Tomcat 8 under Java 7. I assume you are using the tomcat8 package from the distribution. Tomcat on Debian 8 Jessie is a

Tomcat JMS Setup

Hi, I am trying to integrate ActiveMQ with Tomcat. I have defined a queue, Topic and Connection Factory in Tomcat server.xml and Context.xml file as below. Server.xml === Context.xml: Do I need to create the JMS resources using ActiveMQ console as well in order to use

Re: Tomcat 8 runs under Java 7, but not Java 8

On 18/12/2018 20:40, James H. H. Lampert wrote: > I just installed Java 8 (not as the default JRE) on a Google Compute > Debian 8 instance that has been running Tomcat 8 under Java 7. > > If I change setenv.sh to add >> JAVA_HOME="/usr/lib/jvm/java-8-openjdk-amd64/" > > and I try to "service

Tomcat 8 runs under Java 7, but not Java 8

I just installed Java 8 (not as the default JRE) on a Google Compute Debian 8 instance that has been running Tomcat 8 under Java 7. If I change setenv.sh to add JAVA_HOME="/usr/lib/jvm/java-8-openjdk-amd64/" and I try to "service tomcat8 start," I get Job for tomcat8.service failed because

RE: [EXTERNAL] Re: tomcat Finding!

Added following to the Server.xml, still showing in the latest scan. Thank you, Danyaal -Original Message- From: John Palmer [mailto:johnpalm...@gmail.com] Sent: Friday, December 14, 2018 6:26 PM To: Tomcat Users List Subject: [EXTERNAL] Re: tomcat Finding! WARNING:This is an

Re: log4j app logging

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Michael, On 12/18/18 13:53, Lemke, Michael ST/HZA-ZIC2 wrote: > Thanks, Ryan, this JULI thing actually is what worries me. I don't > care about tomcat's logging at the moment. It is my webapp's > logging I can't figure out. It worked on other

Re: log4j app logging

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Michael, On 12/18/18 12:42, Lemke, Michael ST/HZA-ZIC2 wrote: > I have an old webapp that uses log4j 1.2 and which I am trying to > deploy on tomcat. For the heck of it I can't get tomcat to use the > log4.properties file. What am I doing wrong?

RE: log4j app logging

Thanks, Ryan, this JULI thing actually is what worries me. I don't care about tomcat's logging at the moment. It is my webapp's logging I can't figure out. It worked on other containers. -Original Message- From: Ryan Palmer Sent: Tuesday, December 18, 2018 7:49 PM Michael, Tomcat uses

Re: log4j app logging

Michael, Tomcat uses JULI internally. Have you taken necessary steps to redirect JULI to log4j? Thanks, Ryan From: Lemke, Michael ST/HZA-ZIC2 Sent: Tuesday, December 18, 2018 10:20 AM To: Tomcat Users List Subject: RE: log4j app logging On December 18, 2018

RE: log4j app logging

On December 18, 2018 6:59 PM Ryan Palmer wrote: > >The file needs to be named log4j.properties (or .xml, >.json, etc.) and needs to be in the classpath. You ommitted the 'j'. Thanks for spotting this. Unfortunately, this typo was only in the email: pc# ls

Re: log4j app logging

Michael, The file needs to be named log4j.properties (or .xml, .json, etc.) and needs to be in the classpath. You ommitted the 'j'. Sent from BlueMail On Dec 18, 2018, at 9:42 AM, "Lemke, Michael ST/HZA-ZIC2"

log4j app logging

I have an old webapp that uses log4j 1.2 and which I am trying to deploy on tomcat. For the heck of it I can't get tomcat to use the log4.properties file. What am I doing wrong? tomcat 9.0.6 is installed as a Windows service and does serve my webapp, so the app is working fine. The project is

Re: why can't i login to tomcat7 status page from clean install zip

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Bo, On 12/18/18 00:49, Bo wrote: > here is screenshot > > I just tried again still no working > > > https://i.imgur.com/8bQH2YB.png Your XML is invalid and can't be loaded. The log file should confirm this. Unfortunately, Notepad++ makes it

Re: Tomcat 9 throws exception when sending unencoded charecters in QueryString

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Melvin, On 12/18/18 04:21, Melvin wrote: > Tomcat 9.0.13 I switched from tomcat 8.5.35 to 9.0.13. In 8.5 when > I send an unencoded character in queryString it throws 400 error in > the browser itself and no Exception is thrown or seen explicitly.

Re: why can't i login to tomcat7 status page from clean install zip

On 18/12/2018 13:46, Bo wrote: > apologize for what? Your statement that "tomcat is horribly broken and buggy" who did i insult Everyone who has contributed to Tomcat. Which, by the way, is provided to you free of charge. As is the support you are receiving on this list. > i stand by my

Re: why can't i login to tomcat7 status page from clean install zip

apologize for what? who did i insult i stand by my claim, seems thousands people having this issue, if it was intuitively and well designed, this wouldnt be a thing now would it https://www.centos.org/forums/viewtopic.php?t=46150 On Tue, Dec 18, 2018, at 7:15 AM, Mark Thomas wrote: > On

Re: why can't i login to tomcat7 status page from clean install zip

On 18/12/2018 12:55, Bo wrote: > i tested every possible combination. > > anyone can try it themselves > i listed the steps to duplicate this already > its 100 percent generic > > tomcat is horribly broken and buggy > it wont even allow me to login When things go wrong it is usually a good idea

Re: why can't i login to tomcat7 status page from clean install zip

i tested every possible combination. anyone can try it themselves i listed the steps to duplicate this already its 100 percent generic tomcat is horribly broken and buggy it wont even allow me to login On Tue, Dec 18, 2018, at 1:00 AM, Bob Hall wrote: > Bo, > On Monday, December 17, 2018,

Re: How to use server.xml with embedded Tomcat 9?

On Tue, Dec 18, 2018 at 7:33 AM Ryan Palmer wrote: > Hello, > > I'm using the Tomcat class to embed the container in my application. I > have configured the CATLINA_HOME and _BASE properties, and I know those are > working because the 'work' folder gets generated there as expected. However > if

Tomcat 9 throws exception when sending unencoded charecters in QueryString

Tomcat 9.0.13 I switched from tomcat 8.5.35 to 9.0.13. In 8.5 when I send an unencoded character in queryString it throws 400 error in the browser itself and no Exception is thrown or seen explicitly. After I switched to tomcat 9, when I send an unencoded character in queryString it throws