Re: [jetty-user] Weird caching issue

I found out what the problem was by debugging the code line by line. It turns
out that the DefaultServlet had compression enabled, so it was trying to
find a.js.gz if it existed. Unfortunately, this was already there. So when I
updated a.js but hadn't updated a.js.gz, I was still getting the old
version.

Deleting this file fixed up my issue.

Thanks for your help,
Will

janb wrote:
> 
> Will,
> 
> Are you using Windows? It could be the windows nio filemapped buffer
> problem:
> http://docs.codehaus.org/display/JETTY/Files+locked+on+Windows
> 
> regards
> Jan
> 
> wbecker wrote:
>> I am running an embeded Jetty server, and I have a wierd issue, where
>> altering files is not always reflected in on the http interface. 
>> 
>> Say I have a file a.js, and alter the code in it. It will not update,
>> even
>> if I stop and restart the server. However, if i rename it to aa.js, this

Re: [jetty-user] Global JNDI resource

Hi,

On 31.03.2008, at 04:35, David Yu wrote:

> When referencing from your webapp, its java:comp/env/jdbc/DSTest
> Have a read at http://docs.codehaus.org/display/JETTY/JNDI
Okay!

I now have modified my JSPWiki page accordingly (see below):

+-+-+-+-+-+-+-+-+-+-+-+-+-+
----
[{WikiSQL source='java:comp/env/jdbc/DSTest'

select * from roles order by role}]
----
[{WikiSQL source='java:comp/env/jdbc/DSTest' class='grid'

select * from roles order by role}]
----
[{WikiSQL query='select head,leg from body where hands=2' ajax='true'  
source='java:comp/env/jdbc/DSTest' class='undertaker'}]
----
<[WikiSQL Home|http://swdouglass.com/wiki/Wiki.jsp?page=WikiSQL]>
+-+-+-+-+-+-+-+-+-+-+-+-+-+

Unfortunately the error message is persisting. :(

+-+-+-+-+-+-+-+-+-+-+-+-+-+
Plugin insertion failed: Failed to find JNDI datasource: null

Re: [jetty-user] Maven plugin: weird message with Ssl and Select connector

I'm on OS X 10.5.2.

Is the error OS dependent?
Is it a common one? I've seen only a few post about it.

-nodje

jmcconnell wrote:
> 
> What operating system are you on?
> 
> On Fri, Mar 28, 2008 at 2:32 AM, nodje <nodje.co <at> gmail.com> wrote:
> 
>>
>> I've just added connectors to the Maven Jetty plugin default
>> configuration:
>>
>>                    <connectors>
>>                        <connector
>> implementation="org.mortbay.jetty.nio.SelectChannelConnector">
>>                            <port>8080</port>
>>                            <maxIdleTime>60000</maxIdleTime>
>>                        </connector>
>>                        <connector
>> implementation="org.mortbay.jetty.security.SslSocketConnector">
>>                            <port>8443</port>
>>                            <maxIdleTime>60000</maxIdleTime>
>>                            <keystore>metadata/keystore</keystore>
>>                            <password>****</password>

Re: [jetty-user] Global JNDI resource

As per http://docs.codehaus.org/display/JETTY/JNDI__
Do you have this in your web.xml?

<resource-ref>
    <description>My DataSource Reference</description>
    <res-ref-name>jdbc/DSTest</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
</resource-ref>

Silencium Sixty-Eight wrote:
> Hi,
>
> On 31.03.2008, at 04:35, David Yu wrote:
>> When referencing from your webapp, its java:comp/env/jdbc/DSTest
>> Have a read at http://docs.codehaus.org/display/JETTY/JNDI
> Okay!
>
> I now have modified my JSPWiki page accordingly (see below):
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+
> ----
> [{WikiSQL source='java:comp/env/jdbc/DSTest' 
>
> select * from roles order by role}]
> ----
> [{WikiSQL source='java:comp/env/jdbc/DSTest' class='grid' 
>
> select * from roles order by role}]
> ----

Re: [jetty-user] Maven plugin: weird message with Ssl and Select connector

Nodje,

The plugin recursively scans directories associated with your
webapp project to check for differences so that it can 
automatically redeploy the webapp when changes occur.

It looks like it is scanning a directory with lots and
lots of files/directories in it and runs out of file descriptors.
So the number of files could be very large, or perhaps the 
number of open file descriptors might be set to something rather 
small on your os. If you run it again and use a utility like lsof 
you can see the currently open files, and which process as them open.
You'll have to check the OSX doco to see how to read/set the number
of open files.

Have you specified any extra scanTargets in the jetty plugin
<configuration> element? Can you post the whole section
related to jetty? 

regards
Jan

nodje wrote:
> I'm on OS X 10.5.2.
> 
> Is the error OS dependent?
> Is it a common one? I've seen only a few post about it.
> 
> -nodje
> 

[jetty-user] cannot run test-ws-cxf example

Hi,

I got the latest code from trunk, and build it.  When run mvn
jetty:run, got the following

[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'jetty'.
Downloading: http://people.apache.org/repo/m2-incubating-repository/org/mortbay/jetty/maven-jetty-plugin/7.0-SNAPSHOT/ma
ven-jetty-plugin-7.0-SNAPSHOT.pom
Downloading: http://people.apache.org/repo/m2-incubating-repository/org/mortbay/jetty/maven-jetty-plugin/7.0-SNAPSHOT/ma
ven-jetty-plugin-7.0-SNAPSHOT.pom
Downloading: http://download.java.net/maven/2/org/mortbay/jetty/maven-jetty-plugin/7.0-SNAPSHOT/maven-jetty-plugin-7.0-S
NAPSHOT.pom
Downloading: http://snapshots.repository.codehaus.org/org/mortbay/jetty/maven-jetty-plugin/7.0-SNAPSHOT/maven-jetty-plug
in-7.0-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).

Project ID: org.mortbay.jetty:maven-jetty-plugin

Reason: POM 'org.mortbay.jetty:maven-jetty-plugin' not found in
repository: Unable to download the artifact from any rep
ository

  org.mortbay.jetty:maven-jetty-plugin:pom:7.0-SNAPSHOT

from the specified remote repositories:
  codehaus.org (http://snapshots.repository.codehaus.org),

Re: [jetty-user] Jetty and Cargo Remote Deployment

Matt,

so do you need anything to be added/changed in Jetty or are you happy
to start working with the context deployer?

regards

Matt Wringe wrote:
> On Wed, 2008-03-26 at 17:54 -0700, Greg Wilkins wrote:
>> Matt Wringe wrote:
>>> On Wed, 2008-03-26 at 14:21 -0700, Greg Wilkins wrote:
>>>> Matt,
>>>>
>>>> a very quick response... as I'm travelling for the next few days...
>>>>
>>>> Jetty can detect new web contexts at runtime, either via file discovery
>>>> or via JMX calls.   For details see the ContextDeployer page on the
>>>> wiki and perhaps start jetty in JMX mode and browse the JMX interfaces
>>>> with a jmx console.
>>>>
>>>> The main problem will be that jetty can be very flexible and
>>>> there are infinite deployment options and alternatives.  It may
>>>> be hard for cargo to adapt to all of them.
>>>>
>>>> It may be far simpler to create a CargoDeployer, based on the
>>>> other deployer - which gives a bit more structure and can mark
>>>> the jetty server as a target for cargo deployment.  I know
>>>> this needs some "special configuration" but it could be
>>>> done simply as an additive xml file:

[jetty-user] "Dispatch failed" causes Jetty to hang

Hello all,

We are using Jetty 6.1.1 to move files between components of an ActiveMQ
based messaging system (using DefaultServlet and the little bit of code for
uploading I contributed to Jetty some time ago). 

Under some load (large files, 50-100 simultanous requests) Jetty will hang.
That is, it stops processing any incoming HTTP requests. The Jetty process
is still alive. When it happens, this or a couple of these appear to log:

INFO   | jvm 1    | 2008/03/28 10:50:50 | 2008-03-28 10:50:50.064::WARN: 
dispatch failed for org.mortbay.jetty.HttpConnection <at> 7e5619

Why this might happen, and how we should go on to debug the problem?

Could it be related to number of open files?

Regards,
Aleksi
--

-- 
View this message in context: http://www.nabble.com/%22Dispatch-failed%22-causes-Jetty-to-hang-tp16418291p16418291.html
Sent from the Jetty Support mailing list archive at Nabble.com.

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

    http://xircles.codehaus.org/manage_email

Re: [jetty-user] Jetty and Cargo Remote Deployment

On Tue, 2008-04-01 at 22:18 +1100, Greg Wilkins wrote:
> Matt,
> 
> so do you need anything to be added/changed in Jetty or are you happy
> to start working with the context deployer?

I havn't really looked into it since last week,  but it is going to need
remote deployment capabilities to a remotely running server :(

I will let you know when I have started looking into it a bit more. I
was really hoping Jetty already had this capability built in :)

> 
> regards
> 
> 
> Matt Wringe wrote:
> > On Wed, 2008-03-26 at 17:54 -0700, Greg Wilkins wrote:
> >> Matt Wringe wrote:
> >>> On Wed, 2008-03-26 at 14:21 -0700, Greg Wilkins wrote:
> >>>> Matt,
> >>>>
> >>>> a very quick response... as I'm travelling for the next few days...
> >>>>
> >>>> Jetty can detect new web contexts at runtime, either via file discovery
> >>>> or via JMX calls.   For details see the ContextDeployer page on the
> >>>> wiki and perhaps start jetty in JMX mode and browse the JMX interfaces
> >>>> with a jmx console.
> >>>>

Re: [jetty-user] cannot run test-ws-cxf example