Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] After upgrade from Jetty 9.2.x to 9.4.x https.ini configuration does not work

Thanks again for taking the time to look through the configuration and reply with helpful information Joakim. Jetty configuration is unfortunately not my area but now my team became aware of the issue and are working on fixing it.

Thank you very much,
Ganime

On Fri, May 19, 2017 at 3:31 PM, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
Your Jetty 9.2 configuration has no ssl or tls or https configuration specified.
Nor does your 9.4 configuration.

Why are you modifying your jetty-distribution and/or deploying into the jetty-distribution directory?
That is not recommended, and you get warnings on startup telling you that.

Make a proper ${jetty.base} directory, somewhere outside of the jetty-distribution directory, and configure that, leave your jetty-distribution alone (unmodified, no changes!)

# Make a new empty directory
$ mkdir /path/to/mybase

# Initialize the start.d directory with your desired modules
$ cd /path/to/mybase
$ java -jar /path/to/jetty-distribution-9.4.4.v20170414/start.jar --create-startd --add-to-start=http,https,deploy,annotations
# Add more modules to an existing jetty.base using the same command above but with different module names, like: jsp,websocket,proxy etc ..

# Copy your webapps into place
$ cp /Users/gakin/code/myapp.war /path/to/mybase/webapps/

# Edit your configuration
$ edit /path/to/mybase/start.d/ssl.ini

# Run Jetty from your ${jetty.base} directory
$ cd /path/to/mybase
$ java -jar /path/to/jetty-distribution-9.4.4.v20170414/start.jar

# or ...

$ cd /path/to/mybase
$ java -jar /path/to/jetty-distribution-9.2.10.v20150310/start.jar



Joakim Erdfelt / joakim@xxxxxxxxxxx

On Fri, May 19, 2017 at 3:18 AM, Ganime Betül AKIN <ganime@xxxxxxxxx> wrote:
Hi Joakim,
Thanks for the quick answer. I did as you said and here are the two configurations:

9.2 (2 instances working)


Java Environment:
-----------------
 java.home = /Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home/jre
 java.vm.vendor = Oracle Corporation
 java.vm.version = 25.45-b02
 java.vm.name = Java HotSpot(TM) 64-Bit Server VM
 java.vm.info = mixed mode
 java.runtime.name = Java(TM) SE Runtime Environment
 java.runtime.version = 1.8.0_45-b14
 java.io.tmpdir = /var/folders/by/f4kqc2n56djg42_29f01m67c000hz0/T/
 user.dir = /Users/gakin/Documents/workspace_openbis_trunk/integration-tests/targets/playground/test_openbis_sync/openbis1/servers/openBIS-server/jetty-dist
 user.language = en
 user.country = US

Jetty Environment:
-----------------
 jetty.version = 9.2.10.v20150310
 jetty.home = /Users/gakin/Documents/workspace_openbis_trunk/integration-tests/targets/playground/test_openbis_sync/openbis1/servers/openBIS-server/jetty-dist
 jetty.base = /Users/gakin/Documents/workspace_openbis_trunk/integration-tests/targets/playground/test_openbis_sync/openbis1/servers/openBIS-server/jetty-dist

Config Search Order:
--------------------
 <command-line>
 ${jetty.base} -> /Users/gakin/Documents/workspace_openbis_trunk/integration-tests/targets/playground/test_openbis_sync/openbis1/servers/openBIS-server/jetty-dist
 ${jetty.home} -> /Users/gakin/Documents/workspace_openbis_trunk/integration-tests/targets/playground/test_openbis_sync/openbis1/servers/openBIS-server/jetty-dist


JVM Arguments:
--------------
 (no jvm args specified)

System Properties:
------------------
 (no system properties specified)

Properties:
-----------
 http.timeout = 30000
 jetty.delayDispatchUntilContent = false
 jetty.dump.start = false
 jetty.dump.stop = false
 jetty.output.buffer.size = 32768
 jetty.port = 8080
 jetty.request.header.size = 8192
 jetty.response.header.size = 8192
 jetty.send.date.header = false
 jetty.send.server.version = true
 jsp-impl = apache
 threads.max = 200
 threads.min = 10
 threads.timeout = 60000

Jetty Server Classpath:
-----------------------
Version Information on 34 entries in the classpath.
Note: order presented here is how they would appear on the classpath.
      changes to the --module=name command line options will be reflected here.
 0:         9.2.10.v20150310 | ${jetty.base}/lib/apache-jsp/org.eclipse.jetty.apache-jsp-9.2.10.v20150310.jar
 1:   3.8.2.v20130121-145325 | ${jetty.base}/lib/apache-jsp/org.eclipse.jetty.orbit.org.eclipse.jdt.core-3.8.2.v20130121.jar
 2:                    8.0.9 | ${jetty.base}/lib/apache-jsp/org.mortbay.jasper.apache-el-8.0.9.M3.jar
 3:                      2.3 | ${jetty.base}/lib/apache-jsp/org.mortbay.jasper.apache-jsp-8.0.9.M3.jar
 4:                    1.2.1 | ${jetty.base}/lib/apache-jstl/org.apache.taglibs.taglibs-standard-impl-1.2.1.jar
 5:                    1.2.1 | ${jetty.base}/lib/apache-jstl/org.apache.taglibs.taglibs-standard-spec-1.2.1.jar
 6:                    (dir) | ${jetty.base}/resources
 7:                    3.1.0 | ${jetty.base}/lib/servlet-api-3.1.jar
 8:                 3.1.0.M0 | ${jetty.base}/lib/jetty-schemas-3.1.jar
 9:         9.2.10.v20150310 | ${jetty.base}/lib/jetty-http-9.2.10.v20150310.jar
10:         9.2.10.v20150310 | ${jetty.base}/lib/jetty-server-9.2.10.v20150310.jar
11:         9.2.10.v20150310 | ${jetty.base}/lib/jetty-xml-9.2.10.v20150310.jar
12:         9.2.10.v20150310 | ${jetty.base}/lib/jetty-util-9.2.10.v20150310.jar
13:         9.2.10.v20150310 | ${jetty.base}/lib/jetty-io-9.2.10.v20150310.jar
14:         9.2.10.v20150310 | ${jetty.base}/lib/jetty-jndi-9.2.10.v20150310.jar
15:      1.4.1.v201005082020 | ${jetty.base}/lib/jndi/javax.mail.glassfish-1.4.1.v201005082020.jar
16:                      1.2 | ${jetty.base}/lib/jndi/javax.transaction-api-1.2.jar
17:         9.2.10.v20150310 | ${jetty.base}/lib/jetty-security-9.2.10.v20150310.jar
18:         9.2.10.v20150310 | ${jetty.base}/lib/jetty-servlet-9.2.10.v20150310.jar
19:         9.2.10.v20150310 | ${jetty.base}/lib/jetty-webapp-9.2.10.v20150310.jar
20:         9.2.10.v20150310 | ${jetty.base}/lib/jetty-deploy-9.2.10.v20150310.jar
21:         9.2.10.v20150310 | ${jetty.base}/lib/jetty-plus-9.2.10.v20150310.jar
22:         9.2.10.v20150310 | ${jetty.base}/lib/jetty-annotations-9.2.10.v20150310.jar
23:                    5.0.1 | ${jetty.base}/lib/annotations/asm-5.0.1.jar
24:                    5.0.1 | ${jetty.base}/lib/annotations/asm-commons-5.0.1.jar
25:                      1.2 | ${jetty.base}/lib/annotations/javax.annotation-api-1.2.jar
26:                      1.0 | ${jetty.base}/lib/websocket/javax.websocket-api-1.0.jar
27:         9.2.10.v20150310 | ${jetty.base}/lib/websocket/javax-websocket-client-impl-9.2.10.v20150310.jar
28:         9.2.10.v20150310 | ${jetty.base}/lib/websocket/javax-websocket-server-impl-9.2.10.v20150310.jar
29:         9.2.10.v20150310 | ${jetty.base}/lib/websocket/websocket-api-9.2.10.v20150310.jar
30:         9.2.10.v20150310 | ${jetty.base}/lib/websocket/websocket-client-9.2.10.v20150310.jar
31:         9.2.10.v20150310 | ${jetty.base}/lib/websocket/websocket-common-9.2.10.v20150310.jar
32:         9.2.10.v20150310 | ${jetty.base}/lib/websocket/websocket-server-9.2.10.v20150310.jar
33:         9.2.10.v20150310 | ${jetty.base}/lib/websocket/websocket-servlet-9.2.10.v20150310.jar

Jetty Active XMLs:
------------------
 ${jetty.base}/etc/home-base-warning.xml
 ${jetty.base}/etc/jetty.xml
 ${jetty.base}/etc/jetty-http.xml
 ${jetty.base}/etc/jetty-deploy.xml
 ${jetty.base}/etc/jetty-plus.xml
 ${jetty.base}/etc/jetty-annotations.xml

9.4 (2 instances not working side by side)

Java Environment:
-----------------
 java.home = /local0/ci/jdk1.8.0_92/jre
 java.vm.vendor = Oracle Corporation
 java.vm.version = 25.92-b14
 java.vm.name = Java HotSpot(TM) 64-Bit Server VM
 java.vm.info = mixed mode
 java.runtime.name = Java(TM) SE Runtime Environment
 java.runtime.version = 1.8.0_92-b14
 java.io.tmpdir = /tmp
 user.dir = /local0/ci/jenkins/workspace_dist/integration-tests/targets/playground/test_openbis_sync/openbis2/servers/openBIS-server/jetty-dist
 user.language = en
 user.country = US

Jetty Environment:
-----------------
 jetty.version = 9.4.4.v20170414
 jetty.tag.version = master
 jetty.home = /local0/ci/jenkins/workspace_dist/integration-tests/targets/playground/test_openbis_sync/openbis2/servers/openBIS-server/jetty-dist
 jetty.base = /local0/ci/jenkins/workspace_dist/integration-tests/targets/playground/test_openbis_sync/openbis2/servers/openBIS-server/jetty-dist

Config Search Order:
--------------------
 <command-line>
 ${jetty.base} -> /local0/ci/jenkins/workspace_dist/integration-tests/targets/playground/test_openbis_sync/openbis2/servers/openBIS-server/jetty-dist
 ${jetty.home} -> /local0/ci/jenkins/workspace_dist/integration-tests/targets/playground/test_openbis_sync/openbis2/servers/openBIS-server/jetty-dist


JVM Arguments:
--------------
 (no jvm args specified)

System Properties:
------------------
 (no system properties specified)

Properties:
-----------
 java.version = 1.8.0_92
 java.version.major = 1
 java.version.micro = 0
 java.version.minor = 8
 java.version.platform = 8
 java.version.update = 92

Jetty Server Classpath:
-----------------------
Version Information on 35 entries in the classpath.
Note: order presented here is how they would appear on the classpath.
      changes to the --module=name command line options will be reflected here.
 0:                    (dir) | ${jetty.base}/resources
 1:                    3.1.0 | ${jetty.base}/lib/servlet-api-3.1.jar
 2:                 3.1.0.M0 | ${jetty.base}/lib/jetty-schemas-3.1.jar
 3:          9.4.4.v20170414 | ${jetty.base}/lib/jetty-http-9.4.4.v20170414.jar
 4:          9.4.4.v20170414 | ${jetty.base}/lib/jetty-server-9.4.4.v20170414.jar
 5:          9.4.4.v20170414 | ${jetty.base}/lib/jetty-xml-9.4.4.v20170414.jar
 6:          9.4.4.v20170414 | ${jetty.base}/lib/jetty-util-9.4.4.v20170414.jar
 7:          9.4.4.v20170414 | ${jetty.base}/lib/jetty-io-9.4.4.v20170414.jar
 8:          9.4.4.v20170414 | ${jetty.base}/lib/jetty-jndi-9.4.4.v20170414.jar
 9:      1.4.1.v201005082020 | ${jetty.base}/lib/jndi/javax.mail.glassfish-1.4.1.v201005082020.jar
10:                      1.2 | ${jetty.base}/lib/jndi/javax.transaction-api-1.2.jar
11:          9.4.4.v20170414 | ${jetty.base}/lib/jetty-security-9.4.4.v20170414.jar
12:          9.4.4.v20170414 | ${jetty.base}/lib/jetty-servlet-9.4.4.v20170414.jar
13:          9.4.4.v20170414 | ${jetty.base}/lib/jetty-webapp-9.4.4.v20170414.jar
14:          9.4.4.v20170414 | ${jetty.base}/lib/jetty-plus-9.4.4.v20170414.jar
15:          9.4.4.v20170414 | ${jetty.base}/lib/jetty-annotations-9.4.4.v20170414.jar
16:                      5.1 | ${jetty.base}/lib/annotations/asm-5.1.jar
17:                      5.1 | ${jetty.base}/lib/annotations/asm-commons-5.1.jar
18:                      1.2 | ${jetty.base}/lib/annotations/javax.annotation-api-1.2.jar
19:    3.10.2.v20150120-1634 | ${jetty.base}/lib/apache-jsp/org.eclipse.jdt.core.compiler.ecj-4.4.2.jar
20:          9.4.4.v20170414 | ${jetty.base}/lib/apache-jsp/org.eclipse.jetty.apache-jsp-9.4.4.v20170414.jar
21:                   8.0.33 | ${jetty.base}/lib/apache-jsp/org.mortbay.jasper.apache-el-8.5.9.1.jar
22:                      2.3 | ${jetty.base}/lib/apache-jsp/org.mortbay.jasper.apache-jsp-8.5.9.1.jar
23:                    1.2.5 | ${jetty.base}/lib/apache-jstl/org.apache.taglibs.taglibs-standard-impl-1.2.5.jar
24:                    1.2.5 | ${jetty.base}/lib/apache-jstl/org.apache.taglibs.taglibs-standard-spec-1.2.5.jar
25:          9.4.4.v20170414 | ${jetty.base}/lib/jetty-client-9.4.4.v20170414.jar
26:          9.4.4.v20170414 | ${jetty.base}/lib/jetty-deploy-9.4.4.v20170414.jar
27:                      1.0 | ${jetty.base}/lib/websocket/javax.websocket-api-1.0.jar
28:          9.4.4.v20170414 | ${jetty.base}/lib/websocket/javax-websocket-client-impl-9.4.4.v20170414.jar
29:          9.4.4.v20170414 | ${jetty.base}/lib/websocket/javax-websocket-server-impl-9.4.4.v20170414.jar
30:          9.4.4.v20170414 | ${jetty.base}/lib/websocket/websocket-api-9.4.4.v20170414.jar
31:          9.4.4.v20170414 | ${jetty.base}/lib/websocket/websocket-client-9.4.4.v20170414.jar
32:          9.4.4.v20170414 | ${jetty.base}/lib/websocket/websocket-common-9.4.4.v20170414.jar
33:          9.4.4.v20170414 | ${jetty.base}/lib/websocket/websocket-server-9.4.4.v20170414.jar
34:          9.4.4.v20170414 | ${jetty.base}/lib/websocket/websocket-servlet-9.4.4.v20170414.jar

Jetty Active XMLs:
------------------
 ${jetty.base}/etc/jetty.xml
 ${jetty.base}/etc/jetty-webapp.xml
 ${jetty.base}/etc/jetty-plus.xml
 ${jetty.base}/etc/jetty-annotations.xml
 ${jetty.base}/etc/jetty-deploy.xml
 ${jetty.base}/etc/home-base-warning.xml
 ${jetty.base}/etc/jetty-http.xml


On Thu, May 18, 2017 at 10:40 PM, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
You just upgraded 2 major versions.

Reminder: Jetty Versioning is <servlet_support>.<major>.<minor> 

You went from Jetty 9.2.x which was Servlet 3.1, Java 7, NPN and SPDY (48 modules available) ..
To Jetty 9.3.x which has Servlet 3.1, a Java 8 minimum, dropped NPN and SPDY, added ALPN and HTTP/2 ..
To Jetty 9.4.x which is Servlet 3.1, Java 8 minimum, a proposed Servlet 4.x API for HTTP/2, new Threading layer, new WebSocket integration with Jetty HttpClient, (113 modules available).

There's bound to be a few hiccups in your upgrade.

In 9.2.x you had ...

 Modules: http, or https, or spdy.
 Property: https.port=8443

In 9.4.x you have ...

 Modules: http (connector), or ssl (connector, which is ssl/tls, then alpn protocol layering/fallback within it for http/2, https, http-forwarded, etc).
 Property: jetty.ssl.port=8443

The introduction of HTTP/2 support made things more complicated here.

Before we go and suggest that you change things, can you run this command in both versions ...

$ cd /path/to/mybase && java -jar /path/to/jetty-dist/start.jar --list-config

That should list the identified configuration for each of your environments.
If we can see that we can help you identify where things went awry.

NOTE: Please be careful to not copy/paste sensitive information to the mailing list.


Joakim Erdfelt / joakim@xxxxxxxxxxx

On Thu, May 18, 2017 at 1:21 PM, Ganime Betül AKIN <ganime@xxxxxxxxx> wrote:
Hi all,

I have a  test where I am running two instances of an application bundled with jetty  on two different ports on the same machine (local). Before the upgrade, with 9.2.x all I had to do was to edit the start.d/https.ini file and change the port value for the second instance (by default the application uses a port which is different from 8080 and the first instance starts with this port.). The application was recently upgraded to use Jetty 9.4.x and now the second jetty instance start will be attempted on the default port, seemingly ignoring the modified port value in the https.ini. Of course this fails because that port is already in use.

Can someone provide insight on how to resolve this?

Thanks
Ganime

_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users


_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users


_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users


_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users


Back to the top