That was a bug which has been fixed in WildFly and in EAP 6.1.
Thanks Jaikiran for the answer.
Is there any way within Jboss 7.2 that i can make this to be working. can i patch or any alternative way of handling such scenarions
Hi even i Have endedup in similar error. any workaround available for the same?
Thanks in advance
Could you please let me know if there is any workaround for this scenario. or can i do a patching.
Please provide information.
You can perhaps include the remote-naming and EJB client libraries latest 1.x version in the client classpath as a workaround. But I haven't tested it so can't say what other issues you might run into.
I did it by making use of EJB lookup and dynamically setting the selector.
I got the same issue.
Can you please let me know how did you get around of this issue?
we switched from JNDI look up to ejb lookup. and also set the selecot on the fly. with this there is no need to harcode the credentials/address details in the propoerty file.
Thanks for your reply.
I use ejb lookup.as shown below,
I don't use property file. I use property object and set the values on the fly. Still, I get same error.
Can you figure out what I am missing here?
Your help on this is much appreciated.