You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Geoffry Roberts <ge...@gmail.com> on 2011/09/14 01:08:19 UTC
ActiveMq Listening on tcp6
All,
I have having some troubles getting an ActiveMQ consumer to connect to
a remote ActiveMQ broker. then I took a look at netstat and noticed
that ActiveMQ (i.e. 127.0.0.1:61616) is on tcp6. This is apparently a
default because I can't recall doing any such configuration myself.
Is there a way to get ActiveMQ onto ipv4?
Thanks
--
Geoffry Roberts
Re: ActiveMq Listening on tcp6
Posted by Geoffry Roberts <ge...@gmail.com>.
Gareth,
I deployed the file you sent after first making the appropriate
changes to the ip addresses. Now on my consumer side, I at least see
it trying to connect, but the connection is refused.
Is there any security involved here?
On 14 September 2011 15:41, Geoffry Roberts <ge...@gmail.com> wrote:
> I went over to nabble and got it.
>
> Thanks
>
> On 14 September 2011 15:39, Geoffry Roberts <ge...@gmail.com> wrote:
>> I'm on gmail.
>>
>>
>> On 14 September 2011 15:31, Gareth <ga...@gmail.com> wrote:
>>> Geoffry,
>>>
>>> Are you checking this from your email or from nabble? I can see the
>>> attachment in nabble:
>>>
>>> http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tc3334296.html
>>>
>>> Just select my last message and you should see the attachment (at the
>>> bottom).
>>>
>>> regards,
>>> Gareth
>>>
>>> --
>>> View this message in context: http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337375.html
>>> Sent from the Karaf - User mailing list archive at Nabble.com.
>>>
>>
>>
>>
>> --
>> Geoffry Roberts
>>
>
>
>
> --
> Geoffry Roberts
>
--
Geoffry Roberts
Re: ActiveMq Listening on tcp6
Posted by Geoffry Roberts <ge...@gmail.com>.
I went over to nabble and got it.
Thanks
On 14 September 2011 15:39, Geoffry Roberts <ge...@gmail.com> wrote:
> I'm on gmail.
>
>
> On 14 September 2011 15:31, Gareth <ga...@gmail.com> wrote:
>> Geoffry,
>>
>> Are you checking this from your email or from nabble? I can see the
>> attachment in nabble:
>>
>> http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tc3334296.html
>>
>> Just select my last message and you should see the attachment (at the
>> bottom).
>>
>> regards,
>> Gareth
>>
>> --
>> View this message in context: http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337375.html
>> Sent from the Karaf - User mailing list archive at Nabble.com.
>>
>
>
>
> --
> Geoffry Roberts
>
--
Geoffry Roberts
Re: ActiveMq Listening on tcp6
Posted by Geoffry Roberts <ge...@gmail.com>.
I'm on gmail.
On 14 September 2011 15:31, Gareth <ga...@gmail.com> wrote:
> Geoffry,
>
> Are you checking this from your email or from nabble? I can see the
> attachment in nabble:
>
> http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tc3334296.html
>
> Just select my last message and you should see the attachment (at the
> bottom).
>
> regards,
> Gareth
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337375.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Geoffry Roberts
Re: ActiveMq Listening on tcp6
Posted by Gareth <ga...@gmail.com>.
Geoffry,
Are you checking this from your email or from nabble? I can see the
attachment in nabble:
http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tc3334296.html
Just select my last message and you should see the attachment (at the
bottom).
regards,
Gareth
--
View this message in context: http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337375.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: ActiveMq Listening on tcp6
Posted by Geoffry Roberts <ge...@gmail.com>.
Gareth,
I don't see an attachment.
On 14 September 2011 15:16, Gareth <ga...@gmail.com> wrote:
> Hello Geoffry,
>
> What you can put in the broker config comes from here:
>
> https://activemq.apache.org/schema/core/activemq-core-5.5.0.xsd
It's always nice to have the schema.
>
> To cut to the chase, I am attaching a broker blueprint file of mine
> which I know works. It is largely the default except for the
> additional transport connector and a network connector.
>
> Just remove the network connector (as you are not setting up a broker
> network yet) and change the IP address in the transport connector to
> reflect your producer IP and deploy to karaf. I am assuming the karaf
> instance which you will deploy to will have at least the activemq and
> activemq-blueprint features installed.
The above are indeed installed. I can queue messages that's not the
problem. I simply cannot get my consumer to connect.
I disabled ipv6, and ActiveMQ now listens on ipv4.
>
> Let me know if this works for you.
>
> regards,
> Gareth
>
>
>
>
>
>
>
> On Wed, Sep 14, 2011 at 4:38 PM, gcr [via Karaf]
> <ml...@n3.nabble.com> wrote:
>> Gareth,
>>
>> This is what I get from netstat -anp --tcp:
>>
>> tcp6 0 0 127.0.0.1:61616 :::*
>> LISTEN -
>>
>> It's that tcp6 business that concerns me.
>>
>> See below:
>>
>> On 14 September 2011 13:12, Gareth <[hidden email]> wrote:
>>>
>>> Hello Geoffry,
>>>
>>> On the machine with your broker, do you see the following in netstat?:
>>>
>>> tcp 0 0 ::ffff:<server_ip>:61616 :::*
>>> LISTEN
>>> tcp 0 0 ::ffff:127.0.0.1:61616 :::*
>>> LISTEN
>>>
>>> If yes, from the consumer machine, can you now run:
>>>
>>> telnet <server_ip> 61616
>>
>> I'll have to install telnet first.
>>>
>>> and connect (to confirm the port is really accessible)? If yes, this is
>>> now
>>> an issue on your consumer.
>>>
>>> I am not understanding one thing though. How were you configuring your
>>> broker originally? I was expecting you to update an existing broker
>>> configuration file (whether it be outside OSGi, or defined inside OSGi as
>>> a
>>> spring-dm/blueprint file)...rather than creating a new one.
>>
>> I had a file called localhost-broker.xml that I created from the karaf
>> client command line. (I don't recall the exact command I ran.) It contained
>> a transport connector element similar to what you have prescribed. As I
>> thrashed around, trying to get this thing to work, I removed it because none
>> of the sketchy documentation I was referencing seemed to include it.
>>>
>>> regards,
>>> Gareth
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337007.html
>>> Sent from the Karaf - User mailing list archive at Nabble.com.
>>
>>
>>
>> --
>> Geoffry Roberts
>>
>>
>>
>> ________________________________
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337079.html
>> To unsubscribe from ActiveMq Listening on tcp6, click here.
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337343.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Geoffry Roberts
Re: ActiveMq Listening on tcp6
Posted by Gareth <ga...@gmail.com>.
Hello Geoffry,
What you can put in the broker config comes from here:
https://activemq.apache.org/schema/core/activemq-core-5.5.0.xsd
To cut to the chase, I am attaching a broker blueprint file of mine
which I know works. It is largely the default except for the
additional transport connector and a network connector.
Just remove the network connector (as you are not setting up a broker
network yet) and change the IP address in the transport connector to
reflect your producer IP and deploy to karaf. I am assuming the karaf
instance which you will deploy to will have at least the activemq and
activemq-blueprint features installed.
Let me know if this works for you.
regards,
Gareth
On Wed, Sep 14, 2011 at 4:38 PM, gcr [via Karaf]
<ml...@n3.nabble.com> wrote:
> Gareth,
>
> This is what I get from netstat -anp --tcp:
>
> tcp6 0 0 127.0.0.1:61616 :::*
> LISTEN -
>
> It's that tcp6 business that concerns me.
>
> See below:
>
> On 14 September 2011 13:12, Gareth <[hidden email]> wrote:
>>
>> Hello Geoffry,
>>
>> On the machine with your broker, do you see the following in netstat?:
>>
>> tcp 0 0 ::ffff:<server_ip>:61616 :::*
>> LISTEN
>> tcp 0 0 ::ffff:127.0.0.1:61616 :::*
>> LISTEN
>>
>> If yes, from the consumer machine, can you now run:
>>
>> telnet <server_ip> 61616
>
> I'll have to install telnet first.
>>
>> and connect (to confirm the port is really accessible)? If yes, this is
>> now
>> an issue on your consumer.
>>
>> I am not understanding one thing though. How were you configuring your
>> broker originally? I was expecting you to update an existing broker
>> configuration file (whether it be outside OSGi, or defined inside OSGi as
>> a
>> spring-dm/blueprint file)...rather than creating a new one.
>
> I had a file called localhost-broker.xml that I created from the karaf
> client command line. (I don't recall the exact command I ran.) It contained
> a transport connector element similar to what you have prescribed. As I
> thrashed around, trying to get this thing to work, I removed it because none
> of the sketchy documentation I was referencing seemed to include it.
>>
>> regards,
>> Gareth
>>
>>
>>
>> --
>> View this message in context:
>> http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337007.html
>> Sent from the Karaf - User mailing list archive at Nabble.com.
>
>
>
> --
> Geoffry Roberts
>
>
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337079.html
> To unsubscribe from ActiveMq Listening on tcp6, click here.
--
View this message in context: http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337343.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: ActiveMq Listening on tcp6
Posted by Geoffry Roberts <ge...@gmail.com>.
On 14 September 2011 14:30, Johan Edstrom <se...@gmail.com> wrote:
> You probably have your hosts file kinda fuubared.
>
Not so.
>
> You can try supplying : -Djava.net.preferIPv4Stack=true
>
> Or completely disabling ipv6,
>
I'll try this.
>
> or listening to 0.0.0.0
>
Tried this, no go.
Thanks all.
>
>
> On Sep 14, 2011, at 2:40 PM, Geoffry Roberts wrote:
>
> > Gareth,
> >
> > Tried telnet and got the following:
> >
> > telnet: could not resolve 192.168.40.140:61616/telnet: Name or service
> not known
> >
> >
> > On 14 September 2011 13:38, Geoffry Roberts <ge...@gmail.com>
> wrote:
> > Gareth,
> >
> > This is what I get from netstat -anp --tcp:
> >
> > tcp6 0 0 127.0.0.1:61616 :::*
> LISTEN -
> >
> > It's that tcp6 business that concerns me.
> >
> > See below:
> >
> > On 14 September 2011 13:12, Gareth <ga...@gmail.com> wrote:
> > Hello Geoffry,
> >
> > On the machine with your broker, do you see the following in netstat?:
> >
> > tcp 0 0 ::ffff:<server_ip>:61616 :::*
> > LISTEN
> > tcp 0 0 ::ffff:127.0.0.1:61616 :::*
> > LISTEN
> >
> > If yes, from the consumer machine, can you now run:
> >
> > telnet <server_ip> 61616
> >
> > I'll have to install telnet first.
> >
> > and connect (to confirm the port is really accessible)? If yes, this is
> now
> > an issue on your consumer.
> >
> > I am not understanding one thing though. How were you configuring your
> > broker originally? I was expecting you to update an existing broker
> > configuration file (whether it be outside OSGi, or defined inside OSGi as
> a
> > spring-dm/blueprint file)...rather than creating a new one.
> >
> > I had a file called localhost-broker.xml that I created from the karaf
> client command line. (I don't recall the exact command I ran.) It contained
> a transport connector element similar to what you have prescribed. As I
> thrashed around, trying to get this thing to work, I removed it because none
> of the sketchy documentation I was referencing seemed to include it.
> >
> > regards,
> > Gareth
> >
> >
> >
> > --
> > View this message in context:
> http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337007.html
> > Sent from the Karaf - User mailing list archive at Nabble.com.
> >
> >
> >
> > --
> > Geoffry Roberts
> >
> >
> >
> >
> > --
> > Geoffry Roberts
> >
>
>
--
Geoffry Roberts
Re: ActiveMq Listening on tcp6
Posted by Johan Edstrom <se...@gmail.com>.
You probably have your hosts file kinda fuubared.
You can try supplying : -Djava.net.preferIPv4Stack=true
Or completely disabling ipv6,
or listening to 0.0.0.0
On Sep 14, 2011, at 2:40 PM, Geoffry Roberts wrote:
> Gareth,
>
> Tried telnet and got the following:
>
> telnet: could not resolve 192.168.40.140:61616/telnet: Name or service not known
>
>
> On 14 September 2011 13:38, Geoffry Roberts <ge...@gmail.com> wrote:
> Gareth,
>
> This is what I get from netstat -anp --tcp:
>
> tcp6 0 0 127.0.0.1:61616 :::* LISTEN -
>
> It's that tcp6 business that concerns me.
>
> See below:
>
> On 14 September 2011 13:12, Gareth <ga...@gmail.com> wrote:
> Hello Geoffry,
>
> On the machine with your broker, do you see the following in netstat?:
>
> tcp 0 0 ::ffff:<server_ip>:61616 :::*
> LISTEN
> tcp 0 0 ::ffff:127.0.0.1:61616 :::*
> LISTEN
>
> If yes, from the consumer machine, can you now run:
>
> telnet <server_ip> 61616
>
> I'll have to install telnet first.
>
> and connect (to confirm the port is really accessible)? If yes, this is now
> an issue on your consumer.
>
> I am not understanding one thing though. How were you configuring your
> broker originally? I was expecting you to update an existing broker
> configuration file (whether it be outside OSGi, or defined inside OSGi as a
> spring-dm/blueprint file)...rather than creating a new one.
>
> I had a file called localhost-broker.xml that I created from the karaf client command line. (I don't recall the exact command I ran.) It contained a transport connector element similar to what you have prescribed. As I thrashed around, trying to get this thing to work, I removed it because none of the sketchy documentation I was referencing seemed to include it.
>
> regards,
> Gareth
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337007.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
>
>
> --
> Geoffry Roberts
>
>
>
>
> --
> Geoffry Roberts
>
Re: ActiveMq Listening on tcp6
Posted by Geoffry Roberts <ge...@gmail.com>.
Gareth,
Tried telnet and got the following:
telnet: could not resolve 192.168.40.140:61616/telnet: Name or service not
known
On 14 September 2011 13:38, Geoffry Roberts <ge...@gmail.com>wrote:
> Gareth,
>
> This is what I get from netstat -anp --tcp:
>
> tcp6 0 0 127.0.0.1:61616 :::*
> LISTEN -
>
> It's that tcp6 business that concerns me.
>
> See below:
>
> On 14 September 2011 13:12, Gareth <ga...@gmail.com> wrote:
>
>> Hello Geoffry,
>>
>> On the machine with your broker, do you see the following in netstat?:
>>
>> tcp 0 0 ::ffff:<server_ip>:61616 :::*
>> LISTEN
>> tcp 0 0 ::ffff:127.0.0.1:61616 :::*
>> LISTEN
>>
>> If yes, from the consumer machine, can you now run:
>>
>> telnet <server_ip> 61616
>>
>
> I'll have to install telnet first.
>
>>
>> and connect (to confirm the port is really accessible)? If yes, this is
>> now
>> an issue on your consumer.
>>
>> I am not understanding one thing though. How were you configuring your
>> broker originally? I was expecting you to update an existing broker
>> configuration file (whether it be outside OSGi, or defined inside OSGi as
>> a
>> spring-dm/blueprint file)...rather than creating a new one.
>>
>
> I had a file called localhost-broker.xml that I created from the karaf
> client command line. (I don't recall the exact command I ran.) It contained
> a transport connector element similar to what you have prescribed. As I
> thrashed around, trying to get this thing to work, I removed it because none
> of the sketchy documentation I was referencing seemed to include it.
>
>>
>> regards,
>> Gareth
>>
>>
>>
>> --
>> View this message in context:
>> http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337007.html
>> Sent from the Karaf - User mailing list archive at Nabble.com.
>>
>
>
>
> --
> Geoffry Roberts
>
>
--
Geoffry Roberts
Re: ActiveMq Listening on tcp6
Posted by Geoffry Roberts <ge...@gmail.com>.
Gareth,
This is what I get from netstat -anp --tcp:
tcp6 0 0 127.0.0.1:61616 :::*
LISTEN -
It's that tcp6 business that concerns me.
See below:
On 14 September 2011 13:12, Gareth <ga...@gmail.com> wrote:
> Hello Geoffry,
>
> On the machine with your broker, do you see the following in netstat?:
>
> tcp 0 0 ::ffff:<server_ip>:61616 :::*
> LISTEN
> tcp 0 0 ::ffff:127.0.0.1:61616 :::*
> LISTEN
>
> If yes, from the consumer machine, can you now run:
>
> telnet <server_ip> 61616
>
I'll have to install telnet first.
>
> and connect (to confirm the port is really accessible)? If yes, this is now
> an issue on your consumer.
>
> I am not understanding one thing though. How were you configuring your
> broker originally? I was expecting you to update an existing broker
> configuration file (whether it be outside OSGi, or defined inside OSGi as a
> spring-dm/blueprint file)...rather than creating a new one.
>
I had a file called localhost-broker.xml that I created from the karaf
client command line. (I don't recall the exact command I ran.) It contained
a transport connector element similar to what you have prescribed. As I
thrashed around, trying to get this thing to work, I removed it because none
of the sketchy documentation I was referencing seemed to include it.
>
> regards,
> Gareth
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337007.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Geoffry Roberts
Re: ActiveMq Listening on tcp6
Posted by Gareth <ga...@gmail.com>.
Hello Geoffry,
On the machine with your broker, do you see the following in netstat?:
tcp 0 0 ::ffff:<server_ip>:61616 :::*
LISTEN
tcp 0 0 ::ffff:127.0.0.1:61616 :::*
LISTEN
If yes, from the consumer machine, can you now run:
telnet <server_ip> 61616
and connect (to confirm the port is really accessible)? If yes, this is now
an issue on your consumer.
I am not understanding one thing though. How were you configuring your
broker originally? I was expecting you to update an existing broker
configuration file (whether it be outside OSGi, or defined inside OSGi as a
spring-dm/blueprint file)...rather than creating a new one.
regards,
Gareth
--
View this message in context: http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3337007.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: ActiveMq Listening on tcp6
Posted by Geoffry Roberts <ge...@gmail.com>.
Gareth,
I solved my problem using this broker tag. I still can't get my consumer to
work but at least the error went away.
<broker xmlns="http://activemq.apache.org/schema/core"
brokerName="jms">
<transportConnector...
</broker>
On 14 September 2011 10:38, Geoffry Roberts <ge...@gmail.com>wrote:
> Gareth,
>
> I deployed the following on to the Karaf instance where the ActiveMW
> broker is running. The log file says "Unable to start
> blueprint container for bundle brok
> er.xml" then it says,
> "org.osgi.service.blueprint.container.ComponentDefinitionException:
> Unable to validate xml"
>
> Am I missing something?
>
> Thanks
>
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0">
> <transportConnectors>
> <transportConnector name="openwire"
> uri="tcp://localhost:61616" />
> <transportConnector name="openwire remote" uri="tcp://
> 192.168.40.140:61616" />
> </transportConnectors>
> </blueprint>
>
> On 14 September 2011 10:08, Gareth <ga...@gmail.com> wrote:
> > Geoffry,
> >
> > The transport connectors configuration update is for your broker. Not for
> > the broker clients (producer and consumer).
> >
> > regards,
> > Gareth
> >
> > --
> > View this message in context:
> http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3336476.html
> > Sent from the Karaf - User mailing list archive at Nabble.com.
> >
>
>
>
> --
> Geoffry Roberts
>
--
Geoffry Roberts
Re: ActiveMq Listening on tcp6
Posted by Geoffry Roberts <ge...@gmail.com>.
Gareth,
I deployed the following on to the Karaf instance where the ActiveMW
broker is running. The log file says "Unable to start
blueprint container for bundle brok
er.xml" then it says,
"org.osgi.service.blueprint.container.ComponentDefinitionException:
Unable to validate xml"
Am I missing something?
Thanks
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0">
<transportConnectors>
<transportConnector name="openwire" uri="tcp://localhost:61616" />
<transportConnector name="openwire remote" uri="tcp://192.168.40.140:61616" />
</transportConnectors>
</blueprint>
On 14 September 2011 10:08, Gareth <ga...@gmail.com> wrote:
> Geoffry,
>
> The transport connectors configuration update is for your broker. Not for
> the broker clients (producer and consumer).
>
> regards,
> Gareth
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3336476.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Geoffry Roberts
Re: ActiveMq Listening on tcp6
Posted by Gareth <ga...@gmail.com>.
Geoffry,
The transport connectors configuration update is for your broker. Not for
the broker clients (producer and consumer).
regards,
Gareth
--
View this message in context: http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3336476.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: ActiveMq Listening on tcp6
Posted by Geoffry Roberts <ge...@gmail.com>.
Gareth,
Thanks for the input. I tried your suggestion but still all is not well.
Perhaps I got something wrong. Would you take a look and offer any correction?
I am trying to move message in one direction from a producer to a
consumer. I have identical Karaf installations at both ends.
Thanks
Producer Blueprint:
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0">
<transportConnectors>
<transportConnector name="openwire" uri="tcp://localhost:61616" />
<transportConnector name="openwire remote" uri="tcp://producer_ip:61616" />
</transportConnectors>
<bean id="jms" class="org.apache.activemq.camel.component.ActiveMQComponent">
<property name="brokerURL" value="tcp://localhost:61616" />
</bean>
<camelContext xmlns="http://camel.apache.org/schema/blueprint">
<route>
<from uri="timer:test?period=5000" />
<setBody>
<constant>Ave Mundus!!</constant>
</setBody>
<to uri="jms:queue:ave" />
<to uri="stream:out" />
</route>
</camelContext>
</blueprint>
***********************************
Consumer Blueprint:
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0">
<transportConnectors>
<transportConnector name="openwire remote" uri="tcp://producer_ip:61616" />
</transportConnectors>
<bean id="jms" class="org.apache.activemq.camel.component.ActiveMQComponent">
<property name="brokerURL" value="tcp://producer_ip:61616" />
</bean>
<camelContext xmlns="http://camel.apache.org/schema/blueprint">
<route autoStartup="true">
<from uri="jms:queue:ave" />
<to uri="stream:out" />
</route>
</camelContext>
</blueprint>
On 13 September 2011 22:25, Gareth <ga...@gmail.com> wrote:
> Geoffry,
>
> Do this in your activemq blueprint config (or equivalent):
>
> <transportConnectors>
> <transportConnector name="openwire"
> uri="tcp://localhost:61616"/>
> >>> add this line >>> <transportConnector name="openwire
> remote" uri="tcp://<server ip>:61616"/>
> </transportConnectors>
>
> I believe the "tcp://localhost:61616" means it will only listen for local
> connections. You need to explicitly tell it to listen to 61616 on each
> interface IP address (I found this out a few days ago myself :)).
>
> regards,
> Gareth
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3334941.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Geoffry Roberts
Re: ActiveMq Listening on tcp6
Posted by Gareth <ga...@gmail.com>.
Geoffry,
Do this in your activemq blueprint config (or equivalent):
<transportConnectors>
<transportConnector name="openwire"
uri="tcp://localhost:61616"/>
>>> add this line >>> <transportConnector name="openwire
remote" uri="tcp://<server ip>:61616"/>
</transportConnectors>
I believe the "tcp://localhost:61616" means it will only listen for local
connections. You need to explicitly tell it to listen to 61616 on each
interface IP address (I found this out a few days ago myself :)).
regards,
Gareth
--
View this message in context: http://karaf.922171.n3.nabble.com/ActiveMq-Listening-on-tcp6-tp3334296p3334941.html
Sent from the Karaf - User mailing list archive at Nabble.com.