Re: Cannot start Karaf

2014-10-13 Thread Dan
Hi David, I’m running 3.0.1 on Mac out of the box. You’ll likely need to describe more about your circumstances, e.g. the JVM used, what commands you’ve run (to start Karaf and at it’s own command line), what bundles you’ve installed (if any), the complete stack trace, etc? Best, Dan. On 13

Re: Cannot start Karaf

2014-10-13 Thread Achim Nierbeck
which version of Java are you using? Please note with Karaf 3.0.1 it's still recommended to use Java7 regards, Achim 2014-10-13 10:15 GMT+02:00 David Leangen apa...@leangen.net: Hi! I am new to Karaf. I am trying to set up v3.0.1 on my Mac, but am getting a JMRuntimeException: Failed to

Re: Cannot start Karaf

2014-10-13 Thread David Leangen
Wow! Impressive response. :-) Thank you! Can you make a try with 3.0.2 (currently on staging) ? Tried. Same problem. :-( which version of Java are you using? Please note with Karaf 3.0.1 it's still recommended to use Java7 Hmmm. I am still a luddite with 1.6 (more precisely

Re: Cannot start Karaf

2014-10-13 Thread Jean-Baptiste Onofré
It looks like the lib folder doesn't contain the karaf-jmx-boot.jar file (providing the MBeanServerBuilder). Can you check that this jar is in the lib folder ? Do you have something in bin/setenv ? Regards JB On 10/13/2014 10:39 AM, David Leangen wrote: Wow! Impressive response. :-) Thank

Re: Cannot start Karaf

2014-10-13 Thread Jean-Baptiste Onofré
By the way, can you try with Java7 (instead of Java6) ? Regards JB On 10/13/2014 10:39 AM, David Leangen wrote: Wow! Impressive response. :-) Thank you! Can you make a try with 3.0.2 (currently on staging) ? Tried. Same problem. :-( which version of Java are you using? Please note with

Re: Cannot start Karaf

2014-10-13 Thread David Leangen
It looks like the lib folder doesn’t contain the karaf-jmx-boot.jar file (providing the MBeanServerBuilder). Can you check that this jar is in the lib folder ? Yes, it is there. Do you have something in bin/setenv ? No, using defaults. By the way, can you try with Java7 (instead of

Re: Cannot start Karaf

2014-10-13 Thread Jean-Baptiste Onofré
Really weird, Can you do a java -version and send the result. Can you also send the data/log/karaf.log to me ? Regards JB On 10/13/2014 01:47 PM, David Leangen wrote: It looks like the lib folder doesn’t contain the karaf-jmx-boot.jar file (providing the MBeanServerBuilder). Can you check

Re: Cannot start Karaf

2014-10-13 Thread Achim Nierbeck
Do you have another container with a JMXServer running? It's rather strange behavior you're describing. Could you do a cleanup of the cache folder, by removing the data folder? regards, Achim 2014-10-13 13:47 GMT+02:00 David Leangen apa...@leangen.net: It looks like the lib folder doesn’t

Re: Cannot start Karaf

2014-10-13 Thread David Leangen
Really weird, :-) Can you do a java -version and send the result. java version 1.7.0_67 Java(TM) SE Runtime Environment (build 1.7.0_67-b01) Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode) Can you also send the data/log/karaf.log to me ? There is no file (assuming that it

Re: Cannot start Karaf

2014-10-13 Thread David Leangen
Hi! Do you have another container with a JMXServer running? Nope. (Unless there is something happening that I am not aware of. How could I verify?) It’s rather strange behavior you're describing. No doubt. Could you do a cleanup of the cache folder, by removing the data folder? Again,

Re: Cannot start Karaf

2014-10-13 Thread Achim Nierbeck
hmm, did you tell us already which OS you're using? regards, Achim 2014-10-13 13:59 GMT+02:00 David Leangen apa...@leangen.net: Hi! Do you have another container with a JMXServer running? Nope. (Unless there is something happening that I am not aware of. How could I verify?) It’s

Re: Cannot start Karaf

2014-10-13 Thread Jean-Baptiste Onofré
Mac OS X On 10/13/2014 02:01 PM, Achim Nierbeck wrote: hmm, did you tell us already which OS you're using? regards, Achim 2014-10-13 13:59 GMT+02:00 David Leangen apa...@leangen.net mailto:apa...@leangen.net: Hi! Do you have another container with a JMXServer running? Nope.

Re: Cannot start Karaf

2014-10-13 Thread Jean-Baptiste Onofré
in the bin/karaf script, can you confirm that you have something like: exec $JAVA $JAVA_OPTS -Djava.endorsed.dirs=${JAVA_ENDORSED_DIRS} -Djava.ext.dirs=${JAVA_EXT_DIRS} -Dkaraf.instances=${KARAF_HOME}/instances -Dkaraf.home=$KARAF_HOME -Dkaraf.base=$KARAF_BASE -Dkaraf.data=$KARAF_DATA

Re: Cannot start Karaf

2014-10-13 Thread David Leangen
Hi, in the bin/karaf script, can you confirm that you have something like: exec “$JAVA” […] Yes. Do you define some env variables like KARAF_BASE/KARAF_HOME/KARAF_ETC, ? I tried both. Same results. A possible cause is that KARAF_HOME is not well setted or a CLASSPATH system

Re: Cannot start Karaf

2014-10-13 Thread David Leangen
OK, I think we narrow the problem. I bet your KARAF_HOME is defined by empty or it's not correct (I guess that /usr/local/lib folder is not your actual KARAF_HOME). I would advise to unset KARAF_BASE, KARAF_HOME, etc to let the bin/karaf script to define it for you. Sure. What, very

Re: Cannot start Karaf

2014-10-13 Thread David Leangen
Unfortunately, even with KARAF_HOME unset, the problem persists. :-( On Oct 13, 2014, at 9:35 PM, David Leangen apa...@leangen.net wrote: OK, I think we narrow the problem. I bet your KARAF_HOME is defined by empty or it's not correct (I guess that /usr/local/lib folder is not your

Re: Cannot start Karaf

2014-10-13 Thread Guillaume Nodet
2014-10-13 14:14 GMT+02:00 David Leangen apa...@leangen.net: Hi, in the bin/karaf script, can you confirm that you have something like: exec “$JAVA” […] Yes. Do you define some env variables like KARAF_BASE/KARAF_HOME/KARAF_ETC, ? I tried both. Same results. A possible cause

Re: Cannot start Karaf

2014-10-13 Thread Jean-Baptiste Onofré
KARAF_HOME is the location where you uncompressed Karaf. For instance, if you uncompressed Karaf in /opt/apache-karaf (and so, you have /opt/apache-karaf/bin, /opt/apache-karaf/lib, etc), KARAF_HOME is /opt/apache-karaf. However, by default, KARAF_HOME is defined relatively to the bin/karaf.

Re: Cannot start Karaf

2014-10-13 Thread Achim Nierbeck
Just another idea that crosses my mind. Did you place the extracted Karaf folder in some restricted folders? Where does it actually reside in? regards, Achim 2014-10-13 14:43 GMT+02:00 Jean-Baptiste Onofré j...@nanthrax.net: KARAF_HOME is the location where you uncompressed Karaf. For

Re: Cannot start Karaf

2014-10-13 Thread David Leangen
Hi, That seems wrong. Your karaf installation does seem quite weird. :-) I installed it in /usr/local/java. The folder there is apache-karat-3.0.2, exactly as tar-gunzipped. :-) Usually, when unset, your KARAF_HOME should point to something like /usr/local/apache-karaf-3.0.1 Well,

Re: Cannot start Karaf

2014-10-13 Thread David Leangen
Hi, Just another idea that crosses my mind. Did you place the extracted Karaf folder in some restricted folders? Where does it actually reside in? Not sure exactly what you mean by “restricted”, but it resides in /usr/local/java.] This is where I install all my apache apps. No problems so

Re: Cannot start Karaf

2014-10-13 Thread James Carman
Karaf will need to be able to write to that directory by default. What user are you using to run karaf? Does he have permissions to write to /usr/local/java/apache-karaf-3.0.2? On Mon, Oct 13, 2014 at 8:51 AM, David Leangen apa...@leangen.net wrote: Hi, Just another idea that crosses my

Re: Cannot start Karaf

2014-10-13 Thread David Leangen
Indeed, it was a permissions problem. Thanks! :-) The error message was misleading, at least for somebody new to Karaf. Perhaps the launcher could check for permissions and fail on error. Just a thought. In any case, thanks to everybody for a super response! I’m not sure how active the

Re: Cannot start Karaf

2014-10-13 Thread Jean-Baptiste Onofré
Good. It's what Achim asked yesterday (by restricted directories). I will create a Jira to add a permission check in Karaf main. Regards JB On 10/13/2014 11:04 PM, David Leangen wrote: Indeed, it was a permissions problem. Thanks! :-) The error message was misleading, at least for somebody