Facing issue with Jering.Javascript.NodeJS #175
Comments
|
I don't think you will get it to work with Node@6, bump up to a more up to date version of Node and it will work just fine. I have been using it on an Azure App service with Node@14 and it has been great. There is an app setting on azure app services to set the node version your app service runs up with: |
Hi @ianllewellyn , even this step also fails for me eventhough if I set my WEBSITE_NODE_DEFAULT_VERSION in the Azure App configuration still getting the same error in linux function app for the Jering.Javascript.NodeJS |
Hi,
I'm facing the following issue in the linux app service hosted on azure for the NodeJS version 6.3.1
Jering.Javascript.NodeJS.ConnectionException:
at Jering.Javascript.NodeJS.OutOfProcessNodeJSService.ConnectIfNotConnected (Jering.Javascript.NodeJS, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3786d24ab42c57d6)
at Jering.Javascript.NodeJS.OutOfProcessNodeJSService+d__42
1.MoveNext (Jering.Javascript.NodeJS, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3786d24ab42c57d6) at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e) at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e) at Jering.Javascript.NodeJS.OutOfProcessNodeJSService+<InvokeFromFileAsync>d__291.MoveNext (Jering.Javascript.NodeJS, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3786d24ab42c57d6)at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
Inner exception System.InvalidOperationException handled at Jering.Javascript.NodeJS.OutOfProcessNodeJSService.ConnectIfNotConnected:
at Jering.Javascript.NodeJS.NodeJSProcessFactory.CreateProcess (Jering.Javascript.NodeJS, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3786d24ab42c57d6)
at Jering.Javascript.NodeJS.NodeJSProcessFactory.Create (Jering.Javascript.NodeJS, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3786d24ab42c57d6)
at Jering.Javascript.NodeJS.OutOfProcessNodeJSService.CreateAndSetUpProcess (Jering.Javascript.NodeJS, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3786d24ab42c57d6)
at Jering.Javascript.NodeJS.OutOfProcessNodeJSService.ConnectIfNotConnected (Jering.Javascript.NodeJS, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3786d24ab42c57d6)
Inner exception System.ComponentModel.Win32Exception handled at Jering.Javascript.NodeJS.NodeJSProcessFactory.CreateProcess:
at System.Diagnostics.Process.ForkAndExecProcess (System.Diagnostics.Process, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a)
at System.Diagnostics.Process.StartCore (System.Diagnostics.Process, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a)
at System.Diagnostics.Process.Start (System.Diagnostics.Process, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a)
at System.Diagnostics.Process.Start (System.Diagnostics.Process, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a)
at Jering.Javascript.NodeJS.NodeJSProcessFactory.CreateProcess (Jering.Javascript.NodeJS, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3786d24ab42c57d6)
The text was updated successfully, but these errors were encountered: