[jira] [Commented] (IGNITE-4211) Update Spring dependency to latest stable version
[ https://issues.apache.org/jira/browse/IGNITE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823207#comment-15823207 ] Rohit Mohta commented on IGNITE-4211: - As of today, current GA release is *4.3.5.RELEASE*. > Update Spring dependency to latest stable version > - > > Key: IGNITE-4211 > URL: https://issues.apache.org/jira/browse/IGNITE-4211 > Project: Ignite > Issue Type: Improvement > Components: build >Affects Versions: 1.7 >Reporter: Sergey Kozlov >Assignee: Rohit Mohta > Fix For: 2.0 > > > It seems the Spring dependency looks outdated for now. Apache Ignite still > uses 4.1.0 released two years ago. Could we to update to latest stable > version (4.3.4 at the moment)? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4211) Update Spring dependency to latest stable version
[ https://issues.apache.org/jira/browse/IGNITE-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Mohta reassigned IGNITE-4211: --- Assignee: Rohit Mohta > Update Spring dependency to latest stable version > - > > Key: IGNITE-4211 > URL: https://issues.apache.org/jira/browse/IGNITE-4211 > Project: Ignite > Issue Type: Improvement > Components: build >Affects Versions: 1.7 >Reporter: Sergey Kozlov >Assignee: Rohit Mohta > Fix For: 2.0 > > > It seems the Spring dependency looks outdated for now. Apache Ignite still > uses 4.1.0 released two years ago. Could we to update to latest stable > version (4.3.4 at the moment)? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4423) ignite.binary().type(entity.getKeyType())==null before first cache.put()
[ https://issues.apache.org/jira/browse/IGNITE-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Mohta reassigned IGNITE-4423: --- Assignee: Rohit Mohta > ignite.binary().type(entity.getKeyType())==null before first cache.put() > > > Key: IGNITE-4423 > URL: https://issues.apache.org/jira/browse/IGNITE-4423 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Rohit Mohta >Priority: Minor > Attachments: BinTest.java > > > See attacheed test for details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-2895) OS info in console is incorrect when using x86 JRE on x64 Windows
[
https://issues.apache.org/jira/browse/IGNITE-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohit Mohta reassigned IGNITE-2895:
---
Assignee: Rohit Mohta
> OS info in console is incorrect when using x86 JRE on x64 Windows
> -
>
> Key: IGNITE-2895
> URL: https://issues.apache.org/jira/browse/IGNITE-2895
> Project: Ignite
> Issue Type: Bug
> Components: general, newbie
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Rohit Mohta
>Priority: Trivial
> Fix For: 2.0
>
>
> Steps:
> * Use any x64 Windows (*nix might work too)
> * Use x86 JRE (by setting JAVA_HOME accordingly)
> * Run any test or example, see console log:
> {code} OS: Windows 8 6.2 x86{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3622) BinaryObject: print idHash in toString() method only in debug mode
[
https://issues.apache.org/jira/browse/IGNITE-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohit Mohta reassigned IGNITE-3622:
---
Assignee: Rohit Mohta
> BinaryObject: print idHash in toString() method only in debug mode
> --
>
> Key: IGNITE-3622
> URL: https://issues.apache.org/jira/browse/IGNITE-3622
> Project: Ignite
> Issue Type: Task
> Components: newbie
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Assignee: Rohit Mohta
>Priority: Trivial
> Fix For: 2.0
>
>
> Current implementation of BinaryObject.toString() method print idHash for
> internal objects, for example, for AffinityKey.
> This lead to "unstable" result of toString() method, you will get different
> strings on each toString() invocation.
> Possible fix: introduce
> {code}
> private static final boolean debug = false;
> {code}
> And check this flag in toString().
> If some one will need idHash for debug reasons he could change this flag in
> its private build and debug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4438) Remove old branch from Ignite's git repo
Rohit Mohta created IGNITE-4438: --- Summary: Remove old branch from Ignite's git repo Key: IGNITE-4438 URL: https://issues.apache.org/jira/browse/IGNITE-4438 Project: Ignite Issue Type: Wish Environment: Github Repo: https://github.com/apache/ignite Reporter: Rohit Mohta Priority: Minor There are numerous branches out there. Once a milestone is achieved, we should do some kind of cleanup to make sure we only have 3-6 branch at any given time. Tags can be used to record those milestones. Advantage: Folks submitting patch will know which branch to tag Anyone starting with ignite, will be able to see what's going on. Basically, better developer-experience. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4358) Better error reporting in case of unmarshallable classes.
[ https://issues.apache.org/jira/browse/IGNITE-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746656#comment-15746656 ] Rohit Mohta commented on IGNITE-4358: - [~ascherbakov] Changed the message per your comment. NPE check was present in my earlier patch too. ``` Objects.requireNonNull(r, "Trying to execute a null closure. Make sure the closure is not assignable from classes listed in MarshallerExclusions"); ``` > Better error reporting in case of unmarshallable classes. > - > > Key: IGNITE-4358 > URL: https://issues.apache.org/jira/browse/IGNITE-4358 > Project: Ignite > Issue Type: Improvement > Components: compute, messaging, newbie >Affects Versions: 1.6 >Reporter: Alexei Scherbakov >Assignee: Rohit Mohta >Priority: Trivial > Labels: newbie > Fix For: 2,0 > > Attachments: IGNITE-4358-Exceptionlog-05Dec2016.txt, > IGNITE-4358-GridClosureProcessor-05Dec2016.patch, PureIgniteRunTest.java > > > When trying to execute Thread's derived class implementing IgniteRunnable > using compute API, it silently serializes to null because Thread > serialization is prohibited in MarshallerExclusions and throws NPE on > executing node. > We need to throw more informative exception for such case. > Reproducer in the attachment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4358) Better error reporting in case of unmarshallable classes.
[ https://issues.apache.org/jira/browse/IGNITE-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722969#comment-15722969 ] Rohit Mohta commented on IGNITE-4358: - [~ascherbakov] I have uploaded the patch for the change and exception stack trace for the attached Junit test case. If you're OK, then I'm ready to send a PR for this change. > Better error reporting in case of unmarshallable classes. > - > > Key: IGNITE-4358 > URL: https://issues.apache.org/jira/browse/IGNITE-4358 > Project: Ignite > Issue Type: Improvement > Components: compute, messaging, newbie >Affects Versions: 1.6 >Reporter: Alexei Scherbakov >Assignee: Rohit Mohta >Priority: Trivial > Labels: newbie > Fix For: 2,0 > > Attachments: IGNITE-4358-Exceptionlog-05Dec2016.txt, > IGNITE-4358-GridClosureProcessor-05Dec2016.patch, PureIgniteRunTest.java > > > When trying to execute Thread's derived class implementing IgniteRunnable > using compute API, it silently serializes to null because Thread > serialization is prohibited in MarshallerExclusions and throws NPE on > executing node. > We need to throw more informative exception for such case. > Reproducer in the attachment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4358) Better error reporting in case of unmarshallable classes.
[ https://issues.apache.org/jira/browse/IGNITE-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Mohta updated IGNITE-4358: Attachment: IGNITE-4358-Exceptionlog-05Dec2016.txt > Better error reporting in case of unmarshallable classes. > - > > Key: IGNITE-4358 > URL: https://issues.apache.org/jira/browse/IGNITE-4358 > Project: Ignite > Issue Type: Improvement > Components: compute, messaging, newbie >Affects Versions: 1.6 >Reporter: Alexei Scherbakov >Assignee: Rohit Mohta >Priority: Trivial > Labels: newbie > Fix For: 2,0 > > Attachments: IGNITE-4358-Exceptionlog-05Dec2016.txt, > IGNITE-4358-GridClosureProcessor-05Dec2016.patch, PureIgniteRunTest.java > > > When trying to execute Thread's derived class implementing IgniteRunnable > using compute API, it silently serializes to null because Thread > serialization is prohibited in MarshallerExclusions and throws NPE on > executing node. > We need to throw more informative exception for such case. > Reproducer in the attachment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4358) Better error reporting in case of unmarshallable classes.
[ https://issues.apache.org/jira/browse/IGNITE-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Mohta updated IGNITE-4358: Attachment: IGNITE-4358-GridClosureProcessor-05Dec2016.patch Validate non-null runnable. Custom message to give more information, why is the user seeing NPE > Better error reporting in case of unmarshallable classes. > - > > Key: IGNITE-4358 > URL: https://issues.apache.org/jira/browse/IGNITE-4358 > Project: Ignite > Issue Type: Improvement > Components: compute, messaging, newbie >Affects Versions: 1.6 >Reporter: Alexei Scherbakov >Assignee: Rohit Mohta >Priority: Trivial > Labels: newbie > Fix For: 2,0 > > Attachments: IGNITE-4358-GridClosureProcessor-05Dec2016.patch, > PureIgniteRunTest.java > > > When trying to execute Thread's derived class implementing IgniteRunnable > using compute API, it silently serializes to null because Thread > serialization is prohibited in MarshallerExclusions and throws NPE on > executing node. > We need to throw more informative exception for such case. > Reproducer in the attachment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4358) Better error reporting in case of unmarshallable classes.
[
https://issues.apache.org/jira/browse/IGNITE-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722931#comment-15722931
]
Rohit Mohta commented on IGNITE-4358:
-
[~ascherbakov] Is the below message helpful?
{color:red}
Caused by: java.lang.NullPointerException: received null runnable in Grid. Did
we serialize only excluded classes? See MarshallerExclusions for the exclusion
list.
{color}
> Better error reporting in case of unmarshallable classes.
> -
>
> Key: IGNITE-4358
> URL: https://issues.apache.org/jira/browse/IGNITE-4358
> Project: Ignite
> Issue Type: Improvement
> Components: compute, messaging, newbie
>Affects Versions: 1.6
>Reporter: Alexei Scherbakov
>Assignee: Rohit Mohta
>Priority: Trivial
> Labels: newbie
> Fix For: 2,0
>
> Attachments: PureIgniteRunTest.java
>
>
> When trying to execute Thread's derived class implementing IgniteRunnable
> using compute API, it silently serializes to null because Thread
> serialization is prohibited in MarshallerExclusions and throws NPE on
> executing node.
> We need to throw more informative exception for such case.
> Reproducer in the attachment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-4358) Better error reporting in case of unmarshallable classes.
[ https://issues.apache.org/jira/browse/IGNITE-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Mohta reassigned IGNITE-4358: --- Assignee: Rohit Mohta > Better error reporting in case of unmarshallable classes. > - > > Key: IGNITE-4358 > URL: https://issues.apache.org/jira/browse/IGNITE-4358 > Project: Ignite > Issue Type: Improvement > Components: compute, messaging, newbie >Affects Versions: 1.6 >Reporter: Alexei Scherbakov >Assignee: Rohit Mohta >Priority: Trivial > Labels: newbie > Fix For: 2,0 > > Attachments: PureIgniteRunTest.java > > > When trying to execute Thread's derived class implementing IgniteRunnable > using compute API, it silently serializes to null because Thread > serialization is prohibited in MarshallerExclusions and throws NPE on > executing node. > We need to throw more informative exception for such case. > Reproducer in the attachment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
