[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster] JdbcQueuePlugin won't load



Hey Michele,

> Are you always publishing with the same oid ? In that case it should 
> always put the messages in the same table since there is one topic store 
> and one history queue per oid. On the other hand, if your oid is always 
> a new one, then a new queue is created each time. There is also one 
> callback queue per subscriber.
> 
I don't specify an OID, so I guess a new one is generated every time I
publish a message. Thanks for clarifying this issue - I'll try to
specify a unique OID for all the messages that publish the same kind
of messages, and see whether this helps.

> I just finished testing the alternative design 
> (JdbcQueueCommonTablePlugin) on Oracle (postgres was already tested). It 
>  is a simpler design and worth looking at if large amount of tables is 
> a problem.
> 
I'll take a peak later on - right now I'm just trying to get the
overall design right, and it seems as if your implementation is a
performance optimization.

> The requirements are updated and the xmlBlaster.properties.template is 
> updated too and configured per default with this newer approach.
> 
Cool.

> 
> Cheers
> Michele
> 
> 
> >Michael
> >
> >
> >
> >On Wed, Feb 26, 2003 at 10:24:58AM +0100, Marcel Ruff wrote:
> >
> >>>>I noticed a warning about useTopic=false (although I don't set it that
> >>>>way in the property file). After looking at the template property
> >>>>files supplied with xmlblaster, I added the following entries
> >>>>
> >>>>persistence/defaultPlugin=JDBC,1.0
> >>>>queue/defaultPlugin=JDBC,1.0
> >>>>useTopicStore=true
> >>
> >>Probably you should prefer CACHE over JDBC:
> >>
> >> persistence/defaultPlugin=CACHE,1.0
> >> queue/defaultPlugin=CACHE,1.0
> >> useTopicStore=true
> >>
> >>The CACHE implementation uses JDBC internally.
> >>Using JDBC directly you loose all performance
> >>benefits of the cache and it is not safer.
> >>
> >>These lines will disappear as soon as we
> >>deliver a native persistence with xmlBlaster again.
> >>
> >>regards
> >>
> >>Marcel
> >>
> >>
> >
> >
> 
> 

-- 
matighet at bbn.com   BBN Technologies