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.

Sign up for GitHub

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

Jump to bottom

Distributed/Remote ClassLoader #1807

Closed
olamy opened this issue Feb 19, 2014 · 5 comments
Closed

Distributed/Remote ClassLoader #1807

olamy opened this issue Feb 19, 2014 · 5 comments
Labels
Team: Core Type: Enhancement
Milestone
Backlog

Comments

@olamy
Copy link

olamy commented Feb 19, 2014

Currently if I have a look at http://www.hazelcast.org/ Tab "Executor Service".
This sample simply doesn't work on a cluster (multiple nodes) as the inner class MessagePrinter is not defined in the classloader of other nodes.
I wonder if it's a feature you could be interested? (Yes I know it's possible to have jars on remote nodes but not very user friendly).
@olamy
Copy link
Author

olamy commented Feb 19, 2014

@noctarius ping me. I have some ideas for that.

@noctarius
Copy link
Contributor

Yeah I know it's possible, too. Not easy to implement it the right way but yeah pretty much interested - interesting especially while development.

@gurbuzali gurbuzali added this to the 3.2+ milestone Mar 11, 2014
@jerrinot
Copy link
Contributor

for anyone who is interested in this. there is a community project at: https://github.com/serkan-ozal/hermgen

obviously it's not supported by Hazelcast, but it would be great to start some more activity here.

@mdogan
Copy link
Contributor

mdogan commented Feb 16, 2017 •
edited

See User Code Deployment:

http://docs.hazelcast.org/docs/3.8-RC1/manual/html-single/index.html#user-code-deployment-beta

https://github.com/hazelcast/hazelcast/blob/master/hazelcast/src/main/java/com/hazelcast/config/UserCodeDeploymentConfig.java

@noctarius
Copy link
Contributor

Closing this (still) open issue which was forgotten to be closed after 3.8 release. The @mdogan's comment.

frant-hartm pushed a commit that referenced this issue Mar 26, 2021
@viliam-durina
Reduce flexibility and improve JMS sink (#1807)
c4aa54e 
Remove `sessionFn`, `flushFn` and `sendFn`. They would prevent implementing ex-once in the future without breaking changes.

Use transactions for sending: this is recommended for ActiveMQ and WebLogic JMS as an optimization. `MessageProducer.send` is synchronous normally, but in transactions it's async
and `commit()` waits for all in-flight sends.
devOpsHazelcast pushed a commit that referenced this issue May 7, 2024
@orcunc @actions-user
Simplify some assertions (#1807)
294b04f 
GitOrigin-RevId: 92dde7293c8d47dbc20373757d5f03741bddabf8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Team: Core Type: Enhancement
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
8 participants
@olamy @pveentjer @jerrinot @ajermakovics @noctarius @mdogan @gurbuzali @asimarslan