http://permalink.gmane.org/gmane.comp.java.jetty.support hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.java.jetty.support/15215 <pre>I'm using embedded Jetty to deploy several war files and would like some advice on how to make it run under SSL. (I've bought a CERT from a CA and now need to figure out how to use it for the login and admin war files. Here are may war files and how I would like to use them. MainPage.war accessed as: http://mydomain.com/ (port 80 not SSL) Login.war accessed as: https://mydomain.com/login (port 443 + SSL) Admin.war accessed as: https://mydomain.com/admin (port 443 + SSL) Currently I do something like (greatly simplified to make shorter here) //--- Start Code ---// Server = new Server(80); List&lt;Handler&gt; hList = new ArrayList&lt;Handler&gt;(); hList.add( new WebAppContext("../webapps/MainPage.war","/") ); hList.add( new WebAppContext("../webapps/Login.war","/login") ); hList.add( new WebAppContext("../webapps/Admin.war","/admin") ); ContextHandlerCollection contexts = new ContextHandlerCollection(); contexts.setHandlers(ha</pre> Alan 2013-04-25T02:38:25 http://permalink.gmane.org/gmane.comp.java.jetty.support/15214 <pre>Hi, When I copied the jar file in /lib/ext I could not get the class loaded, I am using activiti worflow engine and the engine could not instantiate the class.. I do not have this problem if I deploy the jar in the web-inf/lib of the activiti war file. I had tried this is as a test but this is not a solution. I have tried another thing , adding a jetty-web.xml file in the jetty.home/etc folder but I'm not able to make it work. I'm wondering where to copy the jar file.. i have my jar file copied in jetty.home/lib/my/jar folder how do I specify that in the fragment below, can you help &lt;Configure class="org.eclipse.jetty.webapp.WebAppContext"&gt; .. &lt;Set name="extraClasspath&gt; ???????? &gt; -- View this message in context: http://jetty.4.x6.nabble.com/Jetty-webapps-external-jar-files-tp4960434p4960437.html Sent from the Jetty Support mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: htt</pre> johnrg 2013-04-24T14:18:59 http://permalink.gmane.org/gmane.comp.java.jetty.support/15213 <pre>John, If you want the external jars to behave as if they were in WEB-INF/lib, then you can specify them as extraClassPath using a context xml file. See this doco here: http://www.eclipse.org/jetty/documentation/current/jetty-classloading.html#adding-extra-classpaths If you want them to act as being on the container's classpath, then you were on the right track in putting them in lib/ext. If you say it "didn't work", please describe what you mean by that. Perhaps you meant that they contain annotations and they weren't scanned? In that case, read the following doc which describes how to ensure that jars that are on the containers classpath are scanned: http://www.eclipse.org/jetty/documentation/current/configuring-webapps.html#webapp-context-attributes Jan On 24 April 2013 07:24, johnrg &lt;lowdee2000&lt; at &gt;hotmail.com&gt; wrote: </pre> Jan Bartel 2013-04-24T05:22:40 http://permalink.gmane.org/gmane.comp.java.jetty.support/15212 <pre>Hi, I am new to jetty and I am using jetty version 9. I have an war file deployed to my app server. the web-inf/lib file has a few jar files but I need to deploy some other jar files that are not included in the web-inf/lib I tried to copy the jar file into jetty.home/lib/ext but this is not working. please let me know how to do this so that the application can load the class files. thanks John -- View this message in context: http://jetty.4.x6.nabble.com/Jetty-webapps-external-jar-files-tp4960434.html Sent from the Jetty Support mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> johnrg 2013-04-23T21:24:52 http://permalink.gmane.org/gmane.comp.java.jetty.support/15211 <pre>We are pleased to announce the release of Jetty 9.0.2. There were a couple of issues that we noted with the last release and wanted to get resolved quickly. The first was a fix to one of the new queue algorithms we have been working with that we realized was resulting in a bit of a hit to performance. The second was an issue where sockets would sometimes linger around after the connection was closed when a certain sequence of events occurred with SSL connection close. This issues didn't affect everyone but it was a bother enough to those it did that we included it in this release. Distribution Downloads: - http://download.eclipse.org/jetty/stable-9/dist/ The artifacts are also available in Maven Central. Documentation: - http://www.eclipse.org/jetty/documentation/current cheers, jesse jetty-9.0.2.v20130417 - 17 April 2013 + 364921 FIN WAIT sockets + 402885 reuse Deflaters in GzipFilter + 403591 do not use the ConcurrentArrayBlockingQueue for thread pool, selector and async request log + 404</pre> Jesse McConnell 2013-04-17T20:21:44 http://permalink.gmane.org/gmane.comp.java.jetty.support/15210 <pre>Unfortunately the change made for "404511 Replaced all StringMap usage with Tries" has introduced a garbage producing poor implementation of a common string lookup method. Thus 9.0.1 is not performing well in benchmarks due to frequent GCs. We will have a 9.0.2 out shortly with this fixed (fixed in HEAD already). On 11 April 2013 06:52, Jesse McConnell &lt;jesse&lt; at &gt;intalio.com&gt; wrote: </pre> Greg Wilkins 2013-04-11T05:33:44 http://permalink.gmane.org/gmane.comp.java.jetty.support/15209 <pre> I am out of the office until 15/04/2013. I will respond to your message as soon as possible. For urgent issues, contact WebSphere Support group for Java-WebSphere related activities or unix.admin group for Unix-WebSphere-Jetty related activities Note: This is an automated response to your message "[jetty-user] Jetty 9.0.1.v20130408 Released!" sent on 10/04/2013 22:52:03. This is the only notification you will receive while this person is away. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Walter.Heestermans< at >toyota-europe.com 2013-04-11T02:17:50 http://permalink.gmane.org/gmane.comp.java.jetty.support/15208 <pre>Oops, the issues resolved are here: jetty-9.0.1.v20130408 - 08 April 2013 + 384552 add comment to jetty-https.xml describing keymanager password + 385488 non existing resources in collection are just warnings + 392129 fixed merged of handling of timeouts after startAsync + 393971 Improve setParentLoaderPriorty javadoc + 393972 Improve WebAppContext classloading javadoc + 395620 do not managed inherited life cycle listeners + 396562 Add an implementation of RequestLog that supports Slf4j + 399967 Destroyables destroyed on undeploy and shutdown hook + 400142 ConcurrentModificationException in JDBC SessionManger + 400144 When loading a session fails the JDBCSessionManger produces duplicate session IDs + 400689 Add support for Proxy authentication. + 401150 close input stream used from cached resource + 401806 spdy push properly pass through request and response headers for pushed resources + 402397 InputStreamResponseListener early close inputStream cause hold lock. + 402485 reseed secure </pre> Jesse McConnell 2013-04-10T20:52:41 http://permalink.gmane.org/gmane.comp.java.jetty.support/15207 <pre>Hard to believe we released Jetty 9 a mere month ago but we have been busy resolving some small issues and added to the new documentation hub. If you haven't seen the new documentation take a look, and feel free to contribute through the github project that houses it. Distribution Downloads: - http://download.eclipse.org/jetty/stable-9/dist/ The artifacts are also available in Maven Central. Documentation: - http://www.eclipse.org/jetty/documentation/current I'll attach the resolves issues at the end of this mail, but we have been very happy with the response we have gotten from the Jetty 9 release and are looking forward to future versions. Just as bit of a note for those interested, we'll be releasing 9.1 once the servlet 3.1 spec has finalized and likely the JSR 356 Websocket api spec has released, hopefully these will wrap up around the same time. cheers, jesse -- Jesse McConnell &lt;jesse&lt; at &gt;intalio.com&gt; www.webtide.com – Developer advice, services and support from the Jetty &amp; CometD experts. </pre> Jesse McConnell 2013-04-10T20:52:03 http://permalink.gmane.org/gmane.comp.java.jetty.support/15206 <pre>I had this warning but turns out error wasn't related to that. When I switch to TRACE log I noticed I had an error about ssl handshake. In my case it's because I change my jre from 1.6 to 1.7 because of jetty 9. On 1.7 oracle is more strict about TLS handshake. Now that I solve this problem I still get this same warning but looks like everything works fine. -- View this message in context: http://jetty.4.n6.nabble.com/jetty-9-java-nio-channels-WritePendingException-on-WebSocket-connect-over-SSL-tp4960023p4960305.html Sent from the Jetty Support mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> ghetolay 2013-03-26T13:23:51 http://permalink.gmane.org/gmane.comp.java.jetty.support/15205 <pre>It should be noted that the arguments within the "start.ini" file override the command line arguments. This can catch you out if you are using the start.ini to provide arguments when starting a few instances and then try to stop one using the appropriate arguments via the command line. -- View this message in context: http://jetty.4.n6.nabble.com/Jetty-7-6-9-STOP-PORT-STOP-KEY-behavior-has-changed-tp4960180p4960270.html Sent from the Jetty Support mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> kevinc 2013-03-14T22:20:35 http://permalink.gmane.org/gmane.comp.java.jetty.support/15204 <pre>Joakim Erdfelt-9 wrote Thanks!, that works well for my use-case, and is a little cleaner than my previous method of parsing the generated value from the log file. -- View this message in context: http://jetty.4.n6.nabble.com/Jetty-7-6-9-STOP-PORT-STOP-KEY-behavior-has-changed-tp4960180p4960269.html Sent from the Jetty Support mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> kevinc 2013-03-14T21:28:02 http://permalink.gmane.org/gmane.comp.java.jetty.support/15203 <pre>You can put the STOP.KEY in the start.ini That way it is not present on the command line. -- Joakim Erdfelt &lt;joakim&lt; at &gt;intalio.com&gt; webtide.com &lt;http://www.webtide.com/&gt; Developer advice, services and support from the Jetty &amp; CometD experts eclipse.org/jetty - cometd.org On Thu, Mar 14, 2013 at 1:43 PM, kevinc &lt;kevin&lt; at &gt;coretech.co.nz&gt; wrote: </pre> Joakim Erdfelt 2013-03-14T21:04:27 http://permalink.gmane.org/gmane.comp.java.jetty.support/15202 <pre>Just verified that this is still the case for Jetty 7.6.10. Is there another way of configuring the STOP.KEY such that it is not visible to all other users on the system? Or is the only option to stick with the 7.6.8 release? -- View this message in context: http://jetty.4.n6.nabble.com/Jetty-7-6-9-STOP-PORT-STOP-KEY-behavior-has-changed-tp4960180p4960267.html Sent from the Jetty Support mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> kevinc 2013-03-14T20:43:15 http://permalink.gmane.org/gmane.comp.java.jetty.support/15201 <pre>Hot on the heels of our Jetty 9 release, we have released updates to our two mature versions. We will continue releasing updates to 7 and 8, roughly every couple of months for the foreseeable future. Downloads: http://download.eclipse.org/jetty/ Releases are available in Maven Central as well. cheers, jesse The list of changes are: jetty-7.6.10.v20130312 - 12 March 2013 + 376273 Early EOF because of SSL Protocol Error on https://api-3t.paypal.com/nvp. + 381521 allow compress methods to be configured + 394064 ensure that JarFile instances are closed on JarFileResource.release() + 398649 ServletContextListener.contextDestroyed() is not called on ContextHandler unregistration + 399703 made encoding error handling consistent + 399799 do not hold lock while calling invalidation listeners + 399967 Shutdown hook calls destroy + 400040 NullPointerException in HttpGenerator.prepareBuffers + 400142 ConcurrentModificationException in JDBC SessionManger + 400144 When loading a session fails the JDB</pre> Jesse McConnell 2013-03-14T16:01:24 http://permalink.gmane.org/gmane.comp.java.jetty.support/15200 <pre>The issue with the STOP.KEY behaviour changing in 7.6.9 seems related to the following patch: *Bug 391623 - Add option to --stop to wait for target jetty to stop* Looking at the changes made within this commit it seems that the auto-generation of the STOP.KEY will never occur as it will always default to "eclipse" and never be assigned /null/. The diff can be found here (note the references to STOP.KEY/this.key): https://eclipse.googlesource.com/jetty/org.eclipse.jetty.project/+/b65973afdd280459b8762678d5c5341abf2680ca%5E!/#F0 -- View this message in context: http://jetty.4.n6.nabble.com/Jetty-7-6-9-STOP-PORT-STOP-KEY-behavior-has-changed-tp4960180p4960212.html Sent from the Jetty Support mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> kevinc 2013-03-10T20:40:31 http://permalink.gmane.org/gmane.comp.java.jetty.support/15199 <pre>The Eclipse Jetty Project team is proud to announce the first release of the new Jetty 9 *Jetty 9.0.0.v20130308* The Java Web Server with support for SPDY and WebSocket. *Distributions Downloads:* http://download.eclipse.org/jetty/stable-9/dist/ *Java Artifacts Available on Maven Central:* http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.eclipse.jetty%22%20AND%20v%3A%229.0.0..v20130308%22 &lt;groupId&gt;org.eclipse.jetty&lt;/groupId&gt; &lt;version&gt;9.0.0.v20130308&lt;/version&gt; *Jetty 9.x Features:* - Completely overhauled I/O layer - Servlet API 3.0 - JSP 2.2 - SPDY/3 - WebSocket (RFC-6455) *Notes for those migrating to Jetty 9.x:* - Requires Java 1.7 or newer. - Jetty Maven Plugin has now been moved to org.eclipse.jetty groupId - There is no org.mortbay or codehaus components - Support for early WebSocket drafts has been dropped, only support released RFC-6455 spec. - There now only 1 aggregate jar, called jetty-all. - Bad UTF8 encoding will result in replacement char</pre> Joakim Erdfelt 2013-03-09T00:33:25 http://permalink.gmane.org/gmane.comp.java.jetty.support/15198 <pre>The root of the problem was the chrome browser, which I use for testing. It doesn't create new one connection to the same URL =( -- View this message in context: http://jetty.4.n6.nabble.com/Async-Context-does-not-accept-simultaneous-requests-tp4960197p4960202.html Sent from the Jetty Support mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Valery Dubrava 2013-03-08T21:24:06 http://permalink.gmane.org/gmane.comp.java.jetty.support/15197 <pre>I've found something like workaround. I've added different queries to each test request and they had been handled in parallel. But why it is not work when I use exactly the same URL? It's a common case for me. -- View this message in context: http://jetty.4.n6.nabble.com/Async-Context-does-not-accept-simultaneous-requests-tp4960197p4960201.html Sent from the Jetty Support mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Valery Dubrava 2013-03-08T21:01:36 http://permalink.gmane.org/gmane.comp.java.jetty.support/15196 <pre>I tried to do it, but it is not a soluting. Nothing changes =( Thank you for ansewer in any case! -- View this message in context: http://jetty.4.n6.nabble.com/Async-Context-does-not-accept-simultaneous-requests-tp4960197p4960200.html Sent from the Jetty Support mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Valery Dubrava 2013-03-08T20:18:27 http://permalink.gmane.org/gmane.comp.java.jetty.support/15195 <pre> &lt;!-- Number of connection requests that can be queued up before the operating system starts to send rejections. --&gt; &lt;property name="acceptQueueSize" value="1" /&gt; Change that, bump it up to 20 or so. -- Joakim Erdfelt &lt;joakim&lt; at &gt;intalio.com&gt; webtide.com &lt;http://www.webtide.com/&gt; Developer advice, services and support from the Jetty &amp; CometD experts eclipse.org/jetty - cometd.org On Fri, Mar 8, 2013 at 12:20 PM, Valery Dubrava &lt;valery.dubrava&lt; at &gt;gmail.com&gt;wrote: </pre> Joakim Erdfelt 2013-03-08T19:41:13 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.java.jetty.support