MarkView Application Server - Unable to start MarkView Server on Weblogic / OAS

Applies To

• ERP System: All
• MarkView Version: All

Behavior

The system administrator is unable to start Markview instance from Weblogic / OAS, and is able to see errors similar to the following ones in application server log files:

Weblogic Error :

• java.io.IOException: Invalid state file format. State file contents:
  at weblogic.nodemanager.common.StateInfo.load(StateInfo.java:135)
  at weblogic.nodemanager.server.AbstractServerMonitor.loadStateInfo(AbstractServerMonitor.java:497) at
  weblogic.nodemanager.server.AbstractServerMonitor.isCleanupAfterCrashNeeded(AbstractServerMonitor.java:156)
• OAS Error:
  *** (SEVERE) Failed to set the internal configuration of the OC4J JMS Server with: XMLJMSServerConfig[file:$ORACLE_HOME/j2ee/markview_oas/config/jms.xml]

Known Causes

• The issue usually happens If there was a space issue on the application server which has prevented the application server from updating the state file before stopping, or due to unexpected shut down or reboot of the server.

Resolution

• Weblogic:
  1. Stop the managed server if it is running.
  2. Stop the Admin Server.
  3. Stop Node Manager.
  4. Remove any (state, lck or pid) files under the node manager directory, the system will recreate them upon restart:
     Examples:
     (Win) \oracle\middleware\user_projects\domains\base_domain\servers\soa_server1\data\nodemanager
     (Unix) /projects/wl01/Oracle/Middleware/user_projects/domains/markview/servers/markview_server/data/nodemanager
  5. Start Node Manager again.
  6. Start the Admin Server again.
  7. Start the managed server using the Admin Console.
• OAS:
  1. Delete the state file that can be found under the following location, the application server will recreate it properly upon restart:
     $ORACLE_HOME/oc4j/j2ee/home/persistence/jms.state
  2. Restart Markview Server.