Did you have any prb if start GateIn 3.2 without KS suite?
no, the plain GateIn 3.2/JBoss 5.1 bundle starts without a problem, so the environment seems to be fok.
If you cannot start GateIn, it is clearly not due to this exception as you can see it is an exception for debugging purpose only, it cannot prevent the product to work normally. First of all, I believe that you should set another logging level otherwise the perfs will be terrible, then please provide the full log file to let us identify the real issue.
Are you sure you start GateIn with a jdk6 ???
@macois: I think he's using jdk6, because He could start GateIn if KS suite wasn't bundled.
Sorry for the late reply.
Meanwhile i figured it out: as you mentioned, the message i posted is just for debugging. I don't think that the checkout, build and installation to a clean 5.1. app server works with the versions i tried (Gatein 3.2, App Server 5.1, KS Suite 2.2) - at least i was unable to get that running. What worked for me was the build of the KS Suite 2.1.0.GA and the installation/deploy of gatein-exo-ks-2.1.0-GA.ear to a Jboss 5.1/Gatein 3.1 bundle.
Thanks for your Support.