1 2 3 Previous Next 32 Replies Latest reply on Jul 6, 2012 11:32 AM by Sanjeev Shrestha

    How do I solve this problem ?

    Sanjeev Shrestha Novice

      Please Help me. Nobody seems to know the answer to this and this place is my last hope.

       

      16:54:45,270 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

      16:54:47,085 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

      16:54:47,294 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

      16:54:56,224 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

      16:54:56,255 INFO  [org.xnio] XNIO Version 3.0.3.GA

      16:54:56,484 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

      16:54:56,620 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA

      16:54:56,670 INFO  [org.jboss.as.configadmin] JBAS016200: Activating ConfigAdmin Subsystem

      16:54:56,688 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

      16:54:59,785 INFO  [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.7.Final

      16:55:00,361 INFO  [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

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

      16:55:05,578 INFO  [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service

      16:55:05,913 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA

      16:55:06,069 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]

      16:55:06,435 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:55:07,477 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory D:\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\deployments

      16:55:07,618 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:9999

      16:55:07,629 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on localhost/127.0.0.1:4447

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

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

      16:55:10,194 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 29712ms - Started 133 of 208 services (74 services are passive or on-demand)

      16:56:24,648 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found JSF2MainProj.war in deployment directory. To trigger deployment create a file called JSF2MainProj.war.dodeploy

      16:56:24,748 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "JSF2MainProj.war"

      16:57:08,316 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xml-apis.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/serializer-2.7.1.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:08,318 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xercesImpl.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xalan-2.7.1.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:08,320 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xml-apis.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xalan-2.7.1.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:08,321 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry serializer.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xalan-2.7.1.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:08,323 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry lib/jaxp.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:08,325 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry lib/sax.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:08,327 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry lib/xp.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:08,328 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xslu/lib/saxon.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:08,335 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xslu/lib/resolver.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:08,337 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xslu/lib/fop.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:08,339 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xslu/lib/batik.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:08,340 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xslu/lib/logkit.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:08,342 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xslu/lib/avalon.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:08,343 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xslu/lib/jh.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:08,344 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xslu/lib/kunststoff.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:08,346 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xslu/lib/JimiProClasses.zip in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

      16:57:11,693 ERROR [org.jboss.web] (MSC service thread 1-4) JBAS018212: JSF managed bean class javax.faces.event.PhaseId has no default constructor

      16:57:13,903 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.1)

      16:57:14,085 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.web.deployment.default-host./: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./: Failed to start service

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

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_04]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_04]

        at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_04]

      Caused by: java.lang.IllegalArgumentException: Child container with name  already exists

        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:804)

        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:792)

        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:356)

        at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:62)

        at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:38)

        at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

        at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1549) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

        at org.jboss.msc.service.ServiceControllerImpl.access$1900(ServiceControllerImpl.java:49) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1780) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

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

        ... 3 more

       

       

      16:57:14,339 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "JSF2MainProj.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./: Failed to start service"}}

      16:57:15,104 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment JSF2MainProj.war in 763ms

      16:57:15,106 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report

      JBAS014777:   Services which failed to start:      service jboss.web.deployment.default-host./: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./: Failed to start service

       

       

      16:57:15,108 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.web.deployment.default-host./" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./: Failed to start service"}}}}

        • 1. Re: How do I solve this problem ?
          Stephen Coy Master

          Are you trying to deploy your application so that it is accessible from the root "/" server context?

          • 2. Re: How do I solve this problem ?
            Tomaz Cerar Master

            And also what does you web subsystem config look like?

            is this the only deployed application on that server?

            • 3. Re: How do I solve this problem ?
              Sanjeev Shrestha Novice

              Guys this is one of the major applications. I have other projects but I have closed them all and I have cleared the deployment directoru so that only the current project war file exists in the system. I had the project running in JBoss 4.2.0 but in this it doesn't work. Previously It was working in JSF 1.2 but it should be upgraded to JSF2.0 and so I linked all the jar files there are no errors in the project. There are lots of warnings though. When I run this message comes up. I Have ultimately googled and tried everywhere so I thought this was the last option. Thank you guys for the quick reply.

               

              @Stephen Coy yes I want it available from the root "/" server context and I have edited in the standalone.xml file as "false" as directed in stackoverflow topic.

               

              Im a newbie in this.

               

              @Tomaz Cerar Yes This is the only deployed application I have closed and deleted all other projects. and the deployment folder is blank.

              • 4. Re: How do I solve this problem ?
                Tomaz Cerar Master

                Hi,

                 

                please post web subsystem configuration and content of your jboss-web.xml

                • 5. Re: How do I solve this problem ?
                  Sanjeev Shrestha Novice

                  @Tomaz Cerar This is the jboss-web.xml file and by web subsystem configuration do you mean web.xml????

                   

                  <?xml version="1.0" encoding="UTF-8"?>
                  <jboss-web>
                     
                  <context-root>/</context-root>
                  </jboss-web>

                  • 6. Re: How do I solve this problem ?
                    Tomaz Cerar Master

                    web subsystem configuration, that is part of the standalone.xml

                     

                    just post the part of the web subsystem.

                    1 of 1 people found this helpful
                    • 7. Re: How do I solve this problem ?
                      Sanjeev Shrestha Novice

                      It is the same as everything I just made from enable-welcome-root="true" to enable-welcome-root="false" and that is it.

                      • 8. Re: How do I solve this problem ?
                        Stephen Coy Master

                        Sanjeev Shrestha wrote:

                         

                        ...

                        @Stephen Coy yes I want it available from the root "/" server context and I have edited in the standalone.xml file as "false" as directed in stackoverflow topic.

                         

                        Was the server stopped when you did this? It certainly seems to be complaining about duplicate web deployments of some kind.

                        1 of 1 people found this helpful
                        • 9. Re: How do I solve this problem ?
                          Sanjeev Shrestha Novice

                          Sir, Thank I just restarted eclipse and it seemed to work but how ever it application didnot run . It reaches to the following steps.

                           

                          09:41:19,338 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

                          09:41:22,104 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

                          09:41:22,246 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

                          09:41:28,537 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

                          09:41:28,569 INFO  [org.xnio] XNIO Version 3.0.3.GA

                          09:41:28,713 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

                          09:41:28,842 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA

                          09:41:29,004 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

                          09:41:29,056 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem

                          09:41:29,104 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem

                          09:41:29,104 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.

                          09:41:29,154 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

                          09:41:29,181 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

                          09:41:31,138 INFO  [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.7.Final

                          09:41:31,356 INFO  [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

                          09:41:32,223 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

                          09:41:34,868 INFO  [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service

                          09:41:35,253 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA

                          09:41:35,549 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]

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

                          09:41:36,628 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory D:\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\deployments

                          09:41:36,689 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /127.0.0.1:9999

                          09:41:36,689 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on localhost/127.0.0.1:4447

                          09:41:37,366 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

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

                          09:41:37,584 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 23027ms - Started 132 of 207 services (74 services are passive or on-demand)

                          09:42:17,587 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found JSF2MainProj.war in deployment directory. To trigger deployment create a file called JSF2MainProj.war.dodeploy

                          09:42:17,628 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "JSF2MainProj.war"

                          09:42:51,126 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xml-apis.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/serializer-2.7.1.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:51,128 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xercesImpl.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xalan-2.7.1.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:51,130 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xml-apis.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xalan-2.7.1.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:51,132 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry serializer.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xalan-2.7.1.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:51,133 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry lib/jaxp.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:51,135 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry lib/sax.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:51,136 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry lib/xp.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:51,138 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xslu/lib/saxon.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:51,139 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xslu/lib/resolver.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:51,141 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xslu/lib/fop.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:51,143 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xslu/lib/batik.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:51,144 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xslu/lib/logkit.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:51,146 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xslu/lib/avalon.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:51,148 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xslu/lib/jh.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:51,149 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xslu/lib/kunststoff.jar in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:51,151 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry xslu/lib/JimiProClasses.zip in "/D:/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/JSF2MainProj.war/WEB-INF/lib/xfc.jar"  does not point to a valid jar for a Class-Path reference.

                          09:42:54,818 ERROR [org.jboss.web] (MSC service thread 1-4) JBAS018212: JSF managed bean class javax.faces.event.PhaseId has no default constructor

                          09:42:56,582 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.1)

                           

                          Do you have any suggestions!!!

                          • 10. Re: How do I solve this problem ?
                            Stephen Coy Master

                            Please post your faces-config.xml.

                            • 11. Re: How do I solve this problem ?
                              Sanjeev Shrestha Novice

                              Sir I'm using ojdbc6.jar for the application and I sorry but I cannot post the faces-config.xml

                              • 12. Re: How do I solve this problem ?
                                Sanjeev Shrestha Novice

                                Should I be looking for something particularly in faces-config.xml sir. This is a huge project and it takes a lot of time to compile. and the xml files are linked. Any suggestion would be very helpful.

                                • 13. Re: How do I solve this problem ?
                                  Sanjeev Shrestha Novice

                                  It just doesn't repond after this

                                   

                                  Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.1)

                                   

                                  Is it the version odjc6.jar

                                  • 14. Re: How do I solve this problem ?
                                    Stephen Coy Master

                                    This is the problem we need to deal with:

                                     

                                    {code}

                                    09:42:54,818 ERROR [org.jboss.web] (MSC service thread 1-4) JBAS018212: JSF managed bean class javax.faces.event.PhaseId has no default constructor{code}

                                    and that's why we need to see your faces-config.xml.

                                     

                                    In addition, please show the result of:

                                     

                                    {code}jar -tf yourapp.war{code}

                                    1 2 3 Previous Next