[jboss-user] [Installation, Configuration & DEPLOYMENT] - Errors during deployment of EJB3 application into JBoss 5 R2
ilangocal
do-not-reply at jboss.com
Tue Oct 21 13:53:03 EDT 2008
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 at 17cdd50 for BaseClassLoader at 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 at 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 at 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 at 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)
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183604#4183604
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183604
More information about the jboss-user
mailing list