You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Mark Thomas <ma...@apache.org> on 2018/04/04 16:58:57 UTC
Re: Connection closed error and certificateVerification="required"
On 26/03/18 08:25, Richard Tearle wrote:
<snip/>
> I've uploaded a ZIP with my test "UI" code (standalone java program),
> and the "ESB"
> code which goes into tomcat.
>
> https://www.dropbox.com/s/nhfx7va4uzkr728/Source.zip?dl=0
>
> In the support folder within the ZIP are updated scripts to create the
> certificates - which
> now includes generating the client certificate as well. Also in there
> are the server.xml
> and other tomcat configuration files that are changed as part of our
> installation process
> - although these are the same as I'd included in the previous ZIP.
>
> Also included is a very simple shell script I use to call the UI.
> Usually setting the ESB
> delay to 5 seconds causes the connection closed error to occur in
> around 5 minutes of
> running the program.
Thanks. I've got the test application and UI running but I haven't yet
reproduced the problem. What parameters are you calling run-test.sh with?
I'll continue to try and reproduce the issue but I think it makes sense
to try and generate some debug data on your system as you can reproduce it.
The first step is to move to testing on a Tomcat instance built from
source. This will enable me to add additional debug logging as we go to
try and narrow down the root cause. The build process is fairly simple.
You'll need to check out https://svn.apache.org/repos/asf/tomcat/trunk/
and follow the instructions in BUILDING.txt. You won't need a release
build. The default ant deploy should be fine.
Assuming you can still repeat this on a build from trunk, please enable
the following logging:
- SSL debug logging on client and server via -Djavax.net.debug=ssl
- Tomcat I/O layer debug logging by adding the following to
conf/logging.properties:
org.apache.tomcat.util.net.level = FINE
If you can repeat the issue with the above debug logging enabled, if you
can provide the logs for the 30s or so before the error occurs hopefully
there will be some clues in there as to what is going wrong.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Connection closed error and certificateVerification="required"
Posted by lo...@kreuser.name.
Mark,
> Am 19.04.2018 um 20:58 schrieb Mark Thomas <ma...@apache.org>:
>
> On 19/04/18 16:50, Peter@Kreuser-Online wrote:
>
> <snip/>
>
>> Do you mind to share more about the root cause? I’ve followed this mail communication from the start and am curious.
>
> Sure.
>
> Tomcat was configured to require CLIENT-CERT auth and the main client
> was configured to use this. Occasionally, the main client would see
> connection problems when using 8.5.x or later with NIO and the OpenSSL
> TLS implementation.
>
> There was a second client the performed health checks on the server.
> This client did not use a certificate. The requests it made always
> failed but did so with a predictable error message that the health check
> looked for.
>
> OpenSSL error states are stored per thread.
>
> Each Java thread is mapped 1-to-1 to an OS thread.
>
> The sequence of events that cause the problem was as follows:
>
> - Health check ran
> - TLS connection failed because no client certificate was provided
> - OpenSSL set an error state that - depending on the timing of the
> socket closure - was not always cleaned up
> - Standard request was received and was handled by the thread that
> previously experienced the error
> - Because the error had not been cleaned up, this new connection thought
> the error was meant for it and closed the connection
>
> The fix was to ensure that, whenever the Tomcat code made a call to
> OpenSSL that looked like this:
> - Do something via the OpenSSL API
> - Check the OpenSSL error state
>
> the code was changed so it looked like this:
> - Clear the OpenSSL error state
> - Do something via the OpenSSL API
> - Check the OpenSSL error state
>
> I also added a TODO for the arguably more complete fix which is to check
> the OpenSSL error state after every call to the OpenSSL API.
>
>> Let me tell you that your endurance on all the tricky issues here is admirable!
>>
>> Thank you for that!
>
> Thank you.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Much appreciated. That was a mean one.
Best regards.
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Connection closed error and certificateVerification="required"
Posted by Mark Thomas <ma...@apache.org>.
On 19/04/18 16:50, Peter@Kreuser-Online wrote:
<snip/>
> Do you mind to share more about the root cause? I’ve followed this mail communication from the start and am curious.
Sure.
Tomcat was configured to require CLIENT-CERT auth and the main client
was configured to use this. Occasionally, the main client would see
connection problems when using 8.5.x or later with NIO and the OpenSSL
TLS implementation.
There was a second client the performed health checks on the server.
This client did not use a certificate. The requests it made always
failed but did so with a predictable error message that the health check
looked for.
OpenSSL error states are stored per thread.
Each Java thread is mapped 1-to-1 to an OS thread.
The sequence of events that cause the problem was as follows:
- Health check ran
- TLS connection failed because no client certificate was provided
- OpenSSL set an error state that - depending on the timing of the
socket closure - was not always cleaned up
- Standard request was received and was handled by the thread that
previously experienced the error
- Because the error had not been cleaned up, this new connection thought
the error was meant for it and closed the connection
The fix was to ensure that, whenever the Tomcat code made a call to
OpenSSL that looked like this:
- Do something via the OpenSSL API
- Check the OpenSSL error state
the code was changed so it looked like this:
- Clear the OpenSSL error state
- Do something via the OpenSSL API
- Check the OpenSSL error state
I also added a TODO for the arguably more complete fix which is to check
the OpenSSL error state after every call to the OpenSSL API.
> Let me tell you that your endurance on all the tricky issues here is admirable!
>
> Thank you for that!
Thank you.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Connection closed error and certificateVerification="required"
Posted by "Peter@Kreuser-Online" <lo...@kreuser.name>.
Mark,
>> Am 18.04.2018 um 11:55 schrieb Mark Thomas <ma...@apache.org>:
>>
>> On 18/04/18 10:36, Richard Tearle wrote:
>> On 17 April 2018 at 16:45, Richard Tearle
>> <ri...@northgateps.com> wrote:
>>> On 17 April 2018 at 14:54, Mark Thomas <ma...@apache.org> wrote:
>>>>> On 17/04/18 11:36, Mark Thomas wrote:
>>>>> On 17/04/18 10:14, Richard Tearle wrote:
>>>>
>>>> <snip/>
>>>>
>>>>> Now all we need to to do is to figure out how to fix this. With the
>>>>> understanding of what is (probably) going wrong, the problem can be
>>>>> produced with a clean build and the certs we use for unit tests which
>>>>> makes things a lot easier. I hope to make progress on this today.
>>>>
>>>> I believe this is fixed in trunk for both 9.0.x and 8.5.x.
>>>>
>>>> Are you able to build either of those from source and test? If not, I
>>>> can provide a snapshot build for you to test with.
>>>>
>>>> Cheers,
>>>>
>>>> Mark
>>>
>>> I've built from source, re-enabled the health check, and so
>>> far so good - it's been running an hour without an error.
>>>
>>> Once this run has finished, I'll run it overnight, and let you
>>> know tomorrow morning.
>>>
>>> Many thanks for your help on this.
>>>
>>> --
>>> Richard
>>
>> Just a quick follow up - I've run our test for 8 hours, without the
>> connection closed error.
>
> Excellent. That is really good news.
>
>> Again, many thanks.
>
> No problem. Happy to help. Thanks for your assistance with this issue.
> Your test case and debug logs were invaluable. I couldn't have fixed
> this without them.
>
> Mark
>
Do you mind to share more about the root cause? I’ve followed this mail communication from the start and am curious.
Let me tell you that your endurance on all the tricky issues here is admirable!
Thank you for that!
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Connection closed error and certificateVerification="required"
Posted by Mark Thomas <ma...@apache.org>.
On 18/04/18 10:36, Richard Tearle wrote:
> On 17 April 2018 at 16:45, Richard Tearle
> <ri...@northgateps.com> wrote:
>> On 17 April 2018 at 14:54, Mark Thomas <ma...@apache.org> wrote:
>>> On 17/04/18 11:36, Mark Thomas wrote:
>>>> On 17/04/18 10:14, Richard Tearle wrote:
>>>
>>> <snip/>
>>>
>>>> Now all we need to to do is to figure out how to fix this. With the
>>>> understanding of what is (probably) going wrong, the problem can be
>>>> produced with a clean build and the certs we use for unit tests which
>>>> makes things a lot easier. I hope to make progress on this today.
>>>
>>> I believe this is fixed in trunk for both 9.0.x and 8.5.x.
>>>
>>> Are you able to build either of those from source and test? If not, I
>>> can provide a snapshot build for you to test with.
>>>
>>> Cheers,
>>>
>>> Mark
>>>
>>
>> I've built from source, re-enabled the health check, and so
>> far so good - it's been running an hour without an error.
>>
>> Once this run has finished, I'll run it overnight, and let you
>> know tomorrow morning.
>>
>> Many thanks for your help on this.
>>
>> --
>> Richard
>
> Just a quick follow up - I've run our test for 8 hours, without the
> connection closed error.
Excellent. That is really good news.
> Again, many thanks.
No problem. Happy to help. Thanks for your assistance with this issue.
Your test case and debug logs were invaluable. I couldn't have fixed
this without them.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Connection closed error and certificateVerification="required"
Posted by Richard Tearle <ri...@northgateps.com>.
On 17 April 2018 at 16:45, Richard Tearle
<ri...@northgateps.com> wrote:
> On 17 April 2018 at 14:54, Mark Thomas <ma...@apache.org> wrote:
>> On 17/04/18 11:36, Mark Thomas wrote:
>>> On 17/04/18 10:14, Richard Tearle wrote:
>>
>> <snip/>
>>
>>> Now all we need to to do is to figure out how to fix this. With the
>>> understanding of what is (probably) going wrong, the problem can be
>>> produced with a clean build and the certs we use for unit tests which
>>> makes things a lot easier. I hope to make progress on this today.
>>
>> I believe this is fixed in trunk for both 9.0.x and 8.5.x.
>>
>> Are you able to build either of those from source and test? If not, I
>> can provide a snapshot build for you to test with.
>>
>> Cheers,
>>
>> Mark
>>
>
> I've built from source, re-enabled the health check, and so
> far so good - it's been running an hour without an error.
>
> Once this run has finished, I'll run it overnight, and let you
> know tomorrow morning.
>
> Many thanks for your help on this.
>
> --
> Richard
Just a quick follow up - I've run our test for 8 hours, without the
connection closed error.
Again, many thanks.
--
Richard
--
This email is sent on behalf of Northgate Public Services (UK) Limited and
its associated companies including Rave Technologies (India) Pvt Limited
(together "Northgate Public Services") and is strictly confidential and
intended solely for the addressee(s).
If you are not the intended
recipient of this email you must: (i) not disclose, copy or distribute its
contents to any other person nor use its contents in any way or you may be
acting unlawfully; (ii) contact Northgate Public Services immediately on
+44(0)1442 768445 quoting the name of the sender and the addressee then
delete it from your system.
Northgate Public Services has taken reasonable
precautions to ensure that no viruses are contained in this email, but does
not accept any responsibility once this email has been transmitted. You
should scan attachments (if any) for viruses.
Northgate Public Services
(UK) Limited, registered in England and Wales under number 00968498 with a
registered address of Peoplebuilding 2, Peoplebuilding Estate, Maylands
Avenue, Hemel Hempstead, Hertfordshire, HP2 4NW. Rave Technologies (India)
Pvt Limited, registered in India under number 117068 with a registered
address of 2nd Floor, Ballard House, Adi Marzban Marg, Ballard Estate,
Mumbai, Maharashtra, India, 400001.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Connection closed error and certificateVerification="required"
Posted by Richard Tearle <ri...@northgateps.com>.
On 17 April 2018 at 14:54, Mark Thomas <ma...@apache.org> wrote:
> On 17/04/18 11:36, Mark Thomas wrote:
>> On 17/04/18 10:14, Richard Tearle wrote:
>
> <snip/>
>
>> Now all we need to to do is to figure out how to fix this. With the
>> understanding of what is (probably) going wrong, the problem can be
>> produced with a clean build and the certs we use for unit tests which
>> makes things a lot easier. I hope to make progress on this today.
>
> I believe this is fixed in trunk for both 9.0.x and 8.5.x.
>
> Are you able to build either of those from source and test? If not, I
> can provide a snapshot build for you to test with.
>
> Cheers,
>
> Mark
>
I've built from source, re-enabled the health check, and so
far so good - it's been running an hour without an error.
Once this run has finished, I'll run it overnight, and let you
know tomorrow morning.
Many thanks for your help on this.
--
Richard
--
This email is sent on behalf of Northgate Public Services (UK) Limited and
its associated companies including Rave Technologies (India) Pvt Limited
(together "Northgate Public Services") and is strictly confidential and
intended solely for the addressee(s).
If you are not the intended
recipient of this email you must: (i) not disclose, copy or distribute its
contents to any other person nor use its contents in any way or you may be
acting unlawfully; (ii) contact Northgate Public Services immediately on
+44(0)1442 768445 quoting the name of the sender and the addressee then
delete it from your system.
Northgate Public Services has taken reasonable
precautions to ensure that no viruses are contained in this email, but does
not accept any responsibility once this email has been transmitted. You
should scan attachments (if any) for viruses.
Northgate Public Services
(UK) Limited, registered in England and Wales under number 00968498 with a
registered address of Peoplebuilding 2, Peoplebuilding Estate, Maylands
Avenue, Hemel Hempstead, Hertfordshire, HP2 4NW. Rave Technologies (India)
Pvt Limited, registered in India under number 117068 with a registered
address of 2nd Floor, Ballard House, Adi Marzban Marg, Ballard Estate,
Mumbai, Maharashtra, India, 400001.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Connection closed error and certificateVerification="required"
Posted by Mark Thomas <ma...@apache.org>.
On 17/04/18 11:36, Mark Thomas wrote:
> On 17/04/18 10:14, Richard Tearle wrote:
<snip/>
>> I've also disabled the health check on ESB container, and my tests
>> ran through for an hour, without a connection closed error.
>
> That is good news. That is a strong indicator that we are on the right
> track. It also explains why I could not reproduce the problem with your
> test case. And finally, it is another example of the debug logging added
> to the I/O layer proving worth while.
>
> Now all we need to to do is to figure out how to fix this. With the
> understanding of what is (probably) going wrong, the problem can be
> produced with a clean build and the certs we use for unit tests which
> makes things a lot easier. I hope to make progress on this today.
I believe this is fixed in trunk for both 9.0.x and 8.5.x.
Are you able to build either of those from source and test? If not, I
can provide a snapshot build for you to test with.
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Connection closed error and certificateVerification="required"
Posted by Mark Thomas <ma...@apache.org>.
On 17/04/18 10:14, Richard Tearle wrote:
> On 16 April 2018 at 22:04, Mark Thomas <ma...@apache.org> wrote:
<snip/>
>> I've started to look at them. I don't have any firm conclusions yet. I
>> have noticed that the problem occurs after a connection is made to the
>> service from localhost rather than the remote IP that is making the
>> other requests. The localhost client does not present a certificate.
>>
>> My working theory (so chances are it is completely wrong) is that the
>> missing certificate in the request from localhost puts the OpenSSL
>> engine into an error state that is not correctly handled by Tomcat
>> causing the subsequent request to fail.
>>
>> I've also noticed that the debug level log message consistently report 0
>> bytes being read which looks wrong but is probably a separate (minor) issue.
The above message are correct but misleading. I'm planning to add
additional debug logging which should clarify things.
<snip/>
> Ah that rings a bell.
>
> Our containers have a simple health check, simply does
>
> curl --connect-timeout 5 --max-time 20 -k -s -S --stderr -\
> https://localhost:${TOMCATS_PORT}/ |\
> grep -q "NSS: client certificate not found" || exit 1
>
> just to make sure the ESB is responding, with something we expect.
> These are set to run at an interval of every 2m30s. The full parameters
> in the docker-compose[1] file are:
>
> healthcheck:
> test: ["CMD", "/usr/local/bin/healthcheck.sh"]
> interval: 2m30s
> timeout: 10s
> retries: 3
> start_period: 20s
>
> I've also disabled the health check on ESB container, and my tests
> ran through for an hour, without a connection closed error.
That is good news. That is a strong indicator that we are on the right
track. It also explains why I could not reproduce the problem with your
test case. And finally, it is another example of the debug logging added
to the I/O layer proving worth while.
Now all we need to to do is to figure out how to fix this. With the
understanding of what is (probably) going wrong, the problem can be
produced with a clean build and the certs we use for unit tests which
makes things a lot easier. I hope to make progress on this today.
Mark
>
> [1] https://docs.docker.com/compose/compose-file/#healthcheck
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Connection closed error and certificateVerification="required"
Posted by Richard Tearle <ri...@northgateps.com>.
On 16 April 2018 at 22:04, Mark Thomas <ma...@apache.org> wrote:
> On 11/04/18 09:22, Richard Tearle wrote:
>
> <snip/>
>
>> I've built tomcat from source using the link you provided, and rebuilt the
>> containers with this tomcat, and can still reproduce the issue. I've uploaded
>> the logs (30s before the connection closed error), to dropbox:
>>
>> https://www.dropbox.com/s/qe50jbd196krtyo/logs-10-04-17.zip?dl=0
>
> Thanks for these.
>
> I've started to look at them. I don't have any firm conclusions yet. I
> have noticed that the problem occurs after a connection is made to the
> service from localhost rather than the remote IP that is making the
> other requests. The localhost client does not present a certificate.
>
> My working theory (so chances are it is completely wrong) is that the
> missing certificate in the request from localhost puts the OpenSSL
> engine into an error state that is not correctly handled by Tomcat
> causing the subsequent request to fail.
>
> I've also noticed that the debug level log message consistently report 0
> bytes being read which looks wrong but is probably a separate (minor) issue.
>
> Investigations continue.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Ah that rings a bell.
Our containers have a simple health check, simply does
curl --connect-timeout 5 --max-time 20 -k -s -S --stderr -\
https://localhost:${TOMCATS_PORT}/ |\
grep -q "NSS: client certificate not found" || exit 1
just to make sure the ESB is responding, with something we expect.
These are set to run at an interval of every 2m30s. The full parameters
in the docker-compose[1] file are:
healthcheck:
test: ["CMD", "/usr/local/bin/healthcheck.sh"]
interval: 2m30s
timeout: 10s
retries: 3
start_period: 20s
I've also disabled the health check on ESB container, and my tests
ran through for an hour, without a connection closed error.
[1] https://docs.docker.com/compose/compose-file/#healthcheck
--
Richard
--
This email is sent on behalf of Northgate Public Services (UK) Limited and
its associated companies including Rave Technologies (India) Pvt Limited
(together "Northgate Public Services") and is strictly confidential and
intended solely for the addressee(s).
If you are not the intended
recipient of this email you must: (i) not disclose, copy or distribute its
contents to any other person nor use its contents in any way or you may be
acting unlawfully; (ii) contact Northgate Public Services immediately on
+44(0)1442 768445 quoting the name of the sender and the addressee then
delete it from your system.
Northgate Public Services has taken reasonable
precautions to ensure that no viruses are contained in this email, but does
not accept any responsibility once this email has been transmitted. You
should scan attachments (if any) for viruses.
Northgate Public Services
(UK) Limited, registered in England and Wales under number 00968498 with a
registered address of Peoplebuilding 2, Peoplebuilding Estate, Maylands
Avenue, Hemel Hempstead, Hertfordshire, HP2 4NW. Rave Technologies (India)
Pvt Limited, registered in India under number 117068 with a registered
address of 2nd Floor, Ballard House, Adi Marzban Marg, Ballard Estate,
Mumbai, Maharashtra, India, 400001.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Connection closed error and certificateVerification="required"
Posted by Mark Thomas <ma...@apache.org>.
On 11/04/18 09:22, Richard Tearle wrote:
<snip/>
> I've built tomcat from source using the link you provided, and rebuilt the
> containers with this tomcat, and can still reproduce the issue. I've uploaded
> the logs (30s before the connection closed error), to dropbox:
>
> https://www.dropbox.com/s/qe50jbd196krtyo/logs-10-04-17.zip?dl=0
Thanks for these.
I've started to look at them. I don't have any firm conclusions yet. I
have noticed that the problem occurs after a connection is made to the
service from localhost rather than the remote IP that is making the
other requests. The localhost client does not present a certificate.
My working theory (so chances are it is completely wrong) is that the
missing certificate in the request from localhost puts the OpenSSL
engine into an error state that is not correctly handled by Tomcat
causing the subsequent request to fail.
I've also noticed that the debug level log message consistently report 0
bytes being read which looks wrong but is probably a separate (minor) issue.
Investigations continue.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Connection closed error and certificateVerification="required"
Posted by Richard Tearle <ri...@northgateps.com>.
On 5 April 2018 at 08:35, Richard Tearle <ri...@northgateps.com> wrote:
>
> On 4 April 2018 at 17:58, Mark Thomas <ma...@apache.org> wrote:
> > On 26/03/18 08:25, Richard Tearle wrote:
> >
> > <snip/>
> >
> > Thanks. I've got the test application and UI running but I haven't yet
> > reproduced the problem. What parameters are you calling run-test.sh with?
>
> This usually get's a failure within 10 minutes of running:
>
> ./run-test.sh 28800 5000 5000 0 0 true
>
> (I've just tried it and it failed after 4m 23s - from the previous rounds
> of testing, it failed at around the 4m 30s mark 7 times out of 10)
>
> > I'll continue to try and reproduce the issue but I think it makes sense
> > to try and generate some debug data on your system as you can reproduce it.
> >
>
> I'll get onto this, but it might not be until next week.
>
> Thanks
>
> Richard.
I've built tomcat from source using the link you provided, and rebuilt the
containers with this tomcat, and can still reproduce the issue. I've uploaded
the logs (30s before the connection closed error), to dropbox:
https://www.dropbox.com/s/qe50jbd196krtyo/logs-10-04-17.zip?dl=0
Regards
--
Richard
--
This email is sent on behalf of Northgate Public Services (UK) Limited and
its associated companies including Rave Technologies (India) Pvt Limited
(together "Northgate Public Services") and is strictly confidential and
intended solely for the addressee(s).
If you are not the intended
recipient of this email you must: (i) not disclose, copy or distribute its
contents to any other person nor use its contents in any way or you may be
acting unlawfully; (ii) contact Northgate Public Services immediately on
+44(0)1442 768445 quoting the name of the sender and the addressee then
delete it from your system.
Northgate Public Services has taken reasonable
precautions to ensure that no viruses are contained in this email, but does
not accept any responsibility once this email has been transmitted. You
should scan attachments (if any) for viruses.
Northgate Public Services
(UK) Limited, registered in England and Wales under number 00968498 with a
registered address of Peoplebuilding 2, Peoplebuilding Estate, Maylands
Avenue, Hemel Hempstead, Hertfordshire, HP2 4NW. Rave Technologies (India)
Pvt Limited, registered in India under number 117068 with a registered
address of 2nd Floor, Ballard House, Adi Marzban Marg, Ballard Estate,
Mumbai, Maharashtra, India, 400001.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Connection closed error and certificateVerification="required"
Posted by Richard Tearle <ri...@northgateps.com>.
On 4 April 2018 at 17:58, Mark Thomas <ma...@apache.org> wrote:
> On 26/03/18 08:25, Richard Tearle wrote:
>
> <snip/>
>
> Thanks. I've got the test application and UI running but I haven't yet
> reproduced the problem. What parameters are you calling run-test.sh with?
This usually get's a failure within 10 minutes of running:
./run-test.sh 28800 5000 5000 0 0 true
(I've just tried it and it failed after 4m 23s - from the previous rounds
of testing, it failed at around the 4m 30s mark 7 times out of 10)
> I'll continue to try and reproduce the issue but I think it makes sense
> to try and generate some debug data on your system as you can reproduce it.
>
I'll get onto this, but it might not be until next week.
Thanks
Richard.
--
This email is sent on behalf of Northgate Public Services (UK) Limited and
its associated companies including Rave Technologies (India) Pvt Limited
(together "Northgate Public Services") and is strictly confidential and
intended solely for the addressee(s).
If you are not the intended
recipient of this email you must: (i) not disclose, copy or distribute its
contents to any other person nor use its contents in any way or you may be
acting unlawfully; (ii) contact Northgate Public Services immediately on
+44(0)1442 768445 quoting the name of the sender and the addressee then
delete it from your system.
Northgate Public Services has taken reasonable
precautions to ensure that no viruses are contained in this email, but does
not accept any responsibility once this email has been transmitted. You
should scan attachments (if any) for viruses.
Northgate Public Services
(UK) Limited, registered in England and Wales under number 00968498 with a
registered address of Peoplebuilding 2, Peoplebuilding Estate, Maylands
Avenue, Hemel Hempstead, Hertfordshire, HP2 4NW. Rave Technologies (India)
Pvt Limited, registered in India under number 117068 with a registered
address of 2nd Floor, Ballard House, Adi Marzban Marg, Ballard Estate,
Mumbai, Maharashtra, India, 400001.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org