- This topic has 4 replies, 2 voices, and was last updated 18 years, 4 months ago by
.
-
Posts
-
I have used Trial subscription for 1 month, and used Debugging succssfully, However When I bought Standard Version for $31+ dollars, it stopped working and throwing errors while starting (Debug) Weblogic Server from MyEclipse:
Errors:
A Configuration error occured during startup. Please verify the preference field with the prompt. Transport dt_socket failed to initialize, rc=509.Please responde immediately, I am struckup. I just bought it today.
Sri
Sri,
This problem can be caused by a myriad of problems. It’s essentially an error that the debugger couldn’t connect to the process. The solution is usually that you have configured your app server to run with the wrong JDK. Check your connector settings for weblogic under Window > Prefs > MyEclipse > App server > WebLogic (version) > JDK and make sure you are using the JDK that came with weblogic (is installed under the weblogic directory) to try and run WebLogic with.I have also seen folks say that the Windows firewall can cause this problem because the debugger uses standard TCP/IP connections.
rkalla,
Please note my point that it is an existing setup.
I have used the same setup previously using Trial version of MyEclipse.Today I bought the license, to my unfortunate, it started throwing these type of errors.
I am very much sure that it is pointing to correct JDK that came up with weblogic.
After I bought th license, I have not disturbed the existing configuration.
Please help me to narrow down the issue and make it working.
Sri
rkalla,
After trying to start the weblogic server in “Run” mode, I have started to start the weblogic in “Debug” mode, No Problems.
However it would be nice to display the correct OR detailed error message when some problem occurs which depends on myriad causes.
Thanks
SriSri,
Is the server working now in debug mode?I agree it would have been nice to list the possible causes of the problem, but unfortunately it seems to be different every time (in this case it was the connector mode), in other cases it’s the firewall, in others the JDK, in others the version of app server users, and in others spyware utilities have caused it. It’s very confusing to troubleshoot sometimes.
