Hi
Under the docs directory there is a web console readme file. It has
some pointers about setting up security.
If still a problem then try enabling DEBUG or TRACE logging at io.hawt
and see if you can see more details.
On Sun, Feb 2, 2014 at 5:24 PM, John D. Ament wrote:
> Hi all,
>
> If I'm us
Hey I am seeing this value as negative for my broker :
RegionBroker regionBroker = (RegionBroker) brokerService.getRegionBroker();
DestinationStatistics brokerStats =
regionBroker.getDestinationStatistics();
*"brokerStats.getMessages().getCount()"
*
It should return number of messa
Sounds like your trying to architect a solution. If that's the case, there
are lots of ways to slice the problem, depending on the exact needs trying
to be met. For example, if adding or removing a broker is a once-a-year
action, then manual edits of configuration files may be perfectly
acceptabl
Check the file, conf/jetty-realm.properties - it contains the username and
password for the web console (unless jetty.xml has been modified).
Is the 403 error on url http://${broker}:8161/ ?
>
>
> Hi all,
>
> If I'm using the standalone broker of activemq, I'm not able to log
> in. From what I s
Ah, looking at the precise method of accessing the Admin View more carefully,
I recommend using BrokerService.getAdminView().
As for performance, I think once per minute is fine. However, I recommend
measuring as there are many variables that play in. I would try increasing
the rate (i.e. decrea
Hi all,
If I'm using the standalone broker of activemq, I'm not able to log
in. From what I saw, admin/admin should be the right credentials, but
no matter what I use to login I'm getting back a 403 forbidden.
I have no made any configuration changes to the default app.
John
Thanks for the suggestions.
I cannot go ahead with the other approaches you specified because of some
reasons.
So I just want to ask one more thing:
If I am using plugin to get all the stats.
than is there any other way to get stats without creating
"*ManagementContext*" and "*BrokerViewMBean*".
