Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 9214 invoked from network); 14 Feb 2008 22:23:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Feb 2008 22:23:46 -0000 Received: (qmail 29200 invoked by uid 500); 14 Feb 2008 22:23:34 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 29150 invoked by uid 500); 14 Feb 2008 22:23:34 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 29133 invoked by uid 99); 14 Feb 2008 22:23:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Feb 2008 14:23:34 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Feb 2008 22:22:48 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 3154771403F for ; Thu, 14 Feb 2008 14:23:08 -0800 (PST) Message-ID: <31230286.1203027788188.JavaMail.jira@brutus> Date: Thu, 14 Feb 2008 14:23:08 -0800 (PST) From: "Jarek Gawor (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Commented: (GERONIMO-3836) Deployment fails with FNFE due to missing jline_.dll on Cygwin In-Reply-To: <2943709.1202695568350.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/GERONIMO-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569111#action_12569111 ] Jarek Gawor commented on GERONIMO-3836: --------------------------------------- I was able to replicate this problem with cygwin but not gsh. And the problem seemed to be related to the GERONIMO_TMPDIR which deploy.sh sets. I changed one line in deploy.sh from: GERONIMO_TMPDIR=var/temp to: GERONIMO_TMPDIR=$GERONIMO_HOMEvar/temp deploy.sh worked fine in cygwin. But I'm not really sure why this is a problem now. > Deployment fails with FNFE due to missing jline_.dll on Cygwin > -------------------------------------------------------------- > > Key: GERONIMO-3836 > URL: https://issues.apache.org/jira/browse/GERONIMO-3836 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment > Affects Versions: 2.2 > Reporter: Jacek Laskowski > > Meant to deploy a webapp from a directory outside Geronimo's installation dir. Deployer worked with -u and -p options although it spit FNFE exception, but it failed without them. > jlaskowski@dev /cygdrive/c/apps/apache-wicket/src/jdk-1.5/wicket-examples/target > $ c\:/geronimo/bin/deploy.sh -u system -p manager deploy wicket-examples.war > Using GERONIMO_BASE: c:\geronimo > Using GERONIMO_HOME: c:\geronimo > Using GERONIMO_TMPDIR: c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp > Using JRE_HOME: c:\apps\java5\jre > java.io.FileNotFoundException: c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp\jline_.dll (The system cannot find the path specified) > at java.io.FileOutputStream.open(Native Method) > at java.io.FileOutputStream.(FileOutputStream.java:179) > at java.io.FileOutputStream.(FileOutputStream.java:131) > at jline.WindowsTerminal.loadLibrary(WindowsTerminal.java:274) > at jline.WindowsTerminal.initializeTerminal(WindowsTerminal.java:227) > at jline.Terminal.setupTerminal(Terminal.java:77) > at jline.Terminal.getTerminal(Terminal.java:28) > at jline.ConsoleReader.(ConsoleReader.java:167) > at jline.ConsoleReader.(ConsoleReader.java:162) > at org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:164) > at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45) > at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67) > at org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31) > Deployed default/wicket-examples/1202695110250/war @ > /wicket-examples > jlaskowski@dev /cygdrive/c/apps/apache-wicket/src/jdk-1.5/wicket-examples/target > $ c\:/geronimo/bin/deploy.sh undeploy default/wicket-examples/1202695110250/war > Using GERONIMO_BASE: c:\geronimo > Using GERONIMO_HOME: c:\geronimo > Using GERONIMO_TMPDIR: c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp > Using JRE_HOME: c:\apps\java5\jre > java.io.FileNotFoundException: c:\apps\apache-wicket\src\jdk-1.5\wicket-examples\target\var\temp\jline_.dll (The system cannot find the path specified) > at java.io.FileOutputStream.open(Native Method) > at java.io.FileOutputStream.(FileOutputStream.java:179) > at java.io.FileOutputStream.(FileOutputStream.java:131) > at jline.WindowsTerminal.loadLibrary(WindowsTerminal.java:274) > at jline.WindowsTerminal.initializeTerminal(WindowsTerminal.java:227) > at jline.Terminal.setupTerminal(Terminal.java:77) > at jline.Terminal.getTerminal(Terminal.java:28) > at jline.ConsoleReader.(ConsoleReader.java:167) > at jline.ConsoleReader.(ConsoleReader.java:162) > at org.apache.geronimo.deployment.cli.InputPrompt.(InputPrompt.java:42) > at org.apache.geronimo.deployment.cli.ServerConnection.doAuthPromptAndRetry(ServerConnection.java:230) > at org.apache.geronimo.deployment.cli.ServerConnection.tryToConnect(ServerConnection.java:190) > at org.apache.geronimo.deployment.cli.ServerConnection.(ServerConnection.java:94) > at org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:161) > at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45) > at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:67) > at org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31) > Username: system > Password: Error: Login Failed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.