RE: ACPI Sleep and connection persistence

Hi Venkat,

Thank you for your reply.  Please comment of the “Connection closed by CIM Server” regarding Pegasus client version 2.9.1 and does the CIM connect automatically like version 2.11.0?

Are there are limitations with Open Pegasus version 2.9.1 with connecting to the CIM server automatically?  If so, is there a work around using Open Pegasus version 2.9.1?

We do understand Open Pegasus version 2.11.0 reconnects automatically.

Thank you for the help.

Best Regards,
Ken Kotyuk
Program Manager, CDM MFG. Test Diagnostics
Hewlett-Packard Company
1501 Page Mill Road
Building 3L; Mail Stop 1222
Palo Alto, CA. 94304-1100
Phone: (650) 857-4566
Fax:     (650) 857-4783
email:[email protected]

From: Venkateswara R Puvvada [mailto:[email protected]]
Sent: Wednesday, May 11, 2011 10:56 PM
To: Alexis Boisserand
Cc: OpenPegasus Mailing List
Subject: Re: ACPI Sleep and connection persistence

Hi Alexis,

There were no known issues regarding the reported problem. "Connection closed by CIM server." usually means that either cimserver has crashed or restarted or connection closed with idleConnectionTimeout expired. Latest version of Pegasus client (2.11.0) reconnects automatically if the connection is closed. Test with the latest version of code or provide the stack trace of the client when crash happens for the further debugging.

Venkat



From:        Alexis Boisserand <[email protected]>
To:        OpenPegasus Mailing List <[email protected]>
Date:        04/05/2011 23:05
Subject:        ACPI Sleep and connection persistence
________________________________



Hi everyone,

We are developing a CIM client application on Windows 7 x86 with the
OpenPegasus client library. The CIMOM we use is OpenPegasus 2.9.1. Our
client keeps connected locally (we use the connectLocal() method) to the
CIMOM and issues some CIM operations. Our problem is the following:
while the application is running if the machine enters the ACPI sleep
mode, when it comes back from the sleep mode and tries to issue CIM
operations again, the operations fail and throw an exception with the
message "Connection closed by CIM server.", the type of this exception
is neither NotConnectedException nor ConnectionTimeoutException. We
first tried to make a client that tries to reconnect silently when this
exception is thrown, but when we try to reconnect, our application
crashes. It seems that the client is in an inconsistent state, neither
connected nor disconnected. To my knowledge entering and coming back
from the sleep mode is supposed to be transparent for the applications,
and any application should come back from the sleep mode in the same
state that it entered it. My questions are the following:

- Is this a known limitation of OpenPegasus?
- If not, has anyone any idea of what could be the cause of this
problem?
- Would not there be some workaround to prevent this from happening?

Thanks for your answers,

--
Alexis Boisserand        [email protected]              +55
51 3220 3293
=======================================================
Tools & Technologies – T&T

The Software Development Expert



Rua Riachuelo, 1098 Conj. 1204
Centro - Porto Alegre - CEP 90010-272
Fone: +55 51 3220 3220
http://www.tet.com.br/
=======================================================