Re: [jetty-users] Jetty 9.1.5.v20140505 Released!
Dear Jesse, could you check the Distribution Downloads, it still has 9.1.4, no 9.1.5. Thanks On 5 May 2014 23:30, Jesse McConnell jesse.mcconn...@gmail.com wrote: We are pleased to announce the availability of Jetty 9.1.5! Close to 20 issues have been resolved in this release and we encourage folks to update soon. The issues resolved are listed below. Distribution Downloads: - http://download.eclipse.org/jetty/ The artifacts are also available in Maven Central. P2 repositories are available as well (shortly). If you find an issue with this release you can open a bug through the guided bugzilla page located here: - https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Jettyformat=guided A reminder that both dev and prod support are offered through Webtide (www.webtide.com), feel free to contact us through that site or ping me directly if you are interested in learning more. cheers, jesse jetty-9.1.5.v20140505 - 05 May 2014 + 431459 Jetty WebSocket compression extensions fails to handle big messages properly + 431519 Fixed NetworkTrafficListener + 432145 Pending request is not failed when HttpClient is stopped. + 432270 Slow requests with response content delimited by EOF fail. + 432473 web.xml declaration order of filters not preserved on calls to init() + 432483 make osgi.serviceloader support for javax.servlet.ServletContainerInitializer optional (cherry picked from commit 31043d25708edbea9ef31948093f4eaf2247919b) + 432528 IllegalStateException when using DeferredContentProvider. + 432777 Async Write Loses Data with HTTPS Server. + 432901 ensure a single onError callback only in pending and unready states + 432993 Improve handling of ProxyTo and Prefix parameters in ProxyServlet.Transparent. + 433365 No such servlet: __org.eclipse.jetty.servlet.JspPropertyGroupServlet__ (cherry picked from commit e2ed934978b958d6fccb28a8a5d04768f7c0432d) + 433370 PATCH method does not work with ProxyServlet. + 433483 sync log initialize + 433692 improved buffer resizing + 433916 HttpChannelOverHttp handles HTTP 1.0 connection reuse incorrectly. + 434027 ReadListener.onError() not invoked in case of read failures. -- jesse mcconnell jesse.mcconn...@gmail.com ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users
Re: [jetty-users] Jetty 9.1.5.v20140505 Released!
Sorry, I see it just few lines below. But wonder why is it not Stable? On 6 May 2014 09:36, Peter Ondruška peter.ondruska+je...@kaibo.eu wrote: Dear Jesse, could you check the Distribution Downloads, it still has 9.1.4, no 9.1.5. Thanks On 5 May 2014 23:30, Jesse McConnell jesse.mcconn...@gmail.com wrote: We are pleased to announce the availability of Jetty 9.1.5! Close to 20 issues have been resolved in this release and we encourage folks to update soon. The issues resolved are listed below. Distribution Downloads: - http://download.eclipse.org/jetty/ The artifacts are also available in Maven Central. P2 repositories are available as well (shortly). If you find an issue with this release you can open a bug through the guided bugzilla page located here: - https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Jettyformat=guided A reminder that both dev and prod support are offered through Webtide (www.webtide.com), feel free to contact us through that site or ping me directly if you are interested in learning more. cheers, jesse jetty-9.1.5.v20140505 - 05 May 2014 + 431459 Jetty WebSocket compression extensions fails to handle big messages properly + 431519 Fixed NetworkTrafficListener + 432145 Pending request is not failed when HttpClient is stopped. + 432270 Slow requests with response content delimited by EOF fail. + 432473 web.xml declaration order of filters not preserved on calls to init() + 432483 make osgi.serviceloader support for javax.servlet.ServletContainerInitializer optional (cherry picked from commit 31043d25708edbea9ef31948093f4eaf2247919b) + 432528 IllegalStateException when using DeferredContentProvider. + 432777 Async Write Loses Data with HTTPS Server. + 432901 ensure a single onError callback only in pending and unready states + 432993 Improve handling of ProxyTo and Prefix parameters in ProxyServlet.Transparent. + 433365 No such servlet: __org.eclipse.jetty.servlet.JspPropertyGroupServlet__ (cherry picked from commit e2ed934978b958d6fccb28a8a5d04768f7c0432d) + 433370 PATCH method does not work with ProxyServlet. + 433483 sync log initialize + 433692 improved buffer resizing + 433916 HttpChannelOverHttp handles HTTP 1.0 connection reuse incorrectly. + 434027 ReadListener.onError() not invoked in case of read failures. -- jesse mcconnell jesse.mcconn...@gmail.com ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users
Re: [jetty-users] Jetty 9.1.5.v20140505 Released!
Ooops, fixed now. thanks Jan On 6 May 2014 17:37, Peter Ondruška peter.ondruska+je...@kaibo.eu wrote: Sorry, I see it just few lines below. But wonder why is it not Stable? On 6 May 2014 09:36, Peter Ondruška peter.ondruska+je...@kaibo.eu wrote: Dear Jesse, could you check the Distribution Downloads, it still has 9.1.4, no 9.1.5. Thanks On 5 May 2014 23:30, Jesse McConnell jesse.mcconn...@gmail.com wrote: We are pleased to announce the availability of Jetty 9.1.5! Close to 20 issues have been resolved in this release and we encourage folks to update soon. The issues resolved are listed below. Distribution Downloads: - http://download.eclipse.org/jetty/ The artifacts are also available in Maven Central. P2 repositories are available as well (shortly). If you find an issue with this release you can open a bug through the guided bugzilla page located here: - https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Jettyformat=guided A reminder that both dev and prod support are offered through Webtide (www.webtide.com), feel free to contact us through that site or ping me directly if you are interested in learning more. cheers, jesse jetty-9.1.5.v20140505 - 05 May 2014 + 431459 Jetty WebSocket compression extensions fails to handle big messages properly + 431519 Fixed NetworkTrafficListener + 432145 Pending request is not failed when HttpClient is stopped. + 432270 Slow requests with response content delimited by EOF fail. + 432473 web.xml declaration order of filters not preserved on calls to init() + 432483 make osgi.serviceloader support for javax.servlet.ServletContainerInitializer optional (cherry picked from commit 31043d25708edbea9ef31948093f4eaf2247919b) + 432528 IllegalStateException when using DeferredContentProvider. + 432777 Async Write Loses Data with HTTPS Server. + 432901 ensure a single onError callback only in pending and unready states + 432993 Improve handling of ProxyTo and Prefix parameters in ProxyServlet.Transparent. + 433365 No such servlet: __org.eclipse.jetty.servlet.JspPropertyGroupServlet__ (cherry picked from commit e2ed934978b958d6fccb28a8a5d04768f7c0432d) + 433370 PATCH method does not work with ProxyServlet. + 433483 sync log initialize + 433692 improved buffer resizing + 433916 HttpChannelOverHttp handles HTTP 1.0 connection reuse incorrectly. + 434027 ReadListener.onError() not invoked in case of read failures. -- jesse mcconnell jesse.mcconn...@gmail.com ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users -- Jan Bartel j...@intalio.com www.webtide.com 'Expert Jetty/CometD developer,production,operations advice' ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users
[jetty-users] Migrating Jetty 8 to 9: No contexts
I first posted this to Stack Overflow and didn't get any answers; hoping to get unstuck here. We have a working Jetty 8 environment (and the person who set it up is gone). I'm trying to get our applications running in a test Jetty 9. Jetty starts up and writes to start.log, which informs me that stderr/stdout are being redirected to /opt/jetty/logs/2014_04_17.stderrout.log. The latter file reports: 2014-04-17 13:58:37.437:WARN:oejuc.AbstractLifeCycle:main: FAILED org.eclipse.jetty.deploy.DeploymentManager@7cddffbd: java.lang.IllegalStateException: No Contexts java.lang.IllegalStateException: No Contexts at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:221) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:125) ... The old installation put context deployment descriptor files in /opt/jetty/contexts. The documentation for Jetty 9 appears to say they should go in /opt/jetty/webapps. $JETTY_HOME in my environment is /opt/jetty. I copied one of the deployment descriptor files to webapps, but the error message is the same. There's nothing to tell me where it's looking or why it failed. I put a deliberate XML error into the deployment descriptor file to see if that would affect anything, but it didn't, so Jetty may not even be reading the file. I'm running the Jetty launch script in debug mode, and echoing the command which launches it to the console (changing -b to -v to get more useful output), and here's the full output to the console: Reading /etc/default/jetty.. START_INI = /opt/jetty/start.ini JETTY_HOME = /opt/jetty JETTY_BASE = /opt/jetty JETTY_CONF = /opt/jetty/etc/jetty.conf JETTY_PID = /var/run/jetty.pid JETTY_START= /opt/jetty/start.jar JETTY_ARGS = jetty-logging.xml jetty-started.xml JAVA_OPTIONS = -Djetty.state=/opt/jetty/jetty.state -Djetty.logs=/opt/jetty/logs -Djetty.home=/opt/jetty -Djetty.base=/opt/jetty -Djava.io.tmpdir=/tmp JAVA = /usr/bin/java RUN_CMD= /usr/bin/java Starting Jetty: start-stop-daemon -S -p/var/run/jetty.pid -cjetty -d/opt/jetty -v -m -a /usr/bin/java -- -Djetty.state=/opt/jetty/jetty.state -Djetty.logs=/opt/jetty/logs -Djetty.home=/opt/jetty -Djetty.base=/opt/jetty -Djava.io.tmpdir=/tmp -jar /opt/jetty/start.jar jetty-logging.xml jetty-started.xml start-log-file=start.log Starting /usr/bin/java... Logging to /opt/jetty/start.log FAILED Thu Apr 17 13:58:41 EDT 2014 Anyone have any ideas on what I'm doing wrong? -- Gary McGath, Principal Software Engineer, Outcome Referrals gmcg...@outcomereferrals.com ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users
Re: [jetty-users] 9.1.4 release and --daemon option
Hi, Joakim,
Just wanted to follow up on this. I'm using the jetty.sh script and was
thinking perhaps it's using the full path to the logs directory when it
should be using a relative path? I'm not seeing this behavior with 9.1.3
and am consistently afterwards so curious what changed.
Thanks,
Rob
On Mon, Apr 7, 2014 at 4:21 PM, Rob Moore rob.mo...@gmail.com wrote:
Thanks again, Joakim.
BTW, the issue I was seeing had to do with the new requestlog.filename
configuration. I was using requestlog.filename=request.log and saw this
error:
2014-04-07 20:57:03.258:INFO:oejs.Server:main: jetty-9.1.4.v20140401
2014-04-07 20:57:03.353:WARN:oejuc.AbstractLifeCycle:main: FAILED
org.eclipse.jetty.server.AsyncNCSARequestLog@60e07ad7:
java.io.IOException: Cannot write log directory /opt
java.io.IOException: Cannot write log directory /opt
at
org.eclipse.jetty.util.RolloverFileOutputStream.setFile(RolloverFileOutputStream.java:219)
I'm puzzled as to why it is trying to write to /opt as that's not the
jetty base dir.
I tried changing the value to logs/requestlog.conf assuming that it would
a relative path and that didn't work (it results in
/opt/jettylogs/request.log) so I added the forward slash to the beginning
of it and voila it worked.
On Mon, Apr 7, 2014 at 2:02 PM, Joakim Erdfelt joa...@intalio.com wrote:
Current design for start.log is that it is always relative to
${jetty.base}/${JETTY_LOGS}/start.log
The origin for that decision has been lost in the sands of time.
(In other words, I can't justify that decision).
So I filed a bug for it:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=432192
--
Joakim Erdfelt joa...@intalio.com
webtide.com http://www.webtide.com/ - intalio.com/jetty
Expert advice, services and support from from the Jetty CometD experts
eclipse.org/jetty - cometd.org
On Mon, Apr 7, 2014 at 11:44 AM, Rob Moore rob.mo...@gmail.com wrote:
Indeed, it is complaining about being able to write to the log directory
in the start.log.
I've added the start-log-file=logs/start.log as you suggested and I find
this in the logs:
java.io.IOException: Cannot write start.log to directory
/opt/jetty-distribution-9.1.4.v20140401/opt/jetty-distribution-9.1.4.v20140401/logs
[directory doesn't exist or is read-only]
Note the duplicate jetty home defined in the path.
I ran jetty.sh check and see the following for JETTY_LOGS
JETTY_LOGS = /opt/jetty-distribution-9.1.4.v20140401/logs
What's odd is that the start.log is created in the logs directory even
though jetty complains it can't write it there.
Rob
___
jetty-users mailing list
jetty-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/jetty-users
___
jetty-users mailing list
jetty-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/jetty-users
Re: [jetty-users] Migrating Jetty 8 to 9: No contexts
Some tips ...
From:
http://www.eclipse.org/jetty/documentation/current/configuring-specific-webapp-deployment.html
Your XML context files should be in the ${jetty.base}/webapps/ directory.
(It appears you are still on the old-school method of modifying
${jetty.home}, might want to read up on the jetty.home vs jetty.base
splithttp://www.eclipse.org/jetty/documentation/current/startup.html,
it will make your life easier in the long run)
There were some fundamental behavioral nuances in the split between
/contexts/ and /webapps/ that confused many people, and resulted in
duplicate deployments of the same webapp in an overwhelming number of
cases, the 2 separate directories were merged together with some basic
basename logic to minimize the dual deployment issues that many had.
The XML file format has changed slightly (mainly just a new DTD reference
that *must* be updated), be sure you update your XML files.
If you have your *.war (or webapp directory) in the ${jetty.base}/webapps/
directory too, then make sure your XML file and the basename of the webapp
is the same (otherwise you'll have double deployment).
Said another way...
if you have in ${jetty.base}/webapps/
search.war -- this is ignored, because search.xml exists)
search.xml -- this is used
admin.xml -- this is used
webadmin.war -- this is deployed as the /webadmin context path
(even if admin.xml references it)
mystatic/-- no WEB-INF/web.xml in here? then its a deployment of
static content to the /mystatic context path
Note: if you are using xml deployment descriptors, then you don't need to
have the war file in ${jetty.base}/webapps/ too.
To see what was actually deployed, set jetty.dump.start=true in your
${jetty.base}/start.ini and check your logging output, it will include the
server state tree (including all handlers + webapps).
--
Joakim Erdfelt joa...@intalio.com
webtide.com http://www.webtide.com/ - intalio.com/jetty
Expert advice, services and support from from the Jetty CometD experts
eclipse.org/jetty - cometd.org
On Tue, May 6, 2014 at 12:39 PM, Gary McGath
gmcg...@outcomereferrals.comwrote:
I first posted this to Stack Overflow and didn't get any answers; hoping
to get unstuck here.
We have a working Jetty 8 environment (and the person who set it up is
gone). I'm trying to get our applications running in a test Jetty 9. Jetty
starts up and writes to start.log, which informs me that stderr/stdout are
being redirected to
/opt/jetty/logs/2014_04_17.stderrout.log. The latter file reports:
2014-04-17 13:58:37.437:WARN:oejuc.AbstractLifeCycle:main: FAILED
org.eclipse.jetty.deploy.DeploymentManager@7cddffbd:
java.lang.IllegalStateException:
No Contexts
java.lang.IllegalStateException: No Contexts
at org.eclipse.jetty.deploy.DeploymentManager.doStart(
DeploymentManager.java:221)
at org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.
start(ContainerLifeCycle.java:125)
...
The old installation put context deployment descriptor files in
/opt/jetty/contexts. The documentation for Jetty 9 appears to say they
should go in /opt/jetty/webapps. $JETTY_HOME in my environment is
/opt/jetty. I copied one of the deployment descriptor files to webapps, but
the error message is the same. There's nothing to tell me where it's
looking or why it failed.
I put a deliberate XML error into the deployment descriptor file to see if
that would affect anything, but it didn't, so Jetty may not even be reading
the file.
I'm running the Jetty launch script in debug mode, and echoing the command
which launches it to the console (changing -b to -v to get more useful
output), and here's the full output to the console:
Reading /etc/default/jetty..
START_INI = /opt/jetty/start.ini
JETTY_HOME = /opt/jetty
JETTY_BASE = /opt/jetty
JETTY_CONF = /opt/jetty/etc/jetty.conf
JETTY_PID = /var/run/jetty.pid
JETTY_START= /opt/jetty/start.jar
JETTY_ARGS = jetty-logging.xml jetty-started.xml
JAVA_OPTIONS = -Djetty.state=/opt/jetty/jetty.state
-Djetty.logs=/opt/jetty/logs -Djetty.home=/opt/jetty
-Djetty.base=/opt/jetty -Djava.io.tmpdir=/tmp
JAVA = /usr/bin/java
RUN_CMD= /usr/bin/java
Starting Jetty: start-stop-daemon -S -p/var/run/jetty.pid -cjetty
-d/opt/jetty -v -m -a /usr/bin/java -- -Djetty.state=/opt/jetty/jetty.state
-Djetty.logs=/opt/jetty/logs -Djetty.home=/opt/jetty
-Djetty.base=/opt/jetty -Djava.io.tmpdir=/tmp -jar /opt/jetty/start.jar
jetty-logging.xml jetty-started.xml start-log-file=start.log
Starting /usr/bin/java...
Logging to /opt/jetty/start.log
FAILED Thu Apr 17 13:58:41 EDT 2014
Anyone have any ideas on what I'm doing wrong?
--
Gary McGath, Principal Software Engineer, Outcome Referrals
gmcg...@outcomereferrals.com
___
jetty-users
[jetty-users] Passing parameters using httpCLient
Hi, I am using jetty9 and running into issues while passing parameters using POST - My service exposes multiple operations - op1(param1,param2) op2(param1,param2) I want to invoke op1(param1,param2) using jetty's httpClient and both parameters are not strings. HttpClient client = new HttpClient(); client.start(); ContentResponse response = httpClient.POST(http://www.example.com/myService;); reponse.Param() accepts only String pairs. How do I specify - 1. Method I want to call as op1 2. Pass in two params, param1 and param2 that are not strings Please help! Thanks! ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users
