[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference pamsrc::objectbroker_development

Title:ObjectBroker Development - BEA Systems' CORBA
Notice:See note 2 for kit locations; note 4 for training
Moderator:RECV::GUMBELd
Created:Thu Dec 27 1990
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2482
Total number of notes:13057

2337.0. "The issue is threads!" by OHFSS1::ZAMMIT () Thu Oct 03 1996 09:50

T.RTitleUserPersonal
Name
DateLines
2337.1OBB not thread safe or threadedRECV::SLAVINThu Oct 03 1996 12:317
2337.2FBEDEV::KYZIVATPaul KyzivatThu Oct 03 1996 13:4818
2337.3Some answersCFSCTC::HUSTONSteve HustonFri Oct 04 1996 10:3977
2337.4VAXCPU::michaudJeff Michaud - ObjectBrokerWed Apr 02 1997 23:2623
>>	- are all ObjectBroker APIs thread safe? If they are not, can we get
>>	around this with a mutex?
> None are thread safe.  If they use a mutex to ensure that only one thread
> at a time is in OBB, it's probably ok.

	I would not assume this either.  The ObjectBroker libraries use
	alot of static and global data, some of which if I recall when
	I did the IPMT case that lead to the discovery that you can't
	have more than one OBB application running on Windows 3.1, is
	that some of the global data is used to maintain state between
	calls into ObjectBroker.  So even if you use a global mutex and
	lock/unlock around every call into ObjectBroker, multiple threads
	using ObjectBroker could possibly still step on each other.

	As Maryann said, your safest bet is to funnel all calls into
	ObjectBroker through a single thread.

	We are working towards a threadsafe ORB in the future for IIOP
	(at least the 1st release will still be using some parts of OBB
	classic internals so likely won't be completely thread-safe
	until some subsequent release, but may be more usable, though
	unsupported, in an environment of multiple threads calling
	into the API).