• Post Reply Bookmark Topic Watch Topic
  • New Topic

EJB MDB Queue project  RSS feed

 
sai rama krishna
Ranch Hand
Posts: 524
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I have create EJB project and wrote MDB in that as below



I configured the WQueue in JBoss 5.2 by going to

C:\softwares\jboss-5.0.0.CR2\jboss-5.0.0.CR2\server\default\deploy\messaging

And modified
destinations-services.xml as below by creating new Queue with name GPQueue2



I create application client project and wrote client java file as below



I got console output as below

12:16:04,692 INFO [ServerImpl] Starting JBoss (Microcontainer)...
12:16:04,695 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR2 (build: SVNTag=JBoss_5_0_0_CR2 date=200809171046)
12:16:04,702 INFO [ServerImpl] Home Dir: C:\softwares\jboss-5.0.0.CR2\jboss-5.0.0.CR2
12:16:04,702 INFO [ServerImpl] Home URL: file:/C:/softwares/jboss-5.0.0.CR2/jboss-5.0.0.CR2/
12:16:04,703 INFO [ServerImpl] Library URL: file:/C:/softwares/jboss-5.0.0.CR2/jboss-5.0.0.CR2/lib/
12:16:04,704 INFO [ServerImpl] Patch URL: null
12:16:04,705 INFO [ServerImpl] Server Name: default
12:16:04,705 INFO [ServerImpl] Server Home Dir: C:\softwares\jboss-5.0.0.CR2\jboss-5.0.0.CR2\server\default
12:16:04,705 INFO [ServerImpl] Server Home URL: file:/C:/softwares/jboss-5.0.0.CR2/jboss-5.0.0.CR2/server/default/
12:16:04,706 INFO [ServerImpl] Server Data Dir: C:\softwares\jboss-5.0.0.CR2\jboss-5.0.0.CR2\server\default\data
12:16:04,706 INFO [ServerImpl] Server Temp Dir: C:\softwares\jboss-5.0.0.CR2\jboss-5.0.0.CR2\server\default\tmp
12:16:04,707 INFO [ServerImpl] Server Config URL: file:/C:/softwares/jboss-5.0.0.CR2/jboss-5.0.0.CR2/server/default/conf/
12:16:04,707 INFO [ServerImpl] Server Library URL: file:/C:/softwares/jboss-5.0.0.CR2/jboss-5.0.0.CR2/server/default/lib/
12:16:04,708 INFO [ServerImpl] Root Deployment Filename: jboss-service.xml
12:16:06,198 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/softwares/jboss-5.0.0.CR2/jboss-5.0.0.CR2/server/default/conf/bootstrap.xml
12:16:07,833 INFO [CopyMechanism] VFS temp dir: C:\softwares\jboss-5.0.0.CR2\jboss-5.0.0.CR2\server\default\tmp
12:16:07,876 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
12:16:10,446 INFO [ServerInfo] Java version: 1.7.0_02,Oracle Corporation
12:16:10,446 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 22.0-b10,Oracle Corporation
12:16:10,447 INFO [ServerInfo] OS-System: Windows 7 6.1,amd64
12:16:10,523 INFO [JMXKernel] Legacy JMX core initialized
12:16:12,962 INFO [MetaDataAwareProfile] Using profile root:C:\softwares\jboss-5.0.0.CR2\jboss-5.0.0.CR2\server\default
12:16:15,718 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
12:16:31,479 WARN [HackClassloaderMetaDataDeployer] FIXME Using loader repository config: jboss.console:sar=console-mgr.sar for vfsfile:/C:/softwares/jboss-5.0.0.CR2/jboss-5.0.0.CR2/server/default/deploy/management/console-mgr.sar/ use classloading metadata not loader repository config
12:16:33,615 INFO [AspectDeployer] Deploying xml into org.jboss.aop.AspectManager@27fcd3fe for BaseClassLoader@7f7d499e{vfsfile:/C:/softwares/jboss-5.0.0.CR2/jboss-5.0.0.CR2/server/default/deploy/ejb3-interceptors-aop.xml}
12:16:47,692 WARN [EjbMetadataJndiPolicyDecoratorDeployer] Defaulting to DefaultJndiBindingPolicy of "org.jboss.metadata.ejb.jboss.jndipolicy.plugins.BasicJndiBindingPolicy" for Session Bean FirstDemoEJB
12:16:52,327 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
12:16:52,450 INFO [MailService] Mail Service bound to java:/Mail
12:16:53,215 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
12:16:53,215 INFO [NativeServerConfig] 3.0.3.GA
12:16:54,230 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
12:16:54,486 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
12:16:54,486 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
12:16:54,848 INFO [TransactionManagerService] Initializing recovery manager
12:16:55,110 INFO [TransactionManagerService] Recovery manager configured
12:16:55,110 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
12:16:55,158 INFO [TransactionManagerService] Starting transaction recovery manager
12:16:55,796 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.7.0_02\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\QuickTime\QTSystem\;JAVA_HOME\bin;C:\Program Files\apache-maven-3.0.4-bin\apache-maven-3.0.4\bin;.
12:16:55,913 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
12:16:55,920 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
12:16:55,920 INFO [Catalina] Initialization processed in 412 ms
12:16:55,920 INFO [StandardService] Starting service jboss.web
12:16:55,927 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.1.CR7
12:16:56,039 INFO [Catalina] Server startup in 118 ms
12:16:56,145 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war
12:16:57,408 INFO [TomcatDeployment] deploy, ctxPath=/jbossws, vfsUrl=jbossws.sar/jbossws-management.war
12:16:57,567 INFO [TomcatDeployment] deploy, ctxPath=/web-console, vfsUrl=management/console-mgr.sar/web-console.war
12:16:58,177 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/softwares/jboss-5.0.0.CR2/jboss-5.0.0.CR2/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
12:16:58,201 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/softwares/jboss-5.0.0.CR2/jboss-5.0.0.CR2/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
12:16:58,243 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/softwares/jboss-5.0.0.CR2/jboss-5.0.0.CR2/server/default/deploy/jms-ra.rar/META-INF/ra.xml
12:16:58,268 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/softwares/jboss-5.0.0.CR2/jboss-5.0.0.CR2/server/default/deploy/mail-ra.rar/META-INF/ra.xml
12:16:58,315 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/softwares/jboss-5.0.0.CR2/jboss-5.0.0.CR2/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
12:16:58,520 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
12:16:58,652 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
12:16:58,660 INFO [RAMJobStore] RAMJobStore initialized.
12:16:58,661 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
12:16:58,662 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
12:16:58,663 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
12:16:59,618 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'javaefaultDS'
12:17:00,151 WARN [QuartzTimerServiceFactory] sql failed: CREATE TABLE QRTZ_JOB_DETAILS(JOB_NAME VARCHAR(80) NOT NULL, JOB_GROUP VARCHAR(80) NOT NULL, DESCRIPTION VARCHAR(120) NULL, JOB_CLASS_NAME VARCHAR(128) NOT NULL, IS_DURABLE VARCHAR(1) NOT NULL, IS_VOLATILE VARCHAR(1) NOT NULL, IS_STATEFUL VARCHAR(1) NOT NULL, REQUESTS_RECOVERY VARCHAR(1) NOT NULL, JOB_DATA BINARY NULL, PRIMARY KEY (JOB_NAME,JOB_GROUP))
12:17:00,225 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
12:17:00,230 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
12:17:00,231 INFO [JobStoreCMT] Using db table-based data access locking (synchronization).
12:17:00,249 INFO [JobStoreCMT] Removed 0 Volatile Trigger(s).
12:17:00,249 INFO [JobStoreCMT] Removed 0 Volatile Job(s).
12:17:00,250 INFO [JobStoreCMT] JobStoreCMT initialized.
12:17:00,250 INFO [StdSchedulerFactory] Quartz scheduler 'JBossEJB3QuartzScheduler' initialized from an externally provided properties instance.
12:17:00,251 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
12:17:00,255 INFO [JobStoreCMT] Freed 0 triggers from 'acquired' / 'blocked' state.
12:17:00,269 INFO [JobStoreCMT] Recovering 0 jobs that were in-progress at the time of the last shut-down.
12:17:00,269 INFO [JobStoreCMT] Recovery complete.
12:17:00,269 INFO [JobStoreCMT] Removed 0 'complete' triggers.
12:17:00,270 INFO [JobStoreCMT] Removed 0 stale fired job entries.
12:17:00,274 INFO [QuartzScheduler] Scheduler JBossEJB3QuartzScheduler_$_NON_CLUSTERED started.
12:17:00,604 INFO [ServerPeer] JBoss Messaging 1.4.1.CR1 server [0] started
12:17:00,773 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
12:17:00,848 INFO [QueueService] Queue[/queue/ExpiryQueue2] started, fullSize=200000, pageSize=2000, downCacheSize=2000
12:17:01,026 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
12:17:01,028 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@62ec1663 started
12:17:01,038 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
12:17:01,040 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
12:17:01,041 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@130ac6d3 started
12:17:01,043 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
12:17:01,043 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
12:17:01,053 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
12:17:01,054 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@28835069 started
12:17:01,062 INFO [QueueService] Queue[/queue/GPQueue2] started, fullSize=200000, pageSize=2000, downCacheSize=2000
12:17:01,245 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
12:17:01,260 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war
12:17:01,416 INFO [TomcatDeployment] deploy, ctxPath=/TestEJB, vfsUrl=TestEJB.war
12:17:01,536 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war
12:17:02,640 INFO [JBossASKernel] Created KernelDeployment for: DemoEJB.jar
12:17:02,645 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=DemoEJB.jar,jar=DemoEJB.jar,name=FirstDemoEJB,service=EJB3
12:17:02,646 INFO [JBossASKernel] with dependencies:
12:17:02,646 INFO [JBossASKernel] and demands:
12:17:02,646 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
12:17:02,646 INFO [JBossASKernel] and supplies:
12:17:02,646 INFO [JBossASKernel] jndi:FirstDemoEJB/remote-com.demo.FirstDemoEJBRemote
12:17:02,646 INFO [JBossASKernel] Class:com.demo.FirstDemoEJBRemote
12:17:02,647 INFO [JBossASKernel] jndi:FirstDemoEJB/remote
12:17:02,647 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=DemoEJB.jar,jar=DemoEJB.jar,name=FirstDemoEJB,service=EJB3) to KernelDeployment of: DemoEJB.jar
12:17:03,301 INFO [SessionSpecContainer] Starting jboss.j2ee:ear=DemoEJB.jar,jar=DemoEJB.jar,name=FirstDemoEJB,service=EJB3
12:17:03,322 INFO [EJBContainer] STARTED EJB: com.demo.FirstDemoEJB ejbName: FirstDemoEJB
12:17:03,329 WARN [SessionSpecContainer] Populating JBoss-specific annotation metadata manually until done by deployers: jboss.j2ee:ear=DemoEJB.jar,jar=DemoEJB.jar,name=FirstDemoEJB,service=EJB3
12:17:03,631 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
12:17:03,684 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
12:17:03,706 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.CR2 (build: SVNTag=JBoss_5_0_0_CR2 date=200809171046)] Started in 58s:993ms
12:17:08,566 WARN [EjbMetadataJndiPolicyDecoratorDeployer] Defaulting to DefaultJndiBindingPolicy of "org.jboss.metadata.ejb.jboss.jndipolicy.plugins.BasicJndiBindingPolicy" for Session Bean MDBQueue01
12:17:08,660 INFO [JBossASKernel] Created KernelDeployment for: GpMDBQProj.jar
12:17:08,660 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=GpMDBQProj.jar,jar=GpMDBQProj.jar,name=MDBQueue01,service=EJB3
12:17:08,660 INFO [JBossASKernel] with dependencies:
12:17:08,661 INFO [JBossASKernel] and demands:
12:17:08,661 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
12:17:08,661 INFO [JBossASKernel] and supplies:
12:17:08,661 INFO [JBossASKernel] jndi:null
12:17:08,661 INFO [JBossASKernel] Class:javax.jms.MessageListener
12:17:08,661 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=GpMDBQProj.jar,jar=GpMDBQProj.jar,name=MDBQueue01,service=EJB3) to KernelDeployment of: GpMDBQProj.jar
12:17:08,804 INFO [EJBContainer] STARTED EJB: com.gp.MDBQueue01 ejbName: MDBQueue01
13:09:12,609 WARN [MicroSocketClientInvoker] numberOfRetries is no longer used
13:09:13,938 INFO [ServerSessionEndpoint] Received send for ID:JBM-d0c67d68-89e5-46bd-8454-c940d505dc80 reliable: true
13:09:13,990 INFO [ServerSessionEndpoint] Done send
13:09:14,106 WARN [LifecycleCallbacks] EJBTHREE-1480: LifecycleCallbackStack has not been defined for domain 'Message Driven Bean'
13:09:14,226 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
13:09:14,230 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
13:09:14,238 WARN [InterceptorRegistry] applicable interceptors is non-existent for public void com.gp.MDBQueue01.onMessage(javax.jms.Message)
13:09:14,257 WARN [InterceptorRegistry] applicable interceptors is non-existent for public void com.gp.MDBQueue01.onMessage(javax.jms.Message)
13:09:14,277 INFO [STDOUT] GpMDBQ onMessage method received msgdelegator->JBossMessage[22429482253320192]:PERSISTENT, deliveryId=0






I expected to see something like Header and then body with below message

msg from mdbqclient main class



Please advise on how to fix this issue.

Any ideas, links, resources, sample code highly appreciated. thanks in advance
mdbClient.jpg
[Thumbnail for mdbClient.jpg]
mdb project structure
 
Gangadhara Rao Duvvarapu
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Try the below link which has both MDB Server side and Client Side code which will be helpful for you.

http://grwebservice.blogspot.in/2009/06/message-driven-bean.html
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!