Thanks Joakim. After adding the extra debug line, I see similar output to you [1].
I know you don't see port 1099 in netstat, but are you able to telnet to it, with, e.g. "telnet localhost 1099"?
I'm not sure if my problem is Jetty, or false expectations that it should be responding to TCP on port 1099. To that end, I also tried using the jmx plugin to eclipse, but I'm getting the same "connection refused" exception. For some reason my Jetty seems not to be listening on port 1099.
[1] output I get when starting the server, after adding "-Dorg.eclipse.jetty.jmx.MBeanContainer.LEVEL=DEBUG":
2013-10-22 09:41:15.090:DBUG:oejj.MBeanContainer:main: beanAdded org.eclipse.jetty.server.Server@137a9034->org.eclipse.jetty.jmx.MBeanContainer@67e1ab17
2013-10-22 09:41:15.094:DBUG:oejj.MBeanContainer:main: Registered org.eclipse.jetty.jmx:type=mbeancontainer,id=0
2013-10-22 09:41:15.361:DBUG:oejj.MBeanContainer:main: beanAdded ServerConnector@2921304c{HTTP/1.1}{0.0.0.0:8080}->org.eclipse.jetty.jmx.MBeanContainer@67e1ab17
2013-10-22 09:41:15.375:DBUG:oejj.MBeanContainer:main: beanAdded org.eclipse.jetty.deploy.DeploymentManager@69cb839f->org.eclipse.jetty.jmx.MBeanContainer@67e1ab17
2013-10-22 09:41:17.359:DBUG:oejj.MBeanContainer:main: beanAdded org.eclipse.jetty.rewrite.handler.RewriteHandler@46a01a84->org.eclipse.jetty.jmx.MBeanContainer@67e1ab17
2013-10-22 09:41:17.367:DBUG:oejj.MBeanContainer:main: beanAdded org.eclipse.jetty.server.handler.HandlerCollection@6a0e4b8a->org.eclipse.jetty.jmx.MBeanContainer@67e1ab17
2013-10-22 09:41:17.383:DBUG:oejj.MBeanContainer:main: beanAdded org.eclipse.jetty.server.handler.MovedContextHandler$Redirector@2bfd8364->org.eclipse.jetty.jmx.MBeanContainer@67e1ab17
2013-10-22 09:41:17.383:DBUG:oejj.MBeanContainer:main: beanAdded
o.e.j.s.h.MovedContextHandler@71d5930f{/oldContextPath,null,AVAILABLE}->org.eclipse.jetty.jmx.MBeanContainer@67e1ab17
2013-10-22 09:41:17.498:DBUG:oejj.MBeanContainer:main: beanAdded org.eclipse.jetty.servlet.ServletHandler@6f6c349e->org.eclipse.jetty.jmx.MBeanContainer@67e1ab17
2013-10-22 09:41:17.506:DBUG:oejj.MBeanContainer:main: beanAdded org.eclipse.jetty.security.ConstraintSecurityHandler@415abfe1->org.eclipse.jetty.jmx.MBeanContainer@67e1ab17
2013-10-22
09:41:17.506:DBUG:oejj.MBeanContainer:main: beanAdded org.eclipse.jetty.server.session.SessionHandler@4d77ec7b->org.eclipse.jetty.jmx.MBeanContainer@67e1ab17
2013-10-22 09:41:17.511:DBUG:oejj.MBeanContainer:main: beanAdded org.eclipse.jetty.servlet.ErrorPageErrorHandler@6c1e5d2f->org.eclipse.jetty.jmx.MBeanContainer@67e1ab17
2013-10-22 09:41:17.515:DBUG:oejj.MBeanContainer:main: beanAdded
o.e.j.w.WebAppContext@3af5087d{/test-spec,[file:/private/var/folders/b6/1hrm44bs67sf00dhml3ntldxcr632h/T/jetty-0.0.0.0-8080-test-spec.war-_test-spec-any-/webapp/, jar:file:/private/var/folders/b6/1hrm44bs67sf00dhml3ntldxcr632h/T/jetty-0.0.0.0-8080-test-spec.war-_test-spec-any-/webapp/WEB-INF/lib/test-web-fragment-9.0.6.v20130930.jar!/META-INF/resources/],AVAILABLE}{/Users/jric/Downloads/jetty-distribution-9.0.6.v20130930/webapps.demo/test-spec.war}->org.eclipse.jetty.jmx.MBeanContainer@67e1ab17
+ 35 more similar lines....
On Monday, October 21, 2013 5:16 PM, Joakim Erdfelt
<joakim@xxxxxxxxxxx> wrote:
With --exec enabled, i can still connect, albeit to the forked jetty process, not start.jar