[jboss-jira] [JBoss JIRA] (WFLY-901) JBAS014746: pool-max-size may not be null

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated WFLY-901:
----------------------------------

    Fix Version/s: 8.0.0.Alpha1
         Assignee: Brian Stansberry

    
> JBAS014746: pool-max-size may not be null
> -----------------------------------------
>
>                 Key: WFLY-901
>                 URL: https://issues.jboss.org/browse/WFLY-901
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB, Server
>            Reporter: Erhard Siegl
>            Assignee: Brian Stansberry
>             Fix For: 8.0.0.Alpha1
>
>
> I have an EJB deployed in a WAR. When I want to change the pool size from the deployment I get:
> /deployment=perftest-1.0.0.war/subsystem=ejb3/stateless-session-bean=PerfCall:write-attribute(name=pool-max-size,value=30)
> {
>     "outcome" => "failed",
>     "failure-description" => "JBAS014746: pool-max-size may not be null",
>     "rolled-back" => true
> }
> The bug is not severe, since the feature to change the pool-size here seems to be not implemented yet, but the message is confusing (wrong). The pool-size can be changed in the ejb3 subsystem.

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