When I'm trying to deploy my gwt application (which I transformed
to a web dynamic project) I got this error :
23:46:11,559 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."TestWar.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."TestWar.war".INSTALL: Failed to process phase INSTALL of deployment "TestWar.war"
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.runWorker(Unknown Source) [rt.jar:1.7.0_75]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_75]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_75]
Caused by: javax.persistence.PersistenceException: JBAS011466: PersistenceProvider 'org.datanucleus.api.jpa.PersistenceProviderImpl' not found
at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.lookupProvider(PersistenceUnitDeploymentProcessor.java:555)
at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.deployPersistenceUnit(PersistenceUnitDeploymentProcessor.java:295)
at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.addPuService(PersistenceUnitDeploymentProcessor.java:258)
at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.handleWarDeployment(PersistenceUnitDeploymentProcessor.java:194)
at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.deploy(PersistenceUnitDeploymentProcessor.java:118)
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
I am not using any persistence, and I don't need to use it.
Help me please!
While your gwt application has created, you may be select Use Google App Engine. Because of it, there were files created like `persistence.xml' etc.
If you want simple gwt application, Don't tick on Use Google App Engine option.
Related
I have an application containing ejb2.x and ejb3.0 it is running on jboss5.1 .When we migrate with few changes in configuration and jndi it gives the following error at the time of deployment
11:42:16,884 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."intlwmiejb_.txt.jar".INSTALL: org.j boss.msc.service.StartException in service jboss.deployment.unit."intlwmiejb_.txt.jar".INSTALL: Failed to process phase INSTALL of deployment "intlwmiejb_.txt.jar"
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.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011030: Could not configure component AdminDomainManager
at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:92)
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 Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014522: Could not find method public abstract boolean javax.ejb.EJBObject.isIdentica l(javax.ejb.EJBObject) throws java.rmi.RemoteException from view com.intertel.wmi.ejb.auth.AdminDomainManager on EJB class AdminDomainManager
at org.jboss.as.ejb3.component.session.SessionBeanObjectViewConfigurator.configure(SessionBeanObjectViewConfigurator.java:108)
at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:921)
at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81)
... 6 more jndi shown on server.log is 14:42:23,647 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named AdminDomainManager in deployment unit subdeployment "intlwmiejb.jar" of deployment "wmi.ear" are as follows: java:global/wmi/intlwmiejb/AdminDomainManager!com.intertel.wmi.ejb.auth.AdminDomainManagerLocalHome java:app/intlwmiejb/AdminDomainManager!com.intertel.wmi.ejb.auth.AdminDomainManagerLocalHome java:module/AdminDomainManager!com.intertel.wmi.ejb.auth.AdminDomainManagerLocalHome java:global/wmi/intlwmiejb/AdminDomainManager!com.intertel.wmi.ejb.auth.AdminDomainManager java:app/intlwmiejb/AdminDomainManager!com.intertel.wmi.ejb.auth.AdminDomainManager java:module/AdminDomainManager!com.intertel.wmi.ejb.auth.AdminDomainManager java:jboss/exported/wmi/intlwmiejb/AdminDomainManager!com.intertel.wmi.ejb.auth.AdminDomainManager java:global/wmi/intlwmiejb/AdminDomainManager!com.intertel.wmi.ejb.auth.AdminDomainManagerHome java:app/intlwmiejb/AdminDomainManager!com.intertel.wmi.ejb.auth.AdminDomainManagerHome java:module/AdminDomainManager!com.intertel.wmi.ejb.auth.AdminDomainManagerHome java:jboss/exported/wmi/intlwmiejb/AdminDomainManager!com.intertel.wmi.ejb.auth.AdminDomainManagerHome java:global/wmi/intlwmiejb/AdminDomainManager!com.intertel.wmi.ejb.auth.AdminDomainManagerLocal java:app/intlwmiejb/AdminDomainManager!com.intertel.wmi.ejb.auth.AdminDomainManagerLocal java:module/AdminDomainManager!com.intertel.wmi.ejb.auth.AdminDomainManagerLocal
I'm tryning an integration of SPRING JPA (Hibernate Implementation ) on existant Java EE Project with INFORMIX database.
I have this error
10:18:27,982 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.persistenceunit."sigems-ear-dme.ear/sigems-ihm-dme.war#blDpiPersistenceUnit": org.jboss.msc.service.StartException in service jboss.persistenceunit."sigems-ear-dme.ear/sigems-ihm-dme.war#blDpiPersistenceUnit": 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:1145) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
Caused by: java.lang.RuntimeException: error trying to scan <jar-file>: vfs:/D:/Developpement/Produits/DME/Tools/Server/jboss711/standalone/deployments/sigems-ear-dme.ear/sigems-ihm-dme.war/WEB-INF/classes/
at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:854)
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:596)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:72)
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
Caused by: java.lang.RuntimeException: JBAS011455: Missing PersistenceUnitMetadata (thread local wasn't set)
at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getClassesInJar(HibernateAnnotationScanner.java:208)
at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:484)
at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:851)
... 9 more
Not sure what JBAS011455 is, but try to override the metadata by modifying the app bundled JBoss XML
Overriding metadata through XML
I am trying to migrating from web application (jboss 4.2) to jboss 7.1 with liferay 6.2
I have done some basic configuration .But now I am getting parsing error for web.xml which present in my war. How should I resolve this error in order to update web.xml
error-------
06:05:16,377 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."SupplierPortal.war".PARSE: org.jboss.msc
.service.StartException in service jboss.deployment.unit."SupplierPortal.war".PARSE: Failed to process phase PARSE of deployment "SupplierPortal.war"
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(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_22]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018014: Failed to parse XML descriptor "/E:/NetUploadedLiferay/liferay-portal-6.1.2-ce-ga
3/jboss-7.1.1/standalone/deployments/SupplierPortal.war/WEB-INF/web.xml" at [4,2]
at org.jboss.as.web.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:114)
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
Please help me...?
I get the next error after run jboss 7 in standalone.
16:09:35,699 ERROR [org.jboss.msc.service] (MSC service thread 1-7) MSC00002: Invocation of listener "org.jboss.as.connector.deployers.processors.ParsedRaDeploymentProcessor$1#20863d22" failed: java.lang.IllegalArgumentException: JBAS014809: A node is already registered at '(deployment => activemq-rar-5.7.0.rar)' at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:108) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.registry.AbstractResourceRegistration.registerSubModel(AbstractResourceRegistration.java:68) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.registry.AbstractResourceRegistration.registerOverrideModel(AbstractResourceRegistration.java:97) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.connector.deployers.processors.ParsedRaDeploymentProcessor$1.transition(ParsedRaDeploymentProcessor.java:181) [jboss-as-connector-7.1.1.Final.jar:7.1.1.Final] at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1416) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl.access$2700(ServiceControllerImpl.java:49) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1954) [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_31] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_31] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31]
Anybody Can help me to resolve this issue?
This is a bug in 7.1.1.Final.jar. It's because there are two ironjacamar.xml files in the path. I was able to get this to work using ailed: Jboss AS 7.2.0.Alpha1-SNAPSHOT
I am getting the following error (full stack-trace) when I try to deploy my TagsNavigation-hook.war:
14:04:37,562 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "TagsNavigation-hook.war"
14:04:37,589 INFO [org.jboss.as.jpa] (MSC service thread 1-1) added javax.persistence.api dependency to TagsNavigation-hook.war
14:04:37,596 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."TagsNavigation-hook.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."TagsNavigation-hook.war".INSTALL: Failed to process phase INSTALL of deployment "TagsNavigation-hook.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.0.2.Final.jar:7.0.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [:1.7.0_04]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [:1.7.0_04]
at java.lang.Thread.run(Unknown Source) [:1.7.0_04]
Caused by: java.lang.RuntimeException: Failed to load class com.liferay.taglib.portlet.NamespaceTag
at org.jboss.as.ee.component.deployers.EEClassConfigurationProcessor$1.compute(EEClassConfigurationProcessor.java:141)
at org.jboss.as.ee.component.deployers.EEClassConfigurationProcessor$1.compute(EEClassConfigurationProcessor.java:122)
at org.jboss.as.ee.component.LazyValue.get(LazyValue.java:40)
at org.jboss.as.ee.component.EEApplicationDescription.getClassConfiguration(EEApplicationDescription.java:183)
at org.jboss.as.ee.component.ComponentDescription.createConfiguration(ComponentDescription.java:153)
at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:70)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.0.2.Final.jar:7.0.2.Final]
... 5 more
Caused by: java.lang.ClassNotFoundException: com.liferay.taglib.portlet.NamespaceTag from [Module "deployment.TagsNavigation-hook.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:361)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:333)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:310)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:103)
at java.lang.Class.forName0(Native Method) [:1.7.0_04]
at java.lang.Class.forName(Unknown Source) [:1.7.0_04]
at org.jboss.as.ee.component.deployers.EEClassConfigurationProcessor$1.compute(EEClassConfigurationProcessor.java:139)
... 11 more
This was working before, but is not working after I undeployed by directly deleting the TagsNavigation-hook.war from the location \liferay-portal-6.1.10-ee-ga1\jboss-7.0.2\standalone\deployments, on another Jboss server I undeployed through liferay's Control Panel --> Update Manager
I tried the following:
Renaming the file TagsNavigation-hook.war.failed to TagsNavigation-hook.war.dodeploy but still the same error.
Stopping the server, then change it to TagsNavigation-hook.war.dodeploy and then restart the server but still the same thing.
Completely deleting the TagsNavigation-hook.war and TagsNavigation-hook.war.failed files and then deploying it. I tried this as a hot deployment as well as by stopping the server --> deploying --> starting the server.
Other plugin deployments (themes, hooks and portlets) are working fine. And this hook is also working fine on Tomcat-7!
Environment: Liferay 6.1.10 EE bundled with JBOSS 7.0.2 on Linux
Now it is working.
I just added this property: portal-dependency-jars=util-taglib.jar inside liferay-plugin-package.properties and then deployed.
This feels quite strange because the hook works perfectly fine on tomcat without defining the property and only on Jboss it gave this error and that too only after I undeployed it.