• 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: anyone else tried Big Sur? - DirectConnect problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: anyone else tried Big Sur? - DirectConnect problem


  • Subject: Re: anyone else tried Big Sur? - DirectConnect problem
  • From: Tim W via Webobjects-dev <email@hidden>
  • Date: Tue, 25 Aug 2020 23:23:03 -0700

Hi Jesse:

For me it happens on first run - even after a restart. I don’t think its a
stale handle. I’ve gotten it to stop happening by not declaring any WOPort
property at app runtime. I’ll have to experiment further to see if there is
something happening platform-wise on Big Sur that maybe changes things here.

Tim

> On Aug 25, 2020, at 1:20 PM, Jesse Tayler <email@hidden> wrote:
>
> I use something like that, I’d bet it is still a stale handle somehow.
>
> If you can’t see a task, then restart? Works on windows...
>
>> On Aug 25, 2020, at 2:06 PM, Tim W via Webobjects-dev
>> <email@hidden <mailto:email@hidden>>
>> wrote:
>>
>> I know, I probably shouldn’t have done this. But,
>>
>> Everything seems to be going well for dev. Except…..when I try to run any of
>> my apps, I get
>>
>> Aug 25 10:55:26 eTimesheet[N/A] INFO  er.extensions.appserver.ERXApplication
>>  - WODefaultAdaptor
>> Aug 25 10:55:26 eTimesheet[N/A] INFO  er.extensions.appserver.ERXApplication
>>  - {WOHost = "127.0.0.1"; WOWorkerThreadCountMin = 16;
>> WOWorkerThreadCountMax = 256; WOPort = 55555; WOListenQueueSize = 128;
>> WOAdaptor = "WODefaultAdaptor"; WOMaxSocketIdleTime = 180000;
>> WOWorkerThreadCount = 8; }
>> Aug 25 10:55:26 eTimesheet[N/A] WARN  NSLog  - Unable to establish a
>> connection to port 55555 on this host.  Perhaps this port is already in use
>> by another WebObjects application instance.
>>
>> Caused by: com.webobjects.foundation.NSForwardException
>> [java.net.BindException] Address already in use:java.net.BindException:
>> Address already in use
>>
>> This happens regardless of whether I declare a WOPort argument. Since there
>> is a BindException, ERXApplication.stopPreviousDevInstance() is called. lsof
>> indicates there isn’t anything else using the port in question.
>>
>> lsof -nP -iTCP -sTCP:LISTEN | grep 55555
>>
>> …returns no results. Maybe Big Sur is blocking certain localhost connections
>> by default. Looking into it more but if anyone has gotten past this already
>> I’d love to hear suggestions/solutions.
>>
>> Tim
>> UCLA GSE&IS
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      (email@hidden
>> <mailto:email@hidden>)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>

 _______________________________________________
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: 
 >anyone else tried Big Sur? - DirectConnect problem (From: Tim W via Webobjects-dev <email@hidden>)
 >Re: anyone else tried Big Sur? - DirectConnect problem (From: Jesse Tayler via Webobjects-dev <email@hidden>)

  • Prev by Date: Default form value encoding was changed after parsing multi-part form. Form values will be lost.
  • Next by Date: Apache rules and SSL
  • Previous by thread: Re: anyone else tried Big Sur? - DirectConnect problem
  • Next by thread: Default form value encoding was changed after parsing multi-part form. Form values will be lost.
  • Index(es):
    • Date
    • Thread