I've encountered some very strange behavior in a new TC instance. It's
not actually 'new'. I cloned an Amazon EC2 that had a fully functional
ApacheHTTPD/Tomcat. I replaced the domain on the clone with a new
domain. Otherwise, nothing was changed. I use JSTL extensively on both
the original
On April 4, 2020 7:26:05 PM UTC, calder wrote:
>m
>
>On Sat, Apr 4, 2020, 14:14 Frank Tornack wrote:
>
>> Good evening,
>> I have a question about your e-mail address. Why does the address end
>> on com.INVALID? How do you get such an address?
>>
>
>That question is off topic.
Subject line adjus
m
On Sat, Apr 4, 2020, 14:14 Frank Tornack wrote:
> Good evening,
> I have a question about your e-mail address. Why does the address end
> on com.INVALID? How do you get such an address?
>
That question is off topic.
The invalid is too avoid spam email
Good evening,
I have a question about your e-mail address. Why does the address end
on com.INVALID? How do you get such an address?
Sorry for the interposed question,
Am Samstag, den 04.04.2020, 01:48 + schrieb Mark Boon:
> For the past few months we’ve been trying to trace what looks like
>
I don't have 'proof' Tomcat is to blame. Hence the question-mark. All I have
managed is narrow it down to this NMT data, which is not very informative. I
hoped anyone could give me an idea how or where to investigate further. Or if
someone had run into this before.
The connector of the webapp u
Am 4. April 2020 14:53:17 MESZ schrieb calder :
>On Fri, Apr 3, 2020 at 8:48 PM Mark Boon
>wrote:
>>
>> For the past few months we’ve been trying to trace what looks like
>gradual memory creep. After some long-running experiments it seems due
>to memory leaking when
>> jni_invoke_static(JNIEnv_*,
On Fri, Apr 3, 2020 at 8:48 PM Mark Boon wrote:
>
> For the past few months we’ve been trying to trace what looks like gradual
> memory creep. After some long-running experiments it seems due to memory
> leaking when
> jni_invoke_static(JNIEnv_*, JavaValue*, _jobject*, JNICallType, _jmethodID*,
