Cargo

ExistingConfigurationTest.testDeployWarStatically fails on windows for weblogic8x

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.0
  • Fix Version/s: None
  • Component/s: Weblogic
  • Labels:
    None
  • Environment:
    windows xp weblogic8x
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

file copies to core\samples\java\target\weblogic8x\installed\ExistingConfigurationTest\testDeployWarStatically\container\applications

the following clue from domain.log

####<Nov 30, 2008 8:49:58 PM GMT> <Error> <Deployer> <LDNDTE4PC51174> <server> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149225> <Unable to unpack the application _appsdir_simple-war-1.0-SNAPSHOT_war to the file .\server\stage_appsdir_simple-war-1.0-SNAPSHOT_war\simple-war-1.0-SNAPSHOT.war.
java.lang.Throwable: Couldn't make directory: 'C:\cargo\tmp\trunks\core\samples\java\target\weblogic8x\installed\ExistingConfigurationTest\testDeployWarStatically\container\server\stage_appsdir_simple-war-1.0-SNAPSHOT_war\simple-war-1.0-SNAPSHOT.war\META-INF\maven\org.codehaus.cargo\simple-war'
at weblogic.utils.jars.JarUtils.ensureDirectory(JarUtils.java:161)
at weblogic.utils.jars.JarUtils.unpackJar(JarUtils.java:87)
at weblogic.utils.jars.JarUtils.unpackRemoteJar(JarUtils.java:141)
at weblogic.management.deploy.slave.SlaveDeployer$Application.explode(SlaveDeployer.java:2952)
at weblogic.management.deploy.slave.SlaveDeployer$Application.restage(SlaveDeployer.java:2864)
at weblogic.management.deploy.slave.SlaveDeployer$StagingOrder.execute(SlaveDeployer.java:3391)
at weblogic.management.deploy.slave.SlaveDeployer$Application.stageFromOrder(SlaveDeployer.java:2800)
at weblogic.management.deploy.slave.SlaveDeployer$Application.stageFromTask(SlaveDeployer.java:2818)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2397)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:884)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:592)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:501)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Savas Ali Tokmen added a comment -

The path:

C:\cargo\tmp\trunks\core\samples\java\target\weblogic8x\installed\ExistingConfigurationTest\testDeployWarStatically\container\server\stage_appsdir_simple-war-1.0-SNAPSHOT_war\simple-war-1.0-SNAPSHOT.war\META-INF\maven\org.codehaus.cargo\simple-war

is 249 characters long. Java in Windows doesn't like such long paths. Is it possible to shorten it up?

Show
Savas Ali Tokmen added a comment - The path: C:\cargo\tmp\trunks\core\samples\java\target\weblogic8x\installed\ExistingConfigurationTest\testDeployWarStatically\container\server\stage_appsdir_simple-war-1.0-SNAPSHOT_war\simple-war-1.0-SNAPSHOT.war\META-INF\maven\org.codehaus.cargo\simple-war is 249 characters long. Java in Windows doesn't like such long paths. Is it possible to shorten it up?
Hide
Permalink
Adrian Cole added a comment -

hot deployer (WebLogicCopyingInstalledLocalDeployer) uses the auto-deploy directory to configure applications. When applications are deployed this way, you cannot configure how they are managed. In the case of applications with long filenames, it is not possible in jdk1.4 to use the auto-deployer.

ACTION TAKEN:
created a new deployer: WebLogic8xConfigXmlInstalledLocalDeployer
This adds elements into the config.xml file. When this is in use, applications are setup by default to 'nostage', which avoids the long filename problem

created a new deployer: WebLogic8xSwitchableLocalDeployer
This will use the hot deployer only when it must (server is running). Otherwise, it will use the more reliable config xml (cold) deployer

Tested on windows and also solaris 10

Show
Adrian Cole added a comment - hot deployer (WebLogicCopyingInstalledLocalDeployer) uses the auto-deploy directory to configure applications. When applications are deployed this way, you cannot configure how they are managed. In the case of applications with long filenames, it is not possible in jdk1.4 to use the auto-deployer. ACTION TAKEN: created a new deployer: WebLogic8xConfigXmlInstalledLocalDeployer This adds elements into the config.xml file. When this is in use, applications are setup by default to 'nostage', which avoids the long filename problem created a new deployer: WebLogic8xSwitchableLocalDeployer This will use the hot deployer only when it must (server is running). Otherwise, it will use the more reliable config xml (cold) deployer Tested on windows and also solaris 10

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.