Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to Jetty 9.4.14.v20181114 #15239

Closed
wilkinsona opened this issue Nov 22, 2018 · 4 comments
Closed

Upgrade to Jetty 9.4.14.v20181114 #15239

wilkinsona opened this issue Nov 22, 2018 · 4 comments
Assignees
Labels
type: dependency-upgrade A dependency upgrade
Milestone

Comments

@wilkinsona
Copy link
Member

No description provided.

@wilkinsona wilkinsona added this to the 1.5.18 milestone Nov 22, 2018
@wilkinsona wilkinsona added the type: dependency-upgrade A dependency upgrade label Nov 22, 2018
@wilkinsona
Copy link
Member Author

This appears to have caused 3 test failures. Re-opening.

@wilkinsona wilkinsona reopened this Nov 22, 2018
@wilkinsona wilkinsona self-assigned this Nov 22, 2018
@wilkinsona
Copy link
Member Author

When a connector cannot be started due to a port clash, the BindException is now nested beneath an IOException:

java.io.IOException: Failed to bind to /0.0.0.0:51789
	at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:346)
	at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:308)
	at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
	at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
	at org.springframework.boot.context.embedded.jetty.JettyEmbeddedServletContainer.start(JettyEmbeddedServletContainer.java:143)
	at org.springframework.boot.context.embedded.AbstractEmbeddedServletContainerFactoryTests$5.run(AbstractEmbeddedServletContainerFactoryTests.java:954)
	at org.springframework.boot.context.embedded.AbstractEmbeddedServletContainerFactoryTests.doWithBlockedPort(AbstractEmbeddedServletContainerFactoryTests.java:1263)
	at org.springframework.boot.context.embedded.AbstractEmbeddedServletContainerFactoryTests.portClashOfPrimaryConnectorResultsInPortInUseException(AbstractEmbeddedServletContainerFactoryTests.java:945)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.springframework.boot.testutil.InternalOutputCapture$1.evaluate(InternalOutputCapture.java:60)
	at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
	at org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
Caused by: java.net.BindException: Address already in use
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:433)
	at sun.nio.ch.Net.bind(Net.java:425)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
	at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:342)
	... 38 more

@wilkinsona
Copy link
Member Author

There's a regression in 9.4.14 that means that a programmatically registered ServletContextListener is no longer called. There's also a regression in 9.4.13 so I think we'll need to stay on 9.4.12 for now. I am going to revert the upgrade.

@wilkinsona wilkinsona removed this from the 1.5.18 milestone Nov 22, 2018
@wilkinsona wilkinsona added the status: declined A suggestion or change that we don't feel we should currently apply label Nov 22, 2018
wilkinsona added a commit that referenced this issue Nov 22, 2018
@wilkinsona
Copy link
Member Author

With thanks to @janbartel, we have an alternative approach to ServletContextListener registration that works with 9.4.14 and also works with older version of Jetty. We can do this upgrade now.

@wilkinsona wilkinsona reopened this Dec 12, 2018
@wilkinsona wilkinsona removed the status: declined A suggestion or change that we don't feel we should currently apply label Dec 12, 2018
@wilkinsona wilkinsona added this to the 1.5.x milestone Dec 12, 2018
@snicoll snicoll modified the milestones: 1.5.x, 1.5.19 Jan 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: dependency-upgrade A dependency upgrade
Projects
None yet
Development

No branches or pull requests

2 participants