Not sure if it helps you but I noticed that with the example
test-bridge-service.xml it is doing the jndi lookup for:
jboss.messaging:service=JMSProviderLoader,name=DefaultJMSProvider
This is not registered, perhaps it was in the 4.2 when messaging was manually
deployed following there instruct
We have been struggling with this for some time and I am hoping that someone
can help shed some light.
Are current architecture is as follows:
A clustered pair of JBA 4.2 servers serving up UI code
* Publishers on the UI nodes post messages to be picked up by batch nodes
A clustered pair o
We have been struggling with this for some time and I am hoping that someone
can help shed some light.
Are current architecture is as follows:
A clustered pair of JBA 4.2 servers serving up UI code
* Publishers on the UI nodes post messages to be picked up by batch nodes
A clustered pair of
