You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by maquanjun <ma...@gmail.com> on 2006/07/04 09:25:31 UTC
can't start jmx in activemq4.0.1
I want use the jmx function.But activemqj never listen the 1099 port,such as
follow:
netstat -lpn | grep java
tcp 0 0 :::37386 :::*
LISTEN 4472/java
tcp 0 0 :::61613 :::*
LISTEN 4472/java
tcp 0 0 :::61616 :::*
LISTEN 4472/java
the following is my activemq.xml
<!-- START SNIPPET: example -->
<beans xmlns="http://activemq.org/config/1.0">
<!-- Allows us to use system properties as variables in this configuration
file -->
<bean
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
<broker useJmx="true" brokerName="TESTBROKER">
<!-- Use the following to set the broker memory limit (in bytes)
<memoryManager>
<usageManager id="memory-manager" limit="1048576"/>
</memoryManager>
-->
<managementContext>
<managementContext connectorPort="1099"
jmxDomainName="org.apache.activemq"/>
</managementContext>
<!-- In ActiveMQ 4, you can setup destination policies -->
<destinationPolicy>
<policyMap><policyEntries>
<policyEntry topic="FOO.>">
<dispatchPolicy>
<strictOrderDispatchPolicy />
</dispatchPolicy>
<subscriptionRecoveryPolicy>
<lastImageSubscriptionRecoveryPolicy />
</subscriptionRecoveryPolicy>
</policyEntry>
</policyEntries></policyMap>
</destinationPolicy>
<persistenceAdapter>
<journaledJDBC journalLogFiles="5"
dataDirectory="${activemq.home}/activemq-data"/>
<!-- To use a different datasource, use th following syntax : -->
<!--
<journaledJDBC journalLogFiles="5" dataDirectory="../activemq-data"
dataSource="#postgres-ds"/>
-->
</persistenceAdapter>
<transportConnectors>
<transportConnector name="default" uri="tcp://server107:61616" />
<transportConnector name="stomp" uri="stomp://server107:61613"/>
</transportConnectors>
<networkConnectors>
<networkConnector name="default"
uri="static://(tcp://server108:61616,tcp://server109:61616)"
failover="true"/>
</networkConnectors>
</broker>
<!-- This xbean configuration file supports all the standard spring xml
configuration options -->
<!-- Postgres DataSource Sample Setup -->
<!--
<bean id="postgres-ds" class="org.postgresql.ds.PGPoolingDataSource">
<property name="serverName" value="localhost"/>
<property name="databaseName" value="activemq"/>
<property name="portNumber" value="0"/>
<property name="user" value="activemq"/>
<property name="password" value="activemq"/>
<property name="dataSourceName" value="postgres"/>
<property name="initialConnections" value="1"/>
<property name="maxConnections" value="10"/>
</bean>
-->
<!-- MySql DataSource Sample Setup -->
<!--
<bean id="mysql-ds" class="org.apache.commons.dbcp.BasicDataSource"
destroy-method="close">
<property name="driverClassName" value="com.mysql.jdbc.Driver"/>
<property name="url"
value="jdbc:mysql://localhost/activemq?relaxAutoCommit=true"/>
<property name="username" value="activemq"/>
<property name="password" value="activemq"/>
<property name="poolPreparedStatements" value="true"/>
</bean>
-->
<!-- Embedded Derby DataSource Sample Setup -->
<!--
<bean id="derby-ds" class="org.apache.derby.jdbc.EmbeddedDataSource">
<property name="databaseName" value="derbydb"/>
<property name="createDatabase" value="create"/>
</bean>
-->
</beans>
<!-- END SNIPPET: example -->
--
View this message in context: http://www.nabble.com/can%27t-start-jmx-in-activemq4.0.1-tf1888424.html#a5163041
Sent from the ActiveMQ - User forum at Nabble.com.
Re: can't start jmx in activemq4.0.1
Posted by maquanjun <ma...@gmail.com>.
Thank you
I add the properties of -Dcom.sun.management.jmxremote.port=1099
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
and I can remote control now
Thank you
--
View this message in context: http://www.nabble.com/can%27t-start-jmx-in-activemq4.0.1-tf1888424.html#a5175700
Sent from the ActiveMQ - User forum at Nabble.com.
Re: can't start jmx in activemq4.0.1
Posted by James Strachan <ja...@gmail.com>.
AFAIK 4.0.1 has the -D system properties enabled so starting JConsole
should automatically find the broker
On 7/4/06, Hiram Chirino <hi...@hiramchirino.com> wrote:
> ActiveMQ can only setup the JMX connector in Java 1.4, since Java 1.5 has an
> embedded JMX server implementation, you have to use pass -D system
> properties to configure the JMX connector for your JVM.
>
>
> On 7/4/06, maquanjun <ma...@gmail.com> wrote:
> >
> >
> > this is the start infomation:
> >
> > ./activemq
> > ACTIVEMQ_HOME: /usr/local/activemq-4.0.1
> > Loading message broker from: xbean:activemq.xml
> > INFO BrokerService - ActiveMQ 4.0.1 JMS Message Broker
> > (TESTBROKER) is starting
> > INFO BrokerService - For help or more information please
> > see: http://incubator.apache.org/activemq/
> > INFO JDBCPersistenceAdapter - Database driver recognized:
> > [apache_derby_embedded_jdbc_driver]
> > INFO JournalPersistenceAdapter - Journal Recovery Started from:
> > Active
> > Journal: using 5 x 20.0 Megs at: /usr/local/acti
> > vemq-4.0.1/activemq-data/journal
> > INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in
> > transactions recovered.
> > INFO TransportServerThreadSupport - Listening for connections at:
> > tcp://server107:61616
> > INFO TransportConnector - Connector default Started
> > INFO TransportServerThreadSupport - Listening for connections at:
> > tcp://server107:61613?wireFormat=stomp
> > INFO TransportConnector - Connector stomp Started
> > INFO NetworkConnector - Establishing network connection
> > between from vm://TESTBROKER?network=true to failover:
> > tcp://server108:61616
> > INFO VMTransportFactory - binding to broker: TESTBROKER
> > INFO TransportConnector - Connector vm://TESTBROKER Started
> > INFO DemandForwardingBridge - Starting a network connection
> > between
> > vm://TESTBROKER#0 and tcp://server108:61616 has
> > been established.
> > INFO NetworkConnector - Establishing network connection
> > between from vm://TESTBROKER?network=true to failover:
> > tcp://server109:61616
> > INFO DemandForwardingBridge - Starting a network connection
> > between
> > vm://TESTBROKER#2 and unconnected has been estab
> > lished.
> > INFO NetworkConnector - Network Connector default Started
> > INFO BrokerService - ActiveMQ JMS Message Broker
> > (TESTBROKER, ID:server107-37835-1151997930692-1:0) started
> > --
> > View this message in context:
> > http://www.nabble.com/can%27t-start-jmx-in-activemq4.0.1-tf1888424.html#a5163059
> > Sent from the ActiveMQ - User forum at Nabble.com.
> >
> >
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
>
--
James
-------
http://radio.weblogs.com/0112098/
Re: can't start jmx in activemq4.0.1
Posted by Hiram Chirino <hi...@hiramchirino.com>.
ActiveMQ can only setup the JMX connector in Java 1.4, since Java 1.5 has an
embedded JMX server implementation, you have to use pass -D system
properties to configure the JMX connector for your JVM.
On 7/4/06, maquanjun <ma...@gmail.com> wrote:
>
>
> this is the start infomation:
>
> ./activemq
> ACTIVEMQ_HOME: /usr/local/activemq-4.0.1
> Loading message broker from: xbean:activemq.xml
> INFO BrokerService - ActiveMQ 4.0.1 JMS Message Broker
> (TESTBROKER) is starting
> INFO BrokerService - For help or more information please
> see: http://incubator.apache.org/activemq/
> INFO JDBCPersistenceAdapter - Database driver recognized:
> [apache_derby_embedded_jdbc_driver]
> INFO JournalPersistenceAdapter - Journal Recovery Started from:
> Active
> Journal: using 5 x 20.0 Megs at: /usr/local/acti
> vemq-4.0.1/activemq-data/journal
> INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in
> transactions recovered.
> INFO TransportServerThreadSupport - Listening for connections at:
> tcp://server107:61616
> INFO TransportConnector - Connector default Started
> INFO TransportServerThreadSupport - Listening for connections at:
> tcp://server107:61613?wireFormat=stomp
> INFO TransportConnector - Connector stomp Started
> INFO NetworkConnector - Establishing network connection
> between from vm://TESTBROKER?network=true to failover:
> tcp://server108:61616
> INFO VMTransportFactory - binding to broker: TESTBROKER
> INFO TransportConnector - Connector vm://TESTBROKER Started
> INFO DemandForwardingBridge - Starting a network connection
> between
> vm://TESTBROKER#0 and tcp://server108:61616 has
> been established.
> INFO NetworkConnector - Establishing network connection
> between from vm://TESTBROKER?network=true to failover:
> tcp://server109:61616
> INFO DemandForwardingBridge - Starting a network connection
> between
> vm://TESTBROKER#2 and unconnected has been estab
> lished.
> INFO NetworkConnector - Network Connector default Started
> INFO BrokerService - ActiveMQ JMS Message Broker
> (TESTBROKER, ID:server107-37835-1151997930692-1:0) started
> --
> View this message in context:
> http://www.nabble.com/can%27t-start-jmx-in-activemq4.0.1-tf1888424.html#a5163059
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
Regards,
Hiram
Blog: http://hiramchirino.com
Re: can't start jmx in activemq4.0.1
Posted by maquanjun <ma...@gmail.com>.
this is the start infomation:
./activemq
ACTIVEMQ_HOME: /usr/local/activemq-4.0.1
Loading message broker from: xbean:activemq.xml
INFO BrokerService - ActiveMQ 4.0.1 JMS Message Broker
(TESTBROKER) is starting
INFO BrokerService - For help or more information please
see: http://incubator.apache.org/activemq/
INFO JDBCPersistenceAdapter - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
INFO JournalPersistenceAdapter - Journal Recovery Started from: Active
Journal: using 5 x 20.0 Megs at: /usr/local/acti
vemq-4.0.1/activemq-data/journal
INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in
transactions recovered.
INFO TransportServerThreadSupport - Listening for connections at:
tcp://server107:61616
INFO TransportConnector - Connector default Started
INFO TransportServerThreadSupport - Listening for connections at:
tcp://server107:61613?wireFormat=stomp
INFO TransportConnector - Connector stomp Started
INFO NetworkConnector - Establishing network connection
between from vm://TESTBROKER?network=true to failover:
tcp://server108:61616
INFO VMTransportFactory - binding to broker: TESTBROKER
INFO TransportConnector - Connector vm://TESTBROKER Started
INFO DemandForwardingBridge - Starting a network connection between
vm://TESTBROKER#0 and tcp://server108:61616 has
been established.
INFO NetworkConnector - Establishing network connection
between from vm://TESTBROKER?network=true to failover:
tcp://server109:61616
INFO DemandForwardingBridge - Starting a network connection between
vm://TESTBROKER#2 and unconnected has been estab
lished.
INFO NetworkConnector - Network Connector default Started
INFO BrokerService - ActiveMQ JMS Message Broker
(TESTBROKER, ID:server107-37835-1151997930692-1:0) started
--
View this message in context: http://www.nabble.com/can%27t-start-jmx-in-activemq4.0.1-tf1888424.html#a5163059
Sent from the ActiveMQ - User forum at Nabble.com.