Re: intermittent connectivity failure under ssl

[Mark Thomas]

On 09/03/18 20:18, Alex O'Ree wrote:
> I'll see what I can cook up. It'll be a complete tomcat setup and it was
> reproducible with just a hello world jsp file + test ssl certs and configs.
> Using any browser or java client connecting to tomcat. Page reloads are
> intermittently failing.  Where's the best place to dump this? And
> obviously, you'll need a windows box to replicate (x64)

Zip up the entire Tomcat dir and put it on dropbox or similar and then
ping me with the download details.

Microsoft kindly provide Apache committers with MSDN subscriptions for
their Apache work so if you include the OS details I can make sure I am
using the same OS.

I'll most likely just extract your changes from the default install and
apply them to a locally built instance. That way I can debug and test
any fixes more easily.

Mark


> 
> On Fri, Mar 9, 2018 at 3:01 PM, Christopher Schultz <
> ch...@christopherschultz.net> wrote:
> 
> Alex,
> 
> On 3/9/18 2:50 PM, Mark Thomas wrote:
 On 09/03/18 19:39, Alex O'Ree wrote:
> So I believe i have a resolution for this issue (still
> undergoing additional testing). I hate SSL by the way. After
> exhaustive scanning of the java.net.debug logs i came up with
> nothing. 0 hints to the problem. I tried with browsers and java
> http clients and all of them ended with a socket exception
> (unexpected end of file). Did i mention i'm using the windows
> variant of tomcat 8.5.28? On a whim, I asked a coworker who has
> been using tomcat for quite some time. He suggested that issue
> may be related to OpenSSL. After checking the configs and reading
> the docs here:
> http://tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html#Edit_the_Tomca
> t_Configuration_File
>
>
> for my setup, it was defaulting to use open ssl since it was not defined
>  in
> the config file. After changing the JSSEImplementation my
> problems appear to be sorted. Literally 3 months trying to solve
> this one. Whatever version of open ssl that comes with the
> windows build of tomcat has something wrong with it.

 Unlikely.

 More likely is that there is a bug in the APR/Native connector. But
 with a reliable way to reproduce the problem, we'll never know.
> 
> If you are willing to see if you can come up with a repeatable test
> case, it would be VERY helpful. Mark has a knack for finding and
> fixing irritating bugs like this in the connector very quickly, but
> not if he can't see the problem happen.
> 
> I'd certainly like to see any issue with the native library (or its
> use of OpenSSL) found and fixed for everyone's sake.
> 
> -chris
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: intermittent connectivity failure under ssl

[Alex O'Ree]

I'll see what I can cook up. It'll be a complete tomcat setup and it was
reproducible with just a hello world jsp file + test ssl certs and configs.
Using any browser or java client connecting to tomcat. Page reloads are
intermittently failing.  Where's the best place to dump this? And
obviously, you'll need a windows box to replicate (x64)

On Fri, Mar 9, 2018 at 3:01 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Alex,
>
> On 3/9/18 2:50 PM, Mark Thomas wrote:
> > On 09/03/18 19:39, Alex O'Ree wrote:
> >> So I believe i have a resolution for this issue (still
> >> undergoing additional testing). I hate SSL by the way. After
> >> exhaustive scanning of the java.net.debug logs i came up with
> >> nothing. 0 hints to the problem. I tried with browsers and java
> >> http clients and all of them ended with a socket exception
> >> (unexpected end of file). Did i mention i'm using the windows
> >> variant of tomcat 8.5.28? On a whim, I asked a coworker who has
> >> been using tomcat for quite some time. He suggested that issue
> >> may be related to OpenSSL. After checking the configs and reading
> >> the docs here:
> >> http://tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html#Edit_the_Tomca
> t_Configuration_File
> >>
> >>
> for my setup, it was defaulting to use open ssl since it was not defined
>  in
> >> the config file. After changing the JSSEImplementation my
> >> problems appear to be sorted. Literally 3 months trying to solve
> >> this one. Whatever version of open ssl that comes with the
> >> windows build of tomcat has something wrong with it.
> >
> > Unlikely.
> >
> > More likely is that there is a bug in the APR/Native connector. But
> > with a reliable way to reproduce the problem, we'll never know.
>
> If you are willing to see if you can come up with a repeatable test
> case, it would be VERY helpful. Mark has a knack for finding and
> fixing irritating bugs like this in the connector very quickly, but
> not if he can't see the problem happen.
>
> I'd certainly like to see any issue with the native library (or its
> use of OpenSSL) found and fixed for everyone's sake.
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlqi6CsACgkQHPApP6U8
> pFjQCw//cTuR+GNMMG/cdhyZ09+bWd6NPDdAdc8/poIPrBoKgz7LbSPiWa5QzZBa
> VlOyRmfHizZPCUslmxxJUEUI45vLzHePmetUQaOfAfLp1QQEnQXnQFtL7/x4/RG8
> TZJLOBud708YSDFKQesHQSxd424+ZFXgn6kGpUXKNRIqkqtlmiVFPQ0uatqNUQTF
> htMcMOhL3cxAXOEqkJL7HAEFnJAR1Q9A1itG2nk2hk2yn0wa2aQxQxp5EEa/Gwts
> +7XgZAiHTxvptJSd7lKpvG3l8wi//aC4JMQQZi9WgJf/+pK3HL5PZ55R52uojB+i
> IVUFOMM/gTavyMrHPvLWNUF2AITzXmov85ZJmRZdOsBT4WaUMr4XawFViktoeJMq
> aQonhP5RCOvWLnKHqxmTShExezV9gs+HgmxSRCVCNF0dqVFIa/X3rm/i/pfJJXCe
> IaXJTMRizpKlQfYz5zrptTUzJ0sfRqxL8WEjz6C4Z1FEOeIqW04V4UsVH2Hz5BUO
> WPBjWq807WjeEcpvwE6YkxcHitXIlof9GcCIFWKE6ub0GOI1QSWHWAOIraHSK8OZ
> jWonnzE/FWojuiK4Ntbx0JrWGgIkXMhBprkHI1WRMk+nbHqT64xYQkhDYl//j5rq
> Va3eZ3gz1yYt4D/Qi8q7lxhqLfe8cNkJeO3gCoPJLuKl+lISTSE=
> =neYx
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: intermittent connectivity failure under ssl

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Alex,

On 3/9/18 2:50 PM, Mark Thomas wrote:
> On 09/03/18 19:39, Alex O'Ree wrote:
>> So I believe i have a resolution for this issue (still
>> undergoing additional testing). I hate SSL by the way. After
>> exhaustive scanning of the java.net.debug logs i came up with
>> nothing. 0 hints to the problem. I tried with browsers and java
>> http clients and all of them ended with a socket exception
>> (unexpected end of file). Did i mention i'm using the windows
>> variant of tomcat 8.5.28? On a whim, I asked a coworker who has 
>> been using tomcat for quite some time. He suggested that issue
>> may be related to OpenSSL. After checking the configs and reading
>> the docs here: 
>> http://tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html#Edit_the_Tomca
t_Configuration_File
>>
>> 
for my setup, it was defaulting to use open ssl since it was not defined
 in
>> the config file. After changing the JSSEImplementation my
>> problems appear to be sorted. Literally 3 months trying to solve
>> this one. Whatever version of open ssl that comes with the
>> windows build of tomcat has something wrong with it.
> 
> Unlikely.
> 
> More likely is that there is a bug in the APR/Native connector. But
> with a reliable way to reproduce the problem, we'll never know.

If you are willing to see if you can come up with a repeatable test
case, it would be VERY helpful. Mark has a knack for finding and
fixing irritating bugs like this in the connector very quickly, but
not if he can't see the problem happen.

I'd certainly like to see any issue with the native library (or its
use of OpenSSL) found and fixed for everyone's sake.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlqi6CsACgkQHPApP6U8
pFjQCw//cTuR+GNMMG/cdhyZ09+bWd6NPDdAdc8/poIPrBoKgz7LbSPiWa5QzZBa
VlOyRmfHizZPCUslmxxJUEUI45vLzHePmetUQaOfAfLp1QQEnQXnQFtL7/x4/RG8
TZJLOBud708YSDFKQesHQSxd424+ZFXgn6kGpUXKNRIqkqtlmiVFPQ0uatqNUQTF
htMcMOhL3cxAXOEqkJL7HAEFnJAR1Q9A1itG2nk2hk2yn0wa2aQxQxp5EEa/Gwts
+7XgZAiHTxvptJSd7lKpvG3l8wi//aC4JMQQZi9WgJf/+pK3HL5PZ55R52uojB+i
IVUFOMM/gTavyMrHPvLWNUF2AITzXmov85ZJmRZdOsBT4WaUMr4XawFViktoeJMq
aQonhP5RCOvWLnKHqxmTShExezV9gs+HgmxSRCVCNF0dqVFIa/X3rm/i/pfJJXCe
IaXJTMRizpKlQfYz5zrptTUzJ0sfRqxL8WEjz6C4Z1FEOeIqW04V4UsVH2Hz5BUO
WPBjWq807WjeEcpvwE6YkxcHitXIlof9GcCIFWKE6ub0GOI1QSWHWAOIraHSK8OZ
jWonnzE/FWojuiK4Ntbx0JrWGgIkXMhBprkHI1WRMk+nbHqT64xYQkhDYl//j5rq
Va3eZ3gz1yYt4D/Qi8q7lxhqLfe8cNkJeO3gCoPJLuKl+lISTSE=
=neYx
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: intermittent connectivity failure under ssl

[Mark Thomas]

On 09/03/18 19:39, Alex O'Ree wrote:
> So I believe i have a resolution for this issue (still undergoing
> additional testing). I hate SSL by the way. After exhaustive scanning of
> the java.net.debug logs i came up with nothing. 0 hints to the problem. I
> tried with browsers and java http clients and all of them ended with a
> socket exception (unexpected end of file). Did i mention i'm using the
> windows variant of tomcat 8.5.28? On a whim, I asked a coworker who has
> been using tomcat for quite some time. He suggested that issue may be
> related to OpenSSL. After checking the configs and reading the docs here:
> http://tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html#Edit_the_Tomcat_Configuration_File
> for my setup, it was defaulting to use open ssl since it was not defined in
> the config file. After changing the JSSEImplementation my problems appear
> to be sorted. Literally 3 months trying to solve this one. Whatever version
> of open ssl that comes with the windows build of tomcat has something wrong
> with it.

Unlikely.

More likely is that there is a bug in the APR/Native connector. But with
a reliable way to reproduce the problem, we'll never know.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: intermittent connectivity failure under ssl

[Alex O'Ree]

So I believe i have a resolution for this issue (still undergoing
additional testing). I hate SSL by the way. After exhaustive scanning of
the java.net.debug logs i came up with nothing. 0 hints to the problem. I
tried with browsers and java http clients and all of them ended with a
socket exception (unexpected end of file). Did i mention i'm using the
windows variant of tomcat 8.5.28? On a whim, I asked a coworker who has
been using tomcat for quite some time. He suggested that issue may be
related to OpenSSL. After checking the configs and reading the docs here:
http://tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html#Edit_the_Tomcat_Configuration_File
for my setup, it was defaulting to use open ssl since it was not defined in
the config file. After changing the JSSEImplementation my problems appear
to be sorted. Literally 3 months trying to solve this one. Whatever version
of open ssl that comes with the windows build of tomcat has something wrong
with it.


On Mon, Mar 5, 2018 at 9:29 AM, Alex O'Ree  wrote:

> thanks. what else could be cause this? Chrome says error empty response
> frequently
>
> On Mon, Mar 5, 2018 at 9:27 AM, Rémy Maucherat  wrote:
>
>> On Mon, Mar 5, 2018 at 2:59 PM, Alex O'Ree  wrote:
>>
>> > I may be on to something. I found at a coderanch something that was
>> > related. I'm using a class that extends Http11NioProtocol to provide
>> > encryption support for the keystore passwords. I was setting the xml
>> > attribute in server.xml/Connector@protocol = the class name of the
>> > extended
>> > class. This may be related to the problem as it looks like the protocol
>> > attribute must be one of HTTP/1.1, etc.
>> >
>> > Assuming this is the issue, which attribute can i used to specify my
>> > overridden class?
>> >
>>
>> That's the correct way to use this attribute, you should specify your
>> custom class that way.
>>
>> For server.xml values encryption, you can also use the Tomcat vault here:
>> https://github.com/picketbox/tomcat-vault
>>
>> Rémy
>>
>>
>> >
>> > On Fri, Mar 2, 2018 at 1:58 PM, Alex O'Ree  wrote:
>> >
>> > > Remy, what more information would you like? Any more info on the issue
>> > > that you are referencing?
>> > >
>> > > On Fri, Mar 2, 2018 at 10:56 AM, Rémy Maucherat 
>> wrote:
>> > >
>> > >> On Fri, Mar 2, 2018 at 4:19 PM, Alex O'Ree 
>> wrote:
>> > >>
>> > >> > Ran into a strange problem, not too sure what the problem is.
>> > Basically,
>> > >> > I'm getting intermittent connectivity from a http client to tomcat
>> but
>> > >> only
>> > >> > through SSL using the Http11NioProtocol. Some http requests go
>> > through,
>> > >> > others fail with the stack trace below. Usually, restarting tomcat
>> > fixes
>> > >> > it, but it appears to be random and unpredictable. This is a bit
>> of a
>> > >> major
>> > >> > issue for me so any help is appreciated.
>> > >> >
>> > >> > Any pointers for how to troubleshoot this? Running tomcat 8.5.28.
>> > >> >
>> > >> > There's no tomcat logs to indicate that there's a problem. The
>> > >> following is
>> > >> > logged on the client side:
>> > >> >
>> > >> > Caused by: java.net.SocketException: SocketException invoking
>> > >> > https://localhost:8443/myproject/services/Endpoint1: Unexpected
>> end
>> > of
>> > >> > file from server
>> > >> >
>> > >> > 
>> > >> >
>> > >> > Caused by: java.net.SocketException: Unexpected end of file from
>> > server
>> > >> > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.
>> > >> > java:792)
>> > >> > at sun.net.www.http.HttpClient.pa
>> rseHTTP(HttpClient.java:647)
>> > >> > at sun.net.www.protocol.http.HttpURLConnection.
>> > getInputStream0(
>> > >> > HttpURLConnection.java:1536)
>> > >> > at sun.net.www.protocol.http.HttpURLConnection.
>> > getInputStream(
>> > >> > HttpURLConnection.java:1441)
>> > >> > at java.net.HttpURLConnection.getResponseCode(
>> > >> > HttpURLConnection.java:480)
>> > >> > at sun.net.www.protocol.https.HttpsURLConnectionImpl.
>> > >> > getResponseCode(HttpsURLConnectionImpl.java:338)
>> > >> > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$
>> > >> > URLConnectionWrappedOutputStream.getResponseCode(
>> > >> > URLConnectionHTTPConduit.java:266)
>> > >> > at org.apache.cxf.transport.http.
>> > HTTPConduit$WrappedOutputStrea
>> > >> m.
>> > >> > handleResponseInternal(HTTPConduit.java:1543)
>> > >> > at org.apache.cxf.transport.http.
>> > HTTPConduit$WrappedOutputStrea
>> > >> m.
>> > >> > handleResponse(HTTPConduit.java:1513)
>> > >> > at org.apache.cxf.transport.http.HTTPConduit$
>> > >> > WrappedOutputStream.close(HTTPConduit.java:1318)
>> > >> > ... 46 more
>> > >> >
>> > >>
>> > >> It's impossible to say without more information, but this could look
>> > like
>> > >> an issue that is fixed in the next build.
>> > >>
>> > >> Rémy
>> > >>

Re: intermittent connectivity failure under ssl

[Alex O'Ree]

thanks. what else could be cause this? Chrome says error empty response
frequently

On Mon, Mar 5, 2018 at 9:27 AM, Rémy Maucherat  wrote:

> On Mon, Mar 5, 2018 at 2:59 PM, Alex O'Ree  wrote:
>
> > I may be on to something. I found at a coderanch something that was
> > related. I'm using a class that extends Http11NioProtocol to provide
> > encryption support for the keystore passwords. I was setting the xml
> > attribute in server.xml/Connector@protocol = the class name of the
> > extended
> > class. This may be related to the problem as it looks like the protocol
> > attribute must be one of HTTP/1.1, etc.
> >
> > Assuming this is the issue, which attribute can i used to specify my
> > overridden class?
> >
>
> That's the correct way to use this attribute, you should specify your
> custom class that way.
>
> For server.xml values encryption, you can also use the Tomcat vault here:
> https://github.com/picketbox/tomcat-vault
>
> Rémy
>
>
> >
> > On Fri, Mar 2, 2018 at 1:58 PM, Alex O'Ree  wrote:
> >
> > > Remy, what more information would you like? Any more info on the issue
> > > that you are referencing?
> > >
> > > On Fri, Mar 2, 2018 at 10:56 AM, Rémy Maucherat 
> wrote:
> > >
> > >> On Fri, Mar 2, 2018 at 4:19 PM, Alex O'Ree 
> wrote:
> > >>
> > >> > Ran into a strange problem, not too sure what the problem is.
> > Basically,
> > >> > I'm getting intermittent connectivity from a http client to tomcat
> but
> > >> only
> > >> > through SSL using the Http11NioProtocol. Some http requests go
> > through,
> > >> > others fail with the stack trace below. Usually, restarting tomcat
> > fixes
> > >> > it, but it appears to be random and unpredictable. This is a bit of
> a
> > >> major
> > >> > issue for me so any help is appreciated.
> > >> >
> > >> > Any pointers for how to troubleshoot this? Running tomcat 8.5.28.
> > >> >
> > >> > There's no tomcat logs to indicate that there's a problem. The
> > >> following is
> > >> > logged on the client side:
> > >> >
> > >> > Caused by: java.net.SocketException: SocketException invoking
> > >> > https://localhost:8443/myproject/services/Endpoint1: Unexpected end
> > of
> > >> > file from server
> > >> >
> > >> > 
> > >> >
> > >> > Caused by: java.net.SocketException: Unexpected end of file from
> > server
> > >> > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.
> > >> > java:792)
> > >> > at sun.net.www.http.HttpClient.
> parseHTTP(HttpClient.java:647)
> > >> > at sun.net.www.protocol.http.HttpURLConnection.
> > getInputStream0(
> > >> > HttpURLConnection.java:1536)
> > >> > at sun.net.www.protocol.http.HttpURLConnection.
> > getInputStream(
> > >> > HttpURLConnection.java:1441)
> > >> > at java.net.HttpURLConnection.getResponseCode(
> > >> > HttpURLConnection.java:480)
> > >> > at sun.net.www.protocol.https.HttpsURLConnectionImpl.
> > >> > getResponseCode(HttpsURLConnectionImpl.java:338)
> > >> > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$
> > >> > URLConnectionWrappedOutputStream.getResponseCode(
> > >> > URLConnectionHTTPConduit.java:266)
> > >> > at org.apache.cxf.transport.http.
> > HTTPConduit$WrappedOutputStrea
> > >> m.
> > >> > handleResponseInternal(HTTPConduit.java:1543)
> > >> > at org.apache.cxf.transport.http.
> > HTTPConduit$WrappedOutputStrea
> > >> m.
> > >> > handleResponse(HTTPConduit.java:1513)
> > >> > at org.apache.cxf.transport.http.HTTPConduit$
> > >> > WrappedOutputStream.close(HTTPConduit.java:1318)
> > >> > ... 46 more
> > >> >
> > >>
> > >> It's impossible to say without more information, but this could look
> > like
> > >> an issue that is fixed in the next build.
> > >>
> > >> Rémy
> > >>
> > >
> > >
> >
>

Re: intermittent connectivity failure under ssl

[Rémy Maucherat]

On Mon, Mar 5, 2018 at 2:59 PM, Alex O'Ree  wrote:

> I may be on to something. I found at a coderanch something that was
> related. I'm using a class that extends Http11NioProtocol to provide
> encryption support for the keystore passwords. I was setting the xml
> attribute in server.xml/Connector@protocol = the class name of the
> extended
> class. This may be related to the problem as it looks like the protocol
> attribute must be one of HTTP/1.1, etc.
>
> Assuming this is the issue, which attribute can i used to specify my
> overridden class?
>

That's the correct way to use this attribute, you should specify your
custom class that way.

For server.xml values encryption, you can also use the Tomcat vault here:
https://github.com/picketbox/tomcat-vault

Rémy


>
> On Fri, Mar 2, 2018 at 1:58 PM, Alex O'Ree  wrote:
>
> > Remy, what more information would you like? Any more info on the issue
> > that you are referencing?
> >
> > On Fri, Mar 2, 2018 at 10:56 AM, Rémy Maucherat  wrote:
> >
> >> On Fri, Mar 2, 2018 at 4:19 PM, Alex O'Ree  wrote:
> >>
> >> > Ran into a strange problem, not too sure what the problem is.
> Basically,
> >> > I'm getting intermittent connectivity from a http client to tomcat but
> >> only
> >> > through SSL using the Http11NioProtocol. Some http requests go
> through,
> >> > others fail with the stack trace below. Usually, restarting tomcat
> fixes
> >> > it, but it appears to be random and unpredictable. This is a bit of a
> >> major
> >> > issue for me so any help is appreciated.
> >> >
> >> > Any pointers for how to troubleshoot this? Running tomcat 8.5.28.
> >> >
> >> > There's no tomcat logs to indicate that there's a problem. The
> >> following is
> >> > logged on the client side:
> >> >
> >> > Caused by: java.net.SocketException: SocketException invoking
> >> > https://localhost:8443/myproject/services/Endpoint1: Unexpected end
> of
> >> > file from server
> >> >
> >> > 
> >> >
> >> > Caused by: java.net.SocketException: Unexpected end of file from
> server
> >> > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.
> >> > java:792)
> >> > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
> >> > at sun.net.www.protocol.http.HttpURLConnection.
> getInputStream0(
> >> > HttpURLConnection.java:1536)
> >> > at sun.net.www.protocol.http.HttpURLConnection.
> getInputStream(
> >> > HttpURLConnection.java:1441)
> >> > at java.net.HttpURLConnection.getResponseCode(
> >> > HttpURLConnection.java:480)
> >> > at sun.net.www.protocol.https.HttpsURLConnectionImpl.
> >> > getResponseCode(HttpsURLConnectionImpl.java:338)
> >> > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$
> >> > URLConnectionWrappedOutputStream.getResponseCode(
> >> > URLConnectionHTTPConduit.java:266)
> >> > at org.apache.cxf.transport.http.
> HTTPConduit$WrappedOutputStrea
> >> m.
> >> > handleResponseInternal(HTTPConduit.java:1543)
> >> > at org.apache.cxf.transport.http.
> HTTPConduit$WrappedOutputStrea
> >> m.
> >> > handleResponse(HTTPConduit.java:1513)
> >> > at org.apache.cxf.transport.http.HTTPConduit$
> >> > WrappedOutputStream.close(HTTPConduit.java:1318)
> >> > ... 46 more
> >> >
> >>
> >> It's impossible to say without more information, but this could look
> like
> >> an issue that is fixed in the next build.
> >>
> >> Rémy
> >>
> >
> >
>

Re: intermittent connectivity failure under ssl

[Alex O'Ree]

I may be on to something. I found at a coderanch something that was
related. I'm using a class that extends Http11NioProtocol to provide
encryption support for the keystore passwords. I was setting the xml
attribute in server.xml/Connector@protocol = the class name of the extended
class. This may be related to the problem as it looks like the protocol
attribute must be one of HTTP/1.1, etc.

Assuming this is the issue, which attribute can i used to specify my
overridden class?

On Fri, Mar 2, 2018 at 1:58 PM, Alex O'Ree  wrote:

> Remy, what more information would you like? Any more info on the issue
> that you are referencing?
>
> On Fri, Mar 2, 2018 at 10:56 AM, Rémy Maucherat  wrote:
>
>> On Fri, Mar 2, 2018 at 4:19 PM, Alex O'Ree  wrote:
>>
>> > Ran into a strange problem, not too sure what the problem is. Basically,
>> > I'm getting intermittent connectivity from a http client to tomcat but
>> only
>> > through SSL using the Http11NioProtocol. Some http requests go through,
>> > others fail with the stack trace below. Usually, restarting tomcat fixes
>> > it, but it appears to be random and unpredictable. This is a bit of a
>> major
>> > issue for me so any help is appreciated.
>> >
>> > Any pointers for how to troubleshoot this? Running tomcat 8.5.28.
>> >
>> > There's no tomcat logs to indicate that there's a problem. The
>> following is
>> > logged on the client side:
>> >
>> > Caused by: java.net.SocketException: SocketException invoking
>> > https://localhost:8443/myproject/services/Endpoint1: Unexpected end of
>> > file from server
>> >
>> > 
>> >
>> > Caused by: java.net.SocketException: Unexpected end of file from server
>> > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.
>> > java:792)
>> > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
>> > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(
>> > HttpURLConnection.java:1536)
>> > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(
>> > HttpURLConnection.java:1441)
>> > at java.net.HttpURLConnection.getResponseCode(
>> > HttpURLConnection.java:480)
>> > at sun.net.www.protocol.https.HttpsURLConnectionImpl.
>> > getResponseCode(HttpsURLConnectionImpl.java:338)
>> > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$
>> > URLConnectionWrappedOutputStream.getResponseCode(
>> > URLConnectionHTTPConduit.java:266)
>> > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStrea
>> m.
>> > handleResponseInternal(HTTPConduit.java:1543)
>> > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStrea
>> m.
>> > handleResponse(HTTPConduit.java:1513)
>> > at org.apache.cxf.transport.http.HTTPConduit$
>> > WrappedOutputStream.close(HTTPConduit.java:1318)
>> > ... 46 more
>> >
>>
>> It's impossible to say without more information, but this could look like
>> an issue that is fixed in the next build.
>>
>> Rémy
>>
>
>

Re: intermittent connectivity failure under ssl

[Alex O'Ree]

Remy, what more information would you like? Any more info on the issue that
you are referencing?

On Fri, Mar 2, 2018 at 10:56 AM, Rémy Maucherat  wrote:

> On Fri, Mar 2, 2018 at 4:19 PM, Alex O'Ree  wrote:
>
> > Ran into a strange problem, not too sure what the problem is. Basically,
> > I'm getting intermittent connectivity from a http client to tomcat but
> only
> > through SSL using the Http11NioProtocol. Some http requests go through,
> > others fail with the stack trace below. Usually, restarting tomcat fixes
> > it, but it appears to be random and unpredictable. This is a bit of a
> major
> > issue for me so any help is appreciated.
> >
> > Any pointers for how to troubleshoot this? Running tomcat 8.5.28.
> >
> > There's no tomcat logs to indicate that there's a problem. The following
> is
> > logged on the client side:
> >
> > Caused by: java.net.SocketException: SocketException invoking
> > https://localhost:8443/myproject/services/Endpoint1: Unexpected end of
> > file from server
> >
> > 
> >
> > Caused by: java.net.SocketException: Unexpected end of file from server
> > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.
> > java:792)
> > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
> > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(
> > HttpURLConnection.java:1536)
> > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(
> > HttpURLConnection.java:1441)
> > at java.net.HttpURLConnection.getResponseCode(
> > HttpURLConnection.java:480)
> > at sun.net.www.protocol.https.HttpsURLConnectionImpl.
> > getResponseCode(HttpsURLConnectionImpl.java:338)
> > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$
> > URLConnectionWrappedOutputStream.getResponseCode(
> > URLConnectionHTTPConduit.java:266)
> > at org.apache.cxf.transport.http.HTTPConduit$
> WrappedOutputStream.
> > handleResponseInternal(HTTPConduit.java:1543)
> > at org.apache.cxf.transport.http.HTTPConduit$
> WrappedOutputStream.
> > handleResponse(HTTPConduit.java:1513)
> > at org.apache.cxf.transport.http.HTTPConduit$
> > WrappedOutputStream.close(HTTPConduit.java:1318)
> > ... 46 more
> >
>
> It's impossible to say without more information, but this could look like
> an issue that is fixed in the next build.
>
> Rémy
>

Re: intermittent connectivity failure under ssl

[Rémy Maucherat]

On Fri, Mar 2, 2018 at 4:19 PM, Alex O'Ree  wrote:

> Ran into a strange problem, not too sure what the problem is. Basically,
> I'm getting intermittent connectivity from a http client to tomcat but only
> through SSL using the Http11NioProtocol. Some http requests go through,
> others fail with the stack trace below. Usually, restarting tomcat fixes
> it, but it appears to be random and unpredictable. This is a bit of a major
> issue for me so any help is appreciated.
>
> Any pointers for how to troubleshoot this? Running tomcat 8.5.28.
>
> There's no tomcat logs to indicate that there's a problem. The following is
> logged on the client side:
>
> Caused by: java.net.SocketException: SocketException invoking
> https://localhost:8443/myproject/services/Endpoint1: Unexpected end of
> file from server
>
> 
>
> Caused by: java.net.SocketException: Unexpected end of file from server
> at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.
> java:792)
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(
> HttpURLConnection.java:1536)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(
> HttpURLConnection.java:1441)
> at java.net.HttpURLConnection.getResponseCode(
> HttpURLConnection.java:480)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.
> getResponseCode(HttpsURLConnectionImpl.java:338)
> at org.apache.cxf.transport.http.URLConnectionHTTPConduit$
> URLConnectionWrappedOutputStream.getResponseCode(
> URLConnectionHTTPConduit.java:266)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.
> handleResponseInternal(HTTPConduit.java:1543)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.
> handleResponse(HTTPConduit.java:1513)
> at org.apache.cxf.transport.http.HTTPConduit$
> WrappedOutputStream.close(HTTPConduit.java:1318)
> ... 46 more
>

It's impossible to say without more information, but this could look like
an issue that is fixed in the next build.

Rémy

intermittent connectivity failure under ssl

[Alex O'Ree]

Ran into a strange problem, not too sure what the problem is. Basically,
I'm getting intermittent connectivity from a http client to tomcat but only
through SSL using the Http11NioProtocol. Some http requests go through,
others fail with the stack trace below. Usually, restarting tomcat fixes
it, but it appears to be random and unpredictable. This is a bit of a major
issue for me so any help is appreciated.

Any pointers for how to troubleshoot this? Running tomcat 8.5.28.

There's no tomcat logs to indicate that there's a problem. The following is
logged on the client side:

Caused by: java.net.SocketException: SocketException invoking
https://localhost:8443/myproject/services/Endpoint1: Unexpected end of
file from server



Caused by: java.net.SocketException: Unexpected end of file from server
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:792)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1536)
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
at 
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
at 
sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
at 
org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:266)
at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1543)
at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1513)
at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1318)
... 46 more