I'm more then happy to help in whatever way I can. I sent Jules the server logs from JBoss, but I suspect those weren't helpful being that from JBoss's perspective, there didn't appear to be any deployment errors generated.
Let me know what else I can do to help you get what information you need to fix the problem. Dustin Barlow -----Original Message----- From: Greg Wilkins [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 11, 2002 5:43 AM To: Jules Gosnell Cc: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] [ jboss-Bugs-604085 ] Jetty is not deploying packed wars Jules Gosnell wrote: > This is most likely the same as the spaces within paths issue. > > Because the war is packed, it is unpacked to a temporary dir, which has > spaces in it. > > Greg is looking at it. No I'm not! I've had a total windows failure and after spending hours rebuilding that damn thing - applying service pack 3 rendered the thing unbootable again. I've had one user send me some detailed trace on it, and I'm currently suspecting something about classloading can't handle %20 in file URLs. But without a system I can't test. Jan has tried to reproduce the problem on her, but spaces in filenames are working without problem on straight jetty. So I need verbose debug traces from users with failures -- PLEASE. I'm trying to put a windows dev system back together today... cheers > > Jules > > [EMAIL PROTECTED] wrote: > >> Bugs item #604085, was opened at 2002-09-03 10:34 >> You can respond by visiting: >> https://sourceforge.net/tracker/?func=detail&atid=376685&aid=604085&group_id =22866 >> >> >> Category: JBossServer >> Group: v3.0 Rabbit Hole >> Status: Open >> Resolution: None >> Priority: 5 >> Submitted By: Scott M Stark (starksm) >> Assigned to: Nobody/Anonymous (nobody) >> Summary: Jetty is not deploying packed wars >> >> Initial Comment: >> I am seeing a problem with Jetty not deploying wars from the deploy >> directory in the current 3.0 and 3.2 branches. If you take the >> default/deploy/jmx-console.war and repack this: >> >> deploy 414>ls -l jmx-console.war >> -rw-r--r-- 1 starksm None 58165 Sep 3 13:17 jmx-console.war >> deploy 415>jar -tf jmx-console.war >> META-INF/ >> META-INF/MANIFEST.MF >> WEB-INF/ >> WEB-INF/classes/ >> WEB-INF/classes/org/ >> WEB-INF/classes/org/jboss/ >> WEB-INF/classes/org/jboss/jmx/ >> WEB-INF/classes/org/jboss/jmx/adaptor/ >> WEB-INF/classes/org/jboss/jmx/adaptor/control/ >> WEB- >> INF/classes/org/jboss/jmx/adaptor/control/AttrResultInfo. >> class >> WEB- >> INF/classes/org/jboss/jmx/adaptor/control/OpResultInfo. >> class >> WEB- >> INF/classes/org/jboss/jmx/adaptor/control/Server.class >> WEB-INF/classes/org/jboss/jmx/adaptor/html/ >> WEB- >> INF/classes/org/jboss/jmx/adaptor/html/HtmlAdaptorServ >> let.class >> WEB-INF/classes/org/jboss/jmx/adaptor/model/ >> WEB- >> INF/classes/org/jboss/jmx/adaptor/model/DomainData.cl >> ass >> WEB- >> INF/classes/org/jboss/jmx/adaptor/model/MBeanData.cl >> ass >> WEB-INF/classes/roles.properties >> WEB-INF/classes/users.properties >> WEB-INF/web.xml >> displayMBeans.jsp >> displayOpResult.jsp >> images/ >> images/head_blue.gif >> index.jsp >> inspectMBean.jsp >> style_master.css >> >> Startup the default config and although Jetty says the war was deployed: >> >> 13:18:20,769 INFO [MainDeployer] Starting deployment of package: >> file:/C:/usr/J >> Boss3.2/jboss-all/build/output/jboss- >> 3.2.0RC1/server/default/deploy/jmx-console. >> war >> 13:18:21,340 INFO [jbossweb] Registered >> jboss.web:Jetty=0,JBossWebApplicationCo >> ntext=0,context=/jmx-console >> 13:18:21,390 INFO [jbossweb] Checking Resource aliases >> 13:18:21,490 INFO [jbossweb] Extract >> jar:file:/C:/usr/JBoss3.2/jboss-all/build/ >> output/jboss- >> 3.2.0RC1/server/default/tmp/deploy/server/default/deploy/ >> jmx-consol >> e.war/61.jmx-console.war!/ to C:\DOCUME~1 >> \starksm\LOCALS~1\Temp\Jetty_0_0_0_0_80 >> 80__jmx-console\webapp >> 13:18:22,312 INFO [jbossweb] Started >> WebApplicationContext[/jmx-console,jar:fil >> e:/C:/usr/JBoss3.2/jboss-all/build/output/jboss- >> 3.2.0RC1/server/default/tmp/depl >> oy/server/default/deploy/jmx-console.war/61.jmx- >> console.war!/] >> 13:18:22,392 INFO [jbossweb] successfully deployed >> file:/C:/usr/JBoss3.2/jboss- >> all/build/output/jboss- >> 3.2.0RC1/server/default/tmp/deploy/server/default/deploy/ >> jmx-console.war/61.jmx-console.war to /jmx-console >> 13:18:22,392 INFO [MainDeployer] Deployed package: >> file:/C:/usr/JBoss3.2/jboss- >> all/build/output/jboss-3.2.0RC1/server/default/deploy/jmx- >> console.war >> 13:18:22,402 INFO [URLDeploymentScanner] Started >> >> It is in fact not accessible: >> >> security 409>wget http://localhost:8080/jmx-console >> --13:21:08-- http://localhost:8080/jmx-console >> => `jmx-console' >> Resolving localhost... done. >> Connecting to localhost[127.0.0.1]:8080... connected. >> HTTP request sent, awaiting response... 302 Moved Temporarily >> Location: http://localhost:8080/jmx-console/ [following] >> --13:21:08-- http://localhost:8080/jmx-console/ >> => `index.html' >> Connecting to localhost[127.0.0.1]:8080... connected. >> HTTP request sent, awaiting response... 404 /jmx- >> console/ Not Found >> 13:21:08 ERROR 404: /jmx-console/ Not Found. >> >> >> If the jmx-console.war is unpacked then the content is accessible: >> >> security 410>wget http://localhost:8080/jmx-console >> --13:25:25-- http://localhost:8080/jmx-console >> => `jmx-console' >> Resolving localhost... done. >> Connecting to localhost[127.0.0.1]:8080... connected. >> HTTP request sent, awaiting response... 302 Moved Temporarily >> Location: http://localhost:8080/jmx-console/ [following] >> --13:25:25-- http://localhost:8080/jmx-console/ >> => `index.html' >> Connecting to localhost[127.0.0.1]:8080... connected. >> HTTP request sent, awaiting response... 200 OK >> Length: unspecified [text/html] >> >> [ <=> ] 46,675 735.18K/s >> >> 13:25:30 (735.18 KB/s) - `index.html' saved [46675] >> >> These messages are for the current 3.2 build. The 3.0 build actually >> displays an >> info message with a "Internal Error..." msg during deployment of the war: >> >> 12:57:23,161 INFO [MainDeployer] Starting deployment of package: >> file:/C:/usr/S >> akonnet/jboss-3.0.3RC1/server/default/deploy/jmx- >> console.war >> 12:57:23,442 INFO [jbossweb] Registered >> jboss.web:Jetty=0,JBossWebApplicationCo >> ntext=1,context=/jmx-console >> 12:57:23,472 INFO [jbossweb] Extract >> jar:file:/C:/usr/Sakonnet/jboss-3.0.3RC1/s >> erver/default/tmp/deploy/server/default/deploy/jmx- >> console.war/61.jmx-console.wa >> r!/ to C:\DOCUME~1\starksm\LOCALS~1 >> \Temp\Jetty_0_0_0_0_8080__jmx-console\webapp >> 12:57:23,942 INFO [jbossweb] Started >> WebApplicationContext[/jmx-console,jar:fil >> e:/C:/usr/Sakonnet/jboss- >> 3.0.3RC1/server/default/tmp/deploy/server/default/deplo >> y/jmx-console.war/61.jmx-console.war!/] >> 12:57:23,942 INFO [jbossweb] Internal Error: File /WEB-INF/web.xml >> not found >> 12:57:23,942 INFO [jbossweb] successfully deployed >> file:/C:/usr/Sakonnet/jboss- >> 3.0.3RC1/server/default/tmp/deploy/server/default/deploy/ >> jmx-console.war/61.jmx- >> console.war to /jmx-console >> 12:57:23,942 INFO [MainDeployer] Deployed package: >> file:/C:/usr/Sakonnet/jboss- >> 3.0.3RC1/server/default/deploy/jmx-console.war >> >> but does claim that the war was deployed but it is not accessible. >> >> >> ---------------------------------------------------------------------- >> >> Comment By: Nobody/Anonymous (nobody) >> Date: 2002-09-10 06:00 >> >> Message: >> Logged In: NO >> I found that if you change the TEMP environment variable in Windows >> 2000 to be c:\temp, then war files will deploy *and* function >> properly. I'm not entirely sure that it's strickly a problem with >> spaces in the path name because JBoss's jmx- >> console worked just when the war files were exploded into c:\Documents >> and Settings\<user>\Local Settings\Temp. Deployment does consistently >> work if you do change the TEMP env variable to point to a short >> directory path with no spaces. >> >> My suggestion was to follow what Tomcat does and to store the temp >> files in /<jboss>/server/<target>/tmp as that seems the most >> appropriate to me. >> >> ---------------------------------------------------------------------- >> >> Comment By: Scott M Stark (starksm) >> Date: 2002-09-09 15:49 >> >> Message: >> Logged In: YES user_id=175228 >> >> If I set java.io.tmpdir=D:/temp/web then the war is accessible: >> >> 600474 624>ls /temp/web/Jetty_0_0_0_0_8080__test/webapp/WEB >> -INF/ >> web.xml >> 600474 625>wget http://localhost:8080/test/index.html >> --15:48:31-- http://localhost:8080/test/index.html >> => `index.html' >> Resolving localhost... done. >> Connecting to localhost[127.0.0.1]:8080... connected. >> HTTP request sent, awaiting response... 200 OK >> Length: 61 [text/html] >> >> 100%[====================================>] 61 59.57K/s >> ETA 00:00 >> >> 15:48:32 (59.57 KB/s) - `index.html' saved [61/61] >> >> >> ---------------------------------------------------------------------- >> >> Comment By: Nobody/Anonymous (nobody) >> Date: 2002-09-09 15:35 >> >> Message: >> Logged In: NO >> I reproduce this error on my WinXP setup ... no spaces in these >> filenames though... >> >> file:/C:/jboss/server/default/tmp/deploy/server/default/deploy/in >> terest.ear/101.interest.ear-contents/interest.war!/ to >> C:\WINNT\TEMP\Jetty__8080___interest\webapp >> >> ---------------------------------------------------------------------- >> >> Comment By: Jan Bartel (janb) >> Date: 2002-09-09 15:26 >> >> Message: >> Logged In: YES user_id=45251 >> >> Scott, >> >> It could be a problem with complex dir names under Windows >> (ie possibly dir names with spaces in them). You could try >> setting Jetty's temp directory explicitly to something >> simple (like c:\temp) by setting the System property >> "java.io.tmpdir". We will investigate this further also, >> however as none of us currently has access to a Windows >> environment, we are having to set one up which may take a >> bit of time. >> >> >> ---------------------------------------------------------------------- >> >> Comment By: Scott M Stark (starksm) >> Date: 2002-09-09 14:29 >> >> Message: >> Logged In: YES user_id=175228 >> >> This appears to be a win32 specific issue as the attached war deploys >> fine on linux but fails on both Windows2000 and WindowsXP. The >> attached deploy.log is the server.log output for the deployment of the >> test.war. >> >> ---------------------------------------------------------------------- >> >> You can respond by visiting: >> https://sourceforge.net/tracker/?func=detail&atid=376685&aid=604085&group_id =22866 >> >> >> >> ------------------------------------------------------- >> 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 > > > -- Greg Wilkins<[EMAIL PROTECTED]> Phone/fax: +44 7092063462 Mort Bay Consulting Australia and UK. http://www.mortbay.com ------------------------------------------------------- In remembrance www.osdn.com/911/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ------------------------------------------------------- In remembrance www.osdn.com/911/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
