new object set value thread safe?
I have a ThreadSafeObject and I need to create a object out of it. I can guarantee that ThreadSafeObject is
thread safe.Similarly when multiple threads create a TestObject from ThreadSafeObject, would setValue() and getValue(),
also be threadsafe? Or do I need to apply synchronisation on setValue()? I referred the below two links and what I have understood is the object creation is threadsafe but setValue should be synchrnozed. Is this correct?
Is creation of new object thread safe
Constructor synchronization in Java
public class TestObject
private String value;
public TestObject(ThreadSafeObject threadSafeObject)
public void setValue(String value)
this.value = value;
public String getValue()
return value;
java multithreading thread-safety
add a comment |
I have a ThreadSafeObject and I need to create a object out of it. I can guarantee that ThreadSafeObject is
thread safe.Similarly when multiple threads create a TestObject from ThreadSafeObject, would setValue() and getValue(),
also be threadsafe? Or do I need to apply synchronisation on setValue()? I referred the below two links and what I have understood is the object creation is threadsafe but setValue should be synchrnozed. Is this correct?
Is creation of new object thread safe
Constructor synchronization in Java
public class TestObject
private String value;
public TestObject(ThreadSafeObject threadSafeObject)
public void setValue(String value)
this.value = value;
public String getValue()
return value;
java multithreading thread-safety
The context is not completely clear, but it sounds like each thread creates its own instance ofTestObject
. Since no instances ofTestObject
is shared among multiple threadsTestObject
would be threadsafe.
– Andrew S
Nov 13 '18 at 18:28
add a comment |
I have a ThreadSafeObject and I need to create a object out of it. I can guarantee that ThreadSafeObject is
thread safe.Similarly when multiple threads create a TestObject from ThreadSafeObject, would setValue() and getValue(),
also be threadsafe? Or do I need to apply synchronisation on setValue()? I referred the below two links and what I have understood is the object creation is threadsafe but setValue should be synchrnozed. Is this correct?
Is creation of new object thread safe
Constructor synchronization in Java
public class TestObject
private String value;
public TestObject(ThreadSafeObject threadSafeObject)
public void setValue(String value)
this.value = value;
public String getValue()
return value;
java multithreading thread-safety
I have a ThreadSafeObject and I need to create a object out of it. I can guarantee that ThreadSafeObject is
thread safe.Similarly when multiple threads create a TestObject from ThreadSafeObject, would setValue() and getValue(),
also be threadsafe? Or do I need to apply synchronisation on setValue()? I referred the below two links and what I have understood is the object creation is threadsafe but setValue should be synchrnozed. Is this correct?
Is creation of new object thread safe
Constructor synchronization in Java
public class TestObject
private String value;
public TestObject(ThreadSafeObject threadSafeObject)
public void setValue(String value)
this.value = value;
public String getValue()
return value;
java multithreading thread-safety
java multithreading thread-safety
asked Nov 13 '18 at 18:09
user414967user414967
2,33042549
2,33042549
The context is not completely clear, but it sounds like each thread creates its own instance ofTestObject
. Since no instances ofTestObject
is shared among multiple threadsTestObject
would be threadsafe.
– Andrew S
Nov 13 '18 at 18:28
add a comment |
The context is not completely clear, but it sounds like each thread creates its own instance ofTestObject
. Since no instances ofTestObject
is shared among multiple threadsTestObject
would be threadsafe.
– Andrew S
Nov 13 '18 at 18:28
The context is not completely clear, but it sounds like each thread creates its own instance of
TestObject
. Since no instances of TestObject
is shared among multiple threads TestObject
would be threadsafe.– Andrew S
Nov 13 '18 at 18:28
The context is not completely clear, but it sounds like each thread creates its own instance of
TestObject
. Since no instances of TestObject
is shared among multiple threads TestObject
would be threadsafe.– Andrew S
Nov 13 '18 at 18:28
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53287101%2fnew-object-set-value-thread-safe%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53287101%2fnew-object-set-value-thread-safe%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The context is not completely clear, but it sounds like each thread creates its own instance of
TestObject
. Since no instances ofTestObject
is shared among multiple threadsTestObject
would be threadsafe.– Andrew S
Nov 13 '18 at 18:28