Anyway, it's definitely necessary to control correct synchronization of multiple concurrent jobs if they could possibly interfere with each other, i.e. they update some shared data. One way to do this would be to use correct synchronization mechanisms in the Java code.
Steve
Steve
Deepak Lal wrote:how do we implement CountDownLatch in jdk1.4 since i read in api it is since 1.5
Steve
Steve
Steve
Steve
Steve
1. what is the number of jobs that can be run concurrently and can be handled by the CountdownLatch as you have suggested ?
2. suppose i have 1000 jobs running concurrently ,will it degrade the performance of the running application /server will crash/ or any other possibility you see for such a huge number of jobs running concurrently.
3. Does the Backport with concurency have any limitations in terms of the above scenario ??
Deepak Lal wrote:
How do i use the CountdownLatch and which classes i need to import in the below scenario ?? Please help....
1. what is the number of jobs that can be run concurrently and can be handled by the CountdownLatch as you have suggested ?
2. suppose i have 1000 jobs running concurrently ,will it degrade the performance of the running application /server will crash/ or any other possibility you see for such a huge number of jobs running concurrently.
3. Does the Backport with concurency have any limitations in terms of the above scenario ??
Steve
Steve
Deepak Lal wrote:Steve could you please refine the code which i have pasted...
I'm unable to proceed...
Steve
To do a great right, do a little wrong - shakepeare. twisted little ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
|