Re: HTTP ERROR: 500 Content+Length+Error+%282313318+%3E+2097152%29

Bruce,

This error indicates that more bytes were written to the http response 
output stream than the number set in Content-Length header.

HTTP ERROR: 500 Content+Length+Error+%282313318+%3E+2097152%29
                                      (2313318 > 2097152)

Jan

Bruce R. Lewis wrote:
> When I try uploading a file of size 2312873 I get this error:
> 
> HTTP ERROR: 500 Content+Length+Error+%282313318+%3E+2097152%29
> 
> Smaller files don't give the same problem.  Is there a parameter I can
> set to raise the Content-Length limit, assuming that's what's causing
> the error?
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> Jetty-support mailing list
> Jetty-support <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jetty-support

FW: RE: session instance is changed during same request

Greg, will there be any comment on that? Thanks.

-----Original Message-----
From: Alexey Yudichev 
Sent: Friday, July 23, 2004 9:22 AM
To: jetty-support <at> lists.sourceforge.net
Subject: [Jetty-support] RE: session instance is changed during same request

This is a single webapp with 4 filters installed. One of them (I18nFilter) uses
request.getSession().setAttribute() to place a Map with i18ed string resources into session scope.
Then, because user requested a non-existing page, Jetty forwards to 404 handler which is
error404NotFound.jsp which in turn tries to find this map with resources by calling
request.getSession().getAttribute() and finds nothing. In fact, as I discovered from exeperiments,
this is already a different session instance with no attributes at all. 
I do not get a dispatcher from ServletContext and I never interact with other contexts. So the dispatches
you see are definitely not cross-context dispatches.

-----Original Message-----
From: Greg Wilkins [mailto:gregw <at> mortbay.com]
Sent: Friday, July 23, 2004 3:15 AM
To: jetty-support <at> lists.sourceforge.net
Subject: Re: session instance is changed during same request

Alexey,

by Context I mean webapp.

If you have two different webapps at

   /myapp1/*

forrgot password

RE: JSP is not found [SOLVED]

HI,

I'm afraid that the problem is still exist .... here are the
configuration files I used.

After I could set the default descriptor of the web application as
following:

<Set name="rootWebApp">app</Set>
<Call name="addWebApplications">
  <Arg></Arg>
  <Arg><SystemProperty name="jetty.home" default="."/>/../myapp/≤/Arg>
  <Arg><SystemProperty name="jetty.home"
default="."/>/etc/webdefault.xml</Arg>
<Arg type="boolean">true</Arg>
</Call>

Inside the file webdefault.xml I used the following settings for the
JSPs:
<servlet>
    <servlet-name>jsp</servlet-name>
    <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
    <init-param>
      <param-name>logVerbosityLevel</param-name>
      <param-value>debug</param-value>
    </init-param>
    <init-param>
      <param-name>checkInterval</param-name>
      <param-value>600</param-value>
    </init-param>
    <init-param>
      <param-name>development</param-name>
      <param-value>false</param-value>
    </init-param>
    <init-param>
      <param-name>scratchdir</param-name>
      <param-value>/opt/packages/mightymouse/temp</param-value>
    </init-param>
    <load-on-startup>0</load-on-startup>
  </servlet>

Wha was happening is, if I tried to access any JSP within the 600
second, the jsp will be compiled and access without any problem .. BUT,
after I tried to access it after the 600 second (for the first time of
course)....

I get the same weird error on my browser:

HTTP ERROR: 404 %2Fjsp%2FMyPage%2Ejsp
Request URI=/jsp/MyPage.jsp

Powered by Jetty://

-----Original Message-----
From: jetty-support-admin <at> lists.sourceforge.net
[mailto:jetty-support-admin <at> lists.sourceforge.net] On Behalf Of Ibrahim
Salem
Sent: Tuesday, July 27, 2004 1:03 PM
To: jetty-support <at> lists.sourceforge.net
Subject: RE: [Jetty-support] JSP is not found [SOLVED]

Yes true,

It finally worked ... and by the way, it also happened with linux debian
.. 
Thank you

-----Original Message-----
From: jetty-support-admin <at> lists.sourceforge.net
[mailto:jetty-support-admin <at> lists.sourceforge.net] On Behalf Of Adam
Greene
Sent: Monday, July 26, 2004 7:05 PM
To: jetty-support <at> lists.sourceforge.net
Subject: Re: [Jetty-support] JSP is not found

This can happen under Un*x when your temp directory is auto-cleaned 
(happens under Red Hat on a Server I manage).  Try changing where your 
temp directory is (I don't know how as I run a custom server and I do it

in Java code).

Ibrahim Salem wrote:

>Hi,
>
>I'm using the latest version of Jetty 4.2.21 and I observed one of the
>weirdest problems with JSP files.
>
>I'm using Jetty server, which refers to another webapps folder out of
>its normal webapps folder. In the new folder structure, I have a folder
>called jsp that contains all JSP files.
>
>When I run Jetty, I go through the jsp files and I get each one
compiled
>once I hit it (that's why it takes longer time first time I hit it).
>IN some cases, if I didn't hit all the jsp pages at once, or tried to
>hit any JSP page from another browser or machine (it's not always the
>cases !!!) or tried to wait for a while and tried to try something else
>on the server, then tried to hit any new JSP file I get this WEIRD
>error:
>
>
>Hit: http://mysite/jsp/someJSP.jsp
>I get:
>
>HTTP ERROR: 404 %2Fjsp%2FsomeJSP%2Ejsp
>RequestURI=/jsp/someJSP.jsp
>
>Powered by Jetty:// 
>
>I don't know what is going on here. One of the solutions I tried is by
>making the Jasper compile all the JSP files once I run the JETTY
server.
>
>
>I Also check the folder /tmp/Jetty__80__/jsp and  found only the
>compiled JSP pages I could see on the browser ....
>
>Thank you
>
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
>_______________________________________________
>Jetty-support mailing list
>Jetty-support <at> lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/jetty-support
>
>
>  
>

-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

Jetty problem on Linux 2.4.21-15.0.3.EL #1 SMP Tue Jun 29 17:50:32 EDT 2004 s390 s390 s390 GNU/Linux

RE: Jboss 3.2.5 and jetty 4.2.21: ConfigurationElement is set as <server> not <Configure>

I found the cause. It appeared that in about 50% of jboss start attempts a SAXON XSLT transformer was being
found by TransformerFactory.newInstance(), which was deciding to serialize an org.w3c.Node not
starting from it as a root, but from the root of the DOM. Saxon is deployed in jboss as .SAR and of course
shared among all deployed applications (which I do need). Solved by removing META-INF/services
directory from saxon.jar. In other 50% cases a xalan implementation was being found which worked well. 
I wonder what an interesting classloader architecture jboss has: if a resource with the same name is in
several jar files, any of copies may be found each other time :)

-----Original Message-----
From: Jan Bartel [mailto:janb <at> mortbay.com]
Sent: Thursday, July 22, 2004 5:02 PM
To: jetty-support <at> lists.sourceforge.net
Subject: Re: [Jetty-support] Jboss 3.2.5 and jetty 4.2.21: ConfigurationElement is set as <server> not <Configure>

Alexey,

To build the jetty sar, you need to make sure you have the full source 
tree for Jetty. Then, look in extra/j2ee and just type "ant" to build 
it. The classes most useful to insert extra debug statements into will 
be Jetty.java (around line 197 for the setConfiguration() method), 
JettyService.java (around line 331 for the setConfiguration() method).

What debugger are you using, and how are you starting jboss/jetty in the 
debugger?

Alexey Yudichev wrote:
> Yes, just installed a precompiled jboss and it's all the same. With both jbosses if I run a JVM in debug mode,
it gives me this error, and if I start it normally, jetty starts normally too. Something is not
synchronized I guess... But when I connect to JVM with remote debugger, again it works well so I can't debug
it to find out what's happening. How do I build jetty sar from sources? Maybe then I could add some debug
messages to log.
> 
> -----Original Message-----
> From: Jan Bartel [mailto:janb <at> mortbay.com]
> Sent: Friday, July 16, 2004 12:36 AM
> To: jetty-support <at> lists.sourceforge.net
> Subject: Re: [Jetty-support] Jboss 3.2.5 and jetty 4.2.21: ConfigurationElement is set as <server> not <Configure>
> 
> 
> Alexey,
> 
> Very strange. Have you tried this against a pre-built jboss 3.2.5 ?
> It looks like somehow the xml parsing is screwed up and passing the 
> document root of the jboss-service.xml file to Jetty instead of just the 
> <configuration> element.
> 
> Jan
> 
> 
> Alexey Yudichev wrote:
> 
>>I have built jboss 3.2.5 from sources and downloaded jetty-4.2.21-jboss-3.2.5.sar. Whan I try to start
jboss, I am getting the following exception (see below). But sometimes, for example when I am remotely
connected to JBOSS JVM with a debugger in order to catch the problem, it disappears and a correct
configuration starting with <Configure> is passed to Jetty. 
>>I have tried Jetty 5.0RC2 sar several times and did not manage to repeat the problem, but Jetty 5 has got
several other problems.
>>
>>
>>2004-07-15 17:05:38,571 DEBUG [org.jboss.system.ServiceConfigurator] ConfigurationElement set
to [Configure: null] in jboss.web:service=WebServer
>>2004-07-15 17:05:38,571 DEBUG [org.jboss.jetty.JettyService] Saving Configuration to xml fragment
>>2004-07-15 17:05:38,571 DEBUG [org.jboss.system.ServiceController] Creating service jboss.web:service=WebServer
>>2004-07-15 17:05:38,571 DEBUG [org.jboss.jetty.JettyService] Creating jboss.web:service=WebServer
>>2004-07-15 17:05:38,712 DEBUG [org.jboss.jetty] Passing xml config to jetty:
>><server>
>>
>>  <!-- ==================================================================== -->
>>  <!-- Web Container                                                        -->
>>  <!-- ==================================================================== -->
>>
>>  <!--
>>     | Be sure to check that the configuration values are valid for your
>>     | environment.
>>   -->
>>
>>  <mbean code="org.jboss.jetty.JettyService" name="jboss.web:service=WebServer">
>>
>>    <!-- ================================================================= -->
>>    <!-- Your webdefault.xml file - The default settings for every webapp  -->
>>    <!-- deployed by Jetty. Make systemwide changes here to your webapps   -->
>>    <!-- configurations.                                                   -->
>>    <!-- ================================================================= -->
>>
>>    <attribute name="WebDefaultResource">webdefault.xml</attribute>
>>
>>    <!-- ================================================================== -->
>>    <!-- If true, .war files are unpacked to a temporary directory. This    -->
>>    <!-- is useful with JSPs.                                               -->
>>    <!-- ================================================================== -->
>>
>>    <attribute name="UnpackWars">true</attribute>
>>
>>    <!-- ================================================================== -->
>>    <!-- If true, Jetty will register MBeans representative of every Servlet-->
>>    <!-- and Filter within each WebApp immediately. This will slow down your-->
>>    <!-- development iterations.                                            -->
>>    <!-- ================================================================== -->
>>
>>    <attribute name="SupportJSR77">true</attribute>
>>
>>    <!-- ================================================================== -->
>>    <!-- If true, Jetty first delegates loading a class to the webapp's     -->
>>    <!-- parent class loader (a la Java 2). If false, Jetty follows the     -->
>>    <!--  Servlet 2.3 specification, and tries the webapp's own loader      -->
>>    <!-- first (for "non-system" classes)                                   -->
>>    <!-- ================================================================== -->
>>
>>    <attribute name="Java2ClassLoadingCompliance">true</attribute>
>>
>>    <!-- ================================================================= -->
>>    <!-- If you require JAAS authentication, configure the name of the     -->
>>    <!-- attribute in which you expect to find the JAAS active subject:    -->
>>    <!--                                                                   -->
>>    <!-- Commenting out this configuration will disable JAAS support       -->
>>    <!-- ================================================================= -->
>>
>>    <attribute name="SubjectAttributeName">j_subject</attribute>
>>
>>    <!-- ================================================================= -->
>>    <!-- Configuring Jetty. The XML fragment contained in the              -->
>>    <!-- name="ConfigurationElement" attribute is a Jetty-style            -->
>>    <!-- configuration specification.  It is used to configure Jetty with  -->
>>    <!-- a listener on port 8080, and a HTTP request log location.         -->
>>    <!-- The placement here of other Jetty XML configuration statements    -->
>>    <!-- for deploying webapps etc is not encouraged: if you REALLY NEED   -->
>>    <!-- something extra, place it in WEB-INF/jetty-web.xml files          -->
>>    <!-- ================================================================= -->
>>
>>    <attribute name="ConfigurationElement">
>>      <Configure class="org.mortbay.jetty.Server">
>>
>>       <!-- =============================================================== -->
>>       <!-- Configure the Request Listeners                                 -->
>>       <!-- =============================================================== -->
>>
>>
>>       <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
>>       <!-- Add and configure a HTTP listener to port 8080                       -->
>>       <!-- The default port can be changed using: java -Djetty.port=80     -->
>>       <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
>>       <Call name="addListener">
>>         <Arg>
>>          <New class="org.mortbay.http.SocketListener">
>>            <Set name="Port"><SystemProperty default="80" name="jetty.port"/></Set>
>>            <Set name="MinThreads">10</Set>
>>            <Set name="MaxThreads">100</Set>
>>            <Set name="MaxIdleTimeMs">30000</Set>
>>            <Set name="LowResourcePersistTimeMs">5000</Set>
>>            <Set name="ConfidentialPort">443</Set>
>>            <Set name="IntegralPort">443</Set>
>>          </New>
>>         </Arg>
>>       </Call>
>>
>>
>>       <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
>>       <!-- Add a HTTPS SSL listener on port 8843                           -->
>>       <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
>>       <!-- UNCOMMENT TO ACTIVATE -->
>>       <Call name="addListener">
>>         <Arg>
>>           <New class="org.mortbay.http.SunJsseListener">
>>            <Set name="Port">443</Set>
>>            <Set name="MinThreads">5</Set>
>>            <Set name="MaxThreads">100</Set>
>>            <Set name="MaxIdleTimeMs">30000</Set>
>>            <Set name="LowResourcePersistTimeMs">2000</Set>
>>            <Set name="Keystore"><SystemProperty name="jboss.server.home.dir"/>/conf/demokeystore</Set>
>>            <Set name="Password">123456</Set>
>>            <Set name="KeyPassword">123456</Set>
>>           </New>
>>         </Arg>
>>       </Call>
>>
>>
>>       <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
>>       <!-- Add a AJP13 listener on port 8009                               -->
>>       <!-- This protocol can be used with mod_jk in apache, IIS etc.       -->
>>       <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
>>       <!--Call name="addListener">
>>         <Arg>
>>           <New class="org.mortbay.http.ajp.AJP13Listener">
>>            <Set name="Port">8009</Set>
>>            <Set name="MinThreads">5</Set>
>>            <Set name="MaxThreads">20</Set>
>>            <Set name="MaxIdleTimeMs">0</Set>
>>            <Set name="confidentialPort">443</Set>
>>           </New>
>>         </Arg>
>>       </Call-->
>>
>>       <!-- =============================================================== -->
>>       <!-- Configure the Request Log                                       -->
>>       <!-- =============================================================== -->
>>       <Set name="RequestLog">
>>         <New class="org.mortbay.http.NCSARequestLog">
>>           <Arg><SystemProperty name="jboss.server.home.dir"/><SystemProperty default="/log" name="jetty.log"/>/yyyy_mm_dd.request.log</Arg>
>>           <Set name="retainDays">90</Set>
>>           <Set name="append">true</Set>
>>           <Set name="extended">true</Set>
>>           <Set name="buffered">false</Set>
>>           <Set name="LogTimeZone">GMT</Set>
>>         </New>
>>       </Set>
>>
>>       <!-- ======================================================= -->
>>       <!-- New Distributed Session Manager                         -->
>>       <!-- ======================================================= -->
>>
>>       <!--
>>       These can be set on a per webapp basis in WEB-INF/jetty-web.xml
>>       -->
>>
>>      <Set name="DistributableSessionManagerPrototype">
>>       <New class="org.mortbay.j2ee.session.Manager">
>>        <Set name="scavengerPeriod">600</Set>        
>>        <Set name="idGenerator">
>>          <New class="org.mortbay.j2ee.session.DistributableAjpIdGenerator">
>>            <!-- not needed if mod_jk supports JVMROUTE 
>>            <Set name="workerName">node1</Set>
>>            -->
>>          </New>
>>        </Set>
>>        <Set name="interceptorStack">
>>         <Array type="org.mortbay.j2ee.session.StateInterceptor">
>><!--
>>          <Item><New class="org.mortbay.j2ee.session.DebugInterceptor"/></Item>
>>-->
>>          <Item><New class="org.mortbay.j2ee.session.ValidatingInterceptor"/></Item>
>>          <Item><New class="org.mortbay.j2ee.session.TypeCheckingInterceptor"/></Item>
>>          <Item><New class="org.mortbay.j2ee.session.BindingInterceptor"/></Item>
>>          <Item><New class="org.mortbay.j2ee.session.PublishingInterceptor"/></Item>
>>          <Item><New class="org.mortbay.j2ee.session.SubscribingInterceptor"/></Item>
>>          <Item><New class="org.mortbay.j2ee.session.SynchronizingInterceptor"/></Item>
>>         </Array>
>>        </Set>
>>        <!-- 
>>          ************************************************
>>          ***************** CLUSTERING *******************
>>          ************************************************
>>          To activate HTTP Session clustering with Jetty:
>>           1) Start JBoss with the "all" configuration i.e.
>>                "run.bat -c all" or "./run.sh -c all"
>>           2) Activate HTTP session clustering in your Web
>>               Application: add a <distributable/> tag
>>               at the beginning of your WEB-INF/web.xml file
>>           3) Activate the HTTP session replication 
>>               method below: JGStore is an autonomous implementation
>>               that is part of Jetty and makes use of
>>               NO JBoss service. 
>>               The ClusterStore implementation is no longer
>>	       supported. 
>>          ************************************************
>>          ************************************************
>>          ************************************************ -->
>>        <!-- 
>>            JGStore HTTP session replication scheme
>>            (i.e <distributable/> support)
>>            See above for more information. Only run with 
>>            JBoss "all" configuration!        
>>        <Set name="store">
>>         <New class="org.mortbay.j2ee.session.JGStore">
>>          <Set name="actualMaxInactiveInterval">604800</Set>
>>          <Set name="scavengerPeriod">3600</Set>
>>          <Set name="scavengerExtraTime">900</Set>
>>          <Set name="protocolStack">UDP(mcast_addr=228.8.8.8;mcast_port=45566;ip_ttl=32;ucast_recv_buf_size=16000;ucast_send_buf_size=16000;mcast_send_buf_size=32000;mcast_recv_buf_size=64000;loopback=true):PING(timeout=2000;num_initial_members=3):MERGE2(min_interval=5000;max_interval=10000):FD_SOCK:VERIFY_SUSPECT(timeout=1500):pbcast.STABLE(desired_avg_gossip=20000):pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800;max_xmit_size=8192):UNICAST(timeout=2000):FRAG(frag_size=8192;down_thread=false;up_thread=false):pbcast.GMS(join_timeout=5000;join_retry_timeout=2000;shun=false;print_local_addr=true):pbcast.STATE_TRANSFER</Set>
>>          <Set name="subClusterName">DefaultSubCluster</Set>
>>          <Set name="retrievalTimeOut">20000</Set>
>>          <Set name="distributionTimeOut">5000</Set>
>>          <Set name="distributionMode">GET_ALL</Set>
>>         </New>
>>        </Set>
>>        -->
>>        
>>       </New>
>>      </Set>
>>
>>      <!-- For testing the Distributable SessionManager with e.g. Watchdog -->
>>      <!--
>>      <Set name="forceDistributable">true</Set>
>>      -->
>>
>>      </Configure>
>>     </attribute>
>>  </mbean>
>></server>
>>2004-07-15 17:05:38,791 WARN  [org.jboss.jetty] WARNING: ERROR <at> null line:2 col:129 :
org.xml.sax.SAXParseException: Document root element "server", must match DOCTYPE root "Configure".
>>2004-07-15 17:05:38,791 WARN  [org.jboss.jetty] WARNING: ERROR <at> null line:2 col:129 :
org.xml.sax.SAXParseException: Element type "server" must be declared.
>>2004-07-15 17:05:38,791 WARN  [org.jboss.jetty] WARNING: ERROR <at> null line:13 col:81 :
org.xml.sax.SAXParseException: Element type "mbean" must be declared.
>>2004-07-15 17:05:38,791 WARN  [org.jboss.jetty] WARNING: ERROR <at> null line:21 col:42 :
org.xml.sax.SAXParseException: Element type "attribute" must be declared.
>>2004-07-15 17:05:38,791 WARN  [org.jboss.jetty] WARNING: ERROR <at> null line:28 col:34 :
org.xml.sax.SAXParseException: Element type "attribute" must be declared.
>>2004-07-15 17:05:38,791 WARN  [org.jboss.jetty] WARNING: ERROR <at> null line:36 col:36 :
org.xml.sax.SAXParseException: Element type "attribute" must be declared.
>>2004-07-15 17:05:38,807 WARN  [org.jboss.jetty] WARNING: ERROR <at> null line:45 col:51 :
org.xml.sax.SAXParseException: Element type "attribute" must be declared.
>>2004-07-15 17:05:38,807 WARN  [org.jboss.jetty] WARNING: ERROR <at> null line:54 col:44 :
org.xml.sax.SAXParseException: Element type "attribute" must be declared.
>>2004-07-15 17:05:38,807 WARN  [org.jboss.jetty] WARNING: ERROR <at> null line:66 col:44 :
org.xml.sax.SAXParseException: Element type "attribute" must be declared.
>>2004-07-15 17:05:38,822 ERROR [org.jboss.jetty] problem configuring Jetty:
>>org.xml.sax.SAXParseException: Document root element "server", must match DOCTYPE root "Configure".
>>	at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
>>	at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>>	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>>	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>>	at org.apache.xerces.impl.dtd.XMLDTDValidator.rootElementSpecified(Unknown Source)
>>	at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>>	at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>>	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
>>	at
org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source)
>>	at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>>	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>>	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>>	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>>	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>>	at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>>	at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
>>	at org.mortbay.xml.XmlParser.parse(XmlParser.java:124)
>>	at org.mortbay.xml.XmlConfiguration.<init>(XmlConfiguration.java:140)
>>	at org.jboss.jetty.Jetty.setXMLConfiguration(Jetty.java:264)
>>	at org.jboss.jetty.Jetty.setConfigurationElement(Jetty.java:238)
>>	at org.jboss.jetty.JettyService.createService(JettyService.java:166)
>>	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
>>	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:219)
>>	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>	at java.lang.reflect.Method.invoke(Method.java:324)
>>	at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
>>	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
>>	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
>>	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
>>	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
>>	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
>>	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:837)
>>	at $Proxy17.create(Unknown Source)
>>	at org.jboss.system.ServiceController.create(ServiceController.java:283)
>>	at org.jboss.system.ServiceController.create(ServiceController.java:216)
>>	at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
>>	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>	at java.lang.reflect.Method.invoke(Method.java:324)
>>	at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
>>	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
>>	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
>>	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
>>	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
>>	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
>>	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
>>	at $Proxy4.create(Unknown Source)
>>	at org.jboss.deployment.SARDeployer.create(SARDeployer.java:213)
>>	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:790)
>>	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:644)
>>	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:608)
>>	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>	at java.lang.reflect.Method.invoke(Method.java:324)
>>	at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
>>	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
>>	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
>>	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
>>	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
>>	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
>>	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
>>	at $Proxy7.deploy(Unknown Source)
>>	at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:304)
>>	at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:478)
>>	at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)
>>	at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:274)
>>	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
>>	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
>>	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>>	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>	at java.lang.reflect.Method.invoke(Method.java:324)
>>	at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
>>	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
>>	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
>>	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
>>	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
>>	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
>>	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:837)
>>	at $Proxy0.start(Unknown Source)
>>	at org.jboss.system.ServiceController.start(ServiceController.java:367)
>>	at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
>>	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>	at java.lang.reflect.Method.invoke(Method.java:324)
>>	at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
>>	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
>>	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
>>	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
>>	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
>>	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
>>	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
>>	at $Proxy4.start(Unknown Source)
>>	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:251)
>>	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:836)
>>	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:645)
>>	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:608)
>>	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:592)
>>	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>	at java.lang.reflect.Method.invoke(Method.java:324)
>>	at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
>>	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
>>	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
>>	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
>>	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
>>	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
>>	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
>>	at $Proxy5.deploy(Unknown Source)
>>	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:407)
>>	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:311)
>>	at org.jboss.Main.boot(Main.java:145)
>>	at org.jboss.Main$1.run(Main.java:399)
>>	at java.lang.Thread.run(Thread.java:534)
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by BEA Weblogic Workshop
>>FREE Java Enterprise J2EE developer tools!
>>Get your free copy of BEA WebLogic Workshop 8.1 today.
>>http://ads.osdn.com/?ad_idG21&alloc_id040&op=click
>>_______________________________________________
>>Jetty-support mailing list
>>Jetty-support <at> lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/jetty-support
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> Jetty-support mailing list
> Jetty-support <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jetty-support
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_idG21&alloc_id040&op=click
> _______________________________________________
> Jetty-support mailing list
> Jetty-support <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jetty-support

-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

Use Jetty to redirect HTTP request to backend servers

Hi,

Could anyone explain to me how I can use Jetty to accept an HTTP request, parse
the URL and rewrite the URL to forward it to a backend server.

Thanks 
Clyde

-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

Looking for jetty-4.2.6

Re: jetty as proxy

clyde lo wrote:
> Hi,
>  
> Sorry to email personally but I really need some advice about Jetty.

I've sent this reply to jetty-support - as you will get better response
there and others may be interested in the answer.

> I am planning to use jetty in a major project whereby a jetty server is 
> at front, accepts HTTP request then overrides the URL and then forward 
> it to several backend servers.
>  
> I am thinking of using either the FOrwardHandler or the proxyHandler.  I 
> am a bit confused.
> Could you tell me the difference and also how to setup jetty as a proxy.

The proxy handler is of use mainly when the browser thinks that it is
talking to a HTTP proxy.  In that case the browser makes special requests
with the host name in the URL sent.

The forward handler is only good for forwarding to URLs on the same server - not
on a different server.

If the browser does not know it is talking to a proxy, then you can
build the content of your request anyway you like.  You can extend the
proxyhandler and make it think it has received a proxy request.  Or you can
use a HTTP client (java.net.URLConnection or jakarta HttpClient) to fetch
the content.

regards

-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support

Re: Looking for jetty-4.2.6

Ike,

You want to move to the latest in the 4.2 series, which is 4.2.21.

However, if you really need 4.2.6, then go to the Jetty site and click 
on the "Alternate Archive" item in the left hand menu, which takes you 
to ftp://jetty.mortbay.org/pub then select the directory named OLD and 
you will find all previous releases of Jetty.

cheers,
Jan

Ikonne, Ike wrote:
> 
> Hi all,
> 
> I am trying to download jetty-4.2.6 from jetty download site, but I can 
> only
> find 4.2.21 and 4.2.20 and 5.0.  How can I find jetty-4.2.6?  By the 
> way, which
> one in newer,  jetty-4.2.6 or jetty-4.2.21?
> 
> Thanks,
> 
> Ike
> 

-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Jetty-support mailing list
Jetty-support <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-support