eems normal), I'm eager to understand it, test it, and if it
>>> is the culprit, fix it.
>>>
>>> Thanks!
>>> OC
>>>
>>>>> On Feb 13, 2025, at 6:50 AM, OCsite via Webobjects-dev
>>>>> wrote:
>>>&g
Whew! I sort of think this qualifies as a wotaskd bug; where and whom to report
it?
> On 13. 2. 2025, at 15:07, OCsite via Webobjects-dev
> wrote:
> It looks like it was caused by an existence of /tmp/logWebObjects, added
> there to log the adaptor. What the?!? Does not make any sense to m
avaMonitor never launches any application,
>>> otherwise all seems normal), I'm eager to understand it, test it, and if it
>>> is the culprit, fix it.
>>>
>>> Thanks!
>>> OC
>>>
>>>>> On Feb 13, 2025, at 6:50 AM, OCsite vi
ause the described behaviour (JavaMonitor never launches any application,
>> otherwise all seems normal), I'm eager to understand it, test it, and if it
>> is the culprit, fix it.
>>
>> Thanks!
>> OC
>>
>>>> On Feb 13, 2025, at 6:50 AM,
>
> Thanks!
> OC
>
>>> On Feb 13, 2025, at 6:50 AM, OCsite via Webobjects-dev
>>> wrote:
>>>
>>> Hi there,
>>>
>>> today we have bumped into a completely new and weird problem: JavaMonitor
>>> cannot launch any applic
>> Hi there,
>>
>> today we have bumped into a completely new and weird problem: JavaMonitor
>> cannot launch any application, just increases the number of deaths.
>>
>> Nothing at all occurs in the application log. The access rights of both the
>> log
Wotaskd?
> On Feb 13, 2025, at 6:50 AM, OCsite via Webobjects-dev
> wrote:
>
> Hi there,
>
> today we have bumped into a completely new and weird problem: JavaMonitor
> cannot launch any application, just increases the number of deaths.
>
> Nothing at all occurs
Hi there,
today we have bumped into a completely new and weird problem: JavaMonitor
cannot launch any application, just increases the number of deaths.
Nothing at all occurs in the application log. The access rights of both the log
file and its folder are OK; the disk is not full.
When I try
