users@glassfish.java.net

Re: MDB: max-pool-size vs. steady-pool-size; new instance on every message

From: <glassfish_at_javadesktop.org>
Date: Tue, 26 Aug 2008 08:06:23 PDT

Hi,

no, I didn't setup any other thing than just the sun-ejb-jar.xml.
I am using Glassfish V2ur2 and an EJB3, so my descriptor starts with:
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 EJB 3.0//EN" "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_3_0-0.dtd">

Here is the full DD:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 EJB 3.0//EN" "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_3_0-0.dtd">
<sun-ejb-jar>
    <enterprise-beans>
        <ejb>
                <ejb-name>MessageProcessor</ejb-name>
            <jndi-name>queue/MessageProcessor</jndi-name>
            <bean-pool>
                                <steady-pool-size>1</steady-pool-size>
                                <resize-quantity>1</resize-quantity>
                                <max-pool-size>1</max-pool-size>
                                <pool-idle-timeout-in-seconds>0</pool-idle-timeout-in-seconds>
                        </bean-pool>
        </ejb>
    </enterprise-beans>
</sun-ejb-jar>

I am using a timeout of "0" now since this should disable any timeout.

Cheers
Chris
[Message sent by forum member 'chrjohn' (chrjohn)]

http://forums.java.net/jive/thread.jspa?messageID=295410