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

[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/jss?

Thanks, 
Felix

>
>-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.0.37.
>Tomcat starting fine, but while creating the socket we are getting
>following exception.
>
>For SSL implementation, we are using NSS/JSS from Mozilla.
>The SSL implementation works fine with 6.037, but failing with 45.
>Do you have any idea whether we have to modify SSL implementation to
>reflect new Tomcat changes?
>
>org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler process
>SEVERE: Error reading request, ignored
>java.lang.ClassCastException:
>com.sun.net.ssl.internal.ssl.SSLSocketImpl cannot be cast to
>org.mozilla.jss.ssl.SSLSocket
>at
>org.apache.tomcat.util.net.jsse.XXXSSLImplementation.getSSLSupport(XXXSSLImplementation.java:51)
>at
>org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606)
>at
>org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:504)
>at java.lang.Thread.run(Unknown Source)
>
>Thanks
>Radhakrishna
>
>-
>To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

FW: Tomcat 6.0.45 - Problem in creating the socket.

[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.0.37.
Tomcat starting fine, but while creating the socket we are getting following 
exception.

For SSL implementation, we are using NSS/JSS from Mozilla.
The SSL implementation works fine with 6.037, but failing with 45.
Do you have any idea whether we have to modify SSL implementation to reflect 
new Tomcat changes?

org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler process
SEVERE: Error reading request, ignored
java.lang.ClassCastException: com.sun.net.ssl.internal.ssl.SSLSocketImpl cannot 
be cast to org.mozilla.jss.ssl.SSLSocket
at 
org.apache.tomcat.util.net.jsse.XXXSSLImplementation.getSSLSupport(XXXSSLImplementation.java:51)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606)
at 
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:504)
at java.lang.Thread.run(Unknown Source)

Thanks
Radhakrishna

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Updating Apache Tomcat to a current version

[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 is it normally a customer created file?
>
>
Hi Paul,

I assumed your previous configuration or the reference configuration is
doing so. Then, if you replicate the configuration it should do the same.

Regards,
-
Daniel Savard

RE: Updating Apache Tomcat to a current version

[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 unpackWARs description:
http://tomcat.apache.org/tomcat-7.0-doc/config/host.html#Standard_Implementation

> And is the WAR file format a typical way for vendors to distribute their apps 
> to 
> their customers, or is it normally a customer created file?

Usually in a .war file.  This is actually a .jar file with a specific directory 
structure as defined by the servlet spec (which would be useful to at least 
skim over):
http://jcp.org/aboutJava/communityprocess/final/jsr315/index.html

 - 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.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Updating Apache Tomcat to a current version

[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) Configure conf/server.xml (TLS/SSL stuff, Connector, etc)
3) Start Tomcat
4) Drop the war file in webapps
5) Edit webapps/sm/WEB-INF/web.xml to reflect your installation (SM server,
etc) after the war has been installed into its directory

You are done. Check in logs/catalina.out for error messages.

There is variants in the installation. This one seems to me the simplest on
given you are telling us the war file is actually in the webapps folder.

I am a bit surprised you were told to upgrade to Tomcat 7.0.69, which
version of SM are you running on the server? We still have SM running with
Java 6 and Tomcat 6.0.24 in production with SM 9.34. We are upgrading to SM
9.41, Tomcat 8 and Java 8. So far, SM is running smoothly in all our
environments. Usually HP support whatever version of Tomcat you have,
provided it meets the minimum requirements or unless a specific bug exists
in your Tomcat version.

Regards,
-
Daniel Savard



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 is it normally a customer created file?


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Updating Apache Tomcat to a current version

[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 happened when I went to install 7.0.69 over the top of
> .53; i.e. would there just be a simple "upgrade" option or not. There
> wasn't an option to "upgrade" and the install choked at one point when it
> realized there was another tomcat.exe process running and it couldn't
> overwrite the file.
>
> The server I need to upgrade at *work* is a perfectly functioning instance
> of Service Manager. It is working fine with no issues at the moment. I
> haven't touched anything on this server yet.
>
> It sounds like, from what you've said, the standard way to deploy an app
> in tomcat is via a WAR file getting dropped in the webapps directory. There
> is a sm.war file in the root of ..\webapps; if I copied that file into the
> new tomcat install webapps directory, would that install the app correctly?
> Or does a new *.war file need to be generated with a new version of tomcat?
> Service Manager itself isn't getting upgraded at this time, so if that was
> the same war file used in the last upgrade (they went from 9.33 to 9.40),
> shouldn't it work in this one too?
>
>
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) Configure conf/server.xml (TLS/SSL stuff, Connector, etc)
3) Start Tomcat
4) Drop the war file in webapps
5) Edit webapps/sm/WEB-INF/web.xml to reflect your installation (SM server,
etc) after the war has been installed into its directory

You are done. Check in logs/catalina.out for error messages.

There is variants in the installation. This one seems to me the simplest on
given you are telling us the war file is actually in the webapps folder.

I am a bit surprised you were told to upgrade to Tomcat 7.0.69, which
version of SM are you running on the server? We still have SM running with
Java 6 and Tomcat 6.0.24 in production with SM 9.34. We are upgrading to SM
9.41, Tomcat 8 and Java 8. So far, SM is running smoothly in all our
environments. Usually HP support whatever version of Tomcat you have,
provided it meets the minimum requirements or unless a specific bug exists
in your Tomcat version.

Regards,
-
Daniel Savard

Re: Updating Apache Tomcat to a current version

[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 make the
upgrade that easy.



It is unclear here if you have the HP application installed or not on
7.0.53 in you VM. If you don't, it is pointless to backup any content. The
idea of the backup is to keep a copy of the working configuration for
reference.


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 happened when I went to install 7.0.69 
over the top of .53; i.e. would there just be a simple "upgrade" option 
or not. There wasn't an option to "upgrade" and the install choked at 
one point when it realized there was another tomcat.exe process running 
and it couldn't overwrite the file.


The server I need to upgrade at *work* is a perfectly functioning 
instance of Service Manager. It is working fine with no issues at the 
moment. I haven't touched anything on this server yet.


It sounds like, from what you've said, the standard way to deploy an app 
in tomcat is via a WAR file getting dropped in the webapps directory. 
There is a sm.war file in the root of ..\webapps; if I copied that file 
into the new tomcat install webapps directory, would that install the 
app correctly? Or does a new *.war file need to be generated with a new 
version of tomcat? Service Manager itself isn't getting upgraded at this 
time, so if that was the same war file used in the last upgrade (they 
went from 9.33 to 9.40), shouldn't it work in this one too?


The fall back is that the work servers are running in vmware - so I can 
take a snapshot before starting and roll back if anything goes south.


Thanks again in advance.

Paul




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Updating Apache Tomcat to a current version

[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 unclear here if you have the HP application installed or not on
7.0.53 in you VM. If you don't, it is pointless to backup any content. The
idea of the backup is to keep a copy of the working configuration for
reference.


> So, if I understand your suggestions correctly, would the following plan
> of action work -
>
> Make a backup of everything under C:\Program Files\Apache Software
> Foundation\Tomcat 7.0\, in particular conf and webapps
> Remove the current version of Tomcat (.53)
> Install most recent version (.69)
> Copy the contents of the conf and webapps folder back to the new install
>
>
No, don't blindly copy contents. You can copy the WAR file in the webapps
folder. But you shouldn't just copy over the conf content. Usually, only
the server.xml is modified and you must look at the actual content and
adapt to your particular needs. The old copy being a reference provided it
is not just a vanilla copy.


> There is a *.keystore file and a keystore.jks files in the root of
> C:\Program Files\Apache Software Foundation\Tomcat 7.0\ - I'm guessing they
> are probably needed as well to get SSL working correctly (?)
>
>
If you have SSL enabled you should look into the server.xml for the files
you need to keep. You can relocate them provided you update the location in
the server.xml.


> Should that do the trick?
>
>
You must understand what you are doing. You cannot just blindly copy
everything and expect it to work. Usually, the Tomcat configuration is in
conf/server.xml and the web application configuration is in
webapps/whatever_name/WEB-INF/web.xml. However, with HP you may also have
other files in WEB-INF to edit to configure the application properly.


> (I'm not familiar with WAR files - is that the normal way to install new
> apps into Tomcat?)
>

WAR is the standard to distribute web applications.

Regards,
-
Daniel Savard

Re: Updating Apache Tomcat to a current version

[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 uses the same version. Then
run a diff to figure out what kinds of settings have been changed during
the previous installations. Identify them, document them (so that you
have this documentation next time).

Don't forget to backup /everything/, especially as you seem to not have
too much experience with this environment. Be aware that I typically
only allow someone to name a bunch of file "backup" if they've
demonstrated that they can /recover/ from that set of files to a
completely new environment. This might be a bit too much for the task at
hand, but it's better to be safe than sorry.

Most likely there will be new files and directories in webapps/* and
lib/*, as well as changed files in conf/*.

Tomcat is most likely installed as a service on your windows machine.
Depending on how this has been done, there might be more work for you to
do than just replace some files. You should make yourself familiar with
the steps to install tomcat as a service if it already is on your machine.

In general, upgrading tomcat, especially within the same major version
/theoretically/ is as simple as dropping in the new version - however,
as files /might/ have changed names, it really makes sense to install to
a new location (as Daniel has suggested). This way you can compare both
installations and their plain vanilla installs (without your own
application). Once the new version is running successfully, you can
always get rid of the old one - until then you'll have it unchanged.

With regards to the keystore: If you're referencing this, it probably
doesn't need to be updated (that will be required once the current
certificate runs out). You can typically just continue to use the same
one from the upgraded version

Olaf


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Updating Apache Tomcat to a current version

[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 difference being
the app is using 7.0.69 rather than 7.0.53.


Hi Paul,

What I would do, is keep a copy of the files in conf directory/folder of
your old Tomcat instance as well as a copy of the files in webapps (I
suppose you have drop the war file into that directory/folder). You then
have a copy of all the files you need in case something went wrong or you
need to configure something you don't remember.

Then I would install the new Tomcat version. Configure the server.xml (I
suppose you did previously for the old version and know how to modify it to
reflect your particular needs) and then drop the war file in the new
wepapps directory if this is how you installed the old version of the HP
application. I suppose you have some kind of instructions from HP on how to
install their application. It is just like you install a brand new Tomcat.
The important part is to keep a copy of the old stuff in case you need to
refer to your previous settings.

Regards,
Daniel



Daniel

Thank you. I wasn't involved at all in the previous upgrade or the 
original installation of Tomcat and/or HP Service Manager.


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.


So, if I understand your suggestions correctly, would the following plan 
of action work -


Make a backup of everything under C:\Program Files\Apache Software 
Foundation\Tomcat 7.0\, in particular conf and webapps

Remove the current version of Tomcat (.53)
Install most recent version (.69)
Copy the contents of the conf and webapps folder back to the new install

There is a *.keystore file and a keystore.jks files in the root of 
C:\Program Files\Apache Software Foundation\Tomcat 7.0\ - I'm guessing 
they are probably needed as well to get SSL working correctly (?)


Should that do the trick?

(I'm not familiar with WAR files - is that the normal way to install new 
apps into Tomcat?)


Paul




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org