Re: cimprovagt with jvm crash on shutdown
Kirk Augustin <[email protected]>
| Newsgroups | gmane.network.open-pegasus.general |
|---|---|
| Message-ID | <[email protected]> |
While I have not use the JMPI interface, what you describe is in general the behavior I would expect. In general you should not stop the cimserver, and you should get all the providers to finish their tasks and terminate first. Providers normally should only be loaded and running when they have a specific task, and they should unloaded by default. So my first question would be why the providers are running? Is it because you have altered their timeout so that they stay resident, or is JMPI doing that? And then, why are you stopping the cimserver? There normally is no reason to do that. ________________________________ From: Åkerfeldt Patrik <[email protected]> To: "[email protected]" <[email protected]> Sent: Tue, June 22, 2010 1:35:42 AM Subject: cimprovagt with jvm crash on shutdown Hi all, We are running OpenPegasus 2.9.1 with support for JMPI providers. The provider runs fine and starts within its own cimprovagt. But each time I stop the cimserver each jvm crash, leaving a total of three crash dumps one for each of our current JMPI based providers. Attached is one of these log files. Can someone help me figure out why the jvms are crashing when I stop the cimserver? hs_err_pid10707.log Thanks, Patrik