12 Replies Latest reply on Jun 14, 2013 8:40 AM by prasad k

    Unexpected HTTP response: 500  Request

    prasad k Newbie

      Min/Maximize

       

      Unexpected HTTP response: 500  Request

      { "address" => [("deployment" => "focsear.ear")], "operation" => "deploy"

      }

        Response  Internal Server Error

      {

      "outcome" => "failed",

      "failure-description" => {"JBAS014671: Failed services" => {

      "jboss.deployment.subunit.\"focsear.ear\".\"focswar.war\".PARSE"

      => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"focsear.ear\".\"focswar.war\".PARSE: Failed to process phase PARSE of subdeployment \"focswar.war\" of deployment \"focsear.ear\""}}, "rolled-back" => true }

       

        • 1. Re: Unexpected HTTP response: 500  Request
          Nicklas Karlsson Master

          What's in the log file?

          • 2. Re: Unexpected HTTP response: 500  Request
            Tomaz Cerar Master

            Hi,

             

            what does log say?

             

             

            --

            tomaz

            • 3. Re: Unexpected HTTP response: 500  Request
              prasad k Newbie

              hi Nicklas/Tomaz,

               

               

              16:44:06,001 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

              16:44:06,282 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

              16:44:06,336 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

              16:44:07,752 INFO  [org.xnio] XNIO Version 3.0.3.GA

              16:44:07,752 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

              16:44:07,873 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

              16:44:07,893 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA

              16:44:07,926 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

              16:44:07,964 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem

              16:44:08,066 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

              16:44:08,069 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.

              16:44:08,079 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

              16:44:08,081 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem

              16:44:08,097 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem

              16:44:08,256 INFO  [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.7.Final

              16:44:08,482 INFO  [org.jboss.as.connector] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

              16:44:08,601 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.2.GA

              16:44:08,626 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service

              16:44:08,705 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]

              16:44:08,746 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)

              16:44:08,777 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

              16:44:09,237 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080

              16:44:09,443 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory D:\eclipse-jee-indigo\jboss-as-7.1.1.Final\standalone\deployments

              16:44:09,457 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost/127.0.0.1:4447

              16:44:09,459 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /127.0.0.1:9999

              16:44:09,725 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

              16:44:09,726 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/jdbc/servicing]

              16:44:09,772 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

              16:44:09,775 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 4054ms - Started 139 of 215 services (74 services are passive or on-demand)

              16:44:59,555 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "focsear.ear"

              16:45:03,911 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry classes12.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,914 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-beanutils_1_7_0.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,918 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-collections-3.1.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,921 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-digester_1_6.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,925 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-discovery.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,928 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-fileupload-1.0.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,932 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-httpclient-2.0.2.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,936 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-lang-2.0.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,939 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-logging.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,943 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-pool-1.2.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,946 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-validator-1.1.4.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,950 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry hibernate2.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,953 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry j2ee.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,956 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry log4j-1.2.8.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,960 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry struts.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,963 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry dom4j-1.4.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,966 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry odmg-3.0.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,970 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry ehcache-0.9.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,973 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry cglib-full-2.0.2.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,976 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry security.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,980 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry antlr.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,983 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry castor-1.1.1.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,986 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry castor-1.1.1-codegen.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,990 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry axis.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,993 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jaxrpc.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:03,996 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry saaj.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:04,000 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry wsdl4j.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:04,003 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry rt.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:04,006 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry focsutil.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:04,009 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry focsejb.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:04,013 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry focswar.war in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear"  does not point to a valid jar for a Class-Path reference.

              16:45:04,017 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry log4j.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/commons-logging.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,021 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry log4j-core.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/commons-logging.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,025 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-beanutils.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/struts.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,029 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-collections.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/struts.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,032 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-digester.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/struts.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,038 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-validator.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/struts.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,041 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jakarta-oro.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/struts.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,045 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry xerces-J_1.4.0.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/castor-1.1.1.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,049 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jdbc-se2.0.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/castor-1.1.1.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,053 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jndi_1.2.1.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/castor-1.1.1.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,057 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jta1.0.1.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/castor-1.1.1.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,081 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-logging-1.1.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/castor-1.1.1.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,096 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry qname.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/wsdl4j.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,100 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry log4j.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/commons-logging.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,103 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry log4j-core.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/commons-logging.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,107 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry qname.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/wsdl4j.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,266 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "focswar.war"

              16:45:04,270 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "focsejb.jar"

              16:45:04,289 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry j2ee.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/focsejb.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,545 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry j2ee.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/focswar.war"  does not point to a valid jar for a Class-Path reference.

              16:45:04,927 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry log4j.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/focswar.war/WEB-INF/lib/commons-logging.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,931 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry log4j-core.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/focswar.war/WEB-INF/lib/commons-logging.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,935 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-beanutils.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/struts.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,939 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-collections.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/struts.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,943 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-digester.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/struts.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,946 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-validator.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/struts.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,950 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jakarta-oro.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/struts.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,954 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry xerces-J_1.4.0.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/castor-1.1.1.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,958 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jdbc-se2.0.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/castor-1.1.1.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,962 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jndi_1.2.1.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/castor-1.1.1.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,965 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jta1.0.1.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/castor-1.1.1.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:04,969 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry commons-logging-1.1.jar in "/D:/eclipse-jee-indigo/jboss-as-7.1.1.Final/bin/content/focsear.ear/castor-1.1.1.jar"  does not point to a valid jar for a Class-Path reference.

              16:45:05,220 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.subunit."focsear.ear"."focswar.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."focsear.ear"."focswar.war".PARSE: Failed to process phase PARSE of subdeployment "focswar.war" of deployment "focsear.ear"

                        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

                        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(Unknown Source) [rt.jar:1.6.0_07]

                        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_07]

                        at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_07]

              Caused by: java.lang.IllegalArgumentException: Given parent is not an ancestor of this virtual file

                        at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:116)

                        at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                        at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                        at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                        at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                        at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                        at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                        at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                        at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                        at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                        at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:110)

                        at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:107)

                        at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:109)

                        at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.deploy(TldParsingDeploymentProcessor.java:83)

                        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

                        ... 5 more

               

               

              16:45:05,498 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "focsear.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"focsear.ear\".\"focswar.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"focsear.ear\".\"focswar.war\".PARSE: Failed to process phase PARSE of subdeployment \"focswar.war\" of deployment \"focsear.ear\""}}

              16:45:05,521 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment focsejb.jar in 19ms

              16:45:05,908 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment focswar.war in 408ms

              16:45:05,998 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment focsear.ear in 501ms

              16:45:06,001 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report

              JBAS014777:   Services which failed to start:      service jboss.deployment.subunit."focsear.ear"."focswar.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."focsear.ear"."focswar.war".PARSE: Failed to process phase PARSE of subdeployment "focswar.war" of deployment "focsear.ear"

               

               

              16:45:06,008 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"focsear.ear\".\"focswar.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"focsear.ear\".\"focswar.war\".PARSE: Failed to process phase PARSE of subdeployment \"focswar.war\" of deployment \"focsear.ear\""}}}}

              • 4. Re: Unexpected HTTP response: 500  Request
                Nicklas Karlsson Master

                Does any of the bundles jars have a manifest entry with a suspicous path?

                • 5. Re: Unexpected HTTP response: 500  Request
                  Tomaz Cerar Master

                  This is a known issue with 7.1.1.Final

                  if there is something fishy in class-path entry of manifest.mf of jars you bunlde in your app it breaks...

                   

                  there are two ways to fix this.

                   

                  1) upgrade newer version, i would recomend 7.2.0.Final/EAP6.1.Alpha (it is called EAP alpha but it is really community release of AS 7.2)

                  2) fix manifest.mf entries.

                   

                   

                  --

                  tomaz

                  • 6. Re: Unexpected HTTP response: 500  Request
                    prasad k Newbie

                    yes Nicklas/Tomaz,

                     

                    Manifest-Version: 1.0

                    Created-By: Apache Ant 1.5.1

                    Class-Path: classes12.jar

                      commons-beanutils_1_7_0.jar

                      commons-collections-3.1.jar

                      commons-digester_1_6.jar

                      commons-discovery.jar

                      commons-fileupload-1.0.jar

                      commons-httpclient-2.0.2.jar

                      commons-lang-2.0.jar

                      commons-logging.jar

                      commons-pool-1.2.jar

                      commons-validator-1.1.4.jar

                      hibernate2.jar j2ee.jar

                      log4j-1.2.8.jar struts.jar

                      dom4j-1.4.jar

                      odmg-3.0.jar

                      ehcache-0.9.jar

                      cglib-full-2.0.2.jar

                      security.jar

                      antlr.jar

                      castor-1.1.1.jar

                      castor-1.1.1-codegen.jar

                      axis.jar

                      jaxrpc.jar

                      saaj.jar

                      wsdl4j.jar

                      rt.jar 

                      @application_util_name@

                      @application_ejb_name@

                      @application_war_name@

                     

                    These are the jar files are there in the manifest file.

                     

                    can you please help me to download link, bcz i searched in jboss site unable to find "7.2.0.Final/EAP6.1.Alpha"

                     

                    please help me!

                    Thanks for giving reply.

                    • 8. Re: Unexpected HTTP response: 500  Request
                      prasad k Newbie

                      Nicklas Karlsson/Tomaz Cerar,

                       

                      If you dont mind can you please expalin how to fix manifest.mf entries, Bcz am unable to install the new server wizard.

                       

                      it is showing the following Error.

                       

                      The home directory does not exist or is missing a required file or folder: bin\twiddle.jar

                       

                      Thanks,

                      -Prasad K


                      • 9. Re: Unexpected HTTP response: 500  Request
                        prasad k Newbie

                        Jboss.png

                         

                        This is the error! Please help me!

                         

                        Thanks & Regards,

                        -Prasad K

                        • 10. Re: Unexpected HTTP response: 500  Request
                          Tomaz Cerar Master

                          You need to add AS7 or EAP 6.1 runtime not AS6.x that is big difference.

                           

                          you might need to update jboss tools...

                          • 11. Re: Unexpected HTTP response: 500  Request
                            prasad k Newbie

                            Hi Tomaz,

                             

                            i installed EAP 6.1 but still i am geting same problem.

                            please find the attached log file.

                             

                            17:30:00,758 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.subunit."focsear.ear"."focswar.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."focsear.ear"."focswar.war".PARSE: JBAS018733: Failed to process phase PARSE of subdeployment "focswar.war" of deployment "focsear.ear"

                                      at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]

                                      at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]

                                      at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]

                                      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_07]

                                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_07]

                                      at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_07]

                            Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018097: TLD file /D:/eclipse-jee-indigo/new/jboss-eap-6.1.0.Alpha/jboss-eap-6.1/bin/content/focsear.ear/struts.jar/META-INF/tlds/struts-html.tld not contained in root /D:/eclipse-jee-indigo/new/jboss-eap-6.1.0.Alpha/jboss-eap-6.1/bin/content/focsear.ear/focswar.war

                                      at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:119)

                                      at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:124)

                                      at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.deploy(TldParsingDeploymentProcessor.java:84)

                                      at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]

                                      ... 5 more

                            Caused by: java.lang.IllegalArgumentException: Given parent is not an ancestor of this virtual file

                                      at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:116)

                                      at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                                      at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                                      at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                                      at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                                      at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                                      at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                                      at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                                      at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                                      at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                                      at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                                      at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)

                                      at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:110)

                                      at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:117)

                                      ... 8 more

                             

                             

                            17:30:01,116 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "focsear.ear" was rolled back with the following failure message:

                            {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"focsear.ear\".\"focswar.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"focsear.ear\".\"focswar.war\".PARSE: JBAS018733: Failed to process phase PARSE of subdeployment \"focswar.war\" of deployment \"focsear.ear\"

                                Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018097: TLD file /D:/eclipse-jee-indigo/new/jboss-eap-6.1.0.Alpha/jboss-eap-6.1/bin/content/focsear.ear/struts.jar/META-INF/tlds/struts-html.tld not contained in root /D:/eclipse-jee-indigo/new/jboss-eap-6.1.0.Alpha/jboss-eap-6.1/bin/content/focsear.ear/focswar.war

                                Caused by: java.lang.IllegalArgumentException: Given parent is not an ancestor of this virtual file"}}

                            17:30:01,117 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment null (runtime-name: focsejb.jar) in 13ms

                            17:30:01,414 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment null (runtime-name: focswar.war) in 294ms

                            17:30:01,492 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment focsear.ear (runtime-name: focsear.ear) in 372ms

                             

                             

                            please give me suggisioin.

                             

                            Thanks,

                            -Prasad k

                            • 12. Re: Unexpected HTTP response: 500  Request
                              prasad k Newbie

                              Through admin console i got the following error!

                               

                               

                              Fri Jun 14 17:39:05 GMT+530 2013

                              Failed to enable focsear.ear.

                               

                              Unexpected HTTP response: 500  Request {

                              "address" => [("deployment" => "focsear.ear")], "operation" => "deploy"

                              }

                              Response  Internal Server Error {

                              "outcome" => "failed", "failure-description" => {

                              "JBAS014671: Failed services" => {"jboss.deployment.subunit.\"focsear.ear\".\"focswar.war\".PARSE"

                              => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"focsear.ear\".\"focswar.war\".PARSE: JBAS018733:

                              Failed to process phase PARSE of subdeployment \"focswar.war\" of deployment \"focsear.ear\"

                              Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018097: TLD file /D:/eclipse-jee-indigo/new/jboss-eap-6.1.0.Alpha/jboss-eap-6.1/bin/content/focsear.ear/struts.jar/META-INF/tlds/struts-html.tld not contained in root /D:/eclipse-jee-indigo/new/jboss-eap-6.1.0.Alpha/jboss-eap-6.1/bin/content/focsear.ear/focswar.war Caused by: java.lang.IllegalArgumentException:

                              Given parent is not an ancestor of this virtual file"}},

                              "rolled-back" => true

                              }