Web service disturbs wotaskd communication
Web service disturbs wotaskd communication
- Subject: Web service disturbs wotaskd communication
- From: Maik Musall <email@hidden>
- Date: Fri, 04 May 2018 14:48:12 +0200
Hi all,
we recently refactored a web service running within a WO application. It was
based on com.sun.net <http://com.sun.net/>.httpserver which is of course
deprecated, and now we use org.apache.http instead. It creates a socket on a
high port number, waits for requests and serves responses. Nothing special that
I can see.
Now, whenever we fire up the new implementation, the entire WO app instance
can't be stopped any more through wotaskd (e.g. by stopping the instance
manually in WOMonitor). Force Quit still works, and shutting down from within
through Runtime.exit() works, too. And if I disable that webservice, normal
stops also work fine again.
The application port (2003 here) is reachable, I can connect to it via curl or
telnet, I even get an exception in the log when I send some garbage there. It
just doesn't react to wotaskd commands any more, and I can't figure out why.
Does anyone have a hunch about where to look?
Thanks
Maik
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden