This content has been marked as final.
Show 3 replies
-
1. Re: Pool size of ManagedConnections in JMS
genman Jan 26, 2006 12:34 AM (in response to jaikiran)
1. 200 is not too many, especially if they are in-JVM.
2. You can create separate pools for the same resources. -
2. Re: Pool size of ManagedConnections in JMS
jaikiran Jan 26, 2006 2:14 AM (in response to jaikiran)Hi genman,
Thanks for the quick answers. Your answer to question 1, solves my issue regarding the pool size. Regarding, the answer to question 2, when you mention :You can create separate pools for the same resources.
does this mean, i create a separate myJms-ds.xml file containing the pool size specific to my application and place this file under my application package? If yes, will JBoss pick up this file automatically whenever JMS related activities are happening in my application, or is there some place where i have to mention the name of this file?
Thank you. -
3. Re: Pool size of ManagedConnections in JMS
jaikiran Jan 26, 2006 3:29 AM (in response to jaikiran)does this mean, i create a separate myJms-ds.xml file containing the pool size specific to my application and place this file under my application package? If yes, will JBoss pick up this file automatically whenever JMS related activities are happening in my application, or is there some place where i have to mention the name of this file?
Sorry genman, that was a silly question from my side. Thought about it a bit and now i get your point:
- Create a connection factory through myAppJms-ds.xml
- Give it a jndi-name. Specify application specific pool size
- While doing JMS operations in the application, lookup this specific ConnectionFactory by its JNDI name and continue with the operations.
This looks fine. Thanks for your answers.