Re: CMPI Provider threaded?

Hi Shane,
I have been running CIMPLE providers with these locks commented out and so
far in internal testing, I have not found any issues, but this is
non-production code. I have talked to Karl Schopmeyer (author of CIMPLE) in
the past and he thinks CIMPLE should be fine without those locks as long as
the provider implementation is thread safe.
Anuj


On Fri, Jun 7, 2013 at 1:52 PM, Shane Hender <[email protected]>wrote:

>  Thanks Anuj, that was spot-on.
> Commenting out the CIMPLE CMPI_Adapter.cpp "Auto_Mutex
> auto_lock(adapter->lock);" line for each of the intrinsic functions worked
> like a charm. Of course I'll have to verify later that those locks weren't
> a shortcut to making this code thread safe.  Did you do any testing
> yourself to verify this? As it sounds like you did this yourself sometime
> in the past.
>
>  Thanks,
> Shane.
>
>
>   From: Shane Hender <[email protected]>
> To: Anuj Jain <[email protected]>
>
> Cc: "[email protected]" <[email protected]>
> Subject: Re: CMPI Provider threaded?
>
>   Thanks Anuj, I'll give that a go!
>
>  --Shane.
>
>   From: Anuj Jain <[email protected]>
> To: Shane Hender <[email protected]>
> Cc: "[email protected]" <[email protected]>
> Subject: Re: CMPI Provider threaded?
>
>   The Shane,
> The behavior you are seeing is due to the Pegasus adapter implementation
> in CIMPLE and not Pegasus. CIMPLE uses a common lock across various wbem
> operations. You can see this code under the Pegasus adapter code in CIMPLE.
> You can in fact take that lock out from CIMPLE and try your providers.
>  Anuj
>
>
>
>
> On Thu, Jun 6, 2013 at 9:20 PM, Shane Hender <[email protected]>wrote:
>
>>  Hi,
>>
>>  I'm writing providers using the CIMPLE/SimpleWBEM C++ interface that
>> sits on top of CMPI.
>>
>>  However, I notice that my providers are getting called in a synchronous
>> fashion, I.e., 2 requests to my provider will not get executed
>> concurrently.  Is there something I missed in compiling OpenPegasus to
>> allow this support in the Provider Agent?
>>
>>  Thanks,
>> Shane.
>>
>>
>> ------------------------------
>>
>> Confidentiality Notice: The information contained in this electronic
>> e-mail and any accompanying attachment(s) is intended only for the use of
>> the intended recipient and is confidential and/or privileged. If you and we
>> have a confidentiality agreement or other non-disclosure obligations
>> between us, this Notice shall be deemed to mark and identify the content of
>> this email and any attachments as confidential and proprietary. If any
>> reader of this communication is not the intended recipient, unauthorized
>> use, disclosure or copying is strictly prohibited, and may be unlawful. If
>> you have received this communication in error, please immediately notify
>> the sender by return e-mail, and delete the original message and all copies
>> from your system. Thank you.
>>
>> IRS Circular 230 Disclosure: To ensure compliance with requirements
>> imposed by the IRS, please be advised that any U.S. federal tax advice
>> contained in this communication (including any attachments) is not intended
>> or written to be used or relied upon, and cannot be used or relied upon,
>> for the purpose of (i) avoiding penalties under the Internal Revenue Code,
>> or (ii) promoting, marketing or recommending to another party any
>> transaction or matter addressed herein.
>>
>> E-mail is susceptible to data corruption, interception, unauthorized
>> amendment, tampering and viruses, and we only send and receive e-mails on
>> the basis that we are not liable for any such corruption, interception,
>> amendment, tampering or viruses or any consequences thereof.
>>
>>
>
> ------------------------------
>
> Confidentiality Notice: The information contained in this electronic
> e-mail and any accompanying attachment(s) is intended only for the use of
> the intended recipient and is confidential and/or privileged. If you and we
> have a confidentiality agreement or other non-disclosure obligations
> between us, this Notice shall be deemed to mark and identify the content of
> this email and any attachments as confidential and proprietary. If any
> reader of this communication is not the intended recipient, unauthorized
> use, disclosure or copying is strictly prohibited, and may be unlawful. If
> you have received this communication in error, please immediately notify
> the sender by return e-mail, and delete the original message and all copies
> from your system. Thank you.
>
> IRS Circular 230 Disclosure: To ensure compliance with requirements
> imposed by the IRS, please be advised that any U.S. federal tax advice
> contained in this communication (including any attachments) is not intended
> or written to be used or relied upon, and cannot be used or relied upon,
> for the purpose of (i) avoiding penalties under the Internal Revenue Code,
> or (ii) promoting, marketing or recommending to another party any
> transaction or matter addressed herein.
>
> E-mail is susceptible to data corruption, interception, unauthorized
> amendment, tampering and viruses, and we only send and receive e-mails on
> the basis that we are not liable for any such corruption, interception,
> amendment, tampering or viruses or any consequences thereof.
>
>
> ------------------------------
>
> Confidentiality Notice: The information contained in this electronic
> e-mail and any accompanying attachment(s) is intended only for the use of
> the intended recipient and is confidential and/or privileged. If you and we
> have a confidentiality agreement or other non-disclosure obligations
> between us, this Notice shall be deemed to mark and identify the content of
> this email and any attachments as confidential and proprietary. If any
> reader of this communication is not the intended recipient, unauthorized
> use, disclosure or copying is strictly prohibited, and may be unlawful. If
> you have received this communication in error, please immediately notify
> the sender by return e-mail, and delete the original message and all copies
> from your system. Thank you.
>
> IRS Circular 230 Disclosure: To ensure compliance with requirements
> imposed by the IRS, please be advised that any U.S. federal tax advice
> contained in this communication (including any attachments) is not intended
> or written to be used or relied upon, and cannot be used or relied upon,
> for the purpose of (i) avoiding penalties under the Internal Revenue Code,
> or (ii) promoting, marketing or recommending to another party any
> transaction or matter addressed herein.
>
> E-mail is susceptible to data corruption, interception, unauthorized
> amendment, tampering and viruses, and we only send and receive e-mails on
> the basis that we are not liable for any such corruption, interception,
> amendment, tampering or viruses or any consequences thereof.
>
>