-
1. Re: not a single clustered-invoker...
bruce2 May 21, 2004 4:31 AM (in response to bruce2)Hmm... not much response to that... After a bit of googling, I've discovered that I'm not the only person to find this particular error anyway.
http://www.junlu.com/msg/36581.html
The solution for one person seemed to be to specify a different configuration name, but "Clustered BMP EntityBean" seems appropriate for what I am doing.
This post also mentions an "<invoker-bindings>" tag and talks about detached invokers, but the only reference to invokers in the Clustering docs is an obscure footnote in the overview. There is more in the Administration and Development manual, but there is a lot of material to get through there.
Within the Clustered BMP EntityBean element in standardjboss.xml there is one sub-element that appears to configure an invoker.<invoker-proxy-binding-name>clustered-entity-rmi-invoker</invoker-proxy-binding-name>
Could this be at all relevant? -
2. Re: not a single clustered-invoker...
bruce2 May 21, 2004 4:44 AM (in response to bruce2)It occurs to me that my problem might be just that my entity beans only have local interfaces and no remote interfaces. Is it possible to cluster beans that only have local interfaces? Or are beans required to have remote interfaces for cluustering to work?
-
3. Re: not a single clustered-invoker...
bruce2 May 21, 2004 8:54 AM (in response to bruce2)It is the lack of remote interfaces that is the problem. I created a session bean with local interfaces only, and configured for clustering, and got exactly the same error message.
I added remote and remote home interfaces for one of my entity beans and it solved the problem. -
4. Re: not a single clustered-invoker...
maralcbr Apr 9, 2008 2:49 PM (in response to bruce2)Hi,
Can someone confirm the information from this last post from Bruce?
I am having the same problem with the default JBoss configurations.
I am using JBoss 4.2.2G.A. and the beans that are giving the errors are from EJB 2.
Should EJBs 2 have a remote interface to enable clustering on them? And EJBs 3? They should also? I have many ejbs 3 that have just local interfaces and they deploy fine.
Thanks in advance for any comments.
Marcelo -
5. Re: not a single clustered-invoker...
brian.stansberry Apr 9, 2008 3:11 PM (in response to bruce2)A clustered bean without a remote interface doesn't make sense. The reason you cluster a bean is so a client can load balance calls to multiple servers and fail over to a different server if one fails. Both imply remote calls.