jboss7部署MDB

最新推荐文章于 2021-02-27 23:59:00 发布
最新推荐文章于 2021-02-27 23:59:00 发布
阅读量764 收藏
点赞数
文章标签： jboss jms ejb 3.0 java ee

转自http://theopentutorials.com/examples/java-ee/ejb3/how-to-create-ejb3-mdb-project-in-eclipse-jboss-7-1/
Environment Used

  • JDK 6 (Java SE 6)
  • JMS Sender/Client – Servlet 2.5 API
  • JMS Consumer – EJB 3.0 Message Driven Bean (MDB)
  • Eclipse Indigo IDE for Java EE Developers (3.7.1)
  • JBoss Tools – Core 3.3.0 M5 for Eclipse Indigo (3.7.1)
  • JBoss Application Server (AS) 7.1.0 Final

Setting up development environment:
Read this page for installing and setting up the environment for developing and deploying EJB 3.0 Session bean on JBoss application server.

Project Description

  • We are going to create a simple EJB 3 Message Driven Bean and a Web client (Servlet) which sends messages to the Queue destination.
  • This example explains how to develop, deploy and run EJB3 MDB as a message consumer in JBoss application server.
  • For testing this MDB listener we write a Web client (a servlet) as a message producer which sends a simple text message and an object message.
  • The message driven bean (message consumer) and the Servlet (message producer) are deployed on the same server instance (JBoss AS).

Creating New EJB Project

  • Open Eclipse IDE and create a new EJB project which can be done in three ways,
    • Right click on Project Explorer -> New -> EJB Project
    • File menu -> New -> EJB Project
    • Click on the down arrow on New icon on toolbar -> EJB Project

  • Enter the project name as “FirstMDBProject” and make sure the JBoss 7.1 Runtime has been selected with the EJB 3.0 Module version.
  • This project uses Java 1.6 version. The default Java version in Eclipse Indigo is 1.7 so to change the “Configuration” click on “Modify…” button to make changes.
  • Click Next -> Next -> and Finish.
  • You will see an EJB project in the Project Explorer view.

Creating object message class

  • Right click on ejbModule -> New -> Class
  • Enter the Java package name as com.theopentutorials.mdb.to
  • Enter the Class name as Employee
  • Click “Finish“

Copy the following code:

01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
package com.theopentutorials.mdb.to;
import java.io.Serializable;
public class Employee implements Serializable {
     private int id;
     private String name;
     private String designation;
     private double salary;
     
     public Employee() { }
     
     public Employee( int id, String name, String designation,
             double salary)
     {
         this .id = id;
         this .name = name;
         this .designation = designation;
         this .salary = salary;
     }
     public int getId() {
         return id;
     }
     public void setId( int id) {
         this .id = id;
     }
     public String getName() {
         return name;
     }
     public void setName(String name) {
         this .name = name;
     }
     public String getDesignation() {
         return designation;
     }
     public void setDesignation(String designation) {
         this .designation = designation;
     }
     public double getSalary() {
         return salary;
     }
     public void setSalary( double salary) {
         this .salary = salary;
     }
     @Override
     public String toString() {
         return "Employee [id=" + id + ", name=" + name + ", designation="
                 + designation + ", salary=" + salary + "]" ;
     }
}

Creating Message Driven Bean Consumer

  • Right click on ejbModule -> New -> Message-Driven Bean (EJB 3.x)
  • Enter the Java package name as com.theopentutorials.mdb
  • Enter the Class name as QueueListenerMDB
  • Select the Destination type as Queue
  • Click “Finish“

01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
package com.theopentutorials.mdb;
 
import java.util.Date;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.ObjectMessage;
import javax.jms.TextMessage;
import com.theopentutorials.mdb.to.Employee;
 
@MessageDriven (activationConfig = {
         @ActivationConfigProperty (
         propertyName = "destinationType" , propertyValue = "javax.jms.Queue" ),
         @ActivationConfigProperty (
         propertyName = "destination" , propertyValue = "queue/MyQueue" ) })
public class QueueListenerMDB implements MessageListener {
     public QueueListenerMDB() {
     }
 
     public void onMessage(Message message) {
         try {
             if (message instanceof TextMessage) {
                 System.out.println( "Queue: I received a TextMessage at "
                                 + new Date());
                 TextMessage msg = (TextMessage) message;
                 System.out.println( "Message is : " + msg.getText());
             } else if (message instanceof ObjectMessage) {
                 System.out.println( "Queue: I received an ObjectMessage at "
                                 + new Date());
                 ObjectMessage msg = (ObjectMessage) message;
                 Employee employee = (Employee) msg.getObject();
                 System.out.println( "Employee Details: " );
                 System.out.println(employee.getId());
                 System.out.println(employee.getName());
                 System.out.println(employee.getDesignation());
                 System.out.println(employee.getSalary());
             } else {
                 System.out.println( "Not a valid message for this Queue MDB" );
             }
 
         } catch (JMSException e) {
             e.printStackTrace();
         }
     }
}
  • The activationConfig property of @MessageDriven is an array of ActivationConfigProperty and it should specify the destinationType (Queue or Topic) and destination (Queue/Topic’s JNDI name).
  • In the onMessage() we are receiving two types of message, TextMessage and ObjectMessage.

Configuring messaging services on JBoss AS 7

In the previous version of JBoss AS we had an option to configure the messaging destinations (Queue or Topic) in META-INF/*-service.xml with element. In JBoss AS 7, it is configured in main application server configuration file (standalone.xml) which is found in JBossAS_Home/standalone/configuration.

  • Open standalone.xml and follow the steps below to configure messaging services.

Add entension element

Add

1
< extension module = "org.jboss.as.messaging" />

in the <extensions> element.

Add subsystem element

Add the following <subsystem> inside <profile> element.

01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
< subsystem xmlns = "urn:jboss:domain:messaging:1.1" >
             < hornetq-server >
                 < persistence-enabled >true</ persistence-enabled >
                 < journal-file-size >102400</ journal-file-size >
                 < journal-min-files >2</ journal-min-files >
 
                 < connectors >
                     < netty-connector name = "netty" socket-binding = "messaging" />
                     < netty-connector name = "netty-throughput" socket-binding = "messaging-throughput" >
                         < param key = "batch-delay" value = "50" />
                     </ netty-connector >
                     < in-vm-connector name = "in-vm" server-id = "0" />
                 </ connectors >
 
                 < acceptors >
                     < netty-acceptor name = "netty" socket-binding = "messaging" />
                     < netty-acceptor name = "netty-throughput" socket-binding = "messaging-throughput" >
                         < param key = "batch-delay" value = "50" />
                         < param key = "direct-deliver" value = "false" />
                     </ netty-acceptor >
                     < in-vm-acceptor name = "in-vm" server-id = "0" />
                 </ acceptors >
 
                 < security-settings >
                     < security-setting match = "#" >
                         < permission type = "send" roles = "guest" />
                         < permission type = "consume" roles = "guest" />
                         < permission type = "createNonDurableQueue" roles = "guest" />
                         < permission type = "deleteNonDurableQueue" roles = "guest" />
                     </ security-setting >
                 </ security-settings >
 
                 < address-settings >
                     < address-setting match = "#" >
                         < dead-letter-address >jms.queue.DLQ</ dead-letter-address >
                         < expiry-address >jms.queue.ExpiryQueue</ expiry-address >
                         < redelivery-delay >0</ redelivery-delay >
                         < max-size-bytes >10485760</ max-size-bytes >
                         < address-full-policy >BLOCK</ address-full-policy >
                         < message-counter-history-day-limit >10</ message-counter-history-day-limit >
                     </ address-setting >
                 </ address-settings >
 
                 < jms-connection-factories >
                     < connection-factory name = "InVmConnectionFactory" >
                         < connectors >
                             < connector-ref connector-name = "in-vm" />
                         </ connectors >
                         < entries >
                             < entry name = "java:/ConnectionFactory" />
                         </ entries >
                     </ connection-factory >
                     < connection-factory name = "RemoteConnectionFactory" >
                         < connectors >
                             < connector-ref connector-name = "netty" />
                         </ connectors >
                         < entries >
                             < entry name = "RemoteConnectionFactory" />
                             < entry name = "java:jboss/exported/jms/RemoteConnectionFactory" />
                         </ entries >
                     </ connection-factory >
                     < pooled-connection-factory name = "hornetq-ra" >
                         < transaction mode = "xa" />
                         < connectors >
                             < connector-ref connector-name = "in-vm" />
                         </ connectors >
                         < entries >
                             < entry name = "java:/JmsXA" />
                         </ entries >
                     </ pooled-connection-factory >
                 </ jms-connection-factories >
 
                 < jms-destinations >
                     < jms-queue name = "testQueue" >
                         < entry name = "queue/MyQueue" />
                     </ jms-queue >
                     < jms-topic name = "testTopic" >
                         < entry name = "topic/MyTopic" />
                     </ jms-topic >
                 </ jms-destinations >
             </ hornetq-server >
         </ subsystem >

The entry name for jms-queue should match the destination activation config property in @MessageDriven.

Add messaging port

In <socket-binding-group> add these two elements

1
2
< socket-binding name = "messaging" port = "5445" />
< socket-binding name = "messaging-throughput" port = "5455" />

Add MDB Resource Adapter Reference

Under <subsystem xmlns=”urn:jboss:domain:ejb3:1.2″> add this <mdb> element

1
2
3
4
< mdb >
     < resource-adapter-ref resource-adapter-name = "hornetq-ra" />
     < bean-instance-pool-ref pool-name = "mdb-strict-max-pool" />
</ mdb >

Deploying EJB project

  • Now we need to deploy the EJB project “FirstMDBProject” on server..
  • Deploying the project can be done in two ways,
    • Right click on the EJB project -> Run As -> Run On Server. Select the existing “JBoss 7.1 Runtime Server” and click Finish.
    • Right click on “JBoss 7.1 Runtime Server” available in Servers view -> Add and Remove… -> Select the EJB JAR file from the left pane and click Add-> and then Finish.

Start/Restart the Server

Right click on “JBoss 7.1 Runtime Server” from Servers view and click on Start if it has not yet been started.

If the project is deployed properly with global JNDI mapping then you will see the following message in the console.

Bound messaging object to jndi name java:/queue/MyQueue
Started message driven bean ‘QueueListenerMDB’ with ‘hornetq-ra’ resource adapter
Deployed “FirstMDBProject.jar”

Creating JMS client (Dynamic Web Project)

  • The next step is to write a Web Client (a Servlet) which produces the message and sends to the Queue.
  • The servlet uses JNDI to lookup ConnectionFactory and the Queue.
  • Creating a new ‘Dynamic Web project’ can be done in three ways,
    • Right click on Project Explorer -> New -> Dynamic Web Project
    • File menu -> New -> Dynamic Web Project
    • Click on the down arrow on New icon on toolbar -> Dynamic Web Project

  • Enter the project name as “MDBWebClient” and make sure the JBoss 7.1 Runtime has been selected with the Dynamic web module version as 2.5.
  • This project uses Java 1.6 version. The default Java version in Eclipse Indigo is 1.7 so to change the “Configuration” click on “Modify…” button to make changes.
  • Click “Next” -> “Next” -> and “Finish”.
  • You will see the Dynamic web project in the “Project Explorer” view.

To send object message servlet needs Employee class which we have created in FirstMDBProject.

Creating JAR file

  • Right click on Employee.java file in FirstMDBProject -> Export.
  • Expand Java folder and select “JAR file” and click Next.
  • Click on Browse… and enter the file name and Finish.

Now copy the created JAR file and paste it in MDBWebClient/WebContent/WEB-INF/lib folder.

Creating Servlet class

  • Right click on src or Project -> New -> Servlet

  • Enter the Java package name as com.theopentutorials.servlets
  • Enter the Class name as ServletMessageProducer
  • Click “Finish“

In the doGet() method copy the following code.

01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
package com.theopentutorials.servlets;
 
import java.io.IOException;
import java.io.PrintWriter;
import javax.jms.ObjectMessage;
import javax.jms.Queue;
import javax.jms.QueueConnection;
import javax.jms.QueueConnectionFactory;
import javax.jms.QueueSender;
import javax.jms.QueueSession;
import javax.jms.TextMessage;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
 
import com.theopentutorials.mdb.to.Employee;
 
public class ServletMessageProducer extends HttpServlet {
     private static final long serialVersionUID = 1L;
        
     public ServletMessageProducer() {
         super ();
     }
 
     protected void doGet(HttpServletRequest request,
             HttpServletResponse response)
             throws ServletException, IOException {
         final String QUEUE_LOOKUP = "queue/MyQueue" ;
         final String CONNECTION_FACTORY = "ConnectionFactory" ;
         
         PrintWriter out = response.getWriter();
         try {
             Context context = new InitialContext();
             QueueConnectionFactory factory =
                 (QueueConnectionFactory)context.lookup(CONNECTION_FACTORY);
             QueueConnection connection = factory.createQueueConnection();
             QueueSession session =
                 connection.createQueueSession( false ,
                     QueueSession.AUTO_ACKNOWLEDGE);
             
             Queue queue = (Queue)context.lookup(QUEUE_LOOKUP);
             QueueSender sender = session.createSender(queue);
             
             //1. Sending TextMessage to the Queue
             TextMessage message = session.createTextMessage();
             message.setText( "Hello EJB3 MDB Queue!!!" );
             sender.send(message);
             out.println( "1. Sent TextMessage to the Queue" );
             
             //2. Sending ObjectMessage to the Queue
             ObjectMessage objMsg = session.createObjectMessage();
             
             Employee employee = new Employee();
             employee.setId( 2163 );
             employee.setName( "Kumar" );
             employee.setDesignation( "CTO" );
             employee.setSalary( 100000 );
             objMsg.setObject(employee);                    
             sender.send(objMsg);
             out.println( "2. Sent ObjectMessage to the Queue" );
             
             session.close();
         } catch (Exception e){e.printStackTrace();}
     }
}

Deploying Dynamic Web Project

  • Now we need to deploy the servlet’s project “MDBWebClient” on server.
  • Deploying the project can be done in two ways,
    • Right click on the “MDBWebClient” Dynamic Web project -> Run As -> Run On Server. Select the existing “JBoss 7.1 Runtime Server” and click Finish.
    • Right click on “JBoss 7.1 Runtime Server” available in Servers view -> Add and Remove… -> Select the WAR file from the left pane and click Add-> and then Finish.

Start/Restart the Server

  • Right click on “JBoss 7.1 Runtime Server” from Servers view and click on Start if it has not yet been started.
  • If the projects are deployed properly then you will see the following message in the console.

Deployed “MDBWebClient.war”
Deployed “FirstMDBProject.jar”

Folder Structure

The figure below shows the final directory structure of EJB project “FirstMDBProject”.

The figure below shows the final directory structure of Dynamic Web project “MDBWebClient”

Run the Servlet

Eclipse Internal Web Browser will display the following output

JBoss Runtime Server Console will display the following output.

[stdout] Queue: I received a TextMessage at Fri Feb 17 18:03:41 IST 2012
[stdout] Message is : Hello EJB3 MDB Queue!!!
[stdout] Queue: I received an ObjectMessage at Fri Feb 17 18:03:41 IST 2012
[stdout] Employee Details:
[stdout] 2163
[stdout] Kumar
[stdout] CTO
[stdout] 100000.0

lcullen
关注
Jboss Ejb MDB
rosonsandy的专栏
04-14 1990
 对jms不是很熟悉，弄了几天终于有了点思路。这里有两个程序、增加了个queue-example-service.xml配置文件很简单，复杂点的在以后在说。  package org.jboss.tutorial.mdb.bean; import javax.ejb.MessageDriven;import javax.ejb.ActivationConfigProperty;import jav
MDB的配置与开发
IT人生
03-09 2904
这里我的环境是MyEclipse8.0 + WebLogic10.3 + Ubuntu9.10,EJB的开发其实与这三个环境没有关系，我最早也是在WindowsVista + MyEclipse6.0 + WebLogic10.3上开发成功的，关于Weblogic配置JMS服务大家可以去搜一下，有好多，这里主要是在环境都OK的基础上配置开发MDB，首先是我的MDB代码：/** * 测试
JBOSS 6.0 中 使用 MDB
wy100304441的专栏
09-02 395
MDB: import javax.jms.JMSException; import javax.jms.Message; import javax.jms.MessageListener; import javax.jms.TextMessage; i
你的JBoss跑不通尚学堂讲座中的MDB(queue)的例子？
jeff2033333的博客
05-30 107
CSDN论坛上看见好几个人都在问关于李腾飞版EJB3.0讲座中的MDB例子，为什么在他们的JBoss版本下跑不通，主要是“jms not bound” 这个问题。   有一些“高手”给出了一个方案，在/deploy/目录下放置一个 xxx-server.xml 的配置文件，内容是： &lt;?xml version="1.0" encoding="UTF-8" ?&gt; &lt;se...
java.naming.factory.initial_javax.naming.NamingException：JBAS011843：从类加载器实例化InitialContextFactory or...
weixin_34901508的博客
02-27 699
大家好,我在Jboss-as-7.1.1中遇到了一些问题.我正确部署,但当我从客户端发送请求时,我收到错误.我使用的是Jboss-7.1.1,部署文件夹是独立/部署(axis2.war,response.war,SpSpecific.ear,responsecomponet.ear)部署日志： –13:00:51,457 INFO [org.jboss.modules] JBoss Module...
jboss 6.0 上开发 MDB
09-02
在Java企业级应用中，Message Driven Bean (MDB) 是一种特殊类型的Enterprise ...6. 部署MDB到JBoss 6.0服务器。 理解这些基础知识后，你就能在JBoss 6.0上成功开发和使用MDB，实现高效的异步通信和解耦的应用架构。
JBOSS 4.0.5 EJB3.0之MDB (ACTIVEMQ)
03-19
5. **部署**：最后，将MDB的EJB JAR文件和相关的配置文件部署到JBoss服务器上，服务器会自动检测并激活MDB。 在实际应用中，开发者可能还会遇到如事务管理、消息选择器、消息驱动适配器的定制等高级配置。理解这些...
jboss6-jms-chat:添加基于http的简单Java EE 6 MDB和JMS队列生产者
06-01
"jboss6-jms-chat" 这个标题揭示了我们要讨论的是一个与Java EE 6中间件JBoss AS 6相关的项目，它涉及到消息驱动bean（MDB）和Java消息服务（JMS）队列。MDB是Java EE平台中用于处理消息的组件，而JMS则是一种标准...
JBoss 4.0入门与部署指南：从下载到Web服务应用
第7章则探讨容器管理下的持久化问题，这对于任何使用JBoss进行数据持久化管理的开发者来说，都是不可或缺的部分。这部分内容包括了如何利用JBoss的特性来确保数据的可靠存储和恢复。 《JBoss教程.pdf》提供了一个从...
JBoss使用与配置实战指南
"JBOSS使用指南，涵盖了JBOSS的基础使用、配置、部署和JMX原理及应用，以及EJB3.0的使用说明。" JBOSS是一款开源的应用服务器，广泛应用于企业级Java应用的开发和部署。本指南详细介绍了如何入门JBOSS，包括下载...
idea整合jboos_在 idea 中 启动 jboss 后， 没有运行部署（通过idea部署）的ssm项目，打开后项目404...
weixin_39675215的博客
12-19 614
/Users/y/software/wildfly-10.1.0.Final/bin/standalone.shJAVA_OPTS already set in environment; overriding default settings with values: -agentlib:jdwp=transport=dt_socket,address=127.0.0.1:54668,suspen...
jboss全局配置１
mengshi12的专栏
09-04 1330
jdbc:h2:mem:test;DB_CLOSE_DELAY=-1                     h2                                             sa                         sa                                                         
jboss jms 配置
baduxiaobang的专栏
04-09 207
在standalone.xml中 &lt;extensions&gt; ... &lt;extension module="org.jboss.as.messaging"/&gt; ... &lt;/extensions&gt; ... &lt;subsystem xmlns="urn:jboss:domain:messaging:1.1"&gt; &lt;hornetq-ser
JBoss EAP应用服务器部署方法和JBoss 开发JMS消息服务小例子
weixin_34097242的博客
07-13 187
2019独角兽企业重金招聘Python工程师标准>>> ...
（转）JBOSS7.1下开发JMS(HoernetQ)的示例DEMO
peng4602的专栏
09-16 245
1.首先是要add-user.bat,添加用户,在jboss的bin目录下运行add-user.bat   角色是guest不是gutst。照样添加就可以了.之后就是一路yes敲下去. 2.替换XML文件,CMD命令我用的不熟,折腾半天也没运行起JBOSS,伤心之余就跑去更换JBOSS的启动使用的XML文件了.D:\software\jboss-as-7.1.3.Final\stan...
jboss配置ejb容器_JBoss AS 7 EJB3池配置
最佳 Java 编程
05-30 455
jboss配置ejb容器 现在已经发布了AS 7.0.1，下面让我们看看有哪些新的EJB3功能可用。 就像我在上一篇文章中提到的那样 ，AS 7.0.1现在允许您为无状态会话bean和MDB配置池。 当前，我们允许在子系统级别配置池，这意味着该池将适用于服务器上部署的所有Bean。 在一些即将发布的版本中，我们将允许在单个部署和单个Bean级别上配置池。 现在，让我们看看子系统级别的配置。 ...
JBOSS6.2 + MQ 集群配置
weixin_30731305的博客
06-02 189
一、配置MQ集群环境，首先是多连接配置在JBOSS的configuration下面的standalone.xml文件下 a) 添加IBM的resource-adapters 集群模式下就会配置多个数据源 <subsystem xmlns="urn:jboss:domain:resource-adapters:1.1"> <r...
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值