[jira] [Commented] (AMQ-4998) Old Web Admin console does not manage - new parameter messageTTL consumerTTL connections.jsp and connections Panel display error messages
[
https://issues.apache.org/jira/browse/AMQ-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896329#comment-13896329
]
Guilhem RAMBAL commented on AMQ-4998:
-
You could try my patch file include migration of network ttl ->2 messageTTL
consumerTTL
> Old Web Admin console does not manage - new parameter messageTTL
> consumerTTL connections.jsp and connections Panel display error messages
> ---
>
> Key: AMQ-4998
> URL: https://issues.apache.org/jira/browse/AMQ-4998
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.9.0
> Environment: CentOS release 6.4 (Final)
> java version "1.6.0_45"
> Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
>Reporter: Guilhem RAMBAL
>Priority: Critical
> Attachments: connections.patch
>
>
> 2014-01-29 13:03:31,358 | WARN | /admin/connections.jsp |
> org.eclipse.jetty.servlet.ServletHandler | qtp1721309039-46
> javax.el.PropertyNotFoundException: The class 'com.sun.proxy.$Proxy7' does
> not have the property 'networkTTL'.
> at javax.el.BeanELResolver.getBeanProperty(BeanELResolver.java:579)
> at javax.el.BeanELResolver.getValue(BeanELResolver.java:281)
> 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.connections_jsp._jspx_meth_c_forEach_1(org.apache.jsp.connections_jsp:213)
> at
> org.apache.jsp.connections_jsp._jspService(org.apache.jsp.connections_jsp:95)
> 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:1320)
> at
> org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
> at
> org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:45)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
> at
> org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:102)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
> 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:1291)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:443)
> 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)
> This template seems to work :
>
>
>
> Name
> Message TTL
> Consumer TTL
> Dynamic Only
> Conduit Subscriptions
> Bridge Temps
> Decrease Priorities
> Dispatch Async
>
>
>
>
>
> ${nc.name}
> ${nc.messageTTL}
> ${nc.consumerTTL}
> ${nc.dynamicOnly}
> ${nc.conduitSubscriptions}
> ${nc.bridgeTempDestinations}
> ${nc.decreaseNetworkConsumerPriority}
> ${nc.dispatchAsync}
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (AMQ-4998) Old Web Admin console does not manage - new parameter messageTTL consumerTTL connections.jsp and connections Panel display error messages
[
https://issues.apache.org/jira/browse/AMQ-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guilhem RAMBAL updated AMQ-4998:
Attachment: connections.patch
This is the patch file
> Old Web Admin console does not manage - new parameter messageTTL
> consumerTTL connections.jsp and connections Panel display error messages
> ---
>
> Key: AMQ-4998
> URL: https://issues.apache.org/jira/browse/AMQ-4998
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.9.0
> Environment: CentOS release 6.4 (Final)
> java version "1.6.0_45"
> Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
>Reporter: Guilhem RAMBAL
>Priority: Critical
> Attachments: connections.patch
>
>
> 2014-01-29 13:03:31,358 | WARN | /admin/connections.jsp |
> org.eclipse.jetty.servlet.ServletHandler | qtp1721309039-46
> javax.el.PropertyNotFoundException: The class 'com.sun.proxy.$Proxy7' does
> not have the property 'networkTTL'.
> at javax.el.BeanELResolver.getBeanProperty(BeanELResolver.java:579)
> at javax.el.BeanELResolver.getValue(BeanELResolver.java:281)
> 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.connections_jsp._jspx_meth_c_forEach_1(org.apache.jsp.connections_jsp:213)
> at
> org.apache.jsp.connections_jsp._jspService(org.apache.jsp.connections_jsp:95)
> 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:1320)
> at
> org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
> at
> org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:45)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
> at
> org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:102)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
> 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:1291)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:443)
> 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)
> This template seems to work :
>
>
>
> Name
> Message TTL
> Consumer TTL
> Dynamic Only
> Conduit Subscriptions
> Bridge Temps
> Decrease Priorities
> Dispatch Async
>
>
>
>
>
> ${nc.name}
> ${nc.messageTTL}
> ${nc.consumerTTL}
> ${nc.dynamicOnly}
> ${nc.conduitSubscriptions}
> ${nc.bridgeTempDestinations}
> ${nc.decreaseNetworkConsumerPriority}
> ${nc.dispatchAsync}
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (AMQ-4998) Old Web Admin console does not manage - new parameter messageTTL consumerTTL connections.jsp and connections Panel display error messages
[
https://issues.apache.org/jira/browse/AMQ-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guilhem RAMBAL updated AMQ-4998:
Environment:
CentOS release 6.4 (Final)
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
> Old Web Admin console does not manage - new parameter messageTTL
> consumerTTL connections.jsp and connections Panel display error messages
> ---
>
> Key: AMQ-4998
> URL: https://issues.apache.org/jira/browse/AMQ-4998
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.9.0
> Environment: CentOS release 6.4 (Final)
> java version "1.6.0_45"
> Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
>Reporter: Guilhem RAMBAL
>Priority: Critical
>
> 2014-01-29 13:03:31,358 | WARN | /admin/connections.jsp |
> org.eclipse.jetty.servlet.ServletHandler | qtp1721309039-46
> javax.el.PropertyNotFoundException: The class 'com.sun.proxy.$Proxy7' does
> not have the property 'networkTTL'.
> at javax.el.BeanELResolver.getBeanProperty(BeanELResolver.java:579)
> at javax.el.BeanELResolver.getValue(BeanELResolver.java:281)
> 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.connections_jsp._jspx_meth_c_forEach_1(org.apache.jsp.connections_jsp:213)
> at
> org.apache.jsp.connections_jsp._jspService(org.apache.jsp.connections_jsp:95)
> 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:1320)
> at
> org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
> at
> org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:45)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
> at
> org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:102)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
> 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:1291)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:443)
> 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)
> This template seems to work :
>
>
>
> Name
> Message TTL
> Consumer TTL
> Dynamic Only
> Conduit Subscriptions
> Bridge Temps
> Decrease Priorities
> Dispatch Async
>
>
>
>
>
> ${nc.name}
> ${nc.messageTTL}
> ${nc.consumerTTL}
> ${nc.dynamicOnly}
> ${nc.conduitSubscriptions}
> ${nc.bridgeTempDestinations}
> ${nc.decreaseNetworkConsumerPriority}
> ${nc.dispatchAsync}
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (AMQ-5000) New Web Admin- jolokia error: Cannot connect to Jolokia to access this Java process with -- ACTIVEMQ_OPTS="-Dorg.apache.activemq.UseDedicatedTaskRunner=false"
[ https://issues.apache.org/jira/browse/AMQ-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885483#comment-13885483 ] Guilhem RAMBAL commented on AMQ-5000: - Yes . Maybe you need to improve documentation when using hawtio and want to use ACTIVEMQ_OPTS you need to put : -Djava.util.logging.config.file=logging.properties -Dhawtio.realm=activemq -Dhawtio.role=admins -Dhawtio.rolePrincipalClasses=org.apache.activemq.jaas.GroupPrincipal -Djava.security.auth.login.config=$ACTIVEMQ_CONF/login.config Sincerely > New Web Admin- jolokia error: Cannot connect to Jolokia to access this Java > process with -- > ACTIVEMQ_OPTS="-Dorg.apache.activemq.UseDedicatedTaskRunner=false" > - > > Key: AMQ-5000 > URL: https://issues.apache.org/jira/browse/AMQ-5000 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.9.0 >Reporter: Guilhem RAMBAL >Assignee: Dejan Bosanac > > java.lang.SecurityException: Impossible de trouver une configuration de > connexion > at com.sun.security.auth.login.ConfigFile.(ConfigFile.java:93) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at java.lang.Class.newInstance0(Class.java:357) > at java.lang.Class.newInstance(Class.java:310) > at javax.security.auth.login.Configuration$3.run(Configuration.java:247) > at java.security.AccessController.doPrivileged(Native Method) > at > javax.security.auth.login.Configuration.getConfiguration(Configuration.java:242) > at javax.security.auth.login.LoginContext$1.run(LoginContext.java:237) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.login.LoginContext.init(LoginContext.java:234) > at javax.security.auth.login.LoginContext.(LoginContext.java:367) > at javax.security.auth.login.LoginContext.(LoginContext.java:444) > at io.hawt.system.Authenticator.doAuthenticate(Authenticator.java:99) > at io.hawt.system.Authenticator.authenticate(Authenticator.java:76) > at > io.hawt.web.AuthenticationFilter.doFilter(AuthenticationFilter.java:84) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291) > at io.hawt.web.CORSFilter.doFilter(CORSFilter.java:42) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:443) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:532) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1044) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:372) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:978) > 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:532) > 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:367) > at > org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:486) > at > org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:937) > at > org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:998) > at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:861) > at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) > at > org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) > at > org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:628) > at > org.eclipse.jetty.io.nio.Sel
[jira] [Commented] (AMQ-5000) New Web Admin- jolokia error: Cannot connect to Jolokia to access this Java process with -- ACTIVEMQ_OPTS="-Dorg.apache.activemq.UseDedicatedTaskRunner=false"
[ https://issues.apache.org/jira/browse/AMQ-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885455#comment-13885455 ] Guilhem RAMBAL commented on AMQ-5000: - I Think is link not with -Dorg.apache.activemq.UseDedicatedTaskRunner=false but ACTIVEMQ_OPTS with parameter I put in activemq.conf : Not working: ACTIVEMQ_OPTS="-Xms4096M -Xmx4096M -Dorg.apache.activemq.UseDedicatedTaskRunner=false" cat /proc/31354/cmdline /usr/java/default/bin/java-Xms4096M-Xmx4096M-Dorg.apache.activemq.UseDedicatedTaskRunner=false-Dcom.sun.management.jmxremote.port=11099-Dcom.sun.management.jmxremote.password.file=/hawai/composants/activemq/conf/jmx.password-Dcom.sun.management.jmxremote.access.file=/hawai/composants/activemq/conf/jmx.access-Dcom.sun.management.jmxremote.ssl=false-Dcom.sun.management.jmxremote-Djava.awt.headless=true-Djava.io.tmpdir=/hawai/composants/activemq/tmp-Dactivemq.classpath=/hawai/composants/activemq/conf;-Dactivemq.home=/hawai/composants/activemq-Dactivemq.base=/hawai/composants/activemq-Dactivemq.conf=/hawai/composants/activemq/conf-Dactivemq.data=/hawai/composants/activemq/data-jar/hawai/composants/activemq/bin/activemq.jarstart Not Working (loose of xms xmx): ACTIVEMQ_OPTS_MEMORY="-Xms4096M -Xmx4096M" #ACTIVEMQ_OPTS="-Xms4096M -Xmx4096M -Dorg.apache.activemq.UseDedicatedTaskRunner=false" ACTIVEMQ_OPTS="-Dorg.apache.activemq.UseDedicatedTaskRunner=false" #ACTIVEMQ_OPTS="-Xms4096M -Xmx4096M" cat /proc/707/cmdline /usr/java/default/bin/java-Dorg.apache.activemq.UseDedicatedTaskRunner=false-Dcom.sun.management.jmxremote.port=11099-Dcom.sun.management.jmxremote.password.file=/hawai/composants/activemq/conf/jmx.password-Dcom.sun.management.jmxremote.access.file=/hawai/composants/activemq/conf/jmx.access-Dcom.sun.management.jmxremote.ssl=false-Dcom.sun.management.jmxremote-Djava.awt.headless=true-Djava.io.tmpdir=/hawai/composants/activemq/tmp-Dactivemq.classpath=/hawai/composants/activemq/conf;-Dactivemq.home=/hawai/composants/activemq-Dactivemq.base=/hawai/composants/activemq-Dactivemq.conf=/hawai/composants/activemq/conf-Dactivemq.data=/hawai/composants/activemq/data-jar/hawai/composants/activemq/bin/activemq.jarstart Not working: #ACTIVEMQ_OPTS_MEMORY="-Xms4096M -Xmx4096M" #ACTIVEMQ_OPTS="-Xms4096M -Xmx4096M -Dorg.apache.activemq.UseDedicatedTaskRunner=false" #ACTIVEMQ_OPTS="-Dorg.apache.activemq.UseDedicatedTaskRunner=false" ACTIVEMQ_OPTS="-Xms4096M -Xmx4096M cat /proc/1092/cmdline /usr/java/default/bin/java-Xms4096M-Xmx4096M-Dcom.sun.management.jmxremote.port=11099-Dcom.sun.management.jmxremote.password.file=/hawai/composants/activemq/conf/jmx.password-Dcom.sun.management.jmxremote.access.file=/hawai/composants/activemq/conf/jmx.access-Dcom.sun.management.jmxremote.ssl=false-Dcom.sun.management.jmxremote-Djava.awt.headless=true-Djava.io.tmpdir=/hawai/composants/activemq/tmp-Dactivemq.classpath=/hawai/composants/activemq/conf;-Dactivemq.home=/hawai/composants/activemq-Dactivemq.base=/hawai/composants/activemq-Dactivemq.conf=/hawai/composants/activemq/conf-Dactivemq.data=/hawai/composants/activemq/data-jar/hawai/composants/activemq/bin/activemq.jarstart Working: # Set jvm memory configuration ACTIVEMQ_OPTS_MEMORY="-Xms4096M -Xmx4096M" #ACTIVEMQ_OPTS="-Xms4096M -Xmx4096M -Dorg.apache.activemq.UseDedicatedTaskRunner=false" #ACTIVEMQ_OPTS="-Xms4096M -Xmx4096M" cat /proc/32617/cmdline /usr/java/default/bin/java-Xms4096M-Xmx4096M-Djava.util.logging.config.file=logging.properties-Dhawtio.realm=activemq-Dhawtio.role=admins-Dhawtio.rolePrincipalClasses=org.apache.activemq.jaas.GroupPrincipal-Djava.security.auth.login.config=/hawai/composants/activemq/conf/login.config-Dcom.sun.management.jmxremote.port=11099-Dcom.sun.management.jmxremote.password.file=/hawai/composants/activemq/conf/jmx.password-Dcom.sun.management.jmxremote.access.file=/hawai/composants/activemq/conf/jmx.access-Dcom.sun.management.jmxremote.ssl=false-Dcom.sun.management.jmxremote-Djava.awt.headless=true-Djava.io.tmpdir=/hawai/composants/activemq/tmp-Dactivemq.classpath=/hawai/composants/activemq/conf;-Dactivemq.home=/hawai/composants/activemq-Dactivemq.base=/hawai/composants/activemq-Dactivemq.conf=/hawai/composants/activemq/conf-Dactivemq.data=/hawai/composants/activemq/data-jar/hawai/composants/activemq/bin/activemq.jarstart !!! Working !!!: #ACTIVEMQ_OPTS_MEMORY="-Xms4096M -Xmx4096M" #ACTIVEMQ_OPTS="-Xms4096M -Xmx4096M -Dorg.apache.activemq.UseDedicatedTaskRunner=false" #ACTIVEMQ_OPTS="-Dorg.apache.activemq.UseDedicatedTaskRunner=false" ACTIVEMQ_OPTS="-Xms4096M -Xmx4096M -Dorg.apache.activemq.UseDedicatedTaskRunner=false -Djava.util.logging.config.file=logging.properties -Dhawtio.realm=activemq -Dhawtio.role=admins -Dhawtio.rolePrincipalClasses=org.apache.activemq.jaas.GroupPrincipal -Djava.security.auth.login.config=$ACTIVEMQ_CONF/login.config" cat /proc/1419/cmdline /usr/java/default/bin/java-Xms4096M-Xmx4096M-Dorg.apac
[jira] [Created] (AMQ-5000) New Web Admin- jolokia error: Cannot connect to Jolokia to access this Java process with -- ACTIVEMQ_OPTS="-Dorg.apache.activemq.UseDedicatedTaskRunner=false"
Guilhem RAMBAL created AMQ-5000: --- Summary: New Web Admin- jolokia error: Cannot connect to Jolokia to access this Java process with -- ACTIVEMQ_OPTS="-Dorg.apache.activemq.UseDedicatedTaskRunner=false" Key: AMQ-5000 URL: https://issues.apache.org/jira/browse/AMQ-5000 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.9.0 Reporter: Guilhem RAMBAL java.lang.SecurityException: Impossible de trouver une configuration de connexion at com.sun.security.auth.login.ConfigFile.(ConfigFile.java:93) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:357) at java.lang.Class.newInstance(Class.java:310) at javax.security.auth.login.Configuration$3.run(Configuration.java:247) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.Configuration.getConfiguration(Configuration.java:242) at javax.security.auth.login.LoginContext$1.run(LoginContext.java:237) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.LoginContext.init(LoginContext.java:234) at javax.security.auth.login.LoginContext.(LoginContext.java:367) at javax.security.auth.login.LoginContext.(LoginContext.java:444) at io.hawt.system.Authenticator.doAuthenticate(Authenticator.java:99) at io.hawt.system.Authenticator.authenticate(Authenticator.java:76) at io.hawt.web.AuthenticationFilter.doFilter(AuthenticationFilter.java:84) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291) at io.hawt.web.CORSFilter.doFilter(CORSFilter.java:42) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:443) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:532) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1044) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:372) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:978) 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:532) 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:367) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:486) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:937) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:998) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:861) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:628) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) 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(Thread.java:662) Caused by: java.io.IOException: Impossible de trouver une configuration de connexion at com.sun.security.auth.login.ConfigFile.init(ConfigFile.java:250) at com.sun.security.auth.login.ConfigFile.(ConfigFile.java:91) ... 45 more Caused by: java.io.IOException: Impossible de trouver une configuration de connexion at com.sun.security.auth.login.ConfigFile.init(ConfigFile.java:250) at com.sun.security.auth.login.ConfigFile.(ConfigFile.java:91) at s
[jira] [Created] (AMQ-4998) Old Web Admin console does not manage - new parameter messageTTL consumerTTL connections.jsp and connections Panel display error messages
Guilhem RAMBAL created AMQ-4998:
---
Summary: Old Web Admin console does not manage - new parameter
messageTTL consumerTTL connections.jsp and connections Panel display error
messages
Key: AMQ-4998
URL: https://issues.apache.org/jira/browse/AMQ-4998
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.9.0
Reporter: Guilhem RAMBAL
Priority: Critical
2014-01-29 13:03:31,358 | WARN | /admin/connections.jsp |
org.eclipse.jetty.servlet.ServletHandler | qtp1721309039-46
javax.el.PropertyNotFoundException: The class 'com.sun.proxy.$Proxy7' does not
have the property 'networkTTL'.
at javax.el.BeanELResolver.getBeanProperty(BeanELResolver.java:579)
at javax.el.BeanELResolver.getValue(BeanELResolver.java:281)
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.connections_jsp._jspx_meth_c_forEach_1(org.apache.jsp.connections_jsp:213)
at
org.apache.jsp.connections_jsp._jspService(org.apache.jsp.connections_jsp:95)
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:1320)
at
org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
at org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:45)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
at
org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:102)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291)
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:1291)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:443)
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)
This template seems to work :
Name
Message TTL
Consumer TTL
Dynamic Only
Conduit Subscriptions
Bridge Temps
Decrease Priorities
Dispatch Async
${nc.name}
${nc.messageTTL}
${nc.consumerTTL}
${nc.dynamicOnly}
${nc.conduitSubscriptions}
${nc.bridgeTempDestinations}
${nc.decreaseNetworkConsumerPriority}
${nc.dispatchAsync}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Reopened] (AMQ-3843) ActiveMQ 5.6.0 requires JDK now
[ https://issues.apache.org/jira/browse/AMQ-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guilhem RAMBAL reopened AMQ-3843: - This is a workaround, to work as 5.5.0 you need sun jdk instead of jre, because of tools.jar usage. > ActiveMQ 5.6.0 requires JDK now > --- > > Key: AMQ-3843 > URL: https://issues.apache.org/jira/browse/AMQ-3843 > Project: ActiveMQ > Issue Type: Bug > Components: JMX >Affects Versions: 5.6.0 >Reporter: Guilhem RAMBAL > Fix For: 5.7.0 > > > With this code : > https://issues.apache.org/jira/browse/AMQ-2464 > When you stop activemq regulary with jre instead of jdk : > Connecting to pid: 3316 > ERROR: java.lang.NullPointerException > java.lang.NullPointerException > at javax.management.remote.JMXServiceURL.(JMXServiceURL.java:139) > at > org.apache.activemq.console.command.AbstractJmxCommand.handleOption(AbstractJmxCommand.java:350) > at > org.apache.activemq.console.command.ShutdownCommand.handleOption(ShutdownCommand.java:156) > at > org.apache.activemq.console.command.AbstractCommand.parseOptions(AbstractCommand.java:73) > at > org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:45) > at > org.apache.activemq.console.command.AbstractJmxCommand.execute(AbstractJmxCommand.java:380) > at > org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:148) > at > org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57) > at > org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at org.apache.activemq.console.Main.runTaskClass(Main.java:257) > at org.apache.activemq.console.Main.main(Main.java:111) > . > INFO: Regular shutdown not successful, sending SIGKILL to process with pid > '3316' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-3843) ActiveMQ 5.6.0 requires JDK now
Guilhem RAMBAL created AMQ-3843: --- Summary: ActiveMQ 5.6.0 requires JDK now Key: AMQ-3843 URL: https://issues.apache.org/jira/browse/AMQ-3843 Project: ActiveMQ Issue Type: Bug Components: JMX Affects Versions: 5.6.0 Reporter: Guilhem RAMBAL With this code : https://issues.apache.org/jira/browse/AMQ-2464 When you stop activemq regulary with jre instead of jdk : Connecting to pid: 3316 ERROR: java.lang.NullPointerException java.lang.NullPointerException at javax.management.remote.JMXServiceURL.(JMXServiceURL.java:139) at org.apache.activemq.console.command.AbstractJmxCommand.handleOption(AbstractJmxCommand.java:350) at org.apache.activemq.console.command.ShutdownCommand.handleOption(ShutdownCommand.java:156) at org.apache.activemq.console.command.AbstractCommand.parseOptions(AbstractCommand.java:73) at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:45) at org.apache.activemq.console.command.AbstractJmxCommand.execute(AbstractJmxCommand.java:380) at org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:148) at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57) at org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.activemq.console.Main.runTaskClass(Main.java:257) at org.apache.activemq.console.Main.main(Main.java:111) . INFO: Regular shutdown not successful, sending SIGKILL to process with pid '3316' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3451) Tomcat 6.0.32 complains that ActiveMQ 5.5 doesn't shutdown a thread
[ https://issues.apache.org/jira/browse/AMQ-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268345#comment-13268345 ] Guilhem RAMBAL commented on AMQ-3451: - Hello, Have you got a workaround to solve this issue ? Sincerely > Tomcat 6.0.32 complains that ActiveMQ 5.5 doesn't shutdown a thread > --- > > Key: AMQ-3451 > URL: https://issues.apache.org/jira/browse/AMQ-3451 > Project: ActiveMQ > Issue Type: Bug > Components: JMS client >Affects Versions: 5.5.0 > Environment: jdk 1.6.0_23 for Linux 64 bit, Ubuntu 11.04 > Tomcat 6.0.32 > Spring 3.0.5 >Reporter: John Miller > Labels: leak, resource > > Every time when restarting web application in Tomcat Manager I get messages: > SEVERE: The web application [/sms] appears to have started a thread named > [ActiveMQ Task-3] but has failed to stop it. This is very likely to create a > memory leak. > With every restart PermGen space is increased and finally i got OutOfMemory > error for PermGen space. > I use Spring DefaultMessageListenerContainer, and it's shutdown method closes > properly receivers threads. What is "ActiveMQ Task-3" thread and how to close > it properly ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
