RE: cimprovagt with jvm crash on shutdown

While one of the three providers is an indication provider with active subscriptions the other two seems to stay resident in the memory as well. So to answer the question why they are still loaded; it seems that JMPI is doing that. Anyway, it actually crashes under other weird circumstances as well. Like, if I start the cimserver, one of the provider (the one with active subscriptions) is started, and when I then list the configuration properties (cimconfig -l) my provider crash with the same error log.

-Patrik

________________________________
From: Kirk Augustin [mailto:[email protected]]
Sent: den 22 juni 2010 19:22
To: Åkerfeldt Patrik; [email protected]
Subject: Re: cimprovagt with jvm crash on shutdown

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<cid:71f8e54f-1276-4a62-9e02-8fd04e15b168>

Thanks,
Patrik