# Deploying ElasticSearch 1.3 to Wildfly 8.1 **URL:** \ **Category:** Elasticsearch\ **Created:** [July 25, 2014, 1:30am UTC](https://discuss.elastic.co/t/deploying-elasticsearch-1-3-to-wildfly-8-1/18886 "2014-07-25T01:30:58Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![John\_D\_Ament](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_d_ament/32/764_2.png) [@John\_D\_Ament](https://discuss.elastic.co/u/John_D_Ament)\ **Post date:** [July 25, 2014, 1:30am UTC](https://discuss.elastic.co/t/deploying-elasticsearch-1-3-to-wildfly-8-1/18886/1 "2014-07-25T01:30:58Z")
Hi all I was tinkering a bit with ElasticSearch. I think my target runtime may end up being embedded, just based on our deployment model. Probably not a big deal to get multiple nodes talking to each other and no additional hardware to deploy. I was trying to start the application in WildFly 8.1. When I go to deploy, I get errors related to ASM. It turns out that ES 1.3 ships w/ ASM 4.1. WildFly uses ASM 3.3.1. Is it possible to run ES against this version of ASM? It would seem that the two versions not compatible. If there's an alternative to running it on WF 8.1, I would love to hear it. Thanks, John -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [July 25, 2014, 7:02am UTC](https://discuss.elastic.co/t/deploying-elasticsearch-1-3-to-wildfly-8-1/18886/2 "2014-07-25T07:02:57Z")
You have two choices: - drop ASM and MVEL, switch to Groovy for scripting - use TransportClient to avoid ES-cluster-side services like scripting in Wildfly deployment (this is how I do it currently) Jörg On Fri, Jul 25, 2014 at 3:30 AM, John D. Ament [john.d.ament@gmail.com](mailto:john.d.ament@gmail.com) wrote: > Hi all > > I was tinkering a bit with Elasticsearch. I think my target runtime may > end up being embedded, just based on our deployment model. Probably not a > big deal to get multiple nodes talking to each other and no additional > hardware to deploy. > > I was trying to start the application in WildFly 8.1. When I go to > deploy, I get errors related to ASM. It turns out that ES 1.3 ships w/ ASM > 4.1. WildFly uses ASM 3.3.1. Is it possible to run ES against this > version of ASM? It would seem that the two versions not compatible. > > If there's an alternative to running it on WF 8.1, I would love to hear it. > > Thanks, > > John > > -- > 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). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEojjJwhaBqvGOTErptw10%2BN8TX0fhenUam%2Bq1U9859cw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEojjJwhaBqvGOTErptw10%2BN8TX0fhenUam%2Bq1U9859cw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [July 25, 2014, 7:06am UTC](https://discuss.elastic.co/t/deploying-elasticsearch-1-3-to-wildfly-8-1/18886/3 "2014-07-25T07:06:04Z")
As a side note, I run Wildfly 8.1 on Java 8. ASM 3 does not work with Java 8, so I wonder how things can work out at all, even without ES. If possible, ASM 3 should be replaced by ASM 5.0 Jörg On Fri, Jul 25, 2014 at 9:02 AM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \< [joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote: > You have two choices: > > - drop ASM and MVEL, switch to Groovy for scripting > > - use TransportClient to avoid ES-cluster-side services like scripting in > Wildfly deployment (this is how I do it currently) > > Jörg > > On Fri, Jul 25, 2014 at 3:30 AM, John D. Ament [john.d.ament@gmail.com](mailto:john.d.ament@gmail.com) > wrote: > > > Hi all > > > > I was tinkering a bit with Elasticsearch. I think my target runtime may > > end up being embedded, just based on our deployment model. Probably not a > > big deal to get multiple nodes talking to each other and no additional > > hardware to deploy. > > > > I was trying to start the application in WildFly 8.1. When I go to > > deploy, I get errors related to ASM. It turns out that ES 1.3 ships w/ ASM > > 4.1. WildFly uses ASM 3.3.1. Is it possible to run ES against this > > version of ASM? It would seem that the two versions not compatible. > > > > If there's an alternative to running it on WF 8.1, I would love to hear > > it. > > > > Thanks, > > > > John > > > > -- > > 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). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEWDqkMDNHBqk4EGLftX7w-ftqOkUOtVOodnWnrkfEyjw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEWDqkMDNHBqk4EGLftX7w-ftqOkUOtVOodnWnrkfEyjw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![John\_D\_Ament](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_d_ament/32/764_2.png) [@John\_D\_Ament](https://discuss.elastic.co/u/John_D_Ament)\ **Post date:** [July 26, 2014, 1:44am UTC](https://discuss.elastic.co/t/deploying-elasticsearch-1-3-to-wildfly-8-1/18886/4 "2014-07-26T01:44:25Z")
I can try upgrading ASM locally to see if it works. I'm assuming it's backwards compatible? On Friday, July 25, 2014 3:06:13 AM UTC-4, Jörg Prante wrote: > As a side note, I run Wildfly 8.1 on Java 8. ASM 3 does not work with Java > 8, so I wonder how things can work out at all, even without ES. If > possible, ASM 3 should be replaced by ASM 5.0 > > Jörg > > On Fri, Jul 25, 2014 at 9:02 AM, [joerg...@gmail.com](mailto:joerg...@gmail.com) \ \< > [joerg...@gmail.com](mailto:joerg...@gmail.com) \\> wrote: > > > You have two choices: > > > > - drop ASM and MVEL, switch to Groovy for scripting > > > > - use TransportClient to avoid ES-cluster-side services like scripting in > > Wildfly deployment (this is how I do it currently) > > > > Jörg > > > > On Fri, Jul 25, 2014 at 3:30 AM, John D. Ament \<[john.d...@gmail.com](mailto:john.d...@gmail.com) > > \\> wrote: > > > > > Hi all > > > > > > I was tinkering a bit with Elasticsearch. I think my target runtime may > > > end up being embedded, just based on our deployment model. Probably not a > > > big deal to get multiple nodes talking to each other and no additional > > > hardware to deploy. > > > > > > I was trying to start the application in WildFly 8.1. When I go to > > > deploy, I get errors related to ASM. It turns out that ES 1.3 ships w/ ASM > > > 4.1. WildFly uses ASM 3.3.1. Is it possible to run ES against this > > > version of ASM? It would seem that the two versions not compatible. > > > > > > If there's an alternative to running it on WF 8.1, I would love to hear > > > it. > > > > > > Thanks, > > > > > > John > > > > > > -- > > > 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) \. > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [July 26, 2014, 8:37am UTC](https://discuss.elastic.co/t/deploying-elasticsearch-1-3-to-wildfly-8-1/18886/5 "2014-07-26T08:37:25Z")
ASM is a PITA, it is not backward compatible. IIRC Wildfly 8.1 uses ASM 3 for hibernate and in CXF for some JAXB annotations so as long as you do not use this in your web app classpath it seems doable from within Wildfly, but you get the deployment errors. As said, my preference would be to drop MVEL from ES. Just use an ES TransportClient from within Widlfly. In that case there is no longer the need for a script language. I suggest not to create a full ES node in a web app container, this has other downsides (think of heap memory). Then you can exclude MVEL and ASM from ES jars safely, and most other dependencies too, just keep the ES jar and Lucene core jar with the query builders, this is enough for TransportClient. Jörg On Sat, Jul 26, 2014 at 3:44 AM, John D. Ament [john.d.ament@gmail.com](mailto:john.d.ament@gmail.com) wrote: > I can try upgrading ASM locally to see if it works. I'm assuming it's > backwards compatible? > > On Friday, July 25, 2014 3:06:13 AM UTC-4, Jörg Prante wrote: > > > As a side note, I run Wildfly 8.1 on Java 8. ASM 3 does not work with > > Java 8, so I wonder how things can work out at all, even without ES. If > > possible, ASM 3 should be replaced by ASM 5.0 > > > > Jörg > > > > On Fri, Jul 25, 2014 at 9:02 AM, [joerg...@gmail.com](mailto:joerg...@gmail.com) [joerg...@gmail.com](mailto:joerg...@gmail.com) > > wrote: > > > > > You have two choices: > > > > > > - drop ASM and MVEL, switch to Groovy for scripting > > > > > > - use TransportClient to avoid ES-cluster-side services like scripting > > > in Wildfly deployment (this is how I do it currently) > > > > > > Jörg > > > > > > On Fri, Jul 25, 2014 at 3:30 AM, John D. Ament [john.d...@gmail.com](mailto:john.d...@gmail.com) > > > wrote: > > > > > > > Hi all > > > > > > > > I was tinkering a bit with Elasticsearch. I think my target runtime > > > > may end up being embedded, just based on our deployment model. Probably > > > > not a big deal to get multiple nodes talking to each other and no > > > > additional hardware to deploy. > > > > > > > > I was trying to start the application in WildFly 8.1. When I go to > > > > deploy, I get errors related to ASM. It turns out that ES 1.3 ships w/ ASM > > > > 4.1. WildFly uses ASM 3.3.1. Is it possible to run ES against this > > > > version of ASM? It would seem that the two versions not compatible. > > > > > > > > If there's an alternative to running it on WF 8.1, I would love to hear > > > > it. > > > > > > > > Thanks, > > > > > > > > John > > > > > > > > -- > > > > 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). > > > > > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94% > > > > [40googlegroups.com](http://40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > 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). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoET2XhnoQkt4s%3DsTp%3DG8UjQnBHgFwZpFcxoj1wQK%3DUm\_w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoET2XhnoQkt4s%3DsTp%3DG8UjQnBHgFwZpFcxoj1wQK%3DUm_w%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![John\_D\_Ament](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_d_ament/32/764_2.png) [@John\_D\_Ament](https://discuss.elastic.co/u/John_D_Ament)\ **Post date:** [July 26, 2014, 11:51am UTC](https://discuss.elastic.co/t/deploying-elasticsearch-1-3-to-wildfly-8-1/18886/6 "2014-07-26T11:51:46Z")
Yeah, I know ASM is a PITA 🙂 At least in my app, I'm using hibernate and CXF. I don't use JAXB annotations currently as my webservices are super simple (due to the system that needs to consume them). So I might be OK. If I remove MVEL, is that all I need to remove? In my current use case, I'm planning to do an embedded runtime based on WildFly, where the app server node can act as a data node. This is until we need to start scaling bigger (we're currently only looking at a couple dozen users on at any time). When we start to scale, my recommendation to the infra team is to build out dedicated ES nodes and allow them to join the app server cluster with the app servers eventually moving out of data mode and into just client mode. I'm assuming that doing this will cause the data nodes to pull in whatever data was held by the app servers. Thanks a lot for your help so far! John On Saturday, July 26, 2014 4:37:33 AM UTC-4, Jörg Prante wrote: > ASM is a PITA, it is not backward compatible. > > IIRC Wildfly 8.1 uses ASM 3 for hibernate and in CXF for some JAXB > annotations so as long as you do not use this in your web app classpath it > seems doable from within Wildfly, but you get the deployment errors. > > As said, my preference would be to drop MVEL from ES. > > Just use an ES TransportClient from within Widlfly. In that case there is > no longer the need for a script language. I suggest not to create a full ES > node in a web app container, this has other downsides (think of heap > memory). Then you can exclude MVEL and ASM from ES jars safely, and most > other dependencies too, just keep the ES jar and Lucene core jar with the > query builders, this is enough for TransportClient. > > Jörg > > On Sat, Jul 26, 2014 at 3:44 AM, John D. Ament \<[john.d...@gmail.com](mailto:john.d...@gmail.com) > \\> wrote: > > > I can try upgrading ASM locally to see if it works. I'm assuming it's > > backwards compatible? > > > > On Friday, July 25, 2014 3:06:13 AM UTC-4, Jörg Prante wrote: > > > > > As a side note, I run Wildfly 8.1 on Java 8. ASM 3 does not work with > > > Java 8, so I wonder how things can work out at all, even without ES. If > > > possible, ASM 3 should be replaced by ASM 5.0 > > > > > > Jörg > > > > > > On Fri, Jul 25, 2014 at 9:02 AM, [joerg...@gmail.com](mailto:joerg...@gmail.com) [joerg...@gmail.com](mailto:joerg...@gmail.com) > > > wrote: > > > > > > > You have two choices: > > > > > > > > - drop ASM and MVEL, switch to Groovy for scripting > > > > > > > > - use TransportClient to avoid ES-cluster-side services like scripting > > > > in Wildfly deployment (this is how I do it currently) > > > > > > > > Jörg > > > > > > > > On Fri, Jul 25, 2014 at 3:30 AM, John D. Ament [john.d...@gmail.com](mailto:john.d...@gmail.com) > > > > wrote: > > > > > > > > > Hi all > > > > > > > > > > I was tinkering a bit with Elasticsearch. I think my target runtime > > > > > may end up being embedded, just based on our deployment model. Probably > > > > > not a big deal to get multiple nodes talking to each other and no > > > > > additional hardware to deploy. > > > > > > > > > > I was trying to start the application in WildFly 8.1. When I go to > > > > > deploy, I get errors related to ASM. It turns out that ES 1.3 ships w/ ASM > > > > > 4.1. WildFly uses ASM 3.3.1. Is it possible to run ES against this > > > > > version of ASM? It would seem that the two versions not compatible. > > > > > > > > > > If there's an alternative to running it on WF 8.1, I would love to > > > > > hear it. > > > > > > > > > > Thanks, > > > > > > > > > > John > > > > > > > > > > -- > > > > > 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). > > > > > > > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > > msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94% > > > > > [40googlegroups.com](http://40googlegroups.com) > > > > > [https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > . > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > 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) \. > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [July 26, 2014, 12:26pm UTC](https://discuss.elastic.co/t/deploying-elasticsearch-1-3-to-wildfly-8-1/18886/7 "2014-07-26T12:26:30Z")
Mmmmhhh.... I just examined ES 1.3 dependencies because I did not remember any asm jars in them... I must correct myself, now I learned that Lucene expressions - a new script language - depend on asm 4.1, and MVEL is standalone. So my suggestion is at first, before deploying, decide what script language you want to use. Then, secondly, fix the dependencies if necessary: - If you want Lucene expressions, take care that asm 4.1 is also in your web app classpath =\> this might conflict with Wildfly 8.1 - If you want the default MVEL, it seems ok (the MVEL 2.2.0 packages show a shaded asm which prevents dependency collisions - gotcha) - Also groovy is ok, and the other script language plugins (which I have not examined) as long as they do not depend on asm jars. Jörg ## [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ elasticsearch [INFO] org.elasticsearch:elasticsearch:jar:1.3.0 [INFO] +- org.hamcrest:hamcrest-all:jar:1.3:test [INFO] +- com.carrotsearch.randomizedtesting:randomizedtesting-runner:jar:2.1.2:test [INFO] | - junit:junit:jar:4.10:test [INFO] +- org.apache.lucene:lucene-test-framework:jar:4.9.0:test [INFO] | +- com.carrotsearch.randomizedtesting:junit4-ant:jar:2.1.3:test [INFO] | - org.apache.ant:ant:jar:1.8.2:test [INFO] +- org.apache.httpcomponents:httpclient:jar:4.3.1:test [INFO] | +- org.apache.httpcomponents:httpcore:jar:4.3:test [INFO] | +- commons-logging:commons-logging:jar:1.1.3:test [INFO] | - commons-codec:commons-codec:jar:1.6:test [INFO] +- org.apache.lucene:lucene-core:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-analyzers-common:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-codecs:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-queries:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-memory:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-highlighter:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-queryparser:jar:4.9.0:compile [INFO] | - org.apache.lucene:lucene-sandbox:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-suggest:jar:4.9.0:compile [INFO] | - org.apache.lucene:lucene-misc:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-join:jar:4.9.0:compile [INFO] | - org.apache.lucene:lucene-grouping:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-spatial:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-expressions:jar:4.9.0:compile [INFO] | +- org.antlr:antlr-runtime:jar:3.5:compile [INFO] | +- org.ow2.asm:asm:jar:4.1:compile [INFO] | - org.ow2.asm:asm-commons:jar:4.1:compile [INFO] +- com.spatial4j:spatial4j:jar:0.4.1:compile [INFO] +- com.vividsolutions:jts:jar:1.13:compile [INFO] +- com.github.spullara.mustache.java:compiler:jar:0.8.13:compile [INFO] +- com.google.guava:guava:jar:17.0:compile [INFO] +- com.carrotsearch:hppc:jar:0.5.3:compile [INFO] +- joda-time:joda-time:jar:2.3:compile [INFO] +- org.joda:joda-convert:jar:1.2:compile [INFO] +- org.mvel:mvel2:jar:2.2.0.Final:compile [INFO] +- com.fasterxml.jackson.core:jackson-core:jar:2.4.1.1:compile [INFO] +- com.fasterxml.jackson.dataformat:jackson-dataformat-smile:jar:2.4.1:compile [INFO] +- com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:jar:2.4.1:compile [INFO] +- com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:jar:2.4.1:compile [INFO] +- io.netty:netty:jar:3.9.1.Final:compile [INFO] +- com.ning:compress-lzf:jar:0.9.6:compile [INFO] +- com.tdunning:t-digest:jar:3.0:compile [INFO] +- org.codehaus.groovy:groovy-all:jar:2.3.2:compile [INFO] +- log4j:log4j:jar:1.2.17:compile [INFO] +- org.slf4j:slf4j-api:jar:1.6.2:compile [INFO] +- net.java.dev.jna:jna:jar:4.1.0:compile [INFO] - org.fusesource:sigar:jar:1.6.4:compile On Sat, Jul 26, 2014 at 1:51 PM, John D. Ament [john.d.ament@gmail.com](mailto:john.d.ament@gmail.com) wrote: > Yeah, I know ASM is a PITA 🙂 > > At least in my app, I'm using hibernate and CXF. I don't use JAXB > annotations currently as my webservices are super simple (due to the system > that needs to consume them). So I might be OK. > > If I remove MVEL, is that all I need to remove? > > In my current use case, I'm planning to do an embedded runtime based on > WildFly, where the app server node can act as a data node. This is until > we need to start scaling bigger (we're currently only looking at a couple > dozen users on at any time). When we start to scale, my recommendation to > the infra team is to build out dedicated ES nodes and allow them to join > the app server cluster with the app servers eventually moving out of data > mode and into just client mode. I'm assuming that doing this will cause > the data nodes to pull in whatever data was held by the app servers. > > Thanks a lot for your help so far! > > John > > On Saturday, July 26, 2014 4:37:33 AM UTC-4, Jörg Prante wrote: > > > ASM is a PITA, it is not backward compatible. > > > > IIRC Wildfly 8.1 uses ASM 3 for hibernate and in CXF for some JAXB > > annotations so as long as you do not use this in your web app classpath it > > seems doable from within Wildfly, but you get the deployment errors. > > > > As said, my preference would be to drop MVEL from ES. > > > > Just use an ES TransportClient from within Widlfly. In that case there is > > no longer the need for a script language. I suggest not to create a full ES > > node in a web app container, this has other downsides (think of heap > > memory). Then you can exclude MVEL and ASM from ES jars safely, and most > > other dependencies too, just keep the ES jar and Lucene core jar with the > > query builders, this is enough for TransportClient. > > > > Jörg > > > > On Sat, Jul 26, 2014 at 3:44 AM, John D. Ament [john.d...@gmail.com](mailto:john.d...@gmail.com) > > wrote: > > > > > I can try upgrading ASM locally to see if it works. I'm assuming it's > > > backwards compatible? > > > > > > On Friday, July 25, 2014 3:06:13 AM UTC-4, Jörg Prante wrote: > > > > > > > As a side note, I run Wildfly 8.1 on Java 8. ASM 3 does not work with > > > > Java 8, so I wonder how things can work out at all, even without ES. If > > > > possible, ASM 3 should be replaced by ASM 5.0 > > > > > > > > Jörg > > > > > > > > On Fri, Jul 25, 2014 at 9:02 AM, [joerg...@gmail.com](mailto:joerg...@gmail.com) \<[joerg...@gmail.com](mailto:joerg...@gmail.com) > > > > > > > > > wrote: > > > > > > > > > You have two choices: > > > > > > > > > > - drop ASM and MVEL, switch to Groovy for scripting > > > > > > > > > > - use TransportClient to avoid ES-cluster-side services like scripting > > > > > in Wildfly deployment (this is how I do it currently) > > > > > > > > > > Jörg > > > > > > > > > > On Fri, Jul 25, 2014 at 3:30 AM, John D. Ament [john.d...@gmail.com](mailto:john.d...@gmail.com) > > > > > wrote: > > > > > > > > > > > Hi all > > > > > > > > > > > > I was tinkering a bit with Elasticsearch. I think my target runtime > > > > > > may end up being embedded, just based on our deployment model. Probably > > > > > > not a big deal to get multiple nodes talking to each other and no > > > > > > additional hardware to deploy. > > > > > > > > > > > > I was trying to start the application in WildFly 8.1. When I go to > > > > > > deploy, I get errors related to ASM. It turns out that ES 1.3 ships w/ ASM > > > > > > 4.1. WildFly uses ASM 3.3.1. Is it possible to run ES against this > > > > > > version of ASM? It would seem that the two versions not compatible. > > > > > > > > > > > > If there's an alternative to running it on WF 8.1, I would love to > > > > > > hear it. > > > > > > > > > > > > Thanks, > > > > > > > > > > > > John > > > > > > > > > > > > -- > > > > > > 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). > > > > > > > > > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > > > msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40goo > > > > > > [glegroups.com](http://glegroups.com) > > > > > > [https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > -- > > > > 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). > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221% > > > > [40googlegroups.com](http://40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > -- > > 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). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHw69-3m2d-z\_t%3DV7\_mAZMuyT7\_3edXYGb%3DnBX\_XYRhHQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHw69-3m2d-z_t%3DV7_mAZMuyT7_3edXYGb%3DnBX_XYRhHQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [July 26, 2014, 12:40pm UTC](https://discuss.elastic.co/t/deploying-elasticsearch-1-3-to-wildfly-8-1/18886/8 "2014-07-26T12:40:24Z")
One ticket addressed the issue of this asm dependency, with the solution to switch the scope to "provided" > > > We currently pull in the \`lucene-expression\` module that is referenced by \`lucen…e-suggest\`. Yet, we don't make use of this dependency at all and it pulls in a bunch of unshaded libs like \`antlr\` and \`asm\` which are pretty common in other projects. We should exclude this dependency since we don't use it at all and it causes problems when Elasticsearch is used as a node client. (see https://github.com/elasticsearch/elasticsearch/issues/4858 ) > > If we mark the dependency as provided it won't be included in the distribution. Then, Lucene expressions jar was removed as dependency when ES switched to 4.7.0 > > > Closes #5104 > Closes #5129 > Closes #3757 The jar was reintroduced in > > > These are javascript expressions, which can only access numeric > fielddata, param…eters, and \_score. They can only be used for searches (not document updates). > > closes #6818 with dependency scope "compile". Which looks like a regression... Jörg On Sat, Jul 26, 2014 at 2:26 PM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \< [joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote: > Mmmmhhh.... I just examined ES 1.3 dependencies because I did not remember > any asm jars in them... > > I must correct myself, now I learned that Lucene expressions - a new > script language - depend on asm 4.1, and MVEL is standalone. > > So my suggestion is at first, before deploying, decide what script > language you want to use. Then, secondly, fix the dependencies if necessary: > > - If you want Lucene expressions, take care that asm 4.1 is also in your > web app classpath =\> this might conflict with Wildfly 8.1 > > - If you want the default MVEL, it seems ok (the MVEL 2.2.0 packages show > a shaded asm which prevents dependency collisions - gotcha) > > - Also groovy is ok, and the other script language plugins (which I have > not examined) as long as they do not depend on asm jars. > > Jörg > > ## [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ elasticsearch > > [INFO] org.elasticsearch:elasticsearch:jar:1.3.0 > [INFO] +- org.hamcrest:hamcrest-all:jar:1.3:test > [INFO] +- > com.carrotsearch.randomizedtesting:randomizedtesting-runner:jar:2.1.2:test > [INFO] | - junit:junit:jar:4.10:test > [INFO] +- org.apache.lucene:lucene-test-framework:jar:4.9.0:test > [INFO] | +- com.carrotsearch.randomizedtesting:junit4-ant:jar:2.1.3:test > [INFO] | - org.apache.ant:ant:jar:1.8.2:test > [INFO] +- org.apache.httpcomponents:httpclient:jar:4.3.1:test > [INFO] | +- org.apache.httpcomponents:httpcore:jar:4.3:test > [INFO] | +- commons-logging:commons-logging:jar:1.1.3:test > [INFO] | - commons-codec:commons-codec:jar:1.6:test > [INFO] +- org.apache.lucene:lucene-core:jar:4.9.0:compile > [INFO] +- org.apache.lucene:lucene-analyzers-common:jar:4.9.0:compile > [INFO] +- org.apache.lucene:lucene-codecs:jar:4.9.0:compile > [INFO] +- org.apache.lucene:lucene-queries:jar:4.9.0:compile > [INFO] +- org.apache.lucene:lucene-memory:jar:4.9.0:compile > [INFO] +- org.apache.lucene:lucene-highlighter:jar:4.9.0:compile > [INFO] +- org.apache.lucene:lucene-queryparser:jar:4.9.0:compile > [INFO] | - org.apache.lucene:lucene-sandbox:jar:4.9.0:compile > [INFO] +- org.apache.lucene:lucene-suggest:jar:4.9.0:compile > [INFO] | - org.apache.lucene:lucene-misc:jar:4.9.0:compile > [INFO] +- org.apache.lucene:lucene-join:jar:4.9.0:compile > [INFO] | - org.apache.lucene:lucene-grouping:jar:4.9.0:compile > [INFO] +- org.apache.lucene:lucene-spatial:jar:4.9.0:compile > [INFO] +- org.apache.lucene:lucene-expressions:jar:4.9.0:compile > [INFO] | +- org.antlr:antlr-runtime:jar:3.5:compile > [INFO] | +- org.ow2.asm:asm:jar:4.1:compile > [INFO] | - org.ow2.asm:asm-commons:jar:4.1:compile > [INFO] +- com.spatial4j:spatial4j:jar:0.4.1:compile > [INFO] +- com.vividsolutions:jts:jar:1.13:compile > [INFO] +- com.github.spullara.mustache.java:compiler:jar:0.8.13:compile > [INFO] +- com.google.guava:guava:jar:17.0:compile > [INFO] +- com.carrotsearch:hppc:jar:0.5.3:compile > [INFO] +- joda-time:joda-time:jar:2.3:compile > [INFO] +- org.joda:joda-convert:jar:1.2:compile > [INFO] +- org.mvel:mvel2:jar:2.2.0.Final:compile > [INFO] +- com.fasterxml.jackson.core:jackson-core:jar:2.4.1.1:compile > [INFO] +- > com.fasterxml.jackson.dataformat:jackson-dataformat-smile:jar:2.4.1:compile > [INFO] +- > com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:jar:2.4.1:compile > [INFO] +- > com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:jar:2.4.1:compile > [INFO] +- io.netty:netty:jar:3.9.1.Final:compile > [INFO] +- com.ning:compress-lzf:jar:0.9.6:compile > [INFO] +- com.tdunning:t-digest:jar:3.0:compile > [INFO] +- org.codehaus.groovy:groovy-all:jar:2.3.2:compile > [INFO] +- log4j:log4j:jar:1.2.17:compile > [INFO] +- org.slf4j:slf4j-api:jar:1.6.2:compile > [INFO] +- net.java.dev.jna:jna:jar:4.1.0:compile > [INFO] - org.fusesource:sigar:jar:1.6.4:compile > > On Sat, Jul 26, 2014 at 1:51 PM, John D. Ament [john.d.ament@gmail.com](mailto:john.d.ament@gmail.com) > wrote: > > > Yeah, I know ASM is a PITA 🙂 > > > > At least in my app, I'm using hibernate and CXF. I don't use JAXB > > annotations currently as my webservices are super simple (due to the system > > that needs to consume them). So I might be OK. > > > > If I remove MVEL, is that all I need to remove? > > > > In my current use case, I'm planning to do an embedded runtime based on > > WildFly, where the app server node can act as a data node. This is until > > we need to start scaling bigger (we're currently only looking at a couple > > dozen users on at any time). When we start to scale, my recommendation to > > the infra team is to build out dedicated ES nodes and allow them to join > > the app server cluster with the app servers eventually moving out of data > > mode and into just client mode. I'm assuming that doing this will cause > > the data nodes to pull in whatever data was held by the app servers. > > > > Thanks a lot for your help so far! > > > > John > > > > On Saturday, July 26, 2014 4:37:33 AM UTC-4, Jörg Prante wrote: > > > > > ASM is a PITA, it is not backward compatible. > > > > > > IIRC Wildfly 8.1 uses ASM 3 for hibernate and in CXF for some JAXB > > > annotations so as long as you do not use this in your web app classpath it > > > seems doable from within Wildfly, but you get the deployment errors. > > > > > > As said, my preference would be to drop MVEL from ES. > > > > > > Just use an ES TransportClient from within Widlfly. In that case there > > > is no longer the need for a script language. I suggest not to create a full > > > ES node in a web app container, this has other downsides (think of heap > > > memory). Then you can exclude MVEL and ASM from ES jars safely, and most > > > other dependencies too, just keep the ES jar and Lucene core jar with the > > > query builders, this is enough for TransportClient. > > > > > > Jörg > > > > > > On Sat, Jul 26, 2014 at 3:44 AM, John D. Ament [john.d...@gmail.com](mailto:john.d...@gmail.com) > > > wrote: > > > > > > > I can try upgrading ASM locally to see if it works. I'm assuming it's > > > > backwards compatible? > > > > > > > > On Friday, July 25, 2014 3:06:13 AM UTC-4, Jörg Prante wrote: > > > > > > > > > As a side note, I run Wildfly 8.1 on Java 8. ASM 3 does not work with > > > > > Java 8, so I wonder how things can work out at all, even without ES. If > > > > > possible, ASM 3 should be replaced by ASM 5.0 > > > > > > > > > > Jörg > > > > > > > > > > On Fri, Jul 25, 2014 at 9:02 AM, [joerg...@gmail.com](mailto:joerg...@gmail.com) \< > > > > > [joerg...@gmail.com](mailto:joerg...@gmail.com)\> wrote: > > > > > > > > > > > You have two choices: > > > > > > > > > > > > - drop ASM and MVEL, switch to Groovy for scripting > > > > > > > > > > > > - use TransportClient to avoid ES-cluster-side services like > > > > > > scripting in Wildfly deployment (this is how I do it currently) > > > > > > > > > > > > Jörg > > > > > > > > > > > > On Fri, Jul 25, 2014 at 3:30 AM, John D. Ament [john.d...@gmail.com](mailto:john.d...@gmail.com) > > > > > > wrote: > > > > > > > > > > > > > Hi all > > > > > > > > > > > > > > I was tinkering a bit with Elasticsearch. I think my target runtime > > > > > > > may end up being embedded, just based on our deployment model. Probably > > > > > > > not a big deal to get multiple nodes talking to each other and no > > > > > > > additional hardware to deploy. > > > > > > > > > > > > > > I was trying to start the application in WildFly 8.1. When I go to > > > > > > > deploy, I get errors related to ASM. It turns out that ES 1.3 ships w/ ASM > > > > > > > 4.1. WildFly uses ASM 3.3.1. Is it possible to run ES against this > > > > > > > version of ASM? It would seem that the two versions not compatible. > > > > > > > > > > > > > > If there's an alternative to running it on WF 8.1, I would love to > > > > > > > hear it. > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > John > > > > > > > > > > > > > > -- > > > > > > > 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). > > > > > > > > > > > > > > To view this discussion on the web visit > > > > > > > [https://groups.google.com/d/msgid/elasticsearch/4908b733-bab](https://groups.google.com/d/msgid/elasticsearch/4908b733-bab) > > > > > > > c-41bf-a87f-39ebfaea1f94%[40googlegroups.com](http://40googlegroups.com) > > > > > > > [https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > > > . > > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > > > -- > > > > > 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). > > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > > msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221% > > > > > [40googlegroups.com](http://40googlegroups.com) > > > > > [https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > . > > > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > -- > > > 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). > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFNfXx\_mvCK%3DqxUej7c6LD\_kokxQcjTKCeGHXnCRmCong%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFNfXx_mvCK%3DqxUej7c6LD_kokxQcjTKCeGHXnCRmCong%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![John\_D\_Ament](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_d_ament/32/764_2.png) [@John\_D\_Ament](https://discuss.elastic.co/u/John_D_Ament)\ **Post date:** [July 26, 2014, 1:12pm UTC](https://discuss.elastic.co/t/deploying-elasticsearch-1-3-to-wildfly-8-1/18886/9 "2014-07-26T13:12:21Z")
So, I'm assuming all this means I can safely remove expression, mvel, asm from my packaging requirements? I like this idea BTW [Mark 'lucene-expression' as 'provided' in pom.xml · Issue #4859 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/4859) (at the bottom). On Saturday, July 26, 2014 8:40:30 AM UTC-4, Jörg Prante wrote: > One ticket addressed the issue of this asm dependency, with the solution > to switch the scope to "provided" > > [Mark 'lucene-expression' as 'provided' in pom.xml · Issue #4859 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/4859) > > Then, Lucene expressions jar was removed as dependency when ES switched to > 4.7.0 > > [Upgrade to Lucene 4.7 · elastic/elasticsearch@30d7b8d · GitHub](https://github.com/elasticsearch/elasticsearch/commit/30d7b8de2fa043bdca3ca55026aa74f06d404a76) > > The jar was reintroduced in > > [Scripting: Add script engine for lucene expressions. · elastic/elasticsearch@64ab228 · GitHub](https://github.com/elasticsearch/elasticsearch/commit/64ab22816c1a6dfcd505406da5abef51f5434f49) > > with dependency scope "compile". Which looks like a regression... > > Jörg > > On Sat, Jul 26, 2014 at 2:26 PM, [joerg...@gmail.com](mailto:joerg...@gmail.com) \ \< > [joerg...@gmail.com](mailto:joerg...@gmail.com) \\> wrote: > > > Mmmmhhh.... I just examined ES 1.3 dependencies because I did not > > remember any asm jars in them... > > > > I must correct myself, now I learned that Lucene expressions - a new > > script language - depend on asm 4.1, and MVEL is standalone. > > > > So my suggestion is at first, before deploying, decide what script > > language you want to use. Then, secondly, fix the dependencies if necessary: > > > > - If you want Lucene expressions, take care that asm 4.1 is also in your > > web app classpath =\> this might conflict with Wildfly 8.1 > > > > - If you want the default MVEL, it seems ok (the MVEL 2.2.0 packages show > > a shaded asm which prevents dependency collisions - gotcha) > > > > - Also groovy is ok, and the other script language plugins (which I have > > not examined) as long as they do not depend on asm jars. > > > > Jörg > > > > ## [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ elasticsearch > > > > [INFO] org.elasticsearch:elasticsearch:jar:1.3.0 > > [INFO] +- org.hamcrest:hamcrest-all:jar:1.3:test > > [INFO] +- > > com.carrotsearch.randomizedtesting:randomizedtesting-runner:jar:2.1.2:test > > [INFO] | - junit:junit:jar:4.10:test > > [INFO] +- org.apache.lucene:lucene-test-framework:jar:4.9.0:test > > [INFO] | +- com.carrotsearch.randomizedtesting:junit4-ant:jar:2.1.3:test > > [INFO] | - org.apache.ant:ant:jar:1.8.2:test > > [INFO] +- org.apache.httpcomponents:httpclient:jar:4.3.1:test > > [INFO] | +- org.apache.httpcomponents:httpcore:jar:4.3:test > > [INFO] | +- commons-logging:commons-logging:jar:1.1.3:test > > [INFO] | - commons-codec:commons-codec:jar:1.6:test > > [INFO] +- org.apache.lucene:lucene-core:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-analyzers-common:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-codecs:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-queries:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-memory:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-highlighter:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-queryparser:jar:4.9.0:compile > > [INFO] | - org.apache.lucene:lucene-sandbox:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-suggest:jar:4.9.0:compile > > [INFO] | - org.apache.lucene:lucene-misc:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-join:jar:4.9.0:compile > > [INFO] | - org.apache.lucene:lucene-grouping:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-spatial:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-expressions:jar:4.9.0:compile > > [INFO] | +- org.antlr:antlr-runtime:jar:3.5:compile > > [INFO] | +- org.ow2.asm:asm:jar:4.1:compile > > [INFO] | - org.ow2.asm:asm-commons:jar:4.1:compile > > [INFO] +- com.spatial4j:spatial4j:jar:0.4.1:compile > > [INFO] +- com.vividsolutions:jts:jar:1.13:compile > > [INFO] +- com.github.spullara.mustache.java:compiler:jar:0.8.13:compile > > [INFO] +- com.google.guava:guava:jar:17.0:compile > > [INFO] +- com.carrotsearch:hppc:jar:0.5.3:compile > > [INFO] +- joda-time:joda-time:jar:2.3:compile > > [INFO] +- org.joda:joda-convert:jar:1.2:compile > > [INFO] +- org.mvel:mvel2:jar:2.2.0.Final:compile > > [INFO] +- com.fasterxml.jackson.core:jackson-core:jar:2.4.1.1:compile > > [INFO] +- > > com.fasterxml.jackson.dataformat:jackson-dataformat-smile:jar:2.4.1:compile > > [INFO] +- > > com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:jar:2.4.1:compile > > [INFO] +- > > com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:jar:2.4.1:compile > > [INFO] +- io.netty:netty:jar:3.9.1.Final:compile > > [INFO] +- com.ning:compress-lzf:jar:0.9.6:compile > > [INFO] +- com.tdunning:t-digest:jar:3.0:compile > > [INFO] +- org.codehaus.groovy:groovy-all:jar:2.3.2:compile > > [INFO] +- log4j:log4j:jar:1.2.17:compile > > [INFO] +- org.slf4j:slf4j-api:jar:1.6.2:compile > > [INFO] +- net.java.dev.jna:jna:jar:4.1.0:compile > > [INFO] - org.fusesource:sigar:jar:1.6.4:compile > > > > On Sat, Jul 26, 2014 at 1:51 PM, John D. Ament \<[john.d...@gmail.com](mailto:john.d...@gmail.com) > > \\> wrote: > > > > > Yeah, I know ASM is a PITA 🙂 > > > > > > At least in my app, I'm using hibernate and CXF. I don't use JAXB > > > annotations currently as my webservices are super simple (due to the system > > > that needs to consume them). So I might be OK. > > > > > > If I remove MVEL, is that all I need to remove? > > > > > > In my current use case, I'm planning to do an embedded runtime based on > > > WildFly, where the app server node can act as a data node. This is until > > > we need to start scaling bigger (we're currently only looking at a couple > > > dozen users on at any time). When we start to scale, my recommendation to > > > the infra team is to build out dedicated ES nodes and allow them to join > > > the app server cluster with the app servers eventually moving out of data > > > mode and into just client mode. I'm assuming that doing this will cause > > > the data nodes to pull in whatever data was held by the app servers. > > > > > > Thanks a lot for your help so far! > > > > > > John > > > > > > On Saturday, July 26, 2014 4:37:33 AM UTC-4, Jörg Prante wrote: > > > > > > > ASM is a PITA, it is not backward compatible. > > > > > > > > IIRC Wildfly 8.1 uses ASM 3 for hibernate and in CXF for some JAXB > > > > annotations so as long as you do not use this in your web app classpath it > > > > seems doable from within Wildfly, but you get the deployment errors. > > > > > > > > As said, my preference would be to drop MVEL from ES. > > > > > > > > Just use an ES TransportClient from within Widlfly. In that case there > > > > is no longer the need for a script language. I suggest not to create a full > > > > ES node in a web app container, this has other downsides (think of heap > > > > memory). Then you can exclude MVEL and ASM from ES jars safely, and most > > > > other dependencies too, just keep the ES jar and Lucene core jar with the > > > > query builders, this is enough for TransportClient. > > > > > > > > Jörg > > > > > > > > On Sat, Jul 26, 2014 at 3:44 AM, John D. Ament [john.d...@gmail.com](mailto:john.d...@gmail.com) > > > > wrote: > > > > > > > > > I can try upgrading ASM locally to see if it works. I'm assuming it's > > > > > backwards compatible? > > > > > > > > > > On Friday, July 25, 2014 3:06:13 AM UTC-4, Jörg Prante wrote: > > > > > > > > > > > As a side note, I run Wildfly 8.1 on Java 8. ASM 3 does not work with > > > > > > Java 8, so I wonder how things can work out at all, even without ES. If > > > > > > possible, ASM 3 should be replaced by ASM 5.0 > > > > > > > > > > > > Jörg > > > > > > > > > > > > On Fri, Jul 25, 2014 at 9:02 AM, [joerg...@gmail.com](mailto:joerg...@gmail.com) \< > > > > > > [joerg...@gmail.com](mailto:joerg...@gmail.com)\> wrote: > > > > > > > > > > > > > You have two choices: > > > > > > > > > > > > > > - drop ASM and MVEL, switch to Groovy for scripting > > > > > > > > > > > > > > - use TransportClient to avoid ES-cluster-side services like > > > > > > > scripting in Wildfly deployment (this is how I do it currently) > > > > > > > > > > > > > > Jörg > > > > > > > > > > > > > > On Fri, Jul 25, 2014 at 3:30 AM, John D. Ament [john.d...@gmail.com](mailto:john.d...@gmail.com) > > > > > > > wrote: > > > > > > > > > > > > > > > Hi all > > > > > > > > > > > > > > > > I was tinkering a bit with Elasticsearch. I think my target > > > > > > > > runtime may end up being embedded, just based on our deployment model. > > > > > > > > Probably not a big deal to get multiple nodes talking to each other and no > > > > > > > > additional hardware to deploy. > > > > > > > > > > > > > > > > I was trying to start the application in WildFly 8.1. When I go to > > > > > > > > deploy, I get errors related to ASM. It turns out that ES 1.3 ships w/ ASM > > > > > > > > 4.1. WildFly uses ASM 3.3.1. Is it possible to run ES against this > > > > > > > > version of ASM? It would seem that the two versions not compatible. > > > > > > > > > > > > > > > > If there's an alternative to running it on WF 8.1, I would love to > > > > > > > > hear it. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > > > John > > > > > > > > > > > > > > > > -- > > > > > > > > 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). > > > > > > > > > > > > > > > > To view this discussion on the web visit > > > > > > > > [https://groups.google.com/d/msgid/elasticsearch/4908b733-bab](https://groups.google.com/d/msgid/elasticsearch/4908b733-bab) > > > > > > > > c-41bf-a87f-39ebfaea1f94%[40googlegroups.com](http://40googlegroups.com) > > > > > > > > [https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/4908b733-babc-41bf-a87f-39ebfaea1f94%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > > > > . > > > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > > > > > -- > > > > > > 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). > > > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > > > msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221% > > > > > > [40googlegroups.com](http://40googlegroups.com) > > > > > > [https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/6856b6aa-bfa5-42de-8922-8be6d57a3221%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > > > . > > > > > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > -- > > > > 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) \. > > > > To view this discussion on the web visit > > > > [https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%40googlegroups.com) > > > > [https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/cda15cd8-d714-443b-be22-98637a32dacf%40googlegroups.com?utm_medium=email&utm_source=footer) > > > > . > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/24e74e93-ed4f-491c-b964-9e7a41662f9b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/24e74e93-ed4f-491c-b964-9e7a41662f9b%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [July 26, 2014, 2:46pm UTC](https://discuss.elastic.co/t/deploying-elasticsearch-1-3-to-wildfly-8-1/18886/10 "2014-07-26T14:46:06Z")
Keep lucene expression jar and mvel jar, just asm jar should be excluded. I like the client too :- it's not just an idea 🙂 > **[GitHub - jprante/elasticsearch-client: Modularized, OpenJDK 11 version of...](https://github.com/jprante/elasticsearch-client)** > > Modularized, OpenJDK 11 version of Elasticsearch client - GitHub - jprante/elasticsearch-client: Modularized, OpenJDK 11 version of Elasticsearch client it has to be updated to current ES version though. Jörg On Sat, Jul 26, 2014 at 3:12 PM, John D. Ament [john.d.ament@gmail.com](mailto:john.d.ament@gmail.com) wrote: > So, I'm assuming all this means I can safely remove expression, mvel, asm > from my packaging requirements? > > I like this idea BTW > [Mark 'lucene-expression' as 'provided' in pom.xml · Issue #4859 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/4859) (at the > bottom). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoF8-b5abTWYv%2Bw1nSWok4EZoJkYmabENhCp5KtL%2BoOBhQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoF8-b5abTWYv%2Bw1nSWok4EZoJkYmabENhCp5KtL%2BoOBhQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![John\_D\_Ament](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_d_ament/32/764_2.png) [@John\_D\_Ament](https://discuss.elastic.co/u/John_D_Ament)\ **Post date:** [July 26, 2014, 3:01pm UTC](https://discuss.elastic.co/t/deploying-elasticsearch-1-3-to-wildfly-8-1/18886/11 "2014-07-26T15:01:38Z")
It could be I'm missing something. Here's how I ultimately defined my dep ``` org.elasticsearch elasticsearch ${es.version} org.ow2.asm asm org.antlr antlr-runtime org.ow2.asm asm-commons ``` and everything's working fine. App deploys and WildFly is happy. When I take out my exclusions, this is the resulting dep tree: [INFO] - org.elasticsearch:elasticsearch:jar:1.3.0:compile [INFO] +- org.apache.lucene:lucene-core:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-analyzers-common:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-codecs:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-queries:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-memory:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-highlighter:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-queryparser:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-sandbox:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-suggest:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-misc:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-join:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-grouping:jar:4.9.0:compile [INFO] +- org.apache.lucene:lucene-spatial:jar:4.9.0:compile [INFO] | - com.spatial4j:spatial4j:jar:0.4.1:compile [INFO] +- org.antlr:antlr-runtime:jar:3.5:compile [INFO] +- org.ow2.asm:asm:jar:4.1:compile [INFO] - org.ow2.asm:asm-commons:jar:4.1:compile I'm not seeing mvel or lucene-expression in this list... Should i be worried? John On Saturday, July 26, 2014 10:46:19 AM UTC-4, Jörg Prante wrote: > Keep lucene expression jar and mvel jar, just asm jar should be excluded. > > I like the client too :- it's not just an idea 🙂 > > [GitHub - jprante/elasticsearch-client: Modularized, OpenJDK 11 version of Elasticsearch client](https://github.com/jprante/elasticsearch-client) > > it has to be updated to current ES version though. > > Jörg > > On Sat, Jul 26, 2014 at 3:12 PM, John D. Ament \<[john.d...@gmail.com](mailto:john.d...@gmail.com) > \\> wrote: > > > So, I'm assuming all this means I can safely remove expression, mvel, asm > > from my packaging requirements? > > > > I like this idea BTW > > [Mark 'lucene-expression' as 'provided' in pom.xml · Issue #4859 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/4859) (at the > > bottom). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/0087b76d-5249-4940-bd75-10dc7de1102b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0087b76d-5249-4940-bd75-10dc7de1102b%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [July 26, 2014, 4:09pm UTC](https://discuss.elastic.co/t/deploying-elasticsearch-1-3-to-wildfly-8-1/18886/12 "2014-07-26T16:09:06Z")
Funny. In my dependencies, I see it [INFO] +- org.apache.lucene:lucene-expressions:jar:4.9.0:compile [INFO] | +- org.antlr:antlr-runtime:jar:3.5:compile [INFO] | +- org.ow2.asm:asm:jar:4.1:compile [INFO] | - org.ow2.asm:asm-commons:jar:4.1:compile If it deploys in Wildfly now, it should be fine - just check a few example scripts if they work. In case of problems, you can always come back here to the mailing list and ask. Jörg On Sat, Jul 26, 2014 at 5:01 PM, John D. Ament [john.d.ament@gmail.com](mailto:john.d.ament@gmail.com) wrote: > It could be I'm missing something. Here's how I ultimately defined my dep > > ``` > > org.elasticsearch > elasticsearch > ${es.version} > > > org.ow2.asm > asm > > > org.antlr > antlr-runtime > > > org.ow2.asm > asm-commons > > > > > ``` > > and everything's working fine. App deploys and WildFly is happy. When I > take out my exclusions, this is the resulting dep tree: > > [INFO] - org.elasticsearch:elasticsearch:jar:1.3.0:compile > > [INFO] +- org.apache.lucene:lucene-core:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-analyzers-common:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-codecs:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-queries:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-memory:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-highlighter:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-queryparser:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-sandbox:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-suggest:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-misc:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-join:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-grouping:jar:4.9.0:compile > > [INFO] +- org.apache.lucene:lucene-spatial:jar:4.9.0:compile > > [INFO] | - com.spatial4j:spatial4j:jar:0.4.1:compile > > [INFO] +- org.antlr:antlr-runtime:jar:3.5:compile > > [INFO] +- org.ow2.asm:asm:jar:4.1:compile > > [INFO] - org.ow2.asm:asm-commons:jar:4.1:compile > > I'm not seeing mvel or lucene-expression in this list... Should i be > worried? > > John > > On Saturday, July 26, 2014 10:46:19 AM UTC-4, Jörg Prante wrote: > > > Keep lucene expression jar and mvel jar, just asm jar should be excluded. > > > > I like the client too :- it's not just an idea 🙂 > > > > [GitHub - jprante/elasticsearch-client: Modularized, OpenJDK 11 version of Elasticsearch client](https://github.com/jprante/elasticsearch-client) > > > > it has to be updated to current ES version though. > > > > Jörg > > > > On Sat, Jul 26, 2014 at 3:12 PM, John D. Ament [john.d...@gmail.com](mailto:john.d...@gmail.com) > > wrote: > > > > > So, I'm assuming all this means I can safely remove expression, mvel, > > > asm from my packaging requirements? > > > > > > I like this idea BTW [GitHub - elastic/elasticsearch: Free and Open, Distributed, RESTful Search Engine](https://github.com/elasticsearch/elasticsearch/) > > > issues/4859 (at the bottom). > > > > > > -- > > > 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). > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/0087b76d-5249-4940-bd75-10dc7de1102b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0087b76d-5249-4940-bd75-10dc7de1102b%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/0087b76d-5249-4940-bd75-10dc7de1102b%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/0087b76d-5249-4940-bd75-10dc7de1102b%40googlegroups.com?utm_medium=email&utm_source=footer) > > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoESx28BrhL6Lp26Rqd6dM0YyGbJ9R\_7NzL62duA9%2B6%3Dig%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoESx28BrhL6Lp26Rqd6dM0YyGbJ9R_7NzL62duA9%2B6%3Dig%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 1:12am UTC](https://discuss.elastic.co/t/deploying-elasticsearch-1-3-to-wildfly-8-1/18886/13 "2017-07-06T01:12:56Z")