安装JDK并配置环境变量(略)
 
JAVA_HOME=/home/huangkejie/java/jdk1.8.0_171
 
在home/huangkejie下创建activeMQ目录
 
$ mkdir activeMQ
 
$ cd activeMQ
 
下载Linux版的ActiveMQ(当前最新版apache-activemq-5.11.1-bin.tar.gz)
 
$ wget http://apache.fayea.com/activemq/5.11.1/apache-activemq-5.11.1-bin.tar.gz
 
解压安装
 
$ tar -zxvf apache-activemq-5.11.1-bin.tar.gz
 
$ mv apache-activemq-5.11.1 activemq
 
如果启动脚本activemq没有可执行权限，此时则需要授权(此步可选)
 
$ cd /home/huangkejie/activemq/bin/
 
$ chmod 777 ./activemq
 
防火墙中打开对应的端口
 
ActiveMQ需要用到两个端口
 
一个是消息通讯的端口(默认为61616)
 
一个是管理控制台端口(默认为8161)可在conf/jetty.xml中修改，如下：
 
# vi /etc/sysconfig/iptables
 
添加：
 
-A INPUT -m state --state NEW -m tcp -p tcp --dport 61616 -j ACCEPT
 
-A INPUT -m state --state NEW -m tcp -p tcp --dport 8161 -j ACCEPT
 
重启防火墙：
 
# service iptables restart
 
启动
 
$ cd /home/huangkejie/activemq/bin
 
$ ./activemq start
 

 
点击Manage ActiveMQ broker超链接输入默认用户名和密码为：admin/admin
 
登录后进入
 

 
安全配置(消息安全)
 
ActiveMQ如果不加入安全机制的话，任何人只要知道消息服务的具体地址(包括ip，端口，消息地址[队列或者主题地址]，)，都可以肆无忌惮的发送、接收消息。关于ActiveMQ安装配置http://activemq.apache.org/security.html
 
ActiveMQ的消息安全配置策略有多种，我们以简单授权配置为例：
 
在conf/activemq.xml文件中在broker结束标签前加入以下内容即可：
 
$vi /home/huangkejie/activemq/conf/activemq.xml
 
定义了一个huangkejie用户，密码为huangkejie，角色为users,admins
 
设置admin的用户名和密码:
 
$ vi /home/wusc/activemq-01/conf/jetty.xml
 
确保authenticate的值为true(默认)
 
控制台的登录用户名密码保存在conf/jetty-realm.properties文件中,内容如下:
 
$ vi /home/wusc/activemq-01/conf/jetty-realm.properties
 
# Defines users that can access the web (console, demo, etc.)
 
# username: password [,rolename ...]
 

 
注意:用户名和密码的格式是
 
用户名 : 密码 ,角色名
 
以上的截图可以看出我修改了admin的密码为huangkejie，新增了huangkejie的用户，密码为huangkejie，角色为admin
 
重启:
 
$ /home/huangkejie/activemq/bin/activemq restart
 
设置开机启动：
 
# vi /etc/rc.local
 
加入以下内容
 
## ActiveMQ
 
su - huangkejie -c '/home/huangkejie/activemq/bin/activemq start'

 
 
 linux 重启tomcat和activemq 
 
 
 
 
 
  

   
使用ssh命令连接服务器
 
   

    linux下 tomcat的启动
    
1、使用cd命令进入到bin文件夹
   
 
   

    cd home/apache-tomcat-8.5.15/bin
   
 
   

    2、输入 ./startup.sh 启动tomcat
   
 
   

    3、输入 ./shutdown.sh 关闭tomcat
    
linux下启动acitvemq
    
1、使用cd命令进入到acitvemq的bin文件夹
   
 
   

    cd /home/apache-activemq-5.13.3
    
2、输入 ./activemq start 启动activemq
    
3、输入 ./activemq stop 关闭activemq
   
 
   

     
   
 
   

    在shell输入 ps -ef|grep java 可以查看当前的java进程 用来验证tomcat和mq是否启动成功
   
 
   

    也可以使用kill -9 pid直接结束该进程
    

   
 
   

    这些步骤同样也可以用来重启jboss
   
  
  
 
  
 
  
 
   
 
   
 
   
 
   
 
   
 
   
 
  
 
 
 
 

  posted @ 
  2018-08-31 09:52 
  scd 阅读(
  ...) 评论(
  ...) 
  编辑 
  收藏
 
 
 
转载于:https://www.cnblogs.com/lichenx/p/9564087.html

这篇文章主要讲如何在linux服务器上安装activemq
 一、整体架构说明
 本次安装的activemq版本为5.9.0，为单节点服务。
 
二、准备工作
 http://archive.apache.org/dist/activemq/apache-activemq/5.9.0/apache-activemq-5.9.0-bin.tar.gz 下载activemq5.9.0安装包
 https://mvnrepository.com/artifact/mysql/mysql-connector-java 下载连接mysql的驱动jar包mysql-connector-java-5.1.32.jar
 
三、安装jdk1.8
 比较简单，这里只写一下jdk的环境变量：
 
echo "export JAVA_HOME=/usr/java/jdk1.8.0_91
export JAVA_BIN=$JAVA_HOME/bin
export PATH=$JAVA_HOME/bin:$PATH
export CLASSPATH=.:$JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar
export JAVA_HOME JAVA_BIN PATH CLASSPATH" >> /etc/profile
source /etc/profile
 
四、安装mysql
 mysql的安装比较简单，安装步骤略（如有需要，可留言）
 并在mysql中创建库activemq
 
mysql>create database activemq;
 
五、安装activemq
 
mv apache-activemq-5.9.0-bin.tar.gz /usr/local/
cd /usr/local/
tar -zxvf apache-activemq-5.9.0-bin.tar.gz
 
把连接mysql的驱动jar包放到相应的目录下
 
mv mysql-connector-java-5.1.32.jar /usr/local/apache-activemq-5.9.0/lib/optional/
 
六、修改主配置文件
 
cd /usr/local/apache-activemq-5.9.0/conf/
 
备份主配置文件
 
mv activemq.xml activemq.xml_bak
 
修改主配置文件activemq.xml:
 
 
实现数据的持久化
 1.1在beans标签中添加数据库连接信息
 
<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://192.168.0.11:3306/activemq?relaxAutoCommit=true"/>    
	    <property name="username" value="root"/>    
	    <property name="password" value="123456"/>    
	    <property name="maxActive" value="200"/>    
	    <property name="poolPreparedStatements" value="true"/>    
</bean>
 
1.2注释掉默认的kahadb，使用jdbc持久化
 
<persistenceAdapter>
	    <!--kahaDB directory="${activemq.data}/kahadb" /-->
	    <jdbcPersistenceAdapter dataDirectory="${activemq.base}/data"  dataSource="#mysql-ds" useDatabaseLock="false" transactionIsolation="4" />
</persistenceAdapter>
 
1.3将所有的消息策略修改为“持久化的”，在broker标签的最后，加上如下配置:
 
<plugins>
	<!-- 将所有消息的传输模式，修改为"PERSISTENT" -->
	<forcePersistencyModeBrokerPlugin persistenceFlag="true"/>
</plugins>
 
 
修改内存中存储的消息的数量（超过这个数量后，老的消息将会被剔除或保存在temp store中）
 
<pendingMessageLimitStrategy>
	<!--constantPendingMessageLimitStrategy limit="1000"/-->
	<constantPendingMessageLimitStrategy limit="10000"/>
</pendingMessageLimitStrategy>
 
 
添加安全机制，创建消息通讯用户(即为你代码中配置的用户名和密码)
 activemq如果不加入安全机制的话，任何人只要知道消息服务的具体地址(包括 ip，端口，消息地址 [队列或者主题地址])，都可以肆无忌惮的发送、接收消息。
 
<plugins>
	<simpleAuthenticationPlugin>
		<users>
			<authenticationUser username="product" password="123456" groups="user"/>
		</users>
	</simpleAuthenticationPlugin>
</plugins>
 
此处定义了一个product用户，密码为123456，角色为user。
 修改完后的activemq.xml文件完整内容如下：
 
 
 
 
 
<!-- Allows us to use system properties as variables in this configuration file -->
<bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
    <property name="locations">
        <value>file:${activemq.conf}/credentials.properties</value>
    </property>
</bean>

<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://192.168.0.11:3306/active_mq?relaxAutoCommit=true"/>    
    <property name="username" value="root"/>    
    <property name="password" value="123456"/>    
    <property name="maxActive" value="200"/>    
    <property name="poolPreparedStatements" value="true"/>    
</bean>  

<!-- Allows log searching in hawtio console -->
<bean id="logQuery" class="org.fusesource.insight.log.log4j.Log4jLogQuery"
      lazy-init="false" scope="singleton"
      init-method="start" destroy-method="stop">
</bean>

<!--
    The <broker> element is used to configure the ActiveMQ broker.
-->
<broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="${activemq.data}">

    <destinationPolicy>
        <policyMap>
          <policyEntries>
            <policyEntry topic=">" >
                <!-- The constantPendingMessageLimitStrategy is used to prevent
                     slow topic consumers to block producers and affect other consumers
                     by limiting the number of messages that are retained
                     For more information, see:

                     http://activemq.apache.org/slow-consumer-handling.html

                -->
              <pendingMessageLimitStrategy>
                <!--constantPendingMessageLimitStrategy limit="1000"/-->
				<constantPendingMessageLimitStrategy limit="10000"/>
              </pendingMessageLimitStrategy>
            </policyEntry>
          </policyEntries>
        </policyMap>
    </destinationPolicy>


    <!--
        The managementContext is used to configure how ActiveMQ is exposed in
        JMX. By default, ActiveMQ uses the MBean server that is started by
        the JVM. For more information, see:

        http://activemq.apache.org/jmx.html
    -->
    <managementContext>
        <managementContext createConnector="false"/>
    </managementContext>

    <!--
        Configure message persistence for the broker. The default persistence
        mechanism is the KahaDB store (identified by the kahaDB tag).
        For more information, see:

        http://activemq.apache.org/persistence.html
    -->
    <persistenceAdapter>
        <!--kahaDB directory="${activemq.data}/kahadb" /-->
        <jdbcPersistenceAdapter dataDirectory="${activemq.base}/data"  dataSource="#mysql-ds" useDatabaseLock="false" transactionIsolation="4" />
    </persistenceAdapter>


      <!--
        The systemUsage controls the maximum amount of space the broker will
        use before disabling caching and/or slowing down producers. For more information, see:
        http://activemq.apache.org/producer-flow-control.html
      -->
      <systemUsage>
        <systemUsage>
            <memoryUsage>
                <memoryUsage percentOfJvmHeap="70" />
            </memoryUsage>
            <storeUsage>
                <storeUsage limit="100 gb"/>
            </storeUsage>
            <tempUsage>
                <tempUsage limit="50 gb"/>
            </tempUsage>
        </systemUsage>
    </systemUsage>

    <!--
        The transport connectors expose ActiveMQ over a given protocol to
        clients and other brokers. For more information, see:

        http://activemq.apache.org/configuring-transports.html
    -->
    <transportConnectors>
        <!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB -->
        <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
        <transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
        <transportConnector name="stomp" uri="stomp://0.0.0.0:61613?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
        <transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
        <transportConnector name="ws" uri="ws://0.0.0.0:61614?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
    </transportConnectors>

    <!-- destroy the spring context on shutdown to stop jetty -->
    <shutdownHooks>
        <bean xmlns="http://www.springframework.org/schema/beans" class="org.apache.activemq.hooks.SpringContextHook" />
    </shutdownHooks>
    
    <plugins>
        <simpleAuthenticationPlugin>
            <users>
                <authenticationUser username="product" password="123456" groups="user"/>
            </users>
        </simpleAuthenticationPlugin>
    </plugins>

    <plugins>
        <!-- 将所有消息的传输模式，修改为"PERSISTENT" -->
        <forcePersistencyModeBrokerPlugin persistenceFlag="true"/>
    </plugins>	

</broker>

<!--
    Enable web consoles, REST and Ajax APIs and demos
    The web consoles requires by default login, you can disable this in the jetty.xml file

    Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details
-->
<import resource="jetty.xml"/>
 
 
七、启动activemq
 
cd /usr/local/apache-activemq-5.9.0/bin/
./activemq start
 
这时，activemq管理页面http://192.168.0.11:8161/的默认用户名密码为admin/admin，可以进入新、老管理界面
 
 
八、修改管理页面的用户名和密码
 修改admin的密码下需要修改两个文件，分别为jetty-realm.properties和users.properties
 
修改jetty-realm.properties
 
admin: a1b2c3, admin
user: user, user
 
修改users.properties
 
admin=a1b2c3
 
重启服务，这时候可以用admin/a1b2c3登录管理页面（http://192.168.0.11:8161）
 
九、对消息持久化的验证
 当所有配置完成，我们重启服务之后，对activemq中生产6条消息，并且暂时不消费，这时候会发现，在管理页面可以看到6条消息
 
 并且在对应的mysql中的activemq这个库中会自动生成3张表，分别为
 activemq_acks：ActiveMQ的签收信息
 activemq_lock：ActiveMQ的锁信息
 activemq_msgs：ActiveMQ的消息
 并且在activemq_msgs表中，会存在6条数据，如图所示
 
 
即使是重启activemq之后，打开管理页面，也是显示6条数据，activemq_msgs表中也是6条数据，证明消息的确是持久化的。
 待开启消费者消费这6条数据之后，activemq_msgs表中的数据也将不存在。
 
十、修改activemq的内存配置
 这边把最大内存由1G改为4G（根据实际情况调整）
 修改bin/activemq
 
#Set jvm memory configuration
if [ -z "$ACTIVEMQ_OPTS_MEMORY" ] ; then
    ACTIVEMQ_OPTS_MEMORY="-Xms1G -Xmx4G"
fi

 
 
 
  
2019独角兽企业重金招聘Python工程师标准>>>  
 
 
 
 
 linux环境中, activemq因为磁盘空间不足异常退出, 重启就出现下面的问题. 
 
 
因为看到org.apache.activemq.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero)这个信息猜测可能是activemq异常退出, 导致有不完整的通道或者信息. mq下的data文件夹删除后重启成功
 
 
2018-11-09 14:35:42,044 | INFO  | Refreshing org.apache.activemq.xbean.XBeanBrokerFactory$1@6b0b693e: startup date [Fri Nov 09 14:35:42 CST 2018]; root of context hierarchy | org.apache.activemq.xbean.XBeanBrokerFactory$1 | WrapperSimpleAppMain
2018-11-09 14:35:43,198 | INFO  | PListStore:[/usr/local/apache-activemq-5.9.0/bin/linux-x86-64/../../data/localhost/tmp_storage] started | org.apache.activemq.store.kahadb.plist.PListStoreImpl | WrapperSimpleAppMain
2018-11-09 14:35:43,229 | INFO  | Using Persistence Adapter: KahaDBPersistenceAdapter[/usr/local/apache-activemq-5.9.0/bin/linux-x86-64/../../data/kahadb] | org.apache.activemq.broker.BrokerService | WrapperSimpleAppMain
2018-11-09 14:35:43,419 | INFO  | Corrupt journal records found in '../../data/kahadb/db-1.log' between offsets: 9310090..9316753 | org.apache.activemq.store.kahadb.disk.journal.Journal | WrapperSimpleAppMain
2018-11-09 14:35:43,427 | INFO  | Corrupt journal records found in '../../data/kahadb/db-1.log' between offsets: 9691444..9710929 | org.apache.activemq.store.kahadb.disk.journal.Journal | WrapperSimpleAppMain
2018-11-09 14:35:43,761 | INFO  | KahaDB is version 5 | org.apache.activemq.store.kahadb.MessageDatabase | WrapperSimpleAppMain
2018-11-09 14:35:43,812 | INFO  | Recovering from the journal ... | org.apache.activemq.store.kahadb.MessageDatabase | WrapperSimpleAppMain
2018-11-09 14:35:43,825 | ERROR | Failed to start Apache ActiveMQ ([localhost, null], org.apache.activemq.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero).) | org.apache.activemq.broker.BrokerService | WrapperSimpleAppMain
2018-11-09 14:35:43,828 | INFO  | Apache ActiveMQ 5.9.0 (localhost, null) is shutting down | org.apache.activemq.broker.BrokerService | WrapperSimpleAppMain
2018-11-09 14:35:43,830 | INFO  | Connector openwire stopped | org.apache.activemq.broker.TransportConnector | WrapperSimpleAppMain
2018-11-09 14:35:43,831 | INFO  | Connector amqp stopped | org.apache.activemq.broker.TransportConnector | WrapperSimpleAppMain
2018-11-09 14:35:43,832 | INFO  | Connector stomp stopped | org.apache.activemq.broker.TransportConnector | WrapperSimpleAppMain
2018-11-09 14:35:43,834 | INFO  | Connector mqtt stopped | org.apache.activemq.broker.TransportConnector | WrapperSimpleAppMain
2018-11-09 14:35:43,835 | INFO  | Connector ws stopped | org.apache.activemq.broker.TransportConnector | WrapperSimpleAppMain
2018-11-09 14:35:43,840 | INFO  | PListStore:[/usr/local/apache-activemq-5.9.0/bin/linux-x86-64/../../data/localhost/tmp_storage] stopped | org.apache.activemq.store.kahadb.plist.PListStoreImpl | WrapperSimpleAppMain
2018-11-09 14:35:43,841 | INFO  | Stopping async queue tasks | org.apache.activemq.store.kahadb.KahaDBStore | WrapperSimpleAppMain
2018-11-09 14:35:43,842 | INFO  | Stopping async topic tasks | org.apache.activemq.store.kahadb.KahaDBStore | WrapperSimpleAppMain
2018-11-09 14:35:43,844 | INFO  | Stopped KahaDB | org.apache.activemq.store.kahadb.KahaDBStore | WrapperSimpleAppMain
2018-11-09 14:35:44,290 | INFO  | Apache ActiveMQ 5.9.0 (localhost, null) uptime 1.083 seconds | org.apache.activemq.broker.BrokerService | WrapperSimpleAppMain
2018-11-09 14:35:44,291 | INFO  | Apache ActiveMQ 5.9.0 (localhost, null) is shutdown | org.apache.activemq.broker.BrokerService | WrapperSimpleAppMain
2018-11-09 14:35:44,293 | INFO  | Closing org.apache.activemq.xbean.XBeanBrokerFactory$1@6b0b693e: startup date [Fri Nov 09 14:35:42 CST 2018]; root of context hierarchy | org.apache.activemq.xbean.XBeanBrokerFactory$1 | WrapperSimpleAppMain
2018-11-09 14:35:44,297 | WARN  | Exception thrown from LifecycleProcessor on context close | org.apache.activemq.xbean.XBeanBrokerFactory$1 | WrapperSimpleAppMain
java.lang.IllegalStateException: LifecycleProcessor not initialized - call 'refresh' before invoking lifecycle methods via the context: org.apache.activemq.xbean.XBeanBrokerFactory$1@6b0b693e: startup date [Fri Nov 09 14:35:42 CST 2018]; root of context hierarchy
	at org.springframework.context.support.AbstractApplicationContext.getLifecycleProcessor(AbstractApplicationContext.java:360)
	at org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:1057)
	at org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:1010)
	at org.apache.activemq.hooks.SpringContextHook.run(SpringContextHook.java:30)
	at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:782)
	at org.apache.activemq.xbean.XBeanBrokerService.stop(XBeanBrokerService.java:122)
	at org.apache.activemq.broker.BrokerService.start(BrokerService.java:574)
	at org.apache.activemq.xbean.XBeanBrokerService.afterPropertiesSet(XBeanBrokerService.java:73)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1608)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1549)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1479)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:521)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)
	at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:628)
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479)
	at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:64)
	at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:52)
	at org.apache.activemq.xbean.XBeanBrokerFactory$1.<init>(XBeanBrokerFactory.java:104)
	at org.apache.activemq.xbean.XBeanBrokerFactory.createApplicationContext(XBeanBrokerFactory.java:104)
	at org.apache.activemq.xbean.XBeanBrokerFactory.createBroker(XBeanBrokerFactory.java:67)
	at org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:71)
	at org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:54)
	at org.apache.activemq.console.command.StartCommand.runTask(StartCommand.java:87)
	at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
	at org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:150)
	at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
	at org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:104)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.activemq.console.Main.runTaskClass(Main.java:262)
	at org.apache.activemq.console.Main.main(Main.java:115)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:240)
	at java.lang.Thread.run(Thread.java:748)
 
 
 
 
 
 
  
 
    
  
 
 
 
 
转载于:https://my.oschina.net/MrBamboo/blog/2874190