If you are deploying to a running server the error trace should be in geronimo.log

thanks
david jencks

On Oct 18, 2005, at 1:48 PM, Lin Sun (JIRA) wrote:

Deployer failed to deploy certain applications if geronimo is installed to a directory that has space ----------------------------------------------------------------------- ------------------------------

         Key: GERONIMO-1089
         URL: http://issues.apache.org/jira/browse/GERONIMO-1089
     Project: Geronimo
        Type: Bug
  Components: deployment
    Versions: 1.0-M5
 Environment: Windows + Tomcat
    Reporter: Lin Sun


My geronimo is at directory e:\program files\geronimo\modules\assembly\target\geronimo-1.0-M5. When I deployed daytrader, I got the following failure:

e:\program files\geronimo\modules\assembly\target\geronimo-1.0-M5\bin>deploy.bat deploy "\program files\sandbox\samples\Trade\daytrader-ear-1.0-SNAPSHOT.ear" "\
program files\sandbox\samples\Trade\dayTrader-plan.xml"
Username: system
Password:

Error: Unable to distribute daytrader-ear-1.0-SNAPSHOT.ear: Bad path
    to external module, a connector caused by Illegal character in
    opaque part at index 2: e:\program
files\geronimo\modules\assembly\target\geronimo-1.0- M5\repository\tranql/rar
s/tranql-connector-derby-embed-xa-1.0.rar

This is caused by deployer not able to handle the " <external-path>tranql/rars/tranql-connector-derby-embed-xa-1.0.rar</ external-path>" element specified in the daytrader-plan.xml.

If I broke the daytrader database resource plan to a seperate plan, I can deploy the TradeDataSource as the workaround:

e:\program files\geronimo\modules\assembly\target\geronimo-1.0-M5\bin>deploy.bat deploy "\program files\sandbox\samples\Trade\dayTrader-dbplan.xml" ..\repositor
y\tranql\rars\tranql-connector-derby-embed-xa-1.0.rar
Username: system
Password:

    Deployed TradeDataSource

Similar problem happens with the "<external-rar>activemq/rars/activemq-ra-3.2-M1.rar</external-rar>" element.

I don't mind digging more into this...any help/hints is appreciated. I figure I should start at deployer.log, but I didn't see a deployer.log generated.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Reply via email to