Sorry, mobile typo. Soap stack, as in cxf, axis, sun jaxws ri
On Thu, Oct 4, 2018, 12:57 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Alex,
>
> On 10/3/18 20:25, Alex O'Ree wrote:
> > Thanks Chris. I ended up using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alex,
On 10/3/18 20:25, Alex O'Ree wrote:
> Thanks Chris. I ended up using aggressive read timeout values on
> the Web service clients by adding properties to the binding
> provider. Thing is, every jre version and soap attacks use
> different
Thanks Chris. I ended up using aggressive read timeout values on the Web
service clients by adding properties to the binding provider. Thing is,
every jre version and soap attacks use different versions which made this
much harder to track down.
On Tue, Oct 2, 2018, 1:44 PM Christopher Schultz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alex,
On 9/29/18 08:31, Alex O'Ree wrote:
> Does tomcat detect or mitigate against half open tcp connections?
Not directly. Basically, that's the OS's job.
> I recently ran into an issue where something in between a java
> jaxws client and a
Does tomcat detect or mitigate against half open tcp connections? I
recently ran into an issue where something in between a java jaxws client
and a jaxws service running in tomcat is interfering with the tcp stream.
Resolving this client side has been a challenge due the transmitting thread
