-
1. Re: MDB single instance configuration confusion
ricardom Dec 5, 2003 10:19 AM (in response to thoennes)We had the opposite problem here, we needed to enlarge the number
of concurrent beans and found the following solution.
This might help you if you set the value to one.
For myself I would be interested how to change this value for special
messagebean only and not for the whole jboss.
How To enlarge Maximum Number of Messages in standardjboss.xml :
Change 15 to a higher value.
<invoker-proxy-binding>
message-driven-bean
<invoker-mbean>default</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
DefaultJMSProvider
StdJMSPool
15
1
10
queue/DLQ
10
0
</proxy-factory-config>
</invoker-proxy-binding> -
2. Re: MDB single instance configuration confusion
kavitha31 Dec 9, 2004 7:38 PM (in response to thoennes)
We are trying to create multiple instances of the MDB for the requests in the Oracle Request Queue.We are using Jboss4.0 with Oracle AQ.As suggested above ,when we set the STdJMSPool MaximumSize under the <invoker-proxy-binding> attribute to 100 (from 1) we get the following error
oracle.jms.AQjmsException JMS-106 Cannot have more than one open Session on a JMSConnection
Is this an issue with Oracle AQ or should we configure the concurrent beans setting elsewhere?
Please treat this as urgent.Thank you -
3. Re: MDB single instance configuration confusion
genman Dec 10, 2004 11:35 AM (in response to thoennes)If you use a newer version of JBoss, it has a singleton conf. built in. Refer to FAQ and Wiki