Gareth,

I don't see an attachment.

On 14 September 2011 15:16, Gareth <[email protected]> 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]
> <[email protected]> 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

Reply via email to