Hi,

This exception here is harmless but just annoying, the bundle is still 
generated and installed,  we have issues[1] & [2] to track it.

[1]https://ops4j1.jira.com/browse/PAXSB-75
[2]https://ops4j1.jira.com/browse/PAXURL-265
-------------
Freeman(Yue) Fang

Red Hat, Inc. 
FuseSource is now part of Red Hat



On 2014-6-18, at 上午1:37, John Dubchak wrote:

> JB,
> 
> I was following with this thread because we are in a similar situation 
> lacking internet access.
> 
> On first startup, with a populated system folder, I get the following error:
> 
> 17:34:40,647 | INFO  | FelixStartLevel  | core    | 22 - 
> org.apache.aries.jmx.core - 1.1.1 | Starting JMX OSGi agent
> 17:34:40,673 | INFO  | FelixStartLevel  | core    | 22 - 
> org.apache.aries.jmx.core - 1.1.1 | Registering MBean with ObjectName 
> [osgi.compendium:service=cm,version=1.3,framework=org.apache.felix.framework,uuid=4bce4fca-52f4-4b50-994d-918bd11e5800]
>  for service with service.id [10]
> 17:34:40,797 | INFO  | FelixStartLevel  | BlueprintContainerImpl    | 8 - 
> org.apache.aries.blueprint.core - 1.4.0 | Bundle 
> org.apache.karaf.jaas.modules is waiting for namespace handlers 
> [http://karaf.apache.org/xmlns/jaas/v1.0.0]
> 17:34:47,191 | WARN  | Thread-7         | BndUtils    | 2 - 
> org.ops4j.pax.url.wrap - 1.3.7 | Bundle cannot be generated
> java.io.IOException: Pipe closed
>       at 
> java.io.PipedInputStream.checkStateForReceive(PipedInputStream.java:261)[:1.7.0_60-ea]
>       at 
> java.io.PipedInputStream.receive(PipedInputStream.java:227)[:1.7.0_60-ea]
>       at 
> java.io.PipedOutputStream.write(PipedOutputStream.java:149)[:1.7.0_60-ea]
>       at 
> java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:253)[:1.7.0_60-ea]
>       at 
> java.util.zip.ZipOutputStream.closeEntry(ZipOutputStream.java:238)[:1.7.0_60-ea]
>       at 
> aQute.lib.osgi.Jar.writeResource(Jar.java:305)[2:org.ops4j.pax.url.wrap:1.3.7]
>       at 
> aQute.lib.osgi.Jar.write(Jar.java:211)[2:org.ops4j.pax.url.wrap:1.3.7]
>       at 
> org.ops4j.pax.swissbox.bnd.BndUtils$1.run(BndUtils.java:174)[2:org.ops4j.pax.url.wrap:1.3.7]
> 
> Do I need to configure the URL handler even if the system folder has been 
> seeded?
> 
> Thanks,
> John
> 
> On 6/11/14 8:17 AM, Jean-Baptiste Onofré wrote:
>> Hi,
>> 
>> ServiceMix (Karaf) first looks for the artifacts in the system folder.
>> If the artifact is not present in the system folder, then ServiceMix
>> tries to download from the repositories defined in
>> etc/org.ops4j.pax.url.mvn.cfg.
>> 
>> The system folder is a "local Maven repository" using the Maven
>> directories structure:
>> 
>> groupId/artifactId/version/artifactId-version[-classifier].type
>> 
>> It means that you can simply populate the system folder according to
>> this directories structure.
>> 
>> You can do it:
>> - by hand
>> - using Maven deploy plugin (mvn deploy:deploy-file with the system
>> folder URL)
>> - using Maven Karaf feature plugin (the features-maven-plugin provides a
>> add-features-to-repo goal that automatically populate a directory like
>> the system folder)
>> 
>> Regards
>> JB
>> 
>> On 06/11/2014 04:20 PM, kazanture wrote:
>>> Hello,
>>> we are evaluating different ESB solution for our project.
>>> The problem is our development enviroment is offline because of
>>> classification issues. I have installed servicemix, but to install
>>> additional features, karaf tries to connect online maven repositories. I
>>> have searched for the full features repository for servicemix but I could
>>> not find for the latest version(I have found for one of the previous
>>> versions).
>>> I guess I should be able to download the repository and manually place
>>> it to
>>> a local maven repository and redirect karaf to the local repository
>>> somehow.
>>> Any idea where i can find the repository and how i can do this?
>>> 
>>> 
>>> 
>>> --
>>> View this message in context:
>>> http://servicemix.396122.n5.nabble.com/Servicemix-offline-package-installation-tp5720803.html
>>> 
>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>> 
>> 

Reply via email to