Maven, two apps with direct connect SSL, one works

Hi all, Weird problem. I have two apps. App1 works with SSL direct connect, in eclipse with maven and without. App2 works with SSL direct connect without maven. With maven, the SSL direct connect properties I have in Properties.dev are not located. The reason that happens is in ERXApplicatio

Re: WOAdaptor build and test

Testing? Seriously? :-P If it does not crash, it is tested. Look in the archives for these threads: WebObjects and Apache 2.4 on El Capitan Apache Adaptor on debian:jessie That should get you started. Chuck On 2016-04-06, 11:45 AM, "webobjects-dev-bounces+chill=gevityinc@lists.apple

WOAdaptor build and test

Hi List Is there a procedure for building and testing WOAdaptor? Paul ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https:

Re: Extending the “No Instance Available” timeout

So the negative instance/port number is, IIRC, a signal to wotask to shortcut the configuration and go directly to the instance. So that might be why setting the Receive Timeout in JavaMonitor is not working. I don’t recall if that C code looks for the site config in this case or not. That m

Re: Extending the “No Instance Available” timeout

1) Direct Connect isn’t really an option for us (nor should it be for anyone 😉). 2) The URLs look like: http://localhost/Apps/WebObjects/SmartPractice.woa/-20001 3) We always set a port for development. 4) I did have him set the application up in Monitor with timeouts and he claims it didn’t work.

Re: Extending the “No Instance Available” timeout

Ben, what do the URLs look like? It has been ages since I set this up. I think you might need to set the WOPort in Eclipse and then configure an application in JavaMonitor and create an instance on that port for the Receive Timeout to have any effect. Or, if you are not using Apache to serve

Re: Extending the “No Instance Available” timeout

Aha, I see — I thought Eclipse uses Direct Connect, just as Xcode used to (and mine still does). In that case, beside the adaptor log, I would probably (a) try Direct Connect; no timeouts in this mode; (b) add extra logs to show when the R/R loop begins, how it runs, and when it ends, to see wh

Re: Extending the “No Instance Available” timeout

Just to help Ben while he’s sleeping… This is while he’s running the application from within Eclipse (still through Apache) while he’s testing/debugging. -Lon On Wed, Apr 6, 2016 at 8:37 AM, OC wrote: > Benjamin, > > On 6. 4. 2016, at 10:19, Benjamin Chew wrote: > > > I did change Receive Time

Re: Extending the “No Instance Available” timeout

Benjamin, On 6. 4. 2016, at 10:19, Benjamin Chew wrote: > I did change Receive Timeout to 999,999 under “Site”, and restarted wotaskd > and monitor, but that didn’t help. The only thing which should need to be restarted is your application. > I also tried creating an app in monitor with the s

Re: Deadlock / stack interpretation

Hi Mark, You do not take the globalId of Document, because it is not an EO and does not have any EO attributes right ? Is Report and ExternalDocumentStore are committed to the database when this code is running ? If you answered yes to both questions, I think your problem is in another piece

Re: Deadlock / stack interpretation

I'll try that for all threads and see what happens. I have changed to using the utility methods in ERXEOGlobalIDUtilities in any case. Thank you Mark -- Dr. Mark Wardle Consultant Neurologist, Cardiff, UK (Sent from my mobile) > On 5 Apr 2016, at 23:32, Chuck Hill wrote: > > That code doe

Re: Extending the “No Instance Available” timeout

I did change Receive Timeout to 999,999 under “Site”, and restarted wotaskd and monitor, but that didn’t help. I also tried creating an app in monitor with the same name as the one running in Eclipse, and changing the Receive Timeout, but that didn’t work either. Am I missing something? Thanks,