[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1186) maxBatchTime stops working after the connection between source and target servers is lost

[Ross Nicholson (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMESSAGING-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464625#action_12464625 ] 

Ross Nicholson commented on JBMESSAGING-1186:
---------------------------------------------

I'm currently having similar issues with this. Note that unlike the above issue the remaining messages are never sent until the maxBatchSize is reached again. 

I'm using the latest Beta 5.1.0 of AS5.

Link to forum post: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=154429

> maxBatchTime stops working after the connection between source and target servers is lost
> -----------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1186
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1186
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.SP1
>         Environment: Windows XP 64
> Java 6
> JBoss 4.2.2
>            Reporter: Maurice Zeijen
>            Assignee: Howard Gao
>             Fix For: 1.4.0.SP3.CP08, 1.4.4.GA
>
>
> We have the following Situation:
> A bridge MBean is setup to bridge between a local source and a remote target. The MaxBatchSize attribute is set to 5 and the MaxBatchTime is set to 10000. So the configuration looks like this:
> <mbean code="org.jboss.jms.server.bridge.BridgeService" name="jboss.messaging:service=Bridge,name=wai_sync_customer_bridge" xmbean-dd="xmdesc/Bridge-xmbean.xml">
>        <depends optional-attribute-name="SourceProviderLoader">jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>
>        <depends optional-attribute-name="TargetProviderLoader">jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider</depends>
>        <attribute name="SourceDestinationLookup">/queue/local</attribute>
>        <attribute name="TargetDestinationLookup">/queue/remote</attribute>
>        <attribute name="QualityOfServiceMode">0</attribute>
>        <attribute name="MaxBatchSize">5</attribute>
>        <attribute name="MaxBatchTime">10000</attribute>
>        <attribute name="FailureRetryInterval">5000</attribute>
>        <attribute name="MaxRetries">-1</attribute>
>        <attribute name="AddMessageIDInHeader">false</attribute>
>        <depends>jboss.messaging.destination:name=local,service=Queue</depends>
>   </mbean>
> If the connection between the two servers is available then the MaxBatchTime works fine. After 10 seconds all messages are moved from local queue to remote queue if there are less then 5 messages in the queue. But when for some reason the connection is lost and after a while restored again then the MaxBatchTime doesn't work any more. Luckily the MaxBatchSize still works. Also the MaxBatchSize doesn't work when the remote server isn't available when the bridge on the local server is started. 
> Restarting the bridge makes the MaxBatchTime work again.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira