10 Replies Latest reply on Oct 22, 2008 10:57 AM by Peter Johnson Branched to a new discussion.

    Errors during deployment of EJB3 application into JBoss 5 R2

    ilango gurusamy Novice

      On deploying my Ear file (containing EJB 3 MDBs with annotations, Servlet, Session Facade) into Jboss 5 R2 from Netbeans 6.1, I get the following errors: This is preventing my application from deploying correctly. I (naively perhaps) wrote ejb-jar.xml too and this is included in my EAR file..)
      Any help in sorting out this issue and getting a clean build is gratefully acknowledged. Thanks very much in advance.
      The full stack trace is below:

      11:03:30,584 INFO [ServerImpl] Starting JBoss (Microcontainer)...
      11:03:30,585 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR2 (build: SVNTag=JBoss_5_0_0_CR2 date=200809171139)
      11:03:30,588 INFO [ServerImpl] Home Dir: C:\JBoss5\jboss-5.0.0.CR2
      11:03:30,588 INFO [ServerImpl] Home URL: file:/C:/JBoss5/jboss-5.0.0.CR2/
      11:03:30,589 INFO [ServerImpl] Library URL: file:/C:/JBoss5/jboss-5.0.0.CR2/lib/
      11:03:30,589 INFO [ServerImpl] Patch URL: null
      11:03:30,590 INFO [ServerImpl] Server Name: default
      11:03:30,691 INFO [ServerImpl] Server Home Dir: C:\JBoss5\jboss-5.0.0.CR2\server\default
      11:03:30,692 INFO [ServerImpl] Server Home URL: file:/C:/JBoss5/jboss-5.0.0.CR2/server/default/
      11:03:30,692 INFO [ServerImpl] Server Data Dir: C:\JBoss5\jboss-5.0.0.CR2\server\default\data
      11:03:30,692 INFO [ServerImpl] Server Temp Dir: C:\JBoss5\jboss-5.0.0.CR2\server\default\tmp
      11:03:30,692 INFO [ServerImpl] Server Config URL: file:/C:/JBoss5/jboss-5.0.0.CR2/server/default/conf/
      11:03:30,692 INFO [ServerImpl] Server Library URL: file:/C:/JBoss5/jboss-5.0.0.CR2/server/default/lib/
      11:03:31,189 INFO [ServerImpl] Root Deployment Filename: jboss-service.xml
      11:03:31,841 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/JBoss5/jboss-5.0.0.CR2/server/default/conf/bootstrap.xml
      11:03:32,747 INFO [CopyMechanism] VFS temp dir: C:\JBoss5\jboss-5.0.0.CR2\server\default\tmp
      11:03:32,758 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
      11:03:35,197 INFO [ServerInfo] Java version: 1.6.0_01,Sun Microsystems Inc.
      11:03:35,198 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0_01-b06,Sun Microsystems Inc.
      11:03:35,198 INFO [ServerInfo] OS-System: Windows Vista 6.0,x86
      11:03:35,239 INFO [JMXKernel] Legacy JMX core initialized
      11:03:37,413 INFO [MetaDataAwareProfile] Using profile root:C:\JBoss5\jboss-5.0.0.CR2\server\default
      11:03:39,167 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
      11:03:50,820 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DCQueueing2.ear state=Not Installed mode=Manual requiredState=Parse
      org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DCQueueing2.ear/DCQueueing2-ejb.jar
       at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
       at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:343)
       at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:303)
       at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:275)
       at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:236)
       at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1285)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1003)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1056)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:944)
       at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
       at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
       at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:627)
       at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
       at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:265)
       at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:143)
       at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:409)
       at org.jboss.Main.boot(Main.java:209)
       at org.jboss.Main$1.run(Main.java:544)
       at java.lang.Thread.run(Thread.java:619)
      Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element type "messaging-type" must be declared. @ vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DCQueueing2.ear/DCQueueing2-ejb.jar/META-INF/ejb-jar.xml[9,26]
       at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
       at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
       at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199)
       at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170)
       at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
       at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
       at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256)
       at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188)
       at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:329)
       ... 23 more
      Caused by: org.xml.sax.SAXException: Element type "messaging-type" must be declared. @ vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DCQueueing2.ear/DCQueueing2-ejb.jar/META-INF/ejb-jar.xml[9,26]
       at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:426)
       at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
       at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
       at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
       at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
       at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
       at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
       at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
       at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
       at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
       at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
       at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
       at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
       at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
       at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
       at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
       ... 31 more
      11:03:51,308 WARN [HackClassloaderMetaDataDeployer] FIXME Using loader repository config: jboss.console:sar=console-mgr.sar for vfsfile:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/management/console-mgr.sar/ use classloading metadata not loader repository config
      11:03:51,817 INFO [AspectDeployer] Deploying xml into org.jboss.aop.AspectManager@17cdd50 for BaseClassLoader@13f25e3{vfsfile:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/ejb3-interceptors-aop.xml}
      11:04:07,369 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
      11:04:07,525 INFO [MailService] Mail Service bound to java:/Mail
      11:04:08,579 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
      11:04:08,579 INFO [NativeServerConfig] 3.0.3.GA
      11:04:09,845 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.
      11:04:10,133 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
      11:04:10,133 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
      11:04:11,024 INFO [TransactionManagerService] Initializing recovery manager
      11:04:11,265 INFO [TransactionManagerService] Recovery manager configured
      11:04:11,265 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
      11:04:11,322 INFO [TransactionManagerService] Starting transaction recovery manager
      11:04:11,963 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\jdk1.6.0_01\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\jdk1.6.0_01\bin;C:\jdk1.6.0_01\dev;C:\tomcat55\apache-tomcat-5.5.17\bin;C:\Windows\System32;C:\Program Files\MySQL\MySQL Server 5.0\bin;C:\jdk1.6.0_01\bin;C:\jdk1.6.0_01\dev;C:\tomcat55\apache-tomcat-5.5.17\bin;C:\Windows\System32
      11:04:12,074 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8082
      11:04:12,080 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
      11:04:12,080 INFO [Catalina] Initialization processed in 408 ms
      11:04:12,080 INFO [StandardService] Starting service jboss.web
      11:04:12,088 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.1.CR7
      11:04:12,170 INFO [Catalina] Server startup in 90 ms
      11:04:12,301 INFO [TomcatDeployment] deploy, ctxPath=/jbossws, vfsUrl=jbossws.sar/jbossws-management.war
      11:04:13,472 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war
      11:04:13,654 INFO [TomcatDeployment] deploy, ctxPath=/web-console, vfsUrl=management/console-mgr.sar/web-console.war
      11:04:14,276 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
      11:04:14,293 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
      11:04:14,317 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/jms-ra.rar/META-INF/ra.xml
      11:04:14,334 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/mail-ra.rar/META-INF/ra.xml
      11:04:14,599 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
      11:04:14,751 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
      11:04:14,790 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
      11:04:14,795 INFO [RAMJobStore] RAMJobStore initialized.
      11:04:14,796 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
      11:04:15,072 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
      11:04:15,073 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
      11:04:16,063 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
      11:04:16,432 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))
      11:04:16,513 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
      11:04:16,575 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
      11:04:16,576 INFO [JobStoreCMT] Using db table-based data access locking (synchronization).
      11:04:16,617 INFO [JobStoreCMT] Removed 0 Volatile Trigger(s).
      11:04:16,617 INFO [JobStoreCMT] Removed 0 Volatile Job(s).
      11:04:16,618 INFO [JobStoreCMT] JobStoreCMT initialized.
      11:04:16,618 INFO [StdSchedulerFactory] Quartz scheduler 'JBossEJB3QuartzScheduler' initialized from an externally provided properties instance.
      11:04:16,618 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
      11:04:17,080 INFO [JobStoreCMT] Freed 0 triggers from 'acquired' / 'blocked' state.
      11:04:17,082 INFO [JobStoreCMT] Recovering 0 jobs that were in-progress at the time of the last shut-down.
      11:04:17,082 INFO [JobStoreCMT] Recovery complete.
      11:04:17,083 INFO [JobStoreCMT] Removed 0 'complete' triggers.
      11:04:17,083 INFO [JobStoreCMT] Removed 0 stale fired job entries.
      11:04:17,134 INFO [QuartzScheduler] Scheduler JBossEJB3QuartzScheduler_$_NON_CLUSTERED started.
      11:04:17,633 INFO [ServerPeer] JBoss Messaging 1.4.1.CR1 server [0] started
      11:04:17,763 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
      11:04:17,766 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
      11:04:17,775 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
      11:04:18,073 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
      11:04:18,309 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
      
      11:04:18,309 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@105b8ef started
      11:04:18,310 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
      11:04:18,310 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@ce93f started
      11:04:18,314 INFO [QueueService] Queue[/queue/DCSubmitQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
      11:04:18,647 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
      
      11:04:18,647 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1e7c7a3 started
      11:04:18,804 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
      11:04:18,820 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war
      11:04:18,926 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war
      11:04:19,157 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
      
      *** CONTEXTS IN ERROR: Name -> Error
      
      vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DCQueueing2.ear -> org.xml.sax.SAXException: Element type "messaging-type" must be declared. @ vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DCQueueing2.ear/DCQueueing2-ejb.jar/META-INF/ejb-jar.xml[9,26]
      
      
      11:04:19,179 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8082
      11:04:19,598 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
      11:04:19,613 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.CR2 (build: SVNTag=JBoss_5_0_0_CR2 date=200809171139)] Started in 48s:418ms
      11:08:15,149 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DCQueueing2.ear state=Not Installed mode=Manual requiredState=Parse
      org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DCQueueing2.ear/DCQueueing2-ejb.jar
       at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
       at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:343)
       at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:303)
       at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:275)
       at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:236)
       at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1285)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1003)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1056)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:944)
       at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
       at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
       at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:627)
       at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
       at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:290)
       at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
       at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
       at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
       at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
       at java.lang.Thread.run(Thread.java:619)
      Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element type "messaging-type" must be declared. @ vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DCQueueing2.ear/DCQueueing2-ejb.jar/META-INF/ejb-jar.xml[9,26]
       at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
       at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
       at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199)
       at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170)
       at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
       at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
       at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256)
       at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188)
       at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:329)
       ... 28 more
      Caused by: org.xml.sax.SAXException: Element type "messaging-type" must be declared. @ vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DCQueueing2.ear/DCQueueing2-ejb.jar/META-INF/ejb-jar.xml[9,26]
       at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:426)
       at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
       at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
       at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
       at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
       at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
       at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
       at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
       at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
       at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
       at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
       at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
       at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
       at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
       at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
       at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
       ... 36 more
      11:08:15,231 WARN [HDScanner] Failed to process changes
      org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
      
      *** CONTEXTS IN ERROR: Name -> Error
      
      vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DCQueueing2.ear -> org.xml.sax.SAXException: Element type "messaging-type" must be declared. @ vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DCQueueing2.ear/DCQueueing2-ejb.jar/META-INF/ejb-jar.xml[9,26]
      
      
       at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:709)
       at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:661)
       at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:291)
       at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
       at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
       at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
       at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
       at java.lang.Thread.run(Thread.java:619)
      
      


        • 1. Re: Errors during deployment of EJB3 application into JBoss
          Peter Johnson Master

          The error message appears to be self-explanatory:

          Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element type "messaging-type" must be declared. @ vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DCQueueing2.ear/DCQueue
          ing2-ejb.jar/META-INF/ejb-jar.xml[9,26]

          • 2. messaging-type is already there!!
            ilango gurusamy Novice

            Peter
            Ok, so here goes. The messaging-type element is already there in my ejb-jar.xml. This is baffling me. Maybe I am missing something!!

            Here is my ejb-jar.xml

            <?xml version="1.0" encoding="UTF-8"?>
            <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
            <ejb-jar>
             <enterprise-beans>
             <message-driven>
             <display-name>DCMessageBean</display-name>
             <ejb-name>DCMessageBean</ejb-name>
             <ejb-class>ejb.DCMessageBean</ejb-class>
             <messaging-type>ejb.DCMessageBean</messaging-type>
             <transaction-type>Container</transaction-type>
             <message-destination-type>javax.jms.Queue</message-destination-type>
             <message-destination-link>DCSubmitQueue</message-destination-link>
             <activation-config>
             <activation-config-property>
             <activation-config-property-name>acknowledgeMode</activation-config-property-name>
             <activation-config-property-value>Auto-acknowledge</activation-config-property-value>
             </activation-config-property>
             <activation-config-property>
             <activation-config-property-name>destinationType</activation-config-property-name>
             <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
             </activation-config-property>
             </activation-config>
             <resource-ref>
             <res-ref-name>jms/QCF</res-ref-name>
             <res-type>javax.jms.QueueConnectionFactory</res-type>
             <res-auth>Container</res-auth>
             </resource-ref>
             </message-driven>
             </enterprise-beans>
             <assembly-descriptor>
             <container-transaction>
             <method>
             <ejb-name>DCMessageBean</ejb-name>
             <method-name>*</method-name>
             </method>
             <trans-attribute>Required</trans-attribute>
             </container-transaction>
             <message-destination>
             <display-name>Destination for DCMessageBean MDB</display-name>
             <message-destination-name>DCMessageBean</message-destination-name>
             </message-destination>
             </assembly-descriptor>
             </ejb-jar>


            Apologies if this is a duplicate post.


            • 3. Re: Errors during deployment of EJB3 application into JBoss
              Peter Johnson Master

              You indicated that you were declaring "EJB 3 MDBs with annotations", yet this appears as if you are using EJB 2.x. (EJB 3 uses a 3.0 version XSD for ejb-jar.xml, you are using a 2.0 version DTD.)

              Based on what I see in various tutorials, and looking at the documentation in the XSD, it would appear that the value for messaging-type should be javax.jms.MessageListener.

              Finally, if you are using EJB3 MDBs with annotations, you do not need an ejb-jar.xml.

              If none of this help, then please post the source for your MDB.

              • 4. Re: Errors during deployment of EJB3 application into JBoss
                ilango gurusamy Novice

                I thought I was using EJB 3 all along. Perhaps I have been wrong!!
                The best option is to reproduce the MDB source here: Here is the source for my MDB: Thanks again. Appreciate your kind replies

                /*
                 * To change this template, choose Tools | Templates
                 * and open the template in the editor.
                 */
                package ejb;
                
                import javax.ejb.ActivationConfigProperty;
                import javax.ejb.MessageDriven;
                import javax.jms.Message;
                import javax.jms.MessageListener;
                import javax.annotation.Resource;
                import javax.ejb.MessageDrivenContext;
                import javax.jms.JMSException;
                import javax.jms.ObjectMessage;
                import javax.persistence.EntityManager;
                import javax.persistence.PersistenceContext;
                
                /**
                 *
                 * @author
                 */
                @MessageDriven(mappedName = "jms/DCMessageBean",
                activationConfig = {
                 @ActivationConfigProperty(propertyName = "messagingType", propertyValue = "javax.jms.MessageListener"),
                 @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
                 @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
                 @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/DCSubmitQueue"),
                 @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "4")})
                
                public class DCMessageBean implements MessageListener {
                
                 @Resource
                 private MessageDrivenContext messageDrivenContext;
                 @PersistenceContext
                 private EntityManager entityManager;
                
                 public DCMessageBean() {
                 }
                
                 public void onMessage(Message message) {
                 ObjectMessage msg = null;
                 try {
                 if (message instanceof ObjectMessage) {
                 msg = (ObjectMessage) message;
                 QueueingEntity e = (QueueingEntity) msg.getObject();
                 save(e);
                 }
                 } catch (JMSException e) {
                 e.printStackTrace();
                 messageDrivenContext.setRollbackOnly();
                 } catch (Throwable te) {
                 te.printStackTrace();
                 }
                 }
                
                 public void save(Object object) {
                 entityManager.persist(object);
                 }
                }
                


                • 5. had always been javax.jms.MessageListener
                  ilango gurusamy Novice

                  It had always been javax.jms.MessageListener and then I changed it to the value that you saw, so I changed it back again and I am back to square one.
                  It complains that there is no messaging-type when in fact there is one already!!

                  Thanks again

                  • 6. Re: Errors during deployment of EJB3 application into JBoss
                    Peter Johnson Master

                    The annotations on your MDB look reasonably complete. I would remove the ejb-jar.xml file - you don't need it.

                    • 7. Re: Errors during deployment of EJB3 application into JBoss
                      ilango gurusamy Novice

                      I just did what you told me to and did a clean and did a fresh deploy to JBoss.
                      I was handed a bunch of errors: They are as below:(notably,"jndi-name not found as a child of message-driven" ) is one of them.

                      20:03:35,794 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DexCenterQueueing2.ear state=Not Installed mode=Manual requiredState=Parse
                      org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DexCenterQueueing2.ear/DexCenterQueueing2-ejb.jar
                      at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:343)
                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:303)
                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:275)
                      at org.jboss.deployment.JBossEjbParsingDeployer.createMetaData(JBossEjbParsingDeployer.java:105)
                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:236)
                      at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
                      at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1285)
                      at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1003)
                      at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1056)
                      at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:944)
                      at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
                      at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
                      at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
                      at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
                      at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
                      at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
                      at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
                      at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:627)
                      at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
                      at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:290)
                      at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
                      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
                      at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
                      at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
                      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
                      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
                      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
                      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)

                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
                      at java.lang.Thread.run(Thread.java:619)

                      Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: jndi-name not found as a child of message-driven
                      at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
                      at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
                      at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199)
                      at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170)
                      at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
                      at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
                      at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256)
                      at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188)
                      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:329)
                      ... 29 more
                      Caused by: org.jboss.xb.binding.JBossXBRuntimeException: jndi-name not found as a child of message-driven
                      at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:400)
                      at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
                      at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
                      at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
                      at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
                      at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
                      at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
                      at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
                      at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
                      at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
                      at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
                      at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
                      at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
                      ... 37 more
                      20:03:36,148 WARN [HDScanner] Failed to process changes
                      org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

                      *** CONTEXTS IN ERROR: Name -> Error

                      vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/DexCenterQueueing2.ear -> org.jboss.xb.binding.JBossXBRuntimeException: jndi-name not found as a child of message-driven


                      at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:709)
                      at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:661)
                      at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:291)
                      at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
                      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
                      at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
                      at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
                      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
                      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
                      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
                      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
                      at java.lang.Thread.run(Thread.java:619)

                      • 8. Re: Errors during deployment of EJB3 application into JBoss
                        ilango gurusamy Novice

                         

                        "PeterJ" wrote:
                        The annotations on your MDB look reasonably complete. I would remove the ejb-jar.xml file - you don't need it.


                        JBoss complains that jndi-name is not a child element of message-driven when in fact that is the case!! Thanks very much for bearing with me.

                        These are the contents of my jboss.xml.
                        <?xml version="1.0" encoding="UTF-8"?>

                        <enterprise-beans>
                        <message-driven>
                        <ejb-name>DexCenterMessageBean</ejb-name>
                        <jndi-name>DexCenterMessageBean</jndi-name>
                        <destination-jndi-name>DexCenterSubmitQueue</destination-jndi-name>
                        </message-driven>
                        </enterprise-beans>


                        • 9. No exceptions this time: the <jndi-name> stuff was misleadin
                          ilango gurusamy Novice

                          The exception with regard to <jndi-name> sounded misleading to me. At first I thought it was warning me that there ought to be <jndi-name> when it was actually there. After some thought I felt that the exception was telling me : hey, <jndi-name> is NOT to be found as a jndi-name.

                          Well,I removed the jndi-element and deployed. This time it worked.
                          Could you check the stack-trace and tell me if you find anything amiss?

                          ===============================================================================
                          
                           JBoss Bootstrap Environment
                          
                           JBOSS_HOME: C:\JBoss5\jboss-5.0.0.CR2
                          
                           JAVA: C:\jdk1.6.0_01\bin\java
                          
                           JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
                          
                           CLASSPATH: C:\JBoss5\jboss-5.0.0.CR2\bin\run.jar
                          
                          ===============================================================================
                          
                          22:17:08,366 INFO [ServerImpl] Starting JBoss (Microcontainer)...
                          22:17:08,367 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR2 (build: SVNTag=JBoss_5_0_0_CR2 date=200809171139)
                          22:17:08,370 INFO [ServerImpl] Home Dir: C:\JBoss5\jboss-5.0.0.CR2
                          22:17:08,370 INFO [ServerImpl] Home URL: file:/C:/JBoss5/jboss-5.0.0.CR2/
                          22:17:08,370 INFO [ServerImpl] Library URL: file:/C:/JBoss5/jboss-5.0.0.CR2/lib/
                          22:17:08,371 INFO [ServerImpl] Patch URL: null
                          22:17:08,371 INFO [ServerImpl] Server Name: default
                          22:17:08,501 INFO [ServerImpl] Server Home Dir: C:\JBoss5\jboss-5.0.0.CR2\server\default
                          22:17:08,501 INFO [ServerImpl] Server Home URL: file:/C:/JBoss5/jboss-5.0.0.CR2/server/default/
                          22:17:08,502 INFO [ServerImpl] Server Data Dir: C:\JBoss5\jboss-5.0.0.CR2\server\default\data
                          22:17:08,502 INFO [ServerImpl] Server Temp Dir: C:\JBoss5\jboss-5.0.0.CR2\server\default\tmp
                          22:17:08,502 INFO [ServerImpl] Server Config URL: file:/C:/JBoss5/jboss-5.0.0.CR2/server/default/conf/
                          22:17:08,502 INFO [ServerImpl] Server Library URL: file:/C:/JBoss5/jboss-5.0.0.CR2/server/default/lib/
                          22:17:08,502 INFO [ServerImpl] Root Deployment Filename: jboss-service.xml
                          22:17:09,165 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/JBoss5/jboss-5.0.0.CR2/server/default/conf/bootstrap.xml
                          22:17:10,024 INFO [CopyMechanism] VFS temp dir: C:\JBoss5\jboss-5.0.0.CR2\server\default\tmp
                          22:17:10,047 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
                          22:17:12,367 INFO [ServerInfo] Java version: 1.6.0_01,Sun Microsystems Inc.
                          22:17:12,367 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0_01-b06,Sun Microsystems Inc.
                          22:17:12,367 INFO [ServerInfo] OS-System: Windows Vista 6.0,x86
                          22:17:12,405 INFO [JMXKernel] Legacy JMX core initialized
                          22:17:15,034 INFO [MetaDataAwareProfile] Using profile root:C:\JBoss5\jboss-5.0.0.CR2\server\default
                          22:17:16,603 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
                          22:17:27,267 WARN [HackClassloaderMetaDataDeployer] FIXME Using loader repository config: jboss.console:sar=console-mgr.sar for vfsfile:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/management/console-mgr.sar/ use classloading metadata not loader repository config
                          22:17:27,783 INFO [AspectDeployer] Deploying xml into org.jboss.aop.AspectManager@1be496b for BaseClassLoader@1db637f{vfsfile:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/ejb3-interceptors-aop.xml}
                          22:17:42,065 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
                          22:17:42,172 INFO [MailService] Mail Service bound to java:/Mail
                          22:17:42,697 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
                          22:17:42,697 INFO [NativeServerConfig] 3.0.3.GA
                          22:17:43,601 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.
                          22:17:43,838 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
                          22:17:43,838 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
                          22:17:44,175 INFO [TransactionManagerService] Initializing recovery manager
                          22:17:44,465 INFO [TransactionManagerService] Recovery manager configured
                          22:17:44,465 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
                          22:17:44,497 INFO [TransactionManagerService] Starting transaction recovery manager
                          22:17:45,106 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\jdk1.6.0_01\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\jdk1.6.0_01\bin;C:\jdk1.6.0_01\dev;C:\tomcat55\apache-tomcat-5.5.17\bin;C:\Windows\System32;C:\Program Files\MySQL\MySQL Server 5.0\bin;C:\jdk1.6.0_01\bin;C:\jdk1.6.0_01\dev;C:\tomcat55\apache-tomcat-5.5.17\bin;C:\Windows\System32
                          22:17:45,207 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8082
                          22:17:45,257 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
                          22:17:45,257 INFO [Catalina] Initialization processed in 414 ms
                          22:17:45,257 INFO [StandardService] Starting service jboss.web
                          22:17:45,262 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.1.CR7
                          22:17:45,348 INFO [Catalina] Server startup in 91 ms
                          22:17:45,372 INFO [TomcatDeployment] deploy, ctxPath=/jbossws, vfsUrl=jbossws.sar/jbossws-management.war
                          22:17:46,115 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war
                          22:17:46,270 INFO [TomcatDeployment] deploy, ctxPath=/web-console, vfsUrl=management/console-mgr.sar/web-console.war
                          22:17:46,727 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
                          22:17:46,743 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
                          22:17:46,766 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/jms-ra.rar/META-INF/ra.xml
                          22:17:46,780 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/mail-ra.rar/META-INF/ra.xml
                          22:17:46,809 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/JBoss5/jboss-5.0.0.CR2/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
                          22:17:46,919 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
                          22:17:46,955 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
                          22:17:46,959 INFO [RAMJobStore] RAMJobStore initialized.
                          22:17:46,959 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
                          22:17:47,284 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
                          22:17:47,285 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
                          22:17:47,954 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
                          22:17:48,451 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))
                          22:17:48,506 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
                          22:17:48,786 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
                          22:17:48,786 INFO [JobStoreCMT] Using db table-based data access locking (synchronization).
                          22:17:48,799 INFO [JobStoreCMT] Removed 0 Volatile Trigger(s).
                          22:17:48,799 INFO [JobStoreCMT] Removed 0 Volatile Job(s).
                          22:17:48,799 INFO [JobStoreCMT] JobStoreCMT initialized.
                          22:17:48,800 INFO [StdSchedulerFactory] Quartz scheduler 'JBossEJB3QuartzScheduler' initialized from an externally provided properties instance.
                          22:17:48,800 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
                          22:17:49,331 INFO [JobStoreCMT] Freed 0 triggers from 'acquired' / 'blocked' state.
                          22:17:49,347 INFO [JobStoreCMT] Recovering 0 jobs that were in-progress at the time of the last shut-down.
                          22:17:49,348 INFO [JobStoreCMT] Recovery complete.
                          22:17:49,348 INFO [JobStoreCMT] Removed 0 'complete' triggers.
                          22:17:49,348 INFO [JobStoreCMT] Removed 0 stale fired job entries.
                          22:17:49,354 INFO [QuartzScheduler] Scheduler JBossEJB3QuartzScheduler_$_NON_CLUSTERED started.
                          22:17:49,604 INFO [ServerPeer] JBoss Messaging 1.4.1.CR1 server [0] started
                          22:17:49,891 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
                          22:17:49,892 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
                          22:17:50,372 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
                          
                          22:17:50,372 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1dbadea started
                          22:17:50,390 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                          22:17:50,394 INFO [QueueService] Queue[/queue/DexCenterSubmitQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                          22:17:50,395 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
                          22:17:50,784 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1eed10a started
                          22:17:50,787 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
                          22:17:50,787 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1ddec9e started
                          22:17:50,790 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                          22:17:50,968 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
                          22:17:51,295 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war
                          22:17:51,444 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war
                          22:17:51,646 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8082
                          22:17:51,675 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
                          22:17:51,685 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.CR2 (build: SVNTag=JBoss_5_0_0_CR2 date=200809171139)] Started in 43s:180ms
                          22:18:21,901 WARN [EjbMetadataJndiPolicyDecoratorDeployer] Defaulting to DefaultJndiBindingPolicy of "org.jboss.metadata.ejb.jboss.jndipolicy.plugins.BasicJndiBindingPolicy" for Session Bean QueueingEntityFacade
                          22:18:21,909 WARN [EjbMetadataJndiPolicyDecoratorDeployer] Defaulting to DefaultJndiBindingPolicy of "org.jboss.metadata.ejb.jboss.jndipolicy.plugins.BasicJndiBindingPolicy" for Session Bean DexCenterMessageBean
                          22:18:23,140 INFO [JBossASKernel] Created KernelDeployment for: DexCenterQueueing2-ejb.jar
                          22:18:23,146 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=DexCenterQueueing2.ear,jar=DexCenterQueueing2-ejb.jar,name=DexCenterMessageBean,service=EJB3
                          22:18:23,147 INFO [JBossASKernel] with dependencies:
                          22:18:23,147 INFO [JBossASKernel] and demands:
                          22:18:23,147 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
                          22:18:23,147 INFO [JBossASKernel] persistence.unit:unitName=DexCenterQueueing2.ear/DexCenterQueueing2-ejb.jar#DexCenterQueueing2-ejbPU
                          22:18:23,301 INFO [JBossASKernel] and supplies:
                          22:18:23,301 INFO [JBossASKernel] jndi:null
                          22:18:23,301 INFO [JBossASKernel] Class:javax.jms.MessageListener
                          22:18:23,301 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=DexCenterQueueing2.ear,jar=DexCenterQueueing2-ejb.jar,name=DexCenterMessageBean,service=EJB3) to KernelDeployment of: DexCenterQueueing2-ejb.jar
                          22:18:23,303 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=DexCenterQueueing2.ear,jar=DexCenterQueueing2-ejb.jar,name=QueueingEntityFacade,service=EJB3
                          22:18:23,303 INFO [JBossASKernel] with dependencies:
                          22:18:23,303 INFO [JBossASKernel] and demands:
                          22:18:23,303 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
                          22:18:23,303 INFO [JBossASKernel] persistence.unit:unitName=DexCenterQueueing2.ear/DexCenterQueueing2-ejb.jar#DexCenterQueueing2-ejbPU
                          22:18:23,303 INFO [JBossASKernel] and supplies:
                          22:18:23,802 INFO [JBossASKernel] jndi:DexCenterQueueing2/QueueingEntityFacade/local
                          22:18:23,802 INFO [JBossASKernel] jndi:DexCenterQueueing2/QueueingEntityFacade/remote
                          22:18:23,802 INFO [JBossASKernel] Class:ejb.QueueingEntityFacadeLocal
                          22:18:23,802 INFO [JBossASKernel] jndi:DexCenterQueueing2/QueueingEntityFacade/local-ejb.QueueingEntityFacadeLocal
                          22:18:23,802 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=DexCenterQueueing2.ear,jar=DexCenterQueueing2-ejb.jar,name=QueueingEntityFacade,service=EJB3) to KernelDeployment of: DexCenterQueueing2-ejb.jar
                          22:18:23,859 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.unit:unitName=DexCenterQueueing2.ear/DexCenterQueueing2-ejb.jar#DexCenterQueueing2-ejbPU
                          22:18:23,946 INFO [Version] Hibernate Annotations 3.4.0.GA
                          22:18:23,973 INFO [Environment] Hibernate 3.3.1.GA
                          22:18:23,984 INFO [Environment] hibernate.properties not found
                          22:18:23,990 INFO [Environment] Bytecode provider name : javassist
                          22:18:23,999 INFO [Environment] using JDK 1.4 java.sql.Timestamp handling
                          22:18:24,164 INFO [Version] Hibernate Commons Annotations 3.1.0.GA
                          22:18:24,311 INFO [Version] Hibernate EntityManager 3.4.0.GA
                          22:18:24,412 WARN [Ejb3Configuration] Persistence provider caller does not implement the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null.
                          22:18:25,245 INFO [AnnotationBinder] Binding entity from annotated class: ejb.QueueingEntity
                          22:18:25,343 INFO [EntityBinder] Bind entity ejb.QueueingEntity on table QueueingEntity
                          22:18:25,464 INFO [Version] Hibernate Validator 3.1.0.GA
                          22:18:25,552 INFO [HibernateSearchEventListenerRegister] Unable to find org.hibernate.search.event.FullTextIndexEventListener on the classpath. Hibernate Search is not enabled.
                          22:18:25,683 INFO [ConnectionProviderFactory] Initializing connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
                          22:18:25,688 INFO [InjectedDataSourceConnectionProvider] Using provided datasource
                          22:18:25,811 INFO [SettingsFactory] RDBMS: HSQL Database Engine, version: 1.8.0
                          22:18:25,811 INFO [SettingsFactory] JDBC driver: HSQL Database Engine Driver, version: 1.8.0
                          22:18:25,855 INFO [Dialect] Using dialect: org.hibernate.dialect.HSQLDialect
                          22:18:25,867 INFO [TransactionFactoryFactory] Transaction strategy: org.hibernate.ejb.transaction.JoinableCMTTransactionFactory
                          22:18:25,873 INFO [TransactionManagerLookupFactory] instantiating TransactionManagerLookup: org.hibernate.transaction.JBossTransactionManagerLookup
                          22:18:26,310 INFO [TransactionManagerLookupFactory] instantiated TransactionManagerLookup
                          22:18:26,311 INFO [SettingsFactory] Automatic flush during beforeCompletion(): disabled
                          22:18:26,311 INFO [SettingsFactory] Automatic session close at end of transaction: disabled
                          22:18:26,311 INFO [SettingsFactory] JDBC batch size: 15
                          22:18:26,311 INFO [SettingsFactory] JDBC batch updates for versioned data: disabled
                          22:18:26,313 INFO [SettingsFactory] Scrollable result sets: enabled
                          22:18:26,313 INFO [SettingsFactory] JDBC3 getGeneratedKeys(): disabled
                          22:18:26,804 INFO [SettingsFactory] Connection release mode: auto
                          22:18:26,806 INFO [SettingsFactory] Default batch fetch size: 1
                          22:18:26,806 INFO [SettingsFactory] Generate SQL with comments: disabled
                          22:18:26,806 INFO [SettingsFactory] Order SQL updates by primary key: disabled
                          22:18:26,806 INFO [SettingsFactory] Order SQL inserts for batching: disabled
                          22:18:26,807 INFO [SettingsFactory] Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
                          22:18:26,812 INFO [ASTQueryTranslatorFactory] Using ASTQueryTranslatorFactory
                          22:18:26,813 INFO [SettingsFactory] Query language substitutions: {}
                          22:18:27,305 INFO [SettingsFactory] JPA-QL strict compliance: enabled
                          22:18:27,305 INFO [SettingsFactory] Second-level cache: enabled
                          22:18:27,305 INFO [SettingsFactory] Query cache: disabled
                          22:18:27,305 INFO [SettingsFactory] Cache region factory : org.hibernate.cache.impl.NoCachingRegionFactory
                          22:18:27,306 INFO [SettingsFactory] Optimize cache for minimal puts: disabled
                          22:18:27,306 INFO [SettingsFactory] Structured second-level cache entries: disabled
                          22:18:27,323 INFO [SettingsFactory] Statistics: disabled
                          22:18:27,804 INFO [SettingsFactory] Deleted entity synthetic identifier rollback: disabled
                          22:18:27,806 INFO [SettingsFactory] Default entity-mode: pojo
                          22:18:27,808 INFO [SettingsFactory] Named query checking : enabled
                          22:18:27,908 INFO [SessionFactoryImpl] building session factory
                          22:18:28,300 INFO [SessionFactoryObjectFactory] Factory name: persistence.unit:unitName=DexCenterQueueing2.ear/DexCenterQueueing2-ejb.jar#DexCenterQueueing2-ejbPU
                          22:18:28,303 INFO [NamingHelper] JNDI InitialContext properties:{}
                          22:18:28,320 INFO [NamingHelper] Creating subcontext: persistence.unit:unitName=DexCenterQueueing2.ear
                          22:18:28,320 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name: persistence.unit:unitName=DexCenterQueueing2.ear/DexCenterQueueing2-ejb.jar#DexCenterQueueing2-ejbPU
                          22:18:28,320 WARN [SessionFactoryObjectFactory] InitialContext did not implement EventContext
                          22:18:28,338 INFO [SchemaUpdate] Running hbm2ddl schema update
                          22:18:28,338 INFO [SchemaUpdate] fetching database metadata
                          22:18:28,340 INFO [SchemaUpdate] updating schema
                          22:18:28,872 INFO [TableMetadata] table found: PUBLIC.QUEUEINGENTITY
                          22:18:28,872 INFO [TableMetadata] columns: [id, body, title]
                          22:18:28,872 INFO [TableMetadata] foreign keys: []
                          22:18:28,872 INFO [TableMetadata] indexes: [sys_idx_109]
                          22:18:28,873 INFO [SchemaUpdate] schema update complete
                          22:18:28,875 INFO [NamingHelper] JNDI InitialContext properties:{}
                          22:18:29,257 INFO [EJBContainer] STARTED EJB: ejb.DexCenterMessageBean ejbName: DexCenterMessageBean
                          22:18:29,921 INFO [SessionSpecContainer] Starting jboss.j2ee:ear=DexCenterQueueing2.ear,jar=DexCenterQueueing2-ejb.jar,name=QueueingEntityFacade,service=EJB3
                          22:18:29,945 INFO [EJBContainer] STARTED EJB: ejb.QueueingEntityFacade ejbName: QueueingEntityFacade
                          22:18:29,950 WARN [SessionSpecContainer] Populating JBoss-specific annotation metadata manually until done by deployers: jboss.j2ee:ear=DexCenterQueueing2.ear,jar=DexCenterQueueing2-ejb.jar,name=QueueingEntityFacade,service=EJB3
                          22:18:30,351 INFO [TomcatDeployment] deploy, ctxPath=/DexCenterQueueing2-war, vfsUrl=DexCenterQueueing2.ear/DexCenterQueueing2-war.war
                          22:19:25,360 WARN [LifecycleCallbacks] EJBTHREE-1480: LifecycleCallbackStack has not been defined for domain 'Stateless Bean'
                          22:19:25,368 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                          22:19:25,370 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                          22:19:25,374 WARN [InterceptorRegistry] applicable interceptors is non-existent for public ejb.QueueingEntity ejb.QueueingEntityFacade.find(java.lang.Object)
                          22:19:25,867 WARN [InterceptorRegistry] applicable interceptors is non-existent for public java.util.List ejb.QueueingEntityFacade.findAll()
                          22:19:25,872 WARN [InterceptorRegistry] applicable interceptors is non-existent for public void ejb.QueueingEntityFacade.create(ejb.QueueingEntity)
                          22:19:25,876 WARN [InterceptorRegistry] applicable interceptors is non-existent for public void ejb.QueueingEntityFacade.edit(ejb.QueueingEntity)
                          22:19:25,881 WARN [InterceptorRegistry] applicable interceptors is non-existent for public void ejb.QueueingEntityFacade.remove(ejb.QueueingEntity)
                          22:19:26,365 WARN [InterceptorRegistry] applicable interceptors is non-existent for public ejb.QueueingEntity ejb.QueueingEntityFacade.find(java.lang.Object)
                          22:19:26,371 WARN [InterceptorRegistry] applicable interceptors is non-existent for public java.util.List ejb.QueueingEntityFacade.findAll()
                          22:19:26,377 WARN [InterceptorRegistry] applicable interceptors is non-existent for public void ejb.QueueingEntityFacade.create(ejb.QueueingEntity)
                          22:19:26,382 WARN [InterceptorRegistry] applicable interceptors is non-existent for public void ejb.QueueingEntityFacade.edit(ejb.QueueingEntity)
                          22:19:26,864 WARN [InterceptorRegistry] applicable interceptors is non-existent for public void ejb.QueueingEntityFacade.remove(ejb.QueueingEntity)
                          22:19:38,751 INFO [ServerSessionEndpoint] Received send for ID:JBM-ff70b8c0-56f7-48e4-9774-86b69411e4d4 reliable: true
                          22:19:38,786 INFO [ServerSessionEndpoint] Done send
                          22:19:38,928 WARN [LifecycleCallbacks] EJBTHREE-1480: LifecycleCallbackStack has not been defined for domain 'Message Driven Bean'
                          22:19:38,929 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                          22:19:38,929 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                          22:19:38,930 WARN [InterceptorRegistry] applicable interceptors is non-existent for public void ejb.DexCenterMessageBean.onMessage(javax.jms.Message)
                          22:19:39,363 WARN [InterceptorRegistry] applicable interceptors is non-existent for public void ejb.DexCenterMessageBean.save(java.lang.Object)
                          22:19:39,367 WARN [InterceptorRegistry] applicable interceptors is non-existent for public void ejb.DexCenterMessageBean.onMessage(javax.jms.Message)
                          22:19:39,372 WARN [InterceptorRegistry] applicable interceptors is non-existent for public void ejb.DexCenterMessageBean.save(java.lang.Object)
                          
                          
                          



                          • 10. Re: Errors during deployment of EJB3 application into JBoss
                            Peter Johnson Master

                            I did not know that you had a jboss.xml file, you do not need that either.

                            The console output looks ok. You can ignore the warnings.