Yeah. You're not suppose to do that but it works well.
What you should avoid is to reload your webapp without stopping the container (redeploy for example). You will get OOM as some threads won't be stopped (old issue in Guava as far as I remember).
I used Node Client first and then Transport client within Jboss and did not see any particular issue.
HTH
David 
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 28 juil. 2013 à 17:56, "Oliver B. Fischer" mailsink@swe-blog.net a écrit :
Am 27.07.13 21:01, schrieb joergprante@gmail.com:
Why are you asking for conflict with JEE requirements? I am not aware of
any conflicts. ES TransportClient is easy to use.
I am asking because of EJB restriction not to "create or manage threads" in your application [1]. So using a component that has its own thread management would violate this requirement. Mostly its work but I prefer to respect the EJB restrictions.
Best,
Oliver
[1]: EJB Restrictions)
Jörg
--
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.
For more options, visit 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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.