RE: FW: Tomcat 6.0.45 - Problem in creating the socket.

2016-06-12 Thread Radha Krishna Meduri -X (radmedur - HCL TECHNOLOGIES LIMITED at Cisco)
Thanks Felix for your reply. Yes the connect has defined properly. Above SSL Implementation is custom implantation based on NSS/JSS. As I said same implementation works fine with 6.0.37. Thanks Radhakrishna -Original Message- From: Felix Schumacher [mailto:felix.schumac...@internetall

Re: FW: Tomcat 6.0.45 - Problem in creating the socket.

2016-06-12 Thread Felix Schumacher
Am 13. Juni 2016 07:25:54 MESZ, schrieb "Radha Krishna Meduri -X (radmedur - HCL TECHNOLOGIES LIMITED at Cisco)" : >Anyone can help on this? Could you explain a bit more, how you configured the connector/ssl implementation? Perhaps post a snippet of the server.xml, or where you got the nss/js

FW: Tomcat 6.0.45 - Problem in creating the socket.

2016-06-12 Thread Radha Krishna Meduri -X (radmedur - HCL TECHNOLOGIES LIMITED at Cisco)
Anyone can help on this? -Original Message- From: Radha Krishna Meduri -X (radmedur - HCL TECHNOLOGIES LIMITED at Cisco) Sent: Friday, June 10, 2016 7:12 PM To: users@tomcat.apache.org Subject: Tomcat 6.0.45 - Problem in creating the socket. Hi, We are trying to upgrade to 6.0.45 from 6.

Re: Updating Apache Tomcat to a current version

2016-06-12 Thread Daniel Savard
2016-06-12 19:32 GMT-04:00 paul.greene.va : > > A couple of quick questions - when you drop the WAR file into the webapps > directory, does tomcat automatically expand the contents of the file? And > is the WAR file format a typical way for vendors to distribute their apps > to their customers, or

RE: Updating Apache Tomcat to a current version

2016-06-12 Thread Caldarale, Charles R
> From: paul.greene.va [mailto:paul.greene...@verizon.net] > Subject: Re: Updating Apache Tomcat to a current version > when you drop the WAR file into the webapps directory, does tomcat > automatically > expand the contents of the file? Depends on how you have configured Tomcat; look at the u

Re: Updating Apache Tomcat to a current version

2016-06-12 Thread paul.greene.va
On 6/12/2016 4:28 PM, Daniel Savard wrote: Paul, you do not upgrade Tomcat code, you install a second instance of Tomcat or you delete the existing Tomcat and install the new version. Service Manager is pretty straight forward to install. Here are the setups: 1) Install Tomcat 7.0.69 2) Confi

Re: Updating Apache Tomcat to a current version

2016-06-12 Thread Daniel Savard
2016-06-12 15:10 GMT-04:00 paul.greene.va : > > Daniel - sorry, this was probably confusing. What I did was install Tomcat > 7.0.53 at *home* on a virtual server - there was nothing else installed on > this virtual machine - no Service Manager, no apps, nothing else. I just > wanted to see what hap

Re: Updating Apache Tomcat to a current version

2016-06-12 Thread paul.greene.va
On 6/12/2016 11:29 AM, Daniel Savard wrote: 2016-06-12 9:20 GMT-04:00 paul.greene.va : I got copies of both 7.0.53 and 7.0.69 off the Tomcat website, and installed .53 first on a vmware vm, then tried running .69 over it to see if it was just an easy upgrade, but it looks like Tomcat doesn't

Re: Updating Apache Tomcat to a current version

2016-06-12 Thread Daniel Savard
2016-06-12 9:20 GMT-04:00 paul.greene.va : > > I got copies of both 7.0.53 and 7.0.69 off the Tomcat website, and > installed .53 first on a vmware vm, then tried running .69 over it to see > if it was just an easy upgrade, but it looks like Tomcat doesn't make the > upgrade that easy. > > It is u

Re: Updating Apache Tomcat to a current version

2016-06-12 Thread Olaf Kock
Am 12.06.2016 um 15:20 schrieb paul.greene.va: > Thank you. I wasn't involved at all in the previous upgrade or the > original installation of Tomcat and/or HP Service Manager. Based on this information, I'd install a vanilla version of 7.0 53 next to your currently installed application that us

Re: Updating Apache Tomcat to a current version

2016-06-12 Thread paul.greene.va
On 6/11/2016 11:08 PM, Daniel Savard wrote: 2016-06-10 15:09 GMT-04:00 paul.greene.va : Actually, I don't want to have parallel versions going; 7.0.53 needs to go away to address the vulnerabilities found in the audit scan. Ideally everything should be the same as it is now, with the only dif