Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distributable MES #34

Open
glassfishrobot opened this issue Oct 14, 2013 · 4 comments
Open

Distributable MES #34

glassfishrobot opened this issue Oct 14, 2013 · 4 comments

Comments

@glassfishrobot
Copy link

Discuss whether we need to bring back distributable ManagedExecutorService in the next revision of the concurrency EE spec.

One question that was brought up is how one server instant can retrieve the Future to cancel a long-running task if the task was originally submitted by another server instance.

Affected Versions

[1.0]

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
Reported by alai8

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
This issue was imported from java.net JIRA CONCURRENCY_EE_SPEC-34

@glassfishrobot
Copy link
Author

@mswatosh
Copy link
Member

Adding some context here (without endorsing the idea) from a PDF on JSR 236:

  • Same rules as a ManagedExecutorService
  • Allows distributing the task to a peer on another
    server instance (JVM).
  • Task must implement serializable
  • Optional feature – Java EE Providers do not have to
    supply a distributable ManagedExecutorService.
  • Two distributable types are available:
  • With and without affinity
  • Tasks could provide distributable hint to Java EE
    product providers through executionProperties in
    ManagedTask.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants