yes..we just need to make the time to make the tweaks in the process thanks a ton for working out what was going on though! huge help
jesse -- jesse mcconnell [email protected] On Wed, Jan 19, 2011 at 09:34, Ruslans Tarasovs <[email protected]> wrote: > I got it working. > > The problem was that for some reason (I did not investigate why) > "jetty.conf" is being overwritten by the other one during the build > process. This other one contains the long comment and the following > line only. > > --pre=etc/jetty-logging.xml > > I added another line after the installation. > > etc/jetty.xml > > And now the server works properly! Another way to fix this is to edit > local "start.config" file and replace the following lines. > > # The default configuration files > $(jetty.home)/etc/jetty.xml nargs == 0 > > By something like following. > > # The default configuration files > $(jetty.home)/etc/jetty.xml always > > I still can't believe I did not notice that XML configuration was not > read at all. Now I am happy Jetty 7 user on Debian server again. I hope > very much that my investigation will help the maintainer of these > scripts to release the latest Debian version officially. > > Best regards, > Ruslans. > > > On Sat, 15 Jan 2011 20:44:51 +0200 > Ruslans Tarasovs <[email protected]> wrote: > >> Now I finally stuck. >> >> I found out how to get debug log. I need to add the following option >> to JVM parameters. >> -Dorg.eclipse.jetty.util.log.DEBUG=true >> >> However, the log was completely useless. >> >> start.log: >> >> Establishing start.log on Sat Jan 15 20:29:45 EET 2011 >> 2011-01-15 20:29:48.755:DBUG::Logging to StdErrLog::DEBUG=true via >> org.eclipse.jetty.util.log.StdErrLog 2011-01-15 >> 20:29:48.763:DBUG::parse: file:/etc/jetty/jetty-logging.xml 2011-01-15 >> 20:29:48.791:DBUG::parsing: >> sid=file:/etc/jetty/jetty-logging.xml,pid=null 2011-01-15 >> 20:29:48.928:DBUG::resolveEntity(-//Jetty//Configure//EN, >> http://www.eclipse.org/jetty/configure.dtd) 2011-01-15 >> 20:29:48.935:DBUG::Redirected entity >> http://www.eclipse.org/jetty/configure.dtd --> >> jar:file:/usr/share/java/jetty-xml-7.1.6.v20100715.jar!/org/eclipse/jetty/xml/configure_6_0.dtd >> 2011-01-15 20:29:49.581:DBUG::XML call getTimeZone 2011-01-15 >> 20:29:49.597:DBUG::XML new class >> org.eclipse.jetty.util.RolloverFileOutputStream 2011-01-15 >> 20:29:49.644:DBUG::XML get datedFilename 2011-01-15 >> 20:29:49.646:DBUG::XML new class java.io.PrintStream 2011-01-15 >> 20:29:49.651:DBUG::XML call info 2011-01-15 >> 20:29:49.658:INFO::Redirecting stderr/stdout >> to /var/log/jetty/2011_01_15.stderrout.log 2011-01-15 >> 20:29:49.661:DBUG::XML call setErr >> >> 2011_01_15.stderrout.log: >> >> 2011-01-15 20:29:49.672:DBUG::XML call setOut >> 2011-01-15 20:29:49.676:DBUG::Starting >> org.eclipse.jetty.server.Server@c3014 2011-01-15 >> 20:29:49.678:INFO::jetty-7.1.6.v20100715 2011-01-15 >> 20:29:50.103:DBUG::Container org.eclipse.jetty.server.Server@c3014 + >> qtp32826737{8<=0<=0/254,-1} as threadpool 2011-01-15 >> 20:29:50.106:DBUG::Starting qtp32826737{8<=0<=0/254,-1} 2011-01-15 >> 20:29:50.150:DBUG::STARTED qtp32826737{8<=7<=8/254,0} 2011-01-15 >> 20:29:50.152:DBUG::starting org.eclipse.jetty.server.Server@c3014 >> org.eclipse.jetty.server.Server@c3014 STOPPED >> >> 2011-01-15 20:29:50.170:DBUG::STARTED >> org.eclipse.jetty.server.Server@c3014 >> >> I also tried to debug the server and I got something like following: >> >> root@server:~/install# jdb -attach 4000 >> Set uncaught java.lang.Throwable >> Set deferred uncaught java.lang.Throwable >> Initializing jdb ... >> > threads >> Group system: >> (java.lang.ref.Reference$ReferenceHandler)0x364 Reference >> Handler cond. waiting >> (java.lang.ref.Finalizer$FinalizerThread)0x363 >> Finalizer cond. waiting >> (java.lang.Thread)0x362 Signal >> Dispatcher running Group main: >> (java.util.TimerThread)0x361 >> org.eclipse.jetty.util.RolloverFileOutputStream cond. waiting >> (java.lang.Thread)0x387 >> qtp25421790-11 cond. waiting >> (java.lang.Thread)0x388 >> qtp25421790-12 cond. waiting >> (java.lang.Thread)0x38d >> qtp25421790-13 cond. waiting >> (java.lang.Thread)0x38c >> qtp25421790-14 cond. waiting >> (java.lang.Thread)0x38f >> qtp25421790-15 cond. waiting >> (java.lang.Thread)0x38e >> qtp25421790-16 cond. waiting >> (java.lang.Thread)0x396 >> qtp25421790-17 cond. waiting >> (java.lang.Thread)0x397 >> qtp25421790-18 cond. waiting >> (java.lang.Thread)0x399 >> DestroyJavaVM running >> > >> >> I can not connect to 8080 port and it nothing happens... >> >> No Jetty 7 for me :( >> >> Best regards, >> Ruslans. >> >> On Sat, 15 Jan 2011 16:13:31 +0200 >> Ruslans Tarasovs <[email protected]> wrote: >> >> > The error cause was "start.config" file. >> > >> > I changed the following line. >> > [All,default] >> > >> > To the following. >> > [All,default,*] >> > >> > And the error disappeared. However Jetty does not work anyway. It >> > just says the following and just hangs and does nothing. >> > >> > 2011-01-15 15:58:09.109:INFO::Redirecting stderr/stdout >> > to /var/log/jetty/2011_01_15.stderrout.log >> > >> > That file only contains the following: >> > 2011-01-15 15:58:09.118:INFO::jetty-7.2.2.v20101205 >> > >> > Any help on how to make him more verbose? I tried -DDEBUG, but it >> > does not seem to work. >> > >> > Best regards, >> > Ruslans. >> > >> > On Sat, 15 Jan 2011 13:43:33 +0200 >> > Ruslans Tarasovs <[email protected]> wrote: >> > >> > > Wow, I was finally able to build Jetty 7.2.2. >> > > >> > > Here is what I did: >> > > >> > > 1. Download debian distribution from SVN repository: >> > > http://svn.codehaus.org/jetty-contrib/packaging/debian/trunk/jetty7/ >> > > >> > > 2. Update "changelog" to the latest version (I had to do this >> > > manually, I do not know if you have any scripts for that). >> > > >> > > 3. Run "getsource.sh" to get the latest source. >> > > >> > > 4. Extract the source to the current directory. >> > > tar xzf jetty_7.2.2.v20101205.orig.tar.gz >> > > >> > > 5. Do a full build inside of the extracted directory. >> > > cd jetty-7.2.2.v20101205 >> > > mvn install -Dmaven.test.skip=true >> > > >> > > 6. Download linux packaging plugin from SVN repository: >> > > http://svn.codehaus.org/jetty-contrib/packaging/tools/trunk/jetty-linux-packaging-maven-plugin/ >> > > >> > > 7. Build and install a plugin. >> > > mvn install >> > > >> > > 8. Go back to the server I built in (5). Use the new plugin there. >> > > mvn >> > > org.codehaus.jetty.plugins:jetty-linux-packaging-maven-plugin:generate-patch >> > > >> > > 9. Replace "linux-packaging.patch" in "../debian/patches" by the >> > > one built in target directory. >> > > >> > > 10. Edit "linux-packaging.patch" with VI and run the following >> > > command. >> > > %s/<jar destfile="\([^\/]*\)\//<jar >> > > manifest="\1\/src\/main\/resources\/META-INF\/MANIFEST.MF" >> > > destfile="\1\//g >> > > >> > > 11. Run "build.sh" in the original directory. >> > > sh reset-build.sh; sh getsource.sh; sh build.sh >> > > >> > > If someone only wants to build a 7.2.2 version then it is enough >> > > to copy changelog and linux-packaging.patch I attached to this >> > > e-mail to proper places. No need to go through all of this. Do >> > > not forget to replace "/home/ruslan/" in "linux-packaging.patch" >> > > by "/home/${user.name}/". >> > > >> > > But I still get the same error when trying to start the server. It >> > > says the following: >> > > >> > > java.lang.IllegalArgumentException: No such OPTIONS: * >> > > at >> > > org.eclipse.jetty.start.Config.getCombinedClasspath(Config.java:400) >> > > at >> > > org.eclipse.jetty.start.Config.getActiveClasspath(Config.java:377) >> > > at org.eclipse.jetty.start.Main.start(Main.java:526) at >> > > org.eclipse.jetty.start.Main.parseCommandLine(Main.java:273) at >> > > org.eclipse.jetty.start.Main.main(Main.java:81) >> > > >> > > I guess I will need to dig into sources now unless someone will >> > > help me :) >> > > >> > > Best regards, >> > > Ruslans. >> > > >> > > >> > > On Sat, 15 Jan 2011 01:22:01 +0200 Ruslans Tarasovs >> > > <[email protected]> wrote: >> > > >> > > > Thanks, I could write a patch for that generator then. >> > > > >> > > > http://svn.codehaus.org/jetty-contrib/packaging/tools/trunk/jetty-linux-packaging-maven-plugin/src/main/java/org/codehaus/jetty/plugin/linux/AntBuildWriter.java >> > > > >> > > > The idea is that the following line >> > > > >> > > > printf(" <jar destfile=\"%s\">%n",jarPath); >> > > > >> > > > should be replaced to something like following >> > > > >> > > > printf(" <jar destfile=\"%s\" >> > > > manifest=\"%s\">%n",jarPath,manifestPath); >> > > > >> > > > That manifestPath should be something like >> > > > "src/main/resources/META-INF/MANIFEST.MF" >> > > > >> > > > It should be relatively easy to get it from the list of >> > > > resources. >> > > > >> > > > Do you need such patch? >> > > > >> > > > Best regards, >> > > > Ruslans. >> > > > >> > > > >> > > > >> > > > On Fri, 14 Jan 2011 16:04:51 -0700 >> > > > Joakim Erdfelt <[email protected]> wrote: >> > > > >> > > > > The linux-packaging.patch is generated by the >> > > > > jetty-linux-packaging-maven-plugin. >> > > > > >> > > > > http://svn.codehaus.org/jetty-contrib/packaging/tools/trunk/jetty-linux-packaging-maven-plugin/ >> > > > > >> > > > > The one checked in, is not the one used. >> > > > > >> > > > > -Joakim >> > > > > >> > > > > On Fri, Jan 14, 2011 at 4:01 PM, Ruslans Tarasovs >> > > > > <[email protected]>wrote: >> > > > > >> > > > > > Hi. >> > > > > > >> > > > > > I finally found a way to compile Jetty 7 from sources >> > > > > > properly and I also found a reason why the people have >> > > > > > problem with running it on Debian. >> > > > > > >> > > > > > The problem is that the packaging Ant script provided in >> > > > > > "linux-packaging.patch" uses "jar" task without manifest >> > > > > > specified. That why Ant creates an empty manifest instead of >> > > > > > using the predefined one. I have attached fixed patch that >> > > > > > has the jar task defined properly. >> > > > > > >> > > > > > To build the Jetty 7 properly I did the following: >> > > > > > >> > > > > > 1. Replaced "/home/jesse/" by "/home/${user.name}/" in >> > > > > > "linux-packaging.patch". >> > > > > > 2. Copied all libraries from >> > > > > > "jetty-distribution-7.1.6.v20100715.zip" to >> > > > > > "~/.m2/eclipse-orbit". 3. Made a symbolic link from >> > > > > > "servlet-api-2.5.jar" to >> > > > > > "javax.servlet_2.5.0.v200910301333.jar" in the same >> > > > > > directory. 4. Run "getsource.sh" and "build.sh". >> > > > > > >> > > > > > I hope you will find the changes I did to the patch useful. >> > > > > > >> > > > > > Nevertheless, after all this I still get the following error >> > > > > > message when trying to start Jetty (it is being written to >> > > > > > "/var/log/jetty/start.log"): >> > > > > > >> > > > > > java.lang.IllegalArgumentException: No such OPTIONS: * >> > > > > > at >> > > > > > org.eclipse.jetty.start.Config.getCombinedClasspath(Config.java:393) >> > > > > > at >> > > > > > org.eclipse.jetty.start.Config.getActiveClasspath(Config.java:370) >> > > > > > at org.eclipse.jetty.start.Main.start(Main.java:536) at >> > > > > > org.eclipse.jetty.start.Main.parseCommandLine(Main.java:280) >> > > > > > at org.eclipse.jetty.start.Main.main(Main.java:82) Use java >> > > > > > -jar start.jar --help for usage information. >> > > > > > >> > > > > > Could it be related to >> > > > > > "http://jira.codehaus.org/browse/JETTY-1305";? >> > > > > > >> > > > > > Best regards, >> > > > > > Ruslans. >> > > > > > >> > > > > > On Sun, 09 Jan 2011 16:53:14 +0200 >> > > > > > Ruslans Tarasovs <ruslan@xxxxxxxxx> wrote: >> > > > > > >> > > > > > > Hi. >> > > > > > > >> > > > > > > I have tried to use the files you uploaded, but these >> > > > > > > still have exactly the same problem as described below. >> > > > > > > There is no main class description embedded into metainf >> > > > > > > file. >> > > > > > > >> > > > > > > I also tried to replace take that "start.jar" file from >> > > > > > > the latest non-debian distribution, but I got the error >> > > > > > > message that says that * is an invalid OPTIONS parameter. >> > > > > > > >> > > > > > > Another thing I tried is to build DEB files from the >> > > > > > > source, but there are some hardcoded paths >> > > > > > > (like /home/jesse). I did try to replace them, but there >> > > > > > > are seems to be more dependencies, so I did not have a >> > > > > > > successful build yet. >> > > > > > > >> > > > > > > Do you need anything else to know? I would be happy to >> > > > > > > help :) >> > > > > > > >> > > > > > > Best regards, >> > > > > > > Ruslans. >> > > > > > > > I have uploaded the 7.2.1.v20101111 debian files.. >> > > > > > > > >> > > > > > > > let me know if you have any issues with them and we'll >> > > > > > > > try and get them sorted out >> > > > > > > > >> > > > > > > > http://dist.codehaus.org/jetty/deb/ >> > > > > > > > >> > > > > > > > cheers, >> > > > > > > > jesse >> > > > > > > > >> > > > > > > > -- >> > > > > > > > jesse mcconnell >> > > > > > > > jesse.mcconnell@xxxxxxxxx >> > > > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > > > On Thu, Nov 4, 2010 at 05:39, Jesse >> > > > > > > > McConnell<jesse.mcconnell@xxxxxxxxx> wrote: >> > > > > > > > > that is correct, >> > > > > > > > > >> > > > > > > > > the deb build is ultimately targeted to be picked up >> > > > > > > > > and used by deb distributions and those distributions >> > > > > > > > > won't pickup artifacts from a repo like that...they >> > > > > > > > > have to be built....and since they don't build with >> > > > > > > > > maven the debs are produced by a patched ant build. >> > > > > > > > > >> > > > > > > > > cheers, >> > > > > > > > > jesse >> > > > > > > > > >> > > > > > > > > -- >> > > > > > > > > jesse mcconnell >> > > > > > > > > jesse.mcconnell@xxxxxxxxx >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > On Thu, Nov 4, 2010 at 05:33, AS >> > > > > > > > > Maps<as.maps@xxxxxxxxx> wrote: >> > > > > > > > >> So the deb packaging does not seem to make use of >> > > > > > > > >> the Maven >> > > > > > > > artifacts. >> > > > > > > > >> >> > > > > > > > >> MANIFEST.MF of >> > > > > > > > >> org.eclipse.jetty:jetty-start:jar:7.2.0.v20101020 >> > > > > > > > consists of >> > > > > > > > >> the following lines >> > > > > > > > >> >> > > > > > > > >> Manifest-Version: 1.0 >> > > > > > > > >> Archiver-Version: Plexus Archiver >> > > > > > > > >> Created-By: Apache Maven >> > > > > > > > >> Built-By: jesse >> > > > > > > > >> Build-Jdk: 1.6.0_19 >> > > > > > > > >> Main-Class: org.eclipse.jetty.start.Main >> > > > > > > > >> Implementation-Vendor: Eclipse.org - Jetty >> > > > > > > > >> Implementation-Version: 7.2.0.v20101020 >> > > > > > > > >> url:http://www.eclipse.org/jetty >> > > > > > > > >> >> > > > > > > > >> Everything is fine with this manifest. What made me >> > > > > > > > >> come to this >> > > > > > > > idea was >> > > > > > > > >> the modification date of jetty-start.jar inside the >> > > > > > > > >> deb archive. >> > > > > > > > It is >> > > > > > > > >> 2010-10-27, creation date is 2010-11-04. >> > > > > > > > >> >> > > > > > > > >> I don't know how the deb build is done exactly, but >> > > > > > > > >> to my opinion >> > > > > > > > it doesn't >> > > > > > > > >> use any maven-ly produced artifacts. >> > > > > > > > >> >> > > > > > > > >> BTW: Have a good trip. >> > > > > > > > >> >> > > > > > > > >> Andreas >> > > > > > > > >> >> > > > > > > > >> On Thu, Nov 4, 2010 at 11:22 AM, Jesse >> > > > > > > > McConnell<jesse.mcconnell@xxxxxxxxx> >> > > > > > > > >> wrote: >> > > > > > > > >>> >> > > > > > > > >>> >> > > > > > > > >>> >> > > > > > > > >> > > > > > http://repo2.maven.org/maven2/org/eclipse/jetty/jetty-distribution/7.2.0.v20101020/ >> > > > > > > > >> > > > > > > > >>> >> > > > > > > > >>> you can have up a couple of dirs and go down the >> > > > > > > > >>> jetty-start path >> > > > > > > > for >> > > > > > > > >>> a new start.jar (just rename it) >> > > > > > > > >>> >> > > > > > > > >>> past that, looks like I'll have to dig into it >> > > > > > > > >>> later (traveling atm) >> > > > > > > > >>> >> > > > > > > > >>> jesse >> > > > > > > > >>> >> > > > > > > > >>> -- >> > > > > > > > >>> jesse mcconnell >> > > > > > > > >>> jesse.mcconnell@xxxxxxxxx >> > > > > > > > >>> >> > > > > > > > >>> >> > > > > > > > >>> >> > > > > > > > >>> On Thu, Nov 4, 2010 at 05:17, AS >> > > > > > > > >>> Maps<as.maps@xxxxxxxxx> wrote: >> > > > > > > > >>> > Hey Jesse, >> > > > > > > > >>> > >> > > > > > > > >>> > thanks for uploading. >> > > > > > > > >>> > >> > > > > > > > >>> > Unfortunately this is the content of >> > > > > > > > >>> > jetty-start.jar\META-INF\MANIFEST.MF >> > > > > > > > >>> > >> > > > > > > > >>> > Manifest-Version: 1.0 >> > > > > > > > >>> > Ant-Version: Apache Ant 1.8.1 >> > > > > > > > >>> > Created-By: 1.6.0_0-b11 (Sun Microsystems Inc.) >> > > > > > > > >>> > >> > > > > > > > >>> > Where to check the artifacts in Maven repo (if >> > > > > > > > >>> > any)? >> > > > > > > > >>> > >> > > > > > > > >>> > Regards >> > > > > > > > >>> > Andreas >> > > > > > > > >>> > >> > > > > > > > >>> > On Thu, Nov 4, 2010 at 11:02 AM, Jesse McConnell >> > > > > > > > >>> > <jesse.mcconnell@xxxxxxxxx> >> > > > > > > > >>> > wrote: >> > > > > > > > >>> >> >> > > > > > > > >>> >> I have uploaded a hopefully uncorrupted file so >> > > > > > > > >>> >> hopefully that >> > > > > > > > will >> > > > > > > > >>> >> address one of those issues...and ideally both. >> > > > > > > > >>> >> >> > > > > > > > >>> >> If the missing main class line in the start.jar >> > > > > > > > >>> >> is still a >> > > > > > > > problem >> > > > > > > > >>> >> then I'll have to dig into the deb generation >> > > > > > > > >>> >> process and see >> > > > > > > > what >> > > > > > > > >>> >> might have gone wrong, the 7.2.0 distribution >> > > > > > > > >>> >> itself is just >> > > > > > > > fine. >> > > > > > > > >>> >> >> > > > > > > > >>> >> let me know if you still have issues after >> > > > > > > > >>> >> trying to newly >> > > > > > > > uploaded >> > > > > > > > >>> >> jars >> > > > > > > > >>> >> >> > > > > > > > >>> >> md5 sums are: >> > > > > > > > >>> >> >> > > > > > > > >>> >> 1c700bdb09ac370472435631b9b85679 >> > > > > > > > >>> >> Âjetty_7.2.0.v20101020_all.deb >> > > > > > > > >>> >> 3238348f24cb7534cb112ae1144edb31 >> > > > > > > > Âlibjetty-java_7.2.0.v20101020_all.deb >> > > > > > > > >>> >> 9e984ab0954fefedfe80b26f08a18f27 >> > > > > > > > >>> >> Âlibjetty-java-doc_7.2.0.v20101020_all.deb >> > > > > > > > >>> >> >> > > > > > > > >>> >> jesse >> > > > > > > > >>> >> -- >> > > > > > > > >>> >> jesse mcconnell >> > > > > > > > >>> >> jesse.mcconnell@xxxxxxxxx >> > > > > > > > >>> >> >> > > > > > > > >>> >> >> > > > > > > > >>> >> >> > > > > > > > >>> >> On Wed, Nov 3, 2010 at 11:38, Don >> > > > > > > > >>> >> Santillan<donzymeth@xxxxxxxxx> wrote: >> > > > > > > > >>> >> > This is different in my case. I have 40kb for >> > > > > > > > >>> >> > the start.jar and looking >> > > > > > > > >>> >> > in >> > > > > > > > >>> >> > the manifest file for it, I found that it is >> > > > > > > > >>> >> > missing its >> > > > > > > > main-class >> > > > > > > > >>> >> > property. >> > > > > > > > >>> >> > >> > > > > > > > >>> >> > Manifest-Version: 1.0 >> > > > > > > > >>> >> > Ant-Version: Apache Ant 1.8.1 >> > > > > > > > >>> >> > Created-By: 1.6.0_0-b11 (Sun Microsystems >> > > > > > > > >>> >> > Inc.) >> > > > > > > > >>> >> > >> > > > > > > > >>> >> > So what I did was to add the main-class into >> > > > > > > > >>> >> > the manifest >> > > > > > > > file, such >> > > > > > > > >>> >> > as >> > > > > > > > >>> >> > this: >> > > > > > > > >>> >> > >> > > > > > > > >>> >> > Manifest-Version: 1.0 >> > > > > > > > >>> >> > Ant-Version: Apache Ant 1.8.1 >> > > > > > > > >>> >> > Main-Class: org.eclipse.jetty.start.Main >> > > > > > > > >>> >> > Created-By: 1.6.0_0-b11 (Sun Microsystems >> > > > > > > > >>> >> > Inc.) >> > > > > > > > >>> >> > >> > > > > > > > >>> >> > This time, the command found the main class >> > > > > > > > >>> >> > but still >> > > > > > > > produced an >> > > > > > > > >>> >> > error: >> > > > > > > > >>> >> > >> > > > > > > > >>> >> > prompt$ /usr/bin/java >> > > > > > > > >>> >> > -DSTART=/usr/share/jetty/etc/start.config >> > > > > > > > >>> >> > -Xmx256m -Djava.awt.headless=true >> > > > > > > > >>> >> > >> > > > > > > > >>> >> > >> > > > > > > > -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog >> > > > > > > > >>> >> > -Djetty.port=8080 >> > > > > > > > >>> >> > -Djetty.home=/usr/share/jetty >> > > > > > > > -Djava.io.tmpdir=/tmp >> > > > > > > > >>> >> > -jar >> > > > > > > > >>> >> > /usr/share/jetty/start.jar >> > > > > > > > >>> >> > --pre=etc/jetty-logging.xml >> > > > > > > > >>> >> > java.lang.IllegalArgumentException: No such >> > > > > > > > >>> >> > OPTIONS: Server  at >> > > > > > > > >>> >> > >> > > > > > > > org.eclipse.jetty.start.Config.getCombinedClasspath(Config.java:400) >> > > > > > > > >>> >> >  at >> > > > > > > > >>> >> > >> > > > > > > > org.eclipse.jetty.start.Config.getActiveClasspath(Config.java:377) >> > > > > > > > >>> >> >  at >> > > > > > > > >>> >> > org.eclipse.jetty.start.Main.start(Main.java:536) >> > > > > > > > >>> >> >  at >> > > > > > > > org.eclipse.jetty.start.Main.parseCommandLine(Main.java:280) >> > > > > > > > >>> >> >  at >> > > > > > > > >>> >> > org.eclipse.jetty.start.Main.main(Main.java:82) >> > > > > > > > >>> >> > Use java -jar start.jar --help for usage >> > > > > > > > >>> >> > information. prompt$ >> > > > > > > > >>> >> > >> > > > > > > > >>> >> > -don >> > > > > > > > >>> >> > >> > > > > > > > >>> >> > AS Maps wrote: >> > > > > > > > >>> >> > >> > > > > > > > >>> >> > I examined the jar inside of the deb file >> > > > > > > > libjetty-java_*_all.deb and >> > > > > > > > >>> >> > it >> > > > > > > > >>> >> > turned out that its size is 0 bytes. >> > > > > > > > >>> >> > So there is rarely any file inside this >> > > > > > > > >>> >> > obviously corrupted >> > > > > > > > file. >> > > > > > > > >>> >> > >> > > > > > > > >>> >> > Maybe a new build must be done. >> > > > > > > > >>> >> > >> > > > > > > > >>> >> > On Wed, Nov 3, 2010 at 4:33 PM, Don >> > > > > > > > Santillan<donzymeth@xxxxxxxxx> >> > > > > > > > >>> >> > wrote: >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> Hello, >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> I'm having problems starting jetty >> > > > > > > > >>> >> >> 7.2.0.v20101020 right after installation. >> > > > > > > > >>> >> >> Here's what I did so far. >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> 1. Download the following deb files: >> > > > > > > > >>> >> >>  a. wget >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> >> > > > > > > > >> > > > > > http://dist.codehaus.org/jetty/deb/7.2.0.v20101020/jetty_7.2.0.v20101020_all.deb >> > > > > > > > >> > > > > > > > >>> >> >>  b. wget >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> >> > > > > > > > >> > > > > > http://dist.codehaus.org/jetty/deb/7.2.0.v20101020/libjetty-java-doc_7.2.0.v20101020_all.deb >> > > > > > > > >> > > > > > > > >>> >> >>  c. wget >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> >> > > > > > > > >> > > > > > http://dist.codehaus.org/jetty/deb/7.2.0.v20101020/libjetty-java_7.2.0.v20101020_all.deb >> > > > > > > > >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> 2. Make downloaded deb files executable: >> > > > > > > > >>> >> >>  a. chmod +x jetty_7.2.0.v20101020_all.deb >> > > > > > > > >>> >> >>  b. chmod +x >> > > > > > > > >>> >> >> libjetty-java-doc_7.2.0.v20101020_all.deb  >> > > > > > > > >>> >> >> c. chmod +x >> > > > > > > > >>> >> >> libjetty-java_7.2.0.v20101020_all.deb >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> 3. Installed the deb files in the following >> > > > > > > > >>> >> >> order:  a. sudo dpkg -i >> > > > > > > > >>> >> >> libjetty-java-doc_7.2.0.v20101020_all.deb >> > > > > > > > >>> >> >> (Reading database ... 328484 files and >> > > > > > > > >>> >> >> directories currently installed.) Preparing to >> > > > > > > > >>> >> >> replace libjetty-java-doc 6.1.20-2 (using >> > > > > > > > >>> >> >> libjetty-java-doc_7.2.0.v20101020_all.deb) ... >> > > > > > > > >>> >> >> Unpacking replacement libjetty-java-doc ... >> > > > > > > > >>> >> >> Setting up libjetty-java-doc >> > > > > > > > >>> >> >> (7.2.0.v20101020) ... Processing triggers for >> > > > > > > > >>> >> >> doc-base ... Processing 1 removed doc-base >> > > > > > > > >>> >> >> file(s)... Registering documents with >> > > > > > > > >>> >> >> scrollkeeper... >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >>  b. sudo dpkg -i >> > > > > > > > >>> >> >> libjetty-java_7.2.0.v20101020_all.deb (Reading >> > > > > > > > >>> >> >> database ... 328672 files and directories >> > > > > > > > >>> >> >> currently installed.) Preparing to replace >> > > > > > > > >>> >> >> libjetty-java 6.1.20-2 (using >> > > > > > > > >>> >> >> libjetty-java_7.2.0.v20101020_all.deb) ... >> > > > > > > > >>> >> >> Unpacking replacement libjetty-java ... >> > > > > > > > >>> >> >> Setting up libjetty-java (7.2.0.v20101020) ... >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >>  c. sudo dpkg -i >> > > > > > > > >>> >> >> jetty_7.2.0.v20101020_all.deb (Reading >> > > > > > > > >>> >> >> database ... 328763 files and directories >> > > > > > > > >>> >> >> currently installed.) Preparing to replace >> > > > > > > > >>> >> >> jetty 7.2.0.v20101020 (using >> > > > > > > > >>> >> >> jetty_7.2.0.v20101020_all.deb) ... Unpacking >> > > > > > > > >>> >> >> replacement jetty ... Setting up jetty >> > > > > > > > >>> >> >> (7.2.0.v20101020) ... Adding system user >> > > > > > > > >>> >> >> `jetty' (UID 117) ... Adding new group >> > > > > > > > >>> >> >> `jetty' (GID 127) ... Adding new user >> > > > > > > > >>> >> >> `jetty' (UID 117) with group `jetty' ... Not >> > > > > > > > >>> >> >> creating home directory `/usr/share/jetty'. >> > > > > > > > >>> >> >> update-rc.d: warning: /etc/init.d/jetty >> > > > > > > > >>> >> >> missing LSB >> > > > > > > > information >> > > > > > > > >>> >> >> update-rc.d: >> > > > > > > > >>> >> >> see<http://wiki.debian.org/LSBInitScripts> >> > > > > > > > >>> >> >> Starting Jetty: Not starting jetty - >> > > > > > > > >>> >> >> NO_START=1 >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> Processing triggers for ureadahead ... >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> 4. Change the following >> > > > > > > > >>> >> >> in /etc/default/jetty:  a. NO_START=1 to >> > > > > > > > >>> >> >> NO_START=0  b. UNcommented JETTY.PORT=8080 >> > > > > > > > >>> >> >>  c. set JAVA_HOME=/usr/lib/jvm/java-6-sun >> > > > > > > > >>> >> >> 5. Run jetty: >> > > > > > > > >>> >> >>  a. sudo /etc/init.d/jetty start >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> 6. Here's what I got: >> > > > > > > > >>> >> >> Starting Jetty: FAILED >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> 7. Run "sudo /etc/init.d/jetty check" and >> > > > > > > > >>> >> >> here's what I got: Checking arguments to >> > > > > > > > >>> >> >> Jetty: JETTY_HOME = /usr/share/jetty >> > > > > > > > >>> >> >> JETTY_CONF >> > > > > > > > >>> >> >> = /usr/share/jetty/etc/jetty.conf >> > > > > > > > >>> >> >> JETTY_RUN = /var/run JETTY_PID >> > > > > > > > >>> >> >> = /var/run/jetty.pid JETTY_PORT = 8080 >> > > > > > > > >>> >> >> JETTY_LOGS = >> > > > > > > > >>> >> >> START_INI = >> > > > > > > > >>> >> >> CONFIGS = --pre=etc/jetty-logging.xml >> > > > > > > > >>> >> >> JAVA_OPTIONS = >> > > > > > > > >>> >> >> -DSTART=/usr/share/jetty/etc/start.config >> > > > > > > > -Xmx256m >> > > > > > > > >>> >> >> -Djava.awt.headless=true >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> >> > > > > > > > -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog >> > > > > > > > >>> >> >> -Djetty.port=8080 >> > > > > > > > >>> >> >> -Djetty.home=/usr/share/jetty >> > > > > > > > >>> >> >> -Djava.io.tmpdir=/tmp JAVA >> > > > > > > > >>> >> >> = /usr/bin/java CLASSPATH = >> > > > > > > > >>> >> >> RUN_CMD = /usr/bin/java >> > > > > > > > >>> >> >> -DSTART=/usr/share/jetty/etc/start.config >> > > > > > > > >>> >> >> -Xmx256m -Djava.awt.headless=true >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> >> > > > > > > > -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog >> > > > > > > > >>> >> >> -Djetty.port=8080 >> > > > > > > > >>> >> >> -Djetty.home=/usr/share/jetty >> > > > > > > > >>> >> >> -Djava.io.tmpdir=/tmp -jar >> > > > > > > > >>> >> >> /usr/share/jetty/start.jar >> > > > > > > > >>> >> >> --pre=etc/jetty-logging.xml >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> Jetty running pid=24388 >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> * Notice the running pid=24388 line. This >> > > > > > > > >>> >> >> means the pid was >> > > > > > > > created. >> > > > > > > > >>> >> >> But >> > > > > > > > >>> >> >> going tohttp://localhost:8080 >> > > > > > > > >>> >> >> <http://localhost:8080/> >> > > > > > > > shows the service is offline. >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> 8. Run the following command on a separate >> > > > > > > > >>> >> >> terminal: /usr/bin/java >> > > > > > > > >>> >> >> -DSTART=/usr/share/jetty/etc/start.config >> > > > > > > > -Xmx256m >> > > > > > > > >>> >> >> -Djava.awt.headless=true >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> >> > > > > > > > -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog >> > > > > > > > >>> >> >> -Djetty.port=8080 >> > > > > > > > >>> >> >> -Djetty.home=/usr/share/jetty >> > > > > > > > >>> >> >> -Djava.io.tmpdir=/tmp -jar >> > > > > > > > >>> >> >> /usr/share/jetty/start.jar >> > > > > > > > >>> >> >> --pre=etc/jetty-logging.xml >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> Shows the following: >> > > > > > > > >>> >> >> Failed to load Main-Class manifest attribute >> > > > > > > > >>> >> >> from /usr/share/jetty/start.jar >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> 9. Here's my jetty home directory listing >> > > > > > > > >>> >> >> at /usr/share/jetty: total 28 >> > > > > > > > >>> >> >> drwxr-xr-x 4 root root 4096 2010-11-03 >> > > > > > > > >>> >> >> 23:30 . drwxr-xr-x 353 root root 12288 >> > > > > > > > >>> >> >> 2010-10-27 13:41 .. lrwxrwxrwx 1 root >> > > > > > > > >>> >> >> root 19 2010-11-03 22:58 contexts >> > > > > > > > >>> >> >> -> /etc/jetty/contexts lrwxrwxrwx 1 root >> > > > > > > > >>> >> >> root 10 2010-11-03 22:58 etc -> >> > > > > > > > /etc/jetty >> > > > > > > > >>> >> >> lrwxrwxrwx 1 root root 24 2010-11-03 >> > > > > > > > >>> >> >> 22:59 javadoc -> ../doc/libjetty-java/api >> > > > > > > > >>> >> >> drwxr-xr-x 5 root root 4096 2010-11-03 >> > > > > > > > >>> >> >> 22:59 lib lrwxrwxrwx 1 root root 14 >> > > > > > > > >>> >> >> 2010-11-03 22:58 logs -> /var/log/jetty >> > > > > > > > >>> >> >> drwxr-xr-x 2 root root 4096 2010-11-03 >> > > > > > > > >>> >> >> 22:59 resources -rw-rw-r-- 1 root root 2010 >> > > > > > > > >>> >> >> 2010-11-03 23:30 start.ini lrwxrwxrwx 1 root >> > > > > > > > >>> >> >> root 39 2010-11-03 22:59 start.jar >> > > > > > > > >>> >> >> -> ../java/jetty-start-7.2.0.v20101020.jar >> > > > > > > > >>> >> >> lrwxrwxrwx 1 root root 22 2010-11-03 >> > > > > > > > >>> >> >> 22:58 webapps -> /var/lib/jetty/webapps >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> Is there a problem with the manifest file of >> > > > > > > > >>> >> >> /usr/share/jetty/start.jar? >> > > > > > > > >>> >> >> What seems to be the problem? >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> -don >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> >> _______________________________________________ >> > > > > > > > >>> >> >> jetty-users mailing list >> > > > > > > > >>> >> >> jetty-users@xxxxxxxxxxx >> > > > > > > > >>> >> >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> > > > > > > > >>> >> >> >> > > > > > > > >>> >> > >> > > > > > > > >>> >> > ________________________________ >> > > > > > > > >>> >> > _______________________________________________ >> > > > > > > > >>> >> > jetty-users mailing list >> > > > > > > > >>> >> > jetty-users@xxxxxxxxxxx >> > > > > > > > >>> >> > https://dev.eclipse.org/mailman/listinfo/jetty-users >> > > > > > > > >>> >> > >> > > > > > > > >>> >> > >> > > > > > > > >>> >> > _______________________________________________ >> > > > > > > > >>> >> > jetty-users mailing list >> > > > > > > > >>> >> > jetty-users@xxxxxxxxxxx >> > > > > > > > >>> >> > https://dev.eclipse.org/mailman/listinfo/jetty-users >> > > > > > > > >>> >> > >> > > > > > > > >>> >> > >> > > > > > > > >>> >> _______________________________________________ >> > > > > > > > >>> >> jetty-users mailing list >> > > > > > > > >>> >> jetty-users@xxxxxxxxxxx >> > > > > > > > >>> >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> > > > > > > > >>> > >> > > > > > > > >>> > >> > > > > > > > >>> > _______________________________________________ >> > > > > > > > >>> > jetty-users mailing list >> > > > > > > > >>> > jetty-users@xxxxxxxxxxx >> > > > > > > > >>> > https://dev.eclipse.org/mailman/listinfo/jetty-users >> > > > > > > > >>> > >> > > > > > > > >>> > >> > > > > > > > >>> _______________________________________________ >> > > > > > > > >>> jetty-users mailing list >> > > > > > > > >>> jetty-users@xxxxxxxxxxx >> > > > > > > > >>> https://dev.eclipse.org/mailman/listinfo/jetty-users >> > > > > > > > >> >> > > > > > > > >> >> > > > > > > > >> _______________________________________________ >> > > > > > > > >> jetty-users mailing list >> > > > > > > > >> jetty-users@xxxxxxxxxxx >> > > > > > > > >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> > > > > > > > >> >> > > > > > > > >> >> > > > > > > > > >> > > > > > > >> > > > > > >> > > > > > >> > > > > > _______________________________________________ >> > > > > > jetty-users mailing list >> > > > > > [email protected] >> > > > > > https://dev.eclipse.org/mailman/listinfo/jetty-users >> > > > > > >> > > > > > >> > > > >> > > >> > >> > > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users > _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
