Dynapen
asked on
Deployment Directory Creation Problems OC4J 10.0.3 (Developer Preview)
I am trying to get the new OC4J container (10.0.3) to run on my box. After getting past a couple small bugs on the install, I am getting the following error when I try to start the container.
[code]
Error initializing server: Error creating deployment directory: D:\Development\TFAS\WebApp
04/04/23 11:41:22 Fatal error: Cannot instantiate ApplicationServerThread AND not in embedded mode - forcing exit
[/code]
If I remove the webapp descriptor mentioned from both the appliation and http-web xml files then the container will start fine.
Currently I am running the site under OC4J 9.0.3 (I think), and I have it's config files set to point to the development directory where I am coding from. (Yes, the purists will say this is a bad way, but it's a throw back to my ASP days, and it works for me so no soapbox comments on it). I am trying to find if there is another setting in 10g that I have to set to allow this to happen, or if there is something I am just screwing up, or if "heaven forbid" there is a bug in Oracle's beta.
If anyone has seen this and can help me out I would appreciate it.
[code]
Error initializing server: Error creating deployment directory: D:\Development\TFAS\WebApp
04/04/23 11:41:22 Fatal error: Cannot instantiate ApplicationServerThread AND not in embedded mode - forcing exit
[/code]
If I remove the webapp descriptor mentioned from both the appliation and http-web xml files then the container will start fine.
Currently I am running the site under OC4J 9.0.3 (I think), and I have it's config files set to point to the development directory where I am coding from. (Yes, the purists will say this is a bad way, but it's a throw back to my ASP days, and it works for me so no soapbox comments on it). I am trying to find if there is another setting in 10g that I have to set to allow this to happen, or if there is something I am just screwing up, or if "heaven forbid" there is a bug in Oracle's beta.
If anyone has seen this and can help me out I would appreciate it.
ASKER
I have that line commented out becuase I never got a warning about it not having a compiler defined. The error I get is in creating the deployment directory. What I am trying to find is the place where you can tell OC4J not to worry about auto unpacking anything. So that I can point it to the directory that houses my WEB-INF folder and let it go. For some reason though it keeps trying to insist that it needs to create the directory.
ASKER
Actually, the error I was getting where the app was creating the deployment directory seems to have been caused by using absolute paths for the directory where my app was to run from. As soon as I switched everything over to use relative paths, at least the container will initialize. Now granted I still get a separate error from the Log4J loading, but I want to research that farther before I start spending points to answer it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://www.theserverside.com/news/thread.tss?thread_id=24665
==========================
When I initially started the server, I got a message that there was no compiler defined in the server.xml file. I added the following line to server.xml:
<java-compiler name="jikes" bindir="D:\jikes\bin" in-process="false"/>
It seems that this is what was causing the problem. After I removed this line, everything seems to be working fine.
see above statement also..
best of luck..
R.K.