- This topic has 29 replies, 10 voices, and was last updated 19 years, 5 months ago by
.
-
Posts
-
Ok, tbrantb, I need some help reproducing this.
I put Tomcat in C:\Program Files\tomcat-5.5.9 and I put my JDK under: C:\Program Files\Java\jdk1.5.0_04
I changed all the Tomcat home and JDK settings and launched/stopped it with no problems. So where do you see my setup differs from yours. I’m using 4.0.2 BTW on Eclipse 3.1.1 on Windows XP (JDK 1.5.0_04)
The problem does not occur with tomcat. The problem occurs with the Sun App Server 8.1. I have it installed under C:\Sun\AppServer
We’ve replicated the problem internally on the Sun connector, have entered a PR and a fix is targeted for 4.1 milestone 1 on Monday. Thanks for helping us isolate the problem. We do appreciate it.
relmore,
We don’t have a connector for Sun app server 7 at this time, so it would be hard to walk through a possible workaround as Sun has signifigantly changes their launch model between even monitor revisions (8.0 to 8.1).You can however try launching the app server externally and still use our deployment and remote debugging assuming the app server supports JSR-45 (if it doesn’t JSP debugging won’t work, but Class debugging should still work): http://www.myeclipseide.com/images/tutorials/quickstarts/remotedebugging/
@support-rkalla wrote:
relmore,
We don’t have a connector for Sun app server 7 at this time, so it would be hard to walk through a possible workaround as Sun has signifigantly changes their launch model between even monitor revisions (8.0 to 8.1).You can however try launching the app server externally and still use our deployment and remote debugging assuming the app server supports JSR-45 (if it doesn’t JSP debugging won’t work, but Class debugging should still work): http://www.myeclipseide.com/images/tutorials/quickstarts/remotedebugging/
Thanks.
I followed your instructions and got the following error message when executing the debug process: Failed to connect to remote VM.
Any thoughts?
Were you running the application server in debug mode? Please double check the docs on how to do that, I don’t know off the top of my head.
I just installed MyEclipse 4.0.3 and Sun Java System Application Server Platform Edition 8.1_02 (build b06-fcs) and I am still having this problem as well. My JDK is in the default location.
Sorry, I didn’t see that there were two pages in the thread so I missed the post about it being fixed in 4.1
Thankscalebphillips,
More specifically you mean you are getting a popup error: “Cannot find main class”?If so, and if your JDK is installed into the default location of C:\Program Files\Java\jdk<blah blah>
then try this:
1) Copy your jdk<blah blah> directory (e.g. jdk1.5.0_06) to C:\
2) Adjust your JDK settings in MyEclipse to point to this new JDK location
3) Set the JDK as your launcher for Sun App Server, launch it.Did it work? This bug with spaces should be fixed in 4.1, sorry about this.
I have error
[#|2005-12-10T21:31:46.093+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\AppServer\imq\bin].|#]
[#|2005-12-10T21:31:46.109+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
[#|2005-12-10T21:31:48.250+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2005-12-10T21:31:48.875+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.stream.err|_ThreadID=10;|Exception in thread “main” |#]
[#|2005-12-10T21:31:48.890+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.stream.err|_ThreadID=10;|java.lang.ExceptionInInitializerError
at com.sun.enterprise.security.SecurityLifecycle.onInitialization(SecurityLifecycle.java:59)
at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:215)
at com.sun.enterprise.server.PEMain.run(PEMain.java:284)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: java.lang.IllegalStateException: \config\keystore.jks (Системе не удается найти указанный путь)
at com.sun.enterprise.security.SecuritySupportImpl.loadStores(SecuritySupportImpl.java:80)
at com.sun.enterprise.security.SecuritySupportImpl.<init>(SecuritySupportImpl.java:48)
at com.sun.enterprise.security.SecuritySupportImpl.<init>(SecuritySupportImpl.java:43)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at com.sun.enterprise.pluggable.PluggableFeatureFactoryBaseImpl.invoke(PluggableFeatureFactoryBaseImpl.java:53)
at $Proxy0.getSecuritySupport(Unknown Source)
at com.sun.enterprise.security.SecurityUtil.getSecuritySupport(SecurityUtil.java:338)
at com.sun.enterprise.security.SSLUtils.<clinit>(SSLUtils.java:72)
… 4 more
|#]
My appserver install in
C:\Sun\AppServer\
My jdk(1.5.02) install in
C:\Sun\AppServer\jdk\
=(((This looks like your keystore may be corrupted:
Caused by: java.lang.IllegalStateException: \config\keystore.jks (Системе не удается найти указанный путь)
Do me a favor and reinstall Sun App Server to a new location, like C:\Temp\AppServer and try and setup and use that instance, see if it works.
I just wanted to say, that the original bug in question with starting the Sun App Server v8.1 really has been resolved in MyElipse release 4.1.
Thanks to the MyEclipse staff for fixing this one and struggling through our complaints.
