Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-3503

Clustering testbeancluster test failures - Deployment Error

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • JBossAS-4.0.5.CR1
    • JBossAS-4.0.5.CR1
    • None
    • None

    Description

      Deployment of the test resources for the following tests fail with the error shown below. Hence the tests cannot connect to the service as shown in the results on CC
      http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-sun-1.4/20060809211108/results/index.html

      Server log for the errors shown below:
      http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-sun-1.4/20060809211108/build/output/jboss-4.0.5.CR1/server/cluster-UDP-0/log/server.log

      org.jboss.test.testbeancluster.test.CacheInvalidationUnitTestCase(Default-UDP)
      org.jboss.test.testbeancluster.test.RetryInterceptorUnitTestCase(Default-UDP)
      org.jboss.test.testbeancluster.test.SingleRetryInterceptorUnitTestCase(Default-UDP)

      2006-08-09 22:39:57,054 DEBUG [org.jboss.ejb.EjbModule] Starting failed jboss.j2ee:module=test-cif.jar,service=EjbModule
      org.jboss.deployment.DeploymentException: Error: can't find data source: java:/CIFTestDS; - nested throwable: (javax.naming.NameNotFoundException: CIFTestDS not bound)
      at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.init(JDBCEntityBridge.java:153)
      at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCStoreManager.java:435)
      at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:368)
      at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:172)
      at org.jboss.ejb.EjbModule.startService(EjbModule.java:411)

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. JBAS-3435 Get the 4.0.5.CR1 testsuite passing

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is blocked by

          Feature Request - Feature requests from customers and/or users JBAS-2904 Allow for ear modules to be deployed in the order that they are declared in application.xml

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              vickyk_jira Vicky Kak (Inactive)
              rrajasek@redhat.com Rajesh Rajasekaran
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: