[jboss-dev] AS start-up failure

[Adrian Brock]

I've done this, 
http://jira.jboss.com/jira/browse/JBAS-5308
but the whole thing needs tidying up:
http://jira.jboss.com/jira/browse/JBAS-5309

So don't use this as example of how to do it,
although the principle of "services in deploy" and injecting
service names it correct. :-)

One issue was jboss-messaging not depending on the
security services for its JAASStore.
I've made it depend upon "XMLLoginConfig"

I'm not convinced there is a real dependency here
since none of the security services seem to depend on
each other.

e.g. it could parse the login-config.xml but
still the java:/jaas context is not bound yet?
Which means jboss-messaging would still fail.

We also need to ask whether some of this
should be overridable per deployment.

e.g. add "SecurityManagementName" (the security lookup
mechanism) to jboss(-web).xml like the security domain

The defaults on the deployer should just be used
when there is nothing explicit.

OFF/RELATED TOPIC

Some of this config is mandatory so shouldn't there be
something like?

public void EJBDeployer::create()
{
   if (securityManagementName == null)
      throw new IllegalStateException("No security management name
configured");
}

On Wed, 2008-03-12 at 17:28 +0100, Adrian Brock wrote:
> As per the other post.
> 
> I'm going to move these services to the deploy folder
> and do proper injection into the EJB/Web mbeans.
> 
> The fix for the @JMX is coming shortly, 
> 
> It's fundamentally a JBossXB issue that currently means
> we can't deploy the configuration early enough for the
> deployers to be use the @JMX attribute.
> 
> On Wed, 2008-03-12 at 11:36 -0500, Anil Saldhana wrote:
> > This was done today by stefan. Adrian, can you suggest a solution for 
> > this, please? We need the JMX annotation.
> > 
> > Adrian Brock wrote:
> > > I'm seeing a total different issue:
> > > 
> > > *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required
> > > State:Actual State}
> > > 
> > > SecurityConfig
> > >  -> jboss.security:service=XMLLoginConfig{Start:** NOT FOUND **}
> > >  -> jboss.security:service=XMLLoginConfig{Create:** NOT FOUND **}
> > > 
> > > 
> > > *** CONTEXTS IN ERROR: Name -> Error
> > > 
> > > jboss.security:service=XMLLoginConfig -> ** NOT FOUND **
> > > 
> > > 
> > > This is because the XMLLoginConfig POJO in the security deployers
> > > is trying to use the @JMX annotation before the advice has been
> > > installed in AOP.
> > > 
> > > On Wed, 2008-03-12 at 13:37 +0200, Dimitris Andreadis wrote:
> > >> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15/442/console
> > >>
> > >> The server doesn't start properly due to the 2 bean files in
> > >> deploy/jbossws.sar/META-INF
> > >>    jbossws-beans.xml
> > >>    jbossws-native50-beans.xml
> > >>
> > >> 13:33:03,250 ERROR [AbstractKernelController] Error installing to Parse: name=vf
> > >> sfile:/X:/cvs/jboss-public/jboss-head/build/output/jboss-5.0.0.CR1/server/all/de
> > >> ploy/jbossws.sar/ state=Not Installed mode=Manual requiredState=Parse
> > >> org.jboss.deployers.spi.DeploymentException: Only one file is allowed, found=[Fi
> > >> leHandler at 8930293[path=jbossws.sar/META-INF/jbossws-beans.xml context=file:/X:/c
> > >> vs/jboss-public/jboss-head/build/output/jboss-5.0.0.CR1/server/all/deploy/ real=
> > >> file:/X:/cvs/jboss-public/jboss-head/build/output/jboss-5.0.0.CR1/server/all/dep
> > >> loy/jbossws.sar/META-INF/jbossws-beans.xml], FileHandler at 2464124[path=jbossws.sa
> > >> r/META-INF/jbossws-native50-beans.xml context=file:/X:/cvs/jboss-public/jboss-he
> > >> ad/build/output/jboss-5.0.0.CR1/server/all/deploy/ real=file:/X:/cvs/jboss-publi
> > >> c/jboss-head/build/output/jboss-5.0.0.CR1/server/all/deploy/jbossws.sar/META-INF
> > >> /jbossws-native50-beans.xml]]
> > _______________________________________________
> > jboss-development mailing list
> > jboss-development at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jboss-development
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx