Depends which solution you choose. Can be ensuring JMX is on (IIRC it is by default but didnt check), can just be configuring a remote connection. It is actually up to you
Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-12-09 11:51 GMT+01:00 joeleclems <[email protected]>: > Hi, > > There is certainly a configuration to make in the webconsole but don't you > think there is also a configuration in activemq embedded in tomee+? > > This log appear when tomee start, before any application is deployed: > /(...) > INFO: Creating Resource(id=MyJmsResourceAdapter) > 8 déc. 2014 10:33:15 org.apache.openejb.assembler.classic.Assembler > createResource > INFO: Thread pool size for 'MyJmsResourceAdapter' is (30) > 8 déc. 2014 10:33:15 org.apache.openejb.resource.activemq.ActiveMQ5Factory > createBroker > INFO: ActiveMQ5Factory creating broker > 8 déc. 2014 10:33:15 org.apache.openejb.resource.activemq.ActiveMQ5Factory > createBroker > INFO: Using ActiveMQ startup timeout of 10000ms > 8 déc. 2014 10:33:15 org.apache.openejb.resource.activemq.ActiveMQ5Factory$1 > run > INFO: Starting ActiveMQ BrokerService > 8 déc. 2014 10:33:15 org.apache.activemq.store.kahadb.plist.PListStoreImpl > doStart > INFO: PListStore:[/home/tomcat/activemq-data/localhost/tmp_storage] started > 8 déc. 2014 10:33:15 org.apache.activemq.broker.BrokerService > doStartPersistenceAdapter > INFO: Using Persistence Adapter: > KahaDBPersistenceAdapter[/tomcat/serveur/RI/jmsdata] > 8 déc. 2014 10:33:15 org.apache.activemq.broker.jmx.ManagementContext$1 run > INFO: JMX consoles can connect to > service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi > (...)/ > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/activemq-webconsole-multi-tomee-tp4673183p4673189.html > Sent from the TomEE Users mailing list archive at Nabble.com.
