On 13/05/2016 17:55, Venkata Reddy P wrote:
> Existing implementation:-
>
> In tomcat6.0.43 version, I have enabled the ssl on AJP connector by following
> the below steps
>
> 1) I did override the class "org.apache.jk.common.ChannelSocket" to
> "AjpSslChannelSocket extends ChannelSocket " to
Hi,
Can anyone please help me on this?
Existing implementation:-
In tomcat6.0.43 version, I have enabled the ssl on AJP connector by following
the below steps
1) I did override the class "org.apache.jk.common.ChannelSocket" to
"AjpSslChannelSocket extends ChannelSocket " to enable ssl
On 11/05/2016 02:43, Ooura, Nobuhito wrote:
> Mark and Christopher
>
> Thank you for your reply.
>
>> Are you using mod_jk or mod_proxy_ajp? What versions of everything on the
>> httpd side?
>> Specifically, httpd itself as well as mod_jk (if you are using mod_jk, of
>> course).
>
> I'm using
On 12/05/2016 09:41, Mark Thomas wrote:
> On 10/05/2016 22:00, Thomas Meyer wrote:
>> Hi,
>>
>> I noticed that I can block tomcat 8 by opening 200 connection to the
>> http 1.1 connector and send 512 bytes of zero in each connection.
>>
>> Tomcat 8 seems to block in parseRequestLine() method for
Hello friends,
To start of with, my apologies for sending the mail to two lists, but
as the problem involves around both Tomcat and Apache, I am sending
this email on both lists.
Situation : I have a Debian X64 server running Apache Web-server which
is running a CMS on its own and also
I am using Apache Tomcat 8.0.33
The documentation says:
"The write timeout used when sending WebSocket messages in blocking
mode defaults to 2 milliseconds (20 seconds). This may be changed
by setting the propertyorg.apache.tomcat.websocket.BLOCKING_SEND_TIMEOUT
in the user properties
Hi all,
I dig more into the issue and observed the following and came up with a
solution.
The valve I am using is depending on libthrift and libthrift needs slf4j.
That's the reason to have slf4j in tomcat/lib. The webapp also used slf4j
and it is packed with a higher version of slf4j in
