Re: Cannot upgrade past Tomcat 6 due to massive memory increase

On 18/02/2016 22:57, Ty wrote: > I've re-run my tests using 8.0.x trunk (8.0.33-dev) using the same > procedure from the first message of this thread, and summarized the results > below. Heap usage is vastly improved both with and without JAR scanning. > Heap size and startup time are both

Re: Cannot upgrade past Tomcat 6 due to massive memory increase

I've re-run my tests using 8.0.x trunk (8.0.33-dev) using the same procedure from the first message of this thread, and summarized the results below. Heap usage is vastly improved both with and without JAR scanning. Heap size and startup time are both reasonable and it's now feasible to re-visit

Re: WebEx meeting invitation: Apache Tomcat: Connector Selection

The recording is now on YouTube: https://www.youtube.com/watch?v=LBSWixIwMmU Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Updating SSL certificates

On 18/02/2016 22:03, James H. H. Lampert wrote: > Out of morbid curiosity, is there a way to make a certificate update > take effect without restarting Tomcat? Sort of. Set bindOnInit on the connector to false. Modify the config via JMX. Then you should be able to use JMX to call stop()

Updating SSL certificates

Out of morbid curiosity, is there a way to make a certificate update take effect without restarting Tomcat? -- JHHL - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail:

Re: Session on Tomcat 7 manager screem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Qadeer, On 2/18/16 12:03 PM, Qadeer Khan wrote: > Ok I got a little more information the user Get this, too: What exact version of Tomcat. 7.0.what? > On clicking on the session number '0', he is getting the following > error. Any idea? > > FAIL -

Re: Session on Tomcat 7 manager screem

On 2/18/2016 11:55 AM, Qadeer Khan wrote: I am not sure why so aggravated you get... I am not claiming any bugs or anything and I am no expert in Tomcat 7 application server. I am at client site and they are simply asking me a question as I explained before. They have java applications

Re: Session on Tomcat 7 manager screem

On 18/02/2016 16:55, Qadeer Khan wrote: > I am not sure why so aggravated you get... I am not claiming any bugs or > anything Then you need to modify your language rather than suggesting that there is something wrong in Tomcat that needs fixing. > and I am no expert in Tomcat 7 application

Re: Session on Tomcat 7 manager screem

Ok I got a little more information the user On cllicking on the session number '0', he is getting the following error. Any idea? FAIL - Encountered exception org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: [18] in the generated java file:

Re: Session on Tomcat 7 manager screem

I am not sure why so aggravated you get... I am not claiming any bugs or anything and I am no expert in Tomcat 7 application server. I am at client site and they are simply asking me a question as I explained before. They have java applications deployed and creating more than one sessions of

Re: Session on Tomcat 7 manager screem

On 18/02/2016 16:45, Qadeer Khan wrote: > Can you tell what a session definition is? You are claiming there is a bug with session handling yet you don't know what a session is? Oh dear. Time for you to spend some time reading the Servlet specification. Mark > > > On 18/02/2016 16:28, Qadeer

Re: Session on Tomcat 7 manager screem

Can you tell what a session definition is? On 18/02/2016 16:28, Qadeer Khan wrote: > Hey Guys, > > Someone please throw some light as I am being asked about it several time now Then maybe try reading the responses you received to your previous post and answering the questions you were asked.

Re: Session on Tomcat 7 manager screem

On 18/02/2016 16:28, Qadeer Khan wrote: > Hey Guys, > > Someone please throw some light as I am being asked about it several time now Then maybe try reading the responses you received to your previous post and answering the questions you were asked. > There is are several running java

Session on Tomcat 7 manager screem

Hey Guys, Someone please throw some light as I am being asked about it several time now There is are several running java applications deployed and running on tomcat server 7 but the 'session' field on the Manager screen always show a '0". So there are sessions running by users but no

Re: Close_wait state

On 18.02.2016 16:50, Elias, Michael wrote: Hi - We are running tomcat version 7.0.50. Starting 2 days ago are application stopped responding to requests. Our investigation showed us that we are not closing connections. We see after 300 tcp sessions, for the tomcat PID, in CLOSE_WAIT state out

Close_wait state

Hi - We are running tomcat version 7.0.50. Starting 2 days ago are application stopped responding to requests. Our investigation showed us that we are not closing connections. We see after 300 tcp sessions, for the tomcat PID, in CLOSE_WAIT state out app stops responding. Restarting the app

Re: Cannot upgrade past Tomcat 6 due to massive memory increase

> Are you able to build Tomcat 8.0.x from source to test locally or would > you like me to provide you with a test build? Looks like building is pretty straightforward. I'll dive in and post back with my testing results. On Thu, Feb 18, 2016 at 9:11 AM Mark Thomas wrote: >

Close_wait state

Hi - We are running tomcat version 7.0.50. Starting 2 days ago are application stopped responding to requests. Our investigation showed us that we are not closing connections. We see after 300 tcp sessions, for the tomcat PID, in CLOSE_WAIT state out app stops responding. Restarting the app

Re: Cannot upgrade past Tomcat 6 due to massive memory increase

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark, On 2/18/16 10:11 AM, Mark Thomas wrote: > Another update. > > Before any fixes, my tests showed a heap of ~1GB with ~30% used by > WebappClassLoader and 50% by JarResourceSet > > The WebappClassLoader issue was triggered by JAR scanning. >

Re: Cannot upgrade past Tomcat 6 due to massive memory increase

Another update. Before any fixes, my tests showed a heap of ~1GB with ~30% used by WebappClassLoader and 50% by JarResourceSet The WebappClassLoader issue was triggered by JAR scanning. Disabling / limiting JAR scanning will reduce the impact of this issue. The issue has been fixed in 9.0.x and

Re: Cannot upgrade past Tomcat 6 due to massive memory increase

On 18/02/2016 00:26, Ty wrote: >>> For Ty's purposes, simply avoid JAR scanning entirely should eliminate >>> the heap issues, right? Moving from Tomcat 6 means that JAR scanning >>> is not required for correct operation of their application. > >> Yes.