Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

How to access to a SessionBean in a machine since other SessionBean in other machine  RSS feed

 
lalala lalala
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi!

I'm using Jboss 4, and I would like to know, how I can access to a SessionBean in one machine since other SessionBean in other machine.

The SessionBean must be access to its jboss and the jboss of the other SessionBean.

I have been investigating and I have found that sinde a SessionBean must be access to an EntityBean of other machine (modifying jboss.xml and ejb-jar.xml)

Can anyone help me?

Thanks!
 
Valentin Tanase
Ranch Hand
Posts: 704
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

If I understand you correctly, your question is about accessing an EJB deployed onto another server instance. Because I�m not a JBoss expert, I�m goanna give you some hints but related to WebLogic (JBoss might use similar algorithms). First off all you have to understand that the server might implement a special algorithm for optimizing the access to collocated ejb objects. What I mean is this: if you have ejbA deployed to two or more WebLogic instances within a cluster and you have ejbB calling ejbA, then in order to optimize the access WebLogic will always redirect your call to the ejbA instance located on the same server instance as ejbB. And there is no way to alter this behavior. Not sure if JBoss will allow you to modify the default behavior, but I have my doubts. The only solution you have is to use a technique named "pinned services". This way you�ll use a heterogeneous deployment and you�ll deploy ejbA to a single instance in the cluster. This will force WebLogic to hit the unique ejb object, which will be located on a different server instance. Again in a homogenous deployment you have no control over the way the collocated ejb objects are called.
Regards.
 
lalala lalala
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks!!!

I have found a solution for the problem.

At the jboss.xml of my jboss, the jndi-name references to external EJB
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!