[EMAIL PROTECTED] wrote: >On 19 Sep, Marcel Ruff wrote: > > >>Peter Antman wrote: >> >> >> >>>On 19 Sep, Marcel Ruff wrote: >>> >>> >>> >>> >>>>Could you please add a >>>> >>>>Thread.currentThread().dumpStack(); >>>> >>>>into setExit() to find out who calls it? >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>Here you have it: >>> >>> >>> >>Thanks >>The only point i know of where we send an admin command 'exit' is the last >>test of our testsuite: >> >> xmlBlaster/testsuite/src/java/org/xmlBlaster/test/StopXmlBlaster.java >> >>This is needed that when the tests are run from ant, the tests are >>returning, >>to be ready to generate the html reports ... >> >>Does this happen during running the testsuite?? >> >> > >Yes. > > > >>If yes, StopXmlBlaster is called in AllTests.java, we could add a property >>to switch it on/off from outside >> >> >> > >It more that I am onconfortable with the fact that there are commands in >XmlBlaster that may take down the server its embedded in. > > > If xmlBlaster runs alone, it is normal to have an exit hook.
If running embeded : Probably we should add a parameter which allows disabling exit(). Marcel
