On 1/3/2019 11:53 AM, Mark Thomas wrote:
On 02/01/2019 19:50, Adam Rauch wrote:
Our build pre-compiles JSPs by invoking JspC following a pattern similar
to the JspC JavaDoc example configuration:
https://tomcat.apache.org/tomcat-8.5-doc/api/org/apache/jasper/JspC.html
Starting with 9.0.14 and 8
Something wierd seems to be going on... I have an application on tomcat that
used to be on a physical windows server 2008 standard 32-bit which I p2v'd with
vmware converter over as a VM. I'm upgrading the server to windows server 2008
r2 64bit and instead of doing an inplace, I'm just building
Something wierd seems to be going on... I have an application on tomcat that
used to be on a physical windows server 2008 standard 32-bit which I p2v'd with
vmware converter over as a VM. I'm upgrading the server to windows server 2008
r2 64bit and instead of doing an inplace, I'm just building
On 03/01/2019 20:00, John Larsen wrote:
> How can I surpress it if its not an error?
With difficulty. Tomcat always sets that system property and there is no
way (short of editing the scripts which is generally a bad idea) to stop
it. The JVM always generates that log message to stderr (as far as
How can I surpress it if its not an error? Problem I have is the output
causes the script thinks its an error.
Thanks,
John
On Thu, Jan 3, 2019 at 12:51 PM Mark Thomas wrote:
> On 31/12/2018 15:12, John Larsen wrote:
> > Hello,
> >
> > Ever since we started using jdk10 and up we get this error
On 02/01/2019 19:50, Adam Rauch wrote:
> Our build pre-compiles JSPs by invoking JspC following a pattern similar
> to the JspC JavaDoc example configuration:
> https://tomcat.apache.org/tomcat-8.5-doc/api/org/apache/jasper/JspC.html
>
> Starting with 9.0.14 and 8.5.37, our build stopped pre-compi
On 31/12/2018 15:12, John Larsen wrote:
> Hello,
>
> Ever since we started using jdk10 and up we get this error message whenever
> we do ./shutdown.sh.
>
> NOTE: Picked up JDK_JAVA_OPTIONS:
> --add-opens=java.base/java.lang=ALL-UNNAMED
> --add-opens=java.base/java.io=ALL-UNNAMED
> --add-opens=jav
Hi Christopher,
This is no an issue with locating jaas.config. I've set it in java options
as
-Djava.security.auth.login.config=C:\Program Files\Apache Software
Foundation\Tomcat 9.0\conf\jaas.config
I also tested changing a file that do not exist and I got the FileNotFound
exception so it is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steve,
On 1/3/19 02:07, Steve Demy wrote:
> I opened a bug on this
> (https://bz.apache.org/bugzilla/show_bug.cgi?id=63041). It was
> closed by Christopher Schultz suggesting a probable configuration
> issue. Possibly so, but the configuration i
My server.xml is the delivered server.xml file + my declaration of testresult
===
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
PJ,
On 1/2/19 22:15, PJ Pillai wrote:
> Here is additional information. 1. Tomcat is running on Windows
> 2016 server. 2. Tomcat is started as windows service.
>
> I tried Tomcat 8.5 as well and still get the same warning message
> and user is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 1/3/19 03:56, andre seame wrote:
> Hello,
>
> In tomcat 7, I have a server.xml config file. In the host section I
> have
>
>
>
> So, I can access to static file :
> http://server:8080/testresults/myfile.png, where the file is stored
>
Hello,
In tomcat 7, I have a server.xml config file. In the host section I have
So, I can access to static file : http://server:8080/testresults/myfile.png,
where the file is stored in d:\TESTRESULTS\myfile.png
When using the HTML gui management interface -http://server:8080/manager/html),
I
On 02.01.19 23:11, Janakiram Maganti wrote:
> Hi Support,
>
> Can you suggest what is the latest Java 8 version supported for “Apache
> Tomcat/7.0.77”.
>
According to https://tomcat.apache.org/whichversion.html, there's no
maximum version, it's "Java 6 and later".
E.g. if you're running into sp
14 matches
Mail list logo
