[jboss-user] [EJB 3.0 Users] - Re: Custom StrictMaxPool settings in ...-aop.xml ignored

Okay. I have a solution for this. It turns out that when EJBs applications are deployed, the properties in ejb3-interceptors-aop.xml file under the deploy directory are applied first. The following annotation in the file says if the class is not present then apply this property. |

[jboss-user] [EJB 3.0 Users] - Re: Custom StrictMaxPool settings in ...-aop.xml ignored

I am trying to use StrictMaxPool in JBoss 5.1.0.GA and the properties in the -aop.xml file seem to be ignored. This is for a stateless session bean. The EJB3 container seems to honor only the properties in ejb3-interceptors-aop.xml. Any -aop.xml bundled with the EJB application seem to be

[jboss-user] [EJB/JBoss] - Re: MDB calling a session bean, session bean not getting reu

I have a nice little reproducible test case to see this behavior but I don't know how to attach it to this posting. Thanks, Shreyas View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4210891#4210891 Reply to the post :

[jboss-user] [EJB 3.0] - MDB calling a session bean but session bean not getting reus

Hello, Sorry about the cross post. I have already posted this message in the EJB/JBoss forums but didn't get any solutions. Here is the original post http://www.jboss.org/index.html?module=bbop=viewtopicp=4210891#4210891 The issue is that when an MDB invokes some SLSB, the SLSB seems to be

[jboss-user] [EJB/JBoss] - MDB calling a session bean, session bean not getting reused

Hello, I have an MDB that does a lookup on a stateless session bean, calls some method on the session bean and returns. The MDB and the SLSB are running in the same EJB container. However, everytime an MDB looks up the SLSB, a new instance of the bean is created instead of using the available

[jboss-user] [Clustering/JBoss] - Re: AutoDiscovery for multiple clusters on same machine

Thanks Brian. I understand your comment and I agree with it. How does a client look up two different EJB applications deployed on two different clusters? Can jndi.properties work in this case? In this case, I do understand that the proxy downloaded will be from one of the clusters. Do I load

[jboss-user] [Clustering/JBoss] - AutoDiscovery for multiple clusters on same machine

Hello, I have a machine that is running two instances of JBoss 4.2.2. Each of the instances participates in a different cluster. Both clusters are running the same EJB application. How do I configure the jndi.properties on my client such that it can auto discover both the clusters? Because

[jboss-user] [EJB/JBoss] - Re: Stateless Session Bean pool MaximumSize with strictMaxim

For EJB 3.0 you can edit the ejb3-interceptors-aop.xml file under /jboss_home/server/all/deploy directory. Edit the element for Stateless Bean with something like this @org.jboss.annotation.ejb.PoolClass (value=org.jboss.ejb3.StrictMaxPool.class, maxSize=1, timeout=1) I

[jboss-user] [EJB 3.0] - Re: Changing EJB 3.0 container pool size

Okay got it! You need to edit the ejb3-interceptors-aop.xml file. Specifically, edit the Stateless Bean element to point to @org.jboss.annotation.ejb.PoolClass (value=org.jboss.ejb3.StrictMaxlPool.class, maxSize=10, timeout=1) Thanks, Shreyas View the original post :

[jboss-user] [EJB 3.0] - Removal of Stateless Session Beans

When does the EJB container decide to evict (destroys them) the Stateless sessions beans from the pool? Is this decision based on how long the beans have been sitting in the pool or the memory consumption? If yes, can you configure any of these parameters? Thanks, Shreyas JBoss AS 4.2.2.

[jboss-user] [EJB 3.0] - Changing EJB 3.0 container pool size

Hello, How do you change the EJB 3.0 container pool size? There are elements in standard-jboss.xml like MaximumSize, strictMaximumSize, MinimumSize etc but they are not applicable for EJB 3.0? I would like to restrict the container pool size for Stateless Session Beans to a maximum value

[jboss-user] [EJB/JBoss] - Re: JBoss 4.2.2 not reading standardjboss.xml

I checked the discussion but it is not helping me with setting the EJB 3.0 container pool size constraints. Is there a doc or something on this topic?' Thanks, Shreyas View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4176343#4176343 Reply to the post :

[jboss-user] [EJB/JBoss] - Re: JBoss 4.2.2 not reading standardjboss.xml

EJB 3.0 Thanks, Shreyas View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4174484#4174484 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4174484 ___ jboss-user mailing list

[jboss-user] [EJB/JBoss] - Re: JBoss 4.2.2 not reading standardjboss.xml

Thanks jaikiran. Is it possible for you to tell me how the container pool size can be restricted without using per application configuration in jboss.xml? Thanks, Shreyas View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4174619#4174619 Reply to the post :

[jboss-user] [EJB/JBoss] - JBoss 4.2.2 not reading standardjboss.xml

I have a JBoss 4.2.2 install on Redhat Linux (RHEL4). I am seeing that the configuration properties (specifically the container-configuration like MaximumSize, strictMaximumSize) are not getting enforced. So basically, I am not able to configure my Stateless Session Bean Container to create