[HTTP: 101216] Servlet: "FICMaster" failed to preload on startup in Web application, 101216 ficmaster
I recently obtained an Oracle OFSAA software, which encountered a problem during program deployment. Currently, knowledge sharing of ofsaa on the internet is rare.
Symptoms
There are many error messages. The important error section is truncated as follows:
<Jan 12,201 5 5:59:46 CST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
Weblogic. application. ModuleException: [HTTP: 101216] Servlet: "FICMaster" failed to preload on startup in Web application: "/OFSAA73 ".
Java. lang. NullPointerException
At com. iflex. fic. common. Log4jLogger. initialize (Log4jLogger. java: 116)
At com. iflex. fic. common. Log4jLogger. initializeLog4j (Log4jLogger. java: 55)
At com. iflex. fic. ficml. FICMaster. init (FICMaster. java: 127)
Cause
1. The Data Source for FICMASTER was not created (under JDBC), it was only created for Infodom.
2. The entry for Infodom on the Weblogic server did not match the corresponding entry from web. xml.
3. Deployment was created without having the infrastructure server up.
4. User didn't have full privileges on the deployment directories: the *. ear and *. war dirs.
5. The user who started Weblogic was ofsaa user and not the user who installed weblogic.
This problem is generally caused by the above five situations. This error is caused by an error in creating the FICMASTER data source, which causes the program to fail to start after deployment.
Solution
See Cannot Start Weblogic for OFSAA On Solaris-Missing ejb statelesscachebeanbean (Document ID 1240965.1)
Check the cause in sequence in the document and try to solve the problem as follows:
1. Create a DataSource and add a new entry for it in web. xml under WEB-INF.
Then, in the last deployment step: StateLessCacheBeanBean will show up under EJBs and also a link pointing to WEB-INF/lib/webcache. jar.
2. Re-create the Data Source entry for Infodom on the Weblogic server to match the entry from web. xml.
3. Start./reveleusstartup. sh, re-create the deployment and then upload it again.
4. Grant full permissions on the deployment ear folder by running chmod 777 command.
5. Start Weblogic (startWeblogic. sh-d64) as the user who installed Weblogic.