tomcat cache database server IP forever

Hi All, I have an issue with tomcat dns cache ttl, where if I change the IP address of the database, tomcat still sending connection requests to an old IP until I restart tomcat, this is not the case with Jboss. I verified in java security, this what we have in java. #networkaddress.cache.ttl=-1

Re: FATAL: emalloc(): Unable to allocate 35 bytes

John, On 6/13/2016 9:23 AM, John Beaulaurier -X (jbeaulau - ADVANCED NETWORK INFORMATION INC at Cisco) wrote: > Hello, > > We are running Apache 2.0.63. developer required and this is for use > behind the firewall, with PHP 5.1.5. We are now running into the > FATAL: "emalloc(): Unable to

FATAL: emalloc(): Unable to allocate 35 bytes

Hello, We are running Apache 2.0.63. developer required and this is for use behind the firewall, with PHP 5.1.5. We are now running into the FATAL: "emalloc(): Unable to allocate 35 bytes". Googling I have seen post regarding MPM thread count configurations re this issue, but we are no

Re: Overriding contextPath through (RemoteIp)Valve

On 13/06/2016 15:32, Xavier Dury wrote: > Sorry, resent as plain text: > >> On 13/06/2016 14:23, Xavier Dury wrote: >>> Hi, >>> >>> The recommended approach when using a proxy in front of tomcat is to have >>> the same context path >>> on both sides like this: >>> >>>

RE: Overriding contextPath through (RemoteIp)Valve

Sorry, resent as plain text: > On 13/06/2016 14:23, Xavier Dury wrote: >> Hi, >>  >> The recommended approach when using a proxy in front of tomcat is to have >> the same context path >> on both sides like this: >>  >> http://mycompany.com/myapp --> http://myinternalserver.lan:8080/myapp >>  >>

RE: Overriding contextPath through (RemoteIp)Valve

> On 13/06/2016 14:23, Xavier Dury wrote: > > Hi, > > > > The recommended approach when using a proxy in front of tomcat is to have > > the same context path > > on both sides like this: > > > > http://mycompany.com/myapp --> http://myinternalserver.lan:8080/myapp > > > > Having different

Re: Overriding contextPath through (RemoteIp)Valve

On 13/06/2016 14:23, Xavier Dury wrote: > Hi, > > The recommended approach when using a proxy in front of tomcat is to have the > same context path > on both sides like this: > > http://mycompany.com/myapp --> http://myinternalserver.lan:8080/myapp > > Having different context paths like

Overriding contextPath through (RemoteIp)Valve

Hi, The recommended approach when using a proxy in front of tomcat is to have the same context path on both sides like this: http://mycompany.com/myapp --> http://myinternalserver.lan:8080/myapp Having different context paths like this: http://mycompany.com/mypublicapp -->

Re: Yet another odd file in /tmp created by tomcat7

On Fri, Jun 10, 2016 at 2:19 PM, Scott Derrick wrote: > Tomcat7 > CentOS 6 > > I see the file ehcache-sizeof-agent2473717668134475820.jar in /tmp > > It is created when I run one of my applications for the first time. The > number part of the file name changes every time I

RE: FW: Tomcat 6.0.45 - Problem in creating the socket.

Am 13. Juni 2016 08:01:51 MESZ, schrieb "Radha Krishna Meduri -X (radmedur - HCL TECHNOLOGIES LIMITED at Cisco)" : >Thanks Felix for your reply. Yes the connect has defined properly. > > port="443" protocol="HTTP/1.1" SSLEnabled="true" > maxSavePostSize="-1" >

RE: FW: Tomcat 6.0.45 - Problem in creating the socket.

Thanks Felix for your reply. Yes the connect has defined properly. Above SSL Implementation is custom implantation based on NSS/JSS. As I said same implementation works fine with 6.0.37. Thanks Radhakrishna -Original Message- From: Felix Schumacher