[ mx4j-Bugs-993640 ] Busy Loop on SOAPConnectorServer fetching Notifications

Bugs item #993640, was opened at 2004-07-19 10:19
Message generated for change (Comment added) made by biorn_steedom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450647&aid=993640&group_id=47745

Category: MX4J Tools
Group: Release 2.0.1
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Simone Bordet (biorn_steedom)
Assigned to: Simone Bordet (biorn_steedom)
Summary: Busy Loop on SOAPConnectorServer fetching Notifications

Initial Comment:
The SOAPConnectorServer can busy loop when the
following happens:
1. Start SOAPConnectorServer
2. Connect a SOAPConnector; this will start the fetch
notification threads
3. Close SOAPConnectorServer
4. Now the fetch notification mechanism busy loops.

The problem is in
DefaultRemoteNotificationServerHandler, where if the
handler has been closed, we return immediately from
fetchNotification():

if (closed || send) break; // circa line 315

Since we return with no problems and without waiting
for the timeout, the client calls again, causing the
busy loop.


----------------------------------------------------------------------

>Comment By: Simone Bordet (biorn_steedom)
Date: 2004-07-19 10:22

Message:
Logged In: YES 
user_id=128193

When the handler is closed, and a new fetchNotification()
call arrives, we throw immediately IOException.
The client will use the heartbeat mechanism and give up
after a while (with no busy loop), normally 3 * 5 sec
(default heartbeat configuration).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450647&aid=993640&group_id=47745


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click