（图文）解决重启VCSA 6.0提示：503 Service Unavailable错误_虚拟人_传送门
你是真实用户吗(Are you a robot)?
我们怀疑你不是真实用户，已对你的访问做了限制。如果您是真实用户，非常抱歉我们的误判对您造成的影响，您可以通过QQ()或电子邮件()反馈给我们，并在邮件和QQ请求信息里注明您的IP地址：220.177.198.53，我们会尽快恢复您的正常访问权限。另外，如果您不是在访问的当前页面，我们建议您移步
或者 在浏览器中输入以下地址：http://chuansong.me/n/ 访问，您所访问的网站是从抓取的数据，请直接访问，会有更好的体验和更及时的更新。We suspect you are a robot.We are really sorry if you are not,and you can email us () with your current IP address: 220.177.198.53 to get full access to .If you are not accessing
for the current page,you'd better visit
for better performance,as the current website you are accessing is just spam.
觉得不错，分享给更多人看到
虚拟人 微信二维码
分享这篇文章
7月18日 21:51
虚拟人 最新头条文章
虚拟人 热门头条文章Connection Refused Error Java/Linux - Server Fault
to customize your list.
Server Fault is a question and answer site for system and network administrators. J it only takes a minute:
Here's how it works:
Anybody can ask a question
Anybody can answer
The best answers are voted up and rise to the top
I'm trying to move an existing project over to a new (linux) server environment (note, I have no direct access to the code nor do I have any knowledge about the project in general - talk about a great start), upon starting the project I receive the following error:
Exception in thread "main" municationException: Could not obtain connection to any of these urls: &servername&:1459 [Root exception is municationException: Failed to connect to server &servername&:1459 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server &servername&:1459 [Root exception is java.net.ConnectException:
Connection refused]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1562)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:634)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at org.jboss.Shutdown.main(Shutdown.java:214)
Caused by: municationException: Failed to connect to server &servername& [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server &servername&:1459 [Root exception is java.net.ConnectException: Connection refused]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:274)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1533)
... 4 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server &servername&:1459 [Root exception is java.net.ConnectException: Connection refused]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:248)
... 5 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at java.net.Socket.connect(Socket.java:478)
at java.net.Socket.&init&(Socket.java:375)
at java.net.Socket.&init&(Socket.java:276)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:244)
... 5 more
Now, I've opened the port in question to see whether there are any changes when I do so, alas, nothing happens.
I'm sorry about this very vague level of information, but it's really all I have, I'll gladly provide what I can if you have any ideas what could be at fault here.
It's simple, no one listen on port 1459. You configured jboss not exactly as on previous setup. Here is defaults for varios jboss versions
and snipplets from articles:
JBoss 7.x Ports
Defined in standalone.xml (or what you're using for start jboss)
&socket-binding name="jndi" port="1099"/&
&socket-binding name="jmx-connector-registry" port="1090"/&
&socket-binding name="jmx-connector-server" port="1091"/&
&socket-binding name="http" port="8080"/&
&socket-binding name="https" port="8443"/&
&socket-binding name="jacorb" port="3528"/&
&socket-binding name="jacorb-ssl" port="3529"/&
&socket-binding name="osgi-http" port="8090"/&
&socket-binding name="remoting" port="4447"/&
&socket-binding name="txn-recovery-environment" port="4712"/&
&socket-binding name="txn-status-manager" port="4713"/&
&socket-binding name="messaging" port="5445"/&
&socket-binding name="messaging-throughput" port="5455"/&
&/socket-binding-group&
JBoss 6.X Ports
Most of the default ports are listed in server/default/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml.
1090 RMI/JRMP for Remote JMX
1091 RMI server socket
1098 Naming Service - RMI requests from client proxies
1099 Naming Service - Main port
3873 EJB3 Remoting Connector
4446 JBoss Remoting Connector - Unified Invoker
4712 JBossTS Recovery Manager
4713 JBossTS Transaction Status Manager
4714 JBossTS - used to create a unique process id
5445 HornetQ
5455 Socket for HornetQ throughput connection factory
5500 Non-SSL Remoting
5501 SSL Remoting
8009 AJP Port
8080 HTTP Port
8083 Dynamic class and resource loading
JBoss 4.x Ports
1099 ./conf/jboss-service.xml or ./naming.sar/META-INF/jboss-service.xml Bootstrap JNP port.
1098 (anon) ./conf/jboss-service.xml or ./naming.sar/META-INF/jboss-service.xml RMI naming service port. Use '0' for an anonymous port.
4444 ./conf/jboss-service.xml or ./deploy/invokers-service.xml RMI/JRMP invoker port
4445 ./conf/jboss-service.xml or ./deploy/invokers-service.xml Pooled invoker
8083 ./conf/jboss-service.xml or ./deploy/dynclassloader-service.xml RMI dynamic class loader port
8080 ./deploy/jbossweb-tomcat55.sar/server.xml HTTP port for the web container
8009 ./deploy/jbossweb-tomcat55.sar/server.xml AJP port for the web container
8093 ./deploy/jms/uil2-service.xml UIL for JMS.
8443 (optional) ./deploy/jbossweb-tomcat55.sar/server.xml HTTPS port for the web container
We see from your application exception that it is trying to connect to some server on port 1459, and that the reason for the failure is Connection refused.
This has two possible causes:
Most likely: The remote service is not running. To resolve, start the remote service.
Less likely: The remote service is firewalled. To resolve, open the firewall.
133k19229460
Your Answer
Sign up or
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Post as a guest
By posting your answer, you agree to the
Not the answer you're looking for?
Browse other questions tagged
rev .25515
Server Fault works best with JavaScript enabledRemote JMX Exceptions - dikar云墨竹 - ITeye技术网站
博客分类：
转载自：/2008/06/remote-jmx-exceptions.html（需要fanqiang）
Perhaps the most difficult aspect of getting a freshly written
) compliant
application working is ensuring a proper
In this blog entry, I cover some of the most common
exceptions one may run into when developing the client and server portions of a
management and monitoring system using Remote JMX.
combines the original JMX specification with the Remote
JMX specification in a
(the JMX Remote API Specification is part III of
). This third part covers the required
as well as the optional JMXMP connector. In this blog entry, I'll be focusing on
using the RMI connector with
. Instead of using
as a client, I'll use a simple custom client to illustrate some of the
exceptions one may encounter when writing one's own client.
I am using
essentially the same code in this blog for examples that I previously used in
the previous blog entry
. I will not reproduce the code
here, but it is sufficient to know that the JMX Connector server code generally
establishes its JMXServiceURL
as service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
that the protocol is RMI, the host is localhost, the port is 1099, and the URL
string is "jmxrmi". Because the JMX client needs to use the same JMXServiceURL
as provided by the server, I appreciate it when third-party JMX servers provide
this to me. For example, both
provide their JMXServiceURL
to the console when they are
When the JMXServiceURL
is known, it is relatively
straightforward to write a client. The most significant lines of code for doing
this are extracted from the code in the previously referenced blog and displayed
final String objectNameStr = "dustin:type=status,name=remoteJMX";
final String jmxRmiStr =
"service:jmx:rmi://localhost/jndi/rmi://localhost:1099/jmxrmi";
final ObjectName objectName = new ObjectName(objectNameStr);
final JMXServiceURL jmxUrl = new JMXServiceURL(jmxRmiStr);
final JMXConnector jmxConnector = JMXConnectorFactory.connect(jmxUrl);
final MBeanServerConnection mbsc = jmxConnector.getMBeanServerConnection();
the code listing above demonstrates, it is fairly easy (and mostly boilerplate)
to connect clients to a JMX Connector Server with a well-known
JMXServiceURL
. However, it is not uncommon for new JMX developers
to struggle to get the JMXServiceURL
appropriately set. In the
remainder of this blog entry, I now look at some of the most common
JMXServiceURL
-related exceptions one may run
ERROR: IOException trying to
connect to JMX Connector Server
: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException
exception is java.rmi.ConnectException
Connection refused to host: nested exception is:
java.net.ConnectException: Connection refused: connect]
possible cause of this exception includes no JMX Connector Server running on the
specified host and port combination.
Also, ensure that an RMI registry
has been started at the specified port.
ERROR: IOException
trying to connect to JMX Connector Server:
Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: jmx-
This NameNotFoundException
was a result of
inadvertently mistyping the client's String URL portion (jmx-rmi
specified by the client rather than jmxrmi
without the hyphen).
This is different from the above error because a JMX Connector Server is at the
specified host and port, but with a different String portion. Because multiple
JMX Connector Servers can use the same host/port combination as long as they
have unique String portions of their URLs, it is not surprising that no
assumptions can be made about what String was
intended.Exception in thread "main" java.lang.ClassCastException
: com.sun.jndi.rmi.registry.RegistryContext cannot be cast to
javax.management.remote.rmi.RMIServer
The previous
exception demonstrated the result of attempting to access a JMX Connector Server
from a client with the correct host/port comibination, but with an incorrect
String URL portion. This ClassCastException
is the result of not
specifying any String URL portion at all in the JMXServiceURL
other words, the jmxrmi
portion was left off the end of the
JMXServiceURL
java.io.IOException:
Cannot bind to URL
[rmi://localhost:1099/jmxrmi]
: javax.naming.NameAlreadyBoundException
[Root exception is java.rmi.AlreadyBoundException: jmxrmi
now, all of the previously covered exceptions resulted from a JMX Client using a
mistyped or otherwise incorrect JMXServiceURL
that did not match
that used by the JMX Connector Server. This exception, however, is a JMX
Connector Server exception that results from two different applications trying
to use the same JMXServiceURL on the same host/port with the same URL
String.ERROR: Problem with
JMXServiceURL
based on rmi:///jndi/rmi://localhost:1099/jmxrmi: Service URL must start with
service:jmx:
This error message is particularly
descriptive and occurs when the JMXServiceURL
does not begin with
the specification-required service:jmx:
portion. See Section 13.8
("Connector Server Addresses") for additional details on all
JMXServiceURL
s beginning with this
ERROR: Problem with
JMXServiceURL
based on service:jmx::
///jndi/rmi://localhost:1099/jmxrmi: Missing or invalid protocol name:
As the error message indicates, the protocol is
missing from the JMXServiceURL
, which should be
service:jmx:rmi
:///jndi/rmi://localhost:1099/jmxrmi
the portion in red
omitted.ERROR: Problem with
JMXServiceURL
based on service:jmx:nothing
:///jndi/rmi://localhost:1099/jmxrmi: Unsupported protocol: nothing
the previous error message indicated a missing protocol designation, this error
indicates an erroneous protocol specification. In this particular case, the
incorrect JMXServiceURL
used was service:jmx:nothing
:///jndi/rmi://localhost:1099/jmxrmi
where the "nothing" in red
should have been
ERROR: IOException
trying to connect to JMX Connector Server: Failed to retrieve RMIServer stub:
javax.naming.NoInitialContextException: Need to specify
class name in environment or system property, or as an applet parameter, or in
an application resource file:
java.naming.factory.initial
This error message is
displayed for the case where the second protocol listing in the
JMXServiceURL
is either omitted or has an incorrect value. In other
words, if the highlighted
portion of the correct
JMXServiceURL
(service:jmx:rmi:///jndi/rmi
://localhost:1099/jmxrmi
)was omitted
entirely or had something unexpected like "nothing," this error message would
occur.Other Remote JMX Exceptions/Errors
Considerations
There are, of course, several other types of
exceptions one can run into when remotely accessing a JMX Connector Server.
These exceptions, which have not been covered here, are those that are thrown
when the connection is successfully made, but the sought-after MBean cannot be
found or some other problem occurs. The
document outlines recommendations related to
and also recommends having MBeans intended for
remote management/monitoring implement interfaces with operations that use the
clause (more granular for client than available as
Exceptions in General
The focus of this blog entry has been on
common exceptions and errors encountered when running a custom JMX Connector
Client with a custom JMX Connector Server. Note that JMX spells out its own
exception hierarchy related to the JMX Agent. Section 6.4 (JMX Exceptions) of
the JMX 1.4 Specification is devoted to these JMX exceptions. The section talks
which is the main class and parent of all descendant exception classes
(exception runtime exceptions) thrown by a JMX agent implementation. The JMX
runtime exceptions are represented by
and its descendant exceptions.
浏览: 1251097 次
来自: 杭州
大神，请接收我的膜拜吧，纠结了两天的问题，就这么让你给解决了
谢谢1楼，我也遇到，搞定了
学习了！！！！
感谢分享。我做个补充，也是关于PDF converting的相 ...
楼主太厉害了,我也遇到了