Issue with soa managed server

Today while starting soa managed server,i was getting issues.It used to go to starting mode and then to failed not restartable.I checked logs and found that AIA deployments were failing,

===========

WARNING: Error during preRegister for MBean oracle.dfw:name=Streamer,type=oracle.dfw.jmx.Streaming 

java.lang.RuntimeException: java.lang.NoClassDefFoundError: Could not initialize class oracle.dfw.impl.common.TempFileManager  at oracle.as.jmx.framework.generic.spi.interceptors.LoggingMBeanInterceptor.internalPreRegister(LoggingMBeanInterceptor.java:663) 

at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doPreRegister(AbstractMBeanInterceptor.java:180) 

at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.preRegister(OracleStandardEmitterMBean.java:611) 

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.preRegisterInvoke(DefaultMBeanServerInterceptor.java:1010) 

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:938) 

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917) 

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312) 

at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) 

oracle/dfw/impl/common/TempFileManager --->Appeared many times.

It had a simple fix.

1. Check /tmp directory in your machine and check if having oracle-dfw* files created by a different user other than the "installation owner".

If so, delete them all.

2. If you want to have multiple installations, by different users, ensure to set the following java property Into the EXTRA_JAVA_PROPERTIES for the setDomainEnv.sh:

-Djava.io.tmpdir=<path>

Error on admin console

After a bounce on weblogic domain i got the below error after logging to admin console

================

Error opening /jsp/changemgmt/ChangeManager.jsp.

The source of this error is:
java.lang.NullPointerException
 at com.bea.console.taglib.changemgmt.ChangeCenterTag.doStartTag(ChangeCenterTag.java:82)
 at jsp_servlet._jsp._changemgmt.__changemanager._jspService(__changemanager.java:172)
 at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
 at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:523)
 at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:444)
 at org.apache.beehiv

=====================

I thought someone edited the file and forgot to activate changes.I checked the DOMAIN_HOME pending folder to see if there was a change done.Found nothing here.

To fix this issue i tried restarting admin after clearing tmp and cache but no use,

We can fix this issue as below:

1. Navigate to <Domain_Home>/pending folder. In this folder, there are configuration files which are temporary config files which are cached with changes made from console. At the time of activating changes, the config.xml from the pending folder replaces the

 original config.xml and other configuration files inside the <Domain_Home>/config folder

2. Stop the Admin Server, and replace the config.xml from the <Domain_Home>/config folder with the config.xml from the <Domain_Home>/pending folder.

3. Delete all the .lok files inside <Domain_Home> like edit.lok and config.lok.

4. Restart Admin Server.

I my case i just removed the edit.lok file and restarted.