# Running ES as a OSGi bundle **URL:** \ **Category:** Elasticsearch\ **Created:** [May 9, 2011, 9:46am UTC](https://discuss.elastic.co/t/running-es-as-a-osgi-bundle/4372 "2011-05-09T09:46:50Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![shruthi](https://avatars.discourse-cdn.com/v4/letter/s/7ab992/32.png) [@shruthi](https://discuss.elastic.co/u/shruthi)\ **Post date:** [May 9, 2011, 9:46am UTC](https://discuss.elastic.co/t/running-es-as-a-osgi-bundle/4372/1 "2011-05-09T09:46:50Z")
Hello, I am building an application on the OSGi platform and intending to use ES for indexing and searching. My requirement is to make ES available as a bundle and make it run on OSGi runtime along with my other bundles. Any idea how I could go about achieving this? Thanks! Shruthi ---
**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\ **Post date:** [May 9, 2011, 6:13pm UTC](https://discuss.elastic.co/t/running-es-as-a-osgi-bundle/4372/2 "2011-05-09T18:13:13Z")
Hello, ``` As elasticsearch jar already bundles most of it's dependencies (look ``` at org.elasticsearch.common package) I think it's just a matter of using felix's maven-bundle-plugin and exporting org.elasticsearch.\*. Cheers On Mon, May 9, 2011 at 06:46, shruthi [shruthiarjun@gmail.com](mailto:shruthiarjun@gmail.com) wrote: > Hello, > I am building an application on the OSGi platform and intending to use > ES for indexing and searching. My requirement is to make ES available > as a bundle and make it run on OSGi runtime along with my other > bundles. Any idea how I could go about achieving this? > Thanks! > Shruthi ---
**Author:** ![ildella](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ildella/32/3219_2.png) [@ildella](https://discuss.elastic.co/u/ildella)\ **Post date:** [May 28, 2011, 9:58am UTC](https://discuss.elastic.co/t/running-es-as-a-osgi-bundle/4372/3 "2011-05-28T09:58:04Z")
I'm trying to do the same using bnd to wrap lucene and the elasticsearch jars as osgi bundles. There's one issue: elasticsearch has some org.apache.lucene packages that's overlap with the same packages exported by lucene itself. This is bad in osgi. A quick solution is just not to export, from ES, those packages, that will become not available to other bundle. Maybe they're not intented to be exported so that is good. It they're intented to be used outside ES, so the only solution is to change the name of the package in a way that it bocome unique. ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [May 31, 2011, 11:09pm UTC](https://discuss.elastic.co/t/running-es-as-a-osgi-bundle/4372/4 "2011-05-31T23:09:39Z")
You don't need to expose those classes from the osgi bundle. They are only there because some methods in Lucene are package protected. On Saturday, May 28, 2011 at 12:58 PM, ildella wrote: > I'm trying to do the same using bnd to wrap lucene and the elasticsearch jars > as osgi bundles. > There's one issue: elasticsearch has some org.apache.lucene packages that's > overlap with the same packages exported by lucene itself. This is bad in > osgi. > > A quick solution is just not to export, from ES, those packages, that will > become not available to other bundle. Maybe they're not intented to be > exported so that is good. > > It they're intented to be used outside ES, so the only solution is to change > the name of the package in a way that it bocome unique. > > -- > View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/Running-ES-as-a-OSGi-bundle-tp2918132p2995769.html](http://elasticsearch-users.115913.n3.nabble.com/Running-ES-as-a-OSGi-bundle-tp2918132p2995769.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com) ([http://Nabble.com](http://Nabble.com)). ---
**Author:** ![Wojciech\_Durczynski](https://avatars.discourse-cdn.com/v4/letter/w/fbc32d/32.png) [@Wojciech\_Durczynski](https://discuss.elastic.co/u/Wojciech_Durczynski)\ **Post date:** [June 1, 2011, 7:49am UTC](https://discuss.elastic.co/t/running-es-as-a-osgi-bundle/4372/5 "2011-06-01T07:49:15Z")
You may merge jars from lucene and elasticsearch and create one big bundle elasticsearch\_all. I did it this way and works. On May 28, 11:58 am, ildella [ilde...@gmail.com](mailto:ilde...@gmail.com) wrote: > I'm trying to do the same using bnd to wrap lucene and the elasticsearch jars > as osgi bundles. > There's one issue: elasticsearch has some org.apache.lucene packages that's > overlap with the same packages exported by lucene itself. This is bad in > osgi. > > A quick solution is just not to export, from ES, those packages, that will > become not available to other bundle. Maybe they're not intented to be > exported so that is good. > > It they're intented to be used outside ES, so the only solution is to change > the name of the package in a way that it bocome unique. > > -- > View this message in context:[http://elasticsearch-users.115913.n3.nabble.com/Running-ES-as-a-OSGi-](http://elasticsearch-users.115913.n3.nabble.com/Running-ES-as-a-OSGi-)... > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). ---
**Author:** ![sumitborar](https://avatars.discourse-cdn.com/v4/letter/s/b782af/32.png) [@sumitborar](https://discuss.elastic.co/u/sumitborar)\ **Post date:** [September 5, 2012, 9:20pm UTC](https://discuss.elastic.co/t/running-es-as-a-osgi-bundle/4372/6 "2012-09-05T21:20:08Z")
I was planning to also use ES OSGI bundle for our application. Is there a standard bundle available ? ---
**Author:** ![pmanvi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pmanvi/32/46188_2.png) [@pmanvi](https://discuss.elastic.co/u/pmanvi)\ **Post date:** [July 22, 2013, 12:11pm UTC](https://discuss.elastic.co/t/running-es-as-a-osgi-bundle/4372/7 "2013-07-22T12:11:35Z")
Any updates on this, I see similar questions making elasticsearch OSGI compliant remain open. Currently I have following problems & resorted to some hacks to avoid the same temporarily. Any inputs on correct usage is greatly appreciated. 1. While instantiating the TransportClient it relies on "Names.txt" & is present as part of the jars. It fails to load from classpath in OSGI envioronement. Work around: Currently copying the names.txt in the bundle and specifying the path explicitely. settingsBuilder.put("path.conf", dirPathHavingNamingDotTextFile); 2. As elasticsearch also bundles few lucene classes "org.apache.index", OSGI complains saying it clashes with the classes present in the lucene. Work around: Remove the classes present in one of the jars and rebuild and deploy in the OSGI container. Since elasticsearch configures the compression scheme in TransportClient CompressorFactory.configure(), there is no way to avoid the execution of static bloc of CompressionFactory class. Suggest to make it optional through one more TransportClient constructor Thanks, Praveen ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [July 23, 2013, 6:27am UTC](https://discuss.elastic.co/t/running-es-as-a-osgi-bundle/4372/8 "2013-07-23T06:27:18Z")
Hey, I dont really know anything about OSGI, but you might be able to prevent the first issue by setting the 'node.name' property (which you should do anyway in production), as this prevents the file from being searched... --Alex On Mon, Jul 22, 2013 at 2:11 PM, pmanvi [praveena.manvi@gmail.com](mailto:praveena.manvi@gmail.com) wrote: > Any updates on this, I see similar questions making elasticsearch OSGI > compliant remain open. > > Currently I have following problems & resorted to some hacks to avoid the > same temporarily. Any inputs on correct usage is greatly appreciated. > > 1. While instantiating the TransportClient it relies on "Names.txt" & is > present as part of the jars. It fails to load from classpath in OSGI > envioronement. > Work around: > Currently copying the names.txt in the bundle and specifying the path > explicitely. > settingsBuilder.put("path.conf", dirPathHavingNamingDotTextFile); > > 2. As elasticsearch also bundles few lucene classes "org.apache.index", > OSGI > complains saying it clashes with the classes present in the lucene. > Work around: > Remove the classes present in one of the jars and rebuild and deploy in the > OSGI container. > > Since elasticsearch configures the compression scheme in TransportClient > CompressorFactory.configure(), there is no way to avoid the execution of > static bloc of CompressionFactory class. > Suggest to make it optional through one more TransportClient constructor > > Thanks, > Praveen > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/Running-ES-as-a-OSGi-bundle-tp2918132p4038445.html](http://elasticsearch-users.115913.n3.nabble.com/Running-ES-as-a-OSGi-bundle-tp2918132p4038445.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![costin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/costin/32/44950_2.png) [@costin](https://discuss.elastic.co/u/costin)\ **Post date:** [July 23, 2013, 9:45am UTC](https://discuss.elastic.co/t/running-es-as-a-osgi-bundle/4372/9 "2013-07-23T09:45:01Z")
I assume you're talking just about the Java client in OSGi (I don't see how/why you would use ES with OSGi) and I'm curious what's your use case? Also any information about the OSGi framework that you're using? On 22/07/2013 3:11 PM, pmanvi wrote: > Any updates on this, I see similar questions making elasticsearch OSGI > compliant remain open. > > Currently I have following problems & resorted to some hacks to avoid the > same temporarily. Any inputs on correct usage is greatly appreciated. > > 1. While instantiating the TransportClient it relies on "Names.txt" & is > present as part of the jars. It fails to load from classpath in OSGI > envioronement. > Work around: > Currently copying the names.txt in the bundle and specifying the path > explicitely. > settingsBuilder.put("path.conf", dirPathHavingNamingDotTextFile); What's the exception that you're getting? Accessing resources in OSGi can be tricky since the classpath is not always obvious. ES falls back to loading Names.txt from the Environment class classloader. My guess would be that since config/ is not an exported package, the bundle class loader doesn't allow access to it - try adding config/ to your Export-Package directive and see whether that helps. > 1. As elasticsearch also bundles few lucene classes "org.apache.index", OSGI > complains saying it clashes with the classes present in the lucene. > Work around: > Remove the classes present in one of the jars and rebuild and deploy in the > OSGI container. Is the start-up halted or is it just a warning that you're receiving? Note that it's perfectly fine for a bundle to have 'internal' packages - simply remove "org.apache.index" from your Export-Package (inside the Transport client jar) - thus making the package private - and you should be fine. > Since elasticsearch configures the compression scheme in TransportClient > CompressorFactory.configure(), there is no way to avoid the execution of > static bloc of CompressionFactory class. > Suggest to make it optional through one more TransportClient constructor Why is this a problem? > Thanks, > Praveen > > -- > View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/Running-ES-as-a-OSGi-bundle-tp2918132p4038445.html](http://elasticsearch-users.115913.n3.nabble.com/Running-ES-as-a-OSGi-bundle-tp2918132p4038445.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). -- Costin -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![pmanvi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pmanvi/32/46188_2.png) [@pmanvi](https://discuss.elastic.co/u/pmanvi)\ **Post date:** [July 24, 2013, 11:41am UTC](https://discuss.elastic.co/t/running-es-as-a-osgi-bundle/4372/10 "2013-07-24T11:41:57Z")
Thanks Alex, It works. I did see a thread [config/elasticsearch.yml: add a commented out node.name with docs by avar · Pull Request #1345 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/pull/1345) where it was added in the elasticsearch.yml I could not find any documentation on what''s the value that should be provided and why elasticsearch needs to generate so many names? On Tuesday, July 23, 2013 11:57:18 AM UTC+5:30, Alexander Reelsen wrote: > Hey, > > I dont really know anything about OSGI, but you might be able to prevent > the first issue by setting the 'node.name' property (which you should do > anyway in production), as this prevents the file from being searched... > > --Alex > > On Mon, Jul 22, 2013 at 2:11 PM, pmanvi \<[praveen...@gmail.com](mailto:praveen...@gmail.com)\ > > > wrote: > > > Any updates on this, I see similar questions making elasticsearch OSGI > > compliant remain open. > > > > Currently I have following problems & resorted to some hacks to avoid the > > same temporarily. Any inputs on correct usage is greatly appreciated. > > > > 1. While instantiating the TransportClient it relies on "Names.txt" & is > > present as part of the jars. It fails to load from classpath in OSGI > > envioronement. > > Work around: > > Currently copying the names.txt in the bundle and specifying the path > > explicitely. > > settingsBuilder.put("path.conf", dirPathHavingNamingDotTextFile); > > > > 2. As elasticsearch also bundles few lucene classes "org.apache.index", > > OSGI > > complains saying it clashes with the classes present in the lucene. > > Work around: > > Remove the classes present in one of the jars and rebuild and deploy in > > the > > OSGI container. > > > > Since elasticsearch configures the compression scheme in TransportClient > > CompressorFactory.configure(), there is no way to avoid the execution of > > static bloc of CompressionFactory class. > > Suggest to make it optional through one more TransportClient constructor > > > > Thanks, > > Praveen > > > > -- > > View this message in context: > > [http://elasticsearch-users.115913.n3.nabble.com/Running-ES-as-a-OSGi-bundle-tp2918132p4038445.html](http://elasticsearch-users.115913.n3.nabble.com/Running-ES-as-a-OSGi-bundle-tp2918132p4038445.html) > > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![pmanvi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pmanvi/32/46188_2.png) [@pmanvi](https://discuss.elastic.co/u/pmanvi)\ **Post date:** [July 24, 2013, 11:52am UTC](https://discuss.elastic.co/t/running-es-as-a-osgi-bundle/4372/11 "2013-07-24T11:52:55Z")
On Tuesday, July 23, 2013 3:15:01 PM UTC+5:30, Costin Leau wrote: > I assume you're talking just about the Java client in OSGi (I don't see > how/why you would use ES with OSGi) and I'm > curious what's your use case? > Also any information about the OSGi framework that you're using? > > On 22/07/2013 3:11 PM, pmanvi wrote: > > > Any updates on this, I see similar questions making elasticsearch OSGI > > compliant remain open. > > > > Currently I have following problems & resorted to some hacks to avoid > > the > > same temporarily. Any inputs on correct usage is greatly appreciated. > > > > 1. While instantiating the TransportClient it relies on "Names.txt" & is > > present as part of the jars. It fails to load from classpath in OSGI > > envioronement. > > Work around: > > Currently copying the names.txt in the bundle and specifying the path > > explicitely. > > settingsBuilder.put("path.conf", dirPathHavingNamingDotTextFile); > > What's the exception that you're getting? > > Accessing resources in OSGi can be tricky since the classpath is not > always obvious. ES falls back to loading Names.txt > from the Environment class classloader. > My guess would be that since config/ is not an exported package, the > bundle class loader doesn't allow access to it - > try adding config/ to your Export-Package directive and see whether that > helps. Thanks. It was generic TransportSerializationException. I am not finding the exception messages not that really useful, It always says stream corrupted (for invalid schema, fields etc. forcing me to include try {} catch bloc on each of the statement calls to get the context while throwing the exception back. As suggested in the other thread the problem got solved by un-commenting the line "node.name" in the elasticsearch.yml. But I am not sure what I am losing by doing this. > > 1. As elasticsearch also bundles few lucene classes "org.apache.index", > > OSGI > > complains saying it clashes with the classes present in the lucene. > > Work around: > > Remove the classes present in one of the jars and rebuild and deploy in > > the > > OSGI container. > > Is the start-up halted or is it just a warning that you're receiving? Note > that it's perfectly fine for a bundle to have > 'internal' packages - simply remove "org.apache.index" from your > Export-Package (inside the Transport client jar) - thus > making the package private - and you should be fine. It was getting halted. Since we were running in fuse, we don;t have copied the elastic jar as is without adding OSGI symantics. Will try out defining OSGI entries for POM and try commenting out the package as suggested. Thanks. > > Since elasticsearch configures the compression scheme in TransportClient > > CompressorFactory.configure(), there is no way to avoid the execution of > > static bloc of CompressionFactory class. > > Suggest to make it optional through one more TransportClient constructor > > Why is this a problem? Since we are using this client library (from fuse container), It un-necessarly initializes the compressor (JNI call?), it can be done lazily once the compressor is being called.There is no issue as such. > > Thanks, > > Praveen > > > > -- > > View this message in context: > > [http://elasticsearch-users.115913.n3.nabble.com/Running-ES-as-a-OSGi-bundle-tp2918132p4038445.html](http://elasticsearch-users.115913.n3.nabble.com/Running-ES-as-a-OSGi-bundle-tp2918132p4038445.html) > > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > -- > Costin -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![pmanvi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pmanvi/32/46188_2.png) [@pmanvi](https://discuss.elastic.co/u/pmanvi)\ **Post date:** [July 24, 2013, 12:07pm UTC](https://discuss.elastic.co/t/running-es-as-a-osgi-bundle/4372/12 "2013-07-24T12:07:21Z")
On Tuesday, July 23, 2013 3:15:01 PM UTC+5:30, Costin Leau wrote: > I assume you're talking just about the Java client in OSGi (I don't see > how/why you would use ES with OSGi) and I'm > curious what's your use case? > Also any information about the OSGi framework that you're using? Yes elasticsearch is used its client library. Not sure if there is striped down version exist, something like elasticsearch-client.jar we are using jboss fuse. > On 22/07/2013 3:11 PM, pmanvi wrote: > > > Any updates on this, I see similar questions making elasticsearch OSGI > > compliant remain open. > > > > Currently I have following problems & resorted to some hacks to avoid > > the > > same temporarily. Any inputs on correct usage is greatly appreciated. > > > > 1. While instantiating the TransportClient it relies on "Names.txt" & is > > present as part of the jars. It fails to load from classpath in OSGI > > envioronement. > > Work around: > > Currently copying the names.txt in the bundle and specifying the path > > explicitely. > > settingsBuilder.put("path.conf", dirPathHavingNamingDotTextFile); > > What's the exception that you're getting? > > Accessing resources in OSGi can be tricky since the classpath is not > always obvious. ES falls back to loading Names.txt > from the Environment class classloader. > My guess would be that since config/ is not an exported package, the > bundle class loader doesn't allow access to it - > try adding config/ to your Export-Package directive and see whether that > helps. > > > 1. As elasticsearch also bundles few lucene classes "org.apache.index", > > OSGI > > complains saying it clashes with the classes present in the lucene. > > Work around: > > Remove the classes present in one of the jars and rebuild and deploy in > > the > > OSGI container. > > Is the start-up halted or is it just a warning that you're receiving? Note > that it's perfectly fine for a bundle to have > 'internal' packages - simply remove "org.apache.index" from your > Export-Package (inside the Transport client jar) - thus > making the package private - and you should be fine. > > > Since elasticsearch configures the compression scheme in TransportClient > > CompressorFactory.configure(), there is no way to avoid the execution of > > static bloc of CompressionFactory class. > > Suggest to make it optional through one more TransportClient constructor > > Why is this a problem? > > > Thanks, > > Praveen > > > > -- > > View this message in context: > > [http://elasticsearch-users.115913.n3.nabble.com/Running-ES-as-a-OSGi-bundle-tp2918132p4038445.html](http://elasticsearch-users.115913.n3.nabble.com/Running-ES-as-a-OSGi-bundle-tp2918132p4038445.html) > > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > -- > Costin -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:24am UTC](https://discuss.elastic.co/t/running-es-as-a-osgi-bundle/4372/13 "2017-07-06T02:24:44Z")