]
Thomas Diesler updated AS7-6892:
--------------------------------
Assignee: (was: Thomas Diesler)
Component/s: EJB
Server
(was: ConfigAdmin)
JBAS014746: pool-max-size may not be null
-----------------------------------------
Key: AS7-6892
URL:
https://issues.jboss.org/browse/AS7-6892
Project: Application Server 7
Issue Type: Bug
Components: EJB, Server
Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
Reporter: Erhard Siegl
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: