- This topic has 22 replies, 8 voices, and was last updated 18 years, 5 months ago by
.
-
Posts
-
plynn,
Thank you for the info, all your versions look great.If you had a chance later today, would you be able to install JDK 1.5.0_06 (just released) and then add a new JDK setup for it and set it as your JDK for your Tomcat 5 connector and see if it works?
We have been unable to determine yet what causes this issue, it doesn’t seem to be tied to any of the software you’d think it would be (eclipse/myeclipse/jdk) but it’s possible another plugin or application on the host machine could be the variable in this equation.
rkalla,
I tried your suggestion and when I used jdk 1.5.0_06 as the jdk for Tomcat, it starts up successfully.Hi, I have had the same problem.
Solution is: Check your firewall setting. You have probably disabled communication for Java.Had this same problem with 5.1GA (all-inclusive) and WL 8.1.6
My solution was to fix JAVA_HOME (or perhaps you might need to *set* it).
I simply pointed at the WL-shipped JDK.It was previously pointing to a 1.5 JRE — I’m sure you see a lot of red flags there and I’m not sure which one was the culprit, but I’m guessing it has everything to do with the socket library.
I also prefixed my PATH with %JAVA_HOME%\bin, but I don’t think that’s relevant.
I’m seeing a similar problem, I’m running windows XP and I installed JRE 1.6. After the install i placed the following into my path enviorment variable “C:\Program Files\Java\jdk1.6.0\bin;C:\Program Files\Java\jdk1.6.0\jre\bin;” which replaced this “C:\j2sdk1.4.2_12\bin;C:\j2sdk1.4.2_12\jre\bin”. When I did that I was seeing the same Transport dt_socket failed problem. It worked again when I switched it back. I didn’t change anything relating to eclipse, the only difference was the path enviorment variable.
