You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by atchijov <an...@tchijov.com> on 2015/09/14 02:56:27 UTC
Using Standalone ActiveMQ with Wildfly
I am trying to make ActiveMQ 5.12 and Wildfly 8.2 work on AWS
I have came up with following configuration:
- two ActiveMQ servers (AMQ1, AMQ2) with static network connectors pointing
to each other.
- one ActiveMQ (AMQW1, AMQW2, ...) server per each Wildfly server (WF1, WF2,
...) with static network connectors pointing to AMQ1 and AMQ2
- Wildly configured as per
https://developer.jboss.org/wiki/HowToUseOutOfProcessActiveMQWithWildFly and
act as both producer and consumer of messages on the topic
It is almost works... When I send message (using ActiveMQ Web Interface)
from either AMQ1 or AMQ2 - all WF servers receive the message. But when one
of the WF servers produce message, the same server receive this message, but
no one else.
This gist contains all relevant configuration files:
https://gist.github.com/leapingbytes/a432d40f9fdc11b7d896
I would be more than happy to provide any additional information.
Your help would be highly appreciated.
Cheers,
Andrei
--
View this message in context: http://activemq.2283324.n4.nabble.com/Using-Standalone-ActiveMQ-with-Wildfly-tp4701969.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Using Standalone ActiveMQ with Wildfly
Posted by Tim Bain <tb...@alumni.duke.edu>.
Sorry, not all, only the AMQ-AMQW ones. The AMQ1-AMQ2 connection is
already connected in both directions.
On Sep 23, 2015 8:31 AM, "Tim Bain" <tb...@alumni.duke.edu> wrote:
> Try your original configuration with duplex="true" on all
> networkConnectors.
> On Sep 23, 2015 8:15 AM, "atchijov" <an...@tchijov.com> wrote:
>
>> Hi Tim,
>> Sorry for not been clear enough.
>>
>> AMQ1 has IP 10.0.1.53 and its configuration points to 10.0.1.200:61616
>> AMQ2 has IP 10.0.1.200 and its configuration points to 10.0.1.53:61616
>>
>> The idea is to keep at least one of these two alive at all times... and
>> if
>> one of them goes down, it would be able to re-join cluster via another
>> one.
>>
>> Make sense?
>>
>> Also... I sort of get over this particular problem by getting rid of
>> AMQW1, AMQW2 and using
>>
>>
>> failover:(tcp://
>> 10.0.1.53:61616?wireFormat.maxInactivityDuration=0,tcp://10.0.1.200:61616?wireFormat.maxInactivityDuration=0)?jms.rmIdFromConnectionId=true&initialReconnectDelay=100
>>
>> as ServerUrl in Wildfly resource-adapter configuration. It mostly
>> work...
>> the only problem now -
>>
>> http://activemq.2283324.n4.nabble.com/ActiveMQ-reports-Successfully-connected-to-and-Failed-to-connect-to-at-the-same-time-tp4702034.html
>>
>> Cheers,
>> Andrei
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://activemq.2283324.n4.nabble.com/Using-Standalone-ActiveMQ-with-Wildfly-tp4701969p4702225.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
Re: Using Standalone ActiveMQ with Wildfly
Posted by Tim Bain <tb...@alumni.duke.edu>.
Try your original configuration with duplex="true" on all networkConnectors.
On Sep 23, 2015 8:15 AM, "atchijov" <an...@tchijov.com> wrote:
> Hi Tim,
> Sorry for not been clear enough.
>
> AMQ1 has IP 10.0.1.53 and its configuration points to 10.0.1.200:61616
> AMQ2 has IP 10.0.1.200 and its configuration points to 10.0.1.53:61616
>
> The idea is to keep at least one of these two alive at all times... and
> if
> one of them goes down, it would be able to re-join cluster via another one.
>
> Make sense?
>
> Also... I sort of get over this particular problem by getting rid of
> AMQW1, AMQW2 and using
>
>
> failover:(tcp://
> 10.0.1.53:61616?wireFormat.maxInactivityDuration=0,tcp://10.0.1.200:61616?wireFormat.maxInactivityDuration=0)?jms.rmIdFromConnectionId=true&initialReconnectDelay=100
>
> as ServerUrl in Wildfly resource-adapter configuration. It mostly
> work...
> the only problem now -
>
> http://activemq.2283324.n4.nabble.com/ActiveMQ-reports-Successfully-connected-to-and-Failed-to-connect-to-at-the-same-time-tp4702034.html
>
> Cheers,
> Andrei
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Using-Standalone-ActiveMQ-with-Wildfly-tp4701969p4702225.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Re: Using Standalone ActiveMQ with Wildfly
Posted by atchijov <an...@tchijov.com>.
Hi Tim,
Sorry for not been clear enough.
AMQ1 has IP 10.0.1.53 and its configuration points to 10.0.1.200:61616
AMQ2 has IP 10.0.1.200 and its configuration points to 10.0.1.53:61616
The idea is to keep at least one of these two alive at all times... and if
one of them goes down, it would be able to re-join cluster via another one.
Make sense?
Also... I sort of get over this particular problem by getting rid of
AMQW1, AMQW2 and using
failover:(tcp://10.0.1.53:61616?wireFormat.maxInactivityDuration=0,tcp://10.0.1.200:61616?wireFormat.maxInactivityDuration=0)?jms.rmIdFromConnectionId=true&initialReconnectDelay=100
as ServerUrl in Wildfly resource-adapter configuration. It mostly work...
the only problem now -
http://activemq.2283324.n4.nabble.com/ActiveMQ-reports-Successfully-connected-to-and-Failed-to-connect-to-at-the-same-time-tp4702034.html
Cheers,
Andrei
--
View this message in context: http://activemq.2283324.n4.nabble.com/Using-Standalone-ActiveMQ-with-Wildfly-tp4701969p4702225.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Using Standalone ActiveMQ with Wildfly
Posted by Tim Bain <tb...@alumni.duke.edu>.
I'm having trouble figuring out why AMQ1 and AMQW1 both have a
networkConnector that points to the same endpoint. Can you explain how
10.0.1.53:61616 and 10.0.1.200:61616 map to AMQ1/AMQ2/AMQW1/AMQW2?
Tim
On Sun, Sep 13, 2015 at 6:56 PM, atchijov <an...@tchijov.com> wrote:
> I am trying to make ActiveMQ 5.12 and Wildfly 8.2 work on AWS
>
> I have came up with following configuration:
>
> - two ActiveMQ servers (AMQ1, AMQ2) with static network connectors pointing
> to each other.
> - one ActiveMQ (AMQW1, AMQW2, ...) server per each Wildfly server (WF1,
> WF2,
> ...) with static network connectors pointing to AMQ1 and AMQ2
> - Wildly configured as per
> https://developer.jboss.org/wiki/HowToUseOutOfProcessActiveMQWithWildFly
> and
> act as both producer and consumer of messages on the topic
>
> It is almost works... When I send message (using ActiveMQ Web Interface)
> from either AMQ1 or AMQ2 - all WF servers receive the message. But when one
> of the WF servers produce message, the same server receive this message,
> but
> no one else.
>
> This gist contains all relevant configuration files:
> https://gist.github.com/leapingbytes/a432d40f9fdc11b7d896
>
> I would be more than happy to provide any additional information.
>
>
> Your help would be highly appreciated.
>
> Cheers,
> Andrei
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Using-Standalone-ActiveMQ-with-Wildfly-tp4701969.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>