-
15. Re: Remote EJB Look up in Wildfly 8.2.Final
loreno Sep 1, 2017 12:28 AM (in response to tomekadamski)Tomasz Adamski 留言:
Hi Pawel,
At present remote ejb configuration has to be done statically. Nevertheless, new version of ejb client library which we are currently developing is planned to provided extensible discovery mechanisms, among which dynamic discovery will be included. The new library should be helpful in your use case so please stay tuned for the information about it in new versions of WildFly - it is possible that it will be available in WildFly 11.
Regards,
Tomek
hi Tomasz
My application connect to many remote server dynamicallyIt works well on JBoss 4.2.3(EJB2.1), but have some problem on WildFly 10(EJB3.2)
Is it possible now? -
16. Re: Remote EJB Look up in Wildfly 8.2.Final
jaikiran Sep 1, 2017 3:10 AM (in response to loreno)1 of 1 people found this helpfulLoren Chang wrote:
Tomasz Adamski 留言:
Hi Pawel,
At present remote ejb configuration has to be done statically. Nevertheless, new version of ejb client library which we are currently developing is planned to provided extensible discovery mechanisms, among which dynamic discovery will be included. The new library should be helpful in your use case so please stay tuned for the information about it in new versions of WildFly - it is possible that it will be available in WildFly 11.
Regards,
Tomek
hi Tomasz
My application connect to many remote server dynamicallyIt works well on JBoss 4.2.3(EJB2.1), but have some problem on WildFly 10(EJB3.2)
Is it possible now?The recently release 11.0.0-CR1 version release notes states that it should be possible http://wildfly.org/news/2017/08/25/WildFly11-CR1-Released/
-
17. Re: Remote EJB Look up in Wildfly 8.2.Final
loreno Sep 1, 2017 5:58 AM (in response to jaikiran)hi jaikiran
I try test code on WildFly 11.0.0.CR1(client:wildfly-naming-client-1.0.1.Final)
client→server1→server2it seems possible now but there are still some problems
- 2 WildFly on same host>>> success
- 2 WildFly on different host >>> Fail
- client: Exception in thread "main" javax.ejb.EJBTransactionRolledbackException: Transaction rolled back
- server1: WARN [com.arjuna.ats.arjuna] (default task-31) ARJUNA012125: TwoPhaseCoordinator.beforeCompletion - failed for SynchronizationImple< 0:ffff0a140987:-44c5f711:59a92708:50, org.wildfly.transaction.client.AbstractTransaction$AssociatingSynchronization@19f110be >: org.wildfly.transaction.client.SynchronizationException: javax.transaction.xa.XAException: WFTXN0034: Failed to acquire a connection for this operation
- server2: receive a request success from server1
I will read the release first
If I can't resolve the new problem, I will create a discussion for this.thank you!!!
-
18. Re: Remote EJB Look up in Wildfly 8.2.Final
loreno Sep 18, 2017 5:45 AM (in response to pawel.predki)Pawel Predki wrote:
Hey guys,
I've been doing Remote EJB lookup in Wildfly 8.2 the same way you described here, by setting up everything in the standalone.xml file. However, we're currently developing an application that wants to connect to many remote servers, all of which are created dynamically, so it's not possible to configure the connectores beforehand, as we don't even know the IP addresses of the targets.
Is there any way to create all the needed options programatically, knowing the IP, username, password and the JNDI name of the required class?
Cheers,
Pawel
Do you resolve this issue?
-
19. Re: Remote EJB Look up in Wildfly 8.2.Final
jasonglass Nov 27, 2017 8:13 PM (in response to tomekadamski)On the Error 3, I had initially been getting naming exceptions so I added jms-1.1.jar to the deployment which made the naming exceptions go away. I also had jboss-client-7.2.0.final.jar added to fix an exception that started occurring after the naming exception was gone. I then started too get the loader constraint violation also. Removing the jms-1.1,jar from the deployment and leaving the other got rid of the exception. My .02c and thanks for the clue!