-
1. Re: Fabric error: "Cannot obtain service: org.osgi.service.url.URLStreamHandlerService(url.handler.protocol=profile)"
abhishekkoneru6790 Feb 27, 2015 9:59 AM (in response to kodiak22)Hi, I am not a fabric expert but hope our analysis help.
When you create fabric, Create a new Completely new container and use that. Do no add anything on the default container.
This messes up the whole environment.
If you are already doing this, then even I am waiting for an answer
Hope this helps.
-
2. Re: Fabric error: "Cannot obtain service: org.osgi.service.url.URLStreamHandlerService(url.handler.protocol=profile)"
kodiak22 Mar 2, 2015 5:10 AM (in response to abhishekkoneru6790)Hi Abhishek,
I didn't add anything to the new container, I just restarted it.
Besides, the whole point of the fabric container is that you can add new functionalities by assigning profiles to them.
We've been doing that constantly and the root container is no exception.
As for the error, I've managed to eliminate it by compiling a fabric-agent jar with a longer timeout (120s).
But after som further struggling I've concluded that the fabric-agent in this version (redhat-067 EA) is really buggy.
Our application happily runs in standalone mode, but not in a child container, where it doesn't even start properly.
Peter
-
3. Re: Fabric error: "Cannot obtain service: org.osgi.service.url.URLStreamHandlerService(url.handler.protocol=profile)"
grgrzybek Mar 5, 2015 8:12 AM (in response to kodiak22)Hi
[FABRIC-790] Provisioning failure when using profile:xxx references - JBoss Issue Tracker was to fix issues related to provisioning resources with "profile:" url. But you may be right - this timeout should be configurable.
regards
Grzegorz Grzybek
-
4. Re: Fabric error: "Cannot obtain service: org.osgi.service.url.URLStreamHandlerService(url.handler.protocol=profile)"
grgrzybek Mar 5, 2015 9:01 AM (in response to grgrzybek)Also I have to mention that setting this await for "profile:" url handler helped a lot with all our automated tests which create child containers.
WIthout it they failed with "java.net.MalformedURLException: Unknown protocol: profile" exception
regards
Grzegorz Grzybek
-
5. Re: Fabric error: "Cannot obtain service: org.osgi.service.url.URLStreamHandlerService(url.handler.protocol=profile)"
kodiak22 Mar 5, 2015 10:03 AM (in response to grgrzybek)Hi Grzegorz,
Thanks for the reply. As I wrote, I've managed to eliminate this error, but there are others that keep holding Us from using this EA version.
So we decided to wait for a more stable version, until then we're going to use the vanilla karaf-2.4.1 for development.
regards
Peter
-
6. Re: Fabric error: "Cannot obtain service: org.osgi.service.url.URLStreamHandlerService(url.handler.protocol=profile)"
grgrzybek Mar 5, 2015 10:20 AM (in response to kodiak22)I've changed this await for "profile:" url handler and replaced it with more (and longer) retries of downloading the artifacts.
So [FABRIC-790] Provisioning failure when using profile:xxx references - JBoss Issue Tracker is still correct, but there should be no more problems like the one from the beginning of this thread.
regards
Grzegorz Grzybek
-
7. Re: Fabric error: "Cannot obtain service: org.osgi.service.url.URLStreamHandlerService(url.handler.protocol=profile)"
kodiak22 Mar 5, 2015 11:49 AM (in response to grgrzybek)I will try it in the next build.
thanks
Peter
-
8. Re: Fabric error: "Cannot obtain service: org.osgi.service.url.URLStreamHandlerService(url.handler.protocol=profile)"
grgrzybek Mar 6, 2015 4:05 AM (in response to kodiak22)The fix is present in 1.2.0 branch of Fabric8: Switch from waiting for URL handlers to more download attempts · 2b5d6ef · jboss-fuse/fabric8 · GitHub
regards
Grzegorz Grzybek