Hi, i have a question concerning threads and EJBs. I figured out, that one has to set the -userThreads argument for orion to allow threads to be opened from within servlets and/or EJBs - and this seems to work. But this brings up some questions: 1. Is it safe to assume, that (almost) any application server supports threads from within EJBs (which will call other EJBs)? The EJB 1.1 spec prohibits it, if i remember it right... Though i like orion and will use it, the applications should remain portable. 2. If not, is it a special feature of orion? (well, stupid question) If not, what was the intention in offering it? Are there any things one have to know prior of using this feature? 3. Related to this: non-final static variables should not be used due to the spec. Is there a (fast & easy) way to share such static data (other than having an entity bean in the db or writing something into the jndi context)? Especially in a clustered server this will be interesting. Is there any standard way supposed to use? If not, is there any proprietary way orion offers? It is often neccessary to have caches, which have to be synchronized on data changes, for example. I know, that orion uses only one VM if it's not clustered, but i'd like to be portable - and scalable (clusterable - i like english ;-). Thanx for any answers, Jens Stutte ____________________________________________ [EMAIL PROTECTED], http://www.netmedia.de NetMedia GmbH Neugrabenweg 5-7 66123 Saarbruecken Germany fon: +49 (0) 681 - 3 79 88 - 0 fax: +49 (0) 681 -�3 79 88 - 99
