"[EMAIL PROTECTED]" wrote : Sorry, I saw the 1st post in this thread and
replied; didn't see the rest of the thread. I'll assume your beans are marked
clustered, either via annotation or in the xml.
|
| RetryInterceptor is not yet available in EJB3. Don't think it would solve
your problem
The cause is simple; support for XML configuration of clustering was added in
EJB3 RC9 (see http://jira.jboss.com/jira/browse/EJBTHREE-569), which is after
the EJB3 release included with 4.0.4.GA. You'd need to upgrade your EJB3
release.
Sorry for not knowing this :(
View the original post :
There's another recent post of a problem with failover of beans configured with
an xml override:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=91658.
We're investigating the cause.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975652#3975652
Since I have the same ejb's in two different clusters, I am using the jboss.xml
approach with
true
for each of my sesion beans.
see: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=91189
The jboss failover code does not seem to be working though, and I get the
following exception stac
Sorry, I saw the 1st post in this thread and replied; didn't see the rest of
the thread. I'll assume your beans are marked clustered, either via annotation
or in the xml.
RetryInterceptor is not yet available in EJB3. Don't think it would solve your
problem though. I'd need to know more deta
Are your beans marked
true
in jboss.xml?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973906#3973906
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973906
___
jboss-user m
I would also like to know about that :-)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973838#3973838
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973838
___
jboss-user mai
After looking more closely at the retry interceptor wiki page, I see that it is
geared towards an older ejb, specifically the jboss.xml. Anyone know what this
file would look like for an EJB3.0 Session bean??
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973
Thanks Marc. I've notice that the error I mentioned happens sometime only when
one server is brought down, putting the client in a bad state where the cached
stub continuously fails to reconnect properly. The only way to get the client
program to work again when in that state, is to reconnect wi
If you want the client to not fail if all nodes of the cluster go down have a
look at the client retry Interceptor
http://wiki.jboss.org/wiki/Wiki.jsp?page=RetryInterceptor.
The Default for SLSB LB is RoundRobin afaik, are you looking for some specific
detail?.
Sincerely
Marc
View the origin
I am using a stateless session bean. Now it seems like it does reconnect to
the second server if the first one goes down, but if all servers in the cluster
go down and the client tries to connect when they are down, the client gets in
a state where it fails every time, even after all servers ar
Can you post some more details ? (Code snippet, Config info
(Server/Beans...)). Are you invoking on a SLSB or an SFSB ?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973175#3973175
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&m
12 matches
Mail list logo
