Bolder: Failed to start jboss 7.1.1 service. Why?

Failed to start jboss 7.1.1 service. Why?

I migrate from jboss5 to jboss7 for deploy ear file for make web service.
But I get the following error:
ERROR [org.jboss.msc.service.fail] ... MSC00001: Failed to start service
in jboss7.1.1 ... jboss.persistenceunit
Why does this happen and how do I solve the problem?
Below I have tried to explain my configuration and what I have done.
I edit dependencies in META-INF/MANIFEST.MF file.
Dependencies:
com.sahand.common.util,com.sahand.common.security,com.sahand.model.common,com.sahand.model.user.management,com.sahand.model.security,com.sahand.security.api,com.sahand.security.persistence,com.sahand.security.service,org.apache.commons.codec,org.slf4j,ch.qos.logback.core,ch.qos.logback.classic,javax.validation.api,org.hibernate.validator
File persistence.xml in project:
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="
http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="pu-security">


<jta-data-source>java:jboss/datasources/securityDS</jta-data-source>


<class>com.sahand.common.model.UserAudit</class>
<class>com.sahand.security.model.UserSession</class>
<class>com.sahand.management.model.SystemAction</class>
<class>com.sahand.management.model.User</class>
<class>com.sahand.management.model.User2Group</class>
<class>com.sahand.management.model.UserGroup</class>
<class>com.sahand.management.model.UserGroup2Transaction</class>

<properties>
<property name="hibernate.dialect"
value="org.hibernate.dialect.Oracle10gDialect" />
<property name="hibernate.hbm2ddl.auto" value="none" />
<property name="hibernate.show_sql" value="true" />
<property name="hibernate.format_sql" value="true" />
</properties>
</persistence-unit>
</persistence>
File persistence.xml in ear file:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC
"-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
"http://java.sun.com/dtd/application_1_3.dtd">
<application>
<display-name>sahand-security-product</display-name>
<description>Our Products</description>
<module>
<ejb>sahand-security-persistence-5.0.0-SNAPSHOT.jar</ejb>
</module>
<module>
<ejb>sahand-security-service-5.0.0-SNAPSHOT.jar</ejb>
</module>
</application>
I create any modules in jboss7.1.1 that used in my project from this
template:
How+do+I+migrate+my+application+from+AS5+or+AS6+to+AS
I receive the following message using jboss7.1.1:
Calling
"F:\morteza-pooladi-share\JAVA\tools\jboss-as-7.1.1.Final\bin\standalone.conf.bat"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: F:\morteza-pooladi-share\JAVA\tools\jboss-as-7.1.1.Final
JAVA: D:\java\jdk1.6.0_21\bin\java
JAVA_OPTS: -XX:+TieredCompilation -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
===============================================================================
14:39:41,525 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
14:39:41,696 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
14:39:41,728 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final
"Brontes" starting
14:39:42,400 INFO [org.xnio] XNIO Version 3.0.3.GA
14:39:42,400 INFO [org.jboss.as.server] JBAS015888: Creating http
management service using socket-binding (management-http)
14:39:42,400 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
14:39:42,415 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
14:39:42,431 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap
log handlers
14:39:42,493 INFO [org.jboss.as.configadmin] (ServerService Thread Pool
-- 26) JBAS016200: Activating ConfigAdmin Subsystem
14:39:42,509 INFO [org.jboss.as.security] (ServerService Thread Pool --
44) JBAS013101: Activating Security Subsystem
14:39:42,509 INFO [org.jboss.as.webservices] (ServerService Thread Pool
-- 48) JBAS015537: Activating WebServices Extension
14:39:42,525 INFO [org.jboss.as.security] (MSC service thread 1-1)
JBAS013100: Current PicketBox version=4.0.7.Final
14:39:42,525 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39)
JBAS011940: Activating OSGi Subsystem
14:39:42,525 INFO [org.jboss.as.clustering.infinispan] (ServerService
Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
14:39:42,525 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38)
JBAS011800: Activating Naming Subsystem
14:39:42,603 INFO [org.jboss.as.naming] (MSC service thread 1-7)
JBAS011802: Starting Naming Service
14:39:42,618 INFO [org.jboss.as.connector] (MSC service thread 1-5)
JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
14:39:42,634 INFO [org.jboss.as.connector.subsystems.datasources]
(ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant
driver class oracle.jdbc.OracleDriver (version 1.0)
14:39:42,634 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5)
JBAS015400: Bound mail session [java:jboss/mail/Default]
14:39:42,853 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service
thread 1-3) Starting Coyote HTTP/1.1 on http--192.168.7.167-8080
14:39:43,071 INFO [org.jboss.ws.common.management.AbstractServerConfig]
(MSC service thread 1-5) JBoss Web Services - Stack CXF Server 4.0.2.GA
14:39:43,290 INFO [org.jboss.as.server.deployment.scanner] (MSC service
thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory
F:\morteza-pooladi-share\JAVA\tools\jboss-as-7.1.1.Final\standalone\deployments
14:39:43,306 INFO [org.jboss.as.remoting] (MSC service thread 1-6)
JBAS017100: Listening on /192.168.7.167:9999
14:39:43,306 INFO [org.jboss.as.remoting] (MSC service thread 1-8)
JBAS017100: Listening on /192.168.7.167:4447
14:39:43,353 INFO [org.jboss.as.connector.subsystems.datasources] (MSC
service thread 1-5) JBAS010400: Bound data source
[java:jboss/datasources/securityDS]
14:39:43,415 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service
thread 1-7) Starting Coyote HTTP/1.1 on http--192.168.7.167-8443
14:39:43,431 INFO [org.jboss.as.server.deployment] (MSC service thread
1-1) JBAS015876: Starting deployment of "sahand-security.ear"
14:39:43,759 INFO [org.jboss.as.server.deployment] (MSC service thread
1-8) JBAS015876: Starting deployment of
"sahand-security-service-5.0.0-SNAPSHOT.jar"
14:39:43,759 INFO [org.jboss.as.server.deployment] (MSC service thread
1-6) JBAS015876: Starting deployment of
"sahand-security-persistence-5.0.0-SNAPSHOT.jar"
14:39:43,806 INFO [org.jboss.as.jpa] (MSC service thread 1-6) JBAS011401:
Read persistence.xml for pu-security
14:39:43,868 INFO
[org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor]
(MSC service thread 1-7) JNDI bindings for session bean named
QueryManagementImpl in deployment unit subdeployment
"sahand-security-persistence-5.0.0-SNAPSHOT.jar" of deployment
"sahand-security.ear" are as follows:
java:global/sahand-security/sahand-security-persistence-5.0.0-SNAPSHOT/QueryManagementImpl!com.sahand.security.action.QueryManagement
java:app/sahand-security-persistence-5.0.0-SNAPSHOT/QueryManagementImpl!com.sahand.security.action.QueryManagement
java:module/QueryManagementImpl!com.sahand.security.action.QueryManagement
java:global/sahand-security/sahand-security-persistence-5.0.0-SNAPSHOT/QueryManagementImpl
java:app/sahand-security-persistence-5.0.0-SNAPSHOT/QueryManagementImpl
java:module/QueryManagementImpl
14:39:43,884 INFO
[org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor]
(MSC service thread 1-1) JNDI bindings for session bean named SecurityImpl
in deployment unit subdeployment
"sahand-security-service-5.0.0-SNAPSHOT.jar" of deployment
"sahand-security.ear" are as follows:
14:39:43,884 INFO
[org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor]
(MSC service thread 1-7) JNDI bindings for session bean named
SecurityManagementImpl in deployment unit subdeployment
"sahand-security-persistence-5.0.0-SNAPSHOT.jar" of deployment
"sahand-security.ear" are as follows:
java:global/sahand-security/sahand-security-persistence-5.0.0-SNAPSHOT/SecurityManagementImpl!com.sahand.security.action.SecurityManagement
java:app/sahand-security-persistence-5.0.0-SNAPSHOT/SecurityManagementImpl!com.sahand.security.action.SecurityManagement
java:module/SecurityManagementImpl!com.sahand.security.action.SecurityManagement
java:global/sahand-security/sahand-security-persistence-5.0.0-SNAPSHOT/SecurityManagementImpl
java:app/sahand-security-persistence-5.0.0-SNAPSHOT/SecurityManagementImpl
java:module/SecurityManagementImpl
14:39:43,884 INFO
[org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor]
(MSC service thread 1-1) JNDI bindings for session bean named
SecurityProcessorImpl in deployment unit subdeployment
"sahand-security-service-5.0.0-SNAPSHOT.jar" of deployment
"sahand-security.ear" are as follows:
java:global/sahand-security/sahand-security-service-5.0.0-SNAPSHOT/SecurityProcessorImpl!com.sahand.security.action.SecurityProcessor
java:app/sahand-security-service-5.0.0-SNAPSHOT/SecurityProcessorImpl!com.sahand.security.action.SecurityProcessor
java:module/SecurityProcessorImpl!com.sahand.security.action.SecurityProcessor
java:global/sahand-security/sahand-security-service-5.0.0-SNAPSHOT/SecurityProcessorImpl
java:app/sahand-security-service-5.0.0-SNAPSHOT/SecurityProcessorImpl
java:module/SecurityProcessorImpl
14:39:44,134 INFO [org.jboss.as.jpa] (MSC service thread 1-5) JBAS011402:
Starting Persistence Unit Service
'sahand-security.ear/sahand-security-persistence-5.0.0-SNAPSHOT.jar#pu-security'
14:39:44,150 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC
service thread 1-6) Add Service
id=SecurityImpl
address=http://192.168.7.167:8080/sahand-security-service-5.0.0-SNAPSHOT/SecurityImpl
implementor=com.sahand.security.service.SecurityImpl
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://service.security.sahand.com/}SecurityImplService
portName={http://service.security.sahand.com/}SecurityImplPort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName
-> service
jboss.deployment.subunit."sahand-security.ear"."sahand-security-service-5.0.0-SNAPSHOT.jar".component.SecurityImpl.VIEW."com.sahand.security.service.SecurityImpl".SERVICE_ENDPOINT]
14:39:44,228 INFO [org.hibernate.annotations.common.Version] (MSC service
thread 1-5) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
14:39:44,228 INFO [org.hibernate.Version] (MSC service thread 1-5)
HHH000412: Hibernate Core {4.0.1.Final}
14:39:44,228 INFO [org.hibernate.cfg.Environment] (MSC service thread
1-5) HHH000206: hibernate.properties not found
14:39:44,228 INFO [org.hibernate.cfg.Environment] (MSC service thread
1-5) HHH000021: Bytecode provider name : javassist
14:39:44,243 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service
thread 1-5) HHH000204: Processing PersistenceUnitInfo [
name: pu-security
...]
14:39:44,446 INFO
[org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service
thread 1-6) Creating Service
{http://service.security.sahand.com/}SecurityImplService from class
com.sahand.security.service.SecurityImpl
14:39:44,790 INFO
[org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator]
(MSC service thread 1-5) HHH000130: Instantiating explicit connection
provider:
org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
14:39:45,087 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service
thread 1-6) Setting the server's publish address to be
http://192.168.7.167:8080/sahand-security-service-5.0.0-SNAPSHOT/SecurityImpl
14:39:45,415 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher]
(MSC service thread 1-6) WSDL published to:
file:/F:/morteza-pooladi-share/JAVA/tools/jboss-as-7.1.1.Final/standalone/data/wsdl/sahand-security.ear/sahand-security-service-5.0.0-SNAPSHOT.jar/SecurityImplService.wsdl
14:39:45,415 INFO [org.jboss.as.webservices] (MSC service thread 1-3)
JBAS015539: Starting service jboss.ws.port-component-link
14:39:45,431 INFO [org.jboss.as.webservices] (MSC service thread 1-3)
JBAS015539: Starting service
jboss.ws.endpoint."sahand-security.ear"."sahand-security-service-5.0.0-SNAPSHOT.jar".SecurityImpl
14:39:45,431 INFO
[org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service
thread 1-3) register:
jboss.ws:context=sahand-security-service-5.0.0-SNAPSHOT,endpoint=SecurityImpl
14:39:45,446 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210:
Registering web context: /sahand-security-service-5.0.0-SNAPSHOT
14:39:46,196 WARN [org.hibernate.engine.jdbc.internal.JdbcServicesImpl]
(MSC service thread 1-5) HHH000341: Could not obtain connection metadata :
Unsupported feature
14:39:46,196 INFO [org.hibernate.engine.jdbc.internal.LobCreatorBuilder]
(MSC service thread 1-5) HHH000422: Disabling contextual LOB creation as
connection was null
14:39:46,196 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5)
MSC00001: Failed to start service
jboss.persistenceunit."sahand-security.ear/sahand-security-persistence-5.0.0-SNAPSHOT.jar#pu-security":
org.jboss.msc.service.StartException in service
jboss.persistenceunit."sahand-security.ear/sahand-security-persistence-5.0.0-SNAPSHOT.jar#pu-security":
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$Worker.runTask(ThreadPoolExecutor.java:886)
[rt.jar:1.6.0_21]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[rt.jar:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]
Caused by: java.lang.NullPointerException
at
org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:209)
at
org.hibernate.service.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:75)
at
org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:159)
at
org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:131)
at
org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:71)
at
org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2270)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2266)
at
org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1735)
at
org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:84)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:904)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:889)
at
org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73)
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
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]
... 3 more
14:39:46,228 INFO [org.jboss.as] (MSC service thread 1-5) JBAS015951:
Admin console listening on http://192.168.7.167:9990
14:39:46,228 ERROR [org.jboss.as] (MSC service thread 1-5) JBAS015875:
JBoss AS 7.1.1.Final "Brontes" started (with errors) in 4891ms - Started
260 of 346 services (5 services failed or missing dependencies, 80
services are passive or on-demand)
14:39:46,431 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2)
JBAS015870: Deploy of deployment "sahand-security.ear" was rolled back
with failure message {"JBAS014671: Failed services" =>
{"jboss.persistenceunit.\"sahand-security.ear/sahand-security-persistence-5.0.0-SNAPSHOT.jar#pu-security\""
=> "org.jboss.msc.service.StartException in service
jboss.persistenceunit.\"sahand-security.ear/sahand-security-persistence-5.0.0-SNAPSHOT.jar#pu-security\":
Failed to start service"}}
14:39:46,431 INFO [org.jboss.as.webservices] (MSC service thread 1-3)
JBAS015540: Stopping service
jboss.ws.endpoint."sahand-security.ear"."sahand-security-service-5.0.0-SNAPSHOT.jar".SecurityImpl
14:39:46,446 INFO
[org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service
thread 1-3) remove:
jboss.ws:context=sahand-security-service-5.0.0-SNAPSHOT,endpoint=SecurityImpl
14:39:46,446 INFO [org.jboss.as.webservices] (MSC service thread 1-3)
JBAS015540: Stopping service jboss.ws.port-component-link
14:39:46,462 INFO [org.jboss.as.server.deployment] (MSC service thread
1-5) JBAS015877: Stopped deployment
sahand-security-persistence-5.0.0-SNAPSHOT.jar in 35ms
14:39:46,462 INFO [org.jboss.as.server.deployment] (MSC service thread
1-7) JBAS015877: Stopped deployment
sahand-security-service-5.0.0-SNAPSHOT.jar in 35ms
14:39:46,493 INFO [org.jboss.as.server.deployment] (MSC service thread
1-6) JBAS015877: Stopped deployment sahand-security.ear in 60ms
14:39:46,493 INFO [org.jboss.as.controller] (DeploymentScanner-threads -
2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service
jboss.persistenceunit."sahand-security.ear/sahand-security-persistence-5.0.0-SNAPSHOT.jar#pu-security":
org.jboss.msc.service.StartException in service
jboss.persistenceunit."sahand-security.ear/sahand-security-persistence-5.0.0-SNAPSHOT.jar#pu-security":
Failed to start service
14:39:46,493 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.persistenceunit.\"sahand-security.ear/sahand-security-persistence-5.0.0-SNAPSHOT.jar#pu-security\""
=> "org.jboss.msc.service.StartException in service
jboss.persistenceunit.\"sahand-security.ear/sahand-security-persistence-5.0.0-SNAPSHOT.jar#pu-security\":
Failed to start service"}}}}
14:55:55,459 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap
log handlers
14:55:55,459 INFO [org.jboss.as.connector.subsystems.datasources]
JBAS010409: Unbound data source [java:jboss/datasources/securityDS]
14:55:55,459 INFO [org.apache.coyote.http11.Http11Protocol] Pausing
Coyote HTTP/1.1 on http--192.168.7.167-8443
14:55:55,459 INFO [org.apache.coyote.http11.Http11Protocol] Stopping
Coyote HTTP/1.1 on http--192.168.7.167-8443
14:55:55,459 INFO [org.apache.coyote.http11.Http11Protocol] Pausing
Coyote HTTP/1.1 on http--192.168.7.167-8080
14:55:55,459 WARN [org.jboss.remoting.remote] JBREM000205: Failed to
accept a connection: java.nio.channels.ClosedChannelException
14:55:55,459 INFO [org.apache.coyote.http11.Http11Protocol] Stopping
Coyote HTTP/1.1 on http--192.168.7.167-8080
14:55:55,615 INFO [com.arjuna.ats.jbossatx] ARJUNA032018: Destroying
TransactionManagerService
14:55:55,615 INFO [com.arjuna.ats.jbossatx] ARJUNA032014: Stopping
transaction recovery manager
14:55:55,631 INFO [org.jboss.as] JBAS015950: JBoss AS 7.1.1.Final
"Brontes" stopped in 162ms
Please help me. Thanks.

Bolder

Sunday, 8 September 2013

Failed to start jboss 7.1.1 service. Why?

No comments:

Post a Comment