On Wed, Apr 7, 2010 at 10:56 PM, mattcodes wrote:
>
> The .Net library does not have a pooled connection factory. I will look at
> porting the Java one.
>
> ...Yikes, I think I'll drop that idea, the naming is already making it not
> suitable for hangover day. ConnectionPool represents a connectio
The .Net library does not have a pooled connection factory. I will look at
porting the Java one.
...Yikes, I think I'll drop that idea, the naming is already making it not
suitable for hangover day. ConnectionPool represents a connection and
associated pool, not a connection pool.
1 to 1 for pr
On Wed, Apr 7, 2010 at 10:15 PM, mattcodes wrote:
>
> When you say overhead are you talking about ongoing on startup, I was
> thinking of initializing the pool on startup, so bring up minsize of pools
> say 30 producer(1:1)session(1:1)connection, so when requested its all ready
> to go, use it, an
When you say overhead are you talking about ongoing on startup, I was
thinking of initializing the pool on startup, so bring up minsize of pools
say 30 producer(1:1)session(1:1)connection, so when requested its all ready
to go, use it, and release it back to the pool for the next incoming web
requ
On Wed, Apr 7, 2010 at 5:12 AM, mattcodes wrote:
>
> In a (ASP.Net/c#) web-app I want to pump messages to an ActiveMQ queue
> (nothing complicated - no native transactions etc..). Reading various FAQs
> etc.. I figure I should create a pool of say 50 message producers, each with
> their own sessio
In a (ASP.Net/c#) web-app I want to pump messages to an ActiveMQ queue
(nothing complicated - no native transactions etc..). Reading various FAQs
etc.. I figure I should create a pool of say 50 message producers, each with
their own session and own connection for the best performance. i.e. a 1 to
