You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Christopher Schultz <ch...@christopherschultz.net> on 2022/11/02 16:16:02 UTC
Re: Compatibility, 32 bit ..
John,
On 10/28/22 10:46, John Dale (DB2DOM) wrote:
> I see .. Mark and/or Christopher - this means that no Tomcat 10, right?
https://tomcat.apache.org/whichversion.html
Tomcat 10.0, yes.
Tomcat 10.1, no.
Tomcat 10.0 has been superseded and will not get any further updates,
thus you should not use it for any purpose IMO.
-chris
> On 10/28/22, Konstantin Kolinko <kn...@gmail.com> wrote:
>> чт, 27 окт. 2022 г. в 18:02, John Dale (DB2DOM) <jc...@gmail.com>:
>>>
>>> I had the same thought when I saw it. Here is java -version output
>>> complete:
>>>
>>> openjdk version "9-internal"
>>> OpenJDK Runtime Environment (build
>>> 9-internal+0-2016-04-14-195526.buildd.src)
>>> OpenJDK Server VM (build 9-internal+0-2016-04-14-195526.buildd.src, mixed
>>> mode)
>>
>> The first official release of Java 9 (GA release) was on 21 September
>> 2017 [1][2]
>>
>> What you are seeing here (built in 2016) apparently is some early access
>> stuff.
>>
>> As a whole, Java 9 has already reached its end of life. (LTS releases
>> are Java 8, 11 and 17).
>>
>> [1] https://openjdk.org/projects/jdk9/
>> [2[ https://en.wikipedia.org/wiki/Java_version_history
>>
>> Best regards,
>> Konstantin Kolinko
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Compatibility, 32 bit ..
Posted by Mark Thomas <ma...@apache.org>.
On 03/11/2022 11:48, John Dale (DB2DOM) wrote:
> Greetings - thanks for the pointer below.
>
> Brought up some interesting questions below.
>
> How do changes at Oracle affect Tomcat? Has OpenJRE sufficiently
> insulated the risk?
What changes at Oracle? What risk?
There isn't anything that i am particularly worried about at the moment.
> What would you say is the best O/R M tool for tomcat that still keeps
> coding hands-on with respect to connection management and MVC handler
> deployment/logic?
Sorry, not a clue.
> What are some good object databases (are there any) that work well with Tomcat?
Ditto.
Mark
>
>
> On 11/3/22, Mark Thomas <ma...@apache.org> wrote:
>> On 02/11/2022 18:51, Christopher Schultz wrote:
>>> John,
>>>
>>> On 11/2/22 14:32, John Dale (DB2DOM) wrote:
>>>> On 11/2/22, Christopher Schultz <ch...@christopherschultz.net> wrote:
>>>>> John,
>>>>>
>>>>> On 11/2/22 12:44, John Dale (DB2DOM) wrote:
>>>>>> I'd like to continue to invest in Raspberry Pi, but also try to put
>>>>>> together a functional 32bit build of my software for those poor old
>>>>>> neglected closeted towers (really, poor things!).
>>>>>>
>>>>>> I should be able to do it, from the looks of this.
>>>>>>
>>>>>> Are you guys doing any kind of pruned down version of Tomcat or maybe
>>>>>> a configurable Tomcat that will only include some bare bones stuff
>>>>>> like request parsing, connection pooling, and (obviously) threading?
>>>>>
>>>>> You might be surprised to learn that Tomcat is pretty stripped-down
>>>>> already. What do you imagine that Tomcat is doing that is beyond what
>>>>> you have listed above?
>>>>
>>>> Isn't there still a lot of J2E code allowing deployment and processing
>>>> of J2E standards that aren't necessarily needed? What else?
>>>
>>> Well, it supports a few things that you may not use in your
>>> application(s), such as WebSocket, asynchronous I/O, JSP/EL, and JASPIC.
>>> Maybe you don't use JSPs, so you can throw-out the JSP and EL
>>> components. But if you don't use them, they are a few inert kilobytes of
>>> data on the disk. Same with JASPIC. Removing them would be more work
>>> than simply ignoring them.
>>>
>>> Tomcat 10.1 requires Java 11 because the specs it follows say that's the
>>> minimum required version, for whatever reason.
>>>
>>> The official Tomcat binary releases will be built using Java 11 and thus
>>> they must be run by Java 11 or later.
>>>
>>> But there's nothing stopping you from trying to use the source to build
>>> a Java-8-compatible build of Tomcat 10.1. I don't think we are using any
>>> source-level features of Java that actually require anything past Java
>>> 8. But if it vomits at runtime because something is missing because you
>>> actually /do/ need Java 11, then we're gonna tell you "don't do that."
>>
>> There are a few things that will break - and some of them are fairly
>> fundamental.
>>
>> The simplest way to see what is going to break is to look at the
>> org.apache.tomcat.util.compat package. Then you need to look at the
>> JreNCompat classes that have been removed as a result of the increase in
>> minimum Java version. For 10.0.x to 10.1.x that is Jre9Compat.
>>
>> If you want to run 10.1.x on Java 8, in theory you could revert the
>> commit that removed Jre9Compat but as Chris says you are very much on
>> your own in terms of support if things go wrong.
>>
>> Mark
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Compatibility, 32 bit ..
Posted by "John Dale (DB2DOM)" <jc...@gmail.com>.
Greetings - thanks for the pointer below.
Brought up some interesting questions below.
How do changes at Oracle affect Tomcat? Has OpenJRE sufficiently
insulated the risk?
What would you say is the best O/R M tool for tomcat that still keeps
coding hands-on with respect to connection management and MVC handler
deployment/logic?
What are some good object databases (are there any) that work well with Tomcat?
On 11/3/22, Mark Thomas <ma...@apache.org> wrote:
> On 02/11/2022 18:51, Christopher Schultz wrote:
>> John,
>>
>> On 11/2/22 14:32, John Dale (DB2DOM) wrote:
>>> On 11/2/22, Christopher Schultz <ch...@christopherschultz.net> wrote:
>>>> John,
>>>>
>>>> On 11/2/22 12:44, John Dale (DB2DOM) wrote:
>>>>> I'd like to continue to invest in Raspberry Pi, but also try to put
>>>>> together a functional 32bit build of my software for those poor old
>>>>> neglected closeted towers (really, poor things!).
>>>>>
>>>>> I should be able to do it, from the looks of this.
>>>>>
>>>>> Are you guys doing any kind of pruned down version of Tomcat or maybe
>>>>> a configurable Tomcat that will only include some bare bones stuff
>>>>> like request parsing, connection pooling, and (obviously) threading?
>>>>
>>>> You might be surprised to learn that Tomcat is pretty stripped-down
>>>> already. What do you imagine that Tomcat is doing that is beyond what
>>>> you have listed above?
>>>
>>> Isn't there still a lot of J2E code allowing deployment and processing
>>> of J2E standards that aren't necessarily needed? What else?
>>
>> Well, it supports a few things that you may not use in your
>> application(s), such as WebSocket, asynchronous I/O, JSP/EL, and JASPIC.
>> Maybe you don't use JSPs, so you can throw-out the JSP and EL
>> components. But if you don't use them, they are a few inert kilobytes of
>> data on the disk. Same with JASPIC. Removing them would be more work
>> than simply ignoring them.
>>
>> Tomcat 10.1 requires Java 11 because the specs it follows say that's the
>> minimum required version, for whatever reason.
>>
>> The official Tomcat binary releases will be built using Java 11 and thus
>> they must be run by Java 11 or later.
>>
>> But there's nothing stopping you from trying to use the source to build
>> a Java-8-compatible build of Tomcat 10.1. I don't think we are using any
>> source-level features of Java that actually require anything past Java
>> 8. But if it vomits at runtime because something is missing because you
>> actually /do/ need Java 11, then we're gonna tell you "don't do that."
>
> There are a few things that will break - and some of them are fairly
> fundamental.
>
> The simplest way to see what is going to break is to look at the
> org.apache.tomcat.util.compat package. Then you need to look at the
> JreNCompat classes that have been removed as a result of the increase in
> minimum Java version. For 10.0.x to 10.1.x that is Jre9Compat.
>
> If you want to run 10.1.x on Java 8, in theory you could revert the
> commit that removed Jre9Compat but as Chris says you are very much on
> your own in terms of support if things go wrong.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Compatibility, 32 bit ..
Posted by Mark Thomas <ma...@apache.org>.
On 03/11/2022 12:29, John Dale (DB2DOM) wrote:
> Is Tomcat's HTTP/S processing libraries modular and portable?
That depends on how you define "HTTP/S processing libraries", "modular"
and "portable".
Can you take then and use them with something else where you just need
HTTP/S and no servlet API? Not easily.
Are they portable? Yes, they are as portable as Java is.
Are they modular? The classes are all in a single JAR but it is
structured so it easy to extend with new implementations.
Tomcat uses JSSE for TLS. When using OpenSSL, it is wrapped so it looks
like a JSSE implementation.
Mark
>
>
>
> On 11/3/22, Mark Thomas <ma...@apache.org> wrote:
>> On 02/11/2022 18:51, Christopher Schultz wrote:
>>> John,
>>>
>>> On 11/2/22 14:32, John Dale (DB2DOM) wrote:
>>>> On 11/2/22, Christopher Schultz <ch...@christopherschultz.net> wrote:
>>>>> John,
>>>>>
>>>>> On 11/2/22 12:44, John Dale (DB2DOM) wrote:
>>>>>> I'd like to continue to invest in Raspberry Pi, but also try to put
>>>>>> together a functional 32bit build of my software for those poor old
>>>>>> neglected closeted towers (really, poor things!).
>>>>>>
>>>>>> I should be able to do it, from the looks of this.
>>>>>>
>>>>>> Are you guys doing any kind of pruned down version of Tomcat or maybe
>>>>>> a configurable Tomcat that will only include some bare bones stuff
>>>>>> like request parsing, connection pooling, and (obviously) threading?
>>>>>
>>>>> You might be surprised to learn that Tomcat is pretty stripped-down
>>>>> already. What do you imagine that Tomcat is doing that is beyond what
>>>>> you have listed above?
>>>>
>>>> Isn't there still a lot of J2E code allowing deployment and processing
>>>> of J2E standards that aren't necessarily needed? What else?
>>>
>>> Well, it supports a few things that you may not use in your
>>> application(s), such as WebSocket, asynchronous I/O, JSP/EL, and JASPIC.
>>> Maybe you don't use JSPs, so you can throw-out the JSP and EL
>>> components. But if you don't use them, they are a few inert kilobytes of
>>> data on the disk. Same with JASPIC. Removing them would be more work
>>> than simply ignoring them.
>>>
>>> Tomcat 10.1 requires Java 11 because the specs it follows say that's the
>>> minimum required version, for whatever reason.
>>>
>>> The official Tomcat binary releases will be built using Java 11 and thus
>>> they must be run by Java 11 or later.
>>>
>>> But there's nothing stopping you from trying to use the source to build
>>> a Java-8-compatible build of Tomcat 10.1. I don't think we are using any
>>> source-level features of Java that actually require anything past Java
>>> 8. But if it vomits at runtime because something is missing because you
>>> actually /do/ need Java 11, then we're gonna tell you "don't do that."
>>
>> There are a few things that will break - and some of them are fairly
>> fundamental.
>>
>> The simplest way to see what is going to break is to look at the
>> org.apache.tomcat.util.compat package. Then you need to look at the
>> JreNCompat classes that have been removed as a result of the increase in
>> minimum Java version. For 10.0.x to 10.1.x that is Jre9Compat.
>>
>> If you want to run 10.1.x on Java 8, in theory you could revert the
>> commit that removed Jre9Compat but as Chris says you are very much on
>> your own in terms of support if things go wrong.
>>
>> Mark
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Compatibility, 32 bit ..
Posted by "John Dale (DB2DOM)" <jc...@gmail.com>.
Is Tomcat's HTTP/S processing libraries modular and portable?
On 11/3/22, Mark Thomas <ma...@apache.org> wrote:
> On 02/11/2022 18:51, Christopher Schultz wrote:
>> John,
>>
>> On 11/2/22 14:32, John Dale (DB2DOM) wrote:
>>> On 11/2/22, Christopher Schultz <ch...@christopherschultz.net> wrote:
>>>> John,
>>>>
>>>> On 11/2/22 12:44, John Dale (DB2DOM) wrote:
>>>>> I'd like to continue to invest in Raspberry Pi, but also try to put
>>>>> together a functional 32bit build of my software for those poor old
>>>>> neglected closeted towers (really, poor things!).
>>>>>
>>>>> I should be able to do it, from the looks of this.
>>>>>
>>>>> Are you guys doing any kind of pruned down version of Tomcat or maybe
>>>>> a configurable Tomcat that will only include some bare bones stuff
>>>>> like request parsing, connection pooling, and (obviously) threading?
>>>>
>>>> You might be surprised to learn that Tomcat is pretty stripped-down
>>>> already. What do you imagine that Tomcat is doing that is beyond what
>>>> you have listed above?
>>>
>>> Isn't there still a lot of J2E code allowing deployment and processing
>>> of J2E standards that aren't necessarily needed? What else?
>>
>> Well, it supports a few things that you may not use in your
>> application(s), such as WebSocket, asynchronous I/O, JSP/EL, and JASPIC.
>> Maybe you don't use JSPs, so you can throw-out the JSP and EL
>> components. But if you don't use them, they are a few inert kilobytes of
>> data on the disk. Same with JASPIC. Removing them would be more work
>> than simply ignoring them.
>>
>> Tomcat 10.1 requires Java 11 because the specs it follows say that's the
>> minimum required version, for whatever reason.
>>
>> The official Tomcat binary releases will be built using Java 11 and thus
>> they must be run by Java 11 or later.
>>
>> But there's nothing stopping you from trying to use the source to build
>> a Java-8-compatible build of Tomcat 10.1. I don't think we are using any
>> source-level features of Java that actually require anything past Java
>> 8. But if it vomits at runtime because something is missing because you
>> actually /do/ need Java 11, then we're gonna tell you "don't do that."
>
> There are a few things that will break - and some of them are fairly
> fundamental.
>
> The simplest way to see what is going to break is to look at the
> org.apache.tomcat.util.compat package. Then you need to look at the
> JreNCompat classes that have been removed as a result of the increase in
> minimum Java version. For 10.0.x to 10.1.x that is Jre9Compat.
>
> If you want to run 10.1.x on Java 8, in theory you could revert the
> commit that removed Jre9Compat but as Chris says you are very much on
> your own in terms of support if things go wrong.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Compatibility, 32 bit ..
Posted by Mark Thomas <ma...@apache.org>.
On 02/11/2022 18:51, Christopher Schultz wrote:
> John,
>
> On 11/2/22 14:32, John Dale (DB2DOM) wrote:
>> On 11/2/22, Christopher Schultz <ch...@christopherschultz.net> wrote:
>>> John,
>>>
>>> On 11/2/22 12:44, John Dale (DB2DOM) wrote:
>>>> I'd like to continue to invest in Raspberry Pi, but also try to put
>>>> together a functional 32bit build of my software for those poor old
>>>> neglected closeted towers (really, poor things!).
>>>>
>>>> I should be able to do it, from the looks of this.
>>>>
>>>> Are you guys doing any kind of pruned down version of Tomcat or maybe
>>>> a configurable Tomcat that will only include some bare bones stuff
>>>> like request parsing, connection pooling, and (obviously) threading?
>>>
>>> You might be surprised to learn that Tomcat is pretty stripped-down
>>> already. What do you imagine that Tomcat is doing that is beyond what
>>> you have listed above?
>>
>> Isn't there still a lot of J2E code allowing deployment and processing
>> of J2E standards that aren't necessarily needed? What else?
>
> Well, it supports a few things that you may not use in your
> application(s), such as WebSocket, asynchronous I/O, JSP/EL, and JASPIC.
> Maybe you don't use JSPs, so you can throw-out the JSP and EL
> components. But if you don't use them, they are a few inert kilobytes of
> data on the disk. Same with JASPIC. Removing them would be more work
> than simply ignoring them.
>
> Tomcat 10.1 requires Java 11 because the specs it follows say that's the
> minimum required version, for whatever reason.
>
> The official Tomcat binary releases will be built using Java 11 and thus
> they must be run by Java 11 or later.
>
> But there's nothing stopping you from trying to use the source to build
> a Java-8-compatible build of Tomcat 10.1. I don't think we are using any
> source-level features of Java that actually require anything past Java
> 8. But if it vomits at runtime because something is missing because you
> actually /do/ need Java 11, then we're gonna tell you "don't do that."
There are a few things that will break - and some of them are fairly
fundamental.
The simplest way to see what is going to break is to look at the
org.apache.tomcat.util.compat package. Then you need to look at the
JreNCompat classes that have been removed as a result of the increase in
minimum Java version. For 10.0.x to 10.1.x that is Jre9Compat.
If you want to run 10.1.x on Java 8, in theory you could revert the
commit that removed Jre9Compat but as Chris says you are very much on
your own in terms of support if things go wrong.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Compatibility, 32 bit ..
Posted by Christopher Schultz <ch...@christopherschultz.net>.
John,
On 11/2/22 14:32, John Dale (DB2DOM) wrote:
> On 11/2/22, Christopher Schultz <ch...@christopherschultz.net> wrote:
>> John,
>>
>> On 11/2/22 12:44, John Dale (DB2DOM) wrote:
>>> I'd like to continue to invest in Raspberry Pi, but also try to put
>>> together a functional 32bit build of my software for those poor old
>>> neglected closeted towers (really, poor things!).
>>>
>>> I should be able to do it, from the looks of this.
>>>
>>> Are you guys doing any kind of pruned down version of Tomcat or maybe
>>> a configurable Tomcat that will only include some bare bones stuff
>>> like request parsing, connection pooling, and (obviously) threading?
>>
>> You might be surprised to learn that Tomcat is pretty stripped-down
>> already. What do you imagine that Tomcat is doing that is beyond what
>> you have listed above?
>
> Isn't there still a lot of J2E code allowing deployment and processing
> of J2E standards that aren't necessarily needed? What else?
Well, it supports a few things that you may not use in your
application(s), such as WebSocket, asynchronous I/O, JSP/EL, and JASPIC.
Maybe you don't use JSPs, so you can throw-out the JSP and EL
components. But if you don't use them, they are a few inert kilobytes of
data on the disk. Same with JASPIC. Removing them would be more work
than simply ignoring them.
Tomcat 10.1 requires Java 11 because the specs it follows say that's the
minimum required version, for whatever reason.
The official Tomcat binary releases will be built using Java 11 and thus
they must be run by Java 11 or later.
But there's nothing stopping you from trying to use the source to build
a Java-8-compatible build of Tomcat 10.1. I don't think we are using any
source-level features of Java that actually require anything past Java
8. But if it vomits at runtime because something is missing because you
actually /do/ need Java 11, then we're gonna tell you "don't do that."
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Compatibility, 32 bit ..
Posted by "John Dale (DB2DOM)" <jc...@gmail.com>.
On 11/2/22, Christopher Schultz <ch...@christopherschultz.net> wrote:
> John,
>
> On 11/2/22 12:44, John Dale (DB2DOM) wrote:
>> I'd like to continue to invest in Raspberry Pi, but also try to put
>> together a functional 32bit build of my software for those poor old
>> neglected closeted towers (really, poor things!).
>>
>> I should be able to do it, from the looks of this.
>>
>> Are you guys doing any kind of pruned down version of Tomcat or maybe
>> a configurable Tomcat that will only include some bare bones stuff
>> like request parsing, connection pooling, and (obviously) threading?
>
> You might be surprised to learn that Tomcat is pretty stripped-down
> already. What do you imagine that Tomcat is doing that is beyond what
> you have listed above?
Isn't there still a lot of J2E code allowing deployment and processing
of J2E standards that aren't necessarily needed? What else? I agree
that the download is still very reasonable and it's got great support
because of you et al; clearly a good thing in the computing world that
enabled me to create my DB2DOM doodad. Keep it up and thanks.
>
>> Thanks for the pointers .. I would like to try to meet you guys in
>> person at a conference sometime to swap notes and be pals.
>
> You just missed your first opportunity in 3 years this past month, in
> New Orleans. Well... some of us were there ;)
I need to get to more conferences .. hopefully soon. I have so many questions.
>
> -chris
>
>> On 11/2/22, Christopher Schultz <ch...@christopherschultz.net> wrote:
>>> John,
>>>
>>> On 10/28/22 10:46, John Dale (DB2DOM) wrote:
>>>> I see .. Mark and/or Christopher - this means that no Tomcat 10, right?
>>>
>>> https://tomcat.apache.org/whichversion.html
>>>
>>> Tomcat 10.0, yes.
>>> Tomcat 10.1, no.
>>>
>>> Tomcat 10.0 has been superseded and will not get any further updates,
>>> thus you should not use it for any purpose IMO.
>>>
>>> -chris
>>>
>>>> On 10/28/22, Konstantin Kolinko <kn...@gmail.com> wrote:
>>>>> чт, 27 окт. 2022 г. в 18:02, John Dale (DB2DOM) <jc...@gmail.com>:
>>>>>>
>>>>>> I had the same thought when I saw it. Here is java -version output
>>>>>> complete:
>>>>>>
>>>>>> openjdk version "9-internal"
>>>>>> OpenJDK Runtime Environment (build
>>>>>> 9-internal+0-2016-04-14-195526.buildd.src)
>>>>>> OpenJDK Server VM (build 9-internal+0-2016-04-14-195526.buildd.src,
>>>>>> mixed
>>>>>> mode)
>>>>>
>>>>> The first official release of Java 9 (GA release) was on 21 September
>>>>> 2017 [1][2]
>>>>>
>>>>> What you are seeing here (built in 2016) apparently is some early
>>>>> access
>>>>> stuff.
>>>>>
>>>>> As a whole, Java 9 has already reached its end of life. (LTS releases
>>>>> are Java 8, 11 and 17).
>>>>>
>>>>> [1] https://openjdk.org/projects/jdk9/
>>>>> [2[ https://en.wikipedia.org/wiki/Java_version_history
>>>>>
>>>>> Best regards,
>>>>> Konstantin Kolinko
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Compatibility, 32 bit ..
Posted by Christopher Schultz <ch...@christopherschultz.net>.
John,
On 11/2/22 12:44, John Dale (DB2DOM) wrote:
> I'd like to continue to invest in Raspberry Pi, but also try to put
> together a functional 32bit build of my software for those poor old
> neglected closeted towers (really, poor things!).
>
> I should be able to do it, from the looks of this.
>
> Are you guys doing any kind of pruned down version of Tomcat or maybe
> a configurable Tomcat that will only include some bare bones stuff
> like request parsing, connection pooling, and (obviously) threading?
You might be surprised to learn that Tomcat is pretty stripped-down
already. What do you imagine that Tomcat is doing that is beyond what
you have listed above?
> Thanks for the pointers .. I would like to try to meet you guys in
> person at a conference sometime to swap notes and be pals.
You just missed your first opportunity in 3 years this past month, in
New Orleans. Well... some of us were there ;)
-chris
> On 11/2/22, Christopher Schultz <ch...@christopherschultz.net> wrote:
>> John,
>>
>> On 10/28/22 10:46, John Dale (DB2DOM) wrote:
>>> I see .. Mark and/or Christopher - this means that no Tomcat 10, right?
>>
>> https://tomcat.apache.org/whichversion.html
>>
>> Tomcat 10.0, yes.
>> Tomcat 10.1, no.
>>
>> Tomcat 10.0 has been superseded and will not get any further updates,
>> thus you should not use it for any purpose IMO.
>>
>> -chris
>>
>>> On 10/28/22, Konstantin Kolinko <kn...@gmail.com> wrote:
>>>> чт, 27 окт. 2022 г. в 18:02, John Dale (DB2DOM) <jc...@gmail.com>:
>>>>>
>>>>> I had the same thought when I saw it. Here is java -version output
>>>>> complete:
>>>>>
>>>>> openjdk version "9-internal"
>>>>> OpenJDK Runtime Environment (build
>>>>> 9-internal+0-2016-04-14-195526.buildd.src)
>>>>> OpenJDK Server VM (build 9-internal+0-2016-04-14-195526.buildd.src,
>>>>> mixed
>>>>> mode)
>>>>
>>>> The first official release of Java 9 (GA release) was on 21 September
>>>> 2017 [1][2]
>>>>
>>>> What you are seeing here (built in 2016) apparently is some early access
>>>> stuff.
>>>>
>>>> As a whole, Java 9 has already reached its end of life. (LTS releases
>>>> are Java 8, 11 and 17).
>>>>
>>>> [1] https://openjdk.org/projects/jdk9/
>>>> [2[ https://en.wikipedia.org/wiki/Java_version_history
>>>>
>>>> Best regards,
>>>> Konstantin Kolinko
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Compatibility, 32 bit ..
Posted by "John Dale (DB2DOM)" <jc...@gmail.com>.
I'd like to continue to invest in Raspberry Pi, but also try to put
together a functional 32bit build of my software for those poor old
neglected closeted towers (really, poor things!).
I should be able to do it, from the looks of this.
Are you guys doing any kind of pruned down version of Tomcat or maybe
a configurable Tomcat that will only include some bare bones stuff
like request parsing, connection pooling, and (obviously) threading?
Thanks for the pointers .. I would like to try to meet you guys in
person at a conference sometime to swap notes and be pals.
Anyway, have a great day!
Sincerely,
John
On 11/2/22, Christopher Schultz <ch...@christopherschultz.net> wrote:
> John,
>
> On 10/28/22 10:46, John Dale (DB2DOM) wrote:
>> I see .. Mark and/or Christopher - this means that no Tomcat 10, right?
>
> https://tomcat.apache.org/whichversion.html
>
> Tomcat 10.0, yes.
> Tomcat 10.1, no.
>
> Tomcat 10.0 has been superseded and will not get any further updates,
> thus you should not use it for any purpose IMO.
>
> -chris
>
>> On 10/28/22, Konstantin Kolinko <kn...@gmail.com> wrote:
>>> чт, 27 окт. 2022 г. в 18:02, John Dale (DB2DOM) <jc...@gmail.com>:
>>>>
>>>> I had the same thought when I saw it. Here is java -version output
>>>> complete:
>>>>
>>>> openjdk version "9-internal"
>>>> OpenJDK Runtime Environment (build
>>>> 9-internal+0-2016-04-14-195526.buildd.src)
>>>> OpenJDK Server VM (build 9-internal+0-2016-04-14-195526.buildd.src,
>>>> mixed
>>>> mode)
>>>
>>> The first official release of Java 9 (GA release) was on 21 September
>>> 2017 [1][2]
>>>
>>> What you are seeing here (built in 2016) apparently is some early access
>>> stuff.
>>>
>>> As a whole, Java 9 has already reached its end of life. (LTS releases
>>> are Java 8, 11 and 17).
>>>
>>> [1] https://openjdk.org/projects/jdk9/
>>> [2[ https://en.wikipedia.org/wiki/Java_version_history
>>>
>>> Best regards,
>>> Konstantin Kolinko
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org