Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-7938

Unable to connect pooled connectionFactory with camel-sjms and camel-sjms2

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: fuse-7.0
    • Fix Version/s: fuse-7.1
    • Component/s: Camel, Fuse EAP, Karaf
    • Labels:
      None
    • Environment:

      FUSE 7.0

    • Steps to Reproduce:
      Hide

      1. Start external AMQ-7 e.g. 

      docker run --rm -ti -p 61617:61616 docker-registry.engineering.redhat.com/fuse-qe/jboss-amq-7:7.1.0

      2. Start Fuse on EAP
      3. Execute command to configure external pooledConnectionFactory for AMQ-7:

      mvn clean install -Ddeploy-rar.skip=false

      4. Wait for restarting EAP and execute command to deploy the application:

      mvn clean install -Pdeploy

      Show
      1. Start external AMQ-7 e.g. docker run --rm -ti -p 61617 : 61616 docker-registry.engineering.redhat.com/fuse-qe/jboss-amq- 7 : 7.1 . 0 2. Start Fuse on EAP 3. Execute command to configure external pooledConnectionFactory for AMQ-7: mvn clean install -Ddeploy-rar.skip= false 4. Wait for restarting EAP and execute command to deploy the application: mvn clean install -Pdeploy

      Description

      Unable to connect pooledConnectionFactory configured in EAP with camel-sjms and camel-sjms2. The pooledConnectionFactory is configured according the instructions in EAP 7.1 documentation for connecting to external AMQ-7. To configure camel-sjms, I followed instruction in camel-sjms documentations Plugable Connection Resource Management. The instructions are same in FUSE 6.3 documentation and also in camel-sjms2. I attached reproducer. Not sure how to implement ConnectionResource interface in order to get it working.

      If I create my own connectionFactory instance, everything works. However, certification against AMQ-7 dictates EAP 7.1 documentation. So I think we shouldn't create our own instances of connectionFactory in EAP environment.

      Exception

      15:32:51,382 ERROR [org.apache.camel.component.sjms.SjmsConsumer] (MSC service thread 1-2) Unable to create the MessageConsumer: javax.jms.IllegalStateException: This method is not applicable inside the application server. See the J2EE spec, e.g. J2EE1.4 Section 6.6

      It also applies for karaf and pooledConnectionFactory created by karaf jms command.

        Gliffy Diagrams

          Attachments

            Issue Links

            is related to

            Bug - A problem which impairs or prevents the functions of the product. ENTESB-7953 Support camel-jms options that doesn't work because of EAP's pooledConnectionFactory

            • Blocker - An issue (bug, feature, task) that blocks development and/or testing work, production could not run. An upcoming version that is affected by this issue cannot be released until it's addressed.
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. ENTESB-8049 Unable to setup credentials on SJMSBatchComponent in camel-sjms

            • Critical - An upcoming version that is affected by this issue cannot be released until it's addressed. A critical bug is one that crashes the application, causes loss of data or severe memory leak.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. ENTESB-7946 Durable Subscriber pattern does not work with the external AMQ-7

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed

              Activity

                People

                • Assignee:
                  jamesnetherton James Netherton
                  Reporter:
                  vkasala Viliam Kasala
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: