- This topic has 5 replies, 3 voices, and was last updated 20 years, 3 months ago by
.
-
Posts
-
I am trying to run Weblogic portal through MyEclipse. Adding the right libraries to the classpath, I’ve gotten it to start correctly; the console output looks just like it does when starting it outside MyEclipse. However, when I try to access my application from a browser, it doesn’t connect. Also, trying to stop Weblogic from the Eclipse menu gives me the following error message:
Failed to connect to t3://localhost:7501 due to:[javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7501: Destination unreachable; nested exception is:
java.io.InterruptedIOException: Read timed out; No available router to destination]]Thanks,
TedTed,
That’s peculiar. Can you connect using the same string if you start portal from the command line? Can you connect as t3://127.0.0.1:7501? Are you positive 7501 is the correct port? Can you connect using the WebLogic console? Can you post the answers to these and all the questions we ask in the ‘Posting Guidelines’ thread so we have some context from which we can look into it? Thanks.
Hi,
Sorry it took me so long to reply. I still am unable to connect to WebLogic when it is started through myEclipse. I can connect when WebLogic is started from the command line. I cannot connect using 127.0.0.1, nor can I connect to the WebLogic console. The console output confirms that the server is listening on port 7501.
OS – Win 2000 build 2195 SP4
Eclipse version 3.0.0 – freshly installed
8 plug-ins of type …pde…
myEclipse: Build id: 200407091200-3.8-Beta2
eclipse jdk 1.4.2
appserver jdk 1.3.1
No errors in Eclipse logCan you try telnetting into port 7501 when running from command line and when running from MyEclipse?
Turns out this inablity to connect was caused by an out of memory error. I didn’t put the right memory arguments on the WebLogic command line in the WebLogic connector configuration.
Thanks,
Ted
