You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Violeta Georgieva <vi...@apache.org> on 2019/07/24 13:56:53 UTC
[VOTE] Release Apache Tomcat 7.0.96
The proposed Apache Tomcat 7.0.96 release is now available for voting.
For full details, see the changelog:
https://ci.apache.org/projects/tomcat/tomcat7/docs/changelog.html
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.96/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1224/
The git tag is:
https://github.com/apache/tomcat/tree/7.0.96
5277b175db2e575022672856797240976ad23bcf
The proposed 7.0.96 release is:
[ ] Broken - do not release
[ ] Stable - go ahead and release as 7.0.96 Stable
Regards,
Violeta
Re: [RESULT][VOTE] Release Apache Tomcat 7.0.96
Posted by Violeta Georgieva <vi...@apache.org>.
Hi,
На ср, 24.07.2019 г. в 16:56 ч. Violeta Georgieva <vi...@apache.org>
написа:
>
> The proposed Apache Tomcat 7.0.96 release is now available for voting.
>
> For full details, see the changelog:
> https://ci.apache.org/projects/tomcat/tomcat7/docs/changelog.html
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.96/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1224/
> The git tag is:
> https://github.com/apache/tomcat/tree/7.0.96
> 5277b175db2e575022672856797240976ad23bcf
>
> The proposed 7.0.96 release is:
> [ ] Broken - do not release
> [ ] Stable - go ahead and release as 7.0.96 Stable
+1 (binding): markt, violetagg, fschumacher
No other voters were cast.
The vote has passed.
I'll do the release shortly and announce it once the mirrors catch up.
Regards,
Violeta
Re: [VOTE] Release Apache Tomcat 7.0.96
Posted by Felix Schumacher <fe...@internetallee.de>.
Am 24. Juli 2019 15:56:53 MESZ schrieb Violeta Georgieva <vi...@apache.org>:
>The proposed Apache Tomcat 7.0.96 release is now available for voting.
>
>For full details, see the changelog:
>https://ci.apache.org/projects/tomcat/tomcat7/docs/changelog.html
>
>It can be obtained from:
>https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.96/
>The Maven staging repo is:
>https://repository.apache.org/content/repositories/orgapachetomcat-1224/
>The git tag is:
>https://github.com/apache/tomcat/tree/7.0.96
>5277b175db2e575022672856797240976ad23bcf
>
>The proposed 7.0.96 release is:
>[ ] Broken - do not release
>[x] Stable - go ahead and release as 7.0.96 Stable
Regards
Felix
>
>Regards,
>Violeta
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.96
Posted by Felix Schumacher <fe...@internetallee.de>.
Am 25. Juli 2019 17:00:06 MESZ schrieb Rainer Jung <ra...@kippdata.de>:
>Hi Felix,
>
>could it be you have overwritten objenesis.loc in some
>build.properties?
Could be. I will have a look at my docker file.
Stupid me has looked at the git sources and hasn't thought about my old me copying stuff into the extracted dir :)
Felix
>
>Commit 9e32afaf34e on 2019-07-05 for TC 7 contains:
>
>-objenesis.loc=https://bintray.com/easymock/distributions/download_file?file_path=objenesis-${objenesis.version}-bin.zip
>+objenesis.loc=${base-maven.loc}/org/objenesis/objenesis/${objenesis.version}/objenesis-${objenesis.version}.jar
>
>in build.properties.default (plus the checksum change), but your ant
>task still downloads objenesis-1.2-bin.zip instead of
>objenesis-1.2.jar.
>
>It works here.
>
>Regards,
>
>Rainer
>
>Am 25.07.2019 um 15:48 schrieb Felix Schumacher:
>> While building with 'ant test' I currently get:
>>
>> ,,,
>>
>> downloadfile:
>> [get] Getting:
>>
>https://bintray.com/easymock/distributions/download_file?file_path=objenesis-1.2-bin.zip
>> [get] To: /root/tomcat-build-libs/download-526630409.tmp
>> [get]
>>
>https://bintray.com/easymock/distributions/download_file?file_path=objenesis-1.2-bin.zip
>> moved to
>https://dl.bintray.com/easymock/distributions/objenesis-1.2-bin.zip
>> [get]
>> https://dl.bintray.com/easymock/distributions/objenesis-1.2-bin.zip
>> moved to
>>
>https://d29vzk4ow07wi7.cloudfront.net/2359e04aca6f4f171f92ff77489d1669043dd536?response-content-disposition=attachment%3Bfilename%3D%22objenesis-1.2-bin.zip%22&Policy=eyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6Imh0dHAqOi8vZDI5dnprNG93MDd3aTcuY2xvdWRmcm9udC5uZXQvMjM1OWUwNGFjYTZmNGYxNzFmOTJmZjc3NDg5ZDE2NjkwNDNkZDUzNj9yZXNwb25zZS1jb250ZW50LWRpc3Bvc2l0aW9uPWF0dGFjaG1lbnQlM0JmaWxlbmFtZSUzRCUyMm9iamVuZXNpcy0xLjItYmluLnppcCUyMiIsIkNvbmRpdGlvbiI6eyJEYXRlTGVzc1RoYW4iOnsiQVdTOkVwb2NoVGltZSI6MTU2NDA2Mjg5NX0sIklwQWRkcmVzcyI6eyJBV1M6U291cmNlSXAiOiIwLjAuMC4wLzAifX19XX0_&Signature=IGW4RrDny71UmfjwU2rT~hyMNrU8SBqOQV0wavwC00upzv9ATLZlRGec7c1~-1E~Uh5mE56h1BTmXhdcw8Fi7YTVvTIoP11esCqirEX1NO9qyp7tmur7Y5ihjXkEficCCWKzpXbklCx4ZRiCJ8CpAkVyg9rfExZyCLeAJNSRd8LhWq3j2ecwMzhR9Fb-2U3-ffi5DAJFN7YenKf5-bbVF1yE8pyF3bBo47SlLZl7ocslXm57nF41-oV2c1yrF8XchSG6WlH3DTVHqmRVqAGg4lfMJpPiuOROollmQ6cUiSvKxQ0O~l6FnByHf1D804xMeYha4UahL9clmAbP~54vWA__&Key-Pair-Id=APKAIFKFWOMXM2UMTSFA
>>
>> BUILD FAILED
>> /usr/local/src/tomcat-native/build.xml:2857: The following error
>> occurred while executing this line:
>> /usr/local/src/tomcat-native/build.xml:3138: The following error
>> occurred while executing this line:
>> /usr/local/src/tomcat-native/build.xml:3023: Checksum check failure
>for
>> objenesis-1.2.jar (/root/tomcat-build-libs/download-526630409.tmp).
>> Algorithm: MD5|SHA-1
>> Expected value:
>>
>bee117291d50b41b8e8cf0ac5435df1d|bfcb0539a071a4c5a30690388903ac48c0667f2a
>> Actual values:
>> SHA-512:
>>
>ede5873de8576f2b330407b17d73bb1fdceb19d8b3b674f9e0c5c7c0461f4f3e13be099bf3503328e6d4643874b7187bb8e0db03f55bdafc99449acbc9896a2b
>> SHA-256:
>c732f0bc16a5c6e700652d36533f286a84e5fce9932e1da65e16ab0897d6480f
>> SHA-1: 2359e04aca6f4f171f92ff77489d1669043dd536
>> MD5: c94eeba0f868c80c50eb0202499479ab
>>
>> Regards
>>
>> Felix
>>
>> Am 24.07.19 um 15:56 schrieb Violeta Georgieva:
>>> The proposed Apache Tomcat 7.0.96 release is now available for
>voting.
>>>
>>> For full details, see the changelog:
>>> https://ci.apache.org/projects/tomcat/tomcat7/docs/changelog.html
>>>
>>> It can be obtained from:
>>> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.96/
>>> The Maven staging repo is:
>>>
>https://repository.apache.org/content/repositories/orgapachetomcat-1224/
>>> The git tag is:
>>> https://github.com/apache/tomcat/tree/7.0.96
>>> 5277b175db2e575022672856797240976ad23bcf
>>>
>>> The proposed 7.0.96 release is:
>>> [ ] Broken - do not release
>>> [ ] Stable - go ahead and release as 7.0.96 Stable
>>>
>>> Regards,
>>> Violeta
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: dev-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.96
Posted by Rainer Jung <ra...@kippdata.de>.
I just saw, you can find the source of the property by running in your
TC 7 directory:
ant -debug echoproperties | egrep -e 'Loading|objenesis'
For my checkout it shows:
[property] Loading /path/to/my/home/build.properties
[property] Loading /path/to/my/tomcat/7.0.96/checkout/build.properties
[property] Loading
/path/to/my/tomcat/7.0.96/checkout/build.properties.default
Setting project property: objenesis.home ->
/path/to/my/tomcat/7.0.96/deps/objenesis-1.2
Setting project property: objenesis.checksum.algorithm -> MD5|SHA-1
Setting project property: objenesis.version -> 1.2
Setting project property: objenesis.checksum.enabled -> true
Setting project property: objenesis.loc ->
https://repo.maven.apache.org/maven2/org/objenesis/objenesis/1.2/objenesis-1.2.jar
...
So the objenesis.loc property was set after reading
/path/to/my/tomcat/7.0.96/checkout/build.properties.default (and to the
correct value).
This should show you, where your wring value was read from.
Regards,
Rainer
Am 25.07.2019 um 17:00 schrieb Rainer Jung:
> Hi Felix,
>
> could it be you have overwritten objenesis.loc in some build.properties?
>
> Commit 9e32afaf34e on 2019-07-05 for TC 7 contains:
>
> -objenesis.loc=https://bintray.com/easymock/distributions/download_file?file_path=objenesis-${objenesis.version}-bin.zip
>
> +objenesis.loc=${base-maven.loc}/org/objenesis/objenesis/${objenesis.version}/objenesis-${objenesis.version}.jar
>
>
> in build.properties.default (plus the checksum change), but your ant
> task still downloads objenesis-1.2-bin.zip instead of objenesis-1.2.jar.
>
> It works here.
>
> Regards,
>
> Rainer
>
> Am 25.07.2019 um 15:48 schrieb Felix Schumacher:
>> While building with 'ant test' I currently get:
>>
>> ,,,
>>
>> downloadfile:
>> [get] Getting:
>> https://bintray.com/easymock/distributions/download_file?file_path=objenesis-1.2-bin.zip
>>
>> [get] To: /root/tomcat-build-libs/download-526630409.tmp
>> [get]
>> https://bintray.com/easymock/distributions/download_file?file_path=objenesis-1.2-bin.zip
>>
>> moved to
>> https://dl.bintray.com/easymock/distributions/objenesis-1.2-bin.zip
>> [get]
>> https://dl.bintray.com/easymock/distributions/objenesis-1.2-bin.zip
>> moved to
>> https://d29vzk4ow07wi7.cloudfront.net/2359e04aca6f4f171f92ff77489d1669043dd536?response-content-disposition=attachment%3Bfilename%3D%22objenesis-1.2-bin.zip%22&Policy=eyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6Imh0dHAqOi8vZDI5dnprNG93MDd3aTcuY2xvdWRmcm9udC5uZXQvMjM1OWUwNGFjYTZmNGYxNzFmOTJmZjc3NDg5ZDE2NjkwNDNkZDUzNj9yZXNwb25zZS1jb250ZW50LWRpc3Bvc2l0aW9uPWF0dGFjaG1lbnQlM0JmaWxlbmFtZSUzRCUyMm9iamVuZXNpcy0xLjItYmluLnppcCUyMiIsIkNvbmRpdGlvbiI6eyJEYXRlTGVzc1RoYW4iOnsiQVdTOkVwb2NoVGltZSI6MTU2NDA2Mjg5NX0sIklwQWRkcmVzcyI6eyJBV1M6U291cmNlSXAiOiIwLjAuMC4wLzAifX19XX0_&Signature=IGW4RrDny71UmfjwU2rT~hyMNrU8SBqOQV0wavwC00upzv9ATLZlRGec7c1~-1E~Uh5mE56h1BTmXhdcw8Fi7YTVvTIoP11esCqirEX1NO9qyp7tmur7Y5ihjXkEficCCWKzpXbklCx4ZRiCJ8CpAkVyg9rfExZyCLeAJNSRd8LhWq3j2ecwMzhR9Fb-2U3-ffi5DAJFN7YenKf5-bbVF1yE8pyF3bBo47SlLZl7ocslXm57nF41-oV2c1yrF8XchSG6WlH3DTVHqmRVqAGg4lfMJpPiuOROollmQ6cUiSvKxQ0O~l6FnByHf1D804xMeYha4UahL9clmAbP~54vWA__&Key-Pair-Id=APKAIFKFWOMXM2UMTSFA
>>
>>
>> BUILD FAILED
>> /usr/local/src/tomcat-native/build.xml:2857: The following error
>> occurred while executing this line:
>> /usr/local/src/tomcat-native/build.xml:3138: The following error
>> occurred while executing this line:
>> /usr/local/src/tomcat-native/build.xml:3023: Checksum check failure for
>> objenesis-1.2.jar (/root/tomcat-build-libs/download-526630409.tmp).
>> Algorithm: MD5|SHA-1
>> Expected value:
>> bee117291d50b41b8e8cf0ac5435df1d|bfcb0539a071a4c5a30690388903ac48c0667f2a
>> Actual values:
>> SHA-512:
>> ede5873de8576f2b330407b17d73bb1fdceb19d8b3b674f9e0c5c7c0461f4f3e13be099bf3503328e6d4643874b7187bb8e0db03f55bdafc99449acbc9896a2b
>>
>> SHA-256:
>> c732f0bc16a5c6e700652d36533f286a84e5fce9932e1da65e16ab0897d6480f
>> SHA-1: 2359e04aca6f4f171f92ff77489d1669043dd536
>> MD5: c94eeba0f868c80c50eb0202499479ab
>>
>> Regards
>>
>> Felix
>>
>> Am 24.07.19 um 15:56 schrieb Violeta Georgieva:
>>> The proposed Apache Tomcat 7.0.96 release is now available for voting.
>>>
>>> For full details, see the changelog:
>>> https://ci.apache.org/projects/tomcat/tomcat7/docs/changelog.html
>>>
>>> It can be obtained from:
>>> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.96/
>>> The Maven staging repo is:
>>> https://repository.apache.org/content/repositories/orgapachetomcat-1224/
>>> The git tag is:
>>> https://github.com/apache/tomcat/tree/7.0.96
>>> 5277b175db2e575022672856797240976ad23bcf
>>>
>>> The proposed 7.0.96 release is:
>>> [ ] Broken - do not release
>>> [ ] Stable - go ahead and release as 7.0.96 Stable
>>>
>>> Regards,
>>> Violeta
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.96
Posted by Rainer Jung <ra...@kippdata.de>.
Hi Felix,
could it be you have overwritten objenesis.loc in some build.properties?
Commit 9e32afaf34e on 2019-07-05 for TC 7 contains:
-objenesis.loc=https://bintray.com/easymock/distributions/download_file?file_path=objenesis-${objenesis.version}-bin.zip
+objenesis.loc=${base-maven.loc}/org/objenesis/objenesis/${objenesis.version}/objenesis-${objenesis.version}.jar
in build.properties.default (plus the checksum change), but your ant
task still downloads objenesis-1.2-bin.zip instead of objenesis-1.2.jar.
It works here.
Regards,
Rainer
Am 25.07.2019 um 15:48 schrieb Felix Schumacher:
> While building with 'ant test' I currently get:
>
> ,,,
>
> downloadfile:
> [get] Getting:
> https://bintray.com/easymock/distributions/download_file?file_path=objenesis-1.2-bin.zip
> [get] To: /root/tomcat-build-libs/download-526630409.tmp
> [get]
> https://bintray.com/easymock/distributions/download_file?file_path=objenesis-1.2-bin.zip
> moved to https://dl.bintray.com/easymock/distributions/objenesis-1.2-bin.zip
> [get]
> https://dl.bintray.com/easymock/distributions/objenesis-1.2-bin.zip
> moved to
> https://d29vzk4ow07wi7.cloudfront.net/2359e04aca6f4f171f92ff77489d1669043dd536?response-content-disposition=attachment%3Bfilename%3D%22objenesis-1.2-bin.zip%22&Policy=eyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6Imh0dHAqOi8vZDI5dnprNG93MDd3aTcuY2xvdWRmcm9udC5uZXQvMjM1OWUwNGFjYTZmNGYxNzFmOTJmZjc3NDg5ZDE2NjkwNDNkZDUzNj9yZXNwb25zZS1jb250ZW50LWRpc3Bvc2l0aW9uPWF0dGFjaG1lbnQlM0JmaWxlbmFtZSUzRCUyMm9iamVuZXNpcy0xLjItYmluLnppcCUyMiIsIkNvbmRpdGlvbiI6eyJEYXRlTGVzc1RoYW4iOnsiQVdTOkVwb2NoVGltZSI6MTU2NDA2Mjg5NX0sIklwQWRkcmVzcyI6eyJBV1M6U291cmNlSXAiOiIwLjAuMC4wLzAifX19XX0_&Signature=IGW4RrDny71UmfjwU2rT~hyMNrU8SBqOQV0wavwC00upzv9ATLZlRGec7c1~-1E~Uh5mE56h1BTmXhdcw8Fi7YTVvTIoP11esCqirEX1NO9qyp7tmur7Y5ihjXkEficCCWKzpXbklCx4ZRiCJ8CpAkVyg9rfExZyCLeAJNSRd8LhWq3j2ecwMzhR9Fb-2U3-ffi5DAJFN7YenKf5-bbVF1yE8pyF3bBo47SlLZl7ocslXm57nF41-oV2c1yrF8XchSG6WlH3DTVHqmRVqAGg4lfMJpPiuOROollmQ6cUiSvKxQ0O~l6FnByHf1D804xMeYha4UahL9clmAbP~54vWA__&Key-Pair-Id=APKAIFKFWOMXM2UMTSFA
>
> BUILD FAILED
> /usr/local/src/tomcat-native/build.xml:2857: The following error
> occurred while executing this line:
> /usr/local/src/tomcat-native/build.xml:3138: The following error
> occurred while executing this line:
> /usr/local/src/tomcat-native/build.xml:3023: Checksum check failure for
> objenesis-1.2.jar (/root/tomcat-build-libs/download-526630409.tmp).
> Algorithm: MD5|SHA-1
> Expected value:
> bee117291d50b41b8e8cf0ac5435df1d|bfcb0539a071a4c5a30690388903ac48c0667f2a
> Actual values:
> SHA-512:
> ede5873de8576f2b330407b17d73bb1fdceb19d8b3b674f9e0c5c7c0461f4f3e13be099bf3503328e6d4643874b7187bb8e0db03f55bdafc99449acbc9896a2b
> SHA-256: c732f0bc16a5c6e700652d36533f286a84e5fce9932e1da65e16ab0897d6480f
> SHA-1: 2359e04aca6f4f171f92ff77489d1669043dd536
> MD5: c94eeba0f868c80c50eb0202499479ab
>
> Regards
>
> Felix
>
> Am 24.07.19 um 15:56 schrieb Violeta Georgieva:
>> The proposed Apache Tomcat 7.0.96 release is now available for voting.
>>
>> For full details, see the changelog:
>> https://ci.apache.org/projects/tomcat/tomcat7/docs/changelog.html
>>
>> It can be obtained from:
>> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.96/
>> The Maven staging repo is:
>> https://repository.apache.org/content/repositories/orgapachetomcat-1224/
>> The git tag is:
>> https://github.com/apache/tomcat/tree/7.0.96
>> 5277b175db2e575022672856797240976ad23bcf
>>
>> The proposed 7.0.96 release is:
>> [ ] Broken - do not release
>> [ ] Stable - go ahead and release as 7.0.96 Stable
>>
>> Regards,
>> Violeta
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.96
Posted by Felix Schumacher <fe...@internetallee.de>.
While building with 'ant test' I currently get:
,,,
downloadfile:
[get] Getting:
https://bintray.com/easymock/distributions/download_file?file_path=objenesis-1.2-bin.zip
[get] To: /root/tomcat-build-libs/download-526630409.tmp
[get]
https://bintray.com/easymock/distributions/download_file?file_path=objenesis-1.2-bin.zip
moved to https://dl.bintray.com/easymock/distributions/objenesis-1.2-bin.zip
[get]
https://dl.bintray.com/easymock/distributions/objenesis-1.2-bin.zip
moved to
https://d29vzk4ow07wi7.cloudfront.net/2359e04aca6f4f171f92ff77489d1669043dd536?response-content-disposition=attachment%3Bfilename%3D%22objenesis-1.2-bin.zip%22&Policy=eyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6Imh0dHAqOi8vZDI5dnprNG93MDd3aTcuY2xvdWRmcm9udC5uZXQvMjM1OWUwNGFjYTZmNGYxNzFmOTJmZjc3NDg5ZDE2NjkwNDNkZDUzNj9yZXNwb25zZS1jb250ZW50LWRpc3Bvc2l0aW9uPWF0dGFjaG1lbnQlM0JmaWxlbmFtZSUzRCUyMm9iamVuZXNpcy0xLjItYmluLnppcCUyMiIsIkNvbmRpdGlvbiI6eyJEYXRlTGVzc1RoYW4iOnsiQVdTOkVwb2NoVGltZSI6MTU2NDA2Mjg5NX0sIklwQWRkcmVzcyI6eyJBV1M6U291cmNlSXAiOiIwLjAuMC4wLzAifX19XX0_&Signature=IGW4RrDny71UmfjwU2rT~hyMNrU8SBqOQV0wavwC00upzv9ATLZlRGec7c1~-1E~Uh5mE56h1BTmXhdcw8Fi7YTVvTIoP11esCqirEX1NO9qyp7tmur7Y5ihjXkEficCCWKzpXbklCx4ZRiCJ8CpAkVyg9rfExZyCLeAJNSRd8LhWq3j2ecwMzhR9Fb-2U3-ffi5DAJFN7YenKf5-bbVF1yE8pyF3bBo47SlLZl7ocslXm57nF41-oV2c1yrF8XchSG6WlH3DTVHqmRVqAGg4lfMJpPiuOROollmQ6cUiSvKxQ0O~l6FnByHf1D804xMeYha4UahL9clmAbP~54vWA__&Key-Pair-Id=APKAIFKFWOMXM2UMTSFA
BUILD FAILED
/usr/local/src/tomcat-native/build.xml:2857: The following error
occurred while executing this line:
/usr/local/src/tomcat-native/build.xml:3138: The following error
occurred while executing this line:
/usr/local/src/tomcat-native/build.xml:3023: Checksum check failure for
objenesis-1.2.jar (/root/tomcat-build-libs/download-526630409.tmp).
Algorithm: MD5|SHA-1
Expected value:
bee117291d50b41b8e8cf0ac5435df1d|bfcb0539a071a4c5a30690388903ac48c0667f2a
Actual values:
SHA-512:
ede5873de8576f2b330407b17d73bb1fdceb19d8b3b674f9e0c5c7c0461f4f3e13be099bf3503328e6d4643874b7187bb8e0db03f55bdafc99449acbc9896a2b
SHA-256: c732f0bc16a5c6e700652d36533f286a84e5fce9932e1da65e16ab0897d6480f
SHA-1: 2359e04aca6f4f171f92ff77489d1669043dd536
MD5: c94eeba0f868c80c50eb0202499479ab
Regards
Felix
Am 24.07.19 um 15:56 schrieb Violeta Georgieva:
> The proposed Apache Tomcat 7.0.96 release is now available for voting.
>
> For full details, see the changelog:
> https://ci.apache.org/projects/tomcat/tomcat7/docs/changelog.html
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.96/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1224/
> The git tag is:
> https://github.com/apache/tomcat/tree/7.0.96
> 5277b175db2e575022672856797240976ad23bcf
>
> The proposed 7.0.96 release is:
> [ ] Broken - do not release
> [ ] Stable - go ahead and release as 7.0.96 Stable
>
> Regards,
> Violeta
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.96
Posted by Violeta Georgieva <vi...@apache.org>.
На ср, 24.07.2019 г. в 16:56 ч. Violeta Georgieva <vi...@apache.org>
написа:
>
> The proposed Apache Tomcat 7.0.96 release is now available for voting.
>
> For full details, see the changelog:
> https://ci.apache.org/projects/tomcat/tomcat7/docs/changelog.html
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.96/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1224/
> The git tag is:
> https://github.com/apache/tomcat/tree/7.0.96
> 5277b175db2e575022672856797240976ad23bcf
>
> The proposed 7.0.96 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 7.0.96 Stable
Regards,
Violeta
>
Re: [VOTE] Release Apache Tomcat 7.0.96
Posted by Violeta Georgieva <vi...@apache.org>.
Hi,
На ср, 24.07.2019 г. в 16:56 ч. Violeta Georgieva <vi...@apache.org>
написа:
>
> The proposed Apache Tomcat 7.0.96 release is now available for voting.
>
> For full details, see the changelog:
> https://ci.apache.org/projects/tomcat/tomcat7/docs/changelog.html
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.96/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1224/
> The git tag is:
> https://github.com/apache/tomcat/tree/7.0.96
> 5277b175db2e575022672856797240976ad23bcf
>
> The proposed 7.0.96 release is:
> [ ] Broken - do not release
> [ ] Stable - go ahead and release as 7.0.96 Stable
We still need at least one more vote here.
Thanks in advance,
Violeta
>
Re: [VOTE] Release Apache Tomcat 7.0.96
Posted by Mark Thomas <ma...@apache.org>.
On 24/07/2019 14:56, Violeta Georgieva wrote:
> The proposed Apache Tomcat 7.0.96 release is now available for voting.
>
> For full details, see the changelog:
> https://ci.apache.org/projects/tomcat/tomcat7/docs/changelog.html
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.96/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1224/
> The git tag is:
> https://github.com/apache/tomcat/tree/7.0.96
> 5277b175db2e575022672856797240976ad23bcf
>
> The proposed 7.0.96 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 7.0.96 Stable
Builds with Java 6 (with a bit of 7)
Starts cleanly under a security manager
Unit tests pass on Linux
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.96
Posted by Mark Thomas <ma...@apache.org>.
On 29/07/2019 09:57, Violeta Georgieva wrote:
> На сб, 27.07.2019 г. в 1:06 ч. Rainer Jung <rainer.jung@kippdata.de
<snip/>
>> The test seems to set a socket timeout to -1, which is no longer allowed
>> by the following change:
>>
>>
> https://github.com/unofficial-openjdk/openjdk/commit/3a77350f194df226cb6d618589a59d36fae9dc9c
>>
>> in JDK 13+.
>>
>> The magic value -1 for timeouts are mor efrequent in our code, but I
>> don't know which of these might end up in a setSoTimeout() call.
>
> I don't think this is a showstopper for Tomcat 7 and I'm thinking about
> promoting this release candidate.
+1
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.96
Posted by Violeta Georgieva <vi...@apache.org>.
На сб, 27.07.2019 г. в 1:06 ч. Rainer Jung <ra...@kippdata.de> написа:
>
>
>
> Am 26.07.2019 um 22:57 schrieb Rainer Jung:
> > Am 24.07.2019 um 15:56 schrieb Violeta Georgieva:
> >> The proposed Apache Tomcat 7.0.96 release is now available for voting.
> >>
> >> For full details, see the changelog:
> >> https://ci.apache.org/projects/tomcat/tomcat7/docs/changelog.html
> >>
> >> It can be obtained from:
> >> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.96/
> >> The Maven staging repo is:
> >>
https://repository.apache.org/content/repositories/orgapachetomcat-1224/
> >> The git tag is:
> >> https://github.com/apache/tomcat/tree/7.0.96
> >> 5277b175db2e575022672856797240976ad23bcf
> >>
> >> The proposed 7.0.96 release is:
> >> [ ] Broken - do not release
> >> [ ] Stable - go ahead and release as 7.0.96 Stable
> >
> > I observed the same hang on three different Linux systems when using
> > OpenJDK 13-ea+29. Surely early access. The hang is always in
> > TestAbstractAjpProcessor for NIO in test testKeepAlive. The hanging JVM
> > process only shows the AJP client:
> >
> > "main" #1 prio=5 os_prio=0 cpu=1497.40ms elapsed=18779.47s
> > tid=0x00007ff040017800 nid=0x7ea3 runnable [0x00007ff046b74000]
> > java.lang.Thread.State: RUNNABLE
> > at sun.nio.ch.SocketDispatcher.read0(java.base@13-ea/Native
> > Method)
> > at
> > sun.nio.ch.SocketDispatcher.read(java.base@13-ea
/SocketDispatcher.java:47)
> > at
> > sun.nio.ch.NioSocketImpl.tryRead(java.base@13-ea/NioSocketImpl.java:262)
> > at
> > sun.nio.ch.NioSocketImpl.implRead(java.base@13-ea
/NioSocketImpl.java:313)
> > at
> > sun.nio.ch.NioSocketImpl.read(java.base@13-ea/NioSocketImpl.java:351)
> > at
> > sun.nio.ch.NioSocketImpl$1.read(java.base@13-ea/NioSocketImpl.java:802)
> > at
> > java.net.Socket$SocketInputStream.read(java.base@13-ea/Socket.java:919)
> > at
> > org.apache.coyote.ajp.SimpleAjpClient.read(SimpleAjpClient.java:390)
> > at
> >
org.apache.coyote.ajp.SimpleAjpClient.readMessage(SimpleAjpClient.java:365)
> > at
> > org.apache.coyote.ajp.SimpleAjpClient.cping(SimpleAjpClient.java:350)
> > at
> >
org.apache.coyote.ajp.TestAbstractAjpProcessor.testKeepAlive(TestAbstractAjpProcessor.java:526)
> >
> > ...
> >
> > but the log indicates a problem:
> >
> > INFO: Starting test case [testKeepAlive]
> > Jul 26, 2019 5:20:37 PM org.apache.coyote.AbstractProtocol init
> > INFO: Initializing ProtocolHandler ["ajp-nio-127.0.0.1-auto-6"]
> > Jul 26, 2019 5:20:37 PM org.apache.coyote.AbstractProtocol init
> > SEVERE: Failed to initialize end point associated with ProtocolHandler
> > ["ajp-nio-127.0.0.1-auto-6-34726"]
> > java.lang.IllegalArgumentException: timeout < 0
> > at
> >
java.base/sun.nio.ch.ServerSocketAdaptor.setSoTimeout(ServerSocketAdaptor.java:153)
> >
> > at
> > org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:477)
> > at
> >
org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:728)
> > at
> > org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:452)
> > at
> > org.apache.catalina.connector.Connector.initInternal(Connector.java:978)
> > at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> > at
> >
org.apache.catalina.core.StandardService.initInternal(StandardService.java:560)
> >
> > at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> > at
> >
org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:840)
> >
> > at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> > at
> > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:135)
> > at org.apache.catalina.startup.Tomcat.start(Tomcat.java:449)
> > at
> >
org.apache.catalina.startup.TomcatBaseTest$TomcatWithFastSessionIDs.start(TomcatBaseTest.java:808)
> >
> > at
> >
org.apache.coyote.ajp.TestAbstractAjpProcessor.testKeepAlive(TestAbstractAjpProcessor.java:513)
> >
> > at
> > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> > Method)
> > at
> >
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> >
> > at
> >
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >
> > at java.base/java.lang.reflect.Method.invoke(Method.java:567)
> > at
> >
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> >
> > at
> >
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> >
> > at
> >
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> >
> > at
> >
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> >
> > at
> >
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> >
> > at
> >
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> > at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> > at
org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> > at
> >
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> >
> > at
> >
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> >
> > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> > at
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> > at
> > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> > at
org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> > at
> > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> > at
> >
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> >
> > at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> > at
> > junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:38)
> > at
> >
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:536)
> >
> > at
> >
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1178)
> >
> > at
> >
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1032)
> >
> >
> > Jul 26, 2019 5:20:37 PM org.apache.catalina.core.StandardService
> > initInternal
> > SEVERE: Failed to initialize connector
> > [Connector[org.apache.coyote.ajp.AjpNioProtocol-auto-6]]
> > org.apache.catalina.LifecycleException: Failed to initialize component
> > [Connector[org.apache.coyote.ajp.AjpNioProtocol-auto-6]]
> > at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
> > at
> >
org.apache.catalina.core.StandardService.initInternal(StandardService.java:560)
> >
> > at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> > at
> >
org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:840)
> >
> > at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> > at
> > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:135)
> > at org.apache.catalina.startup.Tomcat.start(Tomcat.java:449)
> > at
> >
org.apache.catalina.startup.TomcatBaseTest$TomcatWithFastSessionIDs.start(TomcatBaseTest.java:808)
> >
> > at
> >
org.apache.coyote.ajp.TestAbstractAjpProcessor.testKeepAlive(TestAbstractAjpProcessor.java:513)
> >
> > at
> > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> > Method)
> > at
> >
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> >
> > at
> >
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >
> > at java.base/java.lang.reflect.Method.invoke(Method.java:567)
> > at
> >
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> >
> > at
> >
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> >
> > at
> >
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> >
> > at
> >
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> >
> > at
> >
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> >
> > at
> >
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> > at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> > at
org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> > at
> >
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> >
> > at
> >
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> >
> > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> > at
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> > at
> > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> > at
org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> > at
> > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> > at
> >
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> >
> > at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> > at
> > junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:38)
> > at
> >
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:536)
> >
> > at
> >
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1178)
> >
> > at
> >
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1032)
> >
> > Caused by: org.apache.catalina.LifecycleException: Protocol handler
> > initialization failed
> > at
> > org.apache.catalina.connector.Connector.initInternal(Connector.java:980)
> > at
> > org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> > ... 34 more
> > Caused by: java.lang.IllegalArgumentException: timeout < 0
> > at
> >
java.base/sun.nio.ch.ServerSocketAdaptor.setSoTimeout(ServerSocketAdaptor.java:153)
> >
> > at
> > org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:477)
> > at
> >
org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:728)
> > at
> > org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:452)
> > at
> > org.apache.catalina.connector.Connector.initInternal(Connector.java:978)
> > ... 35 more
> > Jul 26, 2019 5:20:37 PM org.apache.catalina.core.StandardService
> > startInternal
> > INFO: Starting service Tomcat
> > Jul 26, 2019 5:20:37 PM org.apache.catalina.core.StandardEngine
> > startInternal
> > INFO: Starting Servlet Engine: Apache Tomcat/7.0.96
> > Jul 26, 2019 5:20:37 PM org.apache.catalina.startup.TldConfig execute
> > INFO: At least one JAR was scanned for TLDs yet contained no TLDs.
> > Enable debug logging for this logger for a complete list of JARs that
> > were scanned but no TLDs were found in them. Skipping unneeded JARs
> > during scanning can improve startup time and JSP compilation time.
> >
> > I don't think it is a showstopper (since only Java 13 EA).
>
> The test seems to set a socket timeout to -1, which is no longer allowed
> by the following change:
>
>
https://github.com/unofficial-openjdk/openjdk/commit/3a77350f194df226cb6d618589a59d36fae9dc9c
>
> in JDK 13+.
>
> The magic value -1 for timeouts are mor efrequent in our code, but I
> don't know which of these might end up in a setSoTimeout() call.
I don't think this is a showstopper for Tomcat 7 and I'm thinking about
promoting this release candidate.
Regards,
Violeta
> Regards,
>
> Rainer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.96
Posted by Rainer Jung <ra...@kippdata.de>.
Am 26.07.2019 um 22:57 schrieb Rainer Jung:
> Am 24.07.2019 um 15:56 schrieb Violeta Georgieva:
>> The proposed Apache Tomcat 7.0.96 release is now available for voting.
>>
>> For full details, see the changelog:
>> https://ci.apache.org/projects/tomcat/tomcat7/docs/changelog.html
>>
>> It can be obtained from:
>> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.96/
>> The Maven staging repo is:
>> https://repository.apache.org/content/repositories/orgapachetomcat-1224/
>> The git tag is:
>> https://github.com/apache/tomcat/tree/7.0.96
>> 5277b175db2e575022672856797240976ad23bcf
>>
>> The proposed 7.0.96 release is:
>> [ ] Broken - do not release
>> [ ] Stable - go ahead and release as 7.0.96 Stable
>
> I observed the same hang on three different Linux systems when using
> OpenJDK 13-ea+29. Surely early access. The hang is always in
> TestAbstractAjpProcessor for NIO in test testKeepAlive. The hanging JVM
> process only shows the AJP client:
>
> "main" #1 prio=5 os_prio=0 cpu=1497.40ms elapsed=18779.47s
> tid=0x00007ff040017800 nid=0x7ea3 runnable [0x00007ff046b74000]
> java.lang.Thread.State: RUNNABLE
> at sun.nio.ch.SocketDispatcher.read0(java.base@13-ea/Native
> Method)
> at
> sun.nio.ch.SocketDispatcher.read(java.base@13-ea/SocketDispatcher.java:47)
> at
> sun.nio.ch.NioSocketImpl.tryRead(java.base@13-ea/NioSocketImpl.java:262)
> at
> sun.nio.ch.NioSocketImpl.implRead(java.base@13-ea/NioSocketImpl.java:313)
> at
> sun.nio.ch.NioSocketImpl.read(java.base@13-ea/NioSocketImpl.java:351)
> at
> sun.nio.ch.NioSocketImpl$1.read(java.base@13-ea/NioSocketImpl.java:802)
> at
> java.net.Socket$SocketInputStream.read(java.base@13-ea/Socket.java:919)
> at
> org.apache.coyote.ajp.SimpleAjpClient.read(SimpleAjpClient.java:390)
> at
> org.apache.coyote.ajp.SimpleAjpClient.readMessage(SimpleAjpClient.java:365)
> at
> org.apache.coyote.ajp.SimpleAjpClient.cping(SimpleAjpClient.java:350)
> at
> org.apache.coyote.ajp.TestAbstractAjpProcessor.testKeepAlive(TestAbstractAjpProcessor.java:526)
>
> ...
>
> but the log indicates a problem:
>
> INFO: Starting test case [testKeepAlive]
> Jul 26, 2019 5:20:37 PM org.apache.coyote.AbstractProtocol init
> INFO: Initializing ProtocolHandler ["ajp-nio-127.0.0.1-auto-6"]
> Jul 26, 2019 5:20:37 PM org.apache.coyote.AbstractProtocol init
> SEVERE: Failed to initialize end point associated with ProtocolHandler
> ["ajp-nio-127.0.0.1-auto-6-34726"]
> java.lang.IllegalArgumentException: timeout < 0
> at
> java.base/sun.nio.ch.ServerSocketAdaptor.setSoTimeout(ServerSocketAdaptor.java:153)
>
> at
> org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:477)
> at
> org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:728)
> at
> org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:452)
> at
> org.apache.catalina.connector.Connector.initInternal(Connector.java:978)
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> at
> org.apache.catalina.core.StandardService.initInternal(StandardService.java:560)
>
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> at
> org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:840)
>
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:135)
> at org.apache.catalina.startup.Tomcat.start(Tomcat.java:449)
> at
> org.apache.catalina.startup.TomcatBaseTest$TomcatWithFastSessionIDs.start(TomcatBaseTest.java:808)
>
> at
> org.apache.coyote.ajp.TestAbstractAjpProcessor.testKeepAlive(TestAbstractAjpProcessor.java:513)
>
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.base/java.lang.reflect.Method.invoke(Method.java:567)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:38)
> at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:536)
>
> at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1178)
>
> at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1032)
>
>
> Jul 26, 2019 5:20:37 PM org.apache.catalina.core.StandardService
> initInternal
> SEVERE: Failed to initialize connector
> [Connector[org.apache.coyote.ajp.AjpNioProtocol-auto-6]]
> org.apache.catalina.LifecycleException: Failed to initialize component
> [Connector[org.apache.coyote.ajp.AjpNioProtocol-auto-6]]
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
> at
> org.apache.catalina.core.StandardService.initInternal(StandardService.java:560)
>
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> at
> org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:840)
>
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:135)
> at org.apache.catalina.startup.Tomcat.start(Tomcat.java:449)
> at
> org.apache.catalina.startup.TomcatBaseTest$TomcatWithFastSessionIDs.start(TomcatBaseTest.java:808)
>
> at
> org.apache.coyote.ajp.TestAbstractAjpProcessor.testKeepAlive(TestAbstractAjpProcessor.java:513)
>
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.base/java.lang.reflect.Method.invoke(Method.java:567)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:38)
> at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:536)
>
> at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1178)
>
> at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1032)
>
> Caused by: org.apache.catalina.LifecycleException: Protocol handler
> initialization failed
> at
> org.apache.catalina.connector.Connector.initInternal(Connector.java:980)
> at
> org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
> ... 34 more
> Caused by: java.lang.IllegalArgumentException: timeout < 0
> at
> java.base/sun.nio.ch.ServerSocketAdaptor.setSoTimeout(ServerSocketAdaptor.java:153)
>
> at
> org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:477)
> at
> org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:728)
> at
> org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:452)
> at
> org.apache.catalina.connector.Connector.initInternal(Connector.java:978)
> ... 35 more
> Jul 26, 2019 5:20:37 PM org.apache.catalina.core.StandardService
> startInternal
> INFO: Starting service Tomcat
> Jul 26, 2019 5:20:37 PM org.apache.catalina.core.StandardEngine
> startInternal
> INFO: Starting Servlet Engine: Apache Tomcat/7.0.96
> Jul 26, 2019 5:20:37 PM org.apache.catalina.startup.TldConfig execute
> INFO: At least one JAR was scanned for TLDs yet contained no TLDs.
> Enable debug logging for this logger for a complete list of JARs that
> were scanned but no TLDs were found in them. Skipping unneeded JARs
> during scanning can improve startup time and JSP compilation time.
>
> I don't think it is a showstopper (since only Java 13 EA).
The test seems to set a socket timeout to -1, which is no longer allowed
by the following change:
https://github.com/unofficial-openjdk/openjdk/commit/3a77350f194df226cb6d618589a59d36fae9dc9c
in JDK 13+.
The magic value -1 for timeouts are mor efrequent in our code, but I
don't know which of these might end up in a setSoTimeout() call.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 7.0.96
Posted by Rainer Jung <ra...@kippdata.de>.
Am 24.07.2019 um 15:56 schrieb Violeta Georgieva:
> The proposed Apache Tomcat 7.0.96 release is now available for voting.
>
> For full details, see the changelog:
> https://ci.apache.org/projects/tomcat/tomcat7/docs/changelog.html
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.96/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-1224/
> The git tag is:
> https://github.com/apache/tomcat/tree/7.0.96
> 5277b175db2e575022672856797240976ad23bcf
>
> The proposed 7.0.96 release is:
> [ ] Broken - do not release
> [ ] Stable - go ahead and release as 7.0.96 Stable
I observed the same hang on three different Linux systems when using
OpenJDK 13-ea+29. Surely early access. The hang is always in
TestAbstractAjpProcessor for NIO in test testKeepAlive. The hanging JVM
process only shows the AJP client:
"main" #1 prio=5 os_prio=0 cpu=1497.40ms elapsed=18779.47s
tid=0x00007ff040017800 nid=0x7ea3 runnable [0x00007ff046b74000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.SocketDispatcher.read0(java.base@13-ea/Native Method)
at
sun.nio.ch.SocketDispatcher.read(java.base@13-ea/SocketDispatcher.java:47)
at
sun.nio.ch.NioSocketImpl.tryRead(java.base@13-ea/NioSocketImpl.java:262)
at
sun.nio.ch.NioSocketImpl.implRead(java.base@13-ea/NioSocketImpl.java:313)
at
sun.nio.ch.NioSocketImpl.read(java.base@13-ea/NioSocketImpl.java:351)
at
sun.nio.ch.NioSocketImpl$1.read(java.base@13-ea/NioSocketImpl.java:802)
at
java.net.Socket$SocketInputStream.read(java.base@13-ea/Socket.java:919)
at
org.apache.coyote.ajp.SimpleAjpClient.read(SimpleAjpClient.java:390)
at
org.apache.coyote.ajp.SimpleAjpClient.readMessage(SimpleAjpClient.java:365)
at
org.apache.coyote.ajp.SimpleAjpClient.cping(SimpleAjpClient.java:350)
at
org.apache.coyote.ajp.TestAbstractAjpProcessor.testKeepAlive(TestAbstractAjpProcessor.java:526)
...
but the log indicates a problem:
INFO: Starting test case [testKeepAlive]
Jul 26, 2019 5:20:37 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-nio-127.0.0.1-auto-6"]
Jul 26, 2019 5:20:37 PM org.apache.coyote.AbstractProtocol init
SEVERE: Failed to initialize end point associated with ProtocolHandler
["ajp-nio-127.0.0.1-auto-6-34726"]
java.lang.IllegalArgumentException: timeout < 0
at
java.base/sun.nio.ch.ServerSocketAdaptor.setSoTimeout(ServerSocketAdaptor.java:153)
at
org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:477)
at
org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:728)
at
org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:452)
at
org.apache.catalina.connector.Connector.initInternal(Connector.java:978)
at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at
org.apache.catalina.core.StandardService.initInternal(StandardService.java:560)
at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at
org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:840)
at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:135)
at org.apache.catalina.startup.Tomcat.start(Tomcat.java:449)
at
org.apache.catalina.startup.TomcatBaseTest$TomcatWithFastSessionIDs.start(TomcatBaseTest.java:808)
at
org.apache.coyote.ajp.TestAbstractAjpProcessor.testKeepAlive(TestAbstractAjpProcessor.java:513)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:38)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:536)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1178)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1032)
Jul 26, 2019 5:20:37 PM org.apache.catalina.core.StandardService
initInternal
SEVERE: Failed to initialize connector
[Connector[org.apache.coyote.ajp.AjpNioProtocol-auto-6]]
org.apache.catalina.LifecycleException: Failed to initialize component
[Connector[org.apache.coyote.ajp.AjpNioProtocol-auto-6]]
at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
at
org.apache.catalina.core.StandardService.initInternal(StandardService.java:560)
at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at
org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:840)
at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:135)
at org.apache.catalina.startup.Tomcat.start(Tomcat.java:449)
at
org.apache.catalina.startup.TomcatBaseTest$TomcatWithFastSessionIDs.start(TomcatBaseTest.java:808)
at
org.apache.coyote.ajp.TestAbstractAjpProcessor.testKeepAlive(TestAbstractAjpProcessor.java:513)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:38)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:536)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1178)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1032)
Caused by: org.apache.catalina.LifecycleException: Protocol handler
initialization failed
at
org.apache.catalina.connector.Connector.initInternal(Connector.java:980)
at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
... 34 more
Caused by: java.lang.IllegalArgumentException: timeout < 0
at
java.base/sun.nio.ch.ServerSocketAdaptor.setSoTimeout(ServerSocketAdaptor.java:153)
at
org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:477)
at
org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:728)
at
org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:452)
at
org.apache.catalina.connector.Connector.initInternal(Connector.java:978)
... 35 more
Jul 26, 2019 5:20:37 PM org.apache.catalina.core.StandardService
startInternal
INFO: Starting service Tomcat
Jul 26, 2019 5:20:37 PM org.apache.catalina.core.StandardEngine
startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.96
Jul 26, 2019 5:20:37 PM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs.
Enable debug logging for this logger for a complete list of JARs that
were scanned but no TLDs were found in them. Skipping unneeded JARs
during scanning can improve startup time and JSP compilation time.
I don't think it is a showstopper (since only Java 13 EA).
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org