1. Home
  2. Development
  3. RE: DeveloperStudio failed to start

RE: DeveloperStudio failed to start

michael darretta, modified 9 Years ago.
DeveloperStudio failed to start
New Member Posts: 18 Join Date: 8/5/15 Recent Posts
a java runtime environment(jre) or Java Development Kit (JDK) must be available in order to run DeveloperStudio. No Java Virtual Machine was found after searching the following locations:
c:\liferay\liferay-developer-studio\DeveloperStudio\jre\bin\javaw.exe
javaw.exe in your current PATH.
michael darretta, modified 9 Years ago.
RE: DeveloperStudio failed to start
New Member Posts: 18 Join Date: 8/5/15 Recent Posts
tried adding VM to developerstudio.ini file but did not work.

-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.200.v20150204-1316
-product
com.liferay.studio.product.ui.studio
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
384M
-showsplash
com.liferay.studio.product.ui
-vm C:\jdk1.7.0_79\bin\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.6
-Xms40m
-Xmx1024m
-Dsun.java2d.noddraw=true
thumbnail
David H Nebinger, modified 9 Years ago.
RE: DeveloperStudio failed to start
Liferay Legend Posts: 14933 Join Date: 9/2/06 Recent Posts
set the JAVA_HOME environment variable to C:\jdk1.7.0_79 and add C:\jdk1.7.0_79\bin to the PATH.
michael darretta, modified 9 Years ago.
RE: DeveloperStudio failed to start
New Member Posts: 18 Join Date: 8/5/15 Recent Posts
I did that and now i get "Failed to Create Java Virtual Machine"
michael darretta, modified 9 Years ago.
RE: DeveloperStudio failed to start
New Member Posts: 18 Join Date: 8/5/15 Recent Posts
i took the 384M out of the ini file and it starts now.

but it hangs up after starting tomcat.
website comes up but studio keeps hanging.

ran better on java 1.6
thumbnail
David H Nebinger, modified 9 Years ago.
RE: DeveloperStudio failed to start
Liferay Legend Posts: 14933 Join Date: 9/2/06 Recent Posts
Then just use 1.6 for the IDE. You don't have to run dev studio under 1.7 or 1.8...
thumbnail
Yanan Yuan, modified 9 Years ago.
RE: DeveloperStudio failed to start
Junior Member Posts: 89 Join Date: 10/8/11 Recent Posts
Hello Michael,

Studio should use default java in computer, I'm not sure why it doesn't on your side. Can you try reset the JAVA_HOME and restart your computer?

That's better to add the following codes in DeveloperStudio.ini file.

-vm
C:\jdk1.7.0_79\bin\javaw.exe


I did that and now i get "Failed to Create Java Virtual Machine"


I think it's because your computer didn't have enough space and you can try using 256M instead of 384M.
michael darretta, modified 9 Years ago.
RE: DeveloperStudio failed to start (Answer)
New Member Posts: 18 Join Date: 8/5/15 Recent Posts
yes, i think the space issue is causing a problem.
some of our applications have some 1.7 code that errors with 1.6.
perhaps we can change the code or upgrade our machines to 64bit 8GB mem.

Thank You
Chanakya P, modified 2 Years ago.
RE: DeveloperStudio failed to start
Junior Member Posts: 72 Join Date: 2/17/14 Recent Posts

Hi All,


Is there any solution?

DeveloperStudio automatically closed when am trying to open studio.

 

Can any one help me out.

thumbnail
Olaf Kock, modified 7 Years ago.
RE: DeveloperStudio failed to start
Liferay Legend Posts: 6441 Join Date: 9/23/08 Recent Posts
Chanakya P:
Is there any solution?

DeveloperStudio automatically closed when am trying to open studio.

without a proper error message it's hard to say. I think that the description above was quite good, and it matched my expectations and experiences.

If you absolutely don't get an error message popping up, it might be good to start DevStudio from the command line. Sometimes this is more enlightning than the mouseclick, because the console doesn't go away and might contain an error message.

 

 

 

 

Chanakya P, modified 2 Years ago.
RE: DeveloperStudio failed to start
Junior Member Posts: 72 Join Date: 2/17/14 Recent Posts

Hi Olaf kock,

 

Thanks for your reply.

 

Error:

 

at ch.qos.logback.core.util.DynamicClassLoadingException: Failed to instantiate type ch.qos.logback.core.rolling.RollingFileAppender
        at      at ch.qos.logback.core.util.OptionHelper.instantiateByClassNameAndParameter(OptionHelper.java:73)
        at      at ch.qos.logback.core.util.OptionHelper.instantiateByClassName(OptionHelper.java:48)
        at      at ch.qos.logback.core.util.OptionHelper.instantiateByClassName(OptionHelper.java:35)
        at      at ch.qos.logback.core.joran.action.AppenderAction.begin(AppenderAction.java:54)
        at      at ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java:275)
        at      at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:147)
        at      at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:129)
        at      at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:50)
        at      at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:149)
        at      at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:135)
        at      at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:99)
        at      at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:49)
        at      at org.eclipse.m2e.logback.configuration.LogPlugin.loadConfiguration(LogPlugin.java:185)
        at      at org.eclipse.m2e.logback.configuration.LogPlugin.configureLogback(LogPlugin.java:144)
        at      at org.eclipse.m2e.logback.configuration.LogPlugin.access$2(LogPlugin.java:107)
        at      at org.eclipse.m2e.logback.configuration.LogPlugin$1.run(LogPlugin.java:62)
        at      at java.util.TimerThread.mainLoop(Timer.java:555)
        at      at java.util.TimerThread.run(Timer.java:505)
Caused by: java.lang.ClassNotFoundException: ch.qos.logback.core.rolling.RollingFileAppender cannot be found by ch.qos.logback.classic_1.1.2.v20160208-0839