You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by foucault <ar...@status.net> on 2010/03/30 20:02:06 UTC
updating from 5.3.0 -> 5.3.1 now the admin console's not working
First thing, activemq and its admin panel work fine out of the box (default
config), also both work fine in my dev environment with our re-based config.
production has load blancing, as pretty much the only diffrence, and that is
where the admin panel is not working.
logs showing everything working... --> http://privatepaste.com/8930199c58
heres our activemq.xml --> http://privatepaste.com/c6bc1f5379
from a vanilla untarring the only files we've changed are activeme.xml and
/bin/activemq (upped memory)
so in short, as of updating to 5.3.1 the admin console never shows up,
netstat doesn't show anything running on port 8161, although the logs tell
me it has been launched. anyone else encounter this problem?
--
View this message in context: http://old.nabble.com/updating-from-5.3.0--%3E-5.3.1-now-the-admin-console%27s-not-working-tp28086227p28086227.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: updating from 5.3.0 -> 5.3.1 now the admin console's not
working
Posted by foucault <ar...@status.net>.
Dejan Bosanac wrote:
>
> Hi,
>
> You ran into a Camel web app problem introduced in 5.3.1. I just
> documented
> a workaround for it, you can find it at a top of
> http://cwiki.apache.org/confluence/display/ACTIVEMQ/Web+Console
>
> The fix already in trunk and will be available in the 5.4.0 release.
>
> Cheers
> --
> Dejan Bosanac - http://twitter.com/dejanb
>
> Open Source Integration - http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
>
>
Thanks Dejan, Status.net loves activemq and gives their thanks.
-Aric
--
View this message in context: http://old.nabble.com/updating-from-5.3.0--%3E-5.3.1-now-the-admin-console%27s-not-working-tp28086227p28095696.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: updating from 5.3.0 -> 5.3.1 now the admin console's not working
Posted by Dejan Bosanac <de...@nighttale.net>.
Hi,
You ran into a Camel web app problem introduced in 5.3.1. I just documented
a workaround for it, you can find it at a top of
http://cwiki.apache.org/confluence/display/ACTIVEMQ/Web+Console
The fix already in trunk and will be available in the 5.4.0 release.
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Wed, Mar 31, 2010 at 2:05 AM, Bruce Snyder <br...@gmail.com>wrote:
> On Tue, Mar 30, 2010 at 11:17 PM, Bruce Snyder <br...@gmail.com>
> wrote:
> > On Tue, Mar 30, 2010 at 10:52 PM, foucault <ar...@status.net> wrote:
> >>
> >>
> >>> so in short, as of updating to 5.3.1 the admin console never shows up,
> >>> netstat doesn't show anything running on port 8161, although the logs
> tell
> >>> me it has been launched. anyone else encounter this problem?
> >>
> >> I just double-checked this with the 5.3.1 binary tarball from the
> >> release and the admin console is working just fine. If you download a
> >> fresh binary, expand it and run it without modifying the activemq.xml,
> >> does the admin console work for you?
> > ...
> >
> >> Indeed, it works as expected.
> >> fiddling around between the base config and my own I think I have
> narrowed
> >> it down.
> >>
> >> this works in 5.3.0
> >> <transportConnector name="stomp" uri="stomp://10.1.200.30:61613"/>
> >> but in 5.3.1 it only works like this
> >> <transportConnector name="stomp" uri="stomp://0.0.0.0:61613"/>
> >> If i start it in 5.3.1 with the proper bind address (10.1.200.30),
> Something
> >> gets stuck. I can only kill the java process with kill -9, but... the
> >> program works, just without the admin interface.
> >>
> >> we are currently using 5.3.0 without issue.
> >
> > You are correct, this seems to be a bug in 5.3.1. When I enable debug
> > level logging, I see the following statement over and over:
> >
> > DEBUG | Connect fail to: tcp://localhost:61616, reason:
> > java.net.ConnectException: Connection refused
> >
> > Notice the use of localhost.
> >
> > What does your /etc/hosts file look like?
>
> Nevermind looking at your /etc/hosts file, it's got nothing to do with
> that.
>
> The problem is in the Camel web app that is loaded in the
> conf/jetty.xml file. Just comment it out and the ActiveMQ admin
> console will start up correctly.
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> ActiveMQ in Action: http://bit.ly/2je6cQ
> Blog: http://bruceblog.org/
> Twitter: http://twitter.com/brucesnyder
>
Re: updating from 5.3.0 -> 5.3.1 now the admin console's not working
Posted by Bruce Snyder <br...@gmail.com>.
On Tue, Mar 30, 2010 at 11:17 PM, Bruce Snyder <br...@gmail.com> wrote:
> On Tue, Mar 30, 2010 at 10:52 PM, foucault <ar...@status.net> wrote:
>>
>>
>>> so in short, as of updating to 5.3.1 the admin console never shows up,
>>> netstat doesn't show anything running on port 8161, although the logs tell
>>> me it has been launched. anyone else encounter this problem?
>>
>> I just double-checked this with the 5.3.1 binary tarball from the
>> release and the admin console is working just fine. If you download a
>> fresh binary, expand it and run it without modifying the activemq.xml,
>> does the admin console work for you?
> ...
>
>> Indeed, it works as expected.
>> fiddling around between the base config and my own I think I have narrowed
>> it down.
>>
>> this works in 5.3.0
>> <transportConnector name="stomp" uri="stomp://10.1.200.30:61613"/>
>> but in 5.3.1 it only works like this
>> <transportConnector name="stomp" uri="stomp://0.0.0.0:61613"/>
>> If i start it in 5.3.1 with the proper bind address (10.1.200.30), Something
>> gets stuck. I can only kill the java process with kill -9, but... the
>> program works, just without the admin interface.
>>
>> we are currently using 5.3.0 without issue.
>
> You are correct, this seems to be a bug in 5.3.1. When I enable debug
> level logging, I see the following statement over and over:
>
> DEBUG | Connect fail to: tcp://localhost:61616, reason:
> java.net.ConnectException: Connection refused
>
> Notice the use of localhost.
>
> What does your /etc/hosts file look like?
Nevermind looking at your /etc/hosts file, it's got nothing to do with that.
The problem is in the Camel web app that is loaded in the
conf/jetty.xml file. Just comment it out and the ActiveMQ admin
console will start up correctly.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
Re: updating from 5.3.0 -> 5.3.1 now the admin console's not working
Posted by Bruce Snyder <br...@gmail.com>.
On Tue, Mar 30, 2010 at 10:52 PM, foucault <ar...@status.net> wrote:
>
>
>> so in short, as of updating to 5.3.1 the admin console never shows up,
>> netstat doesn't show anything running on port 8161, although the logs tell
>> me it has been launched. anyone else encounter this problem?
>
> I just double-checked this with the 5.3.1 binary tarball from the
> release and the admin console is working just fine. If you download a
> fresh binary, expand it and run it without modifying the activemq.xml,
> does the admin console work for you?
...
> Indeed, it works as expected.
> fiddling around between the base config and my own I think I have narrowed
> it down.
>
> this works in 5.3.0
> <transportConnector name="stomp" uri="stomp://10.1.200.30:61613"/>
> but in 5.3.1 it only works like this
> <transportConnector name="stomp" uri="stomp://0.0.0.0:61613"/>
> If i start it in 5.3.1 with the proper bind address (10.1.200.30), Something
> gets stuck. I can only kill the java process with kill -9, but... the
> program works, just without the admin interface.
>
> we are currently using 5.3.0 without issue.
You are correct, this seems to be a bug in 5.3.1. When I enable debug
level logging, I see the following statement over and over:
DEBUG | Connect fail to: tcp://localhost:61616, reason:
java.net.ConnectException: Connection refused
Notice the use of localhost.
What does your /etc/hosts file look like?
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
Re: updating from 5.3.0 -> 5.3.1 now the admin console's not
working
Posted by foucault <ar...@status.net>.
> so in short, as of updating to 5.3.1 the admin console never shows up,
> netstat doesn't show anything running on port 8161, although the logs tell
> me it has been launched. anyone else encounter this problem?
I just double-checked this with the 5.3.1 binary tarball from the
release and the admin console is working just fine. If you download a
fresh binary, expand it and run it without modifying the activemq.xml,
does the admin console work for you?
Bruce
--
perl -e 'print
unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
Indeed, it works as expected.
fiddling around between the base config and my own I think I have narrowed
it down.
this works in 5.3.0
<transportConnector name="stomp" uri="stomp://10.1.200.30:61613"/>
but in 5.3.1 it only works like this
<transportConnector name="stomp" uri="stomp://0.0.0.0:61613"/>
If i start it in 5.3.1 with the proper bind address (10.1.200.30), Something
gets stuck. I can only kill the java process with kill -9, but... the
program works, just without the admin interface.
we are currently using 5.3.0 without issue.
--
View this message in context: http://old.nabble.com/updating-from-5.3.0--%3E-5.3.1-now-the-admin-console%27s-not-working-tp28086227p28089549.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: updating from 5.3.0 -> 5.3.1 now the admin console's not working
Posted by Bruce Snyder <br...@gmail.com>.
On Tue, Mar 30, 2010 at 6:02 PM, foucault <ar...@status.net> wrote:
>
> First thing, activemq and its admin panel work fine out of the box (default
> config), also both work fine in my dev environment with our re-based config.
>
> production has load blancing, as pretty much the only diffrence, and that is
> where the admin panel is not working.
>
> logs showing everything working... --> http://privatepaste.com/8930199c58
>
> heres our activemq.xml --> http://privatepaste.com/c6bc1f5379
>
> from a vanilla untarring the only files we've changed are activeme.xml and
> /bin/activemq (upped memory)
>
> so in short, as of updating to 5.3.1 the admin console never shows up,
> netstat doesn't show anything running on port 8161, although the logs tell
> me it has been launched. anyone else encounter this problem?
I just double-checked this with the 5.3.1 binary tarball from the
release and the admin console is working just fine. If you download a
fresh binary, expand it and run it without modifying the activemq.xml,
does the admin console work for you?
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder