Messaging Plugin

I'm having a small problem with the messaging plugin. Clients that call
RegisterClient don't seem to get registered on the server.

How do I troubleshoot this? I've set a breakpoing on the public
bpchProcess procedure in TpsnxMessagingPluginCmdHandler, but it never gets
fired. It seems like the message is getting lost in the transport system
somewhere.

I have two plugin command handlers attached to the same simple command
handler - is that the problem? If so, how do I attach both to the same
command handler?

I guess I'm just asking "where do I go from here"?

Eric

> How do I troubleshoot this? I've set a breakpoing on the public
> bpchProcess procedure in TpsnxMessagingPluginCmdHandler, but it never gets
> fired. It seems like the message is getting lost in the transport system
> somewhere.

First, there is an important step missing in the documentation that comes
with the component. On the client side, there is a setting on the transport
for # of call back threads. Set this to 1.

On the server, are all the required properties set, cmd handler, error log,
etcs. Is it active ?

If this does not solve your problem, on the server set a breakpoint in the
plugins add client message handling procedure. Did it get called ?


> I have two plugin command handlers attached to the same simple command
> handler - is that the problem? If so, how do I attach both to the same
> command handler?

If I understand you correctly than that should not be a problem.


Terry

> First, there is an important step missing in the documentation that comes
> with the component. On the client side, there is a setting on the
transport
> for # of call back threads. Set this to 1.

Thorsten told me about that one, so yep, it's set.

> On the server, are all the required properties set, cmd handler, error
log,
> etcs. Is it active ?

They are all active...

> If this does not solve your problem, on the server set a breakpoint in
the
> plugins add client message handling procedure. Did it get called ?

I did that, an no it didn't get called...

> If I understand you correctly than that should not be a problem.

That's what I thought.

Thanks for the info - let me do some more debugging. I've got some other
things to try....

Eric

Ok, a little firther. I had a few "idiot" moments. <g>

I get the client to register with the server, and the server does a
broadcastmessage to the client, but the client isn't receiving it.

Soooooo close. What's next?

Eric

> Soooooo close. What's next?

On the client, check that you have all the component properties set. Have a
look at the demo application for the correct way. Missing something here is
usually what causes my problems :-)

Terry.

> On the client, check that you have all the component properties set.
Have a
> look at the demo application for the correct way. Missing something here
is
> usually what causes my problems :-)

I found it about an hour ago - I had a property set to the wrong #$^%&ing
component. Sigh.

It's a thing of beauty.

Eric