Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-2366

[EAP] default ee datasource setting broken

XMLWordPrintable

    • Hide

      deploying with both a datasource configured via DB_SERVICE_PREFIX_MAPPING and an A-MQ broker, e.g.:

        - env:
    - name: DB_SERVICE_PREFIX_MAPPING
      value: testdb-postgresql=TESTDB_POSTGRESQL
    - name: TESTDB_POSTGRESQL_PASSWORD
      value: testpwd
    - name: TESTDB_POSTGRESQL_DATABASE
      value: testdb
    - name: TESTDB_POSTGRESQL_USERNAME
      value: testuser
    - name: EAP_JMS_ID_ME
      value: node2
    - name: JBAMQ_PROTOCOL
      value: tcp
    - name: JBAMQ_USERNAME
      value: mqUser
    - name: MQ_SERVICE_PREFIX_MAPPING
      value: jbamq-amq=JBAMQ
    - name: JBAMQ_QUEUES
      value: bmtQueue,xaQueue,plainQueue
    - name: EAP_JMS_ID_PARTNER
      value: node1
    - name: JBAMQ_PASSWORD
      value: mqPassword
    - name: JBAMQ_TOPICS
      value: bmtTopic,plainTopic

      notice the generated default ee datasource is wrong.

      Show
      deploying with both a datasource configured via DB_SERVICE_PREFIX_MAPPING and an A-MQ broker, e.g.: - env: - name: DB_SERVICE_PREFIX_MAPPING value: testdb-postgresql=TESTDB_POSTGRESQL - name: TESTDB_POSTGRESQL_PASSWORD value: testpwd - name: TESTDB_POSTGRESQL_DATABASE value: testdb - name: TESTDB_POSTGRESQL_USERNAME value: testuser - name: EAP_JMS_ID_ME value: node2 - name: JBAMQ_PROTOCOL value: tcp - name: JBAMQ_USERNAME value: mqUser - name: MQ_SERVICE_PREFIX_MAPPING value: jbamq-amq=JBAMQ - name: JBAMQ_QUEUES value: bmtQueue,xaQueue,plainQueue - name: EAP_JMS_ID_PARTNER value: node1 - name: JBAMQ_PASSWORD value: mqPassword - name: JBAMQ_TOPICS value: bmtTopic,plainTopic notice the generated default ee datasource is wrong.
    • CLOUD Maintenance Sprint 16

      The EE default datasource should be setup from the first configured datasource in

      https://github.com/jboss-openshift/cct_module/blob/sprint-14/os-eap-launch/added/launch/datasource-common.sh#L106

      this doesn't work, as the "$jndi" is undefined in the function (is local in inject_datasource )

      (when an A-MQ connection is used, which sets the global "$jndi", the output is actually such that the datasource is set to a connection factory)

      datasource="java:/jbamq-amq/ConnectionFactory"
jms-connection-factory="java:/jbamq-amq/ConnectionFactory"

              kwills@redhat.com Ken Wills
              maschmid@redhat.com Marek Schmidt
              Marek Schmidt Marek Schmidt
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: