Karaf stops unexpectedly - log4j2

After upgrading Karaf from 2.2.11 to 4.0.3 with log4j2 support and running load tests of our Karaf based application, Karaf unexpectedly starts shutdown process.
We increased most of memory options but it did not help. No info in logs - just
"Stopping blueprint extender" and "Unregistering bundles...". Above these messages there was debug info from my bundles. In manifest files of our bundles old OSGI container is used (org.osgi.framework;version="1.3.0"). This occurs for single threaded scenario too, after 3 hours since karaf start.
Can one bundle that fails trigger whole framework to stop?
Any ideas why Karaf 4.0.3 is not stable and where we need to investigate?

Related

log files not created in jbpm, installation incomplete

I have been trying to install jbpm6.1.0 in my Windows 7 32 bit system. However I am unable to complete so because doing an ant demo.start.noeclipse leads to a
build.xml:508: JBoss application server did not start within 5 minutes
I have increased the time in build.xml and tried other simple tweaks. Then I was suggested to look into log files but I observed they were never created, the log folder within standalone is not present at all. I think that my installation is not getting complete and JBoss application server not starting because of that.
I used this tutorial for installation and also used links given by it
http://docs.jboss.org/jbpm/v6.0.Beta2/userguide/ch.installer.html#d0e281
I am not able to debug and get to a reason. Starting the standalone.bat only gives me info that the Java_Home environment variable is set properly. I can do with a way out or even a direction as where to get more information on the process so that I may be able to debug.
Java_Home is C:\Program Files\Java\jdk1.7.0_51\bin and ANT_HOME is C:\Program Files\apache-ant-1.9.4 with path using the C:\Program Files\apache-ant-1.9.4\bin for its purpose. Hence both the applications must be running correctly
You need to find out what the error is because it seems that the application server is not even starting, that can be because you don't have administrator rights or because there is another server running using the required ports

Lifecycle exception in tomcat

I'm getting org.apache.catalina.LifecycleException when running shopizer project in eclipse. Shopizer use struts2. Also I'm using tomcat7 to run it. The bad thing is some times it comes and sometimes it don't. When It comes restarting the server is not helping and I have to restart the whole system to get things working again.
open task manager.
kill the process 'javaw.exe'
then restart the server after cleaning tomcat directory and project
it should work..

Grails app kills itself

I just got a chance to test-drive a VPS for a week, and decided to try Grails on it. The problem is, that it shuts itself down.
Details:
VPS - 512MB Ram, Ubuntu 12.10 x64 (no particular reason for x64)
Oracle Java 7u17
Latest GVM 0.9.5
Grails 2.2.1
What I did was follow along this tutorial http://grails.org/Quick+Start, which is very basic. Everything went smooth until I did grails run-app.
After doing the initialization, it showed running for like 5s, and I could even start loading the page, but it suddenly showed Killed in the terminal. This is what the terminal showed:
root#jp:/var/grails/my-project# grails run-app
| Running Grails application
Killed
There was no input during that time whatsoever. Any ideas on the cause of this problem?
You should only ever run Grails with the run-app command when developing locally. The reason behind this is because run-app starts your Grails app with a lot of dynamic behavior that is great for rapid development, but horrible performance-wise for running on an actual server.
Refer to Grails' User Guide on how best to deploy your application:
http://grails.org/doc/latest/guide/gettingStarted.html#deployingAnApplication
As the docs above state, the correct way to run your Grails app is to embed it in a servlet container. Tomcat is a good place to start since Grails uses that by default when running locally. You may also need to play around with the VM flags of your servlet container, depending on your environment (again, the docs give a few suggestions here).
You can redirect output of your command if it get's killed immediately on your terminal.
grails run-app > output.txt
Then open output.txt and from there you can dissect the problem.
For my case, i got an incorrect JAVA_HOME directory.
Hope it helps.

Integrity CI Server not running builds when using Passenger / Apache webserver

The Integrity App is working fine for me in my OSX dev environment. I've deployed an instance to a Ubuntu server for my production setup, and I'm able to setup a new project. Once I call a manual build to attempt to test a first build the build record is created, but the build is never run.
I've added a bunch of logging to my application and have been able to track the point of failure to when the build job is added in ThreadPool#add It appears everything is running fine to get the job added to the build pool, but that the pool isn't actually running anything despite being spawned and no exceptions being raised.
The environment I'm running is Ubuntu 11.04, RVM & Ruby 1.9.2-p290, Passenger / Apache, and running Integrity from master w/Sqlite3 and ThreadedBuilder.
UPDATE:
I found an article indicating this may be an issue with using Apache & Passenger not loading the Ruby environment properly. This appears to be the case since in dev I'm just running bundle exec rackup, and in production I was trying to use Passenger. So on the production machine I started an instance of Integrity using bundle exec rackup, which does indeed actually start running the builds except that it didn't properly find the bundler gem as it should have. I'm sure I can track down a fix for that somehow.
So essentially the issue I am having is with running Integrity with Passenger rather than using rackup. The article that pointed me in this direction didn't work with their solution of getting Ruby in the Apache environment though. Can anyone help me determine how to properly run Integrity with Passenger?
The issue was in the way Passenger handles threading. By changing to the DelayedBuilder using DelayedJob for builds rather than the ThreadedBuilder I was able to use Passenger as the web server.

How to make/monitor/deploy daemon processes in JRuby

I'm currently porting a Rails App currently using REE to JRuby so I can offer an easy-to-install JRuby alternative.
I've bundled the app into a WAR file using Bundler which I'm currently deploying to GlassFish. However, this app has a couple of daemon processes and it would be ideal if these could be part of the WAR file, and potentially monitored by Glassfish (if possible).
I've looked at QuartzScheduler, and while meets my needs for a couple of things, I have a daemon process that must execute every 20 seconds as it's polling the database for any delayed mail to send.
If anyone can provide any insight as to how best to set up daemon processes in a JRuby/Java/Glassfish environment any help will be greatly appreciated! :)
One way to daemonize a JRuby process is to use akuma framework (on *nix) or others.
I would rather use cronjobs (schedulling) rather than daemons as they are less error-proned, daemons can leak memory, can stop on errors etc. Check jruby-quartz and quartz_scheduler
EDIT
If one uses Torquebox it offers support for services and scheduling.

Resources