You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Daniel Ferreira Castro (JIRA)" <ju...@ws.apache.org> on 2014/05/22 19:55:04 UTC
[jira] [Comment Edited] (JUDDI-878) Fix Jboss AS 7.x deployment
[ https://issues.apache.org/jira/browse/JUDDI-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006182#comment-14006182 ]
Daniel Ferreira Castro edited comment on JUDDI-878 at 5/22/14 5:53 PM:
-----------------------------------------------------------------------
This was done already on May, 12sd of this year.
I did it again, no problem at all in doing that.
The modules.xml is like that
-----------------
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.1" name="org.apache.openjpa">
<resources>
<resource-root path="openjpa-2.2.1.jar"/>
<resource-root path="serp-1.13.1.jar"/>
</resources>
<dependencies>
<module name="javax.persistence.api"/>
<module name="javax.transaction.api"/>
<module name="javax.validation.api"/>
<module name="org.apache.commons.lang"/>
<module name="org.apache.commons.collections"/>
<module name="org.apache.log4j"/>
</dependencies>
</module>
-----------------
The files inside the filesystem are
- openjpa-2.2.1.jar
- serp-1.13.1.jar
After that I start my server
And get that
14:52:11,507 INFO [org.jboss.as.jpa] (MSC service thread 1-5) JBAS011401: Read persistence.xml for juddiDatabase
14:52:11,565 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.module.service."deployment.juddiv3.war".main: org.jboss.msc.service
.StartException in service jboss.module.service."deployment.juddiv3.war".main: Failed to load module: deployment.juddiv3.war:main
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [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_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: org.jboss.modules.ModuleNotFoundException: Module org.apache.openjpa:main is not found in local module loader @1dd0fe7 (roots: C:\Java\jboss-as-7.1.1.Final\modules)
at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.Module.addPaths(Module.java:841) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.Module.link(Module.java:1181) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1207) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208) [jboss-modules.jar:1.1.1.GA]
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
14:52:11,816 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jaxb-api.jar in "/C:/Java/jboss-as-7.1.1.Final/bin/content/juddi-gui.war/WEB-INF/lib/j
axb-impl-2.2.6.jar" does not point to a valid jar for a Class-Path reference.
14:52:11,829 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015893: Encountered invalid class name 'org.springframework.context.ApplicationContext,org.springfr
amework.beans.BeansException,org.springframework.beans.factory.xml.NamespaceHandlerResolver' for service type 'org.apache.cxf.bus.factory'
14:52:11,910 WARN [org.jboss.as.ee] (MSC service thread 1-2) JBAS011006: Not installing optional component org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Conti
nuation due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.apache.cxf.transport.http.S
ervlet3ContinuationProvider$Servlet3Continuation
at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606)
at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [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_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
was (Author: danielfcastro):
This was done already on May, 12sd of this year.
As you can see the file content is the same.
Both jar files are there as well: openjpa-all-2.2.1.jar and serp-1.13.1.jar
> Fix Jboss AS 7.x deployment
> ---------------------------
>
> Key: JUDDI-878
> URL: https://issues.apache.org/jira/browse/JUDDI-878
> Project: jUDDI
> Issue Type: Bug
> Components: core, documentation, website
> Reporter: Daniel Ferreira Castro
> Assignee: Kurt T Stam
> Priority: Minor
> Fix For: 3.2.1
>
> Attachments: Install.java, Juddi.png, boot.log, fix.png, git.png, jboss-web.xml, juddiv3 (jboss7).war, modules.xml, persistence.xml, server - 20140429.log, server.log
>
>
> The online Apache jUDDI Guide specifies at the end of this link (OpenJPA and JBossWS-CXF) http://juddi.apache.org/docs/3.2/juddi-guide/html_single/#_jbossas_7_x_jbosseap_6_x
> says "and in the `modules/system/layers/base/org/jboss/as/jpa/main/module.xml add dependency <module name="org.jboss.as.jpa.openjpa"/>"
> But this folder structure does not exists on jboss-as7 and there is no previous instructions about how to create it and what to put i in. There are tow previous instrctions to create:
> <jboss>/modules/system/layers/base/org/apache/openjpa/main and
> <jboss>/modules/system/layers/base/org/jboss/as/jpa/openjpa/main
> but not <jboss>/modules/system/layers/base/org/jboss/as/jpa/main/module.xml
> So, when I try to deploy it to Jboss AS 7.1.1 I get an exception
> 11:42:43,356 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for juddiDatabase
> 11:42:43,864 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.module.service."deployment.juddiv3.war".main: org.jboss.msc.service
> .StartException in service jboss.module.service."deployment.juddiv3.war".main: Failed to load module: deployment.juddiv3.war:main
> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [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:1110) [rt.jar:1.7.0_11]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_11]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_11]
> Caused by: org.jboss.modules.ModuleNotFoundException: Module org.apache.openjpa:main is not found in local module loader @655c8c (roots: c:\Java\jboss-as-7.1.1.Final\modules)
> at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126)
> at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275)
> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222)
> at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94)
> at org.jboss.modules.Module.addPaths(Module.java:841)
> at org.jboss.modules.Module.link(Module.java:1181)
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1207)
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208)
> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> ... 5 more
> 11:42:44,112 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "juddiv3.war" was rolled back with failure message {"JBAS014671: Failed se
> rvices" => {"jboss.module.service.\"deployment.juddiv3.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.juddiv3.war\".main: Failed
> to load module: deployment.juddiv3.war:main"}}
> 11:42:44,272 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment juddiv3.war in 159ms
> 11:42:44,274 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.module.service."deployment.juddiv3.war".main: org.jboss.msc.service.StartException in service jboss.module.service.
> "deployment.juddiv3.war".main: Failed to load module: deployment.juddiv3.war:main
> 11:42:44,283 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"O
> peration step-2" => {"JBAS014671: Failed services" => {"jboss.module.service.\"deployment.juddiv3.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.servi
> ce.\"deployment.juddiv3.war\".main: Failed to load module: deployment.juddiv3.war:main"}}}}
--
This message was sent by Atlassian JIRA
(v6.2#6252)