-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 7/14/18 4:53 PM, David Babooram wrote:
> Alright.
>
> I guess the thought the process was to upgrade to 6, then 7, 8
Having gone through exactly this process a few years ago (from 4.1 to
5.0 and continuing on up the major-version ladder
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Will,
On 7/10/18 9:03 AM, Will Nordmeyer wrote:
> I have an application in Tomcat 7 that connects to an Oracle
> database. Currently we are connecting using the username/password
> which is embedded in the xml files. To harden security, we are
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Usha,
On 7/3/18 3:25 PM, Support wrote:
> Chris, sorry for the typo! Can't believe I did it.
>
> Client -->F5:8080> does not connect to Tomcat-server1:8080.
> Client -->connects fine to Tomcat-server1:8080.
>
> Client can connect fine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 7/17/18 10:36 AM, Chris Cheshire wrote:
> James, this can be done using something like the following
> configuration in your META-INF/context.xml (I use tomcat 8.5)
>
> className="org.apache.catalina.webresources.DirResourceSet"
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jeffrey,
On 7/17/18 3:08 PM, Jeffrey Beckstrom wrote:
> How will Oracle's new licensing of Java affect Tomcat?
IANAL, but Java's licensing should not affect Tomcat at all, unless
Oracle decides that writing software using Java is somehow no longer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gopi,
On 7/10/18 5:38 PM, Gopi Palla wrote:
> We have two dc, in one of the dc tomcat http sessions are exceeded.
> we are using introscope to monitor tomcat application server and
> getting the alerts, we kept the threshold value as 850 in
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I've got a lb worker with two balanced nodes. One of the nodes has a
non-zero value for the "Err" (errors) field, but there is a blank
entry for the "LE" (last error timestamp) field.
I'm using mod_jk 1.2.41 on x86-64 Linux.
The whole XML
Thanks for the feedback. I was confident all along this wasn't a Tomcat issue,
and I believe we identified the culprit as the firewall. I was looking for
logging that would show the socket behavior (accept, close, etc.) to show that
as far as Tomcat was concerned, the delay was happening before
On 20.07.2018 09:05, Shailendra Kumar Verma wrote:
Hello,
I recently installed Tomcat 9.0.8 on Windows 2016 server with JRE 10.0.2 x64.
After installation, it is taking 95% of CPU and 4 GB of RAM without any calls
running to the box. Why?
System has 32 GB of RAM and 6 CPU cores.
Why is
Shailendra,
On Fri, Jul 20, 2018 at 12:35 PM Shailendra Kumar Verma
wrote:
>
> Hello,
>
> I recently installed Tomcat 9.0.8 on Windows 2016 server with JRE 10.0.2 x64.
> After installation, it is taking 95% of CPU and 4 GB of RAM without any calls
> running to the box. Why?
>
> System has 32
Hello,
I recently installed Tomcat 9.0.8 on Windows 2016 server with JRE 10.0.2 x64.
After installation, it is taking 95% of CPU and 4 GB of RAM without any calls
running to the box. Why?
System has 32 GB of RAM and 6 CPU cores.
Why is Tomcat is taking 95% of CPU at idle condition, that is
11 matches
Mail list logo