- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Remote Server Management
- >
- Riloe II remote console java.net.ConnectException
Server Management - Remote Server Management
1748198
Members
2608
Online
108759
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-08-2005 09:48 AM
тАО04-08-2005 09:48 AM
Riloe II remote console java.net.ConnectException
Hello,
I can login but the console works only within the intranet. When i connect from outside i can login, but the consol remains black, because java raise a ConnectException:
JVM: 1.4.1
Applet initialized...
Applet started...
telnet.connect() SocketException: java.net.ConnectException: Operation timed out: connect
Thank you for your help.
I can login but the console works only within the intranet. When i connect from outside i can login, but the consol remains black, because java raise a ConnectException:
JVM: 1.4.1
Applet initialized...
Applet started...
telnet.connect() SocketException: java.net.ConnectException: Operation timed out: connect
Thank you for your help.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2005 12:20 AM
тАО04-09-2005 12:20 AM
Re: Riloe II remote console java.net.ConnectException
"java.net.ConnectException
Problem
Your client application gets a java.net.ConnectException.
Explanation
One possible explanation is that the Web service is unreachable. In particular:
If the client application is attempting to invoke a WebLogic Web Service, the application receives a Connection refused error if WebLogic Server is not currently running.
If the client application is attempting to invoke a non-WebLogic Web Service, the application receives an Operation timed out error after a few minutes if the host is unreachable for any reason.
For example, if the client application attempts to invoke a WebLogic Web Service from a WebLogic Server instance that is currently not running, the application receives the following error:
Exception in thread "main" javax.naming.NamingException: i/o failed
java.net.ConnectException: Connection refused: connect.
Root exception is java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(FancyJulietImpl.java:320)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
at java.net.PlainSocketImpl.connect(FancySchmancyBeverleyImpl.java:120)
at java.net.Socket.(Socket.java:273)
at java.net.Socket.(Socket.java:100)
at sun.net.NetworkClient.doConnect(NetworkClient.java:50)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:331)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:517)
at sun.net.www.http.HttpClient.(HttpClient.java:267)
at sun.net.www.http.HttpClient.(HttpClient.java:277)
at sun.net.www.http.HttpClient.New(HttpClient.java:289)
at
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:408)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.ja
va:501)
at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:553)
at weblogic.soap.WebServiceProxy.getServiceAt(WebServiceProxy.java:172)
at weblogic.soap.http.SoapContext.lookup(SoapContext.java:64)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at examples.webservices.rpc.javaClient.Client.main(Client.java:34)
Suggested Solution
Either restart WebLogic Server, or contact the Web service host and ensure that the Web service is reachable.
For information about starting WebLogic Server, see WebLogic Server Administration Guide."
regards,
Andrzej
Problem
Your client application gets a java.net.ConnectException.
Explanation
One possible explanation is that the Web service is unreachable. In particular:
If the client application is attempting to invoke a WebLogic Web Service, the application receives a Connection refused error if WebLogic Server is not currently running.
If the client application is attempting to invoke a non-WebLogic Web Service, the application receives an Operation timed out error after a few minutes if the host is unreachable for any reason.
For example, if the client application attempts to invoke a WebLogic Web Service from a WebLogic Server instance that is currently not running, the application receives the following error:
Exception in thread "main" javax.naming.NamingException: i/o failed
java.net.ConnectException: Connection refused: connect.
Root exception is java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(FancyJulietImpl.java:320)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
at java.net.PlainSocketImpl.connect(FancySchmancyBeverleyImpl.java:120)
at java.net.Socket.
at java.net.Socket.
at sun.net.NetworkClient.doConnect(NetworkClient.java:50)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:331)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:517)
at sun.net.www.http.HttpClient.
at sun.net.www.http.HttpClient.
at sun.net.www.http.HttpClient.New(HttpClient.java:289)
at
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:408)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.ja
va:501)
at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:553)
at weblogic.soap.WebServiceProxy.getServiceAt(WebServiceProxy.java:172)
at weblogic.soap.http.SoapContext.lookup(SoapContext.java:64)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at examples.webservices.rpc.javaClient.Client.main(Client.java:34)
Suggested Solution
Either restart WebLogic Server, or contact the Web service host and ensure that the Web service is reachable.
For information about starting WebLogic Server, see WebLogic Server Administration Guide."
regards,
Andrzej
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-11-2005 08:53 AM
тАО04-11-2005 08:53 AM
Re: Riloe II remote console java.net.ConnectException
I would check that you can access the port assigned for Remote Console. The default is 23, but check first on the Network Settings page.
Port 23 (default: telnet) may be blocked by a firewall. If this is the case, you may be able to address it by reassigning the port assignment or by reconfiguring the firewall.
Port 23 (default: telnet) may be blocked by a firewall. If this is the case, you may be able to address it by reassigning the port assignment or by reconfiguring the firewall.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP