WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>)

[mayerw01]

I've an application which runs on WildFly Full 10.0.0.Final. When I try to deploy this application on wildfly-12.0.0.Final (WildFly Core 4.0.0.Final) I get following messages:

.....

2018-04-04 15:07:46,586 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorSupports is deprecated from CDI 1.1!

2018-04-04 15:07:46,604 WARN  [org.jboss.weld.Bootstrap] (MSC service thread 1-8) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!

2018-04-04 15:12:33,374 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0348: Timeout after [300] seconds waiting for service container stability. Operation will roll back.

Does anybode have an idea what might be the reason?

[tremes]

I personally don't think it's a Weld problem, but you can try to enable debug log level for Weld in WF - see Weld: Documentation. Maybe you can describe your app little bit more. It is vanilla WildFly 12.0.0.Final right?

[mayerw01]

Maybe this is related to Hibernate [HV-1410] CDI Integration uses deprecated API - Hibernate JIRA .

Yes this is a vanilla WildFly 12.0.0.Final started with standalone-full.xml configuration. The database is Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit

The OS is openSUSE Leap 42.3 with kernel 4.4.120-45.

The application is more a proof of concept which I took from https://blog.holisticon.de/wp-content/uploads/2011/10/ticket2rock-2.0-dist.zip

This application should cover all aspects of JEE. It was developped and tested under JBoss 6.1.0 Final. l migrated the application to WildFly.

[negora]

I'm having exactly the same warnings that you've, when I deploy my application in Wildfly 12.0.0.Final. However, I think that the error that you're getting has no relation with that warnings. Because my application is deployed well, without any error.

My application uses JPA, EJB and servlets, just for the record.