ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-6974) .NET: consoleWrite error during application shutdown
Date Tue, 21 Nov 2017 12:13:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pavel Tupitsyn updated IGNITE-6974:
-----------------------------------
    Labels: .NET  (was: )

> .NET: consoleWrite error during application shutdown
> ----------------------------------------------------
>
>                 Key: IGNITE-6974
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6974
>             Project: Ignite
>          Issue Type: Bug
>          Components: platforms
>    Affects Versions: 2.3
>            Reporter: Alexey Popov
>            Priority: Minor
>              Labels: .NET
>
> from Gitter:
> Hey all (again xD)! Using Apache Ignite .NET 2.3 I (sometimes) get an error when shutting
down my application. The error is only observable on server nodes and not on every shutdown.
Seems like a kind of race condition.
> The application runs as windows service. The windows application event log shows the
following error (see above) and a I get a hs_err_pid[PID].log like that (snip):
> Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
> j  org.apache.ignite.internal.processors.platform.callback.PlatformCallbackUtils.consoleWrite(Ljava/lang/String;Z)V+0
> j  org.apache.ignite.internal.processors.platform.callback.PlatformCallbackGateway.consoleWrite(Ljava/lang/String;Z)V+2
> j  org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetConsoleStream.write([BII)V+18
> j  java.io.PrintStream.write([BII)V+16
> j  sun.nio.cs.StreamEncoder.writeBytes()V+120
> j  sun.nio.cs.StreamEncoder.implFlushBuffer()V+11
> j  sun.nio.cs.StreamEncoder.flushBuffer()V+15
> j  java.io.OutputStreamWriter.flushBuffer()V+4
> j  java.io.PrintStream.write(Ljava/lang/String;)V+27
> j  java.io.PrintStream.print(Ljava/lang/String;)V+9
> j  org.apache.ignite.internal.util.IgniteUtils.quiet(Z[Ljava/lang/Object;)V+126
> j  org.apache.ignite.internal.IgniteKernal.stop0(Z)V+943
> j  org.apache.ignite.internal.IgniteKernal.stop(Z)V+6
> j  org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(Z)V+162
> j  org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(Z)V+26
> j  org.apache.ignite.internal.IgnitionEx.stop(Ljava/lang/String;ZZ)Z+72
> j  org.apache.ignite.Ignition.stop(Ljava/lang/String;Z)Z+3
> j  org.apache.ignite.internal.processors.platform.PlatformIgnition.stop(Ljava/lang/String;Z)Z+2
> v  ~StubRoutines::call_stub
> For me it seems that the Java side wants to write something to the (.NET) console using
a callback and the underlying memory is already freed - therefore we get a AccessViolation



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message