[harmengosen]

Ok, I’m quite excited about the new 5.5 version of MyEclipse. It finally supports Java EE 5, so I started immediately setting up such a project. I use the following configuration:
– The bundled version of MyEclipse 5.5.1 GA (which includes Eclipse 3.2.2).
– Sun AppServer PE 9 (non-bundled version; just the AppServer)
When I got everything setup, I fired up MyEclipse and created a new EAR project, with an included WebApplication. I just let the wizard do it’s work and changed nothing. Next, I configured a connector to the Sun Appserver 9, which looked as shown in the forum FAQs. I then deployed my ear project to the server and fired it up. Now the AppServer starts fine, no problem with that. The problem starts when I try to load the automatically generated .jsp. The following log excerpt shows the problem (in my opinion):

[#|2007-06-13T22:04:19.625+0200|SEVERE|sun-appserver-pe9.0|org.apache.jasper.compiler.Compiler|_ThreadID=12;_ThreadName=httpWorkerThread-8080-1;_RequestID=1d9c2c08-22ab-446e-9cf8-224af958d998;|Javac exception 
Error running javac.exe compiler
    at org.apache.tools.ant.taskdefs.compilers.DefaultCompilerAdapter.executeExternalCompile(DefaultCompilerAdapter.java:473)
    at org.apache.tools.ant.taskdefs.compilers.JavacExternal.execute(JavacExternal.java:47)
    at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:931)
    at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:757)
    at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:428)
    at org.apache.jasper.compiler.Compiler.compile(Compiler.java:528)
    at org.apache.jasper.compiler.Compiler.compile(Compiler.java:507)
    at org.apache.jasper.compiler.Compiler.compile(Compiler.java:495)
    at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:530)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:412)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:318)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
    at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
    at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
    at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
    at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
    at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
    at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
    at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
    at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
    at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
Caused by: java.io.IOException: CreateProcess: javac.exe -classpath D:\SunAS9\lib\activation.jar;D:\SunAS9\lib\admin-cli.jar;D:\SunAS9\lib\appserv-admin.jar;D:\SunAS9\lib\appserv-cmp.jar;D:\SunAS9\lib\appserv-deployment-client.jar;D:\SunAS9\lib\appserv-ext.jar;D:\SunAS9\lib\appserv-jstl.jar;D:\SunAS9\lib\appserv-jwsacc.jar;D:\SunAS9\lib\appserv-launch.jar;D:\SunAS9\lib\appserv-rt.jar;D:\SunAS9\lib\appserv-tags.jar;D:\SunAS9\lib\appserv-upgrade.jar;D:\SunAS9\lib\appserv-ws.jar;D:\SunAS9\lib\com-sun-commons-launcher.jar;D:\SunAS9\lib\com-sun-commons-logging.jar;D:\SunAS9\lib\dbschema.jar;D:\SunAS9\lib\j2ee-svc.jar;D:\SunAS9\lib\j2ee.jar;D:\SunAS9\lib\javaee.jar;D:\SunAS9\lib\jhall.jar;D:\SunAS9\lib\jmxremote_optional.jar;D:\SunAS9\lib\jsf-impl.jar;D:\SunAS9\lib\mail.jar;D:\SunAS9\lib\sun-appserv-ant.jar;D:\SunAS9\lib\toplink-essentials-agent.jar;D:\SunAS9\lib\toplink-essentials.jar;D:\SunAS9\imq\lib\fscontext.jar;D:\SunAS9\imq\lib\imq.jar;D:\SunAS9\imq\lib\imqadmin.jar;D:\SunAS9\imq\lib\imqbroker.jar;D:\SunAS9\imq\lib\imqjmx.jar;D:\SunAS9\imq”
    at java.lang.ProcessImpl.create(Native Method)
    at java.lang.ProcessImpl.<init>(Unknown Source)
    at java.lang.ProcessImpl.start(Unknown Source)
    at java.lang.ProcessBuilder.start(Unknown Source)
    at java.lang.Runtime.exec(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec(Execute.java:834)
    at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:435)
    at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:449)
    at org.apache.tools.ant.taskdefs.compilers.DefaultCompilerAdapter.executeExternalCompile(DefaultCompilerAdapter.java:470)
    ... 36 more
--- Nested Exception ---
java.io.IOException: CreateProcess: javac.exe -classpath D:\SunAS9\lib\activation.jar;D:\SunAS9\lib\admin-cli.jar;D:\SunAS9\lib\appserv-admin.jar;D:\SunAS9\lib\appserv-cmp.jar;D:\SunAS9\lib\appserv-deployment-client.jar;D:\SunAS9\lib\appserv-ext.jar;D:\SunAS9\lib\appserv-jstl.jar;D:\SunAS9\lib\appserv-jwsacc.jar;D:\SunAS9\lib\appserv-launch.jar;D:\SunAS9\lib\appserv-rt.jar;D:\SunAS9\lib\appserv-tags.jar;D:\SunAS9\lib\appserv-upgrade.jar;D:\SunAS9\lib\appserv-ws.jar;D:\SunAS9\lib\com-sun-commons-launcher.jar;D:\SunAS9\lib\com-sun-commons-logging.jar;D:\SunAS9\lib\dbschema.jar;D:\SunAS9\lib\j2ee-svc.jar;D:\SunAS9\lib\j2ee.jar;D:\SunAS9\lib\javaee.jar;D:\SunAS9\lib\jhall.jar;D:\SunAS9\lib\jmxremote_optional.jar;D:\SunAS9\lib\jsf-impl.jar;D:\SunAS9\lib\mail.jar;D:\SunAS9\lib\sun-appserv-ant.jar;D:\SunAS9\lib\toplink-essentials-agent.jar;D:\SunAS9\lib\toplink-essentials.jar;D:\SunAS9\imq\lib\fscontext.jar;D:\SunAS9\imq\lib\imq.jar;D:\SunAS9\imq\lib\imqadmin.jar;D:\SunAS9\imq\lib\imqbroker.jar;D:\SunAS9\imq\lib\imqjmx.jar;D:\SunAS9\imq”
    at java.lang.ProcessImpl.create(Native Method)
    at java.lang.ProcessImpl.<init>(Unknown Source)
    at java.lang.ProcessImpl.start(Unknown Source)
etc.

The javac gets called with too many jars for arguments, making the commandline too long. The OS truncates it and the thing won’t execute. I’ve seen lots of references to this problem but never answers. Thing is, when I start the Appserver from outside MyEclipse, the application works flawlessly. However, this is not my preferred way of developing apps.

Can anybody help me with this problem? Seems to me sombody out there must’ve run into the same problem!

Thanks in advance!

-Harry

[Riyad Kalla]

What platform are you on? Command length issues persisted into Windows 2k, but stopped (as far as I can tell) with Windows XP… I haven’t seen issues like this reported in almost 2 years, but they certainly used to happen more often in the past (the workaround was always to reinstall to a short path, but from the looks of it, your install path is as good/short as it gets! 🙂

[harmengosen]

Hello Riyad,

thanks for your reply! It’s much appreciated!

Now to your question: i’m running on Windows XP Professional.
To be honest, this is my second installment of SunAS9, since i installed it the first time in “D:\Installed\Java\Sun App…”. Well you guessed it, the path was too long. When installing for the second time, i chose a shorter path. Problem is that the free space is just filled with more jars, so no solution there.
Isn’t it some configuration problem since i’m able to run the application when SunAS9 is started outside of Eclipse?

[Riyad Kalla]

I had an idea… try and make sure that you are running MyEclipse using JDK 1.5.0_08 or later (you can check quickly from MyEclipse > Installation Summary > Installation Details) and then make sure you are starting Sun App Server with either the same JDK, or a later one as well.

[harmengosen]

I checked and got the following results:
The MyEclipse installation summary says

Java version=1.5.0_11

which probably comes from the bundled jre with MyEclipse. This because the same installation summary says that Eclipse is started with the following argument:

-vm
D:\Installed\MyEclipse 5.5.1 GA\jre\bin\javaw.exe

Now the runtime i use (by looking in the preferences under “installed JREs”) is JRE 1.6.0. Last but not least, the Application Server uses JDK 1.6.0, the same one of which the aforementioned JRE 1.6.0. is part of.
I tried something by changing the vm MyEclipse starts with to the same one in JDK1.6.0. This unfortunately did not work.
To be quite honest, i’m a little lost here . . . any suggestions?

[Riyad Kalla]

To be quite honest, i’m a little lost here . . . any suggestions?

That makes two of us…

wait I just had a thought… when you setup the Sun App Server connector, did you leave all the Paths boxes blank? MyEclipse will pickup all libraries by default automatically… if you added them all manually to that screen it’s possible every JAR is being added twice, which is why you are getting a crazy long command line…

[harmengosen]

No, i didn’t leave the paths boxes blank. I used the fileselector to fill in the Sun AS home directory and all other fields (with the exception of the Optional Program Arguments field were filled with default values. I just left them as they were since their values looked ok to me.
I digged a little deeper in the SunAS startup logs, which are generated when you start the AS when clicking on its icon in the Servers view, and found this line:

[#|2007-06-23T21:39:52.098+0200|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;Java HotSpot(TM) Client VM;1.5.0_11;Sun Microsystems Inc.;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.5.0_11] from [Sun Microsystems Inc.]|#]

This seems strange to me since i installed the SunAS again, telling it during the installation procedure to use JDK1.6.0. Furthermore, i started MyEclipse with the following line:

"D:\Installed\MyEclipse 5.5.1 GA\eclipse\eclipse.exe" -vm "D:\Installed\Java\jdk1.6.0\bin\javaw.exe"

In the MyEclipse installation Summary i can see that the 1.6.0 version indeed is used. So, somehow the SunAS is using the VM that was supplied with the MyEclipse bundle, despite the fact that i told it to use another VM.
Referencing to our previous discussion, i got the impression that it is critical that MyEclipse and SunAS use the same JDK/JRE, and therefore the same VM, to prevent loads of jars given as arguments to javac. What i found negates everything i try to do to make them use the same JDK/JRE. Could this be the source of the problem?

[harmengosen]

Hello Riyad,

i think i misunderstood you when you said ‘Paths boxes’. I now see that you probably meant one of the three sub panels of the Appserver configuration panel. I left them indeed blank. However, it focused my attention on the JDK subpanel; it said that the MyEclipse JDK was selected! I changed it to the JDK1.6.0 and everything now works fine! Great!
Thanks for pointing me in the right direction!

[Riyad Kalla]

ahhh very cool, thanks for catching that. I’m glad it’s working now.

[Author]

Posts