[jboss-jira] [JBoss JIRA] (JBAS-9561) Error while deploying app from JBoss 5.1.0 to JBoss 6.2
Ketan Parihar (JIRA)
issues at jboss.org
Thu May 22 02:44:56 EDT 2014
Ketan Parihar created JBAS-9561:
-----------------------------------
Summary: Error while deploying app from JBoss 5.1.0 to JBoss 6.2
Key: JBAS-9561
URL: https://issues.jboss.org/browse/JBAS-9561
Project: Application Server 3 4 5 and 6
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Ketan Parihar
HI,
I am migrating from JBoss 5.1.0 to JBoss 6.2.
but when i deploy my EAR file i get an error due to which my URL dosent work. InFact it is not able to call servlet dispatcher code. The log is as below.
11:56:57,342 INFO [org.jboss.as.security] (ServerService Thread Pool -- 42) JBAS013171: Activating Security Subsystem
11:56:57,385 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800: Activating Naming Subsystem
11:56:57,383 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 35) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
11:56:57,417 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) JBAS010280: Activating Infinispan subsystem.
11:56:57,438 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537: Activating WebServices Extension
11:56:57,564 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
11:56:57,568 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
11:56:57,612 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.19.SP2-redhat-1
11:56:57,675 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 25) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
11:56:57,841 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.23.Final-redhat-1)
11:57:00,249 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003001: Coyote HTTP/1.1 initializing on : http-localhost/127.0.0.1:8080
11:57:00,295 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003000: Coyote HTTP/1.1 starting on: http-localhost/127.0.0.1:8080
11:57:00,836 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory C:\Users\ketanpar\Ketan\Exxom\jboss-6.2\standalone\deployments
11:57:01,001 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:9999
11:57:01,003 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "pegmost.ear" (runtime-name: "pegmost.ear")
11:57:01,006 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:4447
11:57:01,316 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
11:57:01,728 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.3.Final-redhat-1
11:57:02,605 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "null" (runtime-name: "pegmost.war")
11:57:03,388 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry log4j.jar in /C:/Users/ketanpar/Ketan/Exxom/jboss-6.2/bin/content/pegmost.ear/pegmost.war/WEB-INF/lib/commons-logging.jar does not point to a valid jar for a Class-Path reference.
11:57:03,390 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015960: Class Path entry log4j-core.jar in /C:/Users/ketanpar/Ketan/Exxom/jboss-6.2/bin/content/pegmost.ear/pegmost.war/WEB-INF/lib/commons-logging.jar does not point to a valid jar for a Class-Path reference.
11:57:04,832 INFO [org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread Pool -- 49) ISPN000128: Infinispan version: Infinispan 'Delirium' 5.2.7.Final
11:57:04,925 INFO [org.infinispan.factories.TransactionManagerFactory] (ServerService Thread Pool -- 49) ISPN000161: Using a batchMode transaction manager
11:57:04,925 INFO [org.infinispan.factories.TransactionManagerFactory] (ServerService Thread Pool -- 48) ISPN000161: Using a batchMode transaction manager
11:57:05,163 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 48) ISPN000031: MBeans were successfully registered to the platform MBean server.
11:57:05,166 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 49) ISPN000031: MBeans were successfully registered to the platform MBean server.
11:57:05,169 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) JBAS010281: Started local-web cache from web container
11:57:05,169 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 49) JBAS010281: Started default-host/pegmost/servlet cache from web container
11:57:05,427 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "pegmost.ear" (runtime-name : "pegmost.ear")
11:57:05,431 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.naming.context.java.pegmost (missing) dependents: [service jboss.naming.context.java.module.pegmost.pegmost.env.jdbc.pegmost]
11:57:05,950 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
11:57:05,953 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
11:57:05,955 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) started (with errors) in 14281ms - Started 196 of 284 services (23 services failed or missing dependencies, 64 services are passive or on-demand)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
More information about the jboss-jira
mailing list