clebert: Nihility: Can I ask you a dumb (user) question?
[12:35pm] clebert: Nihility: I thought that JBoss-7 had everything started on its startup…
[12:35pm] clebert: is there any services that are only started over demand?
[12:36pm] Nihility: clebert: a few, mainly osgi
[12:37pm] clebert: Nihility: what about EJBs, WebStack…etc?
[12:37pm] Nihility: clebert: all started
[12:37pm] Nihility: clebert: we eagerly start everything that is popular
[12:37pm] Nihility: clebert: we didn’t start osgi because we expect it to be used by a small fraction of folks
[12:38pm] Nihility: and it adds overhead
[12:38pm] clebert: Nihility: thanks a lot! That’s what I though… I got into a battle with a troll user
[12:38pm] Nihility: run jboss-admin.sh
[12:38pm] Nihility: then do
[12:39pm] Nihility: cd core-service/service=container
[12:39pm] Nihility: :dump-services
[12:39pm] Nihility: actually this would be easier
[12:39pm] Nihility: ./bin/jboss-admin.sh --connect --command=/core-service=service-container:dump-services | grep DOWN
[quote=clebert.suconic]
clebert: Nihility: Can I ask you a dumb (user) question?
[12:35pm] clebert: Nihility: I thought that JBoss-7 had everything started on its startup…
[12:35pm] clebert: is there any services that are only started over demand?
[12:36pm] Nihility: clebert: a few, mainly osgi
[12:37pm] clebert: Nihility: what about EJBs, WebStack…etc?
[12:37pm] Nihility: clebert: all started
[12:37pm] Nihility: clebert: we eagerly start everything that is popular
[12:37pm] Nihility: clebert: we didn’t start osgi because we expect it to be used by a small fraction of folks
[12:38pm] Nihility: and it adds overhead
[12:38pm] clebert: Nihility: thanks a lot! That’s what I though… I got into a battle with a troll user
[12:38pm] Nihility: run jboss-admin.sh
[12:38pm] Nihility: then do
[12:39pm] Nihility: cd core-service/service=container
[12:39pm] Nihility: :dump-services
[12:39pm] Nihility: actually this would be easier[/quote]
[Server:server-one] 11:45:05,465 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final “Lightning” started in 2963ms - Started 87 of 138 services (51 services are passive or on-demand)
[Server:server-two] 11:45:05,472 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
[Server:server-two] 11:45:05,509 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final “Lightning” started in 2925ms - Started 87 of 138 services (51 services are passive or on-demand)
[quote=chun][quote=clebert.suconic]
clebert: Nihility: Can I ask you a dumb (user) question?
[12:35pm] clebert: Nihility: I thought that JBoss-7 had everything started on its startup…
[12:35pm] clebert: is there any services that are only started over demand?
[12:36pm] Nihility: clebert: a few, mainly osgi
[12:37pm] clebert: Nihility: what about EJBs, WebStack…etc?
[12:37pm] Nihility: clebert: all started
[12:37pm] Nihility: clebert: we eagerly start everything that is popular
[12:37pm] Nihility: clebert: we didn’t start osgi because we expect it to be used by a small fraction of folks
[12:38pm] Nihility: and it adds overhead
[12:38pm] clebert: Nihility: thanks a lot! That’s what I though… I got into a battle with a troll user
[12:38pm] Nihility: run jboss-admin.sh
[12:38pm] Nihility: then do
[12:39pm] Nihility: cd core-service/service=container
[12:39pm] Nihility: :dump-services
[12:39pm] Nihility: actually this would be easier[/quote]
[Server:server-one] 11:45:05,465 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final “Lightning” started in 2963ms - Started 87 of 138 services (51 services are passive or on-demand)
[Server:server-two] 11:45:05,472 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
[Server:server-two] 11:45:05,509 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final “Lightning” started in 2925ms - Started 87 of 138 services (51 services are passive or on-demand)
[/quote]
[standalone@localhost:9999 core-service=service-container] :dump-services
{
“outcome” => “success”,
“result” => “Services for jboss-as:
Service “jbosgi.AutoInstallProvider” (class org.jboss.as.osgi.service.AutoInstallIntegration) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jbosgi.Framework.INITIALIZED, jbosgi.SystemBundle, jboss.server.environment, jbosgi.StartLevel, jbosgi.BundleManager) (has unavailable dependency)
Service “jbosgi.BundleInstallProvider” (class org.jboss.as.osgi.service.BundleInstallProviderIntegration) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jbosgi.BundleManager, jbosgi.Framework.CREATED, jboss.as.server-controller)
Service “jbosgi.BundleManager” (class org.jboss.osgi.framework.internal.BundleManager) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap)
Service “jbosgi.Framework.ACTIVATOR” (class org.jboss.osgi.framework.internal.FrameworkActivator) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.Framework.ACTIVE) (has unavailable dependency)
Service “jbosgi.Framework.ACTIVE” (class org.jboss.osgi.framework.internal.FrameworkActive) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.AutoInstallProvider.COMPLETE, jbosgi.Framework.INITIALIZED, jbosgi.AutoInstallProvider) (has unavailable dependency)
Service “jbosgi.Framework.CREATED” (class org.jboss.osgi.framework.internal.FrameworkCreate) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.internal.BundleResolver, jbosgi.SystemBundle, jbosgi.internal.ServiceManager, jbosgi.internal.BundleStorage, jbosgi.internal.FrameworkEvents, jbosgi.internal.DeploymentFactory, jbosgi.internal.ModuleManager, jbosgi.internal.NativeCode)
Service “jbosgi.Framework.INITIALIZED” (class org.jboss.osgi.framework.internal.FrameworkInit) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.internal.CoreServices, jbosgi.internal.PersistentBundles, jbosgi.internal.PersistentBundles.COMPLETE, jbosgi.Framework.CREATED) (has unavailable dependency)
Service “jbosgi.FrameworkModuleProvider” (class org.jboss.as.osgi.service.FrameworkBootstrapService$FrameworkModuleIntegration) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jbosgi.SystemModuleProvider)
Service “jbosgi.ModuleLoaderProvider” (class org.jboss.as.osgi.service.ModuleLoaderIntegration) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jboss.as.service-module-loader)
Service “jbosgi.PackageAdmin” (class org.jboss.osgi.framework.internal.PackageAdminPlugin) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.internal.BundleResolver, jbosgi.internal.FrameworkEvents, jbosgi.BundleManager, jbosgi.SystemContext, jbosgi.Framework.CREATED, jbosgi.internal.ModuleManager)
Service “jbosgi.StartLevel” (class org.jboss.osgi.framework.internal.StartLevelPlugin) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.SystemBundle, jbosgi.internal.FrameworkEvents, jbosgi.BundleManager, jbosgi.Framework.CREATED)
Service “jbosgi.SystemBundle” (class org.jboss.osgi.framework.internal.SystemBundleService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.internal.BundleStorage, jbosgi.internal.BundleResolver, jbosgi.internal.SystemPackages, jbosgi.FrameworkModuleProvider)
Service “jbosgi.SystemContext” (class org.jboss.osgi.framework.internal.SystemContextService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.SystemBundle)
Service “jbosgi.SystemModuleProvider” (class org.jboss.osgi.framework.internal.DefaultSystemModuleProvider) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.internal.SystemPackages)
Service “jbosgi.SystemServicesProvider” (class org.jboss.as.osgi.service.FrameworkBootstrapService$SystemServicesIntegration) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jboss.mbean.server, jbosgi.Framework.CREATED)
Service “jbosgi.internal.BundleResolver” (class org.jboss.osgi.framework.internal.ResolverPlugin) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.BundleManager, jbosgi.internal.NativeCode, jbosgi.internal.ModuleManager)
Service “jbosgi.internal.BundleStorage” (class org.jboss.osgi.framework.internal.BundleStoragePlugin) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.BundleManager)
Service “jbosgi.internal.CoreServices” (class org.jboss.osgi.framework.internal.CoreServices) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.StartLevel, jbosgi.BundleInstallProvider, jbosgi.PackageAdmin, jbosgi.SystemServicesProvider, jbosgi.internal.URLHandler, jbosgi.SystemContext, jbosgi.Framework.CREATED, jbosgi.internal.WebXMLVerifier, jbosgi.internal.LifecycleInterceptor)
Service “jbosgi.internal.DeploymentFactory” (class org.jboss.osgi.framework.internal.DeploymentFactoryPlugin) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.BundleManager, jbosgi.internal.BundleResolver)
Service “jbosgi.internal.FrameworkEvents” (class org.jboss.osgi.framework.internal.FrameworkEventsPlugin) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.BundleManager, jbosgi.SystemContext)
Service “jbosgi.internal.LifecycleInterceptor” (class org.jboss.osgi.framework.internal.LifecycleInterceptorPlugin) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.SystemContext, jbosgi.Framework.CREATED)
Service “jbosgi.internal.ModuleManager” (class org.jboss.osgi.framework.internal.ModuleManagerPlugin) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.SystemModuleProvider, jbosgi.ModuleLoaderProvider, jbosgi.BundleManager, jbosgi.internal.SystemPackages)
Service “jbosgi.internal.NativeCode” (class org.jboss.osgi.framework.internal.NativeCodePlugin) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.BundleManager)
Service “jbosgi.internal.PersistentBundles” (class org.jboss.osgi.framework.internal.PersistentBundlesInstaller) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.internal.CoreServices, jbosgi.internal.BundleStorage, jbosgi.BundleManager, jbosgi.internal.DeploymentFactory)
Service “jbosgi.internal.ServiceManager” (class org.jboss.osgi.framework.internal.ServiceManagerPlugin) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.BundleManager, jbosgi.internal.ModuleManager, jbosgi.internal.FrameworkEvents)
Service “jbosgi.internal.SystemPackages” (class org.jboss.osgi.framework.internal.SystemPackagesPlugin) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap)
Service “jbosgi.internal.URLHandler” (class org.jboss.osgi.framework.internal.URLHandlerPlugin) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.BundleManager, jbosgi.SystemContext, jbosgi.Framework.CREATED)
Service “jbosgi.internal.WebXMLVerifier” (class org.jboss.osgi.framework.internal.WebXMLVerifierInterceptor) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.osgi.as.framework.bootstrap) (dependencies: jbosgi.SystemContext, jbosgi.Framework.CREATED, jbosgi.internal.LifecycleInterceptor)
Service “jbosgi.xservice.“javax.naming.InitialContext”” (class org.jboss.as.naming.InitialContextFactoryService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.naming)
Service “jboss.txn.TransactionManager” (aliases: jbosgi.xservice.“javax.transaction.TransactionManager”) (class org.jboss.as.txn.TransactionManagerService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.txn.ArjunaTransactionManager)
Service “jboss.txn.UserTransaction” (aliases: jbosgi.xservice.“javax.transaction.UserTransaction”) (class org.jboss.as.txn.UserTransactionService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.txn.ArjunaTransactionManager)
Service “jboss.as” (class org.jboss.as.server.ApplicationServerService) mode ACTIVE state UP
Service “jboss.as.external-module-service” (class org.jboss.as.server.moduleservice.ExternalModuleService) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.as.module-index-service” (class org.jboss.as.server.moduleservice.ModuleIndexService) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.as.server-controller” (class org.jboss.as.server.ServerService) mode ACTIVE state UP (parent: jboss.as) (dependencies: jboss.as.external-module-service, jboss.content-repository, jboss.as.service-module-loader, jboss.deployment-repository)
Service “jboss.as.server-controller.management.operation.handler” (class org.jboss.as.controller.remote.ModelControllerClientOperationHandlerFactoryService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.as.server-controller)
Service “jboss.as.service-module-loader” (class org.jboss.as.server.moduleservice.ServiceModuleLoader) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.as.weld.singleton” (class org.jboss.as.weld.services.TCCLSingletonService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller)
Service “jboss.binding.http” (class org.jboss.as.server.services.net.SocketBindingService) mode ON_DEMAND state UP (parent: jboss.as.server-controller) (dependencies: jboss.socket-binding-manager)
Service “jboss.binding.https” (class org.jboss.as.server.services.net.SocketBindingService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jboss.socket-binding-manager)
Service “jboss.binding.jmx-connector-registry” (class org.jboss.as.server.services.net.SocketBindingService) mode ON_DEMAND state UP (parent: jboss.as.server-controller) (dependencies: jboss.socket-binding-manager)
Service “jboss.binding.jmx-connector-server” (class org.jboss.as.server.services.net.SocketBindingService) mode ON_DEMAND state UP (parent: jboss.as.server-controller) (dependencies: jboss.socket-binding-manager)
Service “jboss.binding.jndi” (class org.jboss.as.server.services.net.SocketBindingService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jboss.socket-binding-manager)
Service “jboss.binding.osgi-http” (class org.jboss.as.server.services.net.SocketBindingService) mode ON_DEMAND state UP (parent: jboss.as.server-controller) (dependencies: jboss.socket-binding-manager)
Service “jboss.binding.remoting” (class org.jboss.as.server.services.net.SocketBindingService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jboss.socket-binding-manager)
Service “jboss.binding.txn-recovery-environment” (class org.jboss.as.server.services.net.SocketBindingService) mode ON_DEMAND state UP (parent: jboss.as.server-controller) (dependencies: jboss.socket-binding-manager)
Service “jboss.binding.txn-status-manager” (class org.jboss.as.server.services.net.SocketBindingService) mode ON_DEMAND state UP (parent: jboss.as.server-controller) (dependencies: jboss.socket-binding-manager)
Service “jboss.cached-connection-manager” (class org.jboss.as.connector.services.CcmService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.connector.transactionintegration)
Service “jboss.connector.config” (class org.jboss.as.connector.subsystems.jca.JcaConfigService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.connector.defaultbootstrapcontext)
Service “jboss.connector.defaultbootstrapcontext” (class org.jboss.as.connector.bootstrap.DefaultBootStrapContextService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.connector.workmanager, jboss.txn.XATerminator, jboss.txn.ArjunaTransactionManager)
Service “jboss.connector.transactionintegration” (class org.jboss.as.connector.transactionintegration.TransactionIntegrationService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.txn.ArjunaRecoveryManager, jboss.txn.TransactionManager, jboss.txn.UserTransactionRegistry, jboss.txn.XATerminator, jboss.txn.TransactionSynchronizationRegistry)
Service “jboss.connector.workmanager” (class org.jboss.as.connector.workmanager.WorkManagerService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.thread.executor.jca-short-running-threads, jboss.txn.XATerminator, jboss.thread.executor.jca-long-running-threads)
Service “jboss.content-repository” (class org.jboss.as.server.deployment.repository.impl.ContentRepositoryImpl) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.data-source.java:jboss/datasources/ExampleDS” (class org.jboss.as.connector.subsystems.datasources.LocalDataSourceService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.jdbc-driver.registry, jboss.naming, jboss.connector.transactionintegration, jboss.security.subject-factory, jboss.jdbc-driver.h2, jboss.management_repository, jboss.data-source-config.java:jboss/datasources/ExampleDS)
Service “jboss.data-source.reference-factory.java:jboss/datasources/ExampleDS” (class org.jboss.as.connector.subsystems.datasources.DataSourceReferenceFactoryService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.data-source.java:jboss/datasources/ExampleDS)
Service “jboss.data-source-config.java:jboss/datasources/ExampleDS” (class org.jboss.as.connector.subsystems.datasources.DataSourceConfigService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.deployment.chains” (class org.jboss.as.server.deployment.DeployerChainsService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.deployment.extension-index” (class org.jboss.as.server.moduleservice.ExtensionIndexService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller)
Service “jboss.deployment-repository” (class org.jboss.as.server.deployment.repository.impl.ServerDeploymentRepositoryImpl) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.ejb.utilities” (class org.jboss.as.ejb3.component.EJBUtilities) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.txn.TransactionManager, jboss.security.simple-security-manager, jboss.txn.TransactionSynchronizationRegistry, jboss.txn.UserTransaction)
Service “jboss.infinispan” (class org.jboss.msc.service.ValueService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jboss.infinispan.hibernate)
Service “jboss.infinispan.config.defaults” (class org.jboss.as.clustering.infinispan.subsystem.EmbeddedCacheManagerDefaultsService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller)
Service “jboss.infinispan.hibernate” (class org.jboss.as.clustering.infinispan.subsystem.EmbeddedCacheManagerService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jboss.txn.TransactionManager, jboss.mbean.server, jboss.infinispan.config.defaults, jboss.txn.TransactionSynchronizationRegistry)
Service “jboss.infinispan.hibernate.local-query” (aliases: jboss.infinispan.hibernate.___defaultcache) (class org.jboss.as.clustering.infinispan.subsystem.CacheService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jboss.infinispan.hibernate, jboss.naming.context.java.jboss.infinispan/hibernate)
Service “jboss.infinispan.hibernate.entity” (class org.jboss.as.clustering.infinispan.subsystem.CacheService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jboss.infinispan.hibernate, jboss.naming.context.java.jboss.infinispan/hibernate)
Service “jboss.infinispan.hibernate.timestamps” (class org.jboss.as.clustering.infinispan.subsystem.CacheService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jboss.infinispan.hibernate, jboss.naming.context.java.jboss.infinispan/hibernate)
Service “jboss.ironjacamar.mdr” (class org.jboss.as.connector.mdr.MdrService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.jdbc-driver.h2” (class org.jboss.as.connector.registry.DriverService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.jdbc-driver.registry)
Service “jboss.jdbc-driver.registry” (class org.jboss.as.connector.registry.DriverRegistryService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.jndi-view.extension.ee” (class org.jboss.as.ee.subsystem.EEJndiViewExtension) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.jndi-view.extension.registry)
Service “jboss.jndi-view.extension.registry” (class org.jboss.as.naming.management.JndiViewExtensionRegistry) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.jpa” (class org.jboss.as.jpa.service.JPAService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.logging.handler.CONSOLE” (class org.jboss.as.logging.ConsoleHandlerService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.logging.handler.FILE” (class org.jboss.as.logging.PeriodicRotatingFileHandlerService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.logging.handler-file.FILE)
Service “jboss.logging.handler-file.FILE” (class org.jboss.as.logging.HandlerFileService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.server.path.“jboss.server.log.dir”)
Service “jboss.logging.logger.“com.arjuna”” (class org.jboss.as.logging.LoggerService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.logging.logger.“org.apache.tomcat.util.modeler”” (class org.jboss.as.logging.LoggerService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.logging.logger.“sun.rmi”” (class org.jboss.as.logging.LoggerService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.logging.root-logger” (class org.jboss.as.logging.RootLoggerService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.logging.root-logger-handler.CONSOLE” (class org.jboss.as.logging.LoggerHandlerService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.logging.root-logger, jboss.logging.handler.CONSOLE)
Service “jboss.logging.root-logger-handler.FILE” (class org.jboss.as.logging.LoggerHandlerService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.logging.root-logger, jboss.logging.handler.FILE)
Service “jboss.management_repository” (class org.jboss.as.connector.services.ManagementRepositoryService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.mbean.connector” (class org.jboss.as.jmx.JMXConnectorService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.binding.jmx-connector-server, jboss.mbean.server, jboss.binding.jmx-connector-registry)
Service “jboss.mbean.server” (class org.jboss.as.jmx.MBeanServerService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.naming” (aliases: jboss.naming.context.java) (class org.jboss.as.naming.service.NamingService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.naming.context.java.app” (class org.jboss.as.naming.service.EEContextService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.naming.context.java)
Service “jboss.naming.context.java.comp” (class org.jboss.as.naming.service.EEContextService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.naming.context.java)
Service “jboss.naming.context.java.global” (class org.jboss.as.naming.service.GlobalContextService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.naming.context.java)
Service “jboss.naming.context.java.jboss.TransactionManager” (aliases: jboss.naming.context.java.java:jboss/TransactionManager) (class org.jboss.as.naming.service.BinderService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.naming.context.java.jboss, jboss.txn.TransactionManager)
Service “jboss.naming.context.java.jboss.TransactionSynchronizationRegistry” (aliases: jboss.naming.context.java.java:jboss/TransactionSynchronizationRegistry) (class org.jboss.as.naming.service.BinderService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.naming.context.java.jboss, jboss.txn.TransactionSynchronizationRegistry)
Service “jboss.naming.context.java.jboss.infinispan/hibernate” (aliases: jboss.naming.context.java.java:jboss/infinispan/hibernate) (class org.jboss.as.naming.service.BinderService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jboss.naming.context.java.jboss, jboss.infinispan.hibernate)
Service “jboss.naming.context.java.jboss” (class org.jboss.as.naming.service.GlobalContextService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.naming.context.java)
Service “jboss.naming.context.java.jboss.datasources/ExampleDS” (class org.jboss.as.naming.service.BinderService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.data-source.reference-factory.java:jboss/datasources/ExampleDS, jboss.naming.context.java.jboss)
Service “jboss.naming.context.java.jboss.jaas” (class org.jboss.as.naming.service.BinderService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.naming.context.java.jboss, jboss.security.security-management)
Service “jboss.naming.context.java.module” (class org.jboss.as.naming.service.EEContextService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.naming.context.java)
Service “jboss.network.management” (class org.jboss.as.server.services.net.NetworkInterfaceService) mode ON_DEMAND state UP (parent: jboss.as.server-controller)
Service “jboss.network.public” (class org.jboss.as.server.services.net.NetworkInterfaceService) mode ON_DEMAND state UP (parent: jboss.as.server-controller)
Service “jboss.osgi.as.framework.bootstrap” (class org.jboss.as.osgi.service.FrameworkBootstrapService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.server.environment, jboss.binding.osgi-http)
Service “jboss.osgi.as.framework.starttracker” (class org.jboss.as.osgi.deployment.BundleStartTracker) mode PASSIVE state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jbosgi.PackageAdmin)
Service “jboss.osgi.configadmin” (class org.jboss.as.osgi.service.ConfigAdminServiceImpl) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.raregistry” (class org.jboss.as.connector.registry.ResourceAdapterDeploymentRegistryService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.ironjacamar.mdr)
Service “jboss.rarepository” (class org.jboss.as.connector.rarepository.RaRepositoryService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.ironjacamar.mdr)
Service “jboss.remoting.authentication_provider” (class org.jboss.as.remoting.RealmAuthenticationProviderService) mode ON_DEMAND state UP (parent: jboss.as.server-controller)
Service “jboss.remoting.authentication_provider.option_map” (class org.jboss.as.remoting.RealmOptionMapService) mode ON_DEMAND state UP (parent: jboss.as.server-controller) (dependencies: jboss.remoting.authentication_provider)
Service “jboss.remoting.channel.management” (class org.jboss.as.remoting.ChannelOpenListenerService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.remoting.endpoint, jboss.as.server-controller.management.operation.handler)
Service “jboss.remoting.endpoint” (class org.jboss.as.remoting.EndpointService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.remoting.server.management.9999” (class org.jboss.as.remoting.InjectedNetworkBindingStreamServerService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.remoting.authentication_provider, jboss.network.management, jboss.remoting.endpoint, jboss.remoting.authentication_provider.option_map)
Service “jboss.security.bootstrap” (class org.jboss.as.security.service.SecurityBootstrapService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.security.jaas” (class org.jboss.as.security.service.JaasConfigurationService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.security.security-domain.other” (class org.jboss.as.security.service.SecurityDomainService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.txn.TransactionManager, jboss.security.security-management, jboss.security.jaas)
Service “jboss.security.security-management” (class org.jboss.as.security.service.SecurityManagementService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.security.simple-security-manager” (class org.jboss.as.security.service.SimpleSecurityManagerService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.security.subject-factory” (class org.jboss.as.security.service.SubjectFactoryService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.security.security-management)
Service “jboss.server.controller.management.security_realm.PropertiesMgmtSecurityRealm” (class org.jboss.as.domain.management.security.SecurityRealmService) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jboss.server.controller.management.security_realm.PropertiesMgmtSecurityRealm.properties)
Service “jboss.server.controller.management.security_realm.PropertiesMgmtSecurityRealm.properties” (class org.jboss.as.domain.management.security.PropertiesCallbackHandler) mode ON_DEMAND state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: jboss.server.path.“jboss.server.config.dir”)
Service “jboss.server.deployment.scanner.default” (class org.jboss.as.server.deployment.scanner.DeploymentScannerService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.server.deployment.scanner.default.path, jboss.as.server-controller, jboss.content-repository, jboss.server.path.“jboss.server.base.dir”, jboss.deployment-repository, jboss.deployment.chains)
Service “jboss.server.deployment.scanner.default.path” (class org.jboss.as.server.services.path.RelativePathService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.server.path.“jboss.server.base.dir”)
Service “jboss.server.environment” (class org.jboss.as.server.ServerEnvironmentService) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.server.path.“java.home”” (class org.jboss.as.server.services.path.AbsolutePathService) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.server.path.“jboss.home.dir”” (class org.jboss.as.server.services.path.AbsolutePathService) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.server.path.“jboss.server.base.dir”” (class org.jboss.as.server.services.path.AbsolutePathService) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.server.path.“jboss.server.config.dir”” (class org.jboss.as.server.services.path.AbsolutePathService) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.server.path.“jboss.server.data.dir”” (class org.jboss.as.server.services.path.AbsolutePathService) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.server.path.“jboss.server.log.dir”” (class org.jboss.as.server.services.path.AbsolutePathService) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.server.path.“jboss.server.temp.dir”” (class org.jboss.as.server.services.path.AbsolutePathService) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.server.path.“user.dir”” (class org.jboss.as.server.services.path.AbsolutePathService) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.server.path.“user.home”” (class org.jboss.as.server.services.path.AbsolutePathService) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.serverManagement.controller.management.http” (class org.jboss.as.server.mgmt.HttpManagementService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.server.path.“jboss.server.temp.dir”, jboss.as.server-controller, jboss.network.management)
Service “jboss.shutdown-handler” (class org.jboss.as.server.mgmt.ShutdownHandlerImpl) mode ACTIVE state UP (parent: jboss.as)
Service “jboss.socket-binding-manager” (class org.jboss.as.server.services.net.SocketBindingManagerService) mode ON_DEMAND state UP (parent: jboss.as.server-controller) (dependencies: jboss.network.public)
Service “jboss.thread.executor.jca-long-running-threads” (class org.jboss.as.threads.BoundedQueueThreadPoolService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.thread.executor.jca-long-running-threads.thread-factory)
Service “jboss.thread.executor.jca-long-running-threads.thread-factory” (class org.jboss.as.threads.ThreadFactoryService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.thread.executor.jca-short-running-threads” (class org.jboss.as.threads.BoundedQueueThreadPoolService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.thread.executor.jca-short-running-threads.thread-factory)
Service “jboss.thread.executor.jca-short-running-threads.thread-factory” (class org.jboss.as.threads.ThreadFactoryService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.txn.ArjunaObjectStoreEnvironment” (class org.jboss.as.txn.ArjunaObjectStoreEnvironmentService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.txn.CoreEnvironment, jboss.txn.paths.object-store)
Service “jboss.txn.ArjunaRecoveryManager” (class org.jboss.as.txn.ArjunaRecoveryManagerService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.binding.txn-status-manager, jboss.txn.CoreEnvironment, jboss.txn.ArjunaObjectStoreEnvironment, jboss.binding.txn-recovery-environment, jboss.iiop.orb)
Service “jboss.txn.ArjunaTransactionManager” (class org.jboss.as.txn.ArjunaTransactionManagerService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.txn.ArjunaRecoveryManager, jboss.txn.CoreEnvironment, jboss.txn.XATerminator, jboss.iiop.orb, jboss.txn.ArjunaObjectStoreEnvironment)
Service “jboss.txn.CoreEnvironment” (class org.jboss.as.txn.CoreEnvironmentService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.txn.paths.core-var-dir)
Service “jboss.txn.TransactionSynchronizationRegistry” (class org.jboss.as.txn.TransactionSynchronizationRegistryService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.txn.ArjunaTransactionManager)
Service “jboss.txn.UserTransactionRegistry” (class org.jboss.as.txn.UserTransactionRegistryService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.txn.XATerminator” (class org.jboss.as.txn.XATerminatorService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Service “jboss.txn.paths.core-var-dir” (class org.jboss.as.server.services.path.RelativePathService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.server.path.“jboss.server.data.dir”)
Service “jboss.txn.paths.object-store” (class org.jboss.as.server.services.path.RelativePathService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.server.path.“jboss.server.data.dir”)
Service “jboss.web” (class org.jboss.as.web.WebServerService) mode ON_DEMAND state UP (parent: jboss.as.server-controller) (dependencies: jboss.server.path.“jboss.server.temp.dir”, jboss.mbean.server)
Service “jboss.web.connector.http” (class org.jboss.as.web.WebConnectorService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.binding.http, jboss.web)
Service “jboss.web.default-host.welcome” (class org.jboss.as.web.WelcomeContextService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.server.path.“jboss.home.dir”, jboss.serverManagement.controller.management.http, jboss.web.host.default-host)
Service “jboss.web.host.default-host” (class org.jboss.as.web.WebVirtualHostService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: jboss.server.path.“jboss.server.temp.dir”, jboss.web)
147 services displayed
”
}
Sera que voce sabe ler?
Algum servicos ficam sim em Lazy, principalmente servicos de OSGI, so os poucos utilizados. Web, EJBs… tudo ja esta inicializado.
Sou um dos desenvolvedores do JBoss, participei de discussoes iniciais, um dos pontos era ter tudo disponivel. (a nao ser que fosse de baixo uso).
Achei que eu encontraria um pouco mais de civilidade entre os Brasileiros, mas voce pelo visto e uma regra a parte!
Nao espere por nenhuma outra mensagem minha nessa thread. </mute on>
[quote=clebert.suconic][quote=chun]
[Server:server-one] 11:45:05,465 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final “Lightning” started in 2963ms - Started 87 of 138 services (51 services are passive or on-demand)
[Server:server-two] 11:45:05,472 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
[Server:server-two] 11:45:05,509 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final “Lightning” started in 2925ms - Started 87 of 138 services (51 services are passive or on-demand)
[/quote]
Sera que voce sabe ler?
Algum servicos ficam sim em Lazy, principalmente servicos de OSGI, so os poucos utilizados. Web, EJBs… tudo ja esta inicializado.
Sou um dos desenvolvedores do JBoss, participei de discussoes iniciais, um dos pontos era ter tudo disponivel. (a nao ser que fosse de baixo uso).
Achei que eu encontraria um pouco mais de civilidade entre os Brasileiros, mas voce pelo visto e uma regra a parte!
Nao espere por nenhuma outra mensagem minha nessa thread. </mute on>[/quote]
Ahhh LAZY QUER DIZER “PRONTO” … legal hein ? tradução da equipe do Jboss bem curiosa…
Por favor… LAZY é LAZY. Pronto é pronto.
[quote=chun][quote=clebert.suconic][quote=chun]
[Server:server-one] 11:45:05,465 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final “Lightning” started in 2963ms - Started 87 of 138 services (51 services are passive or on-demand)
[Server:server-two] 11:45:05,472 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
[Server:server-two] 11:45:05,509 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final “Lightning” started in 2925ms - Started 87 of 138 services (51 services are passive or on-demand)
[/quote]
Sera que voce sabe ler?
Algum servicos ficam sim em Lazy, principalmente servicos de OSGI, so os poucos utilizados. Web, EJBs… tudo ja esta inicializado.
Sou um dos desenvolvedores do JBoss, participei de discussoes iniciais, um dos pontos era ter tudo disponivel. (a nao ser que fosse de baixo uso).
Achei que eu encontraria um pouco mais de civilidade entre os Brasileiros, mas voce pelo visto e uma regra a parte!
Nao espere por nenhuma outra mensagem minha nessa thread. </mute on>[/quote]
Ahhh LAZY QUER DIZER “PRONTO” … legal hein ? tradução da equipe do Jboss bem curiosa…
Por favor… LAZY é LAZY. Pronto é pronto.
[/quote]
É… tem gente que não sabe ler, tem gente que é burra e tem gente que é os dois. São sempre os mesmos babacas que gostam de aparecer, esse fórum já foi bem melhor.
[mute on]
E… vc nao sabe ler mesmo… (E eu pelo visto nao consigo manter uma promeca de nao escrever novamente)
Eu disse Alguns Servicos ficam em Lazy!!! que sao pouco utilizados.
EJB, WEB Server, JMS (HornetQ) e outros importantes sao pre-inicializados.
[quote=clebert.suconic]E… vc nao sabe ler mesmo… (E eu pelo visto nao consigo manter uma promeca de nao escrever novamente)
Eu disse Alguns Servicos ficam em Lazy!!! que sao pouco utilizados.
EJB, WEB Server, JMS (HornetQ) e outros importantes sao pre-inicializados.
[/quote]
voce disse acima que carregava “fullstack” , mas pelo dump do nosso amigo nem o realm service esta habilitado , jaas nao vai funcionar, logo EJB vai ficar capenga em autorização e autenticação… isso é só um exemplo.
E lazy continua sendo lazy , e FULL continua sendo FULL ou é um “Semi-FULL” ?
[quote=chun][quote=clebert.suconic]E… vc nao sabe ler mesmo… (E eu pelo visto nao consigo manter uma promeca de nao escrever novamente)
Eu disse Alguns Servicos ficam em Lazy!!! que sao pouco utilizados.
EJB, WEB Server, JMS (HornetQ) e outros importantes sao pre-inicializados.
[/quote]
voce disse acima que carregava “fullstack” , mas pelo dump do nosso amigo nem o realm service esta habilitado , jaas nao vai funcionar, logo EJB vai ficar capenga em autorização e autenticação… isso é só um exemplo.
E lazy continua sendo lazy , e FULL continua sendo FULL ou é um “Semi-FULL” ?
[/quote]
Não entendi. Pode me explicar porque o JAAS não vai funcionar? Olha aqui:
Service “jboss.security.jaas” (class org.jboss.as.security.service.JaasConfigurationService) mode ACTIVE state UP (parent: jboss.as.server-controller)
[quote=rimolive][quote=chun][quote=clebert.suconic]E… vc nao sabe ler mesmo… (E eu pelo visto nao consigo manter uma promeca de nao escrever novamente)
Eu disse Alguns Servicos ficam em Lazy!!! que sao pouco utilizados.
EJB, WEB Server, JMS (HornetQ) e outros importantes sao pre-inicializados.
[/quote]
voce disse acima que carregava “fullstack” , mas pelo dump do nosso amigo nem o realm service esta habilitado , jaas nao vai funcionar, logo EJB vai ficar capenga em autorização e autenticação… isso é só um exemplo.
E lazy continua sendo lazy , e FULL continua sendo FULL ou é um “Semi-FULL” ?
[/quote]
Não entendi. Pode me explicar porque o JAAS não vai funcionar? [/quote]
Ele vai funciona , mas o recurso vai ser ativado sob demanda (lazy)
Hmmm, acho que não. Olha aqui:
Service “jboss.security.jaas” (class org.jboss.as.security.service.JaasConfigurationService) mode ACTIVE state UP (parent: jboss.as.server-controller)
[quote=clebert.suconic][quote=chun]
[Server:server-one] 11:45:05,465 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final “Lightning” started in 2963ms - Started 87 of 138 services (51 services are passive or on-demand)
[Server:server-two] 11:45:05,472 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
[Server:server-two] 11:45:05,509 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final “Lightning” started in 2925ms - Started 87 of 138 services (51 services are passive or on-demand)
[/quote]
Sera que voce sabe ler?
Algum servicos ficam sim em Lazy, principalmente servicos de OSGI, so os poucos utilizados. Web, EJBs… tudo ja esta inicializado.
Sou um dos desenvolvedores do JBoss, participei de discussoes iniciais, um dos pontos era ter tudo disponivel. (a nao ser que fosse de baixo uso).
Achei que eu encontraria um pouco mais de civilidade entre os Brasileiros, mas voce pelo visto e uma regra a parte!
Nao espere por nenhuma outra mensagem minha nessa thread. </mute on>[/quote]
Liga não cara. Ossos do ofício.
Mas realmente ficou bem melhor. O JBoss 6, não tinha achado muito bom, mas esse 7 está uma maravilha! 
Ficou “feio” o “não vai funcionar”
Vai funcionar SIM , mas vai carregar serviços caso você use o recurso , ou seja carregar sob demanda, os recursos estão disponiveis mas recebem um “Fica esperando aí , quando ai for te usar voce carrega de vez !”
Isso é mais velho que andar para tras… inclusive até o Geronimo,glassfish v3 entre outros fazem uso deste recurso.
Alguém ae viu o novo painel de administração?!
Nos Webminars sobre o AS 7 JBoss o painel admistrativo parecia ter evoluído muito!
Para quem quiser conferir os Webminars:
[quote=rimolive]Hmmm, acho que não. Olha aqui:
Service “jboss.security.jaas” (class org.jboss.as.security.service.JaasConfigurationService) mode ACTIVE state UP (parent: jboss.as.server-controller)
[/quote]
Se voce perceber varios realms estão “durmindo” , o JAAS vai carrega-los no “uso”
[quote=chun]Ficou “feio” o “não vai funcionar”
Vai funcionar SIM , mas vai carregar serviços caso você use o recurso , ou seja carregar sob demanda, os recursos estão disponiveis mas recebem um “Fica esperando aí , quando ai for te usar voce carrega de vez !”
Isso é mais velho que andar para tras… inclusive até o Geronimo,glassfish v3 entre outros fazem uso deste recurso.
[/quote]
Cara, dá uma olhada de novo:
Service “jboss.security.jaas” (class org.jboss.as.security.service.JaasConfigurationService) mode ACTIVE state UP (parent: jboss.as.server-controller)
Ele está ativo. onde você viu que está sob demanda?
[quote=chun][quote=rimolive]Hmmm, acho que não. Olha aqui:
Service “jboss.security.jaas” (class org.jboss.as.security.service.JaasConfigurationService) mode ACTIVE state UP (parent: jboss.as.server-controller)
[/quote]
Se voce perceber varios realms estão “durmindo” , o JAAS vai carrega-los no “uso”
[/quote]
Cara, ainda não entendi. Qual a relação entre Realm e JAAS?
[quote=rimolive]
Cara, ainda não entendi. Qual a relação entre Realm e JAAS?[/quote]
REALM e a conexao com o Datasource. Daonde os usuarios sao lidos, e JAAS e o autenticador.
Esse tipo de coisa se inicializa em milliseconds. Nao e relevante.
Tudo o que e relevante para o uso estara de pe no startup. (A nao ser que vc seja um usuario de OSGI, mas esse tipo de coisa deve ser configuravel. Se nao for seria um bug ja que o JBoss7 foi feito para ser altamente adaptativo (acho que nao encontrei uma palavra em Portugues melhor aqui))
Acho que o Chun ele está se referindo a esse Realm:
http://tomcat.apache.org/tomcat-5.5-doc/realm-howto.html#What_is_a_Realm?
?
No JBoss é um pouco diferente, não?!
Falando nisso, olha que interessante JAAS no JBoss AS 7:
http://community.jboss.org/message/614256
De novo: Mal posso esperar para testar o novo AS -
5 segundos com projeto JSF+CDI+JPA, soh achei diferente a forma de instalaçao de driver jdbc, mas nada de outro mundo. ta funcionando.