Nabble - Jetty Support

Jars needed for Jetty7 embed

2009-10-19T03:11:56Z

Hi,

I'm looking to upgrade to v7.

However, with the package restructuring et all, the jars have changed. I see util, but it is not abundantly clear which jars make up the previous main jetty jar of 6 (e.g. jetty-6.1.6.jar @ size of 483 kb)

Could someone pls advise on the jars needed? It would also be great if the eclipse doc could be updated for others: http://wiki.eclipse.org/Jetty/Tutorial/Embedding_Jetty

Cheers

Jetty/5.1.12 - Configuring realm for CGI-BIN

2009-10-10T12:10:43Z

Hello, I wonder if someone can provide me with some help with configuring a realm with a CGI-BIN context for Jetty 5.1.12:

A context for cgi-bin has been "configured", but is not picking up the default realm (please see below for configuration). Can someone please tell me what is wrong with the configuration.

thanks

Miles.

<?xml version="1.0" encoding="ISO-8859-1"?>

<web-app xmlns="http://java.sun.com/xml/ns/j2ee"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"

version="2.4">

.......

<security-constraint>

<web-resource-collection>

<web-resource-name>SDP Listbox Editor</web-resource-name>

<url-pattern>/*</url-pattern>

</web-resource-collection>

<auth-constraint>

<role-name>user</role-name>

</auth-constraint>

</security-constraint>

<login-config>

<auth-method>BASIC</auth-method>

<realm-name>defaultrealm</realm-name>

</login-config>

<security-role>

<role-name>user</role-name>

</security-role>

</web-app>

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure 1.2//EN" "http://jetty.mortbay.org/configure_1_2.dtd">

<Configure class="org.mortbay.jetty.Server">

.......

<Call name="addContext">

<Arg>/cgi-bin/*</Arg>

<Set name="ResourceBase"><SystemProperty name="jetty.home" default="."/>/cgi-bin/</Set>

<Call name="addServlet">

<Arg>Common Gateway Interface</Arg>

<Arg>/</Arg>

<Arg>org.mortbay.servlet.CGI</Arg>

<Put name="Path">/usr/local/bin:/usr/ucb:/bin:/usr/bin</Put>

</Call>

</Call>

<Call name="addRealm">

<Arg>

<New class="org.mortbay.http.HashUserRealm">

<Set name="name">defaultrealm</Set>

<Call name="load">

<Arg>/opt/product/changesynergy/tc47_sdp/cs_app/etc/realm.properties</Arg>

</Call>

</New>

</Arg>

</Call>

</Configure>

Jetty7 HttpClient POST problem

2009-10-09T13:31:05Z

Hello,

I am having some problems crafting and sending a POST to a server via the HttpClient. I have the Client set up as per the tutorial (http://wiki.eclipse.org/Jetty/Tutorial/HttpClient). One thing is not clear. How does one set the parameters for the post? I am trying to implement a login for an application such that the application can use the same server side script to login as a web client.

I have tried setting the parameters through a call to setRequestContent() to no avail

AbstractBuffer content = new ByteArrayBuffer("uname=user&pwd=password".getBytes("UTF-8"));
exchange.setRequestContent(content);

is that the correct way to send POST parameters? The server side script does not find any parameters.

Thanks for any help.

-chazzs

[Jetty-announce] Jetty 7.0.0 release

2009-10-07T19:26:14Z

All,

We are really please to announce the release of jetty 7.0.0 from eclipse
and jetty hightide 7.0.0 from codehaus.

Jetty 7 is an evolution of jetty-6, that contains a significant
reorganization of the packaging and jars, as well as many fundamental
improvements in the underlying infrastructure of jetty.

Key highlights of Jetty-7 include:

+ Servlet 2.5 container, with underlying access to servlet 3.0
features such as fragments.
+ Full Java 1.5 support.
+ Improved Continuations to support jetty-6, jetty-7 and servlet-3.0 async
+ JASPI for pluggable standard authentication modules
+ Improved OSGi integration
+ Ongoing optimizations and performance improvements
+ Modular start.jar mechanism

The jetty-distribution is available via http://eclipse.org/jetty
under the terms of the apache 2.0 or eclipse 1.0 licenses. It is
covered by the terms of the Eclipse Foundation Software User Agreement.
The distribution contains the core functionality of HTTP server, servlet
container and HTTP client.

The jetty-hightide is an alternate distribution of jetty
available via http://jetty.codehaus.org. Hightide is
to jetty as ubuntu is to linux. It is fully open source
and contains additional modules and integrations:
+ JSP from glassfish
+ JTA from atomikos
+ maven plugin
+ ant integration
+ setuid
+ spring configuration

Both distributions are available via maven as artefacts
or complete bundles

http://repo1.maven.org/maven2/org/eclipse/jetty/
http://repo1.maven.org/maven2/org/mortbay/jetty/

Jetty 6 will continue to be maintained for some time, but
all new features will now be developed on Jetty-7.
Jetty-8 will be in prelease in the next few months and
will support servlet 3.0

Thanks to all that have contributed code, testing, bug
reports, ideas or otherwise.

cheers

VERSION.txt:

jetty-7.0.0.v20091005 5 October 2009
291340 Race condition in onException() notifications

jetty@codehaus 7.0.0.v20091005 5 October 2009
+ JETTY-1021 jetty-maven-plugin overlay or reload issue
+ JETTY-1089 Upgrade jsp to SJSAS-9_1_1-B60F-07_Jan_2009
+ JETTY-1100 extend setuid feature to set number of open file descriptors
+ JETTY-1109 Improper handling of cookies in Terracotta tests
+ JETTY-1115 Allow configuration of location of web.xml for jetty-jspc-maven-plugin
+ Patch test context to deploy at /test for jetty-hightide
+ Moved example-jetty-spring to jetty-spring
+ Include jetty-jspc-maven-plugin
+ Fix jetty/jboss security integration
+ Remove printlns
+ Exclude setuid from hightide when building on windows

jetty-7.0.0.RC6 September 21 2009
+ Fixed XSS issue in CookieDump demo servlet.
+ 289958 StatisticsServlet incorrectly adds StatisticsHandler
+ 289960 start.jar assumes command line args are configs
+ 290081 Eager consume LF after CR
+ 290761 HttpExchange isDone handles intercepted events.
+ JETTY-719 Document state machine of jetty http client
+ JETTY-780 CNFE during startup of webapp with spring-context >= 2.5.1
+ JETTY-936 274251 Improved servlet matching and optimized'
+ JETTY-1080 modify previous fix to work on windows
+ JETTY-1084 HEAD command not setting content-type in response under certain circumstances
+ JETTY-1086 Use UncheckedPrintWriter & cleaned up HttpStatus.Code usage
+ JETTY-1090 resolve potential infinite loop with webdav listener
+ JETTY-1092 MultiPartFilter can be pushed into infinite loop
+ JETTY-1093 Request.toString throws exception when size exceeds 4k
+ JETTY-1098 Default form encoding is UTF8
+ JETTY-1101 Updated servlet3 continuation constructor
+ JETTY-1105 Custom error pages aren't working
+ JETTY-1108 SSL EOF detection
+ JETTY-1112 Response fails if header exceeds buffer size
+ JETTY-1113 IllegalStateException when adding servlet filters programmatically
+ 280723 Add non blocking statistics handler
+ 282543 HttpClient SSL buffer size fix
+ 283357 org.eclipse.jetty.server.HttpConnectionTest exceptions
+ 288055 jetty-client fails to resolve failed resolution attempts correctly
+ 288153 jetty-client resend doesn't reset exchange
+ 288466 LocalConnector is not thread safe
+ 288514 AbstractConnector does not handle InterruptedExceptions on shutdown
+ 288772 Failure to connect does not set status to EXCEPTED
+ 289146 formalize reload policy functionality
+ 289156 jetty-client: no longer throw runtime exception for bad authn details
+ 288182 PUT request fails during retry
+ 289221 HttpExchange does not timeout when using blocking connector
+ 289285 org.eclipse.jetty.continuation 7.0.0.RC5 imports the org.mortbay.util.ajax package
+ 289686 HttpExchange.setStatus() has too coarse synchronization
+ Tweak DefaultServletTest under windows
+ Copy VERSION.txt to distro
+ Remove printlns from jetty-plus

jetty-7.0.0.RC5 27 August 2009
+ 286911 Clean out cache when recycling HTTP fields
+ JETTY-838 Don't log and throw
+ JETTY-874 Better header full warnings
+ JETTY-960 Support for ldaps
+ JETTY-1081 Handle null content type in GzipFilter
+ JETTY-1084 Disable GzipFilter for HEAD requests
+ JETTY-1085 Allow url sessionID if cookie invalid
+ JETTY-1086 Added UncheckedPrintWriter to avoid ignored EOFs
+ JETTY-1087 Chunked SSL non blocking input
+ 287496 Use start.ini always and added --exec
+ 287632 FilterContinuations for blocking jetty6

jetty-7.0.0.RC4 18 August 2009
+ 286185 Implement ability for JSON implementation to automatically register convertors
+ Added discoverable start options
+ 286535 ContentExchange status code
+ 285891 SessionAuthentication is serializable
+ JETTY-1079 ResourceCollection.toString
+ 279820 Fixed HotSwapHandler
+ JETTY-1080 Ignore files that would be extracted outside the destination directory when unpacking WARs
+ JETTY-1057 XSS error page

jetty-7.0.0.RC3 7 August 2009
+ 277403 remove system properties
+ JETTY-1074 JMX thread manipulation
+ Improved deferred authentication handling
+ 285697 extract parameters if dispatch has query
+ 282447 concurrent destinations in HttpClient
+ 283172 fix Windows build, broken on directory creation with the DefaultServlet
+ 283375 additional error-checking on SSL connector passwords to prevent NPE
+ 283513 Check endp.isOpen when blocking read

jetty-7.0.0.RC2 29 June 2009
+ 283844 Webapp / TLD errors are not clear
+ 283375 improved extensibility of SSL connectors
+ 283818 fixed merge of forward parameters
+ backport jetty-8 annotation parsing to jetty-7
+ Disassociate method on IdentityService
+ 284510 Enhance jetty-start for diagnosis and unit testing
+ 284475 update jetty.sh for new OPTIONS syntax
+ Added DebugHandler
+ Added JavaUtilLog for Jetty logging to java.util.logging framework
+ 284981 Implement a cross-origin filter
+ Improved handling of overlays and resourceCollections
+ 285006 fix AbstractConnector NPE during shutdown.

jetty-7.0.0.RC1 15 June 2009
+ JETTY-1066 283357 400 response for bad URIs
+ JETTY-1068 Avoid busy flush of async SSL
+ 283344 Startup on windows is broken

jetty-7.0.0.RC0 8 June 2009
+ JETTY-967 create standalone build for PKCS12Import at codehaus
+ JETTY-1056 update jetty-ant module for Jetty 7 at codehaus trunk
+ JETTY-1058 Handle trailing / with aliases
+ 280843 Buffer pool uses isHeader
+ 271535 Adding integration tests, and enabling RFC2616 tests
+ 281287 Handle date headers before 1 Jan 1970
+ 282807 Better handling of 100 continues if response committed.
+ 282807 283049 282543 Improved handling of timeouts and complete. More debug

jetty-7.0.0.M4 1 June 2009
+ 281059 NPE in QTP with debug on
+ JETTY-799 shell script for jetty on cygwin
+ JETTY-1031 Handle large pipeline
+ JETTY-1034 Cookie parsing
+ JETTY-1042 Prevent cookie leak between shared connection
+ JETTY-1048 Fix for large partially filtered static content
+ JETTY-1049 Improved transparent proxy usability
+ JETTY-1054 Avoid double deploys
+ JETTY-1055 Cookie quoting
+ JETTY-1057 Error page stack trace XSS

jetty-7.0.0.M3 20 June 2009
+ fixed race with expired async listeners
+ refactored configuration mechanism
+ added WebAppContext.setConfigurationDiscovered for servlet 3.0 features
+ 274251 Allow dispatch to welcome files that are servlets (configurable)
+ 277403 Cleanup system property usage.
+ 277798 Denial of Service Filter
+ Portable continuations for jetty6 and servlet3
+ Refactored continuations to only support response wrapping
+ Added ContinuationThrowable
+ 276545 Quoted cookie paths
+ 279725 Support 100 and 102 expectations
+ Refactored AbstractBuffers to HttpBuffers for performance
+ Numerous cleanups from static code analysis
+ 280707 client.HttpConnection does not catch and handle non-IOExceptions
+ 281470 Handle the case where request.PathInfo() should be "/*"

jetty-7.0.0.M2 18 May 2009
+ JETTY-937 Work around Sun JVM bugs
+ JETTY-941 Linux chkconfig hint
+ JETTY-959 CGI servlet doesn't kill the CGI in case the client disconnects
+ JETTY-980 Fixed ResourceHandler ? handling, and bad URI creation in listings
+ JETTY-996 Make start-stop-daemon optional
+ 273767 Update to use geronimo annotations spec 1.1.1
+ JETTY-1003 java.lang.IllegalArgumentException: timeout can't be negative
+ JETTY-1004 CERT VU#402580 Canonical path handling includes ? in path segment
+ JETTY-1013 MySql Error with JDBCUserRealm
+ JETTY-1014 Enable start-stop-daemon by default on jetty.sh (START_STOP_DAEMON=1)
+ JETTY-1015 Reduce BayeuxClient and HttpClient lock contention
+ JETTY-1020 ZipException in org.mortbay.jetty.webapp.TagLibConfiguration prevents all contexts from being loaded
+ 275396 Added ScopedHandler to set servlet scope before security handler
+ 275396 Added Authentication.Wrapped to allow JSAPI wrapping

jetty-7.0.0.M1 22 April 2009
+ 271258 FORM Authentication dispatch handling avoids caching
+ Initial support for LoginService.logout
+ Removed HTTPConnection specifics from connection dispatching
+ JETTY-695 Handler dump
+ Reworked authentication for deferred authentication
+ Reworked JMX for new layout
+ JETTY-983 DefaultServlet generates accept-ranges for cached/gzip content
+ 273011 JETTY-980 JETTY-992 Security / Directory Listing XSS present
+ 271536 Add support to IO for quietly closing Readers / Writers
+ 273101 Fix DefaultServletTest XSS test case
+ 273153 Test for Nested references in DispatchServlet

jetty-7.0.0.M0 27 March 2009
+ JETTY-496 Support inetd/xinetd through use of System.inheritedChannel()
+ JETTY-540 Merged 3.0 Public Review changes
+ JETTY-567 Delay in initial TLS Handshake With FireFox 3 beta5 and SslSelectChannelConnector
+ JETTY-600 Automated tests of WADI integration + upgrade to WADI 2.0
+ JETTY-691 System.getProperty() calls ... wrap them in doPrivileged
+ JETTY-713 Expose additional AbstractConnector methods via MBean
+ JETTY-731 Completed DeliverListener for cometd
+ JETTY-748 RandomAccessFileBuffer for hadoop optimization
+ JETTY-748 Reduced retries on async writes
+ JETTY-749 Improved ArrayQueue
+ JETTY-765 ensure stop mojo works for all execution phases
+ JETTY-774 Improved caching of mime types with charsets
+ JETTY-775 AbstractSessionTest remove timing related test
+ JETTY-778 handle granular windows timer in lifecycle test
+ JETTY-779 Fixed line feed in request log
+ JETTY-781 Add "mvn jetty:deploy-war" for deploying a pre-assembled war
+ JETTY-782 Implement interval advice for BayeuxClient
+ JETTY-783 Update jetty self-signed certificate
+ JETTY-784 TerracottaSessionManager leaks sessions scavenged in other nodes
+ JETTY-786 Allow DataSourceUserRealm to create tables
+ JETTY-787 Handle MSIE7 mixed encoding
+ JETTY-788 Fix jotm for scoped jndi naming
+ JETTY-790 WaitingContinuations can change mutex if not pending
+ JETTY-792 TerracottaSessionManager does not unlock new session with requested id
+ JETTY-793 Fixed DataCache millisecond rounding
+ JETTY-794 WADI integration tests fail intermittently.
+ JETTY-795 NullPointerException in SocketConnector.java
+ JETTY-801 Bring back 2 arg EnvEntry constructor
+ JETTY-802 Modify the default error pages to make association with Jetty clearer
+ JETTY-804 HttpClient timeout does not always work
+ JETTY-805 Fix jetty-jaas.xml for new UserRealm package
+ JETTY-806 Timeout related Deadlocks in HTTP Client
+ JETTY-807 HttpTester to handle charsets
+ JETTY-808 cometd client demo run.sh
+ JETTY-809 Need a way to customize WEB-INF/lib file extensions that are added to the classpath
+ JETTY-811 Allow configuration of system properties for the maven plugin using a file
+ JETTY-813 Simplify NCSARequestLog.java
+ JETTY-814 Add org.eclipse.jetty.client.Address.toString()
+ JETTY-816 Implement reconnect on java bayeux client
+ JETTY-817 Aborted SSL connections may cause jetty to hang with full cpu
+ JETTY-818 Support javax.servlet.request.ssl_session_id
+ JETTY-821 Allow lazy loading of persistent sessions
+ JETTY-822 Commit when autocommit=true causes error with mysql
+ JETTY-823 Extend start.config profiles
+ JETTY-824 Access to inbound byte statistics
+ JETTY-825 URL decoding of spaces (+) fails for encoding not utf8
+ JETTY-830 Add ability to reserve connections on http client
+ JETTY-831 Add ability to stop java bayeux client
+ JETTY-832 More UrlDecoded handling in relation to JETTY-825
+ JETTY-834 Configure DTD does not allow <Map> children
+ JETTY-837 Response headers set via filter are ignored for static resources
+ JETTY-840 add default mime types to *.htc and *.pps
+ JETTY-841 Duplicate messages when sending private message to yourself with cometd chat demo
+ JETTY-842 NPE in jetty client when no path component
+ JETTY-843 META-INF/MANIFEST.MF is not present in unpacked webapp
+ JETTY-844 Replace reflection with direct invocation in Slf4jLog
+ JETTY-848 Temporary folder not fully cleanup after stop (via Sweeper)
+ JETTY-854 JNDI scope does not work with applications in a .war
+ JETTY-859 MultiPartFilter ignores the query string parameters
+ JETTY-861 switched buffer pools to ThreadLocal implementation
+ JETTY-862 EncodedHttpURI ignores given encoding in constructor
+ JETTY-866 jetty-client test case fix
+ JETTY-869 NCSARequestLog locale config
+ JETTY-870 NullPointerException in Response when performing redirect to wrong relative URL
+ JETTY-871 jetty-client expires() NPE race condition fixed
+ JETTY-876 Added new BlockingArrayQueue and new QueuedThreadPool
+ JETTY-894 Add android .apk to mime types
+ JETTY-897 Remove swing dependency in GzipFilter
+ JETTY-898 Allow jetty debs to start with custom java args provided by users
+ JETTY-899 Standardize location and build process for configuration files which go into etc
+ JETTY-890 merge jaspi branch to trunk
+ JETTY-909 Update useragents cache
+ JETTY-917 Change for JETTY-811 breaks systemProperties config parameter in maven-jetty-plugin
+ JETTY-922 Fixed NPE on getRemoteHost when socket closed
+ JETTY-923 Client supports attributes
+ JETTY-926 default location for generatedClasses of jspc plugin is incorrect
+ JETTY-939 NPE in AbstractConfiguration.callPreDestroyCallbacks
+ JETTY-938 Deadlock in the TerracottaSessionManager
+ JETTY-946 Redeploys with maven jetty plugin of webapps with overlays don't work
+ JETTY-950 Fix double-printing of request URI in request log
+ JETTY-953 SSL keystore file input stream is not being closed directly
+ JETTY-956 SslSelectChannelConnector - password should be the default value of keyPassword if not specified
+ moved to org.eclipse packages
+ simplified HandlerContainer API

jetty-7.0.0.pre5 30 Oct 2008
+ JETTY-766 Fix npe
+ JETTY-767 Fixed SSL Client no progress handshake bug
+ JETTY-768 Remove EnvEntry overloaded constructors
+ JETTY-769 jquery example error
+ JETTY-771 Ensure NamingEntryUtil is jdk1.4 compliant
+ JETTY-772 Increased default threadpool size to 250

jetty-7.0.0.pre4 28 Oct 2008
+ JETTY-241 Support for web application overlays in rapid application development (jetty:run)
+ JETTY-319 improved passing of exception when webapp unavailable
+ JETTY-331 SecureRandom hangs on systems with low entropy (connectors slow to start)
+ JETTY-591 No server classes for jetty-web.xml
+ JETTY-604 AbstractSession.setSessionURL
+ JETTY-670 $JETTY_HOME/bin/jetty.sh not worked in Solaris, because of /usr/bin/which has no error-code
+ JETTY-676 ResourceHandler doesn't support HTTP HEAD requests
+ JETTY-677 GWT serialization issue
+ JETTY-680 Can't configure the ResourceCollection with maven
+ JETTY-681 JETTY-692 MultiPartFilter is slow for file uploads
+ JETTY-682 Added listeners and queue methods to cometd
+ JETTY-686 LifeCycle.Listener
+ JETTY-687 Issue with servlet-mapping in dynamic servlet invoker
+ JETTY-688 Cookie causes NumberFormatException
+ JETTY-689 processing of non-servlet related annotations
+ JETTY-690 Updated XBean dependencies to XBean version 3.4.3 and Spring 2.0.5.
+ JETTY-696 jetty.sh restart not working
+ JETTY-698 org.eclipse.resource.JarResource.extract does not close JarInputStream jin
+ JETTY-699 Optimized cometd sending of 1 message to many many clients
+ JETTY-700 unit test for unread request data
+ JETTY-703 maxStopTimeMs added to QueuedThreadPool
+ JETTY-708 allow 3 scopes for jndi resources: jvm, server or webapp
+ JETTY-709 Jetty plugin's WebAppConfig configured properties gets overridden by AbstractJettyRunMojo even when already set
+ JETTY-710 Worked around poor implementation of File.toURL()
+ JETTY-711 DataSourceUserRealm implementation
+ JETTY-712 HttpClient does not handle request complete after response complete
+ JETTY-715 AJP Key size as Integer
+ JETTY-716 Fixed NPE on empty cometd message
+ JETTY-718 during ssl unwrap, return true if some bytes were read, even if underflow
+ JETTY-720 fix HttpExchange.waitForStatus
+ JETTY-721 Support wildcard in VirtualHosts configuration
+ JETTY-723 jetty.sh does not check if TMP already is set
+ JETTY-724 better handle EBCDIC default JVM encoding
+ JETTY-728 Improve Terracotta integration and performances
+ JETTY-730 Set SAX parse features to defaults
+ JETTY-731 DeliverListener for cometd
+ JETTY-732 Case Sensitive Basic Authentication Response Header Implementations
+ JETTY-733 Expose ssl connectors with xbean
+ JETTY-735 Wrong default jndi name on DataSourceUserRealm
+ JETTY-736 Client Specific cometd advice
+ JETTY-737 refactored jetty.jar into jetty, xml, security, ssl, webapp and deploy jars
+ JETTY-738 If jetty.sh finds a pid file is does not check to see if a process with that pid is still running
+ JETTY-739 Race in QueuedThreadPool
+ JETTY-741 HttpClient connects slowly due to reverse address lookup by InetAddress.getHostName()
+ JETTY-742 Private messages in cometd chat demo
+ JETTY-747 Handle HttpClient exceptions better
+ JETTY-755 Optimized HttpParser and buffers for few busy connections
+ JETTY-757 Unhide JAAS classes
+ JETTY-758 Update JSP to glassfish tag SJSAS-9_1_1-B51-18_Sept_2008
+ JETTY-759 Fixed JSON small negative real numbers
+ JETTY-760 Handle wildcard VirtualHost and normalize hostname in ContextHandlerCollection
+ JETTY-762 improved QueuedThreadPool idle death handling
+ JETTY-763 Fixed AJP13 constructor
+ JETTY-766 Ensure SystemProperties set early on jetty-maven-plugin

jetty-7.0.0pre3 - 6 August 2008
+ Upgrade jsp 2.1 to SJSAS-9_1_02-B04-11_Apr_2008
+ JETTY-30 Externalize servlet-api to own project
+ JETTY-182 Support setting explicit system classpath for jasper Jsr199JavaCompiler
+ JETTY-319 Get unavailable exception and added startWithUnavailable option
+ JETTY-381 JETTY-622 Multiple Web Application Source Directory
+ JETTY-442 Accessors for mimeType on ResourceHandler
+ JETTY-502 forward of an include should hide include attributes
+ JETTY-562 RewriteHandler support for virtual hosts
+ JETTY-563 JETTY-482 OpenRemoteServiceServlet for GWT1.5M2+
+ JETTY-564 Consider optionally importing org.apache.jasper.servlet
+ JETTY-571 SelectChannelConnector throws Exception on close on Windows
+ JETTY-608 Suspend/Resume/Complete request listeners
+ JETTY-621 Improved LazyList javadoc
+ JETTY-626 Null protect reading the dtd resource from classloader
+ JETTY-628 Rewrite rule for rewriting scheme
+ JETTY-629 Don't hold timeout lock during expiry call.
+ JETTY-632 OSGi tags for Jetty client
+ JETTY-633 Default form encoding 8859_1 rather than utf-8
+ JETTY-635 Correctly merge request parameters when doing forward
+ JETTY-636 Separate lifeycle of jsp build
+ JETTY-637 empty date headers throw IllegalArgumentException
+ JETTY-641 JDBC Realm purge cache problem
+ JETTY-642 NPE in LdapLoginModule
+ JETTY-644 LdapLoginModule uses proper filters when searching
+ JETTY-645 Do not provide jetty-util to the webapps
+ JETTY-646 Should set Cache-Control header when sending errors to avoid caching
+ JETTY-647 suspended POSTs with binary data do too many resumes
+ JETTY-650 Parse "*" URI for HTTP OPTIONS request
+ JETTY-651 Release resources during destroy
+ JETTY-653 Upgrade jta api specs to more recent version
+ JETTY-654 Allow Cometd Bayeux object to be JMX manageable
+ JETTY-655 Support parsing application/x-www-form-urlencoded parameters via http PUT
+ JETTY-656 HttpClient defaults to async mode
+ JETTY-659 ContentExchange and missing headers in HttpClient
+ JETTY-663 AbstractDatabaseLoginModule handle not found UserInfo and userName
+ JETTY-665 Support merging class directories
+ JETTY-666 scanTargetPatterns override the values already being set by scanTarget
+ JETTY-667 HttpClient handles chunked content
+ JETTY-669 Http methods other than GET and POST should not have error page content
+ JETTY-671 Configure DTD does not allow <Property> children
+ JETTY-672 Utf8StringBuffer doesn't properly handle null characters (char with byte value 0)
+ JETTY-675 ServletContext.getRealPath("") returns null instead of returning the root dir of the webapp

jetty-7.0.0pre2 - 30 June 2008
+ JETTY-336 413 error for header buffer full
+ JETTY-425 race in stopping SelectManager
+ JETTY-568 Avoid freeing DirectBuffers. New locking NIO ResourceCache.
+ JETTY-569 Stats for suspending requests
+ JETTY-576 servlet dtds and xsds not being loaded locally
+ JETTY-572 Unique cometd client ID
+ JETTY-578 OSGI Bundle-RequiredExcutionEnvironment set to J2SE-1.5
+ JETTY-579 OSGI resolved management and servlet.resources import error
+ JETTY-580 Fixed SSL shutdown
+ JETTY-581 ContextPath constructor
+ JETTY-582 final ISO_8859_1
+ JETTY-584 handle null contextPath
+ JETTY-587 persist sessions to database
+ JETTY-588 handle Retry in ServletException
+ JETTY-589 Added Statistics Servlet
+ JETTY-590 Digest auth domain for root context
+ JETTY-592 expired timeout callback without synchronization
+ JETTY-595 SessionHandler only deals with base request session
+ JETTY-596 proxy support in HttpClient
+ JETTY-598 Added more reliable cometd message flush option
+ JETTY-599 handle buffers consistently handle invalid index for poke
+ JETTY-603 Handle IPv6 in HttpURI
+ JETTY-605 Added optional threadpool to BayeuxService
+ JETTY-606 better writeTo impl for BIO
+ JETTY-607 Add GigaSpaces session clustering
+ JETTY-609 jetty-client improvements for http conversations
+ JETTY-610 jetty.class.path not being interpreted
+ JETTY-611 make general purpose jar scanning mechanism
+ JETTY-612 scan for web.xml fragments
+ JETTY-613 various distribution related changes
+ JETTY-614 scanner allocates hashmap on every iteration
+ JETTY-615 Replaced CDDL servlet.jar with Apache-2.0 licensed version
+ JETTY-623 ServletContext.getServerInfo() non compliant

jetty-7.0.0pre1 - 3 May 2008
+ Allow annotations example to be built regularly, copy to contexts-available
+ Make annotations example consistent with servlet 3.0
+ Refactor JNDI impl to simplify
+ Improved suspend examples
+ address osgi bundling issue relating to build resources
+ JETTY-529 CNFE when deserializing Array from session resolved
+ JETTY-558 optional handling of X-Forwarded-For/Host/Server
+ JETTY-559 ignore unsupported shutdownOutput
+ JETTY-566 allow for non-blocking behavior in jetty maven plugin
+ JETTY-440 allow file name patterns for jsp compilation for jspc plugin

jetty-7.0.0pre0 - 21 April 2008
+ Jetty-6.1.8 Changes
+ Refactor of Continuation towards servlet 3.0 proposal
+ JETTY-282 Support manually-triggered reloading by maven plugin
+ QueuedThreadPool default
+ RetryRequest exception now extends ThreadDeath
+ Added option to dispatch to suspended requests.
+ Delay 100 continues until getInputStream
+ HttpClient supports pipelined request
+ BayeuxClient use a single connection for polling
+ Make javax.servlet.jsp optional osgi import for jetty module
+ Ensure Jotm tx mgr can be found in jetty-env.xml
+ Renamed modules management and naming to jmx and jndi.
+ JETTY-282 Support manually-triggered reloading by maven plugin
+ JETTY-341 100-Continues sent only after getInputStream called.
+ JETTY-386 backout fix and replaced with ContextHandler.setCompactPath(boolean)
+ JETTY-399 update OpenRemoteServiceServlet to gwt 1.4
+ JETTY-467 allow URL rewriting to be disabled.
+ JETTY-468 unique holder names for addServletWithMapping
+ JETTY-471 LDAP JAAS Realm
+ JETTY-474 Fixed case sensitivity issue with HttpFields
+ JETTY-475 AJP connector in RPMs
+ JETTY-486 Improved jetty.sh script
+ JETTY-487 Handle empty chunked request
+ JETTY-494 Client side session replication
+ JETTY-519 HttpClient does not recycle closed connection.
+ JETTY-522 Add build profile for macos for setuid
+ JETTY-523 Default servlet uses ServletContext.getResource
+ JETTY-524 Don't synchronize session event listener calls
+ JETTY-525 Fixed decoding for long strings
+ JETTY-526 Fixed MMBean fields on JMX MBeans
+ JETTY-528 Factor our cookie parsing to CookieCutter
+ JETTY-530 Improved JMX MBeanContainer lifecycle
+ JETTY-531 Optional expires on MovedContextHandler
+ JETTY-532 MBean properties for QueuedThreadPool
+ JETTY-535 Fixed Bayeux server side client memory leak
+ JETTY-537 JSON handles Locales
+ JETTY-538 test harness fix for windows
+ JETTY-540 Servlet-3.0 & java5 support (work in progress)
+ JETTY-543 Atomic batch get and put of files.
+ JETTY-545 Rewrite handler
+ JETTY-546 Webapp runner. All in one jar to run a webapps
+ JETTY-547 Shutdown SocketEndpoint output before close
+ JETTY-550 Reading 0 bytes corrupts ServletInputStream
+ JETTY-551 Wadi 2.0-M10
+ JETTY-553 Fixed customize override
+ JETTY-556 Encode all URI fragments
+ JETTY-557 Allow ServletContext.setAttribute before start
+ JETTY-560 Allow decoupling of jndi names in web.xml

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Jetty-announce mailing list
Jetty-announce@...
https://lists.sourceforge.net/lists/listinfo/jetty-announce

Re: Virtual Directory

2009-10-05T14:35:56Z

Did you ever find a good answer to this? I'm looking for something similar

Thanks,

Tom

al_masson wrote:

Hi,

I was looking for an answer for my question and I found this article
from Howard Lewis Ship:

http://www.theserverside.com/tt/blogs/showblog.tss?id=JettyHack

This is exactly what I want. But, since this article is from 2004, I
was wondering if there is something already embbeded in Jetty to
achieve the same result.

I couldn't find anything in the docs.

Thanks again,

Alexandre Jacques

On 2/3/07, Alexandre Jacques <dev.lists@gmail.com> wrote:
> Hi Nik,
>
> This is almost what I need. The problem is that I need these images to
> be called as if they were under the context of my WebApp.
>
> Something like: http://localhost:8080/voffice/images/some.gif
>
> And not like: http://localhost:8080/images/some.gif
>
> The behaviour I am expecting is just like an virtual directory.
>
> TIA
>
> Alexandre Jacques
>
> On 2/1/07, Nik Gonzalez <ngonzalez@exist.com> wrote:
> > Hi Alexandre,
> >
> > You may define a new Context that points to your images directory like this:
> >
> > <New id="images" class="org.mortbay.jetty.servlet.Context">
> > <Arg><Ref id="Contexts"/></Arg>
> > <Arg>/images</Arg>
> > <Set name="ResourceBase"><SystemProperty name="jetty.home"
> > default="."/>/images</Set>
> > <Call name="addServlet">
> > <Arg>org.mortbay.jetty.servlet.DefaultServlet</Arg>
> > <Arg>/*</Arg>
> > </Call>
> > </New>
> >
> > Then you can get your images with this
> > http://localhost:8080/images/some.gif.
> >
> > HTH,
> > Nik
> >
> > Alexandre Jacques wrote:
> > > Hi,
> > >
> > > I am new to Jetty 6, migrating an application from Tomcat.
> > >
> > > I now find myself trying to find a way to map an external directory to
> > > serve static content from a Java WebApp. Something that sounds like a
> > > "virtual directory".
> > >
> > > Is there any way to do that?
> > >
> > > My configuration looks like:
> > >
> > > <Item>
> > > <New id="voffice" class="org.mortbay.jetty.webapp.WebAppContext">
> > > <Set name="contextPath">/</Set>
> > > <Set name="war">./webapps/voffice.war</Set>
> > > <Set name="VirtualHosts">
> > > <Array type="java.lang.String">
> > > <Item>(...).com</Item>
> > > </Array>
> > > </Set>
> > > </New>
> > > </Item>
> > >
> > > What I need is, when somebody access something like /voffice/images/*,
> > > that Jetty should grab the images from a static location (in my FS)
> > > like /usr/local/apps/voffice/images/*.
> > >
> > > Is it possible?
> > >
> > > TIA
> > >
> > > Alexandre Jacques
> > >
> > > -------------------------------------------------------------------------
> > > Using Tomcat but need to do more? Need to support web services, security?
> > > Get stuff done quickly with pre-integrated technology to make your job easier.
> > > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> > > _______________________________________________
> > > Jetty-support mailing list
> > > Jetty-support@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/jetty-support
> > >
> > >
> >
> >
> > -------------------------------------------------------------------------
> > Using Tomcat but need to do more? Need to support web services, security?
> > Get stuff done quickly with pre-integrated technology to make your job easier.
> > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> > _______________________________________________
> > Jetty-support mailing list
> > Jetty-support@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/jetty-support
> >
>

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Jetty-support mailing list
Jetty-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

Jetty 6.1.14 Startup Failed with NoSuchMethodError

2009-09-23T01:47:45Z

Hi,

I have a problem with Jetty 6.1.14 version. I have downloaded the Jetty 6.1.14 version from Jetty site:

https://olex.openlogic.com/packages/jetty?show=versions&version=2115

Extracted the zip and started the jetty service. Gets the following exception.

I do get the similar kind of issues with latest jetty 6.1.19 also. FYI , I do not see this with 6.1.5. Attaching the Exception trace(NoSuchMethodError) also.

jvm 2 | 2009-09-23 13:40:37.508::INFO: jetty-6.1.14
jvm 2 | 2009-09-23 13:40:37.586::INFO: Deploy C:\jetty-6.1.14\contexts\test.
xml -> org.mortbay.jetty.webapp.WebAppContext@84da23{/,C:\jetty-6.1.14/webapps/t
est}
jvm 2 | 2009-09-23 13:40:37.633::INFO: Deploy C:\jetty-6.1.14\contexts\test-
jndi.xml -> org.mortbay.jetty.webapp.WebAppContext@c05d3b{/test-jndi,C:\jetty-6.
1.14/contexts/test-jndi.d}
jvm 2 | 2009-09-23 13:40:37.665::INFO: Deploy C:\jetty-6.1.14\contexts\javad
oc.xml -> org.mortbay.jetty.handler.ContextHandler@1d10a5c{/javadoc,file:/C:/jet
ty-6.1.14/javadoc/}
jvm 2 | 2009-09-23 13:40:38.399::WARN: failed jsp
jvm 2 | java.lang.NoSuchMethodError: org.w3c.dom.Document.setDocumentURI(Ljav
a/lang/String;)V
jvm 2 | at org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(Pars
erUtils.java:242)
jvm 2 | at org.apache.jasper.compiler.JspConfig.processWebDotXml(JspConf
ig.java:141)
jvm 2 | at org.apache.jasper.compiler.JspConfig.init(JspConfig.java:312)

jvm 2 | at org.apache.jasper.compiler.JspConfig.<init>(JspConfig.java:11
8)
startup+issue.txt

Please let me know how to resolve this issue.

Thanks,
Mohan

JSP 2.1 jstl problem with fmt library

2009-09-22T02:22:28Z

Hello all,

I am having the following problem with a jsp site that uses fmt from the JSTL library.

installed jetty: jetty-6.1.18.jar
Class-Path: ../lib/commons-cli-1.1.jar ../lib/commons-codec-1.3.jar ../lib/commons-io-1.4.jar ../lib/commons-fileupload-1.2.1.jar ../lib/commons-httpclient-3.1.jar ../lib/commons-logging-1.1.jar ../lib/commons-net-2.0.jar ../lib/commons-net-ftp-2.0.jar ../lib/jcommon-0.7.2.jar ../lib/jetty-6.1.18.jar ../lib/jetty-util-6.1.18.jar ../lib/junit-4.5.jar ../lib/log4j-1.2.15.jar ../lib/servlet-api-2.5-20081211.jar ../lib/upnp-stack-1.8.0.jar ../lib/ws-commons-util-1.0.2.jar ../lib/xmlrpc-client-3.1-javadoc.jar ../lib/xmlrpc-client-3.1-sources.jar ../lib/xmlrpc-client-3.1.jar ../lib/xmlrpc-common-3.1-javadoc.jar ../lib/xmlrpc-common-3.1-sources.jar ../lib/xmlrpc-common-3.1.jar ../lib/xmlrpc-server-3.1-javadoc.jar ../lib/xmlrpc-server-3.1-sources.jar ../lib/xmlrpc-server-3.1.jar ../lib/jsp-2.1/ant-1.6.5.jar ../lib/jsp-2.1/core-3.1.1.jar ../lib/jsp-2.1/jsp-2.1-glassfish-9.1.1.B60.25.p0.jar ../lib/jsp-2.1/jsp-2.1-jetty-6.1.18.jar ../lib/jsp-2.1/jsp-api-2.1-glassfish-9.1.1.B60.25.p0.jar

error:
HTTP ERROR 500

Problem accessing /login.jsp. Reason:

/login.jsp(1,63) PWC6188: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application

Caused by:

org.apache.jasper.JasperException: /login.jsp(1,63) PWC6188: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application

in the jsp site login.jsp

<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/fmt" prefix="fmt" %>

<jsp:include page="html/general/index.jsp"/>

web.xml:

<web-app
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
metadata-complete="true"
version="2.5">




<context-param>
<param-name>javax.servlet.jsp.jstl.fmt.localizationContext</param-name>
<param-value>locale</param-value>
</context-param>

....

<login-config>
<auth-method>FORM</auth-method>
<realm-name>MyRealm</realm-name>
<form-login-config>
<form-login-page>/login.jsp</form-login-page>
<form-error-page>/error.jsp</form-error-page>
</form-login-config>
</login-config>

<security-constraint>
<display-name>ProtectEverything</display-name>
<web-resource-collection>
<web-resource-name>ProtectEverything</web-resource-name>
<url-pattern>*.*</url-pattern>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>admin</role-name>
</auth-constraint>
</security-constraint>

<security-constraint>
<web-resource-collection>
<web-resource-name>ExcludeLoginPage</web-resource-name>
<url-pattern>/login.jsp</url-pattern>
<url-pattern>/html/css/*</url-pattern>
<url-pattern>/html/img/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>

....

Does anyone have a hint on this issue? It would be very appreciated...

Jetty JSP

2009-09-03T12:13:36Z

Hi,

This is my requirement - The process flow should be from Jetty to Servlet to JSP.
When I hit a url, my servlet should be called, which adds some params and opens a jsp in the browser.

Snippets of code here:
//url : http://localhost:4122/jsp/admin
WebAppContext webapp= new WebAppContext();
webapp.setContextPath("/jsp");
webapp.setWar("src/main/webapps/test");
webapp.addServlet("TestServlet", "/admin/*");
server.addHandler(webapp);
server.start();
server.join();

// TestServlet
protected void doPost(HttpServletRequest request,
HttpServletResponse response) throws ServletException, IOException {
request.setAttribute("Name", "Billy");
request.getRequestDispatcher("/HelloWorld.jsp").include(request, response);
}

When I hit the url, it shows a blank page and there is no error/exception.
Any Help would be much appreciated!

Thank you.
Brenna

Error while creating, Jetty Connection pool (Illegeal State Exception)

2009-08-31T03:23:36Z

hi everybody,
I want to create a jetty connection pool. So for that,
i have created a new Java web app.
In this,
i created one jsp file to list the table content which is stored in derby database.
code snippets of my index.jsp are:
======================
javax.naming.Context initContext = new javax.naming.InitialContext();
javax.naming.Context envContext = (Context) initContext.lookup("java:/comp/env");
javax.sql.DataSource ds = (DataSource) envContext.lookup("jdbc/TestDB");
java.sql.Connection conn = ds.getConnection();
java.sql.Statement stmt = conn.createStatement();
java.sql.ResultSet resultset = stmt.executeQuery("select * from tbl_user");

And my xml files under "web" package, of my project are attached with this post:
i) web.xml:
ii) jetty-web.xml:
iii) jetty-env.xml:

I got an error as IllegalStateException.... Error log is attached below.

Error Logs :-
----------
error.txt

So, anybody please help to resolve this...
Note, i am using Jetty-6.1.3 - this package downloaded from,
" http://dist.codehaus.org/jetty/jetty-6.1.x/ "

I dont know, the way, which i going is correct or not ??
So, Please guide and give me a solution to solve this problem..
Thanks in advance.

Error while creating, Jetty Connection pool (Illegeal State Exception).

2009-08-29T04:25:19Z

Re: Jetty Plus datasource configuration

2009-08-29T02:39:45Z

hi,
I want to create a jetty connection pool. So for that,
i have created a new Java web app.
In this,
i created one jsp file to list the table content which is stored in derby database.
code snippets of my index.jsp are:
======================
javax.naming.Context initContext = new javax.naming.InitialContext();
javax.naming.Context envContext = (Context) initContext.lookup("java:/comp/env");
javax.sql.DataSource ds = (DataSource) envContext.lookup("jdbc/TestDB");
java.sql.Connection conn = ds.getConnection();
java.sql.Statement stmt = conn.createStatement();
java.sql.ResultSet resultset = stmt.executeQuery("select * from tbl_user");

And my xml files under "web" package, of my project are:
i) web.xml:
======

<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
<session-config>
<session-timeout>30</session-timeout>
</session-config>
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
<resource-ref>
<description>DB Connection</description>
<res-ref-name>jdbc/TestDB</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
</web-app>

ii) jetty-web.xml:
===========

<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN" "http://jetty.mortbay.org/configure.dtd">
<Configure class="org.mortbay.jetty.webapp.WebAppContext">
<New id="TestDB" class="org.mortbay.jetty.plus.naming.Resource">
<Arg>jdbc/TestDB</Arg>
<Arg>
<New class="org.apache.derby.jdbc.ClientBaseDataSource">
<Set name="driverClassName">org.apache.derby.jdbc.ClientDriver</Set>
<Set name="url">jdbc:derby://localhost:1527/C:/DBs/EventsDB_NEW</Set>
<Set name="username">sa</Set>
<Set name="password">sa</Set>
</New>
</Arg>
</New>
<Array id="plusConfig" type="java.lang.String">
<Item>org.mortbay.jetty.webapp.WebInfConfiguration</Item>
<Item>org.mortbay.jetty.plus.webapp.EnvConfiguration</Item>
<Item>org.mortbay.jetty.plus.webapp.Configuration</Item>
<Item>org.mortbay.jetty.webapp.JettyWebXmlConfiguration</Item>
<Item>org.mortbay.jetty.webapp.TagLibConfiguration</Item>
</Array>
<Call class="org.mortbay.jetty.webapp.WebAppContext" name="addWebApplications">
<Arg><Ref id="Server"/></Arg>
<Arg>./webapps</Arg>
<Arg>org/mortbay/jetty/webapp/webdefault.xml</Arg>
<Arg><Ref id="plusConfig"/></Arg>
<Arg type="boolean">True</Arg> 
<Arg type="boolean">False</Arg> 
</Call>
</Configure>

iii) jetty-env.xml:
==========

<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN" "http://jetty.mortbay.org/configure.dtd">
<Configure class="org.mortbay.jetty.webapp.WebAppContext">
<New id="TestDB" class="org.mortbay.jetty.plus.naming.Resource">
<Arg>jdbc/TestDB</Arg>
<Arg>

<New class="org.apache.derby.jdbc.ClientBaseDataSource">
<Set name="driverClassName">org.apache.derby.jdbc.ClientDriver</Set>
<Set name="url">jdbc:derby://localhost:1527/C:/DBs/EventsDB_NEW</Set>
<Set name="username">sa</Set>
<Set name="password">sa</Set>
</New>
</Arg>
</New>
</configure>

NOW, i compiled my web project, and make a war file of it.
And i put this into jetty's webapp folder.
Then i start jetty by,
"java -jar start.jar etc/jetty.xml etc/jetty-plus.xml "

I got the following ERROR...,
2009-08-29 15:03:46.687::WARN: Failed startup of context org.mortbay.jetty.weba
pp.WebAppContext@110fe28{/JettyConnPoolTest,jar:file:/D:/JettyServer/jetty-6.1.3
/webapps/JettyConnPoolTest.war!/}
java.lang.IllegalStateException: No object for id=Server
at org.mortbay.xml.XmlConfiguration.refObj(XmlConfiguration.java:632)
at org.mortbay.xml.XmlConfiguration.itemValue(XmlConfiguration.java:877)

at org.mortbay.xml.XmlConfiguration.value(XmlConfiguration.java:798)
at org.mortbay.xml.XmlConfiguration.call(XmlConfiguration.java:510)
at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:241)

at org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:179)

at org.mortbay.jetty.webapp.JettyWebXmlConfiguration.configureWebApp(Jet
tyWebXmlConfiguration.java:109)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.jav
a:1215)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:
500)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448
)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
40)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection
.java:147)
at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHan
dlerCollection.java:161)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
40)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection
.java:147)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
40)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:
117)
at org.mortbay.jetty.Server.doStart(Server.java:210)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
40)
at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:929)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.mortbay.start.Main.invokeMain(Main.java:183)
at org.mortbay.start.Main.start(Main.java:497)
at org.mortbay.start.Main.main(Main.java:115)
2009-08-29 15:03:46.812::WARN: Unknown realm: Test JAAS Realm
2009-08-29 15:03:46.890::INFO: Started SelectChannelConnector @ 0.0.0.0:8080

So, anybody please help me to resolve the above error...
Note, i am using Jetty-6.1.3 - this package downloaded from,
" http://dist.codehaus.org/jetty/jetty-6.1.x/ "

Please give me a solution to solve this problem..
Thanks in advance.noor@...

jetty / tomcat webapp context.xml

2009-08-17T08:44:28Z

Hello !

I need support regarding integration of a tomcat web application with the jetty webserver. My application is more complex (using it's own context.xml) so that I did not find any examples how to deal with it.

My tomcat webapp project has following file structure (maven compatible):

-------------------------------
* src/main/java
* src/main/webapp
+ META-INF (contains the context.xml file with application specific properties like "<Environment>...", "<Logger>...", "<Valve...>" and "<Resource ...>")
+ jsps (contains jsp files)
+ WEB-INF (contains the web.xml file with properties like "servlet-mapping" or "servlet")
index.jsp
-------------------------------

Now I want to start the maven jetty:run goal. It exits with following exception because my own class InitializeApplication attempts to read some properties from the application context file (META-INF/context.xml).
The reason for this exception is the missing context file that seems not to be managed by jetty. Now my questions:

1. is there any way to execute a tomcat application with both, tomcat and jetty, without configuration changes (perhaps contextHandlers node in the pom.xml, e.g. '<contextHandler implementation="org.apache.catalina.core.StandardContext"> ....' or something similar)?
2. if changes are necessary what should be changed (conversion of the tomcat-specific context.xml into the jetty-specific xml structure and so on...).

-----------------------------
Context file excerpt:
-----------------------------

<?xml version="1.0" encoding="UTF-8"?>
<Context
docBase="mytestapplication"
path="/mytestapplication"
unpackWARs="true"
reloadable="true"
swallowOutput="true">

<Logger className="org.apache.catalina.logger.FileLogger"
prefix="wigeoweb."
suffix=".log"
timestamp="true"/>
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs"
prefix="wigeoweb_access_log."
suffix=".log"
pattern="combined"
resolveHosts="true"/>

<Resource
name="jdbc/ConfigDB"
auth="Container"
type="javax.sql.DataSource"
factory="org.apache.commons.dbcp.BasicDataSourceFactory"
maxActive="500"
maxIdle="5"
maxWait="3000"
username="xxx"
password="yyy"
driverClassName="org.gjt.mm.mysql.Driver"
url=""
/>

<Environment name="baseLogDir" value="C:\tmp\logs" type="java.lang.String" override="false"/>
<Environment name="logEnabled" value="true" type="java.lang.String" override="false"/>
</Context>

-----------------------------
Source Code (InitializeApplication):
-----------------------------

Context appCtx = (Context)(new InitialContext()).lookup("java:comp/env");

//...code

String string = (String)(appCtx.lookup("baseLogDir"));
// here the exception is thrown because appCtx does not contain "baseLogDir" key ===> context.xml has not been recognized by jetty!!

if( string == null ) throw new ConfigurationLoadException(...);

-----------------------------
Thrown Exception:
-----------------------------

[INFO] Starting jetty 6.1.19 ...
2009-08-13 12:30:17.618::INFO: jetty-6.1.19
2009-08-13 12:30:17.868::WARN: Unknown realm: MyTestApplication Realm
2009-08-13 12:30:17.931::INFO: No Transaction manager found - if your webapp requires one, please configure one.
13.08.2009 12:30:18 InitializeApplication init
INFO: ################################################################################################################################
13.08.2009 12:30:18 InitializeApplication init
INFO: MyTestApplication Framework
13.08.2009 12:30:18 InitializeApplication init
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: Initialization failed! (ConfigurationLoadException[sourceInformation="Web application context",message="Key "baseLogDi
r" not found in web application configuration!"])
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: ApplicationContextFrameworkConfiguration.getStringE(ApplicationContextFrameworkConfiguration.java:164)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: mytestapplication.framework.config.BaseFrameworkConfiguration.parseConfiguration(BaseFrameworkConfiguration.jav
a:72)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: ApplicationContextFrameworkConfiguration.<init>(ApplicationContextFrameworkConfiguration.java:66)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: InitializeApplication.init(InitializeApplication.java:254)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:431)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:676)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1239)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:466)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:124)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.Server.doStart(Server.java:224)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:132)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:441)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:383)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:210)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:184)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371
)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: java.lang.reflect.Method.invoke(Method.java:589)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
13.08.2009 12:30:18 InitializeApplication init
SCHWERWIEGEND: ERROR: org.codehaus.classworlds.Launcher.main(Launcher.java:375)
2009-08-13 12:30:18.618::INFO: Shutdown hook executing

thank you for the support
golbie

Jetty Logs

2009-08-16T22:22:09Z

Hi,

We are using Jetty 5.1 for our application which pulls data from Oracle Database. I have some queries
1.
The log file has following entry:
X.X.X.XXX - - [07/Aug/2009:00:01:33 +0000] "POST /somename/hl7 HTTP/1.1" 200 201 "-" "Java/1.5.0" -
X.X.X.XXX - - [07/Aug/2009:00:01:33 +0000] "POST /somename/hl7 HTTP/1.1" 200 2 "-" "Java/1.5.0" -
X.X.X.XXX - - [07/Aug/2009:00:02:28 +0000] "POST /somename/hl7 HTTP/1.1" 203 53 "-" "Java/1.5.0_05" -
X.X.X.XXX - - [13/Aug/2009:11:59:51 +0000] "POST /somename/hl7 HTTP/1.1" 205 38 "-" "Java/1.5.0_09" -

What does 200 201 2 203 53 38 signify?
I think 200 201 203 are http codes but what are 2 & 53 & 38???

2.
Also is it possible to see any logs where I can see how many connections were made during a day/time and how many weere successful, how many rejected. And what was the total time required to process the request.

3.
I have heard about JConsole can I use this to see any graphical representation of connections or is there any other tool which can give me some info regarding my Query 2.

Thanks In Advance
Prasad

how to configure JVMTI library with Jetty

2009-07-28T04:23:57Z

Hi,

I am using jetty6.1.19 for one of my application in which I need to monitor the thread of my application running in the JVM. For this I need to configure a jvmti-win32.dll and a profile.jar file in the with jvm instance in which Jetty web container will start running.

I have trying the below command to configure it:

java -agentpath:"D:\installable\jetty-6.1.19\jvmti-win32" -javaagent:"D:\installable\jetty-6.1.19\Profiler.jar" -Xbootclasspath/a:"D:\installable\jetty-6.1.19\Profile
r.jar" -jar start.jar

Please provide me some solution so that I could configure my profile.jar and dll with jetty.
Any reply will be appriciated.

Thanks,
Puneet

maven jetty:run pluginGroup resolution

2009-07-28T03:27:27Z

Hi,

I'm getting an issue with the maven jetty:run goal. It was working fine and then started to download version 7 of the plugin which broke our configuration. It also appeared as though the plugin was not respecting our version numbers in the pluginManagement section.

I was simply typing

mvn jetty:run

with a settings.xml file configuration of

<pluginGroup>org.mortbay.jetty</pluginGroup>

After playing around with the build some more I found that by explicitly specifying the plugin name like this

mvn org.mortbay.jetty:maven-jetty-plugin:run

forces maven to use the version (6) specified in our pluginManagement section according to the old plugin name.

So it appear that since the release of version 7, the pluginGroup inner workings always resolve to the new jetty-maven-plugin name, and this prompts maven to download a version 7+.

Is there any elegant way for us to continue to use the shorthand mvn jetty:run and have this resolve to the old plugin name?

thanks,

Neil

Hot Deployment in jetty

2009-07-21T23:24:25Z

Hi,
Can anyone plase tell me how to do the hot deplyment in jetty. I am lloking for both Configuration wise as well as using embedded jetty.
Please help

Problem moving to Jetty 7

2009-07-16T05:31:20Z

A few inconsistencies with porting from Jetty 6 to Jetty 7: Using Jetty 7.0.0.RC0

We have an inhouse build server based on Jetty which supports adding multiple WebAppContext's.
Usually with Jetty 6 we would call server.addhandler(webAppContext) to add the WebAppContext after we construct it, but that option has now been removed from Jetty 7.

After digging around in some examples in the org.eclipse.jetty maven repository I came up with the following revision to the code

Constructor adding an ContextHandlerCollection to the server and adding an PingHandler to the ContextHandlerCollection.
public void WebServer(){
....
ContextHandlerCollection contexts = new ContextHandlerCollection();

ContextHandler contextHandler = new ContextHandler();
contextHandler.setContextPath("/ping");
pingHandler = new PingHandler();
contextHandler.setHandler(pingHandler);
contexts.addHandler(contextHandler);
server.setHandler(contexts);
....
}

This method adds a new WebApplication to the server
private WebAppContext addWebApplication(String contextPath, String webApp) {
....
Handler handler = server.getHandler();
if(handler instanceof ContextHandlerCollection){ //As it obviously is, as it has been set in constructor, but I check anyway.
ContextHandlerCollection handlerCollection = (ContextHandlerCollection) handler;
handlerCollection.addHandler(webAppContext);
server.setHandler(handlerCollection);
}
....
}

Is this the correct method of adding a WebAppContext handler to the server instead of the old server.addHandler?

One other thing:
previously
Connector[] connectors = this.server.getConnectors();
for (Connector connector : connectors) {
connector.setBufferHeaderSize(headerBufferSize);
}

revision for Jetty 7
Connector[] connectors = this.server.getConnectors();
for (Connector connector : connectors) {
connector.setRequestHeaderSize(headerBufferSize);
connector.setResponseHeaderSize(headerBufferSize);
}

When I run this new solution with Jetty 7 I get an error stating that:
java.lang.IllegalStateException: No processor for web xml
at org.eclipse.jetty.plus.webapp.AbstractConfiguration.configure(AbstractConfiguration.java:416)
....

I can not find any information for use of the WebXmlProcessor in this situation.

One last thing:
Jetty seriously needs a reference guide like the one Hibernate and Spring got. Jetty 7 has major restructuring which one needs to read the source code to find out about.

Jetty plus?

2009-07-16T04:47:15Z

I am installing Liferay, which seems to requiere Jetty Plus. My Jetty6 installation doesn't have jetty plus, as far as I can see. I can find jetty plus up to version 5, not 6.
In particular, I need JOTM classes that Lifereay refers to. I'm not sure what jetty plus is, is it available for jetty6? should it be part of jetty6?

Multiple domains and sessions

2009-07-15T11:52:03Z

Hi,

I have configured my windows box such that 127.0.0.1 is mapped to localhost, localhost.com, localhost.org

Now, in my application, I use HttpSession object to maintain session across JSP pages.

Whenever I access the website

http://localhost.com:8080/

It opens the index.jsp page just fine.

Then I login and set the session attributes in the session object and go the home page say home.jsp. This works fine too.

http://localhost.com:8080/home.jsp

However, sometime later when i submit a form, which points to another page, searchresults.jsp

the ServerName changes to:

localhost

only and as a result my session is invalidated and I am sent back to the index page.

Can anyone tell me why is this happening?

thanks

mod_proxy and ssl client certificate

2009-07-08T06:55:06Z

Hi!

Jetty docs recommend using mod_proxy instead of mod_proxy_ajp as a preferred proxying approach to use with Apache (2.2.11 in my case). But is it possible to get a SSL Client Certificate from the request with mod_proxy? I wasn't able to get that with mod_proxy, but mod_proxy_ajp is working. Is there any tricks to get mod_proxy working with client certs correctly?

Cheers,
Vladimir

Jetty/ServiceMix goes into deadlock under load

2009-07-02T00:40:40Z

Hi,

I am using Apache ServiceMix 3.0, I am getting SocketTimedOut Exception when I do a load test using LoadRunner Tool.

The application goes into a freeze and I can see a message in the log stating that the Threadpool size of 255 is reached.

I have to restart the application to make it work normally.

I am not sure what is causing the crash is it Jetty or the SEDA queues in ServiceMix?

I need to get a resolution to this issue ASAP, any help will be highly appreciated.

Thanks in advance.

Regards
Jay

Problem in using SSL of GNU classpath from jetty server..

2009-06-30T23:00:32Z

I am using below mentioned configuration to run my web application-

jetty server version 6.1.8
GNU Classpath version 0.98 and
JamVM version 1.5.3
Linux m/c

My web application is deployed on jetty which is running on JamVM using GNU Classpath library. I have no issues in accessing application through normal http protocol but not able to access it using https protocol.
I have successfully created a keystore of type 'GKR' by using tool provided by GNU Classpath and using it for configuring SSL on jetty web server (jetty-ssl.xml). keystore contain valid private key and corresponding public key in certificate.

Initially i faced problem in configuring SSL on jetty because it was not allowing to override default keystore type (JKS), keymanager and trust manager algorithm (SunX05). To overcome this issue, i made changes in the GNU Classpath code to use fixed keystore type ("GKR") and keymanager and trust manager algorithm (JessieX509). After this changes, jetty started successfully on configured https port (8443) but browser gets hanged when accessing application on https port. There is no log on jetty console. I used tcpdump utility to figure out issues and it shows below mentioned logs. here hpnsez153 and 172.16.4.197 is client (browser) and server machine respectively-

19:13:13.765558 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281241052:281241328(276) ack 1368401 win 43148
19:13:13.765621 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281241328:281241604(276) ack 1368401 win 43148
19:13:13.765675 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281241604:281241768(164) ack 1368401 win 43148
19:13:13.765709 IP hpnsez153.india.ipolicynet.com.4706 > 172.16.4.197.ssh: . ack 281240888 win 64967
19:13:13.765728 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281241768:281241932(164) ack 1368401 win 43148
19:13:13.765788 IP hpnsez153.india.ipolicynet.com.4706 > 172.16.4.197.ssh: . ack 281241328 win 64527
19:13:13.765823 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281241932:281242096(164) ack 1368401 win 43148
19:13:13.765875 IP hpnsez153.india.ipolicynet.com.4706 > 172.16.4.197.ssh: . ack 281241768 win 64087
19:13:13.765897 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281242096:281242372(276) ack 1368401 win 43148
19:13:13.765954 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281242372:281242520(148) ack 1368401 win 43148
19:13:13.766011 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281242520:281242796(276) ack 1368401 win 43148
19:13:13.766026 IP hpnsez153.india.ipolicynet.com.4706 > 172.16.4.197.ssh: . ack 281242096 win 65535
19:13:13.766068 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281242796:281243088(292) ack 1368401 win 43148
19:13:13.766144 IP hpnsez153.india.ipolicynet.com.4706 > 172.16.4.197.ssh: . ack 281242520 win 65111
19:13:13.766177 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281243088:281243364(276) ack 1368401 win 43148
19:13:13.766244 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281243364:281243640(276) ack 1368401 win 43148
19:13:13.766300 IP hpnsez153.india.ipolicynet.com.4706 > 172.16.4.197.ssh: . ack 281243088 win 64543
19:13:13.766302 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281243640:281243804(164) ack 1368401 win 43148
19:13:13.766364 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281243804:281243968(164) ack 1368401 win 43148
19:13:13.766465 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281243968:281244372(404) ack 1368401 win 43148
19:13:13.766465 IP hpnsez153.india.ipolicynet.com.4706 > 172.16.4.197.ssh: . ack 281243640 win 65535
19:13:13.766562 IP hpnsez153.india.ipolicynet.com.4706 > 172.16.4.197.ssh: . ack 281243968 win 65207
19:13:13.766595 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281244372:281244488(116) ack 1368401 win 43148
19:13:13.766775 IP hpnsez153.india.ipolicynet.com.4706 > 172.16.4.197.ssh: . ack 281244488 win 64687
19:13:13.777237 IP hpnsez153.india.ipolicynet.com.4706 > 172.16.4.197.ssh: P 1368401:1368453(52) ack 281244488 win 64687
19:13:13.777354 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281244488:281244588(100) ack 1368453 win 43148
19:13:13.777420 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281244588:281245184(596) ack 1368453 win 43148
19:13:13.777474 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281245184:281245348(164) ack 1368453 win 43148
19:13:13.777526 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281245348:281245512(164) ack 1368453 win 43148
19:13:13.777580 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281245512:281245676(164) ack 1368453 win 43148
19:13:13.777633 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281245676:281245840(164) ack 1368453 win 43148
19:13:13.777686 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281245840:281246004(164) ack 1368453 win 43148
19:13:13.777743 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281246004:281246168(164) ack 1368453 win 43148
19:13:13.777744 IP hpnsez153.india.ipolicynet.com.4706 > 172.16.4.197.ssh: . ack 281245184 win 63991
19:13:13.777800 IP hpnsez153.india.ipolicynet.com.4706 > 172.16.4.197.ssh: . ack 281245512 win 63663
19:13:13.777821 IP 172.16.4.197.ssh > hpnsez153.india.ipolicynet.com.4706: P 281246168:281246332(164) ack 1368453 win 43148
19:13:13.777832 IP hpnsez153.india.ipolicynet.com.4706 > 172.16.4.197.ssh: . ack 281245840 win 63335
19:13:13.777976 IP hpnsez153.india.ipolicynet.com.4706 > 172.16.4.197.ssh: . ack 281246168 win 63007

I'd really appreciate any hint on my trouble. I am willing to provide more information if required.

I doubt that above issue might be coming due to wrong SSL configuration on jetty so i am providing contents of jetty-ssl.xml file below-

<Call name="addConnector">
<Arg>
<New class="org.mortbay.jetty.security.SslSocketConnector">
<Set name="Port">8443</Set>
<Set name="maxIdleTime">30000</Set>
<Set name="handshakeTimeout">2000</Set>
<Set name="sslKeyManagerFactoryAlgorithm">JessieX509</Set>
<Set name="sslTrustManagerFactoryAlgorithm">JessieX509</Set>

<Set name="provider">Jessie</Set>
<Set name="keystoreType">GKR</Set>
<Set name="keystore"><SystemProperty name="jetty.home" default="." />/etc/alok_gkr_keystore</Set>
<Set name="password">abc123</Set>
<Set name="keyPassword">abc123</Set>
<Set name="truststore"><SystemProperty name="jetty.home" default="." />/etc/alok_gkr_keystore</Set>
<Set name="trustPassword">abc123</Set>

<Set name="handshakeTimeout">200000</Set>

</New>
</Arg>
</Call>
</Configure>

Socket Timed out Exception with Jetty/Servicemix while performing load testing

2009-06-30T04:09:23Z

Re: Cannot adjust jetty timeout value.

2009-06-29T17:21:38Z

In an app I use, a main class kicks off the jetty server. AFTER the line server.start(), I wrote:

Handler handler = server.getHandler();
if(handler instanceof WebAppContext) {
System.out.println("found wac");
WebAppContext rctx = (WebAppContext) handler;
rctx.getSessionHandler().getSessionManager().setMaxInactiveInterval(30); // sets to 30 sec
}

this seems to work.

Colin Canfield-3 wrote:

I am not 100%, but I think this is the equivalent of
setMaxInactiveInterval in session manager. I have tried setting this
but to no help, it still takes around 10 minutes to time out.

Anyone out there had more success with time outs, or know of a
different way to set it ?

Regards, Colin

> There is a session-timeout element in webdefault.xml that you might
> need
> to have a look at.
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Unexpected Results From HttpServletRequest.getPathInfo()

2009-06-17T09:38:54Z

Using Jetty 6.1.18.

I have a web.xml defined like:

<servlet>
<servlet-name>root</servlet-name>
<servlet-class>RootServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>foo</servlet-name>
<servlet-class>FooServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>root</servlet-name><url-pattern>/</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>foo</servlet-name><url-pattern>/foo/*</url-pattern>
</servlet-mapping>

I use the "/*" so that FooServlet handles "/foo/1", "/foo/2", etc.

In a browser, I request the following URL:

/foo/*

FooServlet is invoked. My expectation would be that the following would be true:
request.getRequestURI() = "/foo/*"
request.getContextPath() = ""
request.getServletPath() = "/foo"
request.getPathInfo() = "/*"

But instead I get:
request.getRequestURI() = "/foo/*"
request.getContextPath() = ""
request.getServletPath() = "/foo"
request.getPathInfo() = ""

In the Java Servlet Specification 2.5 MRel2, SRV.3.4, it says:

It is important to note that, except for URL encoding differences between the
request URI and the path parts, the following equation is always true:
requestURI = contextPath + servletPath + pathInfo

Is this a known issue? Thanks.

SSL and Chunked encoding

2009-06-15T06:13:28Z

I am using transfer-encoding and Continuations quite happily and have been for a while.
This enabled a Duplex Http connection.

The problem is when this happens through the SSL connector, no data is sent to the client. The First part (Chunk) of the response is correctly written, but not data reaches the client after that.

Is there something that has to happen differently when SSL is used over chunked encoding?

The connections are still valid, and it is possible to write to the response output stream, it just doesn't seem to be going on the wire.

The stream is being flushed, and I am wrapping the message in the correct Chunked Encoding headers and this works a dream just using HTTP.

Its not a cert thing, as I can access the web server using https and the SSL hadshake completes OK.

Any ideas?

Behavior of Jetty threads.

2009-06-10T23:23:19Z

After starting Jetty in embedded mode, I open the user browser using the new Java 6 Desktop class. I do all of this in the application main() method.

I noticed that while I am inside the main method (I added a break point after the browser is opened), the Jetty server does not answer the browser request. The page keeps loading as if waiting for the server response. As soon as the main() method finishes, I get the homepage in the browser.

I'm really intrigued why we have this behavior. Is it related to the way threads work in java? I'm concerned because after I start the server and open the browser, I start a new server socket on another port to listen for a command to stop the Jetty server.

Jetty will not answer my browser request until in my shutdown server socket thread I call serverSocket.accept();. Did I make myself clear?

Thanks in advance.

embedding jetty in a war file

2009-06-04T09:09:30Z

Hi

I trying to embed jetty inside a war file.
The idea is to start jetty as follows,

java -jar myapp.war --port 8080

This should start jetty on 8080 in localhost and deploy the war file in the jetty instance started.

have anyone tried this before?

Maven Jetty Run Goals

2009-05-29T04:50:04Z

I use jetty:run for my integration tests. But it forks a parallel lifecycle to ensure that the "compile" phase has been completed before invoking Jetty. So, when I run mvn verify, I get compilation, unit tests, and war creation done twice. How can I prevent the fork and start at run goal?

<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>6.1.17</version>
<executions>
<execution>
<id>start-jetty</id>
<phase>pre-integration-test</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<scanIntervalSeconds>0</scanIntervalSeconds>
<daemon>true</daemon>
</configuration>
</execution>
<execution>
<id>stop-jetty</id>
<phase>post-integration-test</phase>
<goals>
<goal>stop</goal>
</goals>
</execution>
</executions>
. . .
</plugin>

Thanks :)

Filters not firing for welcome-file

2009-05-21T15:06:19Z

I have a gzip filter setup to run on <url-pattern>*.html</url-pattern> and <welcome-file>index.html</welcome-file>. When I request http://localhost:8080/ jetty serves up index.html with out running the gzip filter.

Since there is not .html in the url http://localhost:8080/ I can understand why it doesn't run. So my question is what url-pattern can I use to match whatever the welcome-file is?

Thanks!
Steve

jetty with remote IP

2009-05-14T10:40:54Z

I am using embedded jetty with symmetricDs while i am starting the embedded jetty server in the remote server which is having Static IP Address, i couldnot communicate from my client application please help me out. I tried with connector.setHost("0.0.0.0"); but i didnt work for me

Jetty 7.0.0 Pre1 SSL Configuration Problem

2009-05-13T00:09:36Z

Hi,

I am using Jetty 7.0.0 Pre1 version and trying to configure SSL connection with the keystore generated from the security certificate. The Jetty Server takes more than 95% of CPU resource and not allowing other processes to run, this causes Browser and other application to hang.

I have used keytool to generate certificate request.

keytool -keystore keystore -alias jetty -genkey -keyalg RSA

keytool -certreq -alias jetty -keystore keystore -file jetty.csr

and used import command to create keystore from the security certificate...

keytool -import -v -noprompt -trustcacerts -alias jetty -file serverkey.der -keystore server_keystore.
jks -storepass password

and configured the same in jetty.xml file

<Call name="addConnector">
<Arg>
<New class="org.mortbay.jetty.security.SslSocketConnector">
<Set name="Port">8443</Set>
<Set name="maxIdleTime">30000</Set>
<Set name="keystore"><SystemProperty name="jetty.home" default="." />/etc/server_keystore.jks</Set>
<Set name="password">password</Set>
<Set name="keyPassword">password</Set>
</New>
</Arg>
</Call>

When I restart the server, the server takes all the available CPU resources and not returning any response to the Browser.

But if I create the keystore using keytool with out any thirdparty security certificate, the SSL connection works fine.

How to solve the SSL connection issue. Could you please help me?

welcomeServlets in Jetty 7 M1

2009-05-12T09:50:31Z

Hello,

Per http://docs.codehaus.org/display/JETTY/Welcome+files+not+working, and more specifically per "...From Jetty 6.1.16 onwards, the DefaultServlet can dispatch to welcome files which are servlets, even if the files don't exist...." I am wondering whether or not welcomeServlets functionality exists in 7M1.

Please advise, and thanks in advance

Jetty 6.1.14 cometd performance

2009-05-11T15:49:38Z

Hi,

We've been doing performance/stress testing on Jetty's cometd. We observed that when we test the deliver feature of cometd - for eg - have 5000 HTTP bayeux clients connecting/subscribing to the Jetty cometd server and the server delivering to these clients at 3000notification/second. (Here, for performance testing- we deliver the same message to all the clients on same channel) - the jvm on server side goes out of java heap space after running for 20-24 hours.

The parameters we had:
jetty.xml:
<New class="org.mortbay.thread.QueuedThreadPool">
<Set name="minThreads">10</Set>
<Set name="maxThreads">500</Set>
<Set name="lowThreads">20</Set>
<Set name="SpawnOrShrinkAt">2</Set>
</New>
<Set name="maxIdleTime">2000000000</Set>
<Set name="Acceptors">2</Set>
<Set name="statsOn">false</Set>
<Set name="confidentialPort">8443</Set>
<Set name="lowResourcesConnections">50000000000</Set>
<Set name="lowResourcesMaxIdleTime">50000000000</Set>

We increased the maxIdleTime, lowResourcesConnections and lowResourcesMaxIdleTime to support that many connections.
We wanted to know if this would be a right approach.

web.xml:
<init-param>
<param-name>timeout</param-name>
<param-value>12000000</param-value>
</init-param>
<init-param>
<param-name>interval</param-name>
<param-value>0</param-value>
</init-param>
<init-param>
<param-name>maxInterval</param-name>
<param-value>100000000</param-value>
</init-param>
We faced the problem of clients disconnecting when we had default/lower numbers for timeout and maxInterval. So we played around with it little bit and increasing those params resolved the issue.

After this analysis - we are not able to figure out why the memory goes out of bound or is it something related to huge numbers for the params in jetty.xml and web.xml?

Thanks

seam on Jetty6

2009-04-27T06:44:07Z

hi,

i am trying to run my seam(2.1.1) application on Jetty 6.1, so i guess i should add the Embedded JBoss to Jetty. but unfortunately i can't find something about that in internet.

i have found:
- howto add Embedded JBoss to Tomcat: http://www.jboss.org/community/docs/DOC-9687
but unfortunately there is nothing for jetty.
- a discus: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4093683#4093683
and a blog artikel: http://www.jroller.com/wesleyhales/entry/my_first_seam_2_0
both said, seam2 app. can't run on jetty.

is that true? had someone already try this? is this ever possible?

i am trying this since several weeks. so I am grateful if someone give me a hint.

thanks
quan