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
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 alloc
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 running
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:
>>>
>>> http://mycompany.com/my
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
>>
>> H
> 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 co
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 thi
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 -->
http://myint
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 restart the application
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"
> maxPostSize="20971520"
> maxThr
10 matches
Mail list logo