This content has been marked as final.
Show 3 replies
-
1. Re: Identifying a stuck subscriber
adrian.brock Feb 29, 2004 6:09 PM (in response to richieb)Enable trace logging on the client, see what error you get.
Regards,
Adrian -
2. Re: Identifying a stuck subscriber
richieb Mar 1, 2004 6:57 AM (in response to richieb)"adrian@jboss.org" wrote:
Enable trace logging on the client, see what error you get.
Regards,
Adrian
Unfortunately, this only seems to occur on production machines and I cannot enable trace there. :(
What we did though, was to implement a simple timer inside the client. Then if we find that the client executes for too long, we kill the client. We also log data, so hopefully this will catch the problem and give us enough info to really solve it.
...richie -
3. Re: Identifying a stuck subscriber
josefine Aug 6, 2004 2:36 PM (in response to richieb)Hi Richie,
does you find a useful solution for your problem, besides the described one?
It seems that we have the same problem and we are very intresting in getting further information, which would give us some suggestions for fixing the problem.
we also thought about solving the problem at client-side. but this doesn't work steady at the moment.
best regards.
josefine