This content has been marked as final. Show 5 replies
Hi.1 person found this helpful
Usually, this happens when there is no JDK in the PATH system variable. JDeveloper and WLS will work, but some external tools will fail. Can you please ensure that you have a reference to the <tt>bin</tt> subfolder of a Java SE 6 JDK in it? You should get something like this when you execute <tt>java -version</tt> on the command line:
java version "1.6.0_37" Java(TM) SE Runtime Environment (build 1.6.0_37-b06) Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01, mixed mode)
Hi,1 person found this helpful
the project you are trying to deploy, does it have a blank in its path? If so, try deploying it from a directory location that does not contain blanks
When i type the command in I get
java version "1.7.0_13"
Java (TM) Client VM ( build 1.7.0_13-b20, mixed mode sharing )
Java Hotspot(TM) Client VM ( build 23.7-b01, mixed mode , sharing)
The funny thing is eventually I get the deploy to work... but I have not been able to figure out what happens to make it work....
Again thank you for the assistance.
I set a local var on my machine and now things seem to work...
Variable Name : JAVAOPTIONS
Variable Name : -Xms256m -Xmx512m
(both these values without any quotes)
I found this via google.. not 100% sure what it does but ....
Those settings change the amounts of memory available to the JVM. Xms is the initial size of the pool while Xmx is the maximum size.1 person found this helpful