I have tracked this down to an invalidate manifest header in the org.mortbay.jetty.jar:
Manifest-Version: 1.0
MortBay-StandAlone-MortBay-StandAlone-MortBay-StandAlone-MortBay-Stand
Alone-Class-Path: javax.servlet.jar org.apache.jasper.jar ../ext/com.
sun.net.ssl.jar
Sealed: true
I am seeing this bad header generated on Windows XP, but not Windows 2000. Apparently
the token replacement is being done multiple times. Why is this needed? If I remove the
<replacefilter token="Class-Path" value="MortBay-StandAlone-Class-Path" />
line from the jetty/build.xml file the manifests are fine with the Class-Path
attribute and
the service starts up fine. I have commented this out from the build file for now.
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "Scott M Stark" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, August 31, 2002 8:15 AM
Subject: [JBoss-dev] Jetty won't start in current 3.0 build
> Running the default config in a clean build of the 3.0 branch fails to start Jetty.
>Please
> fix this:
>
> bin 257>run.sh
> ================================================================================
>
>
> JBoss Bootstrap Environment
>
> JBOSS_HOME: C:\usr\JBoss3.0\jboss-all\build\output\jboss-3.0.3RC1
>
> JAVA: /usr/local/Java/jdk1.3.1_04/bin/java
>
> JAVA_OPTS: -server -Dprogram.name=run.sh
>
> CLASSPATH: C:\usr\JBoss3.0\jboss-all\build\output\jboss-3.0.3RC1\bin\run.jar;C
> :\usr\local\Java\jdk1.3.1_04\lib\tools.jar
>
> ================================================================================
>
>
> 08:03:26,493 INFO [Server] JBoss Release: JBoss-3.0.3RC1 CVSTag=Branch_3_0
> 08:03:26,503 INFO [Server] Home Dir:
>C:\usr\JBoss3.0\jboss-all\build\output\jboss-3.0.3RC1
> ...
> 08:03:32,091 INFO [MainDeployer] Starting deployment of package: file:/C:/usr/
> Boss3.0/jboss-all/build/output/jboss-3.0.3RC1/server/default/deploy/jbossweb.sa/
> 08:03:32,562 ERROR [URLDeploymentScanner] Failed to deploy: org.jboss.deploymen
> .scanner.URLDeploymentScanner$DeployedURL@b65d1a72{
>
>url=file:/C:/usr/JBoss3.0/joss-all/build/output/jboss-3.0.3RC1/server/default/deploy/jbossweb.sar/,
> deploydLastModified=0 }
> org.jboss.deployment.DeploymentException: instantiating org.jboss.jetty.JettySe
> vice failed: java.lang.NoClassDefFoundError: org/mortbay/util/MultiException; -
> nested throwable: (RuntimeErrorException: instantiating org.jboss.jetty.JettySe
> vice failed: java.lang.NoClassDefFoundError: org/mortbay/util/MultiException
> Cause: java.lang.NoClassDefFoundError: org/mortbay/util/MultiException)
> at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.jav:155)
> at org.jboss.system.ServiceController.install(ServiceController.java:22)
> at java.lang.reflect.Method.invoke(Native Method)
> at
>org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBenDispatcher.java:284)
> at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
> at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
