REST issue

Some foundation facts: Development environment using NetBeans 8.0.2, Tomcat 8.0.32, Java jdk1.8.0_121 and Postman. The code: I have a simple hello world servlet for testing (in production, the service will serve as an endpoint for information from another organization): package

Re: AW: JVM Crash in tcnative due to concurrency/timing in HTTP/2

On 13/06/17 10:13, Kreuser, Peter wrote: > Mark, > >> On 09/06/17 16:02, Kreuser, Peter wrote: >>> Hi all, >>> >>> Sorry for the long text. I hope somebody can help me track down the problem >>> I'm facing with Tomcat (8.5.15), tcnative (1.2.12), openssl (1.1.0e) and >>> HTTP/2. JVM is

AW: JVM Crash in tcnative due to concurrency/timing in HTTP/2

Mark, > On 09/06/17 16:02, Kreuser, Peter wrote: > > Hi all, > > > > Sorry for the long text. I hope somebody can help me track down the problem > > I'm facing with Tomcat (8.5.15), tcnative (1.2.12), openssl (1.1.0e) and > > HTTP/2. JVM is zulu-8.21.0.1 (1.8.0_131-b11) > > No need to

Re: tomcat 7, null tag attributes

On Tue, Jun 6, 2017 at 2:29 PM, Mark Thomas wrote: > On 31/05/17 23:31, Chris Cheshire wrote: > > I am using tomcat 7 on CentOS 7 and I need to pass a null value to tag > > attributes of type Long/Integer/Float, however it is *always* coerced to > > zero. > > > > <%@attribute

Re: tomcat 7, null tag attributes

On 13/06/17 22:01, Mark Thomas wrote: > On 13/06/17 15:27, Chris Cheshire wrote: >> I'm bewildered at why tomcat operates this way when it comes to Numbers and >> Strings. Why is it insistent on coercion when null and zero are absolutely >> not the same value. If this is because of autoboxing,

AsynContext.dispatch() with encoded URI

hi, The spec says: "If the AsyncContext was initialized via the startAsync(ServletRequest, ServletResponse) and the request passed is an instance of HttpServletRequest , then the dispatch is to the URI returned by HttpServletRequest.getRequestURI()" However AsyncContextImpl seems to be using

Re: tomcat 7, null tag attributes

On 13/06/17 15:27, Chris Cheshire wrote: > On Tue, Jun 6, 2017 at 2:29 PM, Mark Thomas wrote: > >> On 31/05/17 23:31, Chris Cheshire wrote: >>> I am using tomcat 7 on CentOS 7 and I need to pass a null value to tag >>> attributes of type Long/Integer/Float, however it is

IPV6

Hello I am having below query for tomcat 8.5.15 version. Please help. I am using tomcat 8.5.15 and my network is supporting both ipv4 and ipv6 address stacks. However, I want tomcat to listen to only ipv6 address (not ipv4). I was trying to find the solution on google and reached to tomcat's

Re: AsynContext.dispatch() with encoded URI

On 13/06/17 21:30, Rossen Stoyanchev wrote: > hi, > > The spec says: > > "If the AsyncContext was initialized via the startAsync(ServletRequest, > ServletResponse) and the request passed is an instance of > HttpServletRequest , then the dispatch is to the URI returned by >

Re: AsynContext.dispatch() with encoded URI

Issue created https://bz.apache.org/bugzilla/show_bug.cgi?id=61185. On Tue, Jun 13, 2017 at 6:25 PM, Mark Thomas wrote: > On 13/06/17 21:30, Rossen Stoyanchev wrote: > > hi, > > > > The spec says: > > > > "If the AsyncContext was initialized via the startAsync(ServletRequest,

RE: tomcat 7, null tag attributes

All, As of now we are using the below parameters for tomcat8 version on production environment, please recheck and confirm, these are fine or anything need to add or change. Please confirm me. export CATALINA_OPTS="$CATALINA_OPTS -Xms1024m" export CATALINA_OPTS="$CATALINA_OPTS -Xmx8192m"

Re: [OT] tomcat 7, null tag attributes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Naga, Please don't hijack threads. If you wish to ask a question, please post a new message (don't REPLY to an old one) to the list. Thanks, - -chris On 6/13/17 1:00 PM, Naga Ramesh wrote: > All, > > As of now we are using the below parameters