Re: problem with x:set variables

A bit more info supporting my theory that it is a TC bug. I was running TC 7 pretty much out of the box. The only changed files in the TC 7 tree were the server and web app config files. My doc root with the actual webapps is on another drive and not under the TC folder tree. I installed TC

Re: problem with x:set variables

It appears that the problem was truly a bug in that particular version of Tomcat. I dug through all of the jar files and all possibly custom config items, and found absolutely nothing amiss. Finally, I moved up to Tomcat 8 on the server, and everything works fine now. On 7/21/2015 12:07 PM,

Re: Tomcat8 startup service exit (return value 143)

I have been struggling with an issue which resulted in the same message: "Service exit with a return value of 143". In the end the problem was with a custom init script that was calling jsvc directly. I did not bother to find the precise root cause though. When I saw daemon.sh worked, I simply mod

Re: Tomcat-7.0.61 and SFlow_Valve.jar issue

Am 24. Juli 2015 18:34:14 MESZ, schrieb Sergey : >Sorry, > >Do you mean that I have to recompile SFlow_Valve.jar or our application >which we are running on Tomcat server? SFlow_Valve.jar has the problem, so you have to compile those sources. Regards, Felix > >Thanks! >Sergey > >> On Jul 24

Re: Tomcat-7.0.61 and SFlow_Valve.jar issue

Sorry, Do you mean that I have to recompile SFlow_Valve.jar or our application which we are running on Tomcat server? Thanks! Sergey > On Jul 24, 2015, at 1:46 AM, Felix Schumacher > wrote: > > > > Am 23. Juli 2015 21:04:22 MESZ, schrieb Sergey >: >> I see that i

Re: If there a security hardened / production ready binary distribution?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jim, On 7/23/15 11:14 AM, Jim Sellers wrote: > On Thu, Jul 23, 2015 at 10:50 AM, Mark Thomas > wrote: > >> On 23 July 2015 15:07:01 CEST, Jim Sellers >> wrote: >>> Hi all. >>> >>> Sorry if this has already been answered, but I couldn't find >>>

Re: Tomcat8 startup service exit (return value 143)

On Fri, Jul 24, 2015 at 10:15 AM, Mark Eggers wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 7/24/2015 12:59 AM, Robert Jacobs wrote: > > Hello, > > > > We are having problems getting tomcat to work with JSVC on RHEL 7.1 > > (maipo). We found out that Tomcat restarts do not alway

Re: Tomcat, REMOTE_USER, getRemoteUser()

I agree that mod_proxy_ajp is more commonly supported. I've looked/briefly worked on the mod_jk source and it was pretty awful - but that's what happens to code over time. I see your point regarding the ajp protocol but equally, HTTP is everywhere and if every other part of a web stack is HTTP, the

Re: Tomcat-7.0.61 and SFlow_Valve.jar issue

Am 23. Juli 2015 21:04:22 MESZ, schrieb Sergey : >I see that in SFlow_Valve Source code it’s already “long”: > > long bytes_read = (request.getCoyoteRequest()).getBytesRead(); > >Then what’s wrong and how can I fix this issue? Recompile your code with the jars/sources from newer tomcats? The i

Re: Tomcat, REMOTE_USER, getRemoteUser()

On 23/07/15 20:38, John Baker wrote: > The flag to which you refer is for AJP only, hence the inconsistency (as > AJP becomes less common and reverse proxying HTTP becomes the norm). While I agree with you that the http connector should be consistent with the AJP behavior where possible I'm intere

Re: Tomcat8 startup service exit (return value 143)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/24/2015 12:59 AM, Robert Jacobs wrote: > Hello, > > We are having problems getting tomcat to work with JSVC on RHEL 7.1 > (maipo). We found out that Tomcat restarts do not always result in > expected behaviour. The pattern of this unexpected beha

Tomcat8 startup service exit (return value 143)

Hello, We are having problems getting tomcat to work with JSVC on RHEL 7.1 (maipo). We found out that Tomcat restarts do not always result in expected behaviour. The pattern of this unexpected behavior (Service exit with a return value of 143) is random. This random pattern might depend on the dep