Mobile Server Fails To Start After System Crash Or Incorrect Shutdown Process (Doc ID 1089842.1)

Last updated on JUNE 19, 2017

Applies to:

Oracle Lite - Version 10.3.0.3.0 to 10.3.0.3.0 [Release 10.3]
Information in this document applies to any platform.
***Checked for relevance on 14-Aug-2014***

Symptoms

Attemps to start the Mobile Server after a crash, system shutdown, or incorrect shutdown of the mobile server fail with the error:

2010-04-26 14:09:37.993 NOTIFICATION JMSServer[]: OC4J JMS server recovering transactions (commit 0) (rollback 0) (prepared 0).
2010-04-26 14:09:38.009 NOTIFICATION JMSServer[]: OC4J JMS server recovering local transactions Queue[jms/Oc4jJmsExceptionQueue].
10/04/26 14:09:44 WARNING: Application.setConfig Application: mobileserver is in
failed state as initialization failed.
java.lang.InstantiationException: Error loading web-app 'TestApp' at D:\Olite10g_1\mobile_oc4j\j2ee\mobileserver\applications\mobileserver\TestApp: Unable to find/read file WEB-INF/web.xml in D:\Olite10g_1\mobile_oc4j\j2ee\mobileserver\applications\mobileserver\TestApp (WEB-INF/web.xml)
2010-04-26 14:09:44.790 WARNING J2EE OJR-00013 Exception initializing deployed application: mobileserver. Application: mobileserver is in failed state as initialization failed
2010-04-26 14:09:47.321 ERROR J2EE HTTP-00004 Internal error raised tyring to instantiate web-application: webtogo defined in web site OC4J 10g (10.1.3) Default
Web Site. Application: webtogo has been stopped
10/04/26 14:09:47 Oracle Containers for J2EE 10g (10.1.3.4.0) initialized

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms