Not a serious problem. Everything should work ok. On 9/8/06, rubyfan <[EMAIL PROTECTED]> wrote:
Other than the warning below, it looks like it works. Is the warning about not being able to start the jmx connector a serious problem? $ ./activemq ACTIVEMQ_OPTS IS -Xmx512M -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Dderby.system.home=../data -Dderby.storage.fileSyncTransactionLog=true -Dcom.sun.management.jmxremote JAVACMD is: /usr/local/kaffe//bin/java ACTIVEMQ_HOME: /home/patomson/devel/incubator-activemq-4.0.1 Loading message broker from: xbean:activemq.xml Created MBeanServer with ID: [UID: 215454526,1157735673001,-32768]:phpe-dev-10:1 INFO BrokerService - ActiveMQ 4.0.1 JMS Message Broker (localhost) is starting INFO BrokerService - For help or more information please see: http://incubator.apache.org/activemq/ WARN ManagementContext - Failed to start jmx connector: javax.naming.NoInitialContextException: Can't find property: java.naming.factory.initial INFO JDBCPersistenceAdapter - Database driver recognized: [apache_derby_embedded_jdbc_driver] INFO TransportServerThreadSupport - Listening for connections at: tcp://phpe-dev-10:61616 INFO TransportConnector - Connector default Started INFO TransportServerThreadSupport - Listening for connections at: tcp://phpe-dev-10:61613?wireFormat=stomp INFO TransportConnector - Connector stomp Started INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:phpe-dev-10-32806-1157735671413-1:0) started Hiram Chirino wrote: > > Ok.. try this: > > activemq.xml: > > <!-- START SNIPPET: example --> > <beans xmlns="http://activemq.org/config/1.0";> > > <bean > class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/> > > <broker useJmx="true"> > > <!-- In ActiveMQ 4, you can setup destination policies --> > <destinationPolicy> > <policyMap><policyEntries> > > <policyEntry topic="FOO.>"> > <dispatchPolicy> > <strictOrderDispatchPolicy /> > </dispatchPolicy> > <subscriptionRecoveryPolicy> > <lastImageSubscriptionRecoveryPolicy /> > </subscriptionRecoveryPolicy> > </policyEntry> > > </policyEntries></policyMap> > </destinationPolicy> > > > <persistenceAdapter> > <journaledJDBC useJournal="false" dataSource="#derby-ds" > dataDirectory="target/defaultBroker-data"/> > </persistenceAdapter> > > <transportConnectors> > <transportConnector name="default" uri="tcp://localhost:61616"/> > <transportConnector name="stomp" uri="stomp://localhost:61613"/> > </transportConnectors> > > <networkConnectors> > <!-- > <networkConnector name="host1 and host2" > uri="static://(tcp://host1:61616,tcp://host2:61616)" failover="true"/> > --> > </networkConnectors> > > </broker> > > <bean id="derby-ds" class="org.apache.derby.jdbc.EmbeddedDataSource"> > <property name="databaseName" value="derbydb"/> > <property name="createDatabase" value="create"/> > </bean> > > </beans> > > On 9/7/06, rubyfan <[EMAIL PROTECTED]> wrote: >> >> Here's the activemq.xml included below (BTW: how useful is ActiveMQ >> without >> multicast?) >> >> activemq.xml: >> >> <!-- START SNIPPET: example --> >> <beans xmlns="http://activemq.org/config/1.0";> >> >> <!-- Allows us to use system properties as variables in this >> configuration >> file --> >> <bean >> class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/> >> >> <broker useJmx="true"> >> >> <!-- Use the following to set the broker memory limit (in bytes) >> <memoryManager> >> <usageManager id="memory-manager" limit="1048576"/> >> </memoryManager> >> --> >> >> <!-- Use the following to configure how ActiveMQ is exposed in JMX >> <managementContext> >> <managementContext connectorPort="1099" >> jmxDomainName="org.apache.activemq"/> >> </managementContext> >> --> >> >> <!-- In ActiveMQ 4, you can setup destination policies --> >> <destinationPolicy> >> <policyMap><policyEntries> >> >> <policyEntry topic="FOO.>"> >> <dispatchPolicy> >> <strictOrderDispatchPolicy /> >> </dispatchPolicy> >> <subscriptionRecoveryPolicy> >> <lastImageSubscriptionRecoveryPolicy /> >> </subscriptionRecoveryPolicy> >> </policyEntry> >> >> </policyEntries></policyMap> >> </destinationPolicy> >> >> >> <persistenceAdapter> >> <journaledJDBC journalLogFiles="4" journalLogFileSize="32768" >> useJournal="false" dataSource="#derby-ds" >> dataDirectory="target/defaultBroker-data"/> >> <!-- To use a different datasource, use th following syntax : --> >> <!-- >> <journaledJDBC journalLogFiles="5" dataDirectory="../activemq-data" >> dataSource="#postgres-ds"/> >> --> >> </persistenceAdapter> >> >> <transportConnectors> >> <transportConnector name="default" uri="tcp://localhost:61616" >> discoveryUri="multicast://default"/> >> <transportConnector name="stomp" uri="stomp://localhost:61613"/> >> </transportConnectors> >> >> <networkConnectors> >> <!-- by default just auto discover the other brokers --> >> <networkConnector name="default" uri="multicast://default"/> >> <!-- >> <networkConnector name="host1 and host2" >> uri="static://(tcp://host1:61616,tcp://host2:61616)" failover="true"/> >> --> >> </networkConnectors> >> >> </broker> >> >> <!-- This xbean configuration file supports all the standard spring >> xml >> configuration options --> >> >> <bean id="derby-ds" class="org.apache.derby.jdbc.EmbeddedDataSource"> >> <property name="databaseName" value="derbydb"/> >> <property name="createDatabase" value="create"/> >> </bean> <!-- Postgres DataSource Sample Setup --> >> >> <!-- >> <bean id="postgres-ds" class="org.postgresql.ds.PGPoolingDataSource"> >> <property name="serverName" value="localhost"/> >> <property name="databaseName" value="activemq"/> >> <property name="portNumber" value="0"/> >> <property name="user" value="activemq"/> >> <property name="password" value="activemq"/> >> <property name="dataSourceName" value="postgres"/> >> <property name="initialConnections" value="1"/> >> <property name="maxConnections" value="10"/> >> </bean> >> --> >> >> <!-- MySql DataSource Sample Setup --> >> <!-- >> <bean id="mysql-ds" class="org.apache.commons.dbcp.BasicDataSource" >> destroy-method="close"> >> <property name="driverClassName" value="com.mysql.jdbc.Driver"/> >> <property name="url" >> value="jdbc:mysql://localhost/activemq?relaxAutoCommit=true"/> >> <property name="username" value="activemq"/> >> <property name="password" value="activemq"/> >> <property name="poolPreparedStatements" value="true"/> >> </bean> >> --> >> >> <!-- Embedded Derby DataSource Sample Setup --> >> <!-- >> <bean id="derby-ds" class="org.apache.derby.jdbc.EmbeddedDataSource"> >> <property name="databaseName" value="derbydb"/> >> <property name="createDatabase" value="create"/> >> </bean> >> --> >> >> </beans> >> <!-- END SNIPPET: example --> >> >> Hiram Chirino wrote: >> > >> > looks like Multicast is not fully supported either! lol! >> > >> > Could you send us your current activemq.xml and I'll send it back to >> > you with the multicast options disabled? >> > >> > Regards, >> > Hiram >> > >> > On 9/7/06, rubyfan <[EMAIL PROTECTED]> wrote: >> >> >> >> I tried your suggestion and got the following: >> >> >> >> $ ./activemq >> >> ACTIVEMQ_OPTS IS -Xmx512M >> >> -Dorg.apache.activemq.UseDedicatedTaskRunner=true >> >> -Dderby.system.home=../data >> -Dderby.storage.fileSyncTransactionLog=true >> >> -Dcom.sun.management.jmxremote >> >> JAVACMD is: /usr/local/kaffe//bin/java >> >> ACTIVEMQ_HOME: /home/patomson/devel/incubator-activemq-4.0.1 >> >> Loading message broker from: xbean:activemq.xml >> >> Created MBeanServer with ID: [UID: >> >> 127329967,1157580786153,-32768]:phpe-dev-10:1 >> >> INFO BrokerService - ActiveMQ 4.0.1 JMS Message >> Broker >> >> (localhost) is starting >> >> INFO BrokerService - For help or more information >> >> please >> >> see: http://incubator.apache.org/activemq/ >> >> WARN ManagementContext - Failed to start jmx connector: >> >> javax.naming.NoInitialContextException: Can't find property: >> >> java.naming.factory.initial >> >> INFO JDBCPersistenceAdapter - Database driver recognized: >> >> [apache_derby_embedded_jdbc_driver] >> >> INFO TransportServerThreadSupport - Listening for connections at: >> >> tcp://phpe-dev-10:61616 >> >> WARN MulticastDiscoveryAgent - brokerName not set >> >> ERROR BrokerService - Failed to start ActiveMQ JMS >> >> Message >> >> Broker. Reason: java.net.SocketException: Unknown socket option >> >> java.net.SocketException: Unknown socket option >> >> at gnu.java.net.PlainDatagramSocketImpl.setOption >> >> (PlainDatagramSocketImpl.java:90) >> >> at java.net.MulticastSocket.setLoopbackMode >> (MulticastSocket.java:257) >> >> at >> >> >> org.apache.activemq.transport.discovery.multicast.MulticastDiscoveryAgent.start >> >> (MulticastDiscoveryAgent.java:220) >> >> at org.apache.activemq.broker.TransportConnector.start >> >> (TransportConnector.java:205) >> >> at org.apache.activemq.broker.BrokerService.startTransportConnector >> >> (BrokerService.java:1118) >> >> at org.apache.activemq.broker.BrokerService.startAllConnectors >> >> (BrokerService.java:1075) >> >> at org.apache.activemq.broker.BrokerService.start >> >> (BrokerService.java:369) >> >> at org.apache.activemq.xbean.XBeanBrokerService.afterPropertiesSet >> >> (XBeanBrokerService.java:43) >> >> at >> >> >> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods >> >> (AbstractAutowireCapableBeanFactory.java:1059) >> >> at >> >> >> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean >> >> (AbstractAutowireCapableBeanFactory.java:363) >> >> at >> >> org.springframework.beans.factory.support.AbstractBeanFactory.getBean >> >> (AbstractBeanFactory.java:226) >> >> at >> >> org.springframework.beans.factory.support.AbstractBeanFactory.getBean >> >> (AbstractBeanFactory.java:147) >> >> at >> >> >> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons >> >> (DefaultListableBeanFactory.java:275) >> >> at >> >> org.springframework.context.support.AbstractApplicationContext.refresh >> >> (AbstractApplicationContext.java:320) >> >> at >> >> org.apache.xbean.spring.context.ClassPathXmlApplicationContext.<init> >> >> (ClassPathXmlApplicationContext.java:158) >> >> at >> >> org.apache.xbean.spring.context.ClassPathXmlApplicationContext.<init> >> >> (ClassPathXmlApplicationContext.java:48) >> >> at org.apache.activemq.xbean.XBeanBrokerFactory.createBroker >> >> (XBeanBrokerFactory.java:40) >> >> at org.apache.activemq.broker.BrokerFactory.createBroker >> >> (BrokerFactory.java:56) >> >> at org.apache.activemq.console.command.StartCommand.startBroker >> >> (StartCommand.java:81) >> >> at org.apache.activemq.console.command.StartCommand.runTask >> >> (StartCommand.java:46) >> >> at org.apache.activemq.console.command.AbstractCommand.execute >> >> (AbstractCommand.java:49) >> >> at org.apache.activemq.console.command.ShellCommand.runTask >> >> (ShellCommand.java:81) >> >> at org.apache.activemq.console.command.AbstractCommand.execute >> >> (AbstractCommand.java:49) >> >> at org.apache.activemq.console.command.ShellCommand.main >> >> (ShellCommand.java:45) >> >> at java.lang.reflect.Method.invoke0 (Method.java) >> >> at java.lang.reflect.Method.invoke (Method.java:255) >> >> at org.apache.activemq.console.Main.runTaskClass (Main.java:135) >> >> at org.apache.activemq.console.Main.main (Main.java:67) >> >> at java.lang.reflect.Method.invoke0 (Method.java) >> >> at java.lang.reflect.Method.invoke (Method.java:255) >> >> at org.kaffe.jar.ExecJarName.main (ExecJarName.java:64) >> >> at org.kaffe.jar.ExecJar.main (ExecJar.java:57) >> >> >> >> ERROR: java.lang.RuntimeException: Failed to execute start task. >> Reason: >> >> org.springframework.beans.factory.BeanCreationException: Error >> creating >> >> bean >> >> with name 'org.apache.activemq.xbean.XBeanBrokerService' defined in >> class >> >> path resource [activemq.xml]: Initialization of bean failed; nested >> >> exception is java.net.SocketException: Unknown socket option >> >> ERROR: java.lang.Exception: >> >> org.springframework.beans.factory.BeanCreationException: Error >> creating >> >> bean >> >> with name 'org.apache.activemq.xbean.XBeanBrokerService' defined in >> class >> >> path resource [activemq.xml]: Initialization of bean failed; nested >> >> exception is java.net.SocketException: Unknown socket option >> >> >> >> >> >> Adrian Co wrote: >> >> > >> >> > Hi, >> >> > >> >> > You could try specifying your persistence adapter to be just jdbc: >> >> > >> >> > <persistenceAdapter> >> >> > <jdbcPersistenceAdapter dataSource="#derby-ds"/> >> >> > </persistenceAdapter> >> >> > >> >> > ... >> >> > >> >> > <bean id="derby-ds" >> class="org.apache.derby.jdbc.EmbeddedDataSource"> >> >> > <property name="databaseName" value="derbydb"/> >> >> > <property name="createDatabase" value="create"/> >> >> > </bean> >> >> > >> >> > Or better yet, if you're using the default journal-jdbc adapter, >> just >> >> set >> >> > useJournal to false: >> >> > >> >> > <persistenceAdapter> >> >> > <journaledJDBC journalLogFiles="4" journalLogFileSize="32768" >> >> > useJournal="false" dataSource="#derby-ds" >> >> > dataDirectory="target/defaultBroker-data"/> >> >> > </persistenceAdapter> >> >> > >> >> > >> >> > Regards, >> >> > Adrian Co >> >> > >> >> > rubyfan wrote: >> >> >> How does one go about "disabling the journal" ? >> >> >> >> >> >> >> >> >> Hiram Chirino wrote: >> >> >> >> >> >>> I would suggest disabling the journal. Just run with direct jdbc. >> >> >>> the Journal uses some NIO file access witch Kaffe might not be >> >> liking. >> >> >>> >> >> >>> On 9/6/06, James Strachan <[EMAIL PROTECTED]> wrote: >> >> >>> >> >> >>>> It mostly starts up then. I wonder if you delete the >> activemq-data/ >> >> >>>> directory and run it again does it do any better? Am wondering if >> >> that >> >> >>>> directory was created and populated with non-kaffe JVM causing >> >> >>>> marshalling issues? >> >> >>>> >> >> >>>> On 9/6/06, rubyfan <[EMAIL PROTECTED]> wrote: >> >> >>>> >> >> >>>>> Running activemq using kaffe gives the following results: >> >> >>>>> $ ./activemq >> >> >>>>> ACTIVEMQ_OPTS IS -Xmx512M >> >> >>>>> >> >> >>>> -Dorg.apache.activemq.UseDedicatedTaskRunner=true >> >> >>>> >> >> >>>>> -Dderby.system.home=../data >> >> >>>>> -Dderby.storage.fileSyncTransactionLog=true >> >> >>>>> -Dcom.sun.management.jmxremote >> >> >>>>> ACTIVEMQ_HOME: /home/patomson/devel/incubator-activemq-4.0.1 >> >> >>>>> Loading message broker from: xbean:activemq.xml >> >> >>>>> Created MBeanServer with ID: [UID: >> >> >>>>> 116661362,1157564156300,-32768]:phpe-dev-10:1 >> >> >>>>> INFO BrokerService - ActiveMQ 4.0.1 JMS >> Message >> >> >>>>> >> >> >>>> Broker >> >> >>>> >> >> >>>>> (localhost) is starting >> >> >>>>> INFO BrokerService - For help or more >> information >> >> >>>>> >> >> >>>> please >> >> >>>> >> >> >>>>> see: http://incubator.apache.org/activemq/ >> >> >>>>> WARN ManagementContext - Failed to start jmx >> >> connector: >> >> >>>>> javax.naming.NoInitialContextException: Can't find property: >> >> >>>>> java.naming.factory.initial >> >> >>>>> INFO JDBCPersistenceAdapter - Database driver >> recognized: >> >> >>>>> [apache_derby_embedded_jdbc_driver] >> >> >>>>> INFO JournalPersistenceAdapter - Journal Recovery Started >> >> from: >> >> >>>>> >> >> >>>> Active >> >> >>>> >> >> >>>>> Journal: using 5 x 20.0 Megs at: >> >> >>>>> >> /home/patomson/devel/incubator-activemq-4.0.1/activemq-data/journal >> >> >>>>> kaffe-bin: gc-incremental.c:1311: gcFree: Assertion `!!!"Attempt >> to >> >> >>>>> explicitly free nonfixed object"' failed. >> >> >>>>> Aborted >> >> >>>>> >> >> >>>>> >> >> >>>>> >> >> >>>>> >> >> >>>>> Adrian Co wrote: >> >> >>>>> >> >> >>>>>> Out of curiosity, what problems/exceptions are you >> encountering? >> >> >>>>>> >> >> >>>>>> rubyfan wrote: >> >> >>>>>> >> >> >>>>>>> I tried running ActiveMQ using kaffe and I can confirm that it >> >> does >> >> >>>>>>> >> >> >>>> not >> >> >>>> >> >> >>>>>>> work. >> >> >>>>>>> Currently investigating running it with gij, but I'm losing >> hope >> >> >>>>>>> >> >> >>>> that >> >> >>>> >> >> >>>>>>> that >> >> >>>>>>> will work either. >> >> >>>>>>> >> >> >>>>>>> >> >> >>>>>>> >> >> >>>>>>> James.Strachan wrote: >> >> >>>>>>> >> >> >>>>>>> >> >> >>>>>>>> On 8/28/06, rubyfan <[EMAIL PROTECTED]> wrote: >> >> >>>>>>>> >> >> >>>>>>>> >> >> >>>>>>>>> Is it possible to run ActiveMQ using the kaffe VM and libs >> >> (open >> >> >>>>>>>>> >> >> >>>> source >> >> >>>> >> >> >>>>>>>>> java >> >> >>>>>>>>> vm and libs http://www.kaffe.org/)? >> >> >>>>>>>>> >> >> >>>>>>>>> >> >> >>>>>>>> I've no idea - try it and see :) >> >> >>>>>>>> >> >> >>>>>>>> >> >> >>>>>>>> >> >> >>>>>>>> >> >> >>>>>>>>> Does anyone happen to have a script which is equivilent to >> the >> >> >>>>>>>>> bin/activemq >> >> >>>>>>>>> script which uses kaffe instead of Sun's java? >> >> >>>>>>>>> >> >> >>>>>>>>> >> >> >>>>>>>> No - though the script should work with any JVM. Just set >> >> JAVACMD >> >> >>>>>>>> >> >> >>>> to >> >> >>>> >> >> >>>>>>>> be whatever the command is to run 'java' >> >> >>>>>>>> >> >> >>>>>>>> >> >> >>>>>>>> -- >> >> >>>>>>>> >> >> >>>>>>>> James >> >> >>>>>>>> ------- >> >> >>>>>>>> http://radio.weblogs.com/0112098/ >> >> >>>>>>>> >> >> >>>>>>>> >> >> >>>>>>>> >> >> >>>>>>>> >> >> >>>>>>> >> >> >>>>>> >> >> >>>>>> >> >> >>>>> -- >> >> >>>>> View this message in context: >> >> >>>>> >> >> >>>> >> >> >> http://www.nabble.com/Running-ActiveMQ-under-kaffe-tf2180373.html#a6176300 >> >> >>>> >> >> >>>>> Sent from the ActiveMQ - User forum at Nabble.com. >> >> >>>>> >> >> >>>>> >> >> >>>>> >> >> >>>> -- >> >> >>>> >> >> >>>> James >> >> >>>> ------- >> >> >>>> http://radio.weblogs.com/0112098/ >> >> >>>> >> >> >>>> >> >> >>> -- >> >> >>> Regards, >> >> >>> Hiram >> >> >>> >> >> >>> Blog: http://hiramchirino.com >> >> >>> >> >> >>> >> >> >>> >> >> >> >> >> >> >> >> > >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Running-ActiveMQ-under-kaffe-tf2180373.html#a6194433 >> >> Sent from the ActiveMQ - User forum at Nabble.com. >> >> >> >> >> > >> > >> > -- >> > Regards, >> > Hiram >> > >> > Blog: http://hiramchirino.com >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Running-ActiveMQ-under-kaffe-tf2180373.html#a6195157 >> Sent from the ActiveMQ - User forum at Nabble.com. >> >> > > > -- > Regards, > Hiram > > Blog: http://hiramchirino.com > > -- View this message in context: http://www.nabble.com/Running-ActiveMQ-under-kaffe-tf2180373.html#a6213438 Sent from the ActiveMQ - User forum at Nabble.com.
-- Regards, Hiram Blog: http://hiramchirino.com
