[JBoss Microcontainer Development POJO Server] - Re: Getting rid of conf/jboss-service.xml
by smcgowan@redhat.com
With these changes, the 'standard' and 'web' configs fail to boot. The conf/jboss-service.xml files for these configs contains more than what's defined in https://jira.jboss.org/jira/browse/JBAS-7469. 'default' and 'all' configs start fine.
The standard config fails to boot with:
| 2009-11-19 12:14:23,281 INFO [org.jboss.system.server.profileservice.ProfileServiceBootstrap] (Thread-2) Loading profile: ProfileKey@1f1ad4a[domain=default, server=default, name=standard]
| 2009-11-19 12:14:23,281 DEBUG [org.jboss.system.server.profileservice.repository.AbstractProfileService] (Thread-2) Activating profile: NoopProfile@c7bf90{key = ProfileKey@1f1ad4a[domain=default, server=default, name=standard]}
| 2009-11-19 12:14:23,317 ERROR [org.jboss.system.server.profileservice.ProfileServiceBootstrap] (Thread-2) Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| DEPLOYMENTS MISSING DEPENDENCIES:
| Deployment "NamingService" is missing the following dependencies:
| Dependency "RemoteNamingBean" (should be in state "Configured", but is actually in state "**ERROR**")
| Deployment "jboss.jmx:alias=jmx/rmi/RMIAdaptor" is missing the following dependencies:
| Dependency "jboss:service=Naming" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **")
| Deployment "jboss.jmx:name=Invoker,protocol=jrmp,service=proxyFactory,type=adaptor" is missing the following dependencies:
| Dependency "jboss:service=Naming" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **")
| Deployment "jboss.jmx:name=MBeanProxyRemote,protocol=jrmp,type=adaptor" is missing the following dependencies:
| Dependency "jboss.jmx:name=Invoker,protocol=jrmp,service=proxyFactory,type=adaptor" (should be in state "Create", but is actually in state "Configured")
| Deployment "jboss:service=CorbaNaming" is missing the following dependencies:
| Dependency "jboss:service=Naming" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **")
| Deployment "jboss:service=KeyGeneratorFactory,type=UUID" is missing the following dependencies:
| Dependency "jboss:service=Naming" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **")
| Deployment "jboss:service=Mail" is missing the following dependencies:
| Dependency "jboss:service=Naming" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **")
| Deployment "jboss:service=NamingProviderURLWriter" is missing the following dependencies:
| Dependency "jboss:service=Naming" (should be in state "Configured", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **")
| Dependency "jboss:service=Naming" (should be in state "Configured", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **")
| Deployment "jboss:service=invoker,type=iiop" is missing the following dependencies:
| Dependency "jboss:service=Naming" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **")
|
| DEPLOYMENTS IN ERROR:
| Deployment "jboss:service=Naming" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss:service=Naming' **
| Deployment "JndiViewBean" is in error due to the following reason(s): javax.management.InstanceAlreadyExistsException: jboss:service=JNDIView already registered.
| Deployment "RemoteNamingBean" is in error due to the following reason(s): javax.management.InstanceAlreadyExistsException: jboss:service=Naming already registered., **ERROR**
|
and the web config:
| 13:59:01,245 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@1ff8de3[domain=default, server=default, name=web]
| 13:59:01,245 DEBUG [AbstractProfileService] Activating profile: NoopProfile@17ccb2f{key = ProfileKey@1ff8de3[domain=default, server=default, name=web]}
| 13:59:01,248 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| DEPLOYMENTS MISSING DEPENDENCIES:
| Deployment "WebServer" is missing the following dependencies:
| Dependency "jboss.security:service=JaasSecurityManager" (should be in state "Configured", but is actually in state "** NOT FOUND Depends on 'jboss.security:service=JaasSecurityManager' **")
| Deployment "jboss.jca:name=DefaultDS,service=DataSourceBinding" is missing the following dependencies:
| Dependency "jboss.jca:name=DefaultDS,service=LocalTxCM" (should be in state "Create", but is actually in state "Configured")
| Deployment "jboss.jca:name=DefaultDS,service=LocalTxCM" is missing the following dependencies:
| Dependency "jboss.security:service=JaasSecurityManager" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.security:service=JaasSecurityManager' **")
| Deployment "jboss.jdbc:datasource=DefaultDS,service=metadata" is missing the following dependencies:
| Dependency "jboss.jdbc:service=metadata" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jdbc:service=metadata' **")
| Deployment "jboss.web.deployment:war=/ROOT" is missing the following dependencies:
| Dependency "jboss.web:service=WebServer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.web:service=WebServer' **")
| Deployment "jboss.web.deployment:war=/invoker" is missing the following dependencies:
| Dependency "jboss.web:service=WebServer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.web:service=WebServer' **")
| Deployment "jboss.web.deployment:war=/jmx-console" is missing the following dependencies:
| Dependency "jboss.web:service=WebServer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.web:service=WebServer' **")
|
| DEPLOYMENTS IN ERROR:
| Deployment "jboss.security:service=JaasSecurityManager" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.security:service=JaasSecurityManager' **
| Deployment "jboss.jdbc:service=metadata" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jdbc:service=metadata' **
| Deployment "jboss.web:service=WebServer" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.web:service=WebServer' **
|
|
Another issue seen is that minimal fails to shutdown as part of the jboss-minimal-tests target but that may require changes. Is there still work being done for these configs?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266648#4266648
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266648
16 years, 4 months
[JBoss Microcontainer Development] - Re: Testing Deployers with new Reflect + ClassPool
by flavia.rainone@jboss.com
This is the lifecycle of module resgistry and class pools creation today:
1. Use RegisterModuleCallback as a ModuleRegistry so it can be notified of modules being deployed and undeployed
2. RegisterModuleCallback.addModule adds the module to an unrgisteredModules collection.
3. When ClassPoolRepository.registerClassLoader(CL) is invoked, this will trigger a call to JBossClDelegatingCPFactory.
4. The factory will invoke RegisterModuleCallback.registerModule. At this point, the module is going to be reomved from the unregisteredModules collection and added to the registeredModulesCollection.
5. The factory will iterate through all unregisteredModules of RegisterModuleCallback (the so-called "bootstrap" modules) in order to create the "bootstrap" CPs.
Ales suggested me that I got rid of this way of creating ClassPools, making sure that the ClassPool is created by RegisterModuleCallback.addModule. This way, we get rid of the unregisteredCP collection and we get rid of the "bootstrap" CP creation that causes the aforementioned bug.
Unfortunately, that doesn't work :(. I need the ClassLoader in order to create the ClassPool, and at the point RegisterModuleCallback.addModule is invoked the class loader associated with the module is null.
I'm assuming that there is no easy way of filtering out the modules I need to filter. So I'll use the recursion structure itself to deduct when the module needs to be filtered out and I'll abort the CP creation for those modules.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266616#4266616
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266616
16 years, 4 months