Hello,

We have installed new webMethods 9.5 server on linux box,IS is running fine, but i am facing issue while starting up MWS,We are getting below fatal error and then its shuts down all components
Kindly help.

jvm 1 | 2014-02-24 11:17:50 CET (Framework:INFO) - Loading phase: [phaseID, phaseName] [webserver, webserver]
jvm 1 | 2014-02-24 11:17:50 CET (Framework:INFO) - Initializing components of: webserver
jvm 1 | 2014-02-24 11:17:50 CET (Framework:INFO) - Initializing component: com.webMethods.portal.webapp.jetty7.JettySystem
jvm 1 | 2014-02-24 11:17:50 CET (Framework:FATAL) - [POP.001.0002] A “java.lang.NullPointerException” occurred with the Message “at com.webMethods.portal.webapp.jetty7.JettySystem.localJettyConfigFile(JettySystem.java:154)”
jvm 1 | java.lang.NullPointerException
jvm 1 | at com.webMethods.portal.webapp.jetty7.JettySystem.localJettyConfigFile(JettySystem.java:154)
jvm 1 | at com.webMethods.portal.webapp.jetty7.JettySystem.initializeServer(JettySystem.java:169)
jvm 1 | at com.webMethods.portal.webapp.jetty7.JettySystem.initializeJetty(JettySystem.java:127)
jvm 1 | at com.webMethods.portal.webapp.jetty7.JettySystem.init(JettySystem.java:123)
jvm 1 | at com.webMethods.portal.webapp.jetty7.JettySystem.main(JettySystem.java:108)
jvm 1 | at com.webMethods.portal.webapp.jetty7.JettySystem.init(JettySystem.java:69)
jvm 1 | at com.webMethods.portal.system.init.impl.DefaultPhase$InitializableWrapper.init(DefaultPhase.java:136)
jvm 1 | at com.webMethods.portal.system.init.impl.DefaultPhase.initComponent(DefaultPhase.java:117)
jvm 1 | at com.webMethods.portal.system.impl.BaseProvider.initComponents(BaseProvider.java:634)
jvm 1 | at com.webMethods.portal.system.impl.BaseProvider.init(BaseProvider.java:170)
jvm 1 | at com.webMethods.portal.system.init.impl.DefaultPhase.init(DefaultPhase.java:49)
jvm 1 | at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.initComponent(DefaultPhaseProvider.java:266)
jvm 1 | at com.webMethods.portal.system.impl.BaseProvider.initComponents(BaseProvider.java:634)
jvm 1 | at com.webMethods.portal.system.impl.BaseProvider.init(BaseProvider.java:170)
jvm 1 | at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.initializePhases(DefaultPhaseProvider.java:91)
jvm 1 | at com.webMethods.portal.system.init.impl.ClusterPhaseProvider.initializePhases(ClusterPhaseProvider.java:78)
jvm 1 | at com.webMethods.portal.system.init.impl.PartitionPhaseProvider.initializePhases(PartitionPhaseProvider.java:59)
jvm 1 | at com.webMethods.portal.system.PortalSystem.init(PortalSystem.java:905)
jvm 1 | at com.webMethods.portal.system.PortalSystem.main(PortalSystem.java:841)
jvm 1 | at com.webMethods.portal.system.PortalSystemActivator$1.call(PortalSystemActivator.java:59)
jvm 1 | at com.webMethods.portal.system.PortalSystemActivator$1.call(PortalSystemActivator.java:56)
jvm 1 | at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
jvm 1 | at java.util.concurrent.FutureTask.run(FutureTask.java:166)
jvm 1 | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
jvm 1 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
jvm 1 | at java.lang.Thread.run(Thread.java:724)
jvm 1 | 2014-02-24 11:17:50 CET (Framework:INFO) - Shutdown Manager running all shutdown hooks.
jvm 1 | 2014-02-24 11:17:50 CET (com.softwareag.platform.shutdown.internal.ShutdownAction:INFO) - Starting shutdown of OSGi framework with: poll 1000, timeout 120000
jvm 1 | 2014-02-24 11:17:50 CET (com.softwareag.platform.shutdown.internal.ShutdownAction:INFO) - Stopping the OSGi framework
jvm 1 | 2014-02-24 11:17:50 CET (Framework:INFO) - Shutting down PortalServlet

@Unnatiyadav,

Please check the install.log. It seems there is some issue with installation. I assume you have set the Db details right while installation.

If everything was ok last time, I suggest to re-install.

Thanks,
Rankesh

Yes i did specify DB details while installation.I could start the server last time and worked with TN also, so i ruled out any installation issue, Lemme have a look again at installation logs.

Its resolved, Apparently SAG components were running under different use ,So we restarted all under one user and it went fine.

Regards
Unnati Yadav