[ https://issues.jboss.org/browse/RTGOV-476?page=com.atlassian.jira.plugin.... ] David virgil naranjo commented on RTGOV-476: -------------------------------------------- This error appears in the normal flow of fuse fabric deploying. But it dissapears when the deployment is debugged and there are breakpoints in to the jetty-all jar. Steps to follow to deploy without error and check that the application is deployed correctly: Steps - The s-ramp commit has not been merged yet. You can download my development from: https://github.com/dvirgiln/s-ramp/tree/SRAMP-423 Or we can wait Brett will merge on monday. Compile s-ramp and overlord-commons (the head is ok). -Extract the zip in the fuse profiles folder - Execute karaf console. Inside karaf execute these commands: fabric:create --zookeeper-password admin fabric:container-create-child --jvm-opts '-Xms1000m -Xmx1000m -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n' root dd -Debug the s-ramp code in eclipse as remote application port 8787. -Download the jetty-all jar attach as source in the eclipse debug. -Import the breakpoints from the file attached. In case there is an error in the importing, the important ones are: - AggregateLifeCycle 184 - LoginAuthenticator 59 and 61 --> The one that throws the Login Service Not found - SegurityHandler 121 259 287 --> The one that calls the findLoginService - org.eclipse.jetty.server.Server 513 --> Reads the data from the overlord-jetty.xml. Then in the karaf console: fabric:container-add-profile dd overlord-sramp If you debug the code, in the logs: fuse_install/instances/dd/data/log/karaf.log you ll not see any exception. If you add the profile in the child container without debugging, then the exception appears. If the application is deployed without any error and you want to test s-ramp in the browser you have to add to the user that you created the fabric the overlorduser role: jaas:manage --index 3 jaas:roleadd user_name overlorduser jaas:update Then normally in the http://localhost:8182/s-ramp-ui/ should be deployed the application. -- This message was sent by Atlassian JIRA (v6.2.3#6260)