update connection proxy and tomcat
I upgraded tomcat on my solaris 10 system from v4 to v5 in order to support an OEM application.
Since then the update connection proxy which runs on the same platform is failing.
When I start update manager which is setup to use update connection proxy to get to sun , I'm getting following errors on my telnet session :
com.sun.swup.client.engine.solaris.CollectionFileException: Error: Unable to download document : "collection/default"
Cannot connect to retrieve collection/default: Connection refused
at com.sun.swup.client.engine.solaris.PatchCollection.processCollections(PatchColl ection.java:91)
at com.sun.swup.client.engine.solaris.PatchCollection.<init>(PatchCollection .java:53)
at com.sun.swup.client.engine.solaris.PatchCollection.getInstance(PatchCollection. java:70)
at com.sun.swup.client.engine.solaris.SolarisDataCollector.getCollectionsObject(So larisDataCollector.java:392)
at com.sun.swup.client.engine.solaris.SolarisDataCollector.getAvailableCollectionN ames(SolarisDataCollector.java:279)
at com.sun.swup.client.engine.solaris.SolarisDataCollector.getAvailableUpdateColle ctions(SolarisDataCollector.java:158)
at com.sun.swup.client.ui.UpdateFrame$LoadDataWorker.construct(UpdateFrame.java:23 4)
at com.sun.swup.client.ui.foundation.swing.SwingWorker$2.run(SwingWorker.java:109)
at java.lang.Thread.run(Thread.java:595)
and a pop-up window with error message :
Error: Unable to download document: "collection/default" Cannot connect to retrieve collection./default: Connection refused
Question : Is this really related to my tomcat upgrade ? and any idea on how to get around this ?
Thanks
[1731 byte] By [
forum_dev] at [2007-11-26 6:02:43]
# 1
It's not entirely clear from your message whether you are running the Sun Update Connection Proxy on a different system than you are running the Update Manager, and if they are two different machines, which is the one that had the upgrade. I'll assume that the machine that had the Tomcat upgrade was the one running the Sun Update Connection Proxy in the remainder of this reply.
Since the Sun Update Connection Proxy runs a Tomcat instance, it is quite possible that the Tomcat upgrade did cause a problem. You should be able to see the Sun Update Connection Proxy logs at /var/patchsvr/logs, the output in the logs when you attempt to download will be informative for this issue.
Please note that the Sun Update Connection Proxy must be registered using the registration wizard in the Update Manager in order to retrieve patches from Sun, and this could be the source of your issue.
You can also view the configuration of the Sun Update Connnection proxy with the command patchsvr setup -l.
I hope that some of this information will be useful for you in further troubleshooting your issue.
-ethan
# 2
Update manager and sun update connection proxy are both running on the same system.
contents of the logs is not meaningful for a non java expert !!.
What I endup doing ( and I do agree it is not the best approach but it works ) is to tar from a solaris 10 system with tomcat v4 /usr/apache/tomcat , restore that on my system running tomcat v5 as /usr/apache/TOMCAT , then I changed /usr/sbin/patchsvr , replacing
CATALINA_HOME=/usr/apache/tomcat by
CATALINA_HOME=/usr/apache/TOMCAT
now patchsvr can be started and my sun update connection proxy works.
Basicaly I'm running a tomcat v4 and tomcat v5 now.
I would guess that the issue would be to update the tomcat v4 definitions of sun update connection procy to tomcat v5 , I would expect some support from sun form this !!
