eful!
Ian
On 29 July 2011 13:09, Ian Marsh wrote:
> Bugger thanks.
>
> I looked at this but, when I did, I simply compared the two web.xml
> files between Tomcat-7.0.8 and Tomcat-7.0.10 to see if a specific
> setting for development mode was used differently, but the two file
ly 2011 12:27, Mark Thomas wrote:
> On 29/07/2011 09:53, Ian Marsh wrote:
>> Ok thanks... so here's the trace of the 3 biggest
>> org.apache.jasper.servlet.JspServletWrapper objects.
>>
>> I'm just showing the path of the objects that retain the biggest sizes
&
.tld" prefix="bean" %>
<%@ taglib uri="/WEB-INF/struts-bean-el.tld" prefix="bean-el" %>
<%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic" %>
<%@ taglib uri="/WEB-INF/struts-logic-el.tld" prefix="logic-el&q
show that it is very much looking like something within our
JSPs that's causing the issues rather than a difference between the
versions of Tomcat?
Ian
On 26 July 2011 10:52, Mark Thomas wrote:
> On 26/07/2011 10:43, Ian Marsh wrote:
>> Unfortunately the conf changes to fork t
, this has made me concerned that all
request scope variables aren't being released, not just the ones we
use for language text!
Ian
On 25 July 2011 10:45, Ian Marsh wrote:
> Good morning and thanks for the replies!
>
> Unfortunately, as far as I am aware, our bank determines who
gt; On 22/07/2011 20:17, Mark Thomas wrote:
>> On 22/07/2011 17:26, Ian Marsh wrote:
>>> Hi,
>>>
>>> I am in charge of running a Apache-2, Tomcat-7, Ubuntu-10.04 set up
>>> for which we have to be PCI Compliant. We recently upgraded to
>>> Apache-2.2
Hi,
I am in charge of running a Apache-2, Tomcat-7, Ubuntu-10.04 set up
for which we have to be PCI Compliant. We recently upgraded to
Apache-2.2.17 and Tomcat-7.0.8 (from Apache-2.0.x and Tomcat 5.0.28)
in order to comply with the requirements of the PCI Compliance checks
and ironed out any issue
