I'm working on an application that requires users starting batchlike-processes. The processes can taken up to hours to complete. Now this is implemented by classes, extending the thread-class.
The application is not in production, but will have to be within the near future. My question now is this: is this approach (running "standard" threads) a healthy one ? In the past, this wasn't even allowed on most application-servers.
If not, I know about one other solution: using JMS, which also makes running "asynchronous". But is there maybe an alternative, as messaging seems a bit of a "heavy" solution for this (like shooting a mosquito using a 120mm canon). But maybe I'm exaggerating.
0
