You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by matteor <ma...@abodata.com> on 2013/02/28 14:14:03 UTC
Producer gets stuck on a particular PC
I have a broker confugured with the following transport connector:
and a producer that sends a text message.
The program runs perfectly ok on several machines with the producer deployed
on remote servers with respect broker and consumers.
The problem is that if I deploy the broker on a particular PC (a dell
windows 7 laptop) and I deploy the producer on any other machine I got a
very strange behavior: the producer gets stuck in the highlighted line
below:
in org.apache.actviemq.transport.FutureResponse. And this happens just with
the broker deployed on that particular laptop. From wireshark I saw that the
text message never left the producer machine.
Could you please suggest me any possible explanation of this behavior?
I'm working with Activemq 5.6.0
Thank you
matteo
--
View this message in context: http://activemq.2283324.n4.nabble.com/Producer-gets-stuck-on-a-particular-PC-tp4664252.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Producer gets stuck on a particular PC
Posted by matteor <ma...@abodata.com>.
Ok, finally I managed to get the producer working. I guess the issue has been
triggered by the following operations:
- Until yesterday, I run the producer with a default connection id generated
by the connection factory;
- Now I set the connection id of the producer through the
- After the implementation change above, I forgot to delete the
activemq-data folder
As soon as I delete the activemq-data folder, everything start working
again: no message disappeared.
I don't know if this is a bug or a natural behavior of the broker...
Thanks
--
View this message in context: http://activemq.2283324.n4.nabble.com/Producer-gets-stuck-on-a-particular-PC-tp4664252p4664285.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Producer gets stuck on a particular PC
Posted by matteor <ma...@abodata.com>.
Well, during the sending of the text frame, before start waiting at the
responseSlot.take() line as mentioned in my first post, the client invoke
the
in org.apache.activemq.transport.tcp.TcpTransport successfully (the flush
complete without exceptions).
So it seems that message actually leaves the AMQ stack.
On the other hand, as I mentioned in my previous post, I cannot see it in
wireshark.
Besides, if I run both the producer and the broker on the same laptop I get
the same behavior (message never arrives at the broker), so I guess it is
not a problem originated by the LAN.
So apparently it could be a problem of the laptop network configuration; the
question is: has anyone ever experienced a problem like this? Do you have
any suggestion to get a little more insight on this issue.
I could simply classify this behavior as an oddity, but I prefer
understanding why this situation can happen...
Thank you!
--
View this message in context: http://activemq.2283324.n4.nabble.com/Producer-gets-stuck-on-a-particular-PC-tp4664252p4664283.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Producer gets stuck on a particular PC
Posted by Christian Posta <ch...@gmail.com>.
If the message never left the producer machine, (network issue?) then that
explains why the producer thread is stuck there... it's waiting for a reply
for a message it thinks was sent, but it never was. Not sure why the
message never sent?
On Thu, Feb 28, 2013 at 6:14 AM, matteor <ma...@abodata.com> wrote:
>
> I have a broker confugured with the following transport connector:
>
>
> and a producer that sends a text message.
>
> The program runs perfectly ok on several machines with the producer
> deployed
> on remote servers with respect broker and consumers.
>
> The problem is that if I deploy the broker on a particular PC (a dell
> windows 7 laptop) and I deploy the producer on any other machine I got a
> very strange behavior: the producer gets stuck in the highlighted line
> below:
>
> in org.apache.actviemq.transport.FutureResponse. And this happens just with
> the broker deployed on that particular laptop. From wireshark I saw that
> the
> text message never left the producer machine.
>
> Could you please suggest me any possible explanation of this behavior?
>
> I'm working with Activemq 5.6.0
>
> Thank you
> matteo
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Producer-gets-stuck-on-a-particular-PC-tp4664252.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta