10.5 EAP, problems with new Jetty integration

When I tried to start a Jetty server, I get the exception shown here.
The server does not start.

Donald

/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home/bin/java
-DSTOP.PORT=0 -Dcom.sun.management.jmxremote=
-Dcom.sun.management.jmxremote.port=1099
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false -DOPTIONS=jmx
-Didea.launcher.port=7534
-Didea.launcher.bin.path=/Applications/IdeaX-IU-106.330.app/bin
-Dfile.encoding=MacRoman -classpath
start.jar:/Applications/IdeaX-IU-106.330.app/lib/idea_rt.jar
com.intellij.rt.execution.application.AppMain org.eclipse.jetty.start.Main
63270
STOP.KEY=1hzeb9d941ou8
2011-04-04 12:25:31.391:WARN::Config error at 
java.lang.IllegalStateException: No object for id=DeploymentManager
java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.eclipse.jetty.start.Main.invokeMain(Main.java:477)
     at org.eclipse.jetty.start.Main.start(Main.java:623)
     at org.eclipse.jetty.start.Main.parseCommandLine(Main.java:273)
     at org.eclipse.jetty.start.Main.main(Main.java:81)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.intellij.rt.execution.application.AppMain.main(AppMain.java:115)
Caused by: java.lang.IllegalStateException: No object for
id=DeploymentManager
     at
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.refObj(XmlConfiguration.java:826)
     at
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:394)
     at
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:342)
     at
org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:285)
     at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1221)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1156)
     ... 13 more

Usage: java -jar start.jar
        java -jar start.jar --help  # for more information

Process finished with exit code 254
Disconnected from server

5 comments
Comment actions Permalink

Hello,

Please, ensure you have included in the server configuration the following configuration files:
<JETTY HOME>/etc/jetty.xml
<JETTY HOME>/etc/jetty-deploy.xml
<JETTY HOME>/etc/jetty-webapps.xml
<JETTY HOME>/etc/jetty-contexts.xml
<JETTY HOME>/etc/jetty-jmx.xml

You should be able to add the files to the server configuration via either application server configuration form
or via run/debug configuration form.

If you will still have troubles, please provide screenshots of application server configuration form and run/debug configuration form.

Regards,
Michael

0
Comment actions Permalink

Application server configuration form

On 4/5/11 3:14 PM, Michael Golubev wrote:

Hello,

>

Please, ensure you have included in the server configuration the following configuration files:
  <JETTY HOME>/etc/jetty.xml
  <JETTY HOME>/etc/jetty-deploy.xml
  <JETTY HOME>/etc/jetty-webapps.xml
  <JETTY HOME>/etc/jetty-contexts.xml
  <JETTY HOME>/etc/jetty-jmx.xml

>

  You should be able to add the files to the server configuration via either application server configuration form
  or via run/debug configuration form.

>

  If you will still have troubles, please provide screenshots of application server configuration form and run/debug configuration form.



Attachment(s):
ideaJetty001.tiff
0
Comment actions Permalink

Run/debug configuration form.

On 4/5/11 3:14 PM, Michael Golubev wrote:

Hello,

>

Please, ensure you have included in the server configuration the following configuration files:
  <JETTY HOME>/etc/jetty.xml
  <JETTY HOME>/etc/jetty-deploy.xml
  <JETTY HOME>/etc/jetty-webapps.xml
  <JETTY HOME>/etc/jetty-contexts.xml
  <JETTY HOME>/etc/jetty-jmx.xml

>

  You should be able to add the files to the server configuration via either application server configuration form
  or via run/debug configuration form.

>

  If you will still have troubles, please provide screenshots of application server configuration form and run/debug configuration form.



Attachment(s):
ideaJetty002.tiff
0
Comment actions Permalink

Hello,

I've submitted 2 problems, each of them may affect Jetty 7.3.x support (plugin was originally developed against Jetty 7.2.2).
You may track it at the http://youtrack.jetbrains.net/issue/IDEA-67604 and http://youtrack.jetbrains.net/issue/IDEA-67603.
We will hopefully fix it in the one of the upcoming builds.

From what I understand, you may have already experienced the problem with #67603 (which does NOT depends on the actual jetty version).

Please ensure that the order of the configs in jetty.ini is the same as in your app server from screen shot.
In particular, I was able to reproduce the same exception after moving the jetty-webapps above jetty-deploy _in the ini file_.

Regards,
Michael

0
Comment actions Permalink

I downgraded to 7.2.2 and it worked.

Thank you for mentioning the version issue - I don't care all that much
about which version we use since Jetty is just a convenient platform on
my desktop. IT currently has us using Tomcat in production (though that
could change at any time).

Donald

On 4/6/11 11:27 AM, Michael Golubev wrote:

Hello,

>

I've submitted 2 problems, each of them may affect Jetty 7.3.x support (plugin was originally developed against Jetty 7.2.2).
You may track it at the http://youtrack.jetbrains.net/issue/IDEA-67604 and http://youtrack.jetbrains.net/issue/IDEA-67603.
We will hopefully fix it in the one of the upcoming builds.

>

From what I understand, you may have already experienced the problem with #67603 (which does NOT depends on the actual jetty version).

>

Please ensure that the order of the configs in jetty.ini is the same as in your app server from screen shot.
In particular, I was able to reproduce the same exception after moving the jetty-webapps above jetty-deploy in the ini file.


0

Please sign in to leave a comment.