Fellow List members:
In the end, this morning, having been told that getting the development
instance running under Java 8 had become a priority, and knowing that
Tomcat was running under Apache (and also learning that Apache itself
wasn't running under a service name containing recognizable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 12/18/18 17:34, James H. H. Lampert wrote:
> On the Debian List, "deloptes" brought up the subect of
> "openjdk-8-jdk-headless"; could that be relevant?
The "headless" version has fewer package dependencies because it does
not provide
On 12/18/18, 2:49 PM, Caldarale, Charles R wrote:
The above indicates you have a Tomcat (or something much like it) already
running...
You would think so, and yet if I switch the JAVA_HOME line in setenv.sh
to Java 7, it launches just fine. . . .
WAIT A SECOND!
Port 443 is open, and the
> From: James H. H. Lampert [mailto:jam...@touchtonecorp.com]
> Subject: Re: Tomcat 8 runs under Java 7, but not Java 8
> Excerpt from the relevant time period, catalina.2018-12-18.log:
> > 18-Dec-2018 20:18:55.419 SEVERE [main]
org.apache.catalina.core.Stand
On 12/18/18, 12:50 PM, Mark Thomas wrote:
They don't appear to be very helpful.
They certainly didn't suggest anything to me.
What do the Tomcat logs show? catalina.-mm-dd.log is likely to be
the most useful but check them all.
Dear Mr. Thomas, et al:
Excerpt from the relevant time
Hi James,
Le 18/12/2018 à 21:40, James H. H. Lampert a écrit :
> I just installed Java 8 (not as the default JRE) on a Google Compute
> Debian 8 instance that has been running Tomcat 8 under Java 7.
I assume you are using the tomcat8 package from the distribution. Tomcat
on Debian 8 Jessie is a
On 18/12/2018 20:40, James H. H. Lampert wrote:
> I just installed Java 8 (not as the default JRE) on a Google Compute
> Debian 8 instance that has been running Tomcat 8 under Java 7.
>
> If I change setenv.sh to add
>> JAVA_HOME="/usr/lib/jvm/java-8-openjdk-amd64/"
>
> and I try to "service
