RE: GC allocation failure

] Sent: Thursday, January 04, 2018 12:20 PM To: users@tomcat.apache.org Subject: Re: GC allocation failure -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ambica, On 1/4/18 11:17 AM, Sanka, Ambica wrote: > I am seeing below highlighted errors in native_err logs in all my > tomcat applicati

GC allocation failure

I am seeing below highlighted errors in native_err logs in all my tomcat applications. I also increased memory for the VM from 4GB to 8GB. Still seeing those. When do we get that errors? I am reading online that when program asks for memory and java cannot give, that's when we see them. Please

RE: java

Steffen, Is it also possible to test your stuff with jdk1.8.0_51 so that we will know something must be wrong with security in jdk1.8.0_51? Appreciate your help Ambica. -Original Message- From: Sanka, Ambica [mailto:asa...@atpco.net] Sent: Monday, July 18, 2016 11:00 AM To: Tomcat Users

RE: java

Thanks Steffen for letting me know. Did you also post your issue in java community? Did you get any response? Currently we are using 1.8.0_45. In the future we have requirement to upgrade and got stuck here. -Original Message- From: Steffen Heil (Mailinglisten)

RE: java

Users List <users@tomcat.apache.org> Subject: Re: java -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ambica, On 7/15/16 3:41 PM, Sanka, Ambica wrote: > Chris, Seems attachment was not sent properly. Here is the trace > SEVERE: Naming Exception > occuredjavax.naming.ServiceUnava

RE: java

occuredjava.lang.Exception: Naming Exception occured Thanks Ambica. -Original Message- From: Sanka, Ambica [mailto:asa...@atpco.net] Sent: Friday, July 15, 2016 3:30 PM To: Tomcat Users List <users@tomcat.apache.org> Subject: RE: java Chris, Thank you for the quick response. Please see the at

RE: java

: java -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ambica, On 7/14/16 4:31 PM, Sanka, Ambica wrote: > Does anyone facing issues with security from jdk1.8.0_51 onwards? > We wrote a Valve in tomcat that connects to our ldap and gets user > roles and groups. We connect ldap through ssl c

java

Hi, Does anyone facing issues with security from jdk1.8.0_51 onwards? We wrote a Valve in tomcat that connects to our ldap and gets user roles and groups. We connect ldap through ssl certificate. Our ldap ssl Certificate is working fine till jdk1.8.0_45. From jdk1.8.0_51 , our applications

RE: tomcat8.0.33 classpath/classloader issues

otocol classes are trying to load then it gets failed.I have customized by extending the Http11Protocol but unfortunately unable to load the tomcat/lib class(Http11Protocol). -Original Message- From: Sanka, Ambica [mailto:asa...@atpco.net] Sent: 27 May 2016 21:04 To: Tomcat Users List Subje

RE: tomcat8.0.33 classpath/classloader issues

jar: nothing to verify! scl: getPermissions ProtectionDomain (file:/C:/tomcat8.0.33/lib/tomcat-jni.jar ) java.net.URLClassLoader@520a3426 java.security.Permissions@6973bf95 ( ("java.io.FilePermission" "\C:\tomcat8.0.33\lib\tomcat-jni.jar" "read") ) scl: jar: beginEn

RE: tomcat8.0.33 classpath/classloader issues

You can put in catalina.properties. There is entry with common.loader in catalina.properties under conf folder. Please see below # Note: Values are enclosed in double quotes ("...") in case either the # ${catalina.base} path or the ${catalina.home} path contains a comma.

RE: memory leak in Tomcat 8.0.9

ers@tomcat.apache.org> Subject: Re: memory leak in Tomcat 8.0.9 First of all, the subject is wrong. There is no memory leak in Tomcat. There is a memory leak in the application you are running on Tomcat. On 20/05/2016 14:21, Sanka, Ambica wrote: > 2016-05-19 14:03:31,161 [localhost-startSto

memory leak in Tomcat 8.0.9

Support Team, We have been using Tomcat 8.0.9 for our applications. We noticed below memo= ry leak error and out tomcat could not stopped. We had to kill the process = manually. I was reading articles in the internet and this got address after= tomcat 6. But we found error in higher versions.