Application gets automatically undeployed after OC4J container restart

-
Whenever we were restarting the OC4J Container , we observed that some of the applications automatically gets undeployed and are not visible in enterprise manager console.We found below errors in the container logs which are due to the wrong entries in server.xml and default-website.xml file Then we deleted those physical appliation folders from the $OH/j2ee/testoc4j/applications and restarted the container and then deployed the J2EE applications again. It worked even after the restart.


Issue :- opmn referreing to wrong entries in server.xml and default-website.xml file.

Solution :- Delete application folders from $OH/j2ee/testoc4j/applications and redeployed the applications.

#############


09/06/21 17:27:13 [SEVERE]: Error instantiating application at file $OH/j2ee/testoc4j/applications/test.ear: Unable to get A


pplicationConfig for test1 : Error creating deployment directory: IO Error: error in opening zip file


09/06/21 17:27:13 [SEVERE]: Error instantiating application at file/j2ee/testoc4j/applications/test1.ear:


Unable to get ApplicationConfig for test1 : Error creating deployment directory: IO Er


ror: error in opening zip file


09/06/21 17:27:13 [SEVERE]: Error instantiating application at file/j2ee/testoc4j/applications/test2.ear


: Unable to get ApplicationConfig for test2: Error creating deployment directory: IO Er


ror: error in opening zip file


09/06/21 17:27:13 [SEVERE]: Error instantiating application at file/j2ee/testoc4j/applications/test4.ear: Unable to get Appl


icationConfig for test4 : Error creating deployment directory: IO Error: error in opening zip file


09/06/21 17:27:13 [SEVERE]: cannot update a configuration file because configuration parsing is failed. please correct the problem and restart


oc4j.

############

Comments

Iran Vasquez said…
Hi,
You find really what's the problem?
I have this and I can't resolve :(
Thanks.
January 26, 2013 at 7:09 PM
Vinay Singla said…
just follow the steps provided.
March 1, 2015 at 4:10 PM
Post a Comment

Popular posts from this blog

Identity Service Authentication failure

-
Identity Service Authentication failure --2010-01-14 10:34:33,032-- --ERROR-- --oracle.bpel.services.workflow-- --::-- Identity Service Authentication failure. Identity Service Authentication failure. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable. ORABPEL-10528 Identity Service Authentication failure. Identity Service Authentication failure. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable. at oracle.tip.pc.services.identity.jazn.xml.XMLAuthenticationService.authenticateUser(XMLAuthenticationService.java:150) at oracle.tip.pc.services.identity.jazn.xml.XMLIdentityService.authenticateUser(XMLIdentityService.java:426) at oracle.bpel.services.workflow.verification.impl.VerificationService.authenticateUser(VerificationService.java:341) 1) Check username/password used in worklist is correct or not. 2) Add correct password in the descriptor of BPEL Process throwi
Read more

Weblogic server is not starting up ; java.lang.AssertionError

-
  If the weblogic server is not starting up and giving the below error , please follow the below solution :- Error :- #Aug 18, 2014 12:34:29 AM PDT# #Notice# #WebLogicServer# #BEA-000365# #Server state changed to STARTING# #Aug 18, 2014 12:34:29 AM PDT# #Info# #WorkManager# #BEA-002900# #Initializing self-tuning thread pool# #Aug 18, 2014 12:34:29 AM PDT# #Notice# #Log Management# #BEA-170019# #The server log file /u01/app/oracle/config/domains/Vinay/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.# #Aug 18, 2014 12:34:29 AM PDT# #Critical# #WebLogicServer# #BEA-000386# #Server subsystem failed. Reason: java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine. java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine.                 a
Read more

jstatd error : Could not create remote object : access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write)

-
While running "./jstatd -J-Djava.security.policy=jstatd.all.policy &" command , below error is getting encountered Error :- Could not create remote object access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write) java.security.AccessControlException: access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264) at java.security.AccessController.checkPermission(AccessController.java:427) at java.lang.SecurityManager.checkPermission(SecurityManager.java:536) at java.lang.System.setProperty(System.java:699) at sun.tools.jstatd.Jstatd.main(Jstatd.java:122) Cause :- The "access denied" error is expected, because "jstatd" requires a security policy file specified with the "java.security.policy" system property, if there is no security manager running on the machine. Solution :- 1) cd $ORACLE_HOME/jdk
Read more