Jetty?

[wcwilson]

Should the deployment version work with Jetty? I know it is not certified. Is this because it does not work or just because it wasn't tested with that version?

--Wayne

[antun]

It is because we haven't tested on Jetty. You're welcome to give it a go if you are familiar with deploying web applications. If you decide to, let us know how you get on.

-Antun

[Anne]

I actually think we have tested on Jetty at the IBM Solutions Center and it was very fast. I'll ask our QA guy to weigh in with his tips re running the LPS on Jetty...

[mdavis]

We have tested Jetty 4.1.4 and found it to be quite capable. The primary configuration has been: Jetty 4.1.4 with Sun JDK 1.4.1 on Linux (Red Hat 8) and Windows 2000 Advanced Server.

One of the nice things about Jetty is that the config is as simple as Tomcat, but the performance and reliability characteristics are much better.

As we get more test coverage on the various servlet containers the upcoming releases will be certified for use in those containers.

Jetty was just recently brought into the lab and is not "officially certified" but I would put it in "tested compatible" category. There are a couple of gotchas with Jetty and JSP support that are covered in the Jetty docs but it handles the LPS well.


--md

:cool:

[wcwilson]

Great, good information. On Windows I have been happier in general with Jetty as I have found it to be more stable and compatible with the ear files I have deployed (of course I might have been doing something wrong). I haven't benchmarked performance but anecdotally I have heard it to be better.

--Wayne

[wcwilson]

I haven't had time to debug it yet, but if I drploy the .war file that came in lps-dr-core, lps deploys and runs fine. If I try to deploy the lps-dr directory, I get the following errors:

23:19:54,523 INFO [MainDeployer] Starting deployment of package: file:/C:/dev/laszlo/jboss-jetty/server/default/deploy/
lps-dr/
23:19:54,694 INFO [MainDeployer] deployment waiting for deployer: file:/C:/dev/laszlo/jboss-jetty/server/default/deploy
/lps-dr/
23:19:54,694 INFO [MainDeployer] Deployment of package: file:/C:/dev/laszlo/jboss-jetty/server/default/deploy/lps-dr/ i
s waiting for an appropriate deployer.
23:19:54,694 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
[org.jboss.deployment.DeploymentInfo@b7f6683c { url=file:/C:/dev/laszlo/jboss-jetty/server/default/deploy/lps-dr/ }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/dev/laszlo/jboss-jetty/server/default/deploy/lps-dr/
lastDeployed: 1043900394694
lastModified: 1043900365804
mbeans:
]Incompletely deployed packages:
[org.jboss.deployment.DeploymentInfo@b7f6683c { url=file:/C:/dev/laszlo/jboss-jetty/server/default/deploy/lps-dr/ }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/dev/laszlo/jboss-jetty/server/default/deploy/lps-dr/
lastDeployed: 1043900394694
lastModified: 1043900365804
mbeans:
]MBeans waiting for classes:
<none>
MBeans waiting for other MBeans:
<none>

I will pick it up again in the morning. Any hints?

--Wayne

[bloch]

Hey Wayne,

We really like Jetty, too.

We've only deployed in Jetty 4.1.4
by copying webapp directories into $JETTY_HOME/webapps.

That's worked flawlessly to date.

How are you deploying the directory?

From the looks of the following

lastDeployed: 1043900394694
lastModified: 1043900365804

I might make a guess that JBoss?
is confused about you moving from
a .war to an exploded dir or something
similar.

FYI, we've never used JBoss here
since we only require the servlet
container.

Best,

-Eric

[wcwilson]

I was using the JBoss/Jetty integrated package and deploying to \server\default\deploy\. It works with the .war, but not when just copying the directory. I even exploded the war and used it, but to no avail...

From your description it seems like the Jetty standalone has a diferent structure than the JBoss integrated version.

By the way, if you ever need an EJB server, JBoss has worked very well for us.

--Wayne

[bloch]

I googled a bit and found this
at the jboss.org site:

http://www.jboss.org/forums/thread.jsp?forum=137&thread=25058

Perhaps it may have to do
with CLASSPATH and/or jboss classloader
differences when using .wars and
exploded directories.

FYI, LPS does ship with a copy of
the axis jar noted in the thread above.

From the thread above, I'll venture a wild guess that this is a jboss 3 issue.

-Eric

[dwtung]

The problem is that when you deploy an exploded directory in JBoss you need to name the directory with a .war extension.