[jboss-jira] [JBoss JIRA] (WFLY-1402) Too Many Dependencies

jaikiran pai (JIRA) jira-events at lists.jboss.org
Tue Jun 4 03:46:55 EDT 2013


    [ https://issues.jboss.org/browse/WFLY-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779069#comment-12779069 ] 

jaikiran pai commented on WFLY-1402:
------------------------------------

You can even just download the latest nightly binary from here https://community.jboss.org/thread/224262 and give it a try. That way, you can be sure that Alpha2 will have this fixed for your application.

                
> Too Many Dependencies
> ---------------------
>
>                 Key: WFLY-1402
>                 URL: https://issues.jboss.org/browse/WFLY-1402
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 8.0.0.Alpha1
>         Environment: W7 64 bit
>            Reporter: Michael McGovern
>            Assignee: Stuart Douglas
>             Fix For: 8.0.0.Alpha2
>
>
> Large app ~ 1000 SLSB gets
> Caused by: java.lang.IllegalArgumentException: Too many dependencies specified (max is 16383)
>           at org.jboss.msc.service.ServiceBuilderImpl.doAddDependency(ServiceBuilderImpl.java:216) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
>           at org.jboss.msc.service.ServiceBuilderImpl.addDependenciesNoCheck(ServiceBuilderImpl.java:158) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
>           at org.jboss.msc.service.ServiceBuilderImpl.addDependencies(ServiceBuilderImpl.java:152) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
>           at org.jboss.msc.service.ServiceBuilderImpl.addDependencies(ServiceBuilderImpl.java:142) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
>           at org.jboss.as.naming.deployment.JndiNamingDependencyProcessor.deploy(JndiNamingDependencyProcessor.java:59)
>           at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Alpha1.jar:8.0.0.Alpha1]

--
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