Incompatible conflicting binding Exception and EJB naming

[usharik]

Got wired exception for very simple EJB with @Remote annotated interface in time of deploy to WildFly 17.0.1.Final

@Stateless 
public class UserServiceImpl implements UserServiceRemote {  
      @Override 
      public List<UserRepr> getAllUsers() { 
          return null; 
      } 
}

@Remote 
public interface UserServiceRemote {  
     List<UserRepr> getAllUsers(); 
}

The exception is

Caused by: java.lang.IllegalArgumentException: WFLYEE0047: Incompatible conflicting binding at java:jboss/exported/simple-webapp/UserServiceImpl!ru.geekbrains.jsf.UserServiceRemote 
source: org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor$2@6aba1c4b"}, 
"WFLYCTL0412: Required services that are not installed:" => [ "jboss.deployment.unit.\"simple-webapp.war\".beanmanager", "jboss.deployment.unit.\"simple-webapp.war\".WeldStartService" ], 
"WFLYCTL0180: Services with missing/unavailable dependencies" => [ "jboss.deployment.unit.\"simple-webapp.war\".batch.artifact.factory is missing [jboss.deployment.unit.\"simple-webapp.war\".beanmanager]", 
"jboss.deployment.unit.\"simple-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"simple-webapp.war\".beanmanager, jboss.deployment.unit.\"simple-webapp.war\".WeldStartService]" ] }

I found out that I can resolve this problem by changing name of 'UserServiceImpl' class to 'UserServiceRemoteImpl'. Could you help me to understand what is wrong here. Is there some obligatory naming contract for EJB classes and views?

[jaikiran]

Could you post the complete exception stacktrace or even attach the server.log file?

[usharik]

Here is a part of my log file. Also logs are in my question at stackoverflow java - WFLYEE0047: Incompatible conflicting binding at - Stack Overflow

[jaikiran]

I can't reproduce this with the sample code you pasted. Are you sure the application that you are deploying isn't having another bean (class) with that same name? Maybe your packaging is accidentally packaging the bean in multiple locations/jars?

Can you post the output of:

jar -tf simple-webapp.war

[usharik]

Here is it! And thanks for your attention to my issue)

[jaikiran]

I have to say, I don't see anything odd in that attached war file content. Would it be possible for you to attach the source version of this project? One that can be locally built to reproduce this issue?

By the way, what are the contents of the beans.xml that's packaged in this war?

[usharik]

The whole code is here GitHub - usharik/simplewebapp at lesson-6-ejb
Only point to reproduce the bug you should rename class simplewebapp/UserServiceBean to UserServiceImpl and interface UserServiceRemoteBean to UserServiceRemote.

Also worth to mention that I run the Wildfly with standalone-full.xml as a config.

[usharik]

Some new workaround. Found that problem could be resolved by undeploy and Wildfly server restart. May be something wrong with JNDI content?
I've tried to look through the web console but found nothing interesting.

[brian.stansberry]

Hi Alexey,

Could you file a bug at - JBoss Issue Tracker  ? I haven't had a chance to use your reproducer but looking at the code there is nothing I saw wrong with it so this seems worth investigating as a bug.

Thanks for the report!

- Brian

[usharik]

Done [WFLY-12462] Incompatible conflicting binding Exception and EJB naming - JBoss Issue Tracker
Hope it would be helpful for the whole community!