Hi all,
Any insights please .
Thanks,
Madhan
On Thu, 4 Jun, 2020, 11:12 pm Madhan Raj, wrote:
> Hi Christopher,
>
> Yes you correct I can only complete a handshake with RSA cert, not ECDSA
> cert. when i try to connect with ECDSA ciphers using s_client negotiation
> fails.
> Madhan
>
> On Thu,
Thank you for the quick response.
Dream * Excel * Explore * Inspire
Jon McAlexander
Asst Vice President
Middleware Product Engineering
Enterprise CIO | Platform Services | Middleware | Infrastructure Solutions
8080 Cobblestone Rd | Urbandale, IA 50322
MAC: F4469-010
Tel 515-988-2508 | Cell 515-
On 10/06/2020 20:14, jonmcalexan...@wellsfargo.com.INVALID wrote:
> I have an application team that is running into this error after upgrading to
> Tomcat 8.5.55. They did not see this issue with 8.5.54 or earlier.
>
> Resolved [java.lang.IllegalStateException: Current request is not of type
> [
Hi,
Am 10.06.2020 um 15:34 schrieb Mark Thomas:
> On 10/06/2020 14:07, Paul Carter-Brown wrote:
>> At runtime, any code can call TimeZone.setDefault to change the timezone of
>> the JVM.
>>
>> I'd suggest logging TimeZone.getDefault().getDisplayName(Locale.ENGLISH);
>> intermittently and seeing i
I have an application team that is running into this error after upgrading to
Tomcat 8.5.55. They did not see this issue with 8.5.54 or earlier.
Resolved [java.lang.IllegalStateException: Current request is not of type
[org.apache.catalina.servlet4preview.http.HttpServletRequest]:
org.apache.ca
Thank you!
Dream * Excel * Explore * Inspire
Jon McAlexander
Asst Vice President
Middleware Product Engineering
Enterprise CIO | Platform Services | Middleware | Infrastructure Solutions
8080 Cobblestone Rd | Urbandale, IA 50322
MAC: F4469-010
Tel 515-988-2508 | Cell 515-988-2508
jonmcalexan..
On 09/06/2020 17:22, jonmcalexan...@wellsfargo.com.INVALID wrote:
> Mark,
>
> Was the change with 8.5.44 implemented when you run the service.bat file?
It should be. The change was made in Commons Daemon (the .exe files) so
it should apply however you install the service.
Mark
>
> Thanks,
>
On 10/06/2020 14:07, Paul Carter-Brown wrote:
> At runtime, any code can call TimeZone.setDefault to change the timezone of
> the JVM.
>
> I'd suggest logging TimeZone.getDefault().getDisplayName(Locale.ENGLISH);
> intermittently and seeing if some code somewhere is changing the timezone.
> Could
At runtime, any code can call TimeZone.setDefault to change the timezone of
the JVM.
I'd suggest logging TimeZone.getDefault().getDisplayName(Locale.ENGLISH);
intermittently and seeing if some code somewhere is changing the timezone.
Could be in any library...
Paul
On Wed, Jun 10, 2020 at 2:56
Hi,
today I've seen something I don't understand: our developers reported an
application that was returning a non-GMT timezone in Date and
Last-Modified headers.
$ curl -v http://localhost:8080
* Rebuilt URL to: http://localhost:8080/
* Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to local
Hi Luis,
Thanks for your suggestion.
But I am wondering what has changed in 9.0.31. Because my webapp works
perfectly fine in 9.0.24 and 9.0.35.
Thanks
Naveen
On Wed, Jun 10, 2020 at 2:52 PM Luis Rodríguez Fernández
wrote:
> Hello Naveen,
>
> Recently we have had a similar issue migrating a we
Hello Naveen,
Recently we have had a similar issue migrating a webapp from another
application server to tomcat. We solved it specifying
UTF-8 in the
web.xml descriptor.
You can read here [1] the long story :)
Hope it helps,
Luis
[1] https://cwiki.apache.org/confluence/display/TOMCAT/Character
Hi All,
I have a webapp A which has few SOAP services and I consume those services
from webapp B.
I started getting below error since I upgraded the tomcat to 9.0.31 (from
9.0.24):
com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync Couldn't create SOAP
message due to exception: XML reader error
Am 2020-06-09 um 22:20 schrieb Mark Thomas:
Hi all,
An enhancement has been opened to enable response compression by default:
https://bz.apache.org/bugzilla/show_bug.cgi?id=64431
In short, the proposal is to change the default for the Connector's
compression attribute from "off" to "on".
This
Although I believe that buggy clients are no longer a problem today,
compression may introduce complications when Tomcat runs behind a
reverse proxy as it is often the case. If your front-end server (e.g.
Apache) needs to modify the responses (e.g. with mod_proxy_http), you'll
end up with a qui
On Tue, Jun 9, 2020 at 10:20 PM Mark Thomas wrote:
> Hi all,
>
> An enhancement has been opened to enable response compression by default:
> https://bz.apache.org/bugzilla/show_bug.cgi?id=64431
>
> In short, the proposal is to change the default for the Connector's
> compression attribute from "o
16 matches
Mail list logo
