how do we know the restart happened in anypoint Runtime Manager (cloudhub) is automatically restarted (due to some internal issue) or some one manually force restart?
How could we find that? any specific log line which could differentiate manual and automatic restart? Any thoughts on it. Thanks
Using Version 4.2.2.
The manual restart should be visible in the Audit Log. I don't think that the automatic restart due to a crash appears at all. Automatic restarts due to patching will be visible.
Related
Maybe someone had the same problem.
I use Weblogic at work. So, we have two small applications on it. And today it stopped writing logs(all logs stopped writing at the same time). Then, after three hours it writes in log “JVM called WLS shutdown hook. The server will force shutdown now” and shutdown. After start everything works fine.
But I want to understand, why this situation happened
Thanks
This happens when System.exit(int) is called. Check if some of the deployed components call System.exit instead of throwing an Exception. This also can be due to the JVM taking up the OS signals.Set the -Xrs option in the startup scripts in JAVA_OPTIONS if you are using Sun JDK.It reduces use of operating-system signals by the JVM.
I have a couple of Mule applications running on mule container version 3.3.0. Recently I have observed that one of my mule application is getting redeployed again and again in a loop continuously.
The Mule app first get deployed then immediately within 2-3 seconds the mule app gets un-deployed and then gets deployed automatically. This is happening in loop and I don't see any specific errors in the log.
Can somebody please help me out with this problem and let me know the reason for the above behavior and how to fix it.
Thanks
Jai
There has to be an error, the problem is probably that you don't see it. Try locating the logfile named mule.log (or mule_ee.log) rather than mule-app-APPNAME.log. You might find the error there.
Otherwise, triple check that there are no weird permissions on the directory app (as the lock file should be created there).
My machine crashed and corrupted my .workspace file in IntelliJ IDEA> I deleted the .workspace file and restarted IDEA. It restarted but now I've lost my Tomcat config.
When I try to re-add, the Application Server menu is greyed out.
Can anyone tell me how to get my config back, or at least re-add it?
I've tried the Local History method but I don't see any previous history.
Add the Tomcat app server back under settings and you should be fine. Once you do that, Tomcat will appear as an app server choice again.
I restarted and IntelliJ is now working. I don't know what fixed it because I restarted a few time.
Is there a straight forward approach for JBoss AS to print messages to the console in eclipse? I intend to use them only for debugging purposes and nothing more (I swear).
I'm new to JBoss and I don't know where to start and what to do to get my System.out.println()-messages appear in the console.
Unfortunately I have been struggling too long for today to achieve this rather natural requirement. I'm using JBoss AS 7.1.
edit:
Ok, looks like this time the problem is sitting in front of the screen. I couldn't find my logging even in the server.log. The reason is that the code which I was executing throwed an error which prevented the sysouts from being printed to the console. I'm sorry. Thank you for your help.
If you make a Sysout in your application, you can find it at the server.log, inside the folder $JBOSS_HOME/standalone/log
That, however, is not the best practice, since there's a lot of configuration and possibility at the log. You can check more information about that here
But, if you just say System.out.println('hello world') it will be out at server.log
All logging after the boot is made there so there you can check your System.out.println() stuff
With a default install a console handler and a file handler are configured. If you want to log to either you just need to use a logger. Printing to System.out or System.err it will work as well, but I would suggest using a logging facade like JBoss Logging, SLF4J or even just J.U.L.
If you're wanting to run JBoss AS inside eclipse the easiest way is to use JBoss Tools. You can start, stop and deploy your application from within eclipse locally for testing.
In my project I had 2 log4j.proprties files one is provided by jboss other is in my workspace. I removed one log4j.properties file now I am able to see sysout on the console.
Some of our FogBugz users experience that the Screenshot tool does not start-up automatically at boot. The quickest work-around is to re-install it. Any ideas on what causes this to happen? And how to prevent it from happening?
When you repost this on fogbugz.stackexchange.com, make sure you specify your OS.