Description of problem: It seems that module org.jboss.log4j.logmanager has a dependency on javax.mail.api, which is not specificed in its module.xml. Some of the log4j appenders (such as SMTPAppender) require java mail api classes. Version-Release number of selected component (if applicable): JBoss EAP 6.0.1 How reproducible: Very Steps to Reproduce: Deploy an application that uses an appender (for example SMTPAppender), which requires java mail api. Actual results: 13:20:18,105 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."alpha-server.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."alpha-server.ear".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "alpha-server.ear" ... Caused by: java.lang.ClassNotFoundException: javax.mail.internet.AddressException from [Module "org.jboss.log4j.logmanager:main" from local module loader @192328ef (roots: C:\projects\AFF00RSK\aff00rsksrv01\build\dist\jboss\modules)] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) ... 18 more Expected results: Dependcy on java mail api classes is met and application sucessfully deploys. Additional info: Adding <module name="javax.mail.api"/> as a dependency of module org.jboss.log4j.logmanager resolves this issue.
Is there an upstream bug for this one?
>Is there an upstream bug for this one? https://issues.jboss.org/browse/WFLY-1300
Verified in 6.3.0.DR0.
Jonathan, This issue is biting us, too, in EAP 6.2.0. Dumb question - You mention that "Adding <module name="javax.mail.api"/> as a dependency of module org.jboss.log4j.logmanager resolves this issue." First time delving into the module stuff here - could you be more specific about where this is added and the correct syntax? I've been trying but so far blowing things up pretty well.. Thanks. (In reply to Jonathan Mason from comment #0) > Description of problem: > > It seems that module org.jboss.log4j.logmanager has a dependency on > javax.mail.api, which is not specificed in its module.xml. Some of the log4j > appenders (such as SMTPAppender) require java mail api classes. > > Version-Release number of selected component (if applicable): > JBoss EAP 6.0.1 > > How reproducible: > Very > > Steps to Reproduce: > Deploy an application that uses an appender (for example SMTPAppender), > which requires java mail api. > > Actual results: > > 13:20:18,105 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) > MSC000001: Failed to start service > jboss.deployment.unit."alpha-server.ear".POST_MODULE: > org.jboss.msc.service.StartException in service > jboss.deployment.unit."alpha-server.ear".POST_MODULE: JBAS018733: Failed to > process phase POST_MODULE of deployment "alpha-server.ear" > ... > Caused by: java.lang.ClassNotFoundException: > javax.mail.internet.AddressException from [Module > "org.jboss.log4j.logmanager:main" from local module loader @192328ef (roots: > C:\projects\AFF00RSK\aff00rsksrv01\build\dist\jboss\modules)] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) > at > org.jboss.modules.ConcurrentClassLoader. > performLoadClassUnchecked(ConcurrentClassLoader.java:468) > at > org.jboss.modules.ConcurrentClassLoader. > performLoadClassChecked(ConcurrentClassLoader.java:456) > at > org.jboss.modules.ConcurrentClassLoader. > performLoadClass(ConcurrentClassLoader.java:398) > at > org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java: > 120) > ... 18 more > > > Expected results: > Dependcy on java mail api classes is met and application sucessfully deploys. > > > Additional info: > Adding <module name="javax.mail.api"/> as a dependency of module > org.jboss.log4j.logmanager resolves this issue.