if the thread executes normally ( i mean their is no problem in the Thread) in this case , My EJB code waits for the
thread to finish till the specified time interval in milli seconds and after that
EJB code executes which fulfills my requirement.
But the problem is if the thread executes above the configured StuckThreadMaxTime(600sec), then weblogic throws an ecxception but code in the EJB is not executed even though it should because thead is no more.
If application components contain the same functionality
provided by J2EE system infrastructure, there are clashes and mis-management of the functionality.
For example, if enterprise beans were allowed to manage threads, the J2EE
platform could not manage the life cycle of the enterprise beans, and it could not properly manage transactions.
The usual way to handle a long-running process in a web application is to return a message to the user immediately and hand the request off to a non-web client. Once the request has been processed, the non-web client can inform the user the results are available via email.
But in case where execution of the code in the EJB (Which created and started the therad)makes sense only when the thread has done its job , which mechanism shall i follow ...to implement such scenario because i have to wait either for the response of the thread or in case i don't get the response i have to wait for a fixed time duration.Thats why i was using join(120000) in the EJB code.