XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • JBossAS-5.0.1.GA
    • None
    • VFS
    • None

      testDefaultScheduler:

      This tests calls:

      deploy(file);

      where file is defined as:

      private String file = "../resources/util/test-default-scheduler-service.xml";

      Deployment Fails:

      2009-02-06 16:02:50,778 INFO [org.jboss.deployment.MainDeployer] (RMI TCP Connection(553)-127.0.0.1) deploy, url=file:/home/smcgowan2/workspace/Branch_5_0/testsuite/output/lib/../resources/util/test-default-scheduler-service.xml
      2009-02-06 16:02:50,778 WARN [org.jboss.deployment.MainDeployer] (RMI TCP Connection(553)-127.0.0.1) Failed to deploy: file:/home/smcgowan2/workspace/Branch_5_0/testsuite/output/lib/../resources/util/test-default-scheduler-service.xml
      java.io.IOException: Using reverse path on top file handler: FileHandler@23003619[path= context=file:/home/smcgowan2/workspace/Branch_5_0/testsuite/output/lib real=file:/home/smcgowan2/workspace/Branch_5_0/testsuite/output/lib/], ../resources/util/test-default-scheduler-service.xml/
      at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:649)
      at org.jboss.virtual.plugins.context.file.FileHandler.getChild(FileHandler.java:307)
      at org.jboss.virtual.plugins.registry.DefaultVFSRegistry.findHandler(DefaultVFSRegistry.java:103)
      at org.jboss.virtual.plugins.registry.DefaultVFSRegistry.getFile(DefaultVFSRegistry.java:87)
      at org.jboss.virtual.plugins.registry.DefaultVFSRegistry.getFile(DefaultVFSRegistry.java:119)
      at org.jboss.virtual.VFS.getRoot(VFS.java:251)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:815)

      This failure is seen on Hudson and is reproducable using test target jboss-all-config-tests. If I start the server and run this with one-test I do not see the failure.

      2009-02-06 16:27:58,321 INFO [org.jboss.deployment.MainDeployer] (RMI TCP Connection(38)-127.0.0.1) deploy, url=file:/TEST/Branch_5_0/testsuite/output/lib/../resources/util/test-default-scheduler-service.xml
      2009-02-06 16:27:58,322 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] (RMI TCP Connection(38)-127.0.0.1) Add deployment: vfsfile:/TEST/Branch_5_0/testsuite/output/lib/../resources/util/test-default-scheduler-service.xml
      2009-02-06 16:27:58,322 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] (RMI TCP Connection(38)-127.0.0.1) Scheduling deployment: vfsfile:/TEST/Branch_5_0/testsuite/output/lib/../resources/util/test-default-scheduler-service.xml parent=null
      2009-02-06 16:27:58,322 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] (RMI TCP Connection(38)-127.0.0.1) Deploying vfsfile:/TEST/Branch_5_0/testsuite/output/lib/../resources/util/test-default-scheduler-service.xml
      2009-02-06 16:27:58,327 DEBUG [org.jboss.system.deployers.SARDeployer] (RMI TCP Connection(38)-127.0.0.1) Parsing: test-default-scheduler-service.xml
      2009-02-06 16:27:58,332 DEBUG [org.jboss.system.deployers.SARDeployer] (RMI TCP Connection(38)-127.0.0.1) <server>
      <!-- Scheduler, infinite reps -->
      <!-- Note: No good way to verify this works correctly -->
      <mbean code='org.jboss.varia.scheduler.Scheduler' name='test:service=Scheduler'>
      <attribute name='StartAtStartup'>true</attribute>
      <attribute name='SchedulableClass'>org.jboss.varia.scheduler.example.SchedulableExample</attribute>
      <attribute name='SchedulableArguments'>Schedulabe Test,12345</attribute>
      <attribute name='SchedulableArgumentTypes'>java.lang.String,int</attribute>
      <attribute name='InitialStartDate'>0</attribute>
      <attribute name='SchedulePeriod'>500</attribute>
      <attribute name='InitialRepetitions'>-1</attribute>
      </mbean>
      <!-- Scheduler, one rep -->

            ajustin@redhat.com Ales Justin
            smcgowan@redhat.com Shelly McGowan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: