[jboss-jira] [JBoss JIRA] (WFLY-1885) ServiceActivator blocks server startup if more than 8 services - platformspecific

Thomas Frühbeck (JIRA) jira-events at lists.jboss.org
Tue Sep 17 18:27:03 EDT 2013


     [ https://issues.jboss.org/browse/WFLY-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Frühbeck reopened WFLY-1885:
-----------------------------------



still the same behavior if >= 8 HASingletons to be started, server completely blocked:

 "EJB default - 10" prio=10 tid=0x00007fecd80de800 nid=0x3962 waiting for monitor entry [0x00007fec650ce000]
   java.lang.Thread.State: BLOCKED (on object monitor)
        at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:125)
        - waiting to lock <0x00000000e695ea80> (a java.lang.Object)
        at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:47)
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
        at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
        at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
        at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
        at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55)
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
        at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
        at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
        at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:325)

                
> ServiceActivator blocks server startup if more than 8 services - platformspecific
> ---------------------------------------------------------------------------------
>
>                 Key: WFLY-1885
>                 URL: https://issues.jboss.org/browse/WFLY-1885
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Clustering, Server
>    Affects Versions: 8.0.0.Alpha3
>            Reporter: Thomas Frühbeck
>            Assignee: Paul Ferraro
>            Priority: Minor
>             Fix For: 8.0.0.Beta1
>
>         Attachments: stack.log.gz
>
>
> We try to start more than 8 services by ServiceActivator.
> We follow hasingleton quickstart.
> Server startup is blocked on Linux but not on windows (?!?).
> If we introduce a delay of e.g. 1 second, all services start correctly also on Linux:
> public void activate(ServiceActivatorContext context) {
>   ESMSSingletonServiceBase<T> service = getSingletonService();
>   log.info("ESMSService will be installed: " + service.getSingletonServiceName());
>   SingletonService<String> singleton = new SingletonService<String>(service.getSingletonServiceName(), service);
>   singleton.build(new DelegatingServiceContainer(context.getServiceTarget(), context.getServiceRegistry()))
>     .addDependency(ServerEnvironmentService.SERVICE_NAME, ServerEnvironment.class, service.env)
>     .setInitialMode(ServiceController.Mode.ACTIVE).install();
>   // TODO: diesen Workaround evtl mal beheben. 
>   // (Server startet im Moment nicht anders... zumindest nicht auf Linux! Timingproblem?)
>   try {
> 	Thread.sleep(1000);
>   } catch (InterruptedException e) {}
> Thread dump of Linux blocked server attached

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the jboss-jira mailing list