11 Replies Latest reply on Aug 20, 2012 10:54 AM by padrian

Jboss AS 7 deploy error

padrian Aug 3, 2012 8:06 AM

Hi all,

I'm installing Jboss AS 7 on windows 7 and i encountered some problems. My last problems is that although i managed to install jboss i have some issue with my deployed application. The message is that the application.war application was succesfully deployed and a new file with the name my application.war.deployed was created, but i have the following message error:

14:32:01,546 INFO [org.jboss.as.server] (ServerService Thread Pool -- 29) JBAS018559: Deployed "application.war"

14:32:01,562 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

JBAS014777: Services which failed to start: service jboss.deployment.unit."application.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.un

it."application.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "application.war".

In the jboss console i can see my application under the "Manage Deployments" arrea with the status Enabled, but when i try to access my application i get the http 404 error.

Does anyone have any ideea why i can't access my application, or why i have the given error?

Best regards,

1. Re: Jboss AS 7 deploy error

cfang Aug 3, 2012 12:40 PM (in response to padrian)

Any stacktrace in log? I guess the deploy phase succeeded, but your app failed to load and start.
Actions
2. Re: Jboss AS 7 deploy error

padrian Aug 6, 2012 3:03 AM (in response to cfang)

Didn't find anything. Only that message error that i've given eariler. It is odd, the message is "Deployer application.war" but i can't access it, and the http 404 usually means that the application failed to start. I've tried to deploy another 2 applications but one didn't deployed and the other has the same problem as this one(deployed but can't start). Have any ideas how i can fix this? and deploy an application?
Actions
3. Re: Jboss AS 7 deploy error

nickarls Aug 6, 2012 5:02 PM (in response to padrian)

EAR or WAR? Dropped in deployments folder or deployed through CLI? Can the same app be deployed on another AS?
Actions
4. Re: Jboss AS 7 deploy error

padrian Aug 7, 2012 7:37 AM (in response to nickarls)

It's a WAR. I used the JBoss AS 7 nightly builds(jboss-as-7.2.0.Alpha1-SNAPSHOT) and deployed it on the \%JBOSS_HOME%\standalone\deployments folder. The same app works on Tomcat 5.5 and also on JBoss 4.2.1. I'm not installing on a Windows 7 OS but on a Windows Server 2003 Enterprise Edition SP2. I've installed Maven3.0.4.

Thx,
Actions
5. Re: Jboss AS 7 deploy error

padrian Aug 13, 2012 7:21 AM (in response to nickarls)

So... does anyone have any ideea on how i can fix this? I have a jboss 7 standing and an app deployed on it, but i can't use it.

Thx,
Actions
6. Re: Jboss AS 7 deploy error

ctomc Aug 13, 2012 8:12 AM (in response to padrian)

Hi,

you still havent provided complete boot log. we cannot help you without any more info.

also can you post the structure of you application which you get by running jar
tf <name of your deployment archive>

--
tomaz
Actions
7. Re: Jboss AS 7 deploy error

padrian Aug 14, 2012 7:11 AM (in response to ctomc)

Hi,

     I've listed everything i have in the log directory. Also i'm not sure what you mean by "the structure of you application which you get by running jar" or how i can provide you this.

1) boot.log:

16:37:05,250 INFO [org.jboss.modules] JBoss Modules version 1.1.2.GA
16:37:31,031 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
16:37:35,890 INFO [org.jboss.as] JBAS015899: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" starting
16:37:36,156 DEBUG [org.jboss.as.config] Configured system properties:
    awt.toolkit = sun.awt.windows.WToolkit
    file.encoding = Cp1252
    file.encoding.pkg = sun.io
    file.separator = \
    java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
    java.awt.printerjob = sun.awt.windows.WPrinterJob
    java.class.path = C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\jboss-modules.jar
    java.class.version = 50.0
    java.endorsed.dirs = C:\Program Files\Java\jdk1.6.0_12\jre\lib\endorsed
    java.ext.dirs = C:\Program Files\Java\jdk1.6.0_12\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
    java.home = C:\Program Files\Java\jdk1.6.0_12\jre
    java.io.tmpdir = C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\
    java.library.path = C:\Program Files\Java\jdk1.6.0_12\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files\Documentum\Shared;C:\Documentum\product\6.6\bin;C:\Documentum\fulltext\fast;C:\Documentum\fulltext\dsearch;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\;C:\Maven3.0.4\bin;C:\Program Files\Common Files\;C:\Program Files\Common Files\EMC;Pñ
    java.net.preferIPv4Stack = true
    java.runtime.name = Java(TM) SE Runtime Environment
    java.runtime.version = 1.6.0_12-b04
    java.specification.name = Java Platform API Specification
    java.specification.vendor = Sun Microsystems Inc.
    java.specification.version = 1.6
    java.util.logging.manager = org.jboss.logmanager.LogManager
    java.vendor = Sun Microsystems Inc.
    java.vendor.url = http://java.sun.com/
    java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
    java.version = 1.6.0_12
    java.vm.info = mixed mode
    java.vm.name = Java HotSpot(TM) Client VM
    java.vm.specification.name = Java Virtual Machine Specification
    java.vm.specification.vendor = Sun Microsystems Inc.
    java.vm.specification.version = 1.0
    java.vm.vendor = Sun Microsystems Inc.
    java.vm.version = 11.2-b01
    javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
    javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
    javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
    javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
    javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
    javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
    javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
    javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
    javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
    javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
    jboss.home.dir = C:\jboss-as-7.2.0.Alpha1-SNAPSHOT
    jboss.host.name = dctm66ap
    jboss.modules.dir = C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\modules
    jboss.modules.system.pkgs = org.jboss.byteman
    jboss.node.name = dctm66ap
    jboss.qualified.host.name = dctm66ap
    jboss.server.base.dir = C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone
    jboss.server.config.dir = C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\configuration
    jboss.server.data.dir = C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\data
    jboss.server.default.config = standalone.xml
    jboss.server.deploy.dir = C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\data\content
    jboss.server.log.dir = C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\log
    jboss.server.name = dctm66ap
    jboss.server.temp.dir = C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\tmp
    line.separator =

    logging.configuration = file:C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone/configuration/logging.properties
    module.path = C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\modules
    org.jboss.boot.log.file = C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\log\boot.log
    org.jboss.resolver.warning = true
    org.xml.sax.driver = __redirected.__XMLReaderFactory
    os.arch = x86
    os.name = Windows 2003
    os.version = 5.2
    path.separator = ;
    program.name = standalone.bat
    sun.arch.data.model = 32
    sun.boot.class.path = C:\Program Files\Java\jdk1.6.0_12\jre\lib\resources.jar;C:\Program Files\Java\jdk1.6.0_12\jre\lib\rt.jar;C:\Program Files\Java\jdk1.6.0_12\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.6.0_12\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.6.0_12\jre\lib\jce.jar;C:\Program Files\Java\jdk1.6.0_12\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.6.0_12\jre\classes
    sun.boot.library.path = C:\Program Files\Java\jdk1.6.0_12\jre\bin
    sun.cpu.endian = little
    sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86
    sun.desktop = windows
    sun.io.unicode.encoding = UnicodeLittle
    sun.java.launcher = SUN_STANDARD
    sun.jnu.encoding = Cp1252
    sun.management.compiler = HotSpot Client Compiler
    sun.os.patch.level = Service Pack 2
    sun.rmi.dgc.client.gcInterval = 3600000
    sun.rmi.dgc.server.gcInterval = 3600000
    user.country = US
    user.dir = C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\bin
    user.home = C:\Documents and Settings\Administrator
    user.language = en
    user.name = Administrator
    user.timezone = Europe/Minsk
    user.variant =
16:37:36,171 DEBUG [org.jboss.as.config] VM Arguments: -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.default.config=standalone.xml -Dorg.jboss.boot.log.file=C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\log\boot.log -Dlogging.configuration=file:C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone/configuration/logging.properties
16:38:18,250 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
16:38:18,328 INFO [org.xnio] XNIO Version 3.0.5.GA
16:38:18,859 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.5.GA
16:38:19,015 INFO [org.jboss.as.security] JBAS013171: Activating Security Subsystem
16:38:19,046 INFO [org.jboss.as.webservices] JBAS015537: Activating WebServices Extension
16:38:19,187 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
13:57:24,703 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers
13:57:28,171 INFO [com.arjuna.ats.jbossatx] ARJUNA032018: Destroying TransactionManagerService
13:57:28,640 INFO [com.arjuna.ats.jbossatx] ARJUNA032014: Stopping transaction recovery manager
13:59:14,875 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment webtop.war in 130894ms
13:59:25,750 INFO [org.jboss.as.server.deployment] JBAS015877: Stopped deployment da.war in 137991ms
13:59:26,718 INFO [org.jboss.as] JBAS015950: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" stopped in 138943ms

2) server.log.2012-08-17:

11:11:48,921 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
11:11:52,000 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http-/127.0.0.1:8181
11:12:00,250 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
11:12:25,296 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.1.0.Beta1
11:12:38,250 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "webtop.war"
11:12:38,265 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\deployments
11:12:38,609 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:9999
11:12:43,750 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:4447
11:21:33,546 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.
11:23:06,500 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,500 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:23:06,515 WARN [org.jboss.remoting.remote] (Remoting "dctm66ap" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
11:41:22,187 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http-/127.0.0.1:8181
11:41:22,562 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
11:41:22,812 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-2) JBoss Web Services - Stack CXF Server 4.1.0.Beta1
11:41:23,015 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\deployments
11:41:23,031 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "webtop.war"
11:41:23,890 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:9999
11:41:23,953 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:4447
11:47:33,015 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry xerces-J_1.4.0.jar in /C:/jboss-as-7.2.0.Alpha1-SNAPSHOT/bin/content/webtop.war/WEB-INF/lib/castor-1.1-xml.jar does not point to a valid jar for a Class-Path reference.
11:47:33,015 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry jsr173_1.0_api.jar in /C:/jboss-as-7.2.0.Alpha1-SNAPSHOT/bin/content/webtop.war/WEB-INF/lib/jaxb-impl.jar does not point to a valid jar for a Class-Path reference.
11:47:33,015 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry jaxb1-impl.jar in /C:/jboss-as-7.2.0.Alpha1-SNAPSHOT/bin/content/webtop.war/WEB-INF/lib/jaxb-impl.jar does not point to a valid jar for a Class-Path reference.
11:47:33,015 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry relaxngDatatype.jar in /C:/jboss-as-7.2.0.Alpha1-SNAPSHOT/bin/content/webtop.war/WEB-INF/lib/xsdlib.jar does not point to a valid jar for a Class-Path reference.
11:47:33,968 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."webtop.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."webtop.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "webtop.war"
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_12]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_12]
    at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_12]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018014: Failed to parse XML descriptor "/C:/jboss-as-7.2.0.Alpha1-SNAPSHOT/bin/content/webtop.war/WEB-INF/tlds/dmda_1_0.tld" at [26,20]
    at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(TldParsingDeploymentProcessor.java:142)
    at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:121)
    at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.deploy(TldParsingDeploymentProcessor.java:100)
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
    ... 5 more

11:47:33,984 INFO [org.jboss.as.server] (ServerService Thread Pool -- 29) JBAS018559: Deployed "webtop.war"
11:47:33,984 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777:   Services which failed to start:      service jboss.deployment.unit."webtop.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."webtop.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "webtop.war"

11:47:34,109 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
11:47:34,109 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
11:47:34,109 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" started (with errors) in 378953ms - Started 136 of 213 services (1 services failed or missing dependencies, 75 services are passive or on-demand)

3) server.log.2012-08-13:

16:38:27,812 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]
16:38:31,015 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-2) JBoss Web Services - Stack CXF Server 4.1.0.Beta1
16:38:31,890 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http-/127.0.0.1:8181
16:38:33,859 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\deployments
16:38:33,937 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "da.war"
16:38:34,015 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "webtop.war"
16:48:17,515 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.
16:48:17,531 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.
16:51:24,031 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:9999
16:51:27,859 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:4447
16:51:27,859 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
16:52:26,625 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Register web context: /da
16:55:48,468 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry xerces-J_1.4.0.jar in /C:/jboss-as-7.2.0.Alpha1-SNAPSHOT/bin/content/webtop.war/WEB-INF/lib/castor-1.1-xml.jar does not point to a valid jar for a Class-Path reference.
16:55:48,468 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jsr173_1.0_api.jar in /C:/jboss-as-7.2.0.Alpha1-SNAPSHOT/bin/content/webtop.war/WEB-INF/lib/jaxb-impl.jar does not point to a valid jar for a Class-Path reference.
16:55:48,468 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jaxb1-impl.jar in /C:/jboss-as-7.2.0.Alpha1-SNAPSHOT/bin/content/webtop.war/WEB-INF/lib/jaxb-impl.jar does not point to a valid jar for a Class-Path reference.
16:55:48,500 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry relaxngDatatype.jar in /C:/jboss-as-7.2.0.Alpha1-SNAPSHOT/bin/content/webtop.war/WEB-INF/lib/xsdlib.jar does not point to a valid jar for a Class-Path reference.
16:55:49,765 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."webtop.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."webtop.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "webtop.war"
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_12]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_12]
    at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_12]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018014: Failed to parse XML descriptor "/C:/jboss-as-7.2.0.Alpha1-SNAPSHOT/bin/content/webtop.war/WEB-INF/tlds/dmda_1_0.tld" at [26,20]
    at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(TldParsingDeploymentProcessor.java:142)
    at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:121)
    at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.deploy(TldParsingDeploymentProcessor.java:100)
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
    ... 5 more

16:55:52,484 INFO [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "webtop.war"
16:55:52,484 INFO [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "da.war"
16:55:54,546 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777:   Services which failed to start:      service jboss.deployment.unit."webtop.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."webtop.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "webtop.war"

16:55:55,796 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
16:55:55,796 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
16:55:55,796 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" started (with errors) in 1158296ms - Started 176 of 256 services (1 services failed or missing dependencies, 78 services are passive or on-demand)

I have also tried to deploy another app besides my first one(webtop). I have the same issue, the app(da) is deployed but i still can't access it although i can see both of them in the jboss management console under the "Manage Deployments" section.

Thx,
Actions
8. Re: Jboss AS 7 deploy error

sfcoy Aug 14, 2012 10:23 AM (in response to padrian)

You need to fix this:

JBAS018014: Failed to parse XML descriptor "/C:/jboss-as-7.2.0.Alpha1-SNAPSHOT/bin/content/webtop.war/WEB-INF/tlds/dmda_1_0.tld" at [26,20]
Actions
9. Re: Jboss AS 7 deploy error

padrian Aug 14, 2012 10:25 AM (in response to sfcoy)

ok... how can i fix it?
Actions
10. Re: Jboss AS 7 deploy error

sfcoy Aug 14, 2012 11:15 AM (in response to padrian)

dmda_1_0.tld is an xml file that corresponds to a schema. Change it to correspond to that schema.
Actions
11. Re: Jboss AS 7 deploy error

padrian Aug 20, 2012 10:54 AM (in response to sfcoy)

First of all thx for the reply. I don't know what schema you're talking about. I've opened the dmda_1_0.tld file and i don't know what is it that i have to change. I've compared this file(dmda_1_0) from my jboss AS with the dmda_1_0 from my Tomcat AS(that has the same app deployed and it works on it) and there are no differences between them. Can u please provide some more information about this?

Best regards,
Actions

Go to original post