My application is on the .net core platform and uses apache ignite inside itself.
everything works truly on windows, but on ubuntu, the application stops working after a while.
I attached the log files.
log 01
log 02
Both logs end with *** stack smashing detected ***: terminated.
This happens on Linux with .NET Core when NullReferenceException occurs in user code. The reason is that both .NET and Java use SIGSEGV to handle certain exceptions, including NullPointerException and NullReferenceException.
The fix for this issue exists in .NET Core 3.0 and later: try setting the COMPlus_EnableAlternateStackCheck environment variable to 1 before starting the node. This should reveal the exception stack trace.
https://ignite.apache.org/docs/latest/net-specific/net-troubleshooting#stack-smashing-detected-dotnet-terminated
Related
I have a problem starting glassfish on Mac Os X 10.14.6.
I installed it with
brew install glassfish
then I added
AS_JAVA="/Library/Java/JavaVirtualMachines/jdk1.8.0_202.jdk/Contents/Home"
in asenv.conf in order to solve a java null pointer exception.
and now I receive the following error:
$ ./asadmin start-domain domain1
Waiting for domain1 to start .Error starting domain domain1.
The server exited prematurely with exit code 1.
Before it died, it produced the following output:
-Djava.endorsed.dirs=/usr/local/Cellar/glassfish/5.1.0/libexec/glassfish/modules/endorsed:/usr/local/Cellar/glassfish/5.1.0/libexec/glassfish/lib/endorsed is not supported. Endorsed standards and standalone APIs
in modular form will be supported via the concept of upgradeable modules.
Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Command start-domain failed.
Does anyone know how to solve this issue?
The endorsed directories have been removed since Java 9. So the error message suggests that you are running with at least Java 9.
You need to use Java 8 for this to work. If I remember correctly then Glassfish does not support Java 9 and higher.
Caused by: java.lang.IllegalStateException: Unable to complete the scan for annotations for web application [] due to a StackOverflowError. Possible root causes include a too low setting for -Xss and illegal cyclic inheritance dependencies. The class hierarchy being processed was [org.bouncycastle.asn1.ASN1EncodableVector->org.bouncycastle.asn1.DEREncodableVector->org.bouncycastle.asn1.ASN1EncodableVector]
at org.apache.catalina.startup.ContextConfig.checkHandlesTypes(ContextConfig.java:2104)
at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2048)
at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1994)
at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1964)
at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1917)
...
I am new to the Spring framework.
Here is the error message. Sometimes it can run while after stopping the project and re-run it, these messages are shown (but if I leave the IDE along for 5-10 mins, it can be run without errors).
What exactly is happening here? I am using the newest IDEA and Tomcat 8.
Solved. The reason is I was using a different version of Tomcat, version 8, while somehow the code is using version 7.
I am using macOS Mojave. On Windows, the code can be run via different versions, however, it seems that on macOS the version matters.
I am new to use Mulesoft and thus I have started learning it by following the steps in "https://docs.mulesoft.com/mule-user-guide/v/3.7/build-a-hello-world-application".
However, when I try to run the project by selecting "Run As > Mule Application", It gives me this error messages:
Launching a JVM...
JVM exited while loading the application.
Automatic JVM Restarts disabled. Shutting down.
backend pipe closed.
backend pipe closed.
<-- Wrapper Stopped
Note that: I am using Windows 7 (64 bit), Mulesoft 7.1 (64 bit), jdk1.8.0_171 (64 bit) and I have added java home into system variable as instructed in this post "https://forums.mulesoft.com/questions/90429/unable-to-install-mule-4-anypoint-studio-71.html"
Any suggestion, please !!!
See image and check your Run configuration I have post image under bellow url...
I have updated by JDK 4 months back to 1.6.0_45 in my SOLARIS SPRAC Machine, till yesterday it went well without any issues, but yesterday unfortunately i got an fatal error as below and the instance get crashed, as a work around i have restarted my server instance and it up and running fine now.
I need to know,
whats the exact root cause for this error?
How to investigate this ?
How can i avoid this in near future?
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0xfebd390c, pid=2626, tid=3
JRE version: 6.0_45-b06
Java VM: Java HotSpot(TM) Server VM (20.45-b01 mixed mode solaris-sparc )
Problematic frame:
V [libjvm.so+0x7d390c] void PSScavenge::copy_and_push_safe_barrier(PSPromotionManager*,__type_0*)+0xcc
If you would like to submit a bug report, please visit:
http://java.sun.com/webapps/bugreport/crash.jsp
Your JVM did crash inside libjvm.so, while doing GC. You can try changing the GC methodology (for example, try using -XX:+UseParallelOldGC) as meanwhile alternative. Else best bet would be to update the JVM.
I'm new to MonoTouch and more times than not, when I try to run my MonoTouch app on the iPhone simulator (debug mode and regular), I receive a long error output that begins with the following message:
Error connecting stdout and stderr (127.0.0.1:10001)
Couldn't register com.yourcompany.[appnamehere] with the bootstrap server. Error: unknown error code.
This generally means that another instance of this process was already running or is hung in the debugger.Stacktrace:
at (wrapper managed-to-native) MonoTouch.UIKit.UIApplication.UIApplicationMain (int,string[],intptr,intptr) <0x00004>
at (wrapper managed-to-native) MonoTouch.UIKit.UIApplication.UIApplicationMain (int,string[],intptr,intptr) <0x00004>
at MonoTouch.UIKit.UIApplication.Main (string[],string,string) <0x00089>
at MonoTouch.UIKit.UIApplication.Main (string[]) <0x00014>
at PodcastManager.Application.Main (string[]) <0x00010>
at (wrapper runtime-invoke) .runtime_invoke_void_object (object,intptr,intptr,intptr) <0x00043>
And ends with:
=================================================================
Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application.
=================================================================
The weird thing is it will work some of the time. Once, a reboot of my machine did it. Others, just restarting MonoDevelop and/or the simulator.
I can provide the entire error output if you think that may help.
Any ideas?
This is a problem with the monotouch debugger. Sometimes, when the application crashes, the debugger hangs in memory, and that then prevents you from running the app again. As you said, sometimes closing MonoDevelop and the simulator is enough to clean up the debugger, sometimes you need a full reboot. This is also the experience I have, which is probably the only bad thing I found with monotouch so far.
Many times, I'm able to directly kill the process from the console. To do that, open the console and type "top". You'll see the list of processes using the most memory, your app will likely be on top, using almost 100% of cpu. Save the id of the that line, and type q to quit. Now type "kill -9 ???" where ??? is the id you got from top.
Monotouch 2.0 fixed a lot of these problems, if you haven't updated yet I would seriously recommend you to do so. I'm running the beta channel of 2.0, and its a LOT more stable. Crashes went down from 1 or 2 every hour to 1 or 2 a day. It still happens, though, unfortunately.
-- Update -- after updating to 2.0.2 I have not seen this issue.
After playing with it long enough, and coming across this bug report I've come to the conclusion that until it's fixed the way to prevent this error is by NEVER stopping a debug session in the IDE. As long as you stop the debug session when the code is not at a breakpoint by hitting the home button it appears that you will avoid this situation.
I think this error comes when any native library of monotouch is missing. It happen due to uninstall Visual Studio or Update Xamarin. I faced the Same error and resolve it by Unistalland reinstall the Xamarin Visual Studio and Xamarin Studio. It takes 10 min and all issues are solved.