[GUMP@vmgump]: Project tomcat-tc8.0.x-test-apr (in module tomcat-8.0.x) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-tc8.0.x-test-apr has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-tc8.0.x-test-apr : Tomcat 8.x, a web server implementing the Java Servlet 3.1, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-8.0.x/tomcat-tc8.0.x-test-apr/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on commons-daemon exists, no need to add for property commons-daemon.native.src.tgz. -DEBUG- Dependency on commons-daemon exists, no need to add for property tomcat-native.tar.gz. -INFO- Failed with reason build failed -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-8.0.x/output/logs-APR -INFO- Project Reports in: /srv/gump/public/workspace/tomcat-8.0.x/output/test-tmp-APR/logs The following work was performed: http://vmgump.apache.org/gump/public/tomcat-8.0.x/tomcat-tc8.0.x-test-apr/gump_work/build_tomcat-8.0.x_tomcat-tc8.0.x-test-apr.html Work Name: build_tomcat-8.0.x_tomcat-tc8.0.x-test-apr (Type: Build) Work ended in a state of : Failed Elapsed: 37 mins 18 secs Command Line: /usr/lib/jvm/java-8-oracle/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Djunit.jar=/srv/gump/public/workspace/junit/target/junit-4.13-SNAPSHOT.jar -Dobjenesis.jar=/srv/gump/public/workspace/objenesis/main/target/objenesis-2.2-SNAPSHOT.jar -Dtest.reports=output/logs-APR -Dtomcat-native.tar.gz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-20150418-native-src.tar.gz -Dexamples.sources.skip=true -Djdt.jar=/srv/gump/packages/eclipse/plugins/R-4.4-201406061215/ecj-4.4.jar -Dtest.apr.loc=/srv/gump/public/workspace/tomcat-native/dest-20150418/lib -Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons-daemon-20150418.jar -Dcommons-daemon.native.src.tgz=/srv/gump/public/workspace/apache-commons/daemon/dist/bin/commons-daemon-20150418-native-src.tar.gz -Dtest.temp=output/test-tmp-APR -Dtest.accesslog=true -Dexecute.test.nio=false -Dtest .openssl.path=/srv/gump/public/workspace/openssl-1.0.2/dest-20150418/bin/openssl -Dexecute.test.bio=false -Dexecute.test.apr=true -Dtest.excludePerformance=true -Dexecute.test.nio2=false -Deasymock.jar=/srv/gump/public/workspace/easymock/easymock/target/easymock-3.4-SNAPSHOT.jar -Dhamcrest.jar=/srv/gump/packages/hamcrest/hamcrest-core-1.3.jar -Dcglib.jar=/srv/gump/packages/cglib/cglib-nodep-2.2.jar test [Working Directory: /srv/gump/public/workspace/tomcat-8.0.x] CLASSPATH: /usr/lib/jvm/java-8-oracle/lib/tools.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/webapps/examples/WEB-INF/classes:/srv/gump/public/workspace/tomcat-8.0.x/output/testclasses:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit4.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/bin/bootstrap.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/bin/tomcat-juli.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/lib/annotations-api.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/lib/servlet-api.ja r:/srv/gump/public/workspace/tomcat-8.0.x/output/build/lib/jsp-api.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/lib/el-api.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/lib/websocket-api.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/lib/catalina.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/lib/catalina-ant.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/lib/catalina-storeconfig.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/lib/tomcat-coyote.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/lib/jasper.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/lib/jasper-el.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/lib/catalina-tribes.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/lib/catalina-ha.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/lib/tomcat-api.jar:/srv/gump/public/workspace/tomcat-8.0.x/output/build/lib
[Bug 57830] New: Add support for ProxyProtocol
https://bz.apache.org/bugzilla/show_bug.cgi?id=57830 Bug ID: 57830 Summary: Add support for ProxyProtocol Product: Tomcat 8 Version: 8.0.21 Hardware: PC OS: Mac OS X 10.1 Status: NEW Severity: normal Priority: P2 Component: Connectors Assignee: dev@tomcat.apache.org Reporter: frank.kl...@gmail.com When using TCP load balancing to avoid terminating HTTPS at a load balancer, there are few options for passing client information to the backend server from the load balancer. AWS uses ProxyProtocol (http://www.haproxy.org/download/1.5/doc/proxy-protocol.txt) as the mechanism to pass client information to servers behind a load balancer. http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/enable-proxy-protocol.html When ProxyProtocol is enabled for TCP load balancing over HTTPS, Tomcat cannot serve the request. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 57831] New: Fragmented JSON Messages Causing IllegalStateException
https://bz.apache.org/bugzilla/show_bug.cgi?id=57831
Bug ID: 57831
Summary: Fragmented JSON Messages Causing IllegalStateException
Product: Tomcat 8
Version: 8.0.21
Hardware: All
OS: All
Status: NEW
Severity: critical
Priority: P2
Component: WebSocket
Assignee: dev@tomcat.apache.org
Reporter: kenneth.gend...@gmail.com
Created attachment 32660
--> https://bz.apache.org/bugzilla/attachment.cgi?id=32660&action=edit
Message that causes the failure
Tomcat 8.0.21 (not 8.0.20 or earlier) is throwing an IllegalStateException for
JSON messages. Below is the exception being thrown.
Exception in thread "WebSocketServer-localhost-/temp-4"
java.lang.IllegalStateException: When sending a fragmented message, all
fragments bust be of the same type
at
org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:411)
at
org.apache.tomcat.websocket.WsRemoteEndpointImplBase.endMessage(WsRemoteEndpointImplBase.java:366)
at
org.apache.tomcat.websocket.WsRemoteEndpointImplBase$IntermediateMessageHandler.onResult(WsRemoteEndpointImplBase.java:513)
at
org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer$OnResultRunnable.run(WsRemoteEndpointImplServer.java:247)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Attached is the message that is causing the issue.
Looking at the top few lines:
{
"context": "4IVS04",
"data": {
"enterfornext": true,
"inputs": [
{
"autocomplete": 3,
"desc": "Enter Tool: ",
"options": [
"DNOTCH10",
"DNOTCH11",
If the entire "DNOTCH10" line is removed, the message can be transmitted by
Tomcat; however, even adding a single "illegal" character in the JSON after
this line is removed causes the error to be thrown.
It appears Tomcat is analyzing the fragments its sending and determining that
some cannot be sent because they are not legitimate JSON (or something to that
affect).
Again, version 8.0.20 and below does not have this issue.
Thanks
Ken
P.S. I can provide the test web app to demonstrate this.
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 57831] Fragmented JSON Messages Causing IllegalStateException
https://bz.apache.org/bugzilla/show_bug.cgi?id=57831 --- Comment #1 from Kenneth Gendron --- The changes to PerMessageDeflate class have caused the opCode for the subsequent fragments to change from OPCODE_TEXT to OPCODE_CONTINUATION (i.e. they are transformed). This cause the "Util.isText(mp.getOpCode())" code at line 406 of the WsRemoteEndpointImplBase class to return false. I suspect other things are being affected by the PerMessageDeflate class changes, most notably the other send methods; however, adding "|| Util.isContinuation(mp.getOpCode())" will fix this. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 57831] Fragmented JSON Messages Causing IllegalStateException
https://bz.apache.org/bugzilla/show_bug.cgi?id=57831 --- Comment #2 from Kenneth Gendron --- Line 451 in PerMessageDeflate. Just as an aside this should be set to Constants.OPCODE_CONTINUATION, not zero "0" explicitly. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 57831] Fragmented JSON Messages Causing IllegalStateException
https://bz.apache.org/bugzilla/show_bug.cgi?id=57831
--- Comment #3 from Kenneth Gendron ---
The fix I proposed would have broken binary transmission. Instead simply
changing line 410 in WsRemoteEndpointImplBase to "if (text != isText &&
mp.getOpCode() != Constants.OPCODE_CONTINUATION) {" should work. It does
essentially break the implementations ability to detect changes in type but I
do not see a ready alternative.
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
