David Kerry wrote:
On Wed, Jun 09, 2004 at 10:47:46PM +0200, Michele Laghi wrote:
Hi David,
David Kerry wrote:
I hit enter to publish a message and it gets published, the
topic gets created on the server and is subsequently marked 'DEAD'.
Two messages show up in the subscriber window - the publi
On Wed, Jun 09, 2004 at 10:47:46PM +0200, Michele Laghi wrote:
> Hi David,
>
> David Kerry wrote:
> >I hit enter to publish a message and it gets published, the
> >topic gets created on the server and is subsequently marked 'DEAD'.
> >
> >Two messages show up in the subscriber window - the publi
Hi David,
David Kerry wrote:
On Tue, Jun 08, 2004 at 06:08:19PM +0200, Marcel Ruff wrote:
Try this:
java org.xmlBlaster.Main -call[core] true
java javaclients.HelloWorldPublish -lifeTime 0 -destroyDelay 0
you can see in the server log how the topic disappears
(type 'd' in the server console to v
On Tue, Jun 08, 2004 at 06:08:19PM +0200, Marcel Ruff wrote:
> Try this:
>
> java org.xmlBlaster.Main -call[core] true
>
> java javaclients.HelloWorldPublish -lifeTime 0 -destroyDelay 0
>
> you can see in the server log how the topic disappears
> (type 'd' in the server console to verify it
Hi David,
David Kerry wrote:
Hi Michele,
Right now, we're using PubSub, all clients are connected before a publish
(losing the odd message is ok in our environment) and we are setting the
isVolatile() on all messages as well.
Shouldn't setting the volatile flag (as we're already doing) cause the
to
On Tue, Jun 08, 2004 at 06:08:19PM +0200, Marcel Ruff wrote:
> David Kerry wrote:
> >So I guess the question is - how can I force xmlblaster to check
> >for dead topics more often and clean them out?
>
> Hi David,
>
> you've summarized it quite exactly already.
> The best solution is to use name
Hi Michele,
Right now, we're using PubSub, all clients are connected before a publish
(losing the odd message is ok in our environment) and we are setting the
isVolatile() on all messages as well.
Shouldn't setting the volatile flag (as we're already doing) cause the
topics to get destroyed right
David Kerry wrote:
Hello,
We used to run xmlblaster v0.8 for quite some time, but have now
moved to v0.9.
Everything is running fine, but we have a problem where xmlblaster
keeps running out of memory.
We're using ram based storage for now (which we also used in the
v0.8 version). This shouldn't b
hallo David,
As I see it you have several possibilities to solve your problem:
first of all you should consider structuring your system in such a way
to get a limited amount of topics. Topic creation is timeconsuming and
should be kept to a minimum.
An alternative to the described approach would
Hello,
We used to run xmlblaster v0.8 for quite some time, but have now
moved to v0.9.
Everything is running fine, but we have a problem where xmlblaster
keeps running out of memory.
We're using ram based storage for now (which we also used in the
v0.8 version). This shouldn't be a problem as o
10 matches
Mail list logo