Re: MX4J SOAP keeps sending fetchNotifications
"Simone Bordet" <[email protected]>
| Newsgroups | gmane.comp.java.mx4j.user |
|---|---|
| Message-ID | <[email protected]> |
Hi, > I have a prototype of a JMX communication using MX4J SOAP connector between > Java and C components. The MX4J SOAP side (acting as the client side) keeps > sending fetchNotification SOAP messages over the wire at a very fast speed > even when the main thread of the client is sleeping. It must run somehow in > some other thread. Is there any way how to get rid of this behavior? Yes, the notification fetch is done in another thread which is spawned by the client side. There is no way to get rid of this thread, for now. My question is: what do you have on the server side ? A C implementation ? If so, does this C implementation respect the contract of fetchNotification() ? The contract says that fetchNotification must wait on the server side until some notification arrives or the timeout expires. If the server side returns without waiting for the timeout, then you may see the behavior you're describing. Simon -- http://bordet.blogspot.com ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642