-
15. Re: JMS Topics/Queues in ProfileService
Its going to depend on the underlying runtime component providing the stats. The ds don't have them because the pools are not created until needed. I would expect the destinations to have stats from the start since they don't currently have a separate component providing the stats.
-
16. Re: JMS Topics/Queues in ProfileService
"scott.stark@jboss.org" wrote:
Its going to depend on the underlying runtime component providing the stats. The ds don't have them because the pools are not created until needed.
If it's just an issue of lazy pool construction then add something like the following
to your test -ds.xml<min-pool-size>2</min-pool-size> <prefill/>
-
-
18. Re: JMS Topics/Queues in ProfileService
"adrian@jboss.org" wrote:
"scott.stark@jboss.org" wrote:
Its going to depend on the underlying runtime component providing the stats. The ds don't have them because the pools are not created until needed.
If it's just an issue of lazy pool construction then add something like the following
to your test -ds.xml<min-pool-size>2</min-pool-size> <prefill/>
I was using the DefaultDS which already has
<min-pool-size>5</min-pool-size> -
19. Re: JMS Topics/Queues in ProfileService
Ah, I didn't see prefill. But would DefaultDS not have its pool created at startup because it is used for messaging or something else?
-
20. Re: JMS Topics/Queues in ProfileService
yes, that is true. I'll look into why the stats are showing up. Probably a bug and the test should be validating that there are non-null values.
-
21. Re: JMS Topics/Queues in ProfileService
Prefill doesn't work if you specify a security-domain like the DefaultDS does.
Weston only implemented it for the basic pool.
Yes, the jboss-messaging use of the datasource should create the pool,
so I'd guess it is broken? -
22. Re: JMS Topics/Queues in ProfileService
The population of the stats is broken. I have updated the testDefaultDSStats to validate that the stats values are non-null.
http://jira.jboss.com/jira/browse/JBAS-5247