I just upgraded from 7.0.2.Final to 7.1.0.Beta1. After deploying the exact same war file that worked in 7.0.2, I am now getting CNFE's on log4j and slf4j. I tried adding those modules to the <global-modules> section of standalone.xml, but the error persists. It looks like it is coming from guava. Is there any other place that I am supposed to add these jar files? Here are the stack dumps from the log for my startup script:

After working with this all day, I finally found a solution, although I am not sure this is really the ideal fix. It looks like the dependencies for jboss logging are not correct in that module. So I added the following to modules/org/jboss/logging/main/module.xml:

<dependencies>

<modulename="org.jboss.logmanager"/>

<!-- added these 2 dependencies -->

<modulename="org.apache.log4j"/>

<modulename="org.slf4j"/>

</dependencies>

This fixed the stack dumps I was getting on startup, and so far I have not seen any adverse effects.

Adding org.apache.log4j and org.slf4j to the MANIFEST.MF dependencies inside the WAR doesn't work. I already had them in place and get the same exceptions as Ed.

Can someone from the AS7 team please comment on this issue? If Eds workaround ist the only possible way to fix the problem it should be pulled into the next release (CR1) to prevent the need to patch the predifined modules for AS7 users.

We actually have some good news on that front. We are working on having SLF4J and LOG4J available for all deployments. This means that this should no longer be an issue. It's not currently upstream yet unfortunatly, but will be very soon.

Unfortunately those changes didn't make it into the 7.1.0.CR1 release. We are however still working on them. Adding the dependency should work, but clearly it's not. Is there anyway you could send me or attach a sample WAR that causes the issue? I'd love to get in and debug it.

Sorry for the delay on the reply. I hadn't realized you sent me an example. Anyway, it looks like those errors don't seem to effect anything and are mainly noise. From my tests it seems that everything works even though those errors are logged. Arguably we need to find a way to reduce this noise, but I don't think it's anything worry about.

it looks like those errors don't seem to effect anything and are mainly noise.

Yes, i aggree and i'm nott worried about any technical effects. I'm primarily worried about the reaction of our operations team on that noise as soon as we take this into production. I'ts hard for them to differentiate what kind of noise is irrelevant and what not. So the same questions and false positives keep popping up over and over again. Therefore reducing this noise would be much appreciated.

Sadly I don't think we'll have a fix for this anytime soon. The best solution I could give at this point is change the level of the "org.jboss.weld.ClassLoading" category to WARN. That's probably a less than ideal solution, but it will prevent the noise from being printed.