14, 2016 2:10 AM
To: ActiveMQ Users
Subject: Re: Problem With Remote Debug OF Message Broker
Mike,
You referenced a screenshot that showed behavior that wasn't standard for
debugging, but it wasn't attached. Could you share that again? I've
assumed in the rest of this response that
ember 14, 2016 2:10 AM
To: ActiveMQ Users
Subject: Re: Problem With Remote Debug OF Message Broker
Mike,
You referenced a screenshot that showed behavior that wasn't standard for
debugging, but it wasn't attached. Could you share that again? I've assumed
in the rest of th
ichael Tarullo
> Contractor (Engility Corp)
> Software Engineer
> FAA WJH Technical Center
> (609)485-5294
>
>
> -Original Message-----
> From: tbai...@gmail.com [mailto:tbai...@gmail.com] On Behalf Of Tim Bain
> Sent: Tuesday, September 13, 2016 11:31 AM
> To: Act
er 13, 2016 11:31 AM
To: ActiveMQ Users
Subject: Re: Problem With Remote Debug OF Message Broker
I would expect start() to be called when the broker starts (hence the name) not
when a client connects. If you really want to debug that method, there is an
option you can set on the debug port
I would expect start() to be called when the broker starts (hence the name)
not when a client connects. If you really want to debug that method, there
is an option you can set on the debug port that prevents the application
from running until a debugger attaches. You can find nore details via
Goo
