We have an application running on BEA JVM. The application forks another JVM outside of BEA JVM to do some background stuff.
Our BEA infrastructure team is not allowing "anymore" any other JVM running on their Unix/Linux systems other than BEA JVMs.
Can somebody please advise of a good solution how to do the same stuff inside of BEA JVM rather than forking a process outside of it.
Please advise.
> the application needs "some process" to run
> asynchronously.
>
OKay fine.
> While that process is getting completed (some reports
> and all to be specific) ...the application wants the
> request and response on the application to be still
> responsive.
Okay fine.
Why were non BEA JVM's being used? You still have not answered this question.
> the application needs "some process" to run
> asynchronously.
>
> While that process is getting completed (some reports
> and all to be specific) ...the application wants the
> request and response on the application to be still
> responsive.
Cotton.m's questions withstanding, you may still be able to do this using Java Threads instead of forking.
Honestly, I do not know why the "fork" (forkAndExec) method was used inside the application java code running on BEA JVM to create a new JVM outside as a solution to do some asynchronous and background processes.
All i know is that this forked process returns back with some values needed for the application to complete some order reports asynchronously.
null
> Honestly, I do not know why the "fork" (forkAndExec)
> method was used inside the application java code
> running on BEA JVM to create a new JVM outside as a
> solution to do some asynchronous and background
> processes.
>
> All i know is that this forked process returns back
> with some values needed for the application to
> complete some order reports asynchronously.
Well threads are the answer you seek... probably. But you'll have to test to see if it works because there may have been a reason it wasn't done this way previously that is waiting to trip you up.
