Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-742

JMSCorrelationID together with Oracle AQ

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.3
    • Fix Version/s: 2.0.4
    • Component/s: Core
    • Environment:
      spring-ws-2.0.3.RELEASE, spring-framework-3.1.0.RC1, AQAPI12_BUILT_WITH_RDBMS_VERSION_10.2

      Description

      In org.springframework.ws.transport.jms.JmsSenderConnection.onReceiveBeforeRead() the following code set the value of messageSelector:

      if (responseDestination instanceof TemporaryQueue || responseDestination instanceof TemporaryTopic) {
             messageConsumer = session.createConsumer(responseDestination);
      } else {
             String messageId = requestMessage.getJMSMessageID().replaceAll("'", "''");
             String messageSelector = "JMSCorrelationID = '" + messageId + "'";
             messageConsumer = session.createConsumer(responseDestination, messageSelector);
      }

      If I'm using Oracle AQ, expression (responseDestination instanceof TemporaryQueue) always returns true (See Oracle Streams Advanced Queuing Java API Reference http://docs.oracle.com/cd/B19306_01/server.102/b14291/oracle/jms/AQjmsDestination.html). Regarding this it is impossible to use JMSCorrelationID together with Oracle AQ.

        Activity

        Hide
        arjen.poutsma Arjen Poutsma added a comment -

        Fixed.

        Show
        arjen.poutsma Arjen Poutsma added a comment - Fixed.
        Hide
        arjen.poutsma Arjen Poutsma added a comment -

        Closing old issues

        Show
        arjen.poutsma Arjen Poutsma added a comment - Closing old issues

          People

          • Assignee:
            arjen.poutsma Arjen Poutsma
            Reporter:
            amarakov Marakov Andrey
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - Not Specified
              Not Specified
              Logged:
              Time Spent - 1h 10m
              1h 10m