juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex O'Ree (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] [Updated] (JUDDI-878) Fix Jboss AS 7.x deployment
Date Fri, 16 May 2014 11:04:28 GMT

     [ https://issues.apache.org/jira/browse/JUDDI-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alex O'Ree updated JUDDI-878:
-----------------------------

    Attachment: fix.png

Ahh sorry for the confusion. You're probably looking at the tag for 3.2, whereas the fix was
posted to the trunk, which is slightly different.

This screen shot should make this more clear.

> Fix Jboss AS 7.x deployment
> ---------------------------
>
>                 Key: JUDDI-878
>                 URL: https://issues.apache.org/jira/browse/JUDDI-878
>             Project: jUDDI
>          Issue Type: Bug
>          Components: website
>            Reporter: Daniel Ferreira Castro
>            Assignee: Kurt T Stam
>            Priority: Minor
>         Attachments: Juddi.png, fix.png, git.png, jboss-web.xml, juddiv3.war, persistence.xml,
server - 20140429.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)

Mime
View raw message