No. We got away from using JBM recovery for number of reasons. Implemented
custom XA based solution.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218656#4218656
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218656
I forgot to say:
JB 4.2.3
JBM 1.4.2.SP1
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218169#4218169
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218169
___
jboss-user ma
Hi!
Have you solved that issue? I have the same behavior with my bridges.
I have multiple nodes connected to one "root" node via bridges.
In that root node all bridges are configured and usinf remoteProviderLoaders.
I have added them on the jta configuration like:
|
|
|
|
Can anybody comment on this, please?
I think JBM recovery code is expected to handle the remote resource restart.
To restate the problem. I have recovery configured on the JMS client, which
connects to the remote server. If I bounce (restart) the remote server, the
recovery module starts giving
Sorry for confusion, but I was trying to say that "server which hosts that
resource" was restarted, not just stopped (kill server A and then start it
again). And even after it is back, the server which runs the transaction would
keep logging the warning.
So I have both server up and running, my
"szhigunov" wrote : Hi,
| I am testing JBM XA recovery. I have two JBoss servers. Server A runs a
non-clustered queue. Server B runs a JMS listener, which connects to server A
through JCA + remote JMS provider. I added the following configuration to
server B (where TM is running) to turn the r
