Spring Integration Aggregator + JDBC消息存储性能

Question

The performance of aggregator to process JMS messages along with persistence message store is very low. Like for a simple example given below the messages processed are between 25-28 msgs per second.

Is this the normal behavior? Or am I doing something wrong here ?

<!-- ###################### Inbound Message Adapter ####################### -->
<int-jms:message-driven-channel-adapter
    id="xmlInboundMessageAdapter"
    channel="msgUnmarshallingChannel"
    connection-factory="jmsConnectionFactory"
    destination="messsageQueue"
    acknowledge="transacted"
    concurrent-consumers="1"
    max-concurrent-consumers="5"
    auto-startup="true"/>

<!-- ###################### MSG UN-MARSHALLER ####################### -->   
<int:channel id="msgUnmarshallingChannel" />
<int:chain input-channel="msgUnmarshallingChannel" output-channel="msgHeaderEnricherChannel">
    <int-xml:unmarshalling-transformer unmarshaller="msgUnmarshaller" />
</int:chain>

<bean id="msgUnmarshaller" class="org.springframework.oxm.jaxb.Jaxb2Marshaller">
    <property name="contextPath" value="com.msg.something" />
    <property name="supportJaxbElementClass" value="true" />
</bean>

<int:channel id="msgHeaderEnricherChannel" />

<!-- ###################### SOME HEADER ENRICHMENT ####################### -->
<int:chain input-channel="msgHeaderEnricherChannel" output-channel="msgAggreggatorChannel">
    <int:header-enricher>
        <int:header name="CORRELATION_ID" expression="payload.notificationTypeId" />
    </int:header-enricher>
</int:chain>

<int:channel id="msgAggreggatorChannel" />
<int:channel id="msgAggreggatorDiscardChannel" />

<!-- ###################### AGGREGATOR WITH PERSISTENCE MSG STORE ####################### -->   
<int:aggregator
    auto-startup="true"
    send-timeout="-1"
    message-store="messageStore"
    input-channel="msgAggreggatorChannel"
    output-channel="nullChannel"
    discard-channel="msgAggreggatorDiscardChannel"
    correlation-strategy="msgCorrelationStrategy"
    release-strategy="msgReleaseStrategy"
    expire-groups-upon-completion="true" />

<!-- ###################### MSG STORE ####################### -->   
<bean id="messageStore" class="org.springframework.integration.jdbc.JdbcMessageStore">
    <property name="dataSource" ref="dataSourceSPJDBC" />
    <property name="lobHandler" ref="oracleLobHandler" />
</bean>

<bean id="oracleLobHandler" class="org.springframework.jdbc.support.lob.OracleLobHandler" />

<bean id="msgCorrelationStrategy"   class="org.springframework.integration.aggregator.HeaderAttributeCorrelationStrategy">
    <constructor-arg value="CORRELATION_ID" />
</bean>

<bean id="msgReleaseStrategy" class="org.springframework.integration.aggregator.MessageCountReleaseStrategy">
    <constructor-arg value="10"/>
</bean>

Answer 1

It's a known problem for very large groups.

Which version of Spring Integration are you using? There have been a number of improvements made in this area, the latest being in 4.2.

The current version is 4.2.4; let us know if you're still seeing problems with that version.