Indeed, in that case this was the initial intend.
This is a fatal error from nuxeo point of view and server should be stopped.
In production code normally this should never happens (or if it happens
due to some IO errors anyway the server will be unusable).
This is useful when developing because if we have an exception here this
means the nuxeo.ear is malformed
and this will lead to an unusable nuxeo server - and this may help in
detecting the real problem and to avoid loosing time
waiting for the jboss deployment to finish and then debugging to see why
the server is malfunctioning.
But thanks for the remark we will clean them up if necessarily.
About delete on exit - yes we known the problem, we will fix this and
use custom cleanup code for temp files when needed.
Bogdan
Filipchik Alexander wrote:
When we had investigated your code we found that your developers uses
System.exit(1) in several cases.
We found 11 usages of it. For example:
org.nuxeo.runtime.jboss.deployment.preprocessor.DeploymentPreprocessor
//line 412
try {
// initialize
processor.init();
// and predeploy
processor.predeploy();
} catch (Exception e) {
e.printStackTrace();
System.exit(1);
}
And also you use deleteOnExit() when creating temp files. It can cause
different faults.
System.exit – kills JBoss Server when executed
------------------------------------------------------------------------
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
