My co-worker is struggling (it's probably proguard) and it would be useful to know if somebody had succeeded.
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+...@googlegroups.com.
To post to this group, send email to akka...@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
-- Martin Krasser blog: http://krasserm.blogspot.com code: http://github.com/krasserm twitter: http://twitter.com/mrt1nz
You received this message because you are subscribed to a topic in the Google Groups "Akka User List" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/akka-user/qaBSx6sJH2Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to akka-user+...@googlegroups.com.
To post to this group, send email to akka...@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
Hi MartinUnfortunately I don't have his code (he's inn a different Timezone and I only got email last night) but his stack trace
so it looks like there's some reason it can't find the akka.persistence.DeliveredByChannelBatchingconstructor.
I'll get him to add further info here as soon as he comes on line.
Hi Martin,When I get hold of him I intend to ensure we can run a simple test program in both "standard" environment before re-testing on Android. I can see the DeliveredByChannelBatching is part of the standard start-up process and there's no obvious reason the constructor should be "missing". From what little I know of Android development, the culprit in these cases is usually Proguard being over-enthusiastic about pruning stuff it thinks is not required.
If we can get a simple test program working I'll make sure we make it available. Personally I think the eventsource model is an excellent way of overcoming the problems associated with mobile applications being randomly stopped and restarted, either due to the Android OS kicking them out or users powering on and off.
akka.persistence.journal.leveldb.native = false(and remove the mapdb plugin configuration). The LevelDB Java port doesn't use any native libs.
Line 13:This error shows that the configuration by default provided by "reference.conf" isn't merged or automatically included **on Android**, as it usually happens on a "normal" development environment. Maybe this answers your question
04-28 08:54:25.036 12011-12032/com.optrak.sample I/System.out﹕ Caused by: com.typesafe.config.ConfigException$Missing: No configuration setting found for key 'journal.plugin'
04-28 08:54:25.046 12011-12032/com.optrak.sample I/System.out﹕ Caused by: akka.actor.InvalidActorNameException: actor name [snapshot-store] is not unique!
This (kind of) error
actor name [xxx] is not unique!
has been troubling us and have no idea what is the source of problem (on Android)
------
By the way, did you read this (from a previous message)? What do you think?
> https://github.com/Optrak/akkaPersistenceWithAndroid/blob/master/errorMsg2.txt#L203 > shows the guilty guy:
>
> pfn: can see what exactly is null there
> pfn: public static final int CPU_DATA_MODEL = Integer.getInteger("sun.arch.data.model");
> pfn: https://github.com/dain/leveldb/blob/master/leveldb/src/main/java/org/iq80/leveldb/impl/Iq80DBFactory.java#L32
> pfn: there you go
> pfn: leveldb won't even work on android
> pfn: there is no system property sun.arch.data.model
> pfn: so it returns null, unboxing to int => nullpointer
This error was obtained before removing every reference to leveldb in my application.conf. After that, it seemed I had some progress, because the next error message (errorMsg5.txt) seemed to be related to permissions to
write on the Android device.
Hello Martin.
Thanks a lot for helping us.
Following your suggestion gives this error:
https://github.com/Optrak/akkaPersistenceWithAndroid/blob/master/errorMsg6.txt
Line 13: 04-28 08:54:25.036 12011-12032/com.optrak.sample I/System.out﹕ Caused by: com.typesafe.config.ConfigException$Missing: No configuration setting found for key 'journal.plugin'
This error shows that the configuration by default provided by "reference.conf" isn't merged or automatically included **on Android**, as it usually happens on a "normal" development environment. Maybe this answers your question
> why do you copy&paste settings from reference.conf into your application.conf file?
And also this error (take a look at line 49 https://github.com/Optrak/akkaPersistenceWithAndroid/blob/master/errorMsg6.txt#L49)
04-28 08:54:25.046 12011-12032/com.optrak.sample I/System.out﹕ Caused by: akka.actor.InvalidActorNameException: actor name [snapshot-store] is not unique! This (kind of) error actor name [xxx] is not unique! has been troubling us and have no idea what is the source of problem (on Android) ------ By the way, did you read this (from a previous message)? What do you think? > https://github.com/Optrak/akkaPersistenceWithAndroid/blob/master/errorMsg2.txt#L203 > shows the guilty guy: > > pfn: can see what exactly is null there > pfn: public static final int CPU_DATA_MODEL = Integer.getInteger("sun.arch.data.model"); > pfn: https://github.com/dain/leveldb/blob/master/leveldb/src/main/java/org/iq80/leveldb/impl/Iq80DBFactory.java#L32 > pfn: there you go > pfn: leveldb won't even work on android > pfn: there is no system property sun.arch.data.model > pfn: so it returns null, unboxing to int => nullpointer This error was obtained before removing every reference to leveldb in my application.conf. After that, it seemed I had some progress, because the next error message (errorMsg5.txt) seemed to be related to permissions to write on the Android device.
Hello Martin.
Thanks a lot for helping us.
Following your suggestion gives this error:
https://github.com/Optrak/akkaPersistenceWithAndroid/blob/master/errorMsg6.txt
Line 13: 04-28 08:54:25.036 12011-12032/com.optrak.sample I/System.out﹕ Caused by: com.typesafe.config.ConfigException$Missing: No configuration setting found for key 'journal.plugin'This error shows that the configuration by default provided by "reference.conf" isn't merged or automatically included **on Android**, as it usually happens on a "normal" development environment. Maybe this answers your question
> why do you copy&paste settings from reference.conf into your application.conf file?
And also this error (take a look at line 49 https://github.com/Optrak/akkaPersistenceWithAndroid/blob/master/errorMsg6.txt#L49)
04-28 08:54:25.046 12011-12032/com.optrak.sample I/System.out﹕ Caused by: akka.actor.InvalidActorNameException: actor name [snapshot-store] is not unique! This (kind of) error actor name [xxx] is not unique! has been troubling us and have no idea what is the source of problem (on Android) ------ By the way, did you read this (from a previous message)? What do you think? > https://github.com/Optrak/akkaPersistenceWithAndroid/blob/master/errorMsg2.txt#L203 > shows the guilty guy: > > pfn: can see what exactly is null there > pfn: public static final int CPU_DATA_MODEL = Integer.getInteger("sun.arch.data.model"); > pfn: https://github.com/dain/leveldb/blob/master/leveldb/src/main/java/org/iq80/leveldb/impl/Iq80DBFactory.java#L32
> pfn: there you go > pfn: leveldb won't even work on android > pfn: there is no system property sun.arch.data.model > pfn: so it returns null, unboxing to int => nullpointer This error was obtained before removing every reference to leveldb in my application.conf. After that, it seemed I had some progress, because the next error message (errorMsg5.txt) seemed to be related to permissions to write on the Android device.