[JBoss-dev] RE: jaspi instance failes to start

Ignore that target for sometime. It is in flux. ________________________________ From: Jaroslaw Kijanowski Sent: Friday, September 15, 2006 11:27 AM To: jboss-development(a)lists.jboss.org Cc: QA Subject: jaspi instance failes to start The testsuite fails while starting the "jaspi" instance in jbossas beta 5: tests.log: *************************** tests-security-jaspi-unit: [echo] creating jaspi config [copy] Copying 153 files to /services/cruisecontrol/checkout/jboss-head-testsuite-1.5/build/output/j boss-5.0.0.Beta/server/jaspi [echo] Overwriting config descriptors [copy] Copying 2 files to /services/cruisecontrol/checkout/jboss-head-testsuite-1.5/build/output/j boss-5.0.0.Beta/server/jaspi [server:start] Starting server "jaspi" with command: [server:start] /opt/jrockit-jdk1.5.0_06/bin/java -cp /services/cruisecontrol/checkout/jboss-head-testsuite-1.5/build/output/j boss-5.0.0.Beta/bin/run.jar:/opt/jrockit-jdk1.5.0_06/lib/tools.jar org.jboss.Main -c jaspi -b localhost BUILD FAILED /services/cruisecontrol/checkout/jboss-head-testsuite-1.5/testsuite/buil d.xml:827: The following error occurred while executing this line: /services/cruisecontrol/checkout/jboss-head-testsuite-1.5/testsuite/buil d.xml:2414: Error starting server "jaspi": Server failed to start; see logs. ************************** The server.log contains this: ************************** 11:25:01,556 ERROR [AbstractKernelController] Error installing to Configured: name=jboss.web:service=WebServer state=Instantiated mode=Manual requiredState=Configured org.jboss.deployment.DeploymentException: No Attribute found with name: AuthorizationManagerService for jboss.web:service=WebServer at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java: 129) ************************** AuthorizationManager isn't present in the following files (should be?): jbossweb-tomcat6.sar\META-INF\webserver-xmbean.xml \trunk\tomcat\src\main\org\jboss\web\tomcat\tc6\Tomcat6.java \trunk\tomcat\src\main\org\jboss\web\tomcat\tc6\Tomcat6MBean.java \trunk\tomcat\src\main\org\jboss\web\tomcat\tc6\TomcatDeployer.java but is still present in jbossweb-tomcat6.sar\META-INF\jboss-service.xml To start the server (jaspi instance) successfully, it's enough to delete following section in jbossweb-tomcat6.sar\META-INF\jboss-service.xml: <depends optional-attribute-name="AuthorizationManagerService" proxy-type="attribute">jboss.security:service=AuthorizationManager </depends> The other way is to add following lines to jbossweb-tomcat6.sar\META-INF\webserver-xmbean.xml: <attribute access="write-only"> <name>AuthorizationManagerService</name> <type>org.jboss.security.plugins.AuthorizationManagerServiceMBean</type> </attribute> What is the right way to get the testsuite successfully run the jaspi-instance?