Matthias Neubert schrieb:
Hallo again,
now things get confusing. After having success running the iPojo
tutorial under current config yesterday,
it now hangs on startup:
in Felix.start() (line 720)
(without changes in code)
Reseting the emulator doesn't help.
I do not get an real error. Only one warning (which I also had
yesterday, but it worked yesterday despite of this warning) But I have
the feeling
that this warning belongs to this problem
Here last Log data before it hangs:
07-10 14:39:35.902: WARN/System.err(751): Problem creating boot
delegation class loader: java.lang.reflect.InvocationTargetException
I can confirm this behaviour.
07-10 14:41:59.962: INFO/global(751): Default buffer size used in
BufferedReader constructor. It would be better to be explicit if an
8k-char buffer is required.
...
07-10 14:42:53.082: INFO/global(751): Default buffer size used in
BufferedReader constructor. It would be better to be explicit if an
8k-char buffer is required.
07-10 14:43:14.641: INFO/System.out(751): DEBUG: WIRE: 2.0 ->
org.osgi.framework -> 0
07-10 14:43:14.761: INFO/System.out(751): DEBUG: WIRE: 1.0 ->
org.osgi.framework -> 0
07-10 14:43:14.781: INFO/System.out(751): DEBUG: WIRE: 1.0 ->
org.osgi.service.url -> 0
07-10 14:43:14.781: INFO/System.out(751): DEBUG: WIRE: 1.0 ->
org.osgi.service.log -> 2.0
here the app just stops. It remains running, but nothing happens. It
like a deadlock, an endless waiting on something.
Which bundles are you currently running in your application? I updated
to 1.9.0 yesterday evening and did not run into any problems. Bundles
currently installed:
org.apache.felix.log-1.1.0-SNAPSHOT.jar
org.apache.felix.fileinstall-1.3.0-SNAPSHOT.jar
org.apache.felix.shell-1.3.0-SNAPSHOT.jar
org.apache.felix.shell.remote-1.0.5-SNAPSHOT.jar
org.apache.felix.http.jetty-1.1.0-SNAPSHOT.jar
javax.servlet-1.0.1-SNAPSHOT.jar
no issues so far. I just added the classes.dex to the bundles, no
modification of the source.
I guess the warning has something to do with the patch richard made for
making 1.9.0 work/start on Android. As far as I remember that was
an class loader problem.
I also wonders why sometime felix-cache had to be deleted in order to
make the app starting correctly. But even this doesn't help now.
I have so far not witnessed this behaviour because i do create a new
temporary directory each time felix starts.
Cheers,
Stephan
I think I was happy to early, but I hope we can get this too.
regards
matthias
p.s.: code can be found on:
http://code.google.com/p/felixembeddedonandroid/source/checkout
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
