• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Web service disturbs wotaskd communication
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Web service disturbs wotaskd communication


  • Subject: Re: Web service disturbs wotaskd communication
  • From: Maik Musall <email@hidden>
  • Date: Mon, 07 May 2018 14:57:29 +0200

Hi Chuck,

thanks for the suggestions. Thread dump was insightful, revealing that the new
startup code caused didFinishLaunching() to be blocked and never finish.

Maik


> Am 04.05.2018 um 20:33 schrieb Chuck Hill <email@hidden>:
>
> Hi Maik,
>
> Are the WOWorkerThreads still running?  Try getting a thread dump.  Is your
> refactored web service running as a daemon thread?  If that, that could be by
> the app is not stopping.  You will need to tie in application.terminate() to
> stop the web service.
>
> That is the only thing that I can think of that sort-of fits your
> description.
>
>
> Chuck
>
> From: Webobjects-dev
> <webobjects-dev-bounces+chill=email@hidden
> <mailto:webobjects-dev-bounces+chill=email@hidden>> on
> behalf of Maik Musall <email@hidden <mailto:email@hidden>>
> Date: Friday, May 4, 2018 at 5:48 AM
> To: WebObjects-Dev <email@hidden
> <mailto:email@hidden>>
> Subject: Web service disturbs wotaskd communication
>
> 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

References: 
 >Web service disturbs wotaskd communication (From: Maik Musall <email@hidden>)
 >Re: Web service disturbs wotaskd communication (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Looking towards JDK 9, 10
  • Next by Date: Re: Looking towards JDK 9, 10
  • Previous by thread: Re: Web service disturbs wotaskd communication
  • Next by thread: Re: Looking towards JDK 9, 10
  • Index(es):
    • Date
    • Thread