EJB and none Thread safe legacy code

Article View: comp.lang.java.programmer

Article #244

Back to comp.lang.java.programmer Previous Next

#244

From: wilhelm
Date: Thu, 18 Oct 2001 23:22

19 lines
1854 bytes

I have a dll which is not thread safe -> legacy code (c/c++/fortran)
Is there a way of importing the JNI/DLL so each Statefull Session Bean
user
can concurrently access to it ?

DLL are load in the process space, so there is one load per
Application Server
This mean that I can have one user at a time....this does not seem a
good design, isn't it?

Can I spawn a process with each statefull EJB. This process will
communicate via RMI and follow the exact same life-cycle state machine
as the Statefull Session Bean, this should work, isn't it ?

Other idea ?

Thanks

Wilhelm

Technical Details

Message-ID: <d1d4144b.0110181522.21332a64@posting.google.com>

Path: arc1-ca.pugleaf.net!archiver1.google.com!postnews1.google.com!not-for-mail

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10a146,1806e1854d3bca2c,start
X-Google-Attributes: gid10a146,public
X-Google-Thread: fcfbb,1806e1854d3bca2c,start
X-Google-Attributes: gidfcfbb,public
X-Google-Thread: 102719,1806e1854d3bca2c,start
X-Google-Attributes: gid102719,public
X-Google-Thread: 1090f0,1806e1854d3bca2c,start
X-Google-Attributes: gid1090f0,public
X-Google-Thread: fcfb6,1806e1854d3bca2c,start
X-Google-Attributes: gidfcfb6,public
X-Google-ArrivalTime: 2001-10-18 16:22:03 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!postnews1.google.com!not-for-mail
From: wilhelmt@mdli.com (wilhelm)
Newsgroups: comp.lang.java.programmer,comp.lang.java.beans,weblogic.developer.interest.ejb,borland.public.appserver.ejb,ibm.software.websphere.application-server
Subject: EJB and none Thread safe legacy code
Date: 18 Oct 2001 16:22:03 -0700
Organization: http://groups.google.com/
Lines: 19
Message-ID: <d1d4144b.0110181522.21332a64@posting.google.com>
NNTP-Posting-Host: 208.200.221.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1003447323 1191 127.0.0.1 (18 Oct 2001 23:22:03 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 18 Oct 2001 23:22:03 GMT