ing a message for a subscriber that
doesnt run
Radu Maierean wrote:
> hi there,
Hi,
could you please send me (to [EMAIL PROTECTED]) the err.log file of
java org.xmlBlaster.Main -dump[socket] true -call[core] true
-call[dispatch] true -logFile err.log
-logDevice file,console
when the problem oc
Radu Maierean wrote:
hi there,
Hi,
could you please send me (to [EMAIL PROTECTED]) the err.log file of
java org.xmlBlaster.Main -dump[socket] true -call[core] true -call[dispatch] true -logFile err.log
-logDevice file,console
when the problem occurs?
It should contain the login sequences of A and
Radu Maierean wrote:
hi there,
i'm pretty sure this is about my lack of understanding about how
XMLblaster messages work, but i cant figure it out at all. here's what
happens.
in my environment, application A (which is a publisher) needs to send
some commands to application B (which is a subscriber
hi there,
i'm pretty sure this is about my lack of understanding about how
XMLblaster messages work, but i cant figure it out at all. here's what
happens.
in my environment, application A (which is a publisher) needs to send
some commands to application B (which is a subscriber); application B
sh
