Uploaded image for project: 'Red Hat CodeReady Studio (devstudio)'
  1. Red Hat CodeReady Studio (devstudio)
  2. JBDS-1670

Seeing "Target runtime jboss-soa-p-5.0 Runtime is not defined." error - in spite of the name of the runtime being set - with JBDS + AS + JBossESB

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 4.1.0.CR1
    • 4.0.0.GA
    • integration
    • None
    • Hide

      1. Install JBoss AS 5.1
      2. Install JBossESB into JBossAS
      3. Install JBDS
      4. Configure the JBoss AS runtime as "jboss-soa-p-5.0 Runtime"
      5. Install the SOA-P 5.0 helloworld example

      Show
      1. Install JBoss AS 5.1 2. Install JBossESB into JBossAS 3. Install JBDS 4. Configure the JBoss AS runtime as "jboss-soa-p-5.0 Runtime" 5. Install the SOA-P 5.0 helloworld example

    Description

      With JBDS 4 GA + AS 5.1 GA and JBossESB 4.9, I'm seeing this issue with the ESB examples

      Regardless of whether the AS server runtime is named "jboss-soa-p-5.0 Runtime", this error is raised:
      Target runtime jboss-soa-p-5.0 Runtime is not defined.

      See attached screenshots and .log file

      Attachments

        1. log
          29 kB
        2. Screenshot-200.png
          Screenshot-200.png
          181 kB
        3. Screenshot-201.png
          Screenshot-201.png
          166 kB
        4. Screenshot-202.png
          Screenshot-202.png
          147 kB
        5. Screenshot-203.png
          Screenshot-203.png
          163 kB
        6. Screenshot-204.png
          Screenshot-204.png
          176 kB

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1986 "Target runtime jboss-soa-p-5.0 Runtime is not defined." error - JBDS5 M5a and SOA-P 5.2

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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1858 ESB 5.0 quickstarts readme files instruct the user to only use a specific runtime name - but that requirement is no longer needed

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              jpeterka_jira Jiri Peterka (Inactive)
              ldimaggi@redhat.com Len DiMaggio
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: