Re: Allowing tokens without an exp claim
+1 On Fri, Nov 8, 2019 at 10:16 AM Jonathan Gallimore < jonathan.gallim...@gmail.com> wrote: > Hi All, > > At present TomEE will reject JWT tokens where the exp claim is a timestamp > that is in the past. We also reject tokens where there is no exp claim at > all. > > I propose adding a setting which will allow tokens without an exp claim to > be accepted (see https://tools.ietf.org/html/rfc7519#section-4.1.4 - using > exp is optional). > > The current behavior (not allowing a token without an exp claim) would be > the default, and the option to allow tokens without an exp would need to be > explicitly enabled. > > Are there any objections? > > Jon > -- Richard Monson-Haefel https://twitter.com/rmonson https://www.linkedin.com/in/monsonhaefel/
Re: Docker Images on Dockerhub
Looks like the microprofile distribution is missing jakarta.activation. Adding that in (from the plus distribution) allows the server to start correctly. I've filed a JIRA: https://issues.apache.org/jira/browse/TOMEE-2731 I'm happy to take, but if you would like to take a swing at it Rod, let me know and we'll get it assigned to you. Jon On Fri, Nov 8, 2019 at 4:35 PM Jonathan Gallimore < jonathan.gallim...@gmail.com> wrote: > I can confirm I see the same error. Looks like its specific to the > microprofile flavor. I'll see if I can spot anything odd there. > > On Fri, Nov 8, 2019 at 3:39 PM Jenkins, Rodney J (Rod) < > jenki...@nationwide.com> wrote: > >> I have done some further testing >> >> All testing is on : >> >> $ java -version >> openjdk version "11.0.5" 2019-10-15 LTS >> OpenJDK Runtime Environment 18.9 (build 11.0.5+10-LTS) >> OpenJDK 64-Bit Server VM 18.9 (build 11.0.5+10-LTS, mixed mode, sharing) >> >> When I pull apache-tomee-microprofile-7.1.1, I do not get the stack >> traces, but when I pull apache-tomee-microprofile-8.0.0, I do get the stack >> traces. >> >> According to the link the Richard provided, the issue occurs when >> compiling the app. In my case, I am not compiling anything. All I am >> doing is downloading the TomEE tar ball and running it. It is the ROOT, >> docs, manager, and host-manager apps that throw the stack trace. >> >> Can one of you please grab that tar ball and see if you get the same >> issues as I do? >> >> Thank you!! >> Rod. >> >> >> On 11/7/19, 8:08 AM, "Richard Monson-Haefel" >> wrote: >> >> Hi Rodney, >> >> Thanks for all the hard work! I think the problem is with JAXB which >> suffered some changes in Java 8 - 11. This article should provide >> some >> guidance on what needs to be done to fix the problem. >> >> https://www.jesperdj.com/2018/09/30/jaxb-on-java-9-10-11-and-beyond/ >> >> Richard >> >> On Tue, Nov 5, 2019 at 12:09 AM Jenkins, Rodney J (Rod) < >> jenki...@nationwide.com> wrote: >> >> > Hello all, >> > >> > I have a completed repo for you all to look at here: >> > https://github.com/scriptmonkey/docker-tomee >> > >> > The only thing I am having an issue with is the Java 11 8.0.0 >> microprofile >> > image. I am getting some stack traces when I build that. I have >> pasted >> > the log file below. I did not create a pull request because I >> would like >> > to clean up the stack traces. >> > >> > All of the other images start without issue. >> > >> > >> > Using CATALINA_BASE: /usr/local/tomee >> > Using CATALINA_HOME: /usr/local/tomee >> > Using CATALINA_TMPDIR: /usr/local/tomee/temp >> > Using JRE_HOME:/usr/local/openjdk-11 >> > Using CLASSPATH: >> > >> /usr/local/tomee/bin/bootstrap.jar:/usr/local/tomee/bin/tomcat-juli.jar >> > NOTE: Picked up JDK_JAVA_OPTIONS: >> > --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/ >> java.io=ALL-UNNAMED >> > --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED >> > WARNING: An illegal reflective access operation has occurred >> > WARNING: Illegal reflective access by >> > org.apache.tomee.catalina.ServerListener >> > (file:/usr/local/tomee/lib/tomee-catalina-8.0.0.jar) to field >> > java.lang.reflect.Field.modifiers >> > WARNING: Please consider reporting this to the maintainers of >> > org.apache.tomee.catalina.ServerListener >> > WARNING: Use --illegal-access=warn to enable warnings of further >> illegal >> > reflective access operations >> > WARNING: All illegal access operations will be denied in a future >> release >> > 05-Nov-2019 05:49:18.411 INFO [main] >> > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Server version >> name: >> > Apache Tomcat (TomEE)/9.0.22 (8.0.0) >> > 05-Nov-2019 05:49:18.414 INFO [main] >> > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Server built: >> > Jul 4 2019 14:20:06 UTC >> > 05-Nov-2019 05:49:18.414 INFO [main] >> > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Server version >> number: >> > 9.0.22.0 >> > 05-Nov-2019 05:49:18.414 INFO [main] >> > jdk.internal.reflect.NativeMethodAccessorImpl.invoke OS Name: >> > Linux >> > 05-Nov-2019 05:49:18.415 INFO [main] >> > jdk.internal.reflect.NativeMethodAccessorImpl.invoke OS Version: >> > 4.9.184-linuxkit >> > 05-Nov-2019 05:49:18.415 INFO [main] >> > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Architecture: >> > amd64 >> > 05-Nov-2019 05:49:18.415 INFO [main] >> > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Java Home: >> > /usr/local/openjdk-11 >> > 05-Nov-2019 05:49:18.415 INFO [main] >> > jdk.internal.reflect.NativeMethodAccessorImpl.invoke JVM Version: >> > 11.0.4+11 >> > 05-Nov-2019 05:49:18.415 INFO [main] >> > jdk.internal.reflect.NativeMethodAccessorImpl.invoke JVM Vendor:
Re: Docker Images on Dockerhub
I can confirm I see the same error. Looks like its specific to the microprofile flavor. I'll see if I can spot anything odd there. On Fri, Nov 8, 2019 at 3:39 PM Jenkins, Rodney J (Rod) < jenki...@nationwide.com> wrote: > I have done some further testing > > All testing is on : > > $ java -version > openjdk version "11.0.5" 2019-10-15 LTS > OpenJDK Runtime Environment 18.9 (build 11.0.5+10-LTS) > OpenJDK 64-Bit Server VM 18.9 (build 11.0.5+10-LTS, mixed mode, sharing) > > When I pull apache-tomee-microprofile-7.1.1, I do not get the stack > traces, but when I pull apache-tomee-microprofile-8.0.0, I do get the stack > traces. > > According to the link the Richard provided, the issue occurs when > compiling the app. In my case, I am not compiling anything. All I am > doing is downloading the TomEE tar ball and running it. It is the ROOT, > docs, manager, and host-manager apps that throw the stack trace. > > Can one of you please grab that tar ball and see if you get the same > issues as I do? > > Thank you!! > Rod. > > > On 11/7/19, 8:08 AM, "Richard Monson-Haefel" > wrote: > > Hi Rodney, > > Thanks for all the hard work! I think the problem is with JAXB which > suffered some changes in Java 8 - 11. This article should provide some > guidance on what needs to be done to fix the problem. > > https://www.jesperdj.com/2018/09/30/jaxb-on-java-9-10-11-and-beyond/ > > Richard > > On Tue, Nov 5, 2019 at 12:09 AM Jenkins, Rodney J (Rod) < > jenki...@nationwide.com> wrote: > > > Hello all, > > > > I have a completed repo for you all to look at here: > > https://github.com/scriptmonkey/docker-tomee > > > > The only thing I am having an issue with is the Java 11 8.0.0 > microprofile > > image. I am getting some stack traces when I build that. I have > pasted > > the log file below. I did not create a pull request because I would > like > > to clean up the stack traces. > > > > All of the other images start without issue. > > > > > > Using CATALINA_BASE: /usr/local/tomee > > Using CATALINA_HOME: /usr/local/tomee > > Using CATALINA_TMPDIR: /usr/local/tomee/temp > > Using JRE_HOME:/usr/local/openjdk-11 > > Using CLASSPATH: > > > /usr/local/tomee/bin/bootstrap.jar:/usr/local/tomee/bin/tomcat-juli.jar > > NOTE: Picked up JDK_JAVA_OPTIONS: > > --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/ > java.io=ALL-UNNAMED > > --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED > > WARNING: An illegal reflective access operation has occurred > > WARNING: Illegal reflective access by > > org.apache.tomee.catalina.ServerListener > > (file:/usr/local/tomee/lib/tomee-catalina-8.0.0.jar) to field > > java.lang.reflect.Field.modifiers > > WARNING: Please consider reporting this to the maintainers of > > org.apache.tomee.catalina.ServerListener > > WARNING: Use --illegal-access=warn to enable warnings of further > illegal > > reflective access operations > > WARNING: All illegal access operations will be denied in a future > release > > 05-Nov-2019 05:49:18.411 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Server version > name: > > Apache Tomcat (TomEE)/9.0.22 (8.0.0) > > 05-Nov-2019 05:49:18.414 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Server built: > > Jul 4 2019 14:20:06 UTC > > 05-Nov-2019 05:49:18.414 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Server version > number: > > 9.0.22.0 > > 05-Nov-2019 05:49:18.414 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke OS Name: > > Linux > > 05-Nov-2019 05:49:18.415 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke OS Version: > > 4.9.184-linuxkit > > 05-Nov-2019 05:49:18.415 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Architecture: > > amd64 > > 05-Nov-2019 05:49:18.415 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Java Home: > > /usr/local/openjdk-11 > > 05-Nov-2019 05:49:18.415 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke JVM Version: > > 11.0.4+11 > > 05-Nov-2019 05:49:18.415 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke JVM Vendor: > > Oracle Corporation > > 05-Nov-2019 05:49:18.415 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke CATALINA_BASE: > > /usr/local/tomee > > 05-Nov-2019 05:49:18.415 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke CATALINA_HOME: > > /usr/local/tomee > > 05-Nov-2019 05:49:18.451 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Command line > argument: > > --add-opens=java.base/java.lang=ALL-UNNAMED > > 05-Nov-2019 05:49:18.451 INFO [main] >
Re: Allowing tokens without an exp claim
Hi, +1 to the proposed setting since it ensures backward compatibility. El vie., 8 nov. 2019 a las 10:16, Jonathan Gallimore (< jonathan.gallim...@gmail.com>) escribió: > Hi All, > > At present TomEE will reject JWT tokens where the exp claim is a timestamp > that is in the past. We also reject tokens where there is no exp claim at > all. > > I propose adding a setting which will allow tokens without an exp claim to > be accepted (see https://tools.ietf.org/html/rfc7519#section-4.1.4 - using > exp is optional). > > The current behavior (not allowing a token without an exp claim) would be > the default, and the option to allow tokens without an exp would need to be > explicitly enabled. > > Are there any objections? > > Jon > -- Atentamente: César Hernández.
Allowing tokens without an exp claim
Hi All, At present TomEE will reject JWT tokens where the exp claim is a timestamp that is in the past. We also reject tokens where there is no exp claim at all. I propose adding a setting which will allow tokens without an exp claim to be accepted (see https://tools.ietf.org/html/rfc7519#section-4.1.4 - using exp is optional). The current behavior (not allowing a token without an exp claim) would be the default, and the option to allow tokens without an exp would need to be explicitly enabled. Are there any objections? Jon
Re: Docker Images on Dockerhub
Yes, I'll take a look and report back. Thanks Jon On Fri, Nov 8, 2019 at 3:39 PM Jenkins, Rodney J (Rod) < jenki...@nationwide.com> wrote: > I have done some further testing > > All testing is on : > > $ java -version > openjdk version "11.0.5" 2019-10-15 LTS > OpenJDK Runtime Environment 18.9 (build 11.0.5+10-LTS) > OpenJDK 64-Bit Server VM 18.9 (build 11.0.5+10-LTS, mixed mode, sharing) > > When I pull apache-tomee-microprofile-7.1.1, I do not get the stack > traces, but when I pull apache-tomee-microprofile-8.0.0, I do get the stack > traces. > > According to the link the Richard provided, the issue occurs when > compiling the app. In my case, I am not compiling anything. All I am > doing is downloading the TomEE tar ball and running it. It is the ROOT, > docs, manager, and host-manager apps that throw the stack trace. > > Can one of you please grab that tar ball and see if you get the same > issues as I do? > > Thank you!! > Rod. > > > On 11/7/19, 8:08 AM, "Richard Monson-Haefel" > wrote: > > Hi Rodney, > > Thanks for all the hard work! I think the problem is with JAXB which > suffered some changes in Java 8 - 11. This article should provide some > guidance on what needs to be done to fix the problem. > > https://www.jesperdj.com/2018/09/30/jaxb-on-java-9-10-11-and-beyond/ > > Richard > > On Tue, Nov 5, 2019 at 12:09 AM Jenkins, Rodney J (Rod) < > jenki...@nationwide.com> wrote: > > > Hello all, > > > > I have a completed repo for you all to look at here: > > https://github.com/scriptmonkey/docker-tomee > > > > The only thing I am having an issue with is the Java 11 8.0.0 > microprofile > > image. I am getting some stack traces when I build that. I have > pasted > > the log file below. I did not create a pull request because I would > like > > to clean up the stack traces. > > > > All of the other images start without issue. > > > > > > Using CATALINA_BASE: /usr/local/tomee > > Using CATALINA_HOME: /usr/local/tomee > > Using CATALINA_TMPDIR: /usr/local/tomee/temp > > Using JRE_HOME:/usr/local/openjdk-11 > > Using CLASSPATH: > > > /usr/local/tomee/bin/bootstrap.jar:/usr/local/tomee/bin/tomcat-juli.jar > > NOTE: Picked up JDK_JAVA_OPTIONS: > > --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/ > java.io=ALL-UNNAMED > > --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED > > WARNING: An illegal reflective access operation has occurred > > WARNING: Illegal reflective access by > > org.apache.tomee.catalina.ServerListener > > (file:/usr/local/tomee/lib/tomee-catalina-8.0.0.jar) to field > > java.lang.reflect.Field.modifiers > > WARNING: Please consider reporting this to the maintainers of > > org.apache.tomee.catalina.ServerListener > > WARNING: Use --illegal-access=warn to enable warnings of further > illegal > > reflective access operations > > WARNING: All illegal access operations will be denied in a future > release > > 05-Nov-2019 05:49:18.411 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Server version > name: > > Apache Tomcat (TomEE)/9.0.22 (8.0.0) > > 05-Nov-2019 05:49:18.414 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Server built: > > Jul 4 2019 14:20:06 UTC > > 05-Nov-2019 05:49:18.414 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Server version > number: > > 9.0.22.0 > > 05-Nov-2019 05:49:18.414 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke OS Name: > > Linux > > 05-Nov-2019 05:49:18.415 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke OS Version: > > 4.9.184-linuxkit > > 05-Nov-2019 05:49:18.415 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Architecture: > > amd64 > > 05-Nov-2019 05:49:18.415 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Java Home: > > /usr/local/openjdk-11 > > 05-Nov-2019 05:49:18.415 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke JVM Version: > > 11.0.4+11 > > 05-Nov-2019 05:49:18.415 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke JVM Vendor: > > Oracle Corporation > > 05-Nov-2019 05:49:18.415 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke CATALINA_BASE: > > /usr/local/tomee > > 05-Nov-2019 05:49:18.415 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke CATALINA_HOME: > > /usr/local/tomee > > 05-Nov-2019 05:49:18.451 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Command line > argument: > > --add-opens=java.base/java.lang=ALL-UNNAMED > > 05-Nov-2019 05:49:18.451 INFO [main] > > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Command line > argument:
Re: Docker Images on Dockerhub
I have done some further testing All testing is on : $ java -version openjdk version "11.0.5" 2019-10-15 LTS OpenJDK Runtime Environment 18.9 (build 11.0.5+10-LTS) OpenJDK 64-Bit Server VM 18.9 (build 11.0.5+10-LTS, mixed mode, sharing) When I pull apache-tomee-microprofile-7.1.1, I do not get the stack traces, but when I pull apache-tomee-microprofile-8.0.0, I do get the stack traces. According to the link the Richard provided, the issue occurs when compiling the app. In my case, I am not compiling anything. All I am doing is downloading the TomEE tar ball and running it. It is the ROOT, docs, manager, and host-manager apps that throw the stack trace. Can one of you please grab that tar ball and see if you get the same issues as I do? Thank you!! Rod. On 11/7/19, 8:08 AM, "Richard Monson-Haefel" wrote: Hi Rodney, Thanks for all the hard work! I think the problem is with JAXB which suffered some changes in Java 8 - 11. This article should provide some guidance on what needs to be done to fix the problem. https://www.jesperdj.com/2018/09/30/jaxb-on-java-9-10-11-and-beyond/ Richard On Tue, Nov 5, 2019 at 12:09 AM Jenkins, Rodney J (Rod) < jenki...@nationwide.com> wrote: > Hello all, > > I have a completed repo for you all to look at here: > https://github.com/scriptmonkey/docker-tomee > > The only thing I am having an issue with is the Java 11 8.0.0 microprofile > image. I am getting some stack traces when I build that. I have pasted > the log file below. I did not create a pull request because I would like > to clean up the stack traces. > > All of the other images start without issue. > > > Using CATALINA_BASE: /usr/local/tomee > Using CATALINA_HOME: /usr/local/tomee > Using CATALINA_TMPDIR: /usr/local/tomee/temp > Using JRE_HOME:/usr/local/openjdk-11 > Using CLASSPATH: > /usr/local/tomee/bin/bootstrap.jar:/usr/local/tomee/bin/tomcat-juli.jar > NOTE: Picked up JDK_JAVA_OPTIONS: > --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED > --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > org.apache.tomee.catalina.ServerListener > (file:/usr/local/tomee/lib/tomee-catalina-8.0.0.jar) to field > java.lang.reflect.Field.modifiers > WARNING: Please consider reporting this to the maintainers of > org.apache.tomee.catalina.ServerListener > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > 05-Nov-2019 05:49:18.411 INFO [main] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Server version name: > Apache Tomcat (TomEE)/9.0.22 (8.0.0) > 05-Nov-2019 05:49:18.414 INFO [main] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Server built: > Jul 4 2019 14:20:06 UTC > 05-Nov-2019 05:49:18.414 INFO [main] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Server version number: > 9.0.22.0 > 05-Nov-2019 05:49:18.414 INFO [main] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke OS Name: > Linux > 05-Nov-2019 05:49:18.415 INFO [main] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke OS Version: > 4.9.184-linuxkit > 05-Nov-2019 05:49:18.415 INFO [main] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Architecture: > amd64 > 05-Nov-2019 05:49:18.415 INFO [main] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Java Home: > /usr/local/openjdk-11 > 05-Nov-2019 05:49:18.415 INFO [main] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke JVM Version: > 11.0.4+11 > 05-Nov-2019 05:49:18.415 INFO [main] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke JVM Vendor: > Oracle Corporation > 05-Nov-2019 05:49:18.415 INFO [main] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke CATALINA_BASE: > /usr/local/tomee > 05-Nov-2019 05:49:18.415 INFO [main] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke CATALINA_HOME: > /usr/local/tomee > 05-Nov-2019 05:49:18.451 INFO [main] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Command line argument: > --add-opens=java.base/java.lang=ALL-UNNAMED > 05-Nov-2019 05:49:18.451 INFO [main] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Command line argument: > --add-opens=java.base/java.io=ALL-UNNAMED > 05-Nov-2019 05:49:18.451 INFO [main] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Command line argument: > --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED > 05-Nov-2019 05:49:18.452 INFO [main] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke Command
Re: Issue with Chunked encoding in tomcat/tomee with a specific file
Hi! Thanks for reporting this. Is the exception dump from your client communicating with TomEE? I'm assuming that what it is, but I want to be sure. If exception is generated by a TomEE instance that would be a different situation. Richard On Fri, Nov 8, 2019 at 5:27 AM mshvr wrote: > The stack trace looks something like below. I'll share the required sources > and exact stack trace in short time: > > The link for earlier attachment (binaries only without sources) : > > http://tomee-openejb.979440.n4.nabble.com/file/t376364/ChunkedEncodingIssue.zip > > . > . > . > ... 7 common frames omitted > Caused by: java.io.IOException: Protocol violation: Unexpected single > newline character in chunk size > at > > org.apache.commons.httpclient.ChunkedInputStream.getChunkSizeFromInputStream(ChunkedInputStream.java:273) > ~[commons-httpclient-3.1.jar:na] > at > > org.apache.commons.httpclient.ChunkedInputStream.nextChunk(ChunkedInputStream.java:221) > ~[commons-httpclient-3.1.jar:na] > at > > org.apache.commons.httpclient.ChunkedInputStream.read(ChunkedInputStream.java:176) > ~[commons-httpclient-3.1.jar:na] > at java.io.FilterInputStream.read(FilterInputStream.java:133) > ~[na:1.8.0_141] > at > > org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:108) > ~[commons-httpclient-3.1.jar:na] > at java.io.FilterInputStream.read(FilterInputStream.java:107) > ~[na:1.8.0_141] > at > > org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:127) > ~[commons-httpclient-3.1.jar:na] > at java.nio.file.Files.copy(Files.java:2908) ~[na:1.8.0_141] > at java.nio.file.Files.copy(Files.java:3027) ~[na:1.8.0_141] > > > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html > -- Richard Monson-Haefel https://twitter.com/rmonson https://www.linkedin.com/in/monsonhaefel/
Re: Issue with Chunked encoding in tomcat/tomee with a specific file
The stack trace looks something like below. I'll share the required sources and exact stack trace in short time: The link for earlier attachment (binaries only without sources) : http://tomee-openejb.979440.n4.nabble.com/file/t376364/ChunkedEncodingIssue.zip . . . ... 7 common frames omitted Caused by: java.io.IOException: Protocol violation: Unexpected single newline character in chunk size at org.apache.commons.httpclient.ChunkedInputStream.getChunkSizeFromInputStream(ChunkedInputStream.java:273) ~[commons-httpclient-3.1.jar:na] at org.apache.commons.httpclient.ChunkedInputStream.nextChunk(ChunkedInputStream.java:221) ~[commons-httpclient-3.1.jar:na] at org.apache.commons.httpclient.ChunkedInputStream.read(ChunkedInputStream.java:176) ~[commons-httpclient-3.1.jar:na] at java.io.FilterInputStream.read(FilterInputStream.java:133) ~[na:1.8.0_141] at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:108) ~[commons-httpclient-3.1.jar:na] at java.io.FilterInputStream.read(FilterInputStream.java:107) ~[na:1.8.0_141] at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:127) ~[commons-httpclient-3.1.jar:na] at java.nio.file.Files.copy(Files.java:2908) ~[na:1.8.0_141] at java.nio.file.Files.copy(Files.java:3027) ~[na:1.8.0_141] -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
