Re: JoavaMonitor question

Hi Ted, On 26 Oct 2016, at 8:51 AM, Theodore Petrosky wrote: > I think you are saying that JavaMonitor should only be accessed by the direct > connect port. > > I never read that anywhere, and I have alway create an instance to > JavaMonitor. Is this a bad practice? I

Re: JoavaMonitor question

I think the general thought is that you don’t want that accessible externally. If you run it in direct connect mode and then make sure that port isn’t accessible via your firewall you should be “safe”. -Lon On Tue, Oct 25, 2016 at 3:21 PM, Theodore Petrosky wrote: > I think

Re: log4j bug causes deadlock?!? (was: which sort of application bugs hang wotaskd?)

Well, the fix seems easy if that works for you. From: on behalf of "o...@ocs.cz" Date: Tuesday, October 25, 2016 at 2:56 PM To: WebObjects-Dev Subject: Re: log4j bug causes deadlock?!?

Re: JoavaMonitor question

Hi Ted, On 26 Oct 2016, at 2:48 AM, Theodore Petrosky wrote: > Why is it that I can only access the application scheduling or Application > Settings sections of JavaMonitor when I access it with the direct connect > (:56789)? these sections are not accessible if I use the

Re: AWS has surrendered!

Hi Flavio, On 26 Oct 2016, at 1:53 AM, Flavio Donadio wrote: > I’m gonna take a look at the script myself. > > From what I understand, it’s a matter of where to find binaries for > JavaMonitor, wotaskd and mod_WebObjects.so. And, finally, set some parameters > in

Re: log4j bug causes deadlock?!? (was: which sort of application bugs hang wotaskd?)

Hmmm, looks like we are not the only one who got bit by that thing in tender parts: http://stackoverflow.com/a/7397857 > On 25. 10. 2016, at 10:59 PM, OC wrote: > > Chuck, > > On 24. 10. 2016, at 18:23, Chuck Hill wrote: > >> Running “sudo jstack –F ”

log4j bug causes deadlock?!? (was: which sort of application bugs hang wotaskd?)

Chuck, On 24. 10. 2016, at 18:23, Chuck Hill wrote: > Running “sudo jstack –F ” should dump a trace of all threads. > Should… Luckily, it did; just it is sort of weird that it identifies threads by name in the deadlock report, but by some unknown ID (perhaps hash of

AW: ProofOfConcept of EOF-JPA-Compatibility-Layer

Hy, In case someone had a look at the project and had a hard time to setup it up properly, I've extended it a little bit: - Now there is a WO-Framework-Projekt for the compatibility layer and a WO-Application-Project with the first unit-tests which (hopefully) demonstrates that the concept

Re: AWS has surrendered!

Paul, I’m gonna take a look at the script myself. From what I understand, it’s a matter of where to find binaries for JavaMonitor, wotaskd and mod_WebObjects.so. And, finally, set some parameters in httpd.conf for mod_WebObjects. Right? Cheers, Flavio > On 25 Oct 2016, at 01:34, Paul

Re: id uuid type

Hi Theodore, Can you be more specific about the problem you experience ? Any errors or description of wrong behaviour can help a lot here. Samuel > Le 23 oct. 2016 à 21:33, Theodore Petrosky a écrit : > > I spent the day chasing my tail. If I use the new uuid type for