Re: Trivial DataSource ResourceLink error

2017-03-13 Thread Konstantin Kolinko
2017-03-13 13:44 GMT+03:00 Enrico Olivelli : > Hi, > I'm trying to setup a DataSource configured in GlobalNamingResources in > server.xml. > https://tomcat.apache.org/tomcat-8.5-doc/config/context.html#Resource_Links > > in server.xml I have: > > > >

Re: POST + 500 + Response returns no content

2017-03-13 Thread Marc Boorshtein
> > > > >> E.g. "Transfer-Encoding: chunked" and "Content-Length" are mutually >> exclusive, cannot be used at the same time, cannot be used more than >> once. They should not be blindly copied. >> > > Good question on that, I can take a look. I remove Content-Length from > the downstream

Re: POST + 500 + Response returns no content

2017-03-13 Thread Konstantin Kolinko
2017-03-12 15:32 GMT+03:00 Marc Boorshtein : > Mark & Olaf, > > I'm working directly with the servlet api. Whats odd is it worked fine in > 8.0.39. The response is set first: > >

Trivial DataSource ResourceLink error

2017-03-13 Thread Enrico Olivelli
Hi, I'm trying to setup a DataSource configured in GlobalNamingResources in server.xml. https://tomcat.apache.org/tomcat-8.5-doc/config/context.html#Resource_Links in server.xml I have: In context.xml I have In web.xml I have

Re: Trivial DataSource ResourceLink error

2017-03-13 Thread Enrico Olivelli
2017-03-13 12:44 GMT+01:00 Konstantin Kolinko : > 2017-03-13 13:44 GMT+03:00 Enrico Olivelli : > > Hi, > > I'm trying to setup a DataSource configured in GlobalNamingResources in > > server.xml. > >

Re: POST + 500 + Response returns no content

2017-03-13 Thread Marc Boorshtein
> > > I'm working directly with the servlet api. Whats odd is it worked fine in > 8.0.39. The response is set first: > > > Also, I just verified the issue doesn't occur using undertow 1.3.25

Re: POST + 500 + Response returns no content

2017-03-13 Thread Marc Boorshtein
> > > > Status 500 means that some error happened during processing. > > Is there anything in the logs? Exceptions? > > The 500 was generated by a downstream Tomcat 8.5.11 server, this one is just trying to proxy the message. > Maybe the browser closes the connection by its own decision,

java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

2017-03-13 Thread Chandrashekar H . S
Hi All, We have recently upgraded tomcat from 8.0.30 to 8.5.11. The tomcat 8.5.11 rejects the requested URI with below error. Requested URI: /poc-root/resource-lists/users/tel:+918197119913/index/~~/resource-lists/list[@name="oma_pocbuddylist"]/entry[@uri="tel:+919742700996"] Mar 13, 2017

Re: java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

2017-03-13 Thread Mark Thomas
On 13/03/17 15:23, Chandrashekar H.S wrote: > Hi All, > We have recently upgraded tomcat from 8.0.30 to 8.5.11. > > The tomcat 8.5.11 rejects the requested URI with below error. > Requested URI: >

A fatal error has been detected by the Java Runtime Environment libjvm

2017-03-13 Thread Vijay Kumar
Hi Team, We have a web application installed in Tomcat 7.0.47. This was working fine till last week but suddenly its failing due to Java Fatal error as specified below. Could any one please suggest how to know the root cause for this issue. Attached the log for reference. # A fatal error has

Re: java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

2017-03-13 Thread Mark Eggers
First of all, sorry for the wrapping. Hint - turn on message wrapping when writing to the mailing list. Anyway, responses are at the end. On 3/13/2017 8:23 AM, Chandrashekar H.S wrote: > Hi All, > We have recently upgraded tomcat from 8.0.30 to 8.5.11. > > The tomcat 8.5.11 rejects the

[SECURITY] CVE-2016-8747 Apache Tomcat Information Disclosure

2017-03-13 Thread Mark Thomas
CVE-2016-8747 Apache Tomcat Information Disclosure Severity: Moderate Vendor: The Apache Software Foundation Versions Affected: Apache Tomcat 9.0.0.M11 to 9.0.0.M15 Apache Tomcat 8.5.7 to 8.5.9 Description The refactoring to make wider use of ByteBuffer introduced a regression that could cause