activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torbjorn Kristoffersen <torbjo...@gmail.com>
Subject Re: HTTP ERROR 503 in latest ActiveMQ 5.4.0
Date Thu, 19 Aug 2010 19:04:52 GMT
I did a clean install.  I know I said upgraded in the original mail,
but I meant as in deleting the old 5.3.2 and installing 5.4.0.  This
is on a development machine.

On Thu, Aug 19, 2010 at 8:32 PM, Joe Niski <joe.niski@nwea.org> wrote:
> For what it's worth, the default jetty.xml is quite different in 5.4.0 than in 5.3.x.
My old (5.3.0) jetty config didn't work at all with 5.4.0, but it was easy to modify the default
to do what i wanted.
>
> Joe Niski
> IS Development |  NWEA
>
> PHONE 503.212.3382  |  FAX 503.639.7873
>
> NWEA.ORG<3D%22http://www.nwea.org/%22>  |  Partnering to Help All Kids Learn
>
> On 08/19/2010 10:39 AM, Torbjorn Kristoffersen wrote:
>
> I upgraded to ActiveMQ 5.4.0, and running OpenSolaris (b134) on Intel hardware.
>
> I start ActiveMQ, and the broker seems to function, but the jetty
> server does not display any web pages. I get the following if I try to
> access http://<my_ip>:8161/admin
>
> HTTP ERROR: 503
>
> Problem accessing /admin/. Reason:
>
>   Service Unavailable
>
> This is what I see in activemq.log. Not much that pinpoints any
> specific problem or where to start looking.  Please assist..?  I tried
> ActiveMQ 5.4.0 on OS X and it works fine, so it appears to only
> trigger in (Open)Solaris.  I also run Glassfish V3 on this computer
> and everything java-based is up to date.
>
>
>
> ----snip---snip---snip------
>
> 2010-08-19 19:29:02,442 | WARN  | FAILED Jersey Filter:
> com.sun.jersey.api.container.ContainerException:  |
> org.eclipse.jetty.util.log | main
> 2010-08-19 19:29:02,453 | DEBUG | EXCEPTION  | org.eclipse.jetty.util.log | main
> com.sun.jersey.api.container.ContainerException:
>

Mime
View raw message