From: SourceForge.net <no...@so...> - 2007-12-31 14:54:49
|
Bugs item #1113342, was opened at 2005-01-31 19:05 Message generated for change (Settings changed) made by eelco12 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=682377&aid=1113342&group_id=118870 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: JRE source attachment breaks SSL Initial Comment: A strangest bug: Setting source attachment for the JRE System Library rt.jar seems to break HTTPS/SSL. I use a custom jetty.xml which is basically similar to what is described in http://www.behindthesite. com/blog/C1931765677/E691537542/. Everything worked fine (for weeks) until I set the source attachment for the rt.jar to an external file. I spent a day trying to find out what broke the HTTPS/SSL connection and tried even discarding the source attachment. Restarting the app, Eclipse or rebooting the machine didn't have any effect. HTTPS/SSL started working only after I changed the JRE used from Window/Preferences/Java/Installed JREs. Basic HTTP has been working fine the whole time. I verified this behaviour a couple of times. I use JettyLauncher 1.2.1, Jetty 4.2.21 (tried also 5. 1.2, but it didn't work), Eclipse 3.0.1, Spindle 3.1.15, Tapestry 3.0.1, Java 1.5.0_01 on a Windows XP. Regards Samppa (sam...@he...) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=682377&aid=1113342&group_id=118870 |