-
15. Re: ejb access from one server to multiple servers
vinaykayjay Jan 24, 2013 2:27 AM (in response to jaikiran)Hi jai kiran, thanks i ve resolved this issue. It was because of firewall modification
-
16. Re: ejb access from one server to multiple servers
wdfink Jan 24, 2013 2:32 AM (in response to vinaykayjay)Hi Vinay,
It would be helpful to mark the thread as answered and mark the correct answer to help other people
-
17. Re: ejb access from one server to multiple servers
zeppelinux Jan 24, 2013 3:01 AM (in response to jaikiran)jaikirian pai wrote:
When an EJB request is handled by the EJB client library, it looks for EJB receiver(s), within the EJB client context, which can handle that EJB
Is EJB client context 'knows' about all available EJB reciecers on each destination server? At what point this info is propagated from the destination server?
-
18. Re: ejb access from one server to multiple servers
jaikiran Jan 24, 2013 3:08 AM (in response to zeppelinux)1 of 1 people found this helpfulDmitry Shultz wrote:
jaikirian pai wrote:
When an EJB request is handled by the EJB client library, it looks for EJB receiver(s), within the EJB client context, which can handle that EJB
Is EJB client context 'knows' about all available EJB reciecers on each destination server? At what point this info is propagated from the destination server?
A client context "knows" about the available EJB receivers when a receiver is registered within that context. This typically happens during application bootup (for example in standalone apps you use the jboss-ejb-client.properties which is parsed typically at boot time) or during application deployment (the jboss-ejb-client.xml on a server side deployment is parsed and receivers created out of it).
Now, after these EJB receivers which actually correspond to a destination server are registered, the destination server sends/pushes down the deployment repository (i.e. the EJB deployments available on that server) to that receiver and hence the EJB receiver and ultimately the EJB client context will know which receiver can handle which deployments (i.e. app name/ module name/ distinct name combo). This information is propagated for the first time when the receiver connects to the destination server and then each time a new deployment is added or an existing deployment removed from the destination server.
-
19. Re: ejb access from one server to multiple servers
sshyika May 16, 2013 10:30 AM (in response to zeppelinux)Hi guys,
I have the following problem, I have 3 jboss servers, two of them publishes remote EJBs (I will call them backend servers) and third is a client. On client jboss I use following jboss-ejb-client.xml:
<jboss-ejb-client xmlns="urn:jboss:ejb-client:1.0">
<client-context>
<ejb-receivers>
<remoting-ejb-receiver outbound-connection-ref="remote-ejb-backendA"/>
<remoting-ejb-receiver outbound-connection-ref="remote-ejb-backendB"/>
</ejb-receivers>
</client-context>
</jboss-ejb-client>
It works fine, client balances calls among backend servers, but when I restart one of the backend servers, client looses connection to it and doesn`t restore.
Is it possible to setup automatic reconnect from client to backend servers?
-
20. Re: ejb access from one server to multiple servers
jaikiran May 16, 2013 11:05 AM (in response to sshyika)Which exact version of AS7?
-
21. Re: ejb access from one server to multiple servers
sshyika May 16, 2013 3:01 PM (in response to jaikiran)jaikiran pai wrote:
Which exact version of AS7?
I use EAP 6.1.0 Beta
-
22. Re: ejb access from one server to multiple servers
mohammadwrk Jun 17, 2013 7:28 PM (in response to jaikiran)jaikiran pai wrote:
What about if my Client Server needs to access EJB's deployed on multiple Destination Servers? Is it supported?
Any related info/docs will be greatly appreciated.
You can configure multiple outbound connections, one each for the destination server and use a receiver for that in your jboss-ejb-client.xml.
Can we configure outbound connections dynamically to use current user instead of a predefined/fixed user (propagating subject from client-server to destination-server)?
-
23. Re: ejb access from one server to multiple servers
zeppelinux Jun 17, 2013 9:20 PM (in response to mohammadwrk)in order to use outboud conection - is has to be specified in jboss-ejb-client.xml (looks like it is the only one place), xml config can't dynamic
-
24. Re: ejb access from one server to multiple servers
mohammadwrk Jun 17, 2013 9:28 PM (in response to zeppelinux)Yes you are right! Looks like it's not supported yet :-(
https://access.redhat.com/site/solutions/190383
-
25. Re: ejb access from one server to multiple servers
zeppelinux Jun 18, 2013 1:54 AM (in response to mohammadwrk)the fact that 'principal' propagation is not supported - can be a showstoper for different reasons, but remote ejb is using different type of user for authentication with realm and all that jass... should not be mixed with 'principal'
-
26. Re: ejb access from one server to multiple servers
mohammadwrk Jun 18, 2013 11:08 AM (in response to zeppelinux)I was hoping to use dynamically generated remote-outbound-connection as a workaround for lack of prinicipal propagation!
-
27. Re: ejb access from one server to multiple servers
clichybi Jun 18, 2013 11:19 AM (in response to mohammadwrk)Sorry, but your options are very limited today:
- no 'principal' propagation or security context propagation
- no dynamic remote connections
Both are currently showstoppers for a number of application projects.
-
28. Re: ejb access from one server to multiple servers
jaikiran Jun 18, 2013 11:21 AM (in response to mohammadwrk)WildFly has the ability where you can just not configure a remote outbound connection and use JNDI API to lookup and invoke on EJBs https://github.com/wildfly/wildfly/blob/master/testsuite/integration/multinode/src/test/java/org/jboss/as/test/multinode/remotecall/scoped/context/DynamicJNDIContextEJBInvocationTestCase.java#L43
-
29. Re: ejb access from one server to multiple servers
clichybi Jun 18, 2013 11:26 AM (in response to jaikiran)Thank you Jaikiran,
that's really a good news!
Hopefully this supports also cluster access with failover, etc.