[
https://issues.apache.org/jira/browse/IGNITE-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253844#comment-16253844
]
Pavel Tupitsyn commented on IGNITE-6911:
----------------------------------------
[~alexey.tank2]
1: Waiting for test run
2 & 3: I think {{RedirectJavaConsoleOutput}} is a better name. It is similar to
{{ProcessStartInfo.RedirectStandardOutput}}
(https://msdn.microsoft.com/en-us/library/system.diagnostics.processstartinfo.redirectstandardoutput.aspx).
Having default {{true}} value is also fine, many .NET classes do this
(https://msdn.microsoft.com/en-us/library/system.windows.uielement.isenabled.aspx).
> .NET: Optionally disable Java console redirect
> ----------------------------------------------
>
> Key: IGNITE-6911
> URL: https://issues.apache.org/jira/browse/IGNITE-6911
> Project: Ignite
> Issue Type: Improvement
> Security Level: Public(Viewable by anyone)
> Components: platforms
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.4
>
>
> Java console redirect ({{PlatformCallbackUtils.consoleWrite}} involves JNI
> callback and, potentially, can affect performance and stability of the
> application.
> It would be a good idea to disable this in production.
> * Add {{IgniteConfiguration.EnableJavaConsoleRedirect}} propery.
> * Disable callback on both .NET and Java sides
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
