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 <james.strachan@gmail.com> 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 <philtomson@gmail.com> 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 <philtomson@gmail.com> 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
>>
>>
>>
>
>
|