-
1. Re: bridge related: source queue still consumes the jms request
jbertram Dec 22, 2013 11:30 PM (in response to ohmygod)Please elaborate on the MDB configuration on the source server (e.g. attach the activation configuration properties).
Also, please elaborate as to why you're using EAP 6.1 alpha when GA/Final builds of 6.1 and 6.2 are available for download.
-
2. Re: Re: bridge related: source queue still consumes the jms request
ohmygod Dec 22, 2013 11:58 PM (in response to jbertram)The reason why I am using EAP 6.1. alpha is because our project is using this version. It has not got a chance to upgrade to a newer GA/Final version.
Source MDB on source server:
@MessageDriven(messageListenerInterface = MessageListener.class, activationConfig = { @ActivationConfigProperty(propertyName = "destination", propertyValue = "source"), @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") }) @TransactionManagement(value = TransactionManagementType.BEAN)
target MDB on target server:
@MessageDriven(messageListenerInterface = MessageListener.class, activationConfig =
{
@ActivationConfigProperty(propertyName = "destination", propertyValue = "target"),
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") })
@TransactionManagement(value = TransactionManagementType.BEAN)
-
3. Re: Re: bridge related: source queue still consumes the jms request
ohmygod Dec 23, 2013 12:07 AM (in response to ohmygod)Hi Justin,
If you can help confirm this is a hornetq bug in 6.1.0 alpha version, I will ignore it and walk aournd it by not defining the source queue on source server, because so far I found the bridge works well if there is no source queue defined on server server.
-
4. Re: bridge related: source queue still consumes the jms request
jbertram Dec 23, 2013 9:56 AM (in response to ohmygod)It looks to me like you're simply creating competing consumers for the "source" queue. You have both a bridge and an MDB consuming from the "source" queue. Since only one consumer can receive a message from a queue if the MDB consumes the message then the bridge won't be able to.
My guess is that if you define the <jms-queue> you allow the MDB to actually deploy and consume messages.
-
5. Re: bridge related: source queue still consumes the jms request
jbertram Dec 23, 2013 9:57 AM (in response to ohmygod)At this point I don't think it's a bug.
-
6. Re: bridge related: source queue still consumes the jms request
ohmygod Dec 23, 2013 9:59 AM (in response to jbertram)Then how could this happen? I can not find anything unusual configuration which caused this. Do you have any idea?
-
7. Re: bridge related: source queue still consumes the jms request
jbertram Dec 23, 2013 10:01 AM (in response to ohmygod)Did you read my other reply on this thread?
-
8. Re: bridge related: source queue still consumes the jms request
ohmygod Dec 23, 2013 9:09 PM (in response to jbertram)Sorry, I missed reading your first reply. Then you think how to resolve this situation? Any method to fix this(just let bridge forward the message instead of letting source queue consumes it) if the source queue is also defined?
-
9. Re: bridge related: source queue still consumes the jms request
jbertram Dec 23, 2013 11:29 PM (in response to ohmygod)I believe I've already provided the basic answer to your question, but I'll summarize again to be clear...
In essence, the bridge is just a message consumer - it consumes messages from a "source" queue and forwards them to a "destination" address. The MDB is just a consumer as well. Therefore, if you want the bridge to always forward every message sent to the queue then you shouldn't also have an MDB consuming messages from that same queue because only one of them (either the bridge or the MDB) can get the message. That's the basic semantics of a queue.
I can't really advise you beyond that without knowing more about your application architecture and functional priorities.
-
10. Re: bridge related: source queue still consumes the jms request
ohmygod Dec 23, 2013 11:35 PM (in response to jbertram)I see. Thanks for the detailed explanation.
When you have time ,can you also ake a look at another problem I am seeing? Thanks in advance.
bridge related: not working between source server and target server from a Vitual machine