Understanding (JNDI) Binding

[Holger]

Hi, I am in the process of migrating an old client server app using JBoss 5.0.1 to Wildfly 27.
In this process I am running into trouble with the deployment throwing WFLYEE0047: Incompatible conflicting binding at java:jboss/exported/
I assumed before that this happened if multiple beans implemented the same interface which was marked as remote.
But now I am getting this message beans and interfaces which exist only once in the code.
So my understanding seems to be ways off and I am unable to find good information on this in the available documentation.
Could somebody point me in the right direction or has experienced trouble like this?
Gratefull for any help, slowly going mad.

[Jignesh Patel]

I am not able to understand the problem.

Wondering why migrate all the way from 5 to 27.

Jignesh Patel

iCare.com LLC 

Las Olas City Centre, Suite 1400
401 East Las Olas Boulevard
Fort Lauderdale, Florida  33301
Office: 954-768-7100
jig...@icare.com

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/35497b92-e498-4562-9e49-ac423605d9cbn%40googlegroups.com.

[Holger]

Thank you for replying.
I was able to solve the binding problem using the oldest trick in the book: "Have you tried turning it off and on again." I undeployed the old version(s) and restarted wildfly. So it appears the bindings persisted partly even if deployments were undeployed, removed. Kicking myself a bit.
In my understanding this conversion is the first step to add additional functionality to the application, including web facing components. And for that to be remotely viaable it can not be using 15+ year technology.

[Bartosz Baranowski]

On Friday, July 14, 2023 at 8:47:56 AM UTC+2 Holger wrote:

Thank you for replying.
I was able to solve the binding problem using the oldest trick in the book: "Have you tried turning it off and on again." I undeployed the old version(s) and restarted wildfly. So it appears the bindings persisted partly even if deployments were undeployed, removed. Kicking myself a bit.
In my understanding this conversion is the first step to add additional functionality to the application, including web facing components. And for that to be remotely viaable it can not be using 15+ year technology.

There is flaw in WFLY which cause lingering services(JNDI) to be left after deployment failure: https://issues.redhat.com/browse/WFLY-17732

 

On Friday, July 14, 2023 at 12:05:20 AM UTC+2 Jignesh Patel wrote:

I am not able to understand the problem.

Wondering why migrate all the way from 5 to 27.

5 is way different than 6, not to mention 27 - not even talking about numbers but performance, compatibility, upgrade path etc etc. AFAIR, 5-6 was a major overhaul, as well as 6+.