Hi OC,
when you say 2 MB, is it possible you mean 2 GB? There used to be (and maybe
still is? it's been a while) a problem with both the Apache adaptor and WO's
own WOAdaptor using an int to keep track of content-length, meaning file
uploads/downloads tended to fail when it was larger than Inte
Hugi,
well I can't say I _entirely_ understand the behaviour (probably would have to
analyse and understand the adaptor code first), but my testing sort of suggests
that
(i) the culprit is too long a computation in the takeValuesFromRequest phase
I've tried to prolong it artificially first, bu
Thanks!
> On 13. 2. 2025, at 12:49, Hugi Thordarson via Webobjects-dev
> wrote:
> Sorry, then I'm kind of out of ideas.
Makes two of us :)
> My first thought was that the adaptor logging was accurate and that the
> application's adaptor configuration was set up so that the file upload
> requ
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 in the application log. The a
Hugi,
> On 13. 2. 2025, at 9:55, Hugi Thordarson via Webobjects-dev
> wrote:
> when you say 2 MB, is it possible you mean 2 GB?
Nope. The file which fails to upload has 2 024 943 bytes.
> ...
> Is this also a problem in direct connect mode or only if you're going through
> the web server adap
> On 13. 2. 2025, at 14:00, Jesse Tayler wrote:
> Wotaskd?
What with it?
It runs (see “runs normally, connects properly to wotaskd, shows as running”
below). We have even restarted it (along with JavaMonitor), did not help.
But if there is some kind of specific wotaskd-related problem which wo
Do you know what user your monitor is running under?
I have no idea, but sometimes wotaskd craps out and I need to restart it…
I also try to use the exact same launch as wo monitor by taking the args out
and using that but it sounds like you’ve checked launch with args.
Software voodoo?
> On F
Voodoo would be the right answer I guess.
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 me (does anybody
here understand perhaps?), but it looks like soon as I've removed the file, I
can launch anyth
I believe in software voodoo. It’s part of software rot.
> On Feb 13, 2025, at 9:07 AM, OCsite wrote:
>
> Voodoo would be the right answer I guess.
>
> 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 t
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
Sorry, then I'm kind of out of ideas.
My first thought was that the adaptor logging was accurate and that the
application's adaptor configuration was set up so that the file upload request
actually times out. But creating a simple file upload page and setting all the
adaptor timeouts to a short
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 t
Well I couldn't easily try the streamed upload, for it requires a single-action
form; nevertheless I have tried streamToFilePath — with precisely the same
outcome as normal upload :(
> On 13. 2. 2025, at 13:20, OCsite via Webobjects-dev
> wrote:
>
> Thanks!
>
>> On 13. 2. 2025, at 12:49, Hug
13 matches
Mail list logo
