Has anybody installed patch 1 and found that the installer hangs on the "Uncaching Deployment Units" step ? The upgrade appears to have completed successfully and the application is up and running. I saw an earlier post on a similar issue http://scn.sap.com/thread/3388134 but stopping all java processes (APSs and Tomcat) didn't make a difference. Equally the note linked cannot be implemented without taking down the server, which is a bit late when the installer is running. It looks like killing the setupengine is the only way to go, but the impacts of doing so are unknown. There's probably some incomplete commits ready to come back to bite.
The 7 pages of ADAPTs in patch 1 were being held up my sleeve in case any of the issues fixed in this patch were raised as showstoppers by our user community. So far this is not the case. Ideally I would like to avoid the patch as this extends the production outage by x hours.
Any thoughts welcome, and any suprises found in 4.1 SP2 are welcome.
Kevin.