Andre, thanks for asking the questions. Yes, we try to get understand the
behaviors.
We have seen iphone and other android phones, on different carriers, from
different networks, encounter this problem - losing session. It does not
seem there is a pattern so far. Users use all kinds of phones. Som
On 28.04.2020 18:28, AJ Chen wrote:
Thanks. Martin and Mark.
I can recreate the problem: I compare two different mobile phones. One
phone can log in and proceed. Server log shows the same session persists
(same sessionID upon different requests). The other phone can log in, but
upon next request
On 28.04.20, 17:49, "Mark Thomas" wrote:
> This has been fixed in:
> - master for 10.0.0-M5 onwards
> - 9.0.x for 9.0.35 onwards
> - 8.5.x for 8.5.55 onwards
> - 7.0.x for 7.0.104 onwards
>
> The private isPackage(String) method needed to be updated to correctly
> identify that "org.apache.jsp.te
On 28/04/2020 16:30, Satya Kishore Thumu wrote:
> Hi Chris,
> Post the Ghostcat changes tomcat now listens only on ipv4 by default, what
> if somebody is using on IPv6,
> Tomcat starts to listen on mapped IPv4 address which I think is not
correct.
> I know that we can use ::1 in IPv6.
> Is there a
Thanks. Martin and Mark.
I can recreate the problem: I compare two different mobile phones. One
phone can log in and proceed. Server log shows the same session persists
(same sessionID upon different requests). The other phone can log in, but
upon next request, server log show a new session is alw
On 28/04/2020 10:57, Mark Thomas wrote:
> I've made some progress with the debugging. JDT 4.15 makes an additional
> call to INameEnvironment.findType() and passes
> "org.apache.jsp.test_jsp$1InnerClass". JDT 4.13 does not make that call.
>
> I want to research a little more into why this has chan
Hi Chris,
Post the Ghostcat changes tomcat now listens only on ipv4 by default, what
if somebody is using on IPv6,
Tomcat starts to listen on mapped IPv4 address which I think is not correct.
I know that we can use ::1 in IPv6.
Is there a way tomcat can listen on both loopback addresses when availa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Satya,
On 4/28/20 06:06, Satya Kishore Thumu wrote:
> We are using apache before Tomcat as front end and using modjk for
> connection between apache and Tomcat. After upgrading tomcat(to
> 7.0.100 as we have other dependencies we can't use latest as
On Tue, Apr 28, 2020 at 3:39 PM Satya Kishore Thumu
wrote:
> *@Naga Ramesh*,
> we are using apache 2.4.41 and AJP connector 2.4.48.
>
> worker.ajp13.port=8009
> worker.ajp13.host=localhost
> These are entries that we use on Tomcat server.xml and use the same
> entries for apache.
>
> *@martin* Ti
On Mon, Apr 27, 2020 at 3:31 PM calder wrote:
>
> On Mon, Apr 27, 2020 at 11:22 AM Beard, Shawn M. wrote:
>
> > I have an app running in tomcat 9 that makes an ssl call to an external
> > webservice.
> >
> > It fails with these errors in the logs:
> >
> > ERROR javax.net.ssl.SSLHandshakeException:
*@Naga Ramesh*,
we are using apache 2.4.41 and AJP connector 2.4.48.
worker.ajp13.port=8009
worker.ajp13.host=localhost
These are entries that we use on Tomcat server.xml and use the same entries
for apache.
*@martin* Till we upgraded to tomcat 7.0.100, we were able to use localhost
both for IPv4
We are running the Adopt Open JDK 8 and 11 builds on tomcat 9 with no issues.
Shawn Beard
Sr. Systems Engineer
BTS
+1-515-564-2528
-Original Message-
From: Martin Grigorov
Sent: Tuesday, April 28, 2020 12:56 AM
To: Tomcat Users List
Subject: Re: Apache tomcat 9.0.6 Compatibility with
Hi,
On Tue, Apr 28, 2020 at 1:06 PM Satya Kishore Thumu
wrote:
> Hi,
> We are using apache before Tomcat as front end and using modjk for
> connection between apache and Tomcat. After upgrading tomcat(to 7.0.100 as
> we have other dependencies we can't use latest as of now), i'm unable to
> use
Hi,
We are using apache before Tomcat as front end and using modjk for
connection between apache and Tomcat. After upgrading tomcat(to 7.0.100 as
we have other dependencies we can't use latest as of now), i'm unable to
use ajp.host as "localhost" in IPv6 and works only with ::1. Need help if
there
On 28/04/2020 10:25, Markus Fömpe wrote:
> On 28.04.20, 10:06, "Mark Thomas" wrote:
>
> [...]
>>
>>> This is root cause:
>>>
>>> java.lang.ClassCastException: class
>>> org.eclipse.jdt.internal.compiler.lookup.PlainPackageBinding cannot be cast
>>> to class org.eclipse.jdt.internal.compiler.loo
On 28.04.20, 10:06, "Mark Thomas" wrote:
[...]
>
>> This is root cause:
>>
>> java.lang.ClassCastException: class
>> org.eclipse.jdt.internal.compiler.lookup.PlainPackageBinding cannot be cast
>> to class org.eclipse.jdt.internal.compiler.lookup.TypeBinding
>> (org.eclipse.jdt.internal.compile
On 28/04/2020 07:02, Markus Fömpe wrote:
> Hi,
>
> With Tomcat 9.0.34 the JDT compiler was updated to 4.15.
> Since then, there is an error when Tomcat compiles the JSP at runtime when
> this construct is used in a JSP:
Not good news but thanks for bring this up.
We skipped 4.14 because there w
On 28/04/2020 06:42, Mahathi Vavilala wrote:
> Hi,
>
> For default values of frequency (=500) and dropTime (=3000) in cluster
> installation with TOMEE 7.0.7 (uses Tomcat 8.5.50.0) using JDK 12 or above
> only, many memberDisappeared messages are logged on all nodes of the
> cluster (almost for ev
On 28/04/2020 07:47, Martin Grigorov wrote:
> On Tue, Apr 28, 2020 at 9:11 AM AJ Chen wrote:
>
>> Anyway to fix it? thanks. -aj
>>
>
> First you need to investigate whether there is a proxy.
> Then what kind of proxy.
> Then where is its configuration.
> Then consult with its manual and see whet
19 matches
Mail list logo
