- This topic has 6 replies, 3 voices, and was last updated 20 years, 1 month ago by
.
-
Posts
-
Been developing on Weblogic 8.1 for a couple of months. Never had a problem starting or stopping from the windows start menu. Just loaded MyEclipse and configured Weblogic 8.1. I can successfully start WLS from the Eclipse menu bar (Run/stop servers), but cannot stop the server. I get the following error:
Failed to connect to t3://localhost:243: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destinationSpecifics:
Eclipse 3.0
MyEclipse 3.8.3
WLS8.1
Using https on WLSI tried substituting :7001 for :243; I tried my local machine name vice localhost. No dice!
I verified that the server has not stopped, since I can still browse to it. Any help would be greatly appreciated!
Jonathon
Using https on WLS
This might be the cause. Also, have you tried 127.0.0.1? Are you really running WLS on port 243 and not 7001, which is the default? From the error, it appears that your machine doesn’t know what “localhost” is, which is peculiar, at best.
@support-scott wrote:
Using https on WLS
This might be the cause. Also, have you tried 127.0.0.1? Are you really running WLS on port 243 and not 7001, which is the default? From the error, it appears that your machine doesn’t know what “localhost” is, which is peculiar, at best.
Scott,
Trying 127.0.0.1 did not make the system work differently. I changed the SSL port to 443 and verified in a web browser and the WebLogic console that the server is running on that port. After starting the WLS from Eclipse, I can browse to the TraderX application (using https vice http) and can browse the j2ee application I have been working on (using https).
When I try to close the application from the menu: Run/Stop Servers (icon) / WebLogic 8 / Stop, the console reads:
Failed to connect to t3://localhost:443: Destination unreachable; nested exception is:
java.io.IOException: Empty server reply; No available router to destinationAnd I am still able to browse using Mozilla to https://localhost/<valid path to application>
Exiting from Eclipse is the only way I have figured out how to shut down WLS if started from Eclipse.
Please help. Jonathon
Jonathon,
I believe the error is trying to stop the server via t3 on the SSL port. I don’t believe the two are compatabile. The shutdown command should be issued against the http port, 7001, only. I just reverified with a local install on 3.8.3 with the host:port set to localhost:7001 and it shutdown normally. Have you made changes to your weblogic config files externally? Do you have the same behavior on a “new” domain, created by the WLS domain creation tools?
@support-scott wrote:
Jonathon,
I believe the error is trying to stop the server via t3 on the SSL port. I don’t believe the two are compatabile. The shutdown command should be issued against the http port, 7001, only. I just reverified with a local install on 3.8.3 with the host:port set to localhost:7001 and it shutdown normally. Have you made changes to your weblogic config files externally? Do you have the same behavior on a “new” domain, created by the WLS domain creation tools?
I created a new domain on WLS and modified the server preferences with the correct location and port number. I can even start and stop the server from MyEclipse. Unfortunately I cannot deploy the TraderX application (which worked fine before using SSL) Despite Weblogic 8 being accessible from the start/stop icon, it is not available from the deployment icon. Selecting custom or remote does not work either. It reports that it has been “deployed”, browsing to http://localhost:7001/TraderWeb/html/welcome.html returns a 404. Did I forget something?
Jonathon
Now I can start stop and deploy on the new domain I created. The problem was that I never undeployed the project from the https domain. I don’t see why I was being prevented from deploying an application to multiple domains, but there you go.
Still scratching my head over why https will not work. Is there an on-line reference or previous post that discusses this? All of my applications need to be https, I’d love to work and test like I’ll have to deploy.
Jonathon
