I do not see any reasons. I have tested the samples and they work. Could you paste the content of your SU and the console log ?
On 8/31/06, jsolderitsch <[EMAIL PROTECTED]> wrote:
jsolderitsch wrote: > > I have tried both the August 29 and August 30 binary snapshots. > > With 3.0M2, I see a log message reporting jetty starting up. I can reach a > port 8192 url as expected. > > With the snapshots, I see no such messages, and any attempt to reach a url > on my servicemix machine with port 8192 results in a can't conect to > server message. > > If this is a known issue, which snapshot has a working jetty integration? > > Jim > I really need some advice here. I saw in another post that jetty is supposed to start automatically if you use an http su. My service assembly DOES include such an su. With 3.0M2, deploying my sa causes jetty to start as expected. With the last 3 days snapshots, this is NOT the case. A deployment that works just fine with 3.0M2 now fails to work. I learned that you can force jetty to start with the proper servicemix configuration entry. But I need an example of the syntax I need to add to servicemix.xml or servicemix.conf to make this happen. Any reason why the startup behavior with the snapshots is different than the last milestone? Jim -- View this message in context: http://www.nabble.com/Is-jetty-broken-in-latest-snapshots--tf2191258.html#a6086662 Sent from the ServiceMix - Dev forum at Nabble.com.
-- Cheers, Guillaume Nodet
