Re: RE: Re: Tomcat 5.5.17 migration to 6
Alright. I guess the thought the process was to upgrade to 6, then 7, 8 Thanks, David On Sat, Jul 14, 2018 at 3:38 PM -0400, "Caldarale, Charles R" mailto:chuck.caldar...@unisys.com>> wrote: > From: David Babooram [mailto:david.baboo...@digicelgroup.com] > Subject: Re: Re: Tomcat 5.5.17 migration to 6 > But by decision was based on what was presented in the Apache site. In that, upgrade from > 5.5 was known to only go to 6. Seriously, don't even think about "upgrading" to another very dead level. There haven't been updates to Tomcat 6 for over a year; subsequent fixes for known security holes and other issues have been applied to current levels, but none of those will ever be retrofitted to Tomcat 6 (and 7, in the not too distant future). 8.5 or 9.0 are the only sensible choices. > Nevertheless.. is there some official documents on migrating to 8.5? Due to the age of where you're starting from (over 12 years old), you're not going to find anything specific for that level to a current one. What you can do is read all of the Migration Guides linked from here: http://tomcat.apache.org/migration.html and get a sense of the changes needed for your webapp configurations. You may well need to update JVM versions as well; if the one you're using is also 12 years old, it's scary dangerous. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. Notice of Confidentiality: The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system.
RE: Tomcat JDBC Pool memory leak when using StatementFinalizer interceptor
> From: Felix Schumacher [mailto:felix.schumac...@internetallee.de] > Subject: Re: Tomcat JDBC Pool memory leak when using StatementFinalizer interceptor > Am 11.07.2018 um 16:22 schrieb Martin Knoblauch: > > Now it might be, that we are just using the StatementFinalizer in a wrong > > manner. And what we see is expected behavior. Below is our pool > > configuration. Maybe something is just missing :-) > The docs in the interceptor says one has to call close on the > connection, that the statements created. Does your application call > close on the connection? This section of the doc includes a decent model that your webapp code should be following: http://tomcat.apache.org/tomcat-8.0-doc/jndi-datasource-examples-howto.html# Random_Connection_Closed_Exceptions Proper use of a finally block is critical. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. smime.p7s Description: S/MIME cryptographic signature
RE: Re: Tomcat 5.5.17 migration to 6
> From: David Babooram [mailto:david.baboo...@digicelgroup.com] > Subject: Re: Re: Tomcat 5.5.17 migration to 6 > But by decision was based on what was presented in the Apache site. In that, upgrade from > 5.5 was known to only go to 6. Seriously, don't even think about "upgrading" to another very dead level. There haven't been updates to Tomcat 6 for over a year; subsequent fixes for known security holes and other issues have been applied to current levels, but none of those will ever be retrofitted to Tomcat 6 (and 7, in the not too distant future). 8.5 or 9.0 are the only sensible choices. > Nevertheless.. is there some official documents on migrating to 8.5? Due to the age of where you're starting from (over 12 years old), you're not going to find anything specific for that level to a current one. What you can do is read all of the Migration Guides linked from here: http://tomcat.apache.org/migration.html and get a sense of the changes needed for your webapp configurations. You may well need to update JVM versions as well; if the one you're using is also 12 years old, it's scary dangerous. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. smime.p7s Description: S/MIME cryptographic signature
Re: Re: Tomcat 5.5.17 migration to 6
Hi Good point. But by decision was based on what was presented in the Apache site. In that, upgrade from 5.5 was known to only go to 6. Nevertheless.. is there some official documents on migrating to 8.5? Thanks, David On Sat, Jul 14, 2018 at 11:05 AM -0400, "calder" mailto:calder@gmail.com>> wrote: Why migrate to a version that is EOL (no doubt why you can't find docs) ? https://urldefense.proofpoint.com/v2/url?u=https-3A__tomcat.apache.org_tomcat-2D60-2Deol.html=DwIBaQ=rgYoxYEBLrFNu7L2jzNzTw=MW5XW3Oy92ra15dUPR3jKJRFG4SYwI8WcMv_vsnkhI8=BBOP12O2WPzudlhwCFnUC4e0DvDT_OfVbr1ORuU60EU=Ph5R4aW_MIkR03OtVE8KeF2sTCSJjI25o_HEqjp2r5k= If I were in the situation, I'd migrate to a more modern version, such as 8.5 On Saturday, July 14, 2018, David Babooram wrote: > Good morning > > My intent is to migrate from 5.5.17 to 6 with the intent to upgrade to > 6.0.48. , mainly due to a vulnerability notice. > > I understand the changes listed from the Apache site wrt the migration. > but I have not gotten any steps on how to proceed. > > Is there any proper documentation on how to proceed > Notice of Confidentiality: The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system.
Re: Tomcat JDBC Pool memory leak when using StatementFinalizer interceptor
Am 11.07.2018 um 16:22 schrieb Martin Knoblauch: Hi, while analyzing some heap dump for other reasons, I found that our application is apparently aggregating a considerable amount of memory in "org.apache.tomcat.jdbc.pool.TrapException", which is never cleaned by GC. Digging deeper, it seems that the entries of the "statements" linked list in the StatementFinalizer are never removed from the list, so after three weeks of lifetime one ends up with a list of 7 million entries, each 80 bytes. Now it might be, that we are just using the StatementFinalizer in a wrong manner. And what we see is expected behavior. Below is our pool configuration. Maybe something is just missing :-) The docs in the interceptor says one has to call close on the connection, that the statements created. Does your application call close on the connection? Regards, Felix We are at Tomcat 8.0.36 (yeah, I know, but that is the version we have to use) and Java 8 (1.8.0_171). Underlying DB is Oracle 12.1.0.2 and we are using the latest "ojdbc7.jar" from Oracle. Thanks Martin - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 5.5.17 migration to 6
Why migrate to a version that is EOL (no doubt why you can't find docs) ? https://tomcat.apache.org/tomcat-60-eol.html If I were in the situation, I'd migrate to a more modern version, such as 8.5 On Saturday, July 14, 2018, David Babooram wrote: > Good morning > > My intent is to migrate from 5.5.17 to 6 with the intent to upgrade to > 6.0.48. , mainly due to a vulnerability notice. > > I understand the changes listed from the Apache site wrt the migration. > but I have not gotten any steps on how to proceed. > > Is there any proper documentation on how to proceed >
Re: Can not use multiple war files on single port.
On Sat, Jul 14, 2018 at 1:54 AM, Muhammad Rasul Bobonazarov <19mra...@gmail.com> wrote: > I can not run multiple war files on tomcat webapps. All war files are > unpacking, but they are not running except the last I placed So what do your log files show? -- Hassan Schroeder hassan.schroe...@gmail.com twitter: @hassan Consulting Availability : Silicon Valley or remote - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 5.5.17 migration to 6
Good morning My intent is to migrate from 5.5.17 to 6 with the intent to upgrade to 6.0.48. , mainly due to a vulnerability notice. I understand the changes listed from the Apache site wrt the migration. but I have not gotten any steps on how to proceed. Is there any proper documentation on how to proceed with this migration? Thanks, David Notice of Confidentiality: The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system.
Can not use multiple war files on single port.
Hello everyone. I can not run multiple war files on tomcat webapps. All war files are unpacking, but they are not running except the last I placed For example, if there are 3 war files test1, test2 test3, only test3 is working and the others not working. if I remove test3 and restart tomcat server test2 is working now and test1 not. I tried in on different tomcat versions - 8, 8.5, 9.. I used tomcat before and at that time there was not such problem. Thank you in advance for your answer. Abdurasul
