]
jaikiran pai reassigned EJBTHREE-2005:
--------------------------------------
Assignee: jaikiran pai
The EJB pool is not updated through xml configuration
-----------------------------------------------------
Key: EJBTHREE-2005
URL:
https://jira.jboss.org/jira/browse/EJBTHREE-2005
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EAP 5
Environment: Development
Reporter: Farhan Hussain
Assignee: jaikiran pai
In the documentation:
http://www.jboss.org/file-access/default/members/jbossejb3/freezone/docs/...
The xml configuration for mdb's does not work (mydomain-aop.xml):
<?xml version="1.0" encoding="UTF-8"?>
<aop xmlns="urn:jboss:aop-beans:1.0">
<domain name="Strictly Pooled Stateless Bean" extends="Stateless
Bean" inheritBindings="true">
<annotation expr="!class((a)org.jboss.ejb3.annotation.Pool)">
@org.jboss.ejb3.annotation.Pool (value="StrictMaxPool", maxSize=5,
timeout=10000)
</annotation>
</domain>
<domain name="Strictly Pooled Message Driven Bean" extends="Message
Driven Bean" inheritBindings="true">
<annotation expr="!class((a)org.jboss.ejb3.annotation.Pool)">
@org.jboss.ejb3.annotation.Pool (value="StrictMaxPool", maxSize=5,
timeout=10000)
</annotation>
</domain>
</aop>
The work around is to set inheritBindings=false and removing extends="Message Driven
Bean". This will apply the correct maxSize value.
Now shouldn't the default behaviour result in the XML overriding the defaults
regardless of inheritBindings? Either the documentation should be updated, or if this
indeed is a bug, it should be resolved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: