You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by CallMeXYZ <am...@gmail.com> on 2016/11/01 01:45:30 UTC
Re: scheduler message deliver immediately
Yes,the web console runs and show no activity. I thought it was because my
broker takes the port of '616167' and the web console listens '61616'.
Right?Sure that only one broker.the broker and web console cannot have the
same port
--
View this message in context: http://activemq.2283324.n4.nabble.com/scheduler-message-deliver-immediately-tp4718568p4718714.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: scheduler message deliver immediately
Posted by CallMeXYZ <am...@gmail.com>.
ActiveMQ has installed as a service. Restart my PC,and do nothing.And check
the port using n/netstat -ano|findstr "61616"/.I got
/ TCP 0.0.0.0:61616 0.0.0.0:0 LISTENING 1820
TCP [::]:61616 [::]:0 LISTENING 1820/
And if the process was killed through /taskkill /pid portNumber /F/
manually, it will restart in another pid quickly.
PS:I'm programming using IDEA with tomcat as a server.Sure that the tomcat
was not running when checking the port.
--
View this message in context: http://activemq.2283324.n4.nabble.com/scheduler-message-deliver-immediately-tp4718568p4718848.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: scheduler message deliver immediately
Posted by Tim Bain <tb...@alumni.duke.edu>.
That error means either 1) an ActiveMQ broker is already running on that
host, or 2) your configuration somehow causes you to start two brokers.
The web console you're connecting to is the one for that other broker,
which is why you see no activity.
When your broker is stopped and you issue a netstat -a | grep 61616, what
response do you get?
On Nov 1, 2016 8:02 PM, "CallMeXYZ" <am...@gmail.com> wrote:
> I do understand the web console take the localhost:8161.But I always get
> 'java.net.BindException: Address already in use: JVM_Bind exception. ' if
> my
> broker url is 61616.
> Either I change my broker url to 61617 or change the activemq.xml
> configuration /<transportConnector name="openwire"
> uri="tcp://0.0.0.0:61616?maximumConnections=1000&
> wireFormat.maxFrameSize=104857600"/>/
> to /tcp://0.0.0.0:61616/,then the exception disappears and ActiveMQ works
> while just the web console cannot get my broker infos.(That's why I assume
> that web console may take the 61616 port of broker)
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/scheduler-message-deliver-immediately-tp4718568p4718785.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Re: scheduler message deliver immediately
Posted by CallMeXYZ <am...@gmail.com>.
I do understand the web console take the localhost:8161.But I always get
'java.net.BindException: Address already in use: JVM_Bind exception. ' if my
broker url is 61616.
Either I change my broker url to 61617 or change the activemq.xml
configuration /<transportConnector name="openwire"
uri="tcp://0.0.0.0:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>/
to /tcp://0.0.0.0:61616/,then the exception disappears and ActiveMQ works
while just the web console cannot get my broker infos.(That's why I assume
that web console may take the 61616 port of broker)
--
View this message in context: http://activemq.2283324.n4.nabble.com/scheduler-message-deliver-immediately-tp4718568p4718785.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: scheduler message deliver immediately
Posted by Tim Bain <tb...@alumni.duke.edu>.
The web console is typically configured to use port 8161 (see
http://activemq.apache.org/web-console.html) unless you've changed it. Are
you saying you access the web console on 61616?
When you shut down your broker, can you access the web console?
You may want to post your configuration.
On Oct 31, 2016 8:02 PM, "CallMeXYZ" <am...@gmail.com> wrote:
> Yes,the web console runs and show no activity. I thought it was because my
> broker takes the port of '616167' and the web console listens '61616'.
> Right?Sure that only one broker.the broker and web console cannot have the
> same port
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/scheduler-message-deliver-immediately-tp4718568p4718714.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>