ActiveMQ5.2.0集成到JBoss4.X

1、在JBoss的部署目录下建立activemq-ra.rar目录(注意这是一个目录)

2、在ActiveMQ5.2.0的目录X:\apache-activemq-5.2.0\lib\optional下找到activemq-rar- 5.2.0.rar文件,将其全部内容解压缩到第一步建立的目录

3、上面的解压的后,找到META-INF\ra.xml文件,按照下面进行修改

<config-property-value></config-property-value>

<!--<config-property-value>xbean:broker-config.xml</config-property-value> -->

改为

<!--<config-property-value></config-property-value> -->

<config-property-value>xbean:broker-config.xml</config-property-value>

4、配置jboss4.2.3.GA集成ActiveMQ5.2.0的数据源,文件名activemq-ds.xml,内容:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE connection-factories
PUBLIC "-//JBoss//DTD JBOSS JCA Config 1.5//EN"
"http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd">
<connection-factories>
<tx-connection-factory>
<jndi-name>activemq/QueueConnectionFactory</jndi-name>
<xa-transaction/>
<track-connection-by-tx/>
<rar-name>activemq-ra.rar</rar-name>
<connection-definition>javax.jms.QueueConnectionFactory</connection-definition>
<ServerUrl>tcp://localhost:61616</ServerUrl>
<min-pool-size>1</min-pool-size>
<max-pool-size>200</max-pool-size>
<blocking-timeout-millis>30000</blocking-timeout-millis>
<idle-timeout-minutes>3</idle-timeout-minutes>
</tx-connection-factory>
<tx-connection-factory>
<jndi-name>activemq/TopicConnectionFactory</jndi-name>
<xa-transaction/>
<track-connection-by-tx/>
<rar-name>activemq-ra.rar</rar-name>
<connection-definition>javax.jms.TopicConnectionFactory</connection-definition>
<ServerUrl>tcp://localhost:61616</ServerUrl>
<min-pool-size>1</min-pool-size>
<max-pool-size>200</max-pool-size>
<blocking-timeout-millis>30000</blocking-timeout-millis>
<idle-timeout-minutes>3</idle-timeout-minutes>
</tx-connection-factory>
<mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.queue:name=outboundQueue">
<attribute name="JNDIName">activemq/queue/outbound</attribute>
<depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name=&apos;activemq-ra.rar&apos;</depends>
<attribute name="Type">javax.jms.Queue</attribute>
<attribute name="Properties">PhysicalName=queue.outbound</attribute>
</mbean>
<mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.topic:name=inboundTopic">
<attribute name="JNDIName">activemq/topic/inbound</attribute>
<depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name=&apos;activemq-ra.rar&apos;</depends>
<attribute name="Type">javax.jms.Topic</attribute>
<attribute name="Properties">PhysicalName=topic.inbound</attribute>
</mbean>
</connection-factories>

将此文件复制到jboss的部署目录

5、将X:\apache-activemq-5.2.0\lib\optional下的的以spring-开头的文件、xbean-spring-3.4.jar文件、commons-dbcp-1.2.jar、commons-pool-1.4.jar复制到

x:\jboss-4.2.3.GA\server\default\lib中

6、测试运行,注意查看jboss控制台,有类似以下内容

12:17:21,538 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/activemq-ra.rar/
12:17:21,677 INFO [ResourceXmlApplicationContext] Refreshing org.apache.xbean.s
pring.context.ResourceXmlApplicationContext@2d4c7e: display name [org.apache.xbe
an.spring.context.ResourceXmlApplicationContext@2d4c7e]; startup date [Mon Jan 1
9 12:17:21 CST 2009]; root of context hierarchy
12:17:21,771 INFO [XBeanXmlBeanDefinitionReader] Loading XML bean definitions f
rom class path resource [broker-config.xml]
12:17:22,008 INFO [ResourceXmlApplicationContext] Bean factory for application
context [org.apache.xbean.spring.context.ResourceXmlApplicationContext@2d4c7e]:
org.springframework.beans.factory.support.DefaultListableBeanFactory@17777a1
12:17:22,024 INFO [DefaultListableBeanFactory] Pre-instantiating singletons in
org.springframework.beans.factory.support.DefaultListableBeanFactory@17777a1: de
fining beans [org.apache.activemq.xbean.XBeanBrokerService#0]; root of factory h
ierarchy
12:17:23,284 INFO [BrokerService] Using Persistence Adapter: JournalPersistence
Adapator(JDBCPersistenceAdaptor(org.apache.derby.jdbc.EmbeddedDataSource@8d539f)
)

7、配置消息持久化数据库,使用以下内容替换broker-config.xml文件内容,注意配置数据库连接参数,以及将jdbc驱动库文件拷贝到jboss/server/default/lib目录中

<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version
2.0 (the "License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0 Unless required by
applicable law or agreed to in writing, software distributed under the
License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
CONDITIONS OF ANY KIND, either express or implied. See the License for
the specific language governing permissions and limitations under the
License.
-->
<!-- START SNIPPET: example -->
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:amq="http://activemq.apache.org/schema/core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd
http://activemq.apache.org/camel/schema/spring http://activemq.apache.org/camel/schema/spring/camel-spring.xsd">

<!--
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.base}/conf/credentials.properties </value>
</property> </bean>
-->

<broker xmlns="http://activemq.apache.org/schema/core"
brokerName="localhost" dataDirectory="../data">

<!--
Destination specific policies using destination names or wildcards
-->
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry queue=">" memoryLimit="5mb" />
<policyEntry topic=">" memoryLimit="5mb">
<!--
you can add other policies too such as these <dispatchPolicy>
<strictOrderDispatchPolicy/> </dispatchPolicy>
<subscriptionRecoveryPolicy>
<lastImageSubscriptionRecoveryPolicy/>
</subscriptionRecoveryPolicy>
-->
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>

<!-- Use the following to configure how ActiveMQ is exposed in JMX -->
<managementContext>
<managementContext createConnector="false" />
</managementContext>

<transportConnectors>
<!--
prefixing a connector with discovery: causes the connector to be
advertiesed over rendezvous
-->
<transportConnector uri="tcp://localhost:61616"
discoveryUri="multicast://default" />
</transportConnectors>

<networkConnectors>
<!-- by default just auto discover the other brokers -->
<networkConnector uri="multicast://default" />
<!--
<networkConnector
uri="static://(tcp://host1:61616,tcp://host2:61616)"/>
-->
</networkConnectors>

<!--
<persistenceAdapter> <amqPersistenceAdapter syncOnWrite="false"
directory="../data" maxFileLength="20 mb" /> </persistenceAdapter>
-->
<!--
Use the following if you wish to configure the journal with JDBC
-->
<!--
<persistenceAdapter> <journaledJDBC
dataDirectory="${activemq.base}/data" dataSource="#postgres-ds"/>
</persistenceAdapter>
-->

<!-- Or if you want to use pure JDBC without a journal -->
<!---->
<persistenceAdapter>
<jdbcPersistenceAdapter dataSource="#mysql-ds" />
</persistenceAdapter>

<!--
<sslContext> <sslContext
keyStore="file:${activemq.base}/conf/broker.ks"
keyStorePassword="password"
trustStore="file:${activemq.base}/conf/broker.ts"
trustStorePassword="password"/> </sslContext>
-->

<!--
The maximum about of space the broker will use before slowing down
producers
-->
<systemUsage>
<systemUsage>
<memoryUsage>
<memoryUsage limit="20 mb" />
</memoryUsage>
<storeUsage>
<storeUsage limit="1 gb" name="foo" />
</storeUsage>
<tempUsage>
<tempUsage limit="100 mb" />
</tempUsage>
</systemUsage>
</systemUsage>

<!--
The transport connectors ActiveMQ will listen to
<transportConnectors> <transportConnector name="openwire"
uri="tcp://localhost:61616" discoveryUri="multicast://default" />
<transportConnector name="ssl" uri="ssl://localhost:61617" />
<transportConnector name="stomp" uri="stomp://localhost:61613" />
<transportConnector name="xmpp" uri="xmpp://localhost:61222" />
</transportConnectors>
-->
</broker>

<!--
** Lets deploy some Enterprise Integration Patterns inside the
ActiveMQ Message Broker ** For more details see ** **
http://activemq.apache.org/enterprise-integration-patterns.html
-->
<!--
<camelContext id="camel"
xmlns="http://activemq.apache.org/camel/schema/spring">

<package>org.foo.bar</package> <route> <from uri="activemq:example.A"
/> <to uri="activemq:example.B" /> </route> </camelContext>
-->
<!--
** Lets configure some Camel endpoints ** **
http://activemq.apache.org/camel/components.html
-->

<!--
configure the camel activemq component to use the current broker <bean
id="activemq"
class="org.apache.activemq.camel.component.ActiveMQComponent">
<property name="connectionFactory"> <bean
class="org.apache.activemq.ActiveMQConnectionFactory"> <property
name="brokerURL"
value="vm://localhost?create=false&waitForStart=10000" />
<property name="userName" value="${activemq.username}" /> <property
name="password" value="${activemq.password}" /> </bean> </property>
</bean>
-->

<!--
Uncomment to create a command agent to respond to message based admin
commands on the ActiveMQ.Agent topic
-->
<!--
<commandAgent xmlns="http://activemq.apache.org/schema/core"
brokerUrl="vm://localhost" username="${activemq.username}"
password="${activemq.password}"/>
-->

<!--
An embedded servlet engine for serving up the Admin console <jetty
xmlns="http://mortbay.com/schemas/jetty/1.0"> <connectors>
<nioConnector port="8161" /> </connectors> <handlers> <webAppContext
contextPath="/admin" resourceBase="${activemq.base}/webapps/admin"
logUrlOnStart="true" /> <webAppContext contextPath="/demo"
resourceBase="${activemq.base}/webapps/demo" logUrlOnStart="true" />
<webAppContext contextPath="/fileserver"
resourceBase="${activemq.base}/webapps/fileserver"
logUrlOnStart="true" /> </handlers> </jetty>
-->
<!--
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:3306/mydb?characterEncoding=utf-8&relaxAutoCommit=true" />
<property name="username" value="root" />
<property name="password" value="root" />
<property name="maxActive" value="200" />
<property name="poolPreparedStatements" value="true" />
</bean>

<!-- Oracle DataSource Sample Setup -->
<!--
<bean id="oracle-ds" class="org.apache.commons.dbcp.BasicDataSource"
destroy-method="close"> <property name="driverClassName"
value="oracle.jdbc.driver.OracleDriver"/> <property name="url"
value="jdbc:oracle:thin:@localhost:1521:AMQDB"/> <property
name="username" value="scott"/> <property name="password"
value="tiger"/> <property name="maxActive" value="200"/> <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 -->
  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
1 目标检测的定义 目标检测(Object Detection)的任务是找出图像中所有感兴趣的目标(物体),确定它们的类别和位置,是计算机视觉领域的核心问题之一。由于各类物体有不同的外观、形状和姿态,加上成像时光照、遮挡等因素的干扰,目标检测一直是计算机视觉领域最具有挑战性的问题。 目标检测任务可分为两个关键的子任务,目标定位和目标分类。首先检测图像中目标的位置(目标定位),然后给出每个目标的具体类别(目标分类)。输出结果是一个边界框(称为Bounding-box,一般形式为(x1,y1,x2,y2),表示框的左上角坐标和右下角坐标),一个置信度分数(Confidence Score),表示边界框中是否包含检测对象的概率和各个类别的概率(首先得到类别概率,经过Softmax可得到类别标签)。 1.1 Two stage方法 目前主流的基于深度学习的目标检测算法主要分为两类:Two stage和One stage。Two stage方法将目标检测过程分为两个阶段。第一个阶段是 Region Proposal 生成阶段,主要用于生成潜在的目标候选框(Bounding-box proposals)。这个阶段通常使用卷积神经网络(CNN)从输入图像中提取特征,然后通过一些技巧(如选择性搜索)来生成候选框。第二个阶段是分类和位置精修阶段,将第一个阶段生成的候选框输入到另一个 CNN 中进行分类,并根据分类结果对候选框的位置进行微调。Two stage 方法的优点是准确度较高,缺点是速度相对较慢。 常见Tow stage目标检测算法有:R-CNN系列、SPPNet等。 1.2 One stage方法 One stage方法直接利用模型提取特征值,并利用这些特征值进行目标的分类和定位,不需要生成Region Proposal。这种方法的优点是速度快,因为省略了Region Proposal生成的过程。One stage方法的缺点是准确度相对较低,因为它没有对潜在的目标进行预先筛选。 常见的One stage目标检测算法有:YOLO系列、SSD系列和RetinaNet等。 2 常见名词解释 2.1 NMS(Non-Maximum Suppression) 目标检测模型一般会给出目标的多个预测边界框,对成百上千的预测边界框都进行调整肯定是不可行的,需要对这些结果先进行一个大体的挑选。NMS称为非极大值抑制,作用是从众多预测边界框中挑选出最具代表性的结果,这样可以加快算法效率,其主要流程如下: 设定一个置信度分数阈值,将置信度分数小于阈值的直接过滤掉 将剩下框的置信度分数从大到小排序,选中值最大的框 遍历其余的框,如果和当前框的重叠面积(IOU)大于设定的阈值(一般为0.7),就将框删除(超过设定阈值,认为两个框的里面的物体属于同一个类别) 从未处理的框中继续选一个置信度分数最大的,重复上述过程,直至所有框处理完毕 2.2 IoU(Intersection over Union) 定义了两个边界框的重叠度,当预测边界框和真实边界框差异很小时,或重叠度很大时,表示模型产生的预测边界框很准确。边界框A、B的IOU计算公式为: 2.3 mAP(mean Average Precision) mAP即均值平均精度,是评估目标检测模型效果的最重要指标,这个值介于0到1之间,且越大越好。mAP是AP(Average Precision)的平均值,那么首先需要了解AP的概念。想要了解AP的概念,还要首先了解目标检测中Precision和Recall的概念。 首先我们设置置信度阈值(Confidence Threshold)和IoU阈值(一般设置为0.5,也会衡量0.75以及0.9的mAP值): 当一个预测边界框被认为是True Positive(TP)时,需要同时满足下面三个条件: Confidence Score > Confidence Threshold 预测类别匹配真实值(Ground truth)的类别 预测边界框的IoU大于设定的IoU阈值 不满足条件2或条件3,则认为是False Positive(FP)。当对应同一个真值有多个预测结果时,只有最高置信度分数的预测结果被认为是True Positive,其余被认为是False Positive。 Precision和Recall的概念如下图所示: Precision表示TP与预测边界框数量的比值 Recall表示TP与真实边界框数量的比值 改变不同的置信度阈值,可以获得多组Precision和Recall,Recall放X轴,Precision放Y轴,可以画出一个Precision-Recall曲线,简称P-R
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值