[jboss-jira] [JBoss JIRA] (WFLY-956) deploy hangs if module import doesn't exist

[Claudio Miranda (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010932#comment-13010932 ] 

Claudio Miranda commented on WFLY-956:
--------------------------------------

My system with EAP 6.3.1 was having a similar effect, where the deployment hangs. Seeing this issue I tested the described problem on EAP 6.3.1 and  WildFly Full 9.0.0.Alpha2-SNAPSHOT and this deploy hangs doesn't happen. There is a ClassNotFoundException that says exactly where is the source jar.

Caused by: java.lang.ClassNotFoundException: br.com.claudius.BeanLib2 from [Module "lib1:main" from local module loader @582178a6 (finder: local module finder @7d78077d (roots: /opt/jboss-eap-6.3/modules,/opt/jboss-eap-6.3/modules/system/layers/base/.overlays/layer-base-jboss-eap-6.3.1.CP,/opt/jboss-eap-6.3/modules/system/layers/base))]  

As this an old issue, perhaps it was just fixed by accident.

> deploy hangs if module import doesn't exist
> -------------------------------------------
>
>                 Key: WFLY-956
>                 URL: https://issues.jboss.org/browse/WFLY-956
>             Project: WildFly
>          Issue Type: Bug
>          Components: Class Loading
>            Reporter: Bill Burke
>            Assignee: David Lloyd
>
> If you have a module dependency and that module has its own dependency that doesn't exist, deployment will hang.
> To reproduce, create a simple WAR that has a jboss-deployment-structure.xml that imports an existing module.  Have that existing module import a different module that doesn't exist.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)