More information: When running from Terminal with "mvn jetty:run" or from within Eclipse using the M2E plugin (Run or Debug mode), it will create extra threads. When running from within Eclipse using RunJettyRun (Run or Debug mode), no extra threads are created and it works perfectly.
Could be the Maven plugin, perhaps. On Thu, Aug 28, 2014 at 4:17 PM, Michael Gentry <mgen...@masslight.net> wrote: > I can try Tomcat, but i'll be a day or two or so before I can get to that. > > mrg > > > > On Thu, Aug 28, 2014 at 3:35 PM, Lance Java <lance.j...@googlemail.com> > wrote: > >> Totally weird, can you try deploying to tomcat? It's worth a try to see if >> an issue with jetty. >> On 28 Aug 2014 19:36, "Michael Gentry" <mgen...@masslight.net> wrote: >> >> > Hi again Lance, >> > >> > 1) No proxy. Directly connecting to Jetty @ http://localhost:6789/.... >> > >> > 2) No other filters. I'm using Tapestry's IOC for services and trying >> to >> > keep things lean. >> > >> > FWIW, when I dropped the file in as a unit test, it would import just >> fine >> > using the T5 service without spawning extra threads, so I don't think >> it is >> > related to the T5 service itself (which make's sense, since the >> > onValidate/onSuccess events are being triggered more than once). >> > >> > Thanks, >> > >> > mrg >> > >> > >> > >> > On Thu, Aug 28, 2014 at 2:05 PM, Lance Java <lance.j...@googlemail.com> >> > wrote: >> > >> > > 1.Is your app sitting behind a proxy? (eg apache?). >> > > >> > > 2. Are there any other servlet filters we should know about? (eg >> spring?) >> > > >> > >> > >
