activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Pickett (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2085) AMQ should not install a JMXConnectorServer for an MBeanServer it does not create
Date Tue, 27 Apr 2010 23:19:27 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59138#action_59138
] 

Phil Pickett commented on AMQ-2085:
-----------------------------------

I'm seeing some different behavior between a webapp with an embedded broker deployed to JBoss
and am suspicious that what I see may be related to these changes.  With ActiveMQ 5.3 and
the web demo chat application, I don't see the org.apache.activemq MBeans in the JBoss jmx-console
but with the ActiveMQ 5.2 version I do.

I'm bundling up the ActiveMQ demo webapps as two war files, demo52.war and demo53.war.  At
first I used the 5.2 jars for the 5.2 webapp and the 5.3 jars for the 5.3 webapp.  To only
vary one thing, I changed this so that each bundles the ActiveMQ 5.3 activemq-web-5.3.0.jar,
camel-core-2.0.0.jar, and jetty-util-6.1.9.jar.  The difference is that demo5.2 bundles activemq-core-5.2.0.jar
and demo53.war bundles activemq-core-5.3.0.jar.

When I deploy demo52.war to JBoss, open a browser to the app at URI http://localhost:8280/demo52/chat.html,
and enter a username, I see the messages in the JBoss log:

11:07:34,485 INFO  [TomcatDeployer] deploy, ctxPath=/demo52, warUrl=.../tmp/deploy/tmp8966298452211694373demo52-exp.war/
11:07:56,779 INFO  [BrokerService] Using Persistence Adapter: AMQPersistenceAdapter(activemq-data\localhost)
11:07:56,781 INFO  [AMQPersistenceAdapter] AMQStore starting using directory: activemq-data\localhost
11:07:56,820 INFO  [KahaStore] Kaha Store using data directory activemq-data\localhost\kr-store\state
11:07:56,891 INFO  [AMQPersistenceAdapter] Active data files: []
11:07:56,980 INFO  [BrokerService] ActiveMQ 5.2.0 JMS Message Broker (localhost) is starting
11:07:56,981 INFO  [BrokerService] For help or more information please see: http://activemq.apache.org/
11:07:56,988 INFO  [ManagementContext] JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
11:07:57,185 INFO  [KahaStore] Kaha Store using data directory activemq-data\localhost\kr-store\data
11:07:57,293 INFO  [BrokerService] ActiveMQ JMS Message Broker (localhost, ID:ppickett-PC-64367-1272388077023-0:0)
started
11:07:57,304 INFO  [TransportConnector] Connector vm://localhost Started

and also see the org.apache.activemq MBeans on the JBoss jmx-console at http://localhost:8280/jmx-console/

When I undeploy the demo52.war and deploy demo53.war, open a browser to http://localhost:8280/demo53/chat.html,
and enter a username, I see similar messages in the JBoss log:

11:11:18,962 INFO  [TomcatDeployer] deploy, ctxPath=/demo53, warUrl=.../tmp/deploy/tmp8938444770518177909demo53-exp.war/
11:11:35,950 INFO  [BrokerService] Using Persistence Adapter: AMQPersistenceAdapter(activemq-data\localhost)
11:11:35,952 INFO  [AMQPersistenceAdapter] AMQStore starting using directory: activemq-data\localhost
11:11:35,989 INFO  [KahaStore] Kaha Store using data directory activemq-data\localhost\kr-store\state
11:11:36,060 INFO  [AMQPersistenceAdapter] Active data files: []
11:11:36,125 INFO  [BrokerService] ActiveMQ 5.3.0 JMS Message Broker (localhost) is starting
11:11:36,125 INFO  [BrokerService] For help or more information please see: http://activemq.apache.org/
11:11:36,333 INFO  [KahaStore] Kaha Store using data directory activemq-data\localhost\kr-store\data
11:11:36,485 INFO  [ManagementContext] JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
11:11:36,490 INFO  [BrokerService] ActiveMQ JMS Message Broker (localhost, ID:ppickett-PC-64379-1272388296166-0:0)
started
11:11:36,501 INFO  [TransportConnector] Connector vm://localhost Started

but with the demo53.war, no org.apache.activemq MBeans are shown on the JBoss jmx-console.

Any ideas on this?

Thanks,

Phil


> AMQ should not install a JMXConnectorServer for an MBeanServer it does not create
> ---------------------------------------------------------------------------------
>
>                 Key: AMQ-2085
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2085
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMX
>    Affects Versions: 5.3.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 5.3.0
>
>
> ManagementContext tends to create a JMXConnectorServer whenever findMBeanServer is called.
 This seems like really wrong behavior -- amq should not be setting up jmx remoting on mbean
servers it hasn't created, certainly not as a side effect of something like creating a vm
transport connection:
> 	  createConnector():365, ManagementContext.java
> 	  findMBeanServer():293, ManagementContext.java
> 	  getMBeanServer():148, ManagementContext.java
> 	  start():77, ManagementContext.java
> 	  start():458, BrokerService.java
> 	  doCompositeConnect():123, VMTransportFactory.java
> 	  doConnect():53, VMTransportFactory.java
> 	  doConnect():51, TransportFactory.java
> 	  connect():80, TransportFactory.java
> 	  createTransport():239, ActiveMQConnectionFactory.java
> 	  createActiveMQConnection():254, ActiveMQConnectionFactory.java
> 	  createConnection():181, ActiveMQConnectionFactory.java
> 	  makeConnection():79, ActiveMQConnectionSupport.java
> 	  makeConnection():61, ActiveMQConnectionSupport.java
> 	  createManagedConnection():169, ActiveMQManagedConnectionFactory.java

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message