You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Christian Mueller <ch...@gmail.com> on 2011/02/07 13:13:54 UTC
problem by installing a custom jboss-netty feature in SMX 4.2
Hello List!
We are using FUSE ESB 4.2.0-fuse-02-00 and providing our own features (based
on our use cases). We have a problem with one of our feature definitions.
If we run a
osgi:install -s mvn:org.jboss.netty/netty/3.1.5.GA
everything works well.
If we create a feature which includes this bundle like the following
<feature name="netty" version="1.1.0">
<bundle>mvn:org.jboss.netty/netty/3.1.5.GA</bundle>
</feature>
and we run a
features:install netty
Nothing happens. On the console, we get the following result:
features:install netty
null
Nothing in the log file.
Does anybody have also seen this issue? Any ideas why this is happening?
Thanks in advance,
Christian
--
View this message in context: http://servicemix.396122.n5.nabble.com/problem-by-installing-a-custom-jboss-netty-feature-in-SMX-4-2-tp3374147p3374147.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem by installing a custom jboss-netty feature in SMX 4.2
Posted by Christian Mueller <ch...@gmail.com>.
Hello Gert,
good, I think this will be less confusing users like me... ;-)
Thanks,
Christian
--
View this message in context: http://servicemix.396122.n5.nabble.com/problem-by-installing-a-custom-jboss-netty-feature-in-SMX-4-2-tp3374147p3376504.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem by installing a custom jboss-netty feature in SMX 4.2
Posted by Gert Vanthienen <ge...@gmail.com>.
Christian,
FWIW - we also created a JIRA issue in Karaf to try and make the
behavior of both commands consistent (cfr.
https://issues.apache.org/jira/browse/KARAF-448)
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Mon, Feb 7, 2011 at 10:40 PM, Christian Mueller
<ch...@gmail.com> wrote:
>
> Hallo Gert!
>
> Thank your for the hint. I upgraded our netty bundle to the one provided by
> Servicemix (3.2.3.FINAL_1) and everything looks good. Thank you (and
> Andreas) again for your quick help!
>
> Cheers,
> Christian
>
> --
> View this message in context: http://servicemix.396122.n5.nabble.com/problem-by-installing-a-custom-jboss-netty-feature-in-SMX-4-2-tp3374147p3374970.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
Re: problem by installing a custom jboss-netty feature in SMX 4.2
Posted by Christian Mueller <ch...@gmail.com>.
Hallo Gert!
Thank your for the hint. I upgraded our netty bundle to the one provided by
Servicemix (3.2.3.FINAL_1) and everything looks good. Thank you (and
Andreas) again for your quick help!
Cheers,
Christian
--
View this message in context: http://servicemix.396122.n5.nabble.com/problem-by-installing-a-custom-jboss-netty-feature-in-SMX-4-2-tp3374147p3374970.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem by installing a custom jboss-netty feature in SMX 4.2
Posted by Gert Vanthienen <ge...@gmail.com>.
Christian,
We're expecting the META-INF/MANIFEST.MF to be the first entry of the
JAR - not sure if that's part of any specification, but all the JAR
tooling (jar command line tool, Ant, Buildr, Maven, ...) seems to
behave that way anyway. One of the benefits is that you don't have to
read through an entire archive to get to the metadata, mostly
important for larger JAR files or things being downloaded over the
network. The FeaturesService uses the metadata to determine whether
or not the bundle listed in the feature is actually installed and can
be skipped. Looks like the OSGi framework itself does not depend on
that behavior, that's why a plain osgi:install works fine.
This issue is fixed in more recent versions of Netty
(https://issues.jboss.org/browse/NETTY-376), for the 3.2.3.Final
version we did our own bundle release to fix this issue.
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Mon, Feb 7, 2011 at 6:58 PM, Christian Mueller
<ch...@gmail.com> wrote:
>
> We use the official JBoss Netty artifact from
> http://repository.jboss.org/nexus/content/groups/public/
> We can try to build our own/correct OSGI bundle with the
> maven-bundle-plugin. But it looks strange for me, that osgi:install runs
> without a problem and wrapping only this bundle into a features fails by
> running features:install. I think both should run with success or both
> should fail...
>
> Christian
>
> --
> View this message in context: http://servicemix.396122.n5.nabble.com/problem-by-installing-a-custom-jboss-netty-feature-in-SMX-4-2-tp3374147p3374677.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
Re: problem by installing a custom jboss-netty feature in SMX 4.2
Posted by Christian Mueller <ch...@gmail.com>.
We use the official JBoss Netty artifact from
http://repository.jboss.org/nexus/content/groups/public/
We can try to build our own/correct OSGI bundle with the
maven-bundle-plugin. But it looks strange for me, that osgi:install runs
without a problem and wrapping only this bundle into a features fails by
running features:install. I think both should run with success or both
should fail...
Christian
--
View this message in context: http://servicemix.396122.n5.nabble.com/problem-by-installing-a-custom-jboss-netty-feature-in-SMX-4-2-tp3374147p3374677.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem by installing a custom jboss-netty feature in SMX 4.2
Posted by Andreas Pieber <an...@gmail.com>.
This means that your bundle does not follow the osgi standard. I'm not sure how
you build your artifact, but if you're using the latest version of the
maven-bundle-plugin this should not happen
kind regards,
andreas
On Mon, Feb 07, 2011 at 09:41:17AM -0800, Christian Mueller wrote:
>
> I tried to install it on FUSE ESB 4.3.0-fuse-03-00 and got a better error
> message:
>
> karaf@root> features:install netty
> Error executing command: Manifest not present in the first entry of the zip
>
> and the following stack trace in the servocemix.log file:
> {code}
> 18:31:31,282 | TRACE | l Console Thread | Connection |
> .pax.url.mvn.internal.Connection 181 | 1 - org.ops4j.pax.url.mvn - 1.2.1 |
> Downloading [Version [3.1.5.GA] from URL
> [file:/Users/cmueller/.m2/repository/org/jboss/netty/netty/3.1.5.GA/netty-3.1.5.GA.jar]]
> 18:31:31,283 | INFO | l Console Thread | Console |
> araf.shell.console.jline.Console 199 | 12 - org.apache.karaf.shell.console
> - 2.0.0.fuse-02-00 | Exception caught while executing command
> org.osgi.framework.BundleException: Manifest not present in the first entry
> of the zip
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installBundleIfNeeded(FeaturesServiceImpl.java:564)[21:org.apache.karaf.features.core:2.0.0.fuse-02-00]
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:404)[21:org.apache.karaf.features.core:2.0.0.fuse-02-00]
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:249)[21:org.apache.karaf.features.core:2.0.0.fuse-02-00]
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:238)[21:org.apache.karaf.features.core:2.0.0.fuse-02-00]
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:234)[21:org.apache.karaf.features.core:2.0.0.fuse-02-00]
> at
> org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:51)[11:org.apache.karaf.features.command:2.0.0.fuse-02-00]
> at
> org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)[11:org.apache.karaf.features.command:2.0.0.fuse-02-00]
> at
> org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:41)[12:org.apache.karaf.shell.console:2.0.0.fuse-02-00]
> at
> org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[12:org.apache.karaf.shell.console:2.0.0.fuse-02-00]
> at
> org.apache.felix.gogo.runtime.shell.CommandProxy.execute(CommandProxy.java:50)[17:org.apache.felix.gogo.runtime:0.4.0]
> at
> org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:229)[17:org.apache.felix.gogo.runtime:0.4.0]
> at
> org.apache.felix.gogo.runtime.shell.Closure.executeStatement(Closure.java:162)[17:org.apache.felix.gogo.runtime:0.4.0]
> at
> org.apache.felix.gogo.runtime.shell.Pipe.run(Pipe.java:101)[17:org.apache.felix.gogo.runtime:0.4.0]
> at
> org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:79)[17:org.apache.felix.gogo.runtime:0.4.0]
> at
> org.apache.felix.gogo.runtime.shell.CommandSessionImpl.execute(CommandSessionImpl.java:71)[17:org.apache.felix.gogo.runtime:0.4.0]
> at
> org.apache.karaf.shell.console.jline.Console.run(Console.java:181)[12:org.apache.karaf.shell.console:2.0.0.fuse-02-00]
> at java.lang.Thread.run(Thread.java:680)[:1.6.0_22]
> {code}
>
>
> The manifest file is the following:
> {code:title=MANIFEST:MF}
> Manifest-Version: 1.0
> Export-Package: org.jboss.netty.container.microcontainer;uses:="org.jb
> oss.netty.logging";version="3.1.5.GA",org.jboss.netty.channel.xnio;us
> es:="org.jboss.netty.buffer,org.jboss.xnio,org.jboss.netty.channel,or
> g.jboss.xnio.channels,org.jboss.netty.logging";version="3.1.5.GA",org
> .jboss.netty.handler.codec.serialization;uses:="org.jboss.netty.buffe
> r,org.jboss.netty.handler.codec.replay,org.jboss.netty.channel,org.jb
> oss.netty.handler.codec.oneone,org.jboss.netty.handler.codec.frame";v
> ersion="3.1.5.GA",org.jboss.netty.handler.codec.protobuf;uses:="org.j
> boss.netty.buffer,org.jboss.netty.channel,org.jboss.netty.handler.cod
> ec.oneone,com.google.protobuf";version="3.1.5.GA",org.jboss.netty.con
> tainer.guice;uses:="com.google.inject,org.jboss.netty.channel.socket.
> oio,org.jboss.netty.channel.socket,org.jboss.netty.channel.local,com.
> google.inject.binder,org.jboss.netty.channel.socket.nio";version="3.1
> .5.GA",org.jboss.netty.util;uses:="org.jboss.netty.buffer,org.jboss.n
> etty.channel,org.jboss.netty.logging";version="3.1.5.GA",org.jboss.ne
> tty.channel.socket.http;uses:="org.jboss.netty.channel,org.jboss.nett
> y.channel.socket,org.jboss.netty.handler.codec.http,javax.net.ssl,org
> .jboss.netty.handler.ssl,org.jboss.netty.buffer,org.jboss.netty.loggi
> ng,javax.servlet,org.jboss.netty.channel.local,javax.servlet.http";ve
> rsion="3.1.5.GA",org.jboss.netty.channel.group;uses:="org.jboss.netty
> .channel,org.jboss.netty.buffer,org.jboss.netty.logging";version="3.1
> .5.GA",org.jboss.netty.handler.codec.embedder;uses:="org.jboss.netty.
> channel,org.jboss.netty.buffer";version="3.1.5.GA",org.jboss.netty.ch
> annel.socket.oio;uses:="org.jboss.netty.channel,org.jboss.netty.chann
> el.socket,org.jboss.netty.util,org.jboss.netty.buffer,org.jboss.netty
> .logging";version="3.1.5.GA",org.jboss.netty.handler.execution;uses:=
> "org.jboss.netty.channel,org.jboss.netty.util,org.jboss.netty.logging
> ";version="3.1.5.GA",org.jboss.netty.handler.codec.frame;uses:="org.j
> boss.netty.buffer,org.jboss.netty.channel,org.jboss.netty.handler.cod
> ec.oneone";version="3.1.5.GA",org.jboss.netty.channel.local;uses:="or
> g.jboss.netty.channel,org.jboss.netty.logging";version="3.1.5.GA",org
> .jboss.netty.handler.codec.oneone;uses:="org.jboss.netty.channel";ver
> sion="3.1.5.GA",org.jboss.netty.container.osgi;uses:="org.jboss.netty
> .logging,org.jboss.netty.channel.socket.oio,org.jboss.netty.channel.s
> ocket,org.jboss.netty.channel,org.jboss.netty.channel.local,org.osgi.
> framework,org.jboss.netty.channel.socket.nio";version="3.1.5.GA",org.
> jboss.netty.bootstrap;uses:="org.jboss.netty.channel,org.jboss.netty.
> util";version="3.1.5.GA",org.jboss.netty.logging;uses:="org.apache.co
> mmons.logging,org.jboss.logging,org.apache.log4j,org.osgi.service.log
> ,org.osgi.util.tracker,org.osgi.framework,org.slf4j";version="3.1.5.G
> A",org.jboss.netty.buffer;version="3.1.5.GA",org.jboss.netty.handler.
> codec.base64;uses:="org.jboss.netty.buffer,org.jboss.netty.channel,or
> g.jboss.netty.handler.codec.oneone";version="3.1.5.GA",org.jboss.nett
> y.handler.timeout;uses:="org.jboss.netty.channel,org.jboss.netty.util
> ";version="3.1.5.GA",org.jboss.netty.handler.codec.http;uses:="org.jb
> oss.netty.buffer,org.jboss.netty.handler.codec.frame,org.jboss.netty.
> channel,org.jboss.netty.handler.codec.replay,org.jboss.netty.handler.
> codec.oneone";version="3.1.5.GA",org.jboss.netty.channel.socket.nio;u
> ses:="org.jboss.netty.logging,org.jboss.netty.channel.socket,org.jbos
> s.netty.channel,org.jboss.netty.util,org.jboss.netty.buffer";version=
> "3.1.5.GA",org.jboss.netty.channel.socket;uses:="org.jboss.netty.chan
> nel";version="3.1.5.GA",org.jboss.netty.handler.codec.replay;uses:="o
> rg.jboss.netty.buffer,org.jboss.netty.channel";version="3.1.5.GA",org
> .jboss.netty.handler.codec.string;uses:="org.jboss.netty.buffer,org.j
> boss.netty.channel,org.jboss.netty.handler.codec.oneone";version="3.1
> .5.GA",org.jboss.netty.channel;uses:="org.jboss.netty.buffer,org.jbos
> s.netty.util,org.jboss.netty.logging";version="3.1.5.GA",org.jboss.ne
> tty.handler.logging;uses:="org.jboss.netty.logging,org.jboss.netty.bu
> ffer,org.jboss.netty.channel";version="3.1.5.GA",org.jboss.netty.hand
> ler.stream;uses:="org.jboss.netty.buffer,org.jboss.netty.channel,org.
> jboss.netty.logging";version="3.1.5.GA",org.jboss.netty.container.spr
> ing;uses:="org.jboss.netty.logging,org.springframework.beans.factory"
> ;version="3.1.5.GA",org.jboss.netty.handler.ssl;uses:="org.jboss.nett
> y.channel,javax.net.ssl,org.jboss.netty.logging,org.jboss.netty.buffe
> r,org.jboss.netty.handler.codec.frame";version="3.1.5.GA"
> Private-Package: org.jboss.netty.example.http.snoop,org.jboss.netty.ex
> ample.securechat,org.jboss.netty.example.http.file,org.jboss.netty.ex
> ample.factorial,org.jboss.netty.example.http.tunnel,org.jboss.netty.e
> xample.uptime,org.jboss.netty.example.proxy,org.jboss.netty.example.t
> elnet,org.jboss.netty.example.objectecho,org.jboss.netty.example.echo
> ,org.jboss.netty.example.localtime,org.jboss.netty.example.discard,or
> g.jboss.netty.example.qotm,org.jboss.netty.util.internal,org.jboss.ne
> tty.example.local
> Built-By: trustin
> Tool: Bnd-0.0.311
> Bundle-Name: The Netty Project
> Created-By: Apache Maven Bundle Plugin
> Bundle-Vendor: JBoss, by Red Hat
> SCM-Revision: 1772
> Build-Jdk: 1.6.0_16
> Bundle-Version: 3.1.5.GA
> Bnd-LastModified: 1255345463119
> Bundle-ManifestVersion: 2
> Bundle-Activator: org.jboss.netty.container.osgi.NettyBundleActivator
> Bundle-License: http://www.apache.org/licenses/LICENSE-2.0
> Bundle-Description: The Netty project is an effort to provide an async
> hronous event-driven network application framework and tools for r
> apid development of maintainable high performance and high scalabi
> lity protocol servers and clients. In other words, Netty is a NIO
> client server framework which enables quick and easy development
> of network applications such as protocol servers and clients. It g
> reatly simplifies and streamlines network programming such as TCP
> and UDP socket server.
> Bundle-DocURL: http://www.jboss.org/netty/
> Bundle-SymbolicName: org.jboss.netty
> Import-Package: com.google.inject;resolution:=optional,com.google.inje
> ct.binder;resolution:=optional,com.google.protobuf;resolution:=option
> al,javax.net.ssl;resolution:=optional,javax.servlet;resolution:=optio
> nal,javax.servlet.http;resolution:=optional,org.apache.commons.loggin
> g;resolution:=optional,org.apache.log4j;resolution:=optional,org.jbos
> s.logging;resolution:=optional,org.jboss.netty.bootstrap;resolution:=
> optional;version="3.1",org.jboss.netty.buffer;resolution:=optional;ve
> rsion="3.1",org.jboss.netty.channel;resolution:=optional;version="3.1
> ",org.jboss.netty.channel.group;resolution:=optional;version="3.1",or
> g.jboss.netty.channel.local;resolution:=optional;version="3.1",org.jb
> oss.netty.channel.socket;resolution:=optional;version="3.1",org.jboss
> .netty.channel.socket.http;resolution:=optional;version="3.1",org.jbo
> ss.netty.channel.socket.nio;resolution:=optional;version="3.1",org.jb
> oss.netty.channel.socket.oio;resolution:=optional;version="3.1",org.j
> boss.netty.channel.xnio;resolution:=optional;version="3.1",org.jboss.
> netty.container.guice;resolution:=optional;version="3.1",org.jboss.ne
> tty.container.microcontainer;resolution:=optional;version="3.1",org.j
> boss.netty.container.osgi;resolution:=optional;version="3.1",org.jbos
> s.netty.container.spring;resolution:=optional;version="3.1",org.jboss
> .netty.handler.codec.base64;resolution:=optional;version="3.1",org.jb
> oss.netty.handler.codec.embedder;resolution:=optional;version="3.1",o
> rg.jboss.netty.handler.codec.frame;resolution:=optional;version="3.1"
> ,org.jboss.netty.handler.codec.http;resolution:=optional;version="3.1
> ",org.jboss.netty.handler.codec.oneone;resolution:=optional;version="
> 3.1",org.jboss.netty.handler.codec.protobuf;resolution:=optional;vers
> ion="3.1",org.jboss.netty.handler.codec.replay;resolution:=optional;v
> ersion="3.1",org.jboss.netty.handler.codec.serialization;resolution:=
> optional;version="3.1",org.jboss.netty.handler.codec.string;resolutio
> n:=optional;version="3.1",org.jboss.netty.handler.execution;resolutio
> n:=optional;version="3.1",org.jboss.netty.handler.logging;resolution:
> =optional;version="3.1",org.jboss.netty.handler.ssl;resolution:=optio
> nal;version="3.1",org.jboss.netty.handler.stream;resolution:=optional
> ;version="3.1",org.jboss.netty.handler.timeout;resolution:=optional;v
> ersion="3.1",org.jboss.netty.logging;resolution:=optional;version="3.
> 1",org.jboss.netty.util;resolution:=optional;version="3.1",org.jboss.
> xnio;resolution:=optional,org.jboss.xnio.channels;resolution:=optiona
> l,org.osgi.framework;resolution:=optional;version="1.4",org.osgi.serv
> ice.log;resolution:=optional;version="1.3",org.osgi.util.tracker;reso
> lution:=optional;version="1.3",org.slf4j;resolution:=optional;version
> ="1.5",org.springframework.beans.factory;resolution:=optional
> {code}
>
> But if I execute
> karaf@root> install -s mvn:org.jboss.netty/netty/3.1.5.GA
> Bundle ID: 119
> karaf@root> list | grep -i netty
> [ 119] [Active ] [ ] [ ] [ 60] The Netty Project
> (3.1.5.GA)
>
> it looks like the bundle is installed.
>
> Can anybody explain this?
>
> Christian
>
> --
> View this message in context: http://servicemix.396122.n5.nabble.com/problem-by-installing-a-custom-jboss-netty-feature-in-SMX-4-2-tp3374147p3374639.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem by installing a custom jboss-netty feature in SMX 4.2
Posted by Christian Mueller <ch...@gmail.com>.
I tried to install it on FUSE ESB 4.3.0-fuse-03-00 and got a better error
message:
karaf@root> features:install netty
Error executing command: Manifest not present in the first entry of the zip
and the following stack trace in the servocemix.log file:
{code}
18:31:31,282 | TRACE | l Console Thread | Connection |
.pax.url.mvn.internal.Connection 181 | 1 - org.ops4j.pax.url.mvn - 1.2.1 |
Downloading [Version [3.1.5.GA] from URL
[file:/Users/cmueller/.m2/repository/org/jboss/netty/netty/3.1.5.GA/netty-3.1.5.GA.jar]]
18:31:31,283 | INFO | l Console Thread | Console |
araf.shell.console.jline.Console 199 | 12 - org.apache.karaf.shell.console
- 2.0.0.fuse-02-00 | Exception caught while executing command
org.osgi.framework.BundleException: Manifest not present in the first entry
of the zip
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installBundleIfNeeded(FeaturesServiceImpl.java:564)[21:org.apache.karaf.features.core:2.0.0.fuse-02-00]
at
org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:404)[21:org.apache.karaf.features.core:2.0.0.fuse-02-00]
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:249)[21:org.apache.karaf.features.core:2.0.0.fuse-02-00]
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:238)[21:org.apache.karaf.features.core:2.0.0.fuse-02-00]
at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:234)[21:org.apache.karaf.features.core:2.0.0.fuse-02-00]
at
org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:51)[11:org.apache.karaf.features.command:2.0.0.fuse-02-00]
at
org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)[11:org.apache.karaf.features.command:2.0.0.fuse-02-00]
at
org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:41)[12:org.apache.karaf.shell.console:2.0.0.fuse-02-00]
at
org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[12:org.apache.karaf.shell.console:2.0.0.fuse-02-00]
at
org.apache.felix.gogo.runtime.shell.CommandProxy.execute(CommandProxy.java:50)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:229)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.executeStatement(Closure.java:162)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Pipe.run(Pipe.java:101)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:79)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.CommandSessionImpl.execute(CommandSessionImpl.java:71)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.karaf.shell.console.jline.Console.run(Console.java:181)[12:org.apache.karaf.shell.console:2.0.0.fuse-02-00]
at java.lang.Thread.run(Thread.java:680)[:1.6.0_22]
{code}
The manifest file is the following:
{code:title=MANIFEST:MF}
Manifest-Version: 1.0
Export-Package: org.jboss.netty.container.microcontainer;uses:="org.jb
oss.netty.logging";version="3.1.5.GA",org.jboss.netty.channel.xnio;us
es:="org.jboss.netty.buffer,org.jboss.xnio,org.jboss.netty.channel,or
g.jboss.xnio.channels,org.jboss.netty.logging";version="3.1.5.GA",org
.jboss.netty.handler.codec.serialization;uses:="org.jboss.netty.buffe
r,org.jboss.netty.handler.codec.replay,org.jboss.netty.channel,org.jb
oss.netty.handler.codec.oneone,org.jboss.netty.handler.codec.frame";v
ersion="3.1.5.GA",org.jboss.netty.handler.codec.protobuf;uses:="org.j
boss.netty.buffer,org.jboss.netty.channel,org.jboss.netty.handler.cod
ec.oneone,com.google.protobuf";version="3.1.5.GA",org.jboss.netty.con
tainer.guice;uses:="com.google.inject,org.jboss.netty.channel.socket.
oio,org.jboss.netty.channel.socket,org.jboss.netty.channel.local,com.
google.inject.binder,org.jboss.netty.channel.socket.nio";version="3.1
.5.GA",org.jboss.netty.util;uses:="org.jboss.netty.buffer,org.jboss.n
etty.channel,org.jboss.netty.logging";version="3.1.5.GA",org.jboss.ne
tty.channel.socket.http;uses:="org.jboss.netty.channel,org.jboss.nett
y.channel.socket,org.jboss.netty.handler.codec.http,javax.net.ssl,org
.jboss.netty.handler.ssl,org.jboss.netty.buffer,org.jboss.netty.loggi
ng,javax.servlet,org.jboss.netty.channel.local,javax.servlet.http";ve
rsion="3.1.5.GA",org.jboss.netty.channel.group;uses:="org.jboss.netty
.channel,org.jboss.netty.buffer,org.jboss.netty.logging";version="3.1
.5.GA",org.jboss.netty.handler.codec.embedder;uses:="org.jboss.netty.
channel,org.jboss.netty.buffer";version="3.1.5.GA",org.jboss.netty.ch
annel.socket.oio;uses:="org.jboss.netty.channel,org.jboss.netty.chann
el.socket,org.jboss.netty.util,org.jboss.netty.buffer,org.jboss.netty
.logging";version="3.1.5.GA",org.jboss.netty.handler.execution;uses:=
"org.jboss.netty.channel,org.jboss.netty.util,org.jboss.netty.logging
";version="3.1.5.GA",org.jboss.netty.handler.codec.frame;uses:="org.j
boss.netty.buffer,org.jboss.netty.channel,org.jboss.netty.handler.cod
ec.oneone";version="3.1.5.GA",org.jboss.netty.channel.local;uses:="or
g.jboss.netty.channel,org.jboss.netty.logging";version="3.1.5.GA",org
.jboss.netty.handler.codec.oneone;uses:="org.jboss.netty.channel";ver
sion="3.1.5.GA",org.jboss.netty.container.osgi;uses:="org.jboss.netty
.logging,org.jboss.netty.channel.socket.oio,org.jboss.netty.channel.s
ocket,org.jboss.netty.channel,org.jboss.netty.channel.local,org.osgi.
framework,org.jboss.netty.channel.socket.nio";version="3.1.5.GA",org.
jboss.netty.bootstrap;uses:="org.jboss.netty.channel,org.jboss.netty.
util";version="3.1.5.GA",org.jboss.netty.logging;uses:="org.apache.co
mmons.logging,org.jboss.logging,org.apache.log4j,org.osgi.service.log
,org.osgi.util.tracker,org.osgi.framework,org.slf4j";version="3.1.5.G
A",org.jboss.netty.buffer;version="3.1.5.GA",org.jboss.netty.handler.
codec.base64;uses:="org.jboss.netty.buffer,org.jboss.netty.channel,or
g.jboss.netty.handler.codec.oneone";version="3.1.5.GA",org.jboss.nett
y.handler.timeout;uses:="org.jboss.netty.channel,org.jboss.netty.util
";version="3.1.5.GA",org.jboss.netty.handler.codec.http;uses:="org.jb
oss.netty.buffer,org.jboss.netty.handler.codec.frame,org.jboss.netty.
channel,org.jboss.netty.handler.codec.replay,org.jboss.netty.handler.
codec.oneone";version="3.1.5.GA",org.jboss.netty.channel.socket.nio;u
ses:="org.jboss.netty.logging,org.jboss.netty.channel.socket,org.jbos
s.netty.channel,org.jboss.netty.util,org.jboss.netty.buffer";version=
"3.1.5.GA",org.jboss.netty.channel.socket;uses:="org.jboss.netty.chan
nel";version="3.1.5.GA",org.jboss.netty.handler.codec.replay;uses:="o
rg.jboss.netty.buffer,org.jboss.netty.channel";version="3.1.5.GA",org
.jboss.netty.handler.codec.string;uses:="org.jboss.netty.buffer,org.j
boss.netty.channel,org.jboss.netty.handler.codec.oneone";version="3.1
.5.GA",org.jboss.netty.channel;uses:="org.jboss.netty.buffer,org.jbos
s.netty.util,org.jboss.netty.logging";version="3.1.5.GA",org.jboss.ne
tty.handler.logging;uses:="org.jboss.netty.logging,org.jboss.netty.bu
ffer,org.jboss.netty.channel";version="3.1.5.GA",org.jboss.netty.hand
ler.stream;uses:="org.jboss.netty.buffer,org.jboss.netty.channel,org.
jboss.netty.logging";version="3.1.5.GA",org.jboss.netty.container.spr
ing;uses:="org.jboss.netty.logging,org.springframework.beans.factory"
;version="3.1.5.GA",org.jboss.netty.handler.ssl;uses:="org.jboss.nett
y.channel,javax.net.ssl,org.jboss.netty.logging,org.jboss.netty.buffe
r,org.jboss.netty.handler.codec.frame";version="3.1.5.GA"
Private-Package: org.jboss.netty.example.http.snoop,org.jboss.netty.ex
ample.securechat,org.jboss.netty.example.http.file,org.jboss.netty.ex
ample.factorial,org.jboss.netty.example.http.tunnel,org.jboss.netty.e
xample.uptime,org.jboss.netty.example.proxy,org.jboss.netty.example.t
elnet,org.jboss.netty.example.objectecho,org.jboss.netty.example.echo
,org.jboss.netty.example.localtime,org.jboss.netty.example.discard,or
g.jboss.netty.example.qotm,org.jboss.netty.util.internal,org.jboss.ne
tty.example.local
Built-By: trustin
Tool: Bnd-0.0.311
Bundle-Name: The Netty Project
Created-By: Apache Maven Bundle Plugin
Bundle-Vendor: JBoss, by Red Hat
SCM-Revision: 1772
Build-Jdk: 1.6.0_16
Bundle-Version: 3.1.5.GA
Bnd-LastModified: 1255345463119
Bundle-ManifestVersion: 2
Bundle-Activator: org.jboss.netty.container.osgi.NettyBundleActivator
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0
Bundle-Description: The Netty project is an effort to provide an async
hronous event-driven network application framework and tools for r
apid development of maintainable high performance and high scalabi
lity protocol servers and clients. In other words, Netty is a NIO
client server framework which enables quick and easy development
of network applications such as protocol servers and clients. It g
reatly simplifies and streamlines network programming such as TCP
and UDP socket server.
Bundle-DocURL: http://www.jboss.org/netty/
Bundle-SymbolicName: org.jboss.netty
Import-Package: com.google.inject;resolution:=optional,com.google.inje
ct.binder;resolution:=optional,com.google.protobuf;resolution:=option
al,javax.net.ssl;resolution:=optional,javax.servlet;resolution:=optio
nal,javax.servlet.http;resolution:=optional,org.apache.commons.loggin
g;resolution:=optional,org.apache.log4j;resolution:=optional,org.jbos
s.logging;resolution:=optional,org.jboss.netty.bootstrap;resolution:=
optional;version="3.1",org.jboss.netty.buffer;resolution:=optional;ve
rsion="3.1",org.jboss.netty.channel;resolution:=optional;version="3.1
",org.jboss.netty.channel.group;resolution:=optional;version="3.1",or
g.jboss.netty.channel.local;resolution:=optional;version="3.1",org.jb
oss.netty.channel.socket;resolution:=optional;version="3.1",org.jboss
.netty.channel.socket.http;resolution:=optional;version="3.1",org.jbo
ss.netty.channel.socket.nio;resolution:=optional;version="3.1",org.jb
oss.netty.channel.socket.oio;resolution:=optional;version="3.1",org.j
boss.netty.channel.xnio;resolution:=optional;version="3.1",org.jboss.
netty.container.guice;resolution:=optional;version="3.1",org.jboss.ne
tty.container.microcontainer;resolution:=optional;version="3.1",org.j
boss.netty.container.osgi;resolution:=optional;version="3.1",org.jbos
s.netty.container.spring;resolution:=optional;version="3.1",org.jboss
.netty.handler.codec.base64;resolution:=optional;version="3.1",org.jb
oss.netty.handler.codec.embedder;resolution:=optional;version="3.1",o
rg.jboss.netty.handler.codec.frame;resolution:=optional;version="3.1"
,org.jboss.netty.handler.codec.http;resolution:=optional;version="3.1
",org.jboss.netty.handler.codec.oneone;resolution:=optional;version="
3.1",org.jboss.netty.handler.codec.protobuf;resolution:=optional;vers
ion="3.1",org.jboss.netty.handler.codec.replay;resolution:=optional;v
ersion="3.1",org.jboss.netty.handler.codec.serialization;resolution:=
optional;version="3.1",org.jboss.netty.handler.codec.string;resolutio
n:=optional;version="3.1",org.jboss.netty.handler.execution;resolutio
n:=optional;version="3.1",org.jboss.netty.handler.logging;resolution:
=optional;version="3.1",org.jboss.netty.handler.ssl;resolution:=optio
nal;version="3.1",org.jboss.netty.handler.stream;resolution:=optional
;version="3.1",org.jboss.netty.handler.timeout;resolution:=optional;v
ersion="3.1",org.jboss.netty.logging;resolution:=optional;version="3.
1",org.jboss.netty.util;resolution:=optional;version="3.1",org.jboss.
xnio;resolution:=optional,org.jboss.xnio.channels;resolution:=optiona
l,org.osgi.framework;resolution:=optional;version="1.4",org.osgi.serv
ice.log;resolution:=optional;version="1.3",org.osgi.util.tracker;reso
lution:=optional;version="1.3",org.slf4j;resolution:=optional;version
="1.5",org.springframework.beans.factory;resolution:=optional
{code}
But if I execute
karaf@root> install -s mvn:org.jboss.netty/netty/3.1.5.GA
Bundle ID: 119
karaf@root> list | grep -i netty
[ 119] [Active ] [ ] [ ] [ 60] The Netty Project
(3.1.5.GA)
it looks like the bundle is installed.
Can anybody explain this?
Christian
--
View this message in context: http://servicemix.396122.n5.nabble.com/problem-by-installing-a-custom-jboss-netty-feature-in-SMX-4-2-tp3374147p3374639.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem by installing a custom jboss-netty feature in SMX 4.2
Posted by Christian Mueller <ch...@gmail.com>.
Hello Gert, hello Andreas!
Thank you verry much for your quick answer, and the logging level hin (which
I should have done without your help).
We configured our own maven repository 'wlsi-maven-repository' inside SMX
with the '@snapshots' suffix. This repository (and only this repository)
contains the netty-3.1.5.GA.jar file (verified). But when SMX tries to
download the file, something goes wrong and nothing is logged...
{code}
14:38:30,766 | DEBUG | l Console Thread | FeaturesServiceImpl |
res.internal.FeaturesServiceImpl 475 | Checking mvn:org.jboss.netty/netty/
3.1.5.GA
14:38:30,766 | DEBUG | l Console Thread | Connection |
.pax.url.mvn.internal.Connection 145 | Resolving
[mvn:org.jboss.netty/netty/3.1.5.GA]
14:38:30,766 | DEBUG | l Console Thread | Connection |
.pax.url.mvn.internal.Connection 260 | Collecting versions from repository
[file:D:/Programme/progress/apache-servicemix-4.2.0-fuse-02-00/system/,releases=true,snapshots=true]
14:38:30,766 | DEBUG | l Console Thread | Connection |
.pax.url.mvn.internal.Connection 378 | Resolving exact version
14:38:30,766 | DEBUG | l Console Thread | Connection |
.pax.url.mvn.internal.Connection 260 | Collecting versions from repository
[file:D:/Programme/progress/apache-servicemix-4.2.0-fuse-02-00/wlsi-maven-repository/,releases=true,snapshots=true]
14:38:30,766 | DEBUG | l Console Thread | Connection |
.pax.url.mvn.internal.Connection 378 | Resolving exact version
14:38:30,766 | TRACE | l Console Thread | Connection |
.pax.url.mvn.internal.Connection 149 | Possible default download locations
for [mvn:org.jboss.netty/netty/3.1.5.GA]
14:38:30,766 | TRACE | l Console Thread | Connection |
.pax.url.mvn.internal.Connection 152 | Version [3.1.5.GA] from URL
[file:D:/Programme/progress/apache-servicemix-4.2.0-fuse-02-00/system/org/jboss/netty/netty/
3.1.5.GA/netty-3.1.5.GA.jar]
14:38:30,766 | TRACE | l Console Thread | Connection |
.pax.url.mvn.internal.Connection 152 | Version [3.1.5.GA] from URL
[file:D:/Programme/progress/apache-servicemix-4.2.0-fuse-02-00/wlsi-maven-repository/org/jboss/netty/netty/
3.1.5.GA/netty-3.1.5.GA.jar]
14:38:30,766 | TRACE | l Console Thread | Connection |
.pax.url.mvn.internal.Connection 157 | Downloading [Version [3.1.5.GA] from
URL
[file:D:/Programme/progress/apache-servicemix-4.2.0-fuse-02-00/system/org/jboss/netty/netty/
3.1.5.GA/netty-3.1.5.GA.jar]]
14:38:30,766 | DEBUG | l Console Thread | Connection |
.pax.url.mvn.internal.Connection 166 | Could not download [Version [
3.1.5.GA] from URL
[file:D:/Programme/progress/apache-servicemix-4.2.0-fuse-02-00/system/org/jboss/netty/netty/
3.1.5.GA/netty-3.1.5.GA.jar]]
14:38:30,766 | TRACE | l Console Thread | Connection |
.pax.url.mvn.internal.Connection 167 | Reason
[java.io.FileNotFoundException:
D:\Programme\progress\apache-servicemix-4.2.0-fuse-02-00\system\org\jboss\netty\netty\
3.1.5.GA\netty-3.1.5.GA.jar (Das System kann den angegebenen Pfad nicht
finden)]
14:38:30,766 | TRACE | l Console Thread | Connection |
.pax.url.mvn.internal.Connection 157 | Downloading [Version [3.1.5.GA] from
URL
[file:D:/Programme/progress/apache-servicemix-4.2.0-fuse-02-00/wlsi-maven-repository/org/jboss/netty/netty/
3.1.5.GA/netty-3.1.5.GA.jar]]
{code}
Cheers,
Christian
--
View this message in context: http://servicemix.396122.n5.nabble.com/problem-by-installing-a-custom-jboss-netty-feature-in-SMX-4-2-tp3374147p3374256.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem by installing a custom jboss-netty feature in SMX 4.2
Posted by Andreas Pieber <an...@gmail.com>.
Another thing which might go wrong is if you create a new feature file and do
not add it (features:addurls)? In addition, if you simply restart things are
cached; it's possible that you have to refresh the feature file
(features:refresh)
kind regards,
andreas
On Mon, Feb 07, 2011 at 04:13:54AM -0800, Christian Mueller wrote:
>
> Hello List!
>
> We are using FUSE ESB 4.2.0-fuse-02-00 and providing our own features (based
> on our use cases). We have a problem with one of our feature definitions.
> If we run a
> osgi:install -s mvn:org.jboss.netty/netty/3.1.5.GA
>
> everything works well.
> If we create a feature which includes this bundle like the following
> <feature name="netty" version="1.1.0">
> <bundle>mvn:org.jboss.netty/netty/3.1.5.GA</bundle>
> </feature>
>
> and we run a
> features:install netty
>
> Nothing happens. On the console, we get the following result:
> features:install netty
> null
>
> Nothing in the log file.
> Does anybody have also seen this issue? Any ideas why this is happening?
>
> Thanks in advance,
> Christian
> --
> View this message in context: http://servicemix.396122.n5.nabble.com/problem-by-installing-a-custom-jboss-netty-feature-in-SMX-4-2-tp3374147p3374147.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem by installing a custom jboss-netty feature in SMX 4.2
Posted by Gert Vanthienen <ge...@gmail.com>.
Christian,
The only real, relevant difference I see between the osgi:install and
the features:install would be that the features:install would try to
refresh other bundles that have an optional import for netty in order
to get those imports wired. Could you try using a 'features:install
-r netty' (no auto refresh) to check if that is really the problem
here.
If it is, you could try running a 'features:install -c netty' (don't
clean up after failure) after setting the log level to DEBUG or TRACE
to figure out what the problem bundles are. Also, you might want to
try switching to felix in etc/config.properties to see if Felix
manages to give you a more precise error message in this case.
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Mon, Feb 7, 2011 at 1:13 PM, Christian Mueller
<ch...@gmail.com> wrote:
>
> Hello List!
>
> We are using FUSE ESB 4.2.0-fuse-02-00 and providing our own features (based
> on our use cases). We have a problem with one of our feature definitions.
> If we run a
> osgi:install -s mvn:org.jboss.netty/netty/3.1.5.GA
>
> everything works well.
> If we create a feature which includes this bundle like the following
> <feature name="netty" version="1.1.0">
> <bundle>mvn:org.jboss.netty/netty/3.1.5.GA</bundle>
> </feature>
>
> and we run a
> features:install netty
>
> Nothing happens. On the console, we get the following result:
> features:install netty
> null
>
> Nothing in the log file.
> Does anybody have also seen this issue? Any ideas why this is happening?
>
> Thanks in advance,
> Christian
> --
> View this message in context: http://servicemix.396122.n5.nabble.com/problem-by-installing-a-custom-jboss-netty-feature-in-SMX-4-2-tp3374147p3374147.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>