Application deploy name cause JMX counter can't being fetched

Question

Hello all, I'm a fresh newer in WebLogic.
When I using WebLogic, I deploy a application named "WORLD" in side a managed server, the archive version of this WORLD is 1.0.0, then after I fix some bugs and re-deploy this application with archive version 1.0.1, found a problem that I can't get HealthState of this application, I investigate it, found this problem caused by that the naming rule of JMX counter object name, as bellow:
com.bea:ServerRuntime=managedxx,Name=WORLD_1.0.1,Type=ApplicationRuntime"
But previously before I upgrade the application, the object name of HealthState is:
com.bea:ServerRuntime=managedxx,Name=WORLD_1.0.0,Type=ApplicationRuntime"
Archive is used in the object name.
My question: is there some setting inside WebLogic to make it doesn't use the archive version to detect a JMX counter's object name, for example, if the HealthState always use only application name and without archive version, then no such problem will occurred, for example:
com.bea:ServerRuntime=managedxx,Name=WORLD,Type=ApplicationRuntime"
Is there somebody can help me?

Answer 1

Thanks for the suggestions, believe me we've restarted the server many, many times, we just can't find any errors in the log that pertain to this problem.
I did some more tests on this problem just recently and I did find that saving the process as a new process and comparing the two process xml (from the metadata) shows differences in the indentation and the <?xml...?> tag which is now missing. I replaced the old process with the new one and this managed to get me past the issue for now. But this is the second time this has happened to this process and last time renaming the process just wouldn't work past the first check-in.
Thanks for the reply, I appreciate any ideas!
Nic