You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by artnaseef <ar...@artnaseef.com> on 2014/02/13 05:12:38 UTC
Re: Problem with JMX mbean, not showing ActiveMQ.DLQ when ActiveMQ
service restarted
Is the broker configured with a persistent store? Is the persistent store in
tact after the restart?
Make sure the deleteAllMessagesOnStartup property is not set to true on the
broker.
--
View this message in context: http://activemq.2283324.n4.nabble.com/Problem-with-JMX-mbean-not-showing-ActiveMQ-DLQ-when-ActiveMQ-service-restarted-tp4677858p4677908.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Problem with JMX mbean, not showing ActiveMQ.DLQ when ActiveMQ
service restarted
Posted by artnaseef <ar...@artnaseef.com>.
Something is very odd. This error:
Should not be reported when hitting the main Queue page on the broker
because that page is iterating existing destinations in the broker, unless
the broker is starting up with JMX disabled.
Is it possible the wrapper is causing a different broker config file to be
used? If that's hard to tell, try making the config file invalid (i.e. put
random text in the file) and start the broker with the wrapper.
Another check - once the broker starts with the wrapper, is it possible to
connect JConsole of VisualVM to the broker?
--
View this message in context: http://activemq.2283324.n4.nabble.com/Problem-with-JMX-mbean-not-showing-ActiveMQ-DLQ-when-ActiveMQ-service-restarted-tp4677858p4677996.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Problem with JMX mbean, not showing ActiveMQ.DLQ when ActiveMQ
service restarted
Posted by sharma_arun_se <ar...@gmail.com>.
Below are answers:
>>Is that the exception from the attempt to access the queue via JMX, or
from the web console?
Ans: Both. I am getting this error from both JMX and/or from the web
console.
>> If it's from the web console, are you hitting the main Queue page, or
>> trying to hit the browse page for the DLQ? If the latter, then that
>> won't work as long as the Queue does not exist.
Ans: I am hitting main queue page.
You can have the broker auto-create the queue at startup; let me find that
config for you.
Ans: I added below entry for auto-create queue on fresh installation
<destinations>
<queue physicalName="ActiveMQ.DLQ" />
</destinations>
and installed wrapper service.
When I opened http://bwin5049:8161/admin/queues.jsp, I got same error. This
is happening both with ActiveMQ 5.8 and 5.9.
started wrapper service. G
--
View this message in context: http://activemq.2283324.n4.nabble.com/Problem-with-JMX-mbean-not-showing-ActiveMQ-DLQ-when-ActiveMQ-service-restarted-tp4677858p4677971.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Problem with JMX mbean, not showing ActiveMQ.DLQ when ActiveMQ
service restarted
Posted by artnaseef <ar...@artnaseef.com>.
Here's a page that tries to show how to setup startup destinations; it
doesn't render in the FireFox or Safari for me, but the show source can be
deciphered:
http://activemq.apache.org/configure-startup-destinations.html
Here's how to configure a startup destination:
<broker ...>
<destinations>
<queue physicalName="QUEUE.STARTUP" />
<topic physicalName="TOPIC.STARTUP" />
</destinations>
</broker>
--
View this message in context: http://activemq.2283324.n4.nabble.com/Problem-with-JMX-mbean-not-showing-ActiveMQ-DLQ-when-ActiveMQ-service-restarted-tp4677858p4677947.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Problem with JMX mbean, not showing ActiveMQ.DLQ when ActiveMQ
service restarted
Posted by artnaseef <ar...@artnaseef.com>.
Is that the exception from the attempt to access the queue via JMX, or
from the web console?
If it's from the web console, are you hitting the main Queue page, or
trying to hit the browse page for the DLQ? If the latter, then that won't
work as long as the Queue does not exist.
You can have the broker auto-create the queue at startup; let me find that
config for you.
>
>
> Yes, I already posted broker log when I post this issue first time. See
> top
> of this topic.
>
> The log from wrapper/broker is:
> 2014-02-12 15:46:46,812 | WARN | /admin/queues.jsp |
> org.eclipse.jetty.servlet.ServletHandler | qtp1530088410-59
> javax.el.ELException: java.lang.reflect.UndeclaredThrowableException
> at javax.el.BeanELResolver.getValue(BeanELResolver.java:298)
> at
> javax.el.CompositeELResolver.getValue(CompositeELResolver.java:175)
> at com.sun.el.parser.AstValue.getValue(AstValue.java:138)
> at
> com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:206)
> at
> org.apache.jasper.runtime.PageContextImpl.evaluateExpression(PageContextImpl.java:1001)
> at
> org.apache.jsp.queues_jsp._jspx_meth_c_param_0(org.apache.jsp.queues_jsp:291)
> at
> org.apache.jsp.queues_jsp._jspx_meth_c_url_0(org.apache.jsp.queues_jsp:264)
> at
> org.apache.jsp.queues_jsp._jspx_meth_c_forEach_0(org.apache.jsp.queues_jsp:173)
> at
> org.apache.jsp.queues_jsp._jspService(org.apache.jsp.queues_jsp:114)
> at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:389)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486)
> at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:652)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1329)
> at
> org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:83)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
> at
> org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:45)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
> at
> org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:102)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
> at
> com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(SiteMeshFilter.java:129)
> at
> com.opensymphony.sitemesh.webapp.SiteMeshFilter.doFilter(SiteMeshFilter.java:77)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:445)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:521)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1038)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:374)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:972)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:521)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
> at org.eclipse.jetty.server.Server.handle(Server.java:363)
> at
> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:483)
> at
> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:920)
> at
> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:982)
> at
> org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:635)
> at
> org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
> at
> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
> at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:627)
> at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:51)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.reflect.UndeclaredThrowableException
> at $Proxy5.getName(Unknown Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at javax.el.BeanELResolver.getValue(BeanELResolver.java:293)
> ... 51 more
> Caused by: javax.management.InstanceNotFoundException:
> org.apache.activemq:type=Broker,brokerName=localhost,destinationType=Queue,destinationName=ActiveMQ.DLQ
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(Unknown
> Source)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(Unknown
> Source)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(Unknown
> Source)
> at javax.management.MBeanServerInvocationHandler.invoke(Unknown
> Source)
> ... 57 more
>
>
>
> _______________________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/Problem-with-JMX-mbean-not-showing-ActiveMQ-DLQ-when-ActiveMQ-service-restarted-tp4677858p4677944.html
> To start a new topic under ActiveMQ - User, email
> ml-node+s2283324n2341805h3@n4.nabble.com
> To unsubscribe from ActiveMQ - User, visit
> http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2341805&code=YXJ0QGFydG5hc2VlZi5jb218MjM0MTgwNXwtMjA1NDcyNjY5MQ==
--
View this message in context: http://activemq.2283324.n4.nabble.com/Problem-with-JMX-mbean-not-showing-ActiveMQ-DLQ-when-ActiveMQ-service-restarted-tp4677858p4677946.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Problem with JMX mbean, not showing ActiveMQ.DLQ when ActiveMQ
service restarted
Posted by sharma_arun_se <ar...@gmail.com>.
Yes, I already posted broker log when I post this issue first time. See top
of this topic.
The log from wrapper/broker is:
2014-02-12 15:46:46,812 | WARN | /admin/queues.jsp |
org.eclipse.jetty.servlet.ServletHandler | qtp1530088410-59
javax.el.ELException: java.lang.reflect.UndeclaredThrowableException
at javax.el.BeanELResolver.getValue(BeanELResolver.java:298)
at
javax.el.CompositeELResolver.getValue(CompositeELResolver.java:175)
at com.sun.el.parser.AstValue.getValue(AstValue.java:138)
at
com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:206)
at
org.apache.jasper.runtime.PageContextImpl.evaluateExpression(PageContextImpl.java:1001)
at
org.apache.jsp.queues_jsp._jspx_meth_c_param_0(org.apache.jsp.queues_jsp:291)
at
org.apache.jsp.queues_jsp._jspx_meth_c_url_0(org.apache.jsp.queues_jsp:264)
at
org.apache.jsp.queues_jsp._jspx_meth_c_forEach_0(org.apache.jsp.queues_jsp:173)
at
org.apache.jsp.queues_jsp._jspService(org.apache.jsp.queues_jsp:114)
at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:389)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:652)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1329)
at
org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:83)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at
org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:45)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at
org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:102)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at
com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(SiteMeshFilter.java:129)
at
com.opensymphony.sitemesh.webapp.SiteMeshFilter.doFilter(SiteMeshFilter.java:77)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:445)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:521)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1038)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:374)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:972)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:521)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:363)
at
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:483)
at
org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:920)
at
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:982)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:635)
at
org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
at
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:627)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:51)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.reflect.UndeclaredThrowableException
at $Proxy5.getName(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at javax.el.BeanELResolver.getValue(BeanELResolver.java:293)
... 51 more
Caused by: javax.management.InstanceNotFoundException:
org.apache.activemq:type=Broker,brokerName=localhost,destinationType=Queue,destinationName=ActiveMQ.DLQ
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(Unknown
Source)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(Unknown
Source)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(Unknown
Source)
at javax.management.MBeanServerInvocationHandler.invoke(Unknown
Source)
... 57 more
--
View this message in context: http://activemq.2283324.n4.nabble.com/Problem-with-JMX-mbean-not-showing-ActiveMQ-DLQ-when-ActiveMQ-service-restarted-tp4677858p4677944.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Problem with JMX mbean, not showing ActiveMQ.DLQ when ActiveMQ
service restarted
Posted by artnaseef <ar...@artnaseef.com>.
Is there an error message in the broker log?
Sent from my iPhone
> On Feb 13, 2014, at 4:29 AM, "sharma_arun_se [via ActiveMQ]" <ml...@n4.nabble.com> wrote:
>
> Agree with you. We have no messages in DLQ, when I restarted ActiveMQ service.
>
> But ActiveMQ web-console queue tab (http://localhost:8161/admin/queues.jsp) must be visible to me which has other queue.
>
> But currently, it is throwing error when I click queue tab in ActiveMQ web-console.
>
> "
> Error!
>
> Exception occurred while processing this request, check the log for more information!"
>
>
> If you reply to this email, your message will be added to the discussion below:
> http://activemq.2283324.n4.nabble.com/Problem-with-JMX-mbean-not-showing-ActiveMQ-DLQ-when-ActiveMQ-service-restarted-tp4677858p4677927.html
> To start a new topic under ActiveMQ - User, email ml-node+s2283324n2341805h3@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here.
> NAML
--
View this message in context: http://activemq.2283324.n4.nabble.com/Problem-with-JMX-mbean-not-showing-ActiveMQ-DLQ-when-ActiveMQ-service-restarted-tp4677858p4677940.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Problem with JMX mbean, not showing ActiveMQ.DLQ when ActiveMQ
service restarted
Posted by sharma_arun_se <ar...@gmail.com>.
Agree with you. We have no messages in DLQ, when I restarted ActiveMQ
service.
But ActiveMQ web-console queue tab (http://localhost:8161/admin/queues.jsp)
must be visible to me which has other queue.
But currently, it is throwing error when I click queue tab in ActiveMQ
web-console.
"
Error!
Exception occurred while processing this request, check the log for more
information!"
--
View this message in context: http://activemq.2283324.n4.nabble.com/Problem-with-JMX-mbean-not-showing-ActiveMQ-DLQ-when-ActiveMQ-service-restarted-tp4677858p4677927.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Problem with JMX mbean, not showing ActiveMQ.DLQ when ActiveMQ
service restarted
Posted by artnaseef <ar...@artnaseef.com>.
Are there any messages on the DLQ at shutdown? If not, the DLQ won't be auto-created and so you won't find the mbean as indicated by the no such instance exception.
Sent from my iPhone
> On Feb 12, 2014, at 10:45 PM, "sharma_arun_se [via ActiveMQ]" <ml...@n4.nabble.com> wrote:
>
>
> We have default setting for persistent (ActiveMQ 5.8.x):
> <persistenceAdapter>
> <kahaDB directory="${activemq.data}/kahadb"/>
> </persistenceAdapter>
>
> Also we did not specify broker option "deleteAllMessagesOnStartup". So it must have its default value i.e. false
>
>
>
>
> If you reply to this email, your message will be added to the discussion below:
> http://activemq.2283324.n4.nabble.com/Problem-with-JMX-mbean-not-showing-ActiveMQ-DLQ-when-ActiveMQ-service-restarted-tp4677858p4677909.html
> To start a new topic under ActiveMQ - User, email ml-node+s2283324n2341805h3@n4.nabble.com
> To unsubscribe from ActiveMQ - User, click here.
> NAML
--
View this message in context: http://activemq.2283324.n4.nabble.com/Problem-with-JMX-mbean-not-showing-ActiveMQ-DLQ-when-ActiveMQ-service-restarted-tp4677858p4677912.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Problem with JMX mbean, not showing ActiveMQ.DLQ when ActiveMQ
service restarted
Posted by sharma_arun_se <ar...@gmail.com>.
We have default setting for persistent (ActiveMQ 5.8.x):
<persistenceAdapter>
<kahaDB directory="${activemq.data}/kahadb"/>
</persistenceAdapter>
Also we did not specify broker option "deleteAllMessagesOnStartup". So it
must have its default value i.e. false
--
View this message in context: http://activemq.2283324.n4.nabble.com/Problem-with-JMX-mbean-not-showing-ActiveMQ-DLQ-when-ActiveMQ-service-restarted-tp4677858p4677909.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.