ok - thanks for the feedback!
On 19 Jan 2010, at 21:05, quinn wrote:
Thanks very much for the response.
After rebooting it is working again. If I can reproduce, I will post
again.
rajdavies wrote:
ok - some basic things to re-check - just in case:
1. so in the broker config only you h
Thanks very much for the response.
After rebooting it is working again. If I can reproduce, I will post again.
rajdavies wrote:
>
> ok - some basic things to re-check - just in case:
> 1. so in the broker config only you have set tcp://0.0.0.0:port
> 2. your remote client is using tcp://hostn
ok - some basic things to re-check - just in case:
1. so in the broker config only you have set tcp://0.0.0.0:port
2. your remote client is using tcp://hostname:port to connect to your
broker
3. you don't have a rouge broker on your remote client's machine that
its connected to
4. your remote
I spoke too soon.
While this solution did allow my client to connect from a remote client
without exceptions thrown, when I try to push data through, nothing happens.
Yet, when I run the server and the client on the same machine, the data
flows.
Any further ideas?
Thanks in advance.
quinn wr
That fixed the problem.
Thanks very much!
How would I have figured that out? I don't recall seeing 0.0.0.0 in any of
the examples.
Cheers.
TQ
rajdavies wrote:
>
> instead of defining tcp://localhost:port in your broker config - try
> tcp://0.0.0.0:port
> On 15 Jan 2010, at 22:43, quinn w
instead of defining tcp://localhost:port in your broker config - try
tcp://0.0.0.0:port
On 15 Jan 2010, at 22:43, quinn wrote:
I am using ActiveMQ 5.3 and JDK 1.6.
I have a XP box and an Ubuntu box. On either machine I can start an
embedded
broker and the vm and tcp transports work well o
I am using ActiveMQ 5.3 and JDK 1.6.
I have a XP box and an Ubuntu box. On either machine I can start an embedded
broker and the vm and tcp transports work well on one machine. When I try to
access the tcp transport from a remote machine I am unable to connect.
The stack trace is attached.
http:
