And what happens when you take Claus's suggestion and run "activemq start"
from the bin directory instead of invoking java directly?
Calling java yourself isn't recommended for someone just getting started
with ActiveMQ. In fact, it's not recommended for anyone at all unless they
have a concrete
yes when i push the button start, it no longer running...
and the ports are not open too..
Atually i had experience to running this ActivemQ at 32bit Window computer
before.
but when i tryied in 64bit window and linux it just stopped in that moment.
i can't type anything
after stop this moment.
It is valid.
But it's then, up to you, to manually pass all the environment
variables, which, at the end, is what the script does for you,
together with other helper functionalities.
On Mon, Nov 28, 2016 at 4:24 AM, Tim Bain wrote:
> The script is definitely the most common way to start a broke
The script is definitely the most common way to start a broker, but if the
other way is no longer valid, we would need to update
https://activemq.apache.org/activemq-command-line-tools-reference.html to
reflect that. But I'm not aware of a reason why it shouldn't be possible
to direct invoke Java
Hi
You start ActiveMQ using the scripts in the bin directory, not using java -jar.
See here how to start/stop ActiveMQ
http://activemq.apache.org/getting-started.html#GettingStarted-StartingActiveMQStartingActiveMQ
On Sun, Nov 27, 2016 at 11:09 AM, jang wrote:
> Hello im a new user of this Acti
First, the log line you quoted is an INFO line, not a WARN or an ERROR;
it's probably not a problem.
Second, what are the symptoms of the problem? Is the process no longer
running (via ps)? The logs show that it's listening for data on ports
61616, 5672, 61613, 1883, and 61614 and for web consol
