Bill Barker wrote:
> I don't recognize the problem, but AJP12 was deprecated even for 3.3.1a
> (which, for Pid's benifit, was a single security issue bugfix release from
> 3.3.1).
Hat duly tipped.
p
>
> -
> To start a new t
Mark Thomas wrote:
> Pid wrote:
>> Marko Krejic wrote:
>>> Hi,
>>>
>>> We are running Tomcat 3.3.1a on a Windows Server 2003. A apache server is
>>> also installed on the machine as a proxy and it is connected with the
>>> tomcat through AJP12. Tomcat is running on JDK1.4.2_13.
>> The silence y
I don't recognize the problem, but AJP12 was deprecated even for 3.3.1a
(which, for Pid's benifit, was a single security issue bugfix release from
3.3.1). In any case, it will be a bottleneck for any attempt to scale your
application. You should try with the AJP13 connector, which works better
Pid wrote:
> Marko Krejic wrote:
>> Hi,
>>
>> We are running Tomcat 3.3.1a on a Windows Server 2003. A apache server is
>> also installed on the machine as a proxy and it is connected with the tomcat
>> through AJP12. Tomcat is running on JDK1.4.2_13.
>
> The silence you experienced is people
Marko Krejic wrote:
> Hi,
>
> We are running Tomcat 3.3.1a on a Windows Server 2003. A apache server is
> also installed on the machine as a proxy and it is connected with the tomcat
> through AJP12. Tomcat is running on JDK1.4.2_13.
The silence you experienced is people being dumbfounded that
