I think the other processes are oracle processes.
Anyway I tried using direct instead of activemq component.
The application can be stopped normally from the console. However the
threads still remain.
Is there any setting that I can tweak so that once the threads parent has
died the other threads will die as well?
Looking at it it seems that thread death does not occur even when the web
application was stopped.
Here is my route
from("file://c://ufm//upload?moveNamePrefix=c://ufm//processed//&moveNamePostfix=USED").process(new
Processor() {
public void process(Exchange exchange) throws Exception
{
FileModel fileModel = new FileModel();
fileModel.setFileName(exchange.getIn().getHeader("org.apache.camel.file.name").toString());
fileModel.setContent(exchange.getIn().getBody(String.class));
exchange.getOut().setBody(fileModel);
}
}).to("direct:carlo");
from("direct:carlo").thread(5).process(new Processor() {
public void process(Exchange exchange) throws Exception
{
FileModel fileModel = (FileModel)
exchange.getIn().getBody();
System.out.println(fileModel.getFileName());
System.out.println(fileModel.getContent());
while(1==1) {
System.out.println("aaa");
try {
} catch(Exception e) {
e.printStackTrace();
}
}
}
});
This is just for investigation. Also if i use activemq instead of direct.
The application just doesn't stop.
--
View this message in context:
http://www.nabble.com/Camel%2C-Websphere%2C-And-Long-Running-Threads-tp18834455s22882p18838295.html
Sent from the Camel - Users mailing list archive at Nabble.com.
