Hi again,
Well, I could easily come up with a patch that essentially duplicates the "start server in JVM or not" logic and passes the info on to HTTPSession (I actually already had that patch done before I came up with the other one).
You can find that patch attached, again *COMPLETELY UNTESTED*. It should get rid of the pointless TCP overhead, but it does not fix the "magic" behaviour.
Kind regards, Ralf