MWS not restarting

Hello All,
We are getting the below errors when trying to restart MWS. Please let me know if anyone else experienced this kind of errors before and the steps performed to resolve the issue.

2011-01-05 18:06:26 IST (webm.caf : INFO) - My webMethods Server 7.1.2.0.131
2011-01-05 18:06:26 IST (Framework : INFO) - Loading phase: [phaseID, phaseName] [miePhaseTwo, miePhaseTwo]
2011-01-05 18:06:26 IST (Framework : INFO) - Initializing components of: miePhaseTwo
2011-01-05 18:06:26 IST (Framework : INFO) - Initializing components of: cluster
2011-01-05 18:06:26 IST (Framework : FATAL) - Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at com.webmethods.rtl.util.xml.XMLUtil._loadDocument(XMLUtil.java:344)
at com.webmethods.rtl.util.xml.XMLUtil.loadDocumentFromInputStream(XMLUtil.java:307)
at com.webmethods.rtl.util.xml.XMLUtil.loadDocument(XMLUtil.java:291)
at com.webmethods.portal.system.cluster.impl.ClusterProvider.getRegistryBasedComponentCollection(ClusterProvider.java:127)
at com.webmethods.portal.system.impl.BaseProvider.initComponents(BaseProvider.java:494)
at com.webmethods.portal.system.impl.BaseProvider.init(BaseProvider.java:125)
at com.webmethods.portal.system.cluster.impl.ClusterProvider.init(ClusterProvider.java:166)
at com.webmethods.portal.system.init.impl.DefaultPhase.initComponent(DefaultPhase.java:99)
at com.webmethods.portal.system.impl.BaseProvider.initComponents(BaseProvider.java:512)
at com.webmethods.portal.system.impl.BaseProvider.init(BaseProvider.java:125)
at com.webmethods.portal.system.init.impl.DefaultPhase.init(DefaultPhase.java:44)
at com.webmethods.portal.system.init.impl.DefaultPhaseProvider.initComponent(DefaultPhaseProvider.java:257)
at com.webmethods.portal.system.impl.BaseProvider.initComponents(BaseProvider.java:512)
at com.webmethods.portal.system.impl.BaseProvider.init(BaseProvider.java:125)
at com.webmethods.portal.system.init.impl.DefaultPhaseProvider.initializePhases(DefaultPhaseProvider.java:89)
at com.webmethods.portal.system.init.impl.ClusterPhaseProvider.initializePhases(ClusterPhaseProvider.java:27)
at com.webmethods.portal.system.PortalSystem.init(PortalSystem.java:868)
at com.webmethods.portal.system.PortalSystem.main(PortalSystem.java:827)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.webmethods.portal.system.start.Main.start(Main.java:131)
at com.webmethods.portal.system.start.Main.main(Main.java:48)
2011-01-05 18:06:26 IST (Framework : INFO) - No registered exception delegate
2011-01-05 18:06:26 IST (Framework : FATAL) - [POP.001.0002] A “java.lang.NullPointerException” occurred with the Message “at com.webmethods.portal.system.cluster.impl.ClusterProvider.getRegistryBasedComponentCollection(ClusterProvider.java:127)”
java.lang.NullPointerException
at com.webmethods.portal.system.cluster.impl.ClusterProvider.getRegistryBasedComponentCollection(ClusterProvider.java:127)
at com.webmethods.portal.system.impl.BaseProvider.initComponents(BaseProvider.java:494)
at com.webmethods.portal.system.impl.BaseProvider.init(BaseProvider.java:125)
at com.webmethods.portal.system.cluster.impl.ClusterProvider.init(ClusterProvider.java:166)
at com.webmethods.portal.system.init.impl.DefaultPhase.initComponent(DefaultPhase.java:99)
at com.webmethods.portal.system.impl.BaseProvider.initComponents(BaseProvider.java:512)
at com.webmethods.portal.system.impl.BaseProvider.init(BaseProvider.java:125)
at com.webmethods.portal.system.init.impl.DefaultPhase.init(DefaultPhase.java:44)
at com.webmethods.portal.system.init.impl.DefaultPhaseProvider.initComponent(DefaultPhaseProvider.java:257)
at com.webmethods.portal.system.impl.BaseProvider.initComponents(BaseProvider.java:512)
at com.webmethods.portal.system.impl.BaseProvider.init(BaseProvider.java:125)
at com.webmethods.portal.system.init.impl.DefaultPhaseProvider.initializePhases(DefaultPhaseProvider.java:89)
at com.webmethods.portal.system.init.impl.ClusterPhaseProvider.initializePhases(ClusterPhaseProvider.java:27)
at com.webmethods.portal.system.PortalSystem.init(PortalSystem.java:868)
at com.webmethods.portal.system.PortalSystem.main(PortalSystem.java:827)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.webmethods.portal.system.start.Main.start(Main.java:131)
at com.webmethods.portal.system.start.Main.main(Main.java:48)
2011-01-05 18:06:26 IST (Framework : INFO) - Shutting down…
2011-01-05 18:06:26 IST (Framework : INFO) - Shutting down components of: MWS
2011-01-05 18:06:26 IST (Framework : INFO) - Shutting down components of: miePhaseOne
2011-01-05 18:06:26 IST (Framework : INFO) - Shutdown complete.

1 Like

It appears that your cluster.xml file is corrupted, or at least un-parseable. Was it modified recently? Please have a look at that file and see if it is well formed xml.

Regards,
–mark

Thanks Mark for your quick response. The only files that are present in the MWS\server\default\config directory are demo.keystore and deployMap.properties and that the deployMap.properties is empty.

Also mws.db.xml file seems to have created during the last restart. Apart from the mentioned files there are no other files in the MWS\server\default\config directory.

Please suggest if there is a mechanism to recover the missing files that are required for Mws to be started.

Thanks again for all your assistance…

Regards,
Sivaram

Have a look at the Administering My webMethods Server pdf. In chapter 11, “My webMethods Server Clustering”, there is a section called ‘Editing the cluster.xml file’, which describes how to fetch that file from the db and edit it.

Hope this helps.
–mark

I’m facing this error when I’m changing my DB character set to UTF-8, prior to WE8MSWIN1252 (after I’ve deployed MWS & all components in DB), of which I’ve explored so far caused by:

“This is often caused by a white space before the XML declaration, but it could be any text, like a dash or any character. I say often caused by white space because people assume white space is always ignorable, but that’s not the case here.
Another thing that often happens is a UTF-8 BOM (byte order mark), which is allowed before the XML declaration can be treated as whitespace if the document is handed as a stream of characters to an XML parser rather than as a stream of bytes.”
-Mike Sokolov
http://stackoverflow.com/questions/5138696/org-xml-sax-saxparseexception-content-is-not-allowed-in-prolog

I’m not sure if I could explained technically very well, but IMHO xml document which used by MWS to read/write into DB was malformed (not read very well) by DB server, because differences in unicode for specific character (in this case: space or whitespace or any other characted was misread).
This could be the culprit after unicode altered, and messing up all identification in characters.

I’m solving this by re-creating MWS database using Database Component Configurator for MWS.
I know it sounds not solving the problem, but that’s far as I know to solving this kind of problem, hopefully there’s someone out there have any the best solution for this apart to re-creating DB.

Regards,

Ivan